A resource dynamic adjustment method, device, equipment and storage medium

Abstract

The application provides a resource dynamic adjustment method and device, electronic equipment and storage medium. The resource dynamic adjustment method is applied to a first wireless network resource, the first wireless network resource includes shared resources and first priority resources allocated to a first network slice group, and the resource dynamic adjustment method includes the following steps: when a first user equipment accesses the first network slice group, if the use rate of first set priority resources of the first network slice group exceeds a first resource overload threshold, the first network slice group applies first resources from the shared resources as second priority resources of the first network slice group; wherein the first set priority resources are the first priority resources. The method in the application can adjust the priority resources in real time according to the utilization of the priority resources in each network slice group, improve the utilization rate of the total resources of the cell, and increase the number of network slice groups.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method, apparatus, electronic device, and storage medium for dynamic resource adjustment. Background Technology

[0002] With the emergence of diverse new services in the 5G and cloud era, different industries, businesses, and users are placing various quality of service (QoS) requirements on networks. For example, services such as mobile communications, smart homes, environmental monitoring, smart agriculture, and smart metering require networks to support massive device connections and frequent small packet transmissions; services such as live streaming, video backhaul, and mobile healthcare place higher demands on transmission rates; and services such as vehicle-to-everything (V2X), smart grids, and industrial control require millisecond-level latency and near 100% reliability. Therefore, 5G networks should possess capabilities such as massive access, deterministic latency, and extremely high reliability, and require the construction of flexible and dynamic networks to meet the diverse business needs of users and vertical industries.

[0003] In response to these needs, network slicing technology has emerged. Through network slicing, operators can build multiple dedicated, virtualized, and isolated logical networks on top of a common physical network to meet the differentiated network capability requirements of different customers.

[0004] Network slicing is one of the hallmark technologies that distinguishes 5G networks from 4G networks. As an end-to-end logical network that is customized on demand, network slicing is based on the Standalone (SA) architecture, which flexibly allocates network resources and enables the network to be combined on demand, virtually creating multiple logical subnets with different characteristics on a single physical 5G network.

[0005] Different network slices need to be isolated using appropriate measures. On one hand, from a quality of service (QoS) perspective, it's necessary to control and prevent sudden or abnormal traffic surges in one network slice from affecting other network slices within the same network, ensuring that services within different network slices do not interfere with each other. On the other hand, from a security perspective, some services or user information in certain network slices, such as dedicated lines for finance or government, may not be accessible to users in other network slices. Therefore, effective isolation measures are needed between different network slices. Network slice isolation measures can be divided into three levels: service isolation, resource isolation, and operational isolation.

[0006] Resource isolation refers to the isolation between network resources used by one network slice and those used by other network slices. Resource isolation can be categorized into hard isolation and soft isolation based on the degree of isolation. Hard isolation allocates completely exclusive dedicated resources to different network slices within the network. Soft isolation means that different network slices possess some independent dedicated resources while also sharing other resources within the network, thus providing isolation characteristics that meet business needs while maintaining a certain level of statistical multiplexing capability. Through both hard and soft isolation technologies, it is possible to flexibly select which network slices need exclusive resources and which network slices can share some resources, thereby achieving the fulfillment of differentiated Service Level Agreement (SLA) requirements for different services within the same network.

[0007] Multiple network slices can be grouped into the same network slice group according to certain partitioning rules. A network slice group can include multiple network slices, and the network slices in a network slice group can share all the resources within that group. Each network slice group is also configured with dedicated resources and priority resources. Existing network slice group resource allocation schemes allocate fixed dedicated and priority resources to each network slice group. However, because the situation of each network slice group is dynamic, during certain periods, no users or services need to use the allocated priority resources, resulting in idle and wasted resources. During other periods, a relatively large number of users and services access the network slice group, and the allocated priority resources may be exhausted, even reaching the maximum available resources, causing users and services hoping to access the network to be denied access. Furthermore, with this fixed allocation method, the number of network slice groups that a cell can support is very limited, and the overall capacity resources of the cell cannot be fully utilized.

[0008] Therefore, there is an urgent need for a method for prioritizing network slice group resources, which can dynamically adjust the allocation of limited resources and increase the number of network slice groups supported by a cell, so as to make full use of the cell's capacity resources. Summary of the Invention

[0009] To address the aforementioned technical problems, this invention provides a method for dynamic resource adjustment. The method is characterized in that it is applied to a first wireless network resource, which includes shared resources and a first priority resource allocated to a first network slice group. The method includes: when a first user equipment accesses the first network slice group, if the utilization rate of a first set priority resource in the first network slice group exceeds a first resource overload threshold, the first network slice group requests a first resource from the shared resources as a second priority resource for the first network slice group; wherein the first set priority resource is the first priority resource.

[0010] The network slice group priority resource dynamic adjustment method provided in this invention has the following advantages: (1) Priority resources can be adjusted in real time according to the priority resource utilization in each network slice group to improve the utilization rate of the total resources of the cell; when the priority resource utilization rate is too high, priority resources are requested from the shared resources; (2) The number of network slice groups can be increased because the priority resources of each network slice group are dynamically adjusted according to the actual usage. Priority resources of each network slice group can be dynamically allocated according to the actual situation, and the configuration of the network slice group will no longer completely depend on the initial priority resource configuration; (3) By setting a resource overload threshold, the future priority resource usage can be predicted according to the past priority resource usage in the network slice group, and priority resources can be requested in advance to improve network operation efficiency.

[0011] Preferably, the method further includes: when the second user equipment accesses the first network slice group, if the utilization rate of the first set priority resource of the first network slice group exceeds the second resource overload threshold, the first network slice group requests the second resource from the shared resources as the third priority resource of the first network slice group; wherein, the first priority resource is the sum of the first priority resource and the second priority resource, or is the second priority resource.

[0012] Preferably, the amount of the second priority resource is greater than the amount of the third priority resource. By setting a gradually decreasing resource request amount, it is possible to prevent a single network slice group from receiving too many resources in a short period of time, which could cause resource shortages when other slice groups request resources.

[0013] Preferably, the sum of the amounts of the first priority resource, the second priority resource, and the third priority resource is less than the first priority resource upper limit, which is the maximum amount of priority resources that the first network slice group can obtain. By setting the first priority resource upper limit, the maximum amount of priority resources that the first network slice group can request can be controlled, preventing a single network slice group from obtaining too many priority resources.

[0014] Preferably, the resource dynamic adjustment method further includes: when a third user equipment exits the first network slice group, if the utilization rate of a second set priority resource in the first network slice group is lower than a resource idle threshold, the first network slice group releases the third resource to shared resources. The second set priority resource includes all priority resources in the first network slice group. When the utilization rate of a priority resource in a certain network slice group is low, the resource can be released to shared resources by releasing the priority resource so that other network slice groups can use it. Here, the third user equipment can be the first user equipment, the second user equipment, or other user equipment in the first network slice group, and is not limited thereto.

[0015] Preferably, the third resource is the first resource, or the amount of the third resource is equal to the amount of the first resource. When the network slice group releases resources, the amount of resources released is the same as the amount of resources requested. By summing the released resources, the priority resources of the network slice group can be restored to their initial settings, that is, the amount of priority resources is the amount of the first priority resource. Of course, for application scenarios where resources are allocated and used on a first-come, first-served basis, the released resources are the portion of priority resources requested from the shared resources, that is, the released third resource is the requested first resource.

[0016] Preferably, the method further includes: when a fourth user equipment exits the first network slice group, if the utilization rate of the second set priority resource in the first network slice group is lower than the resource idle threshold, then the first network slice group releases the fourth resource to the shared resource; when a fifth user equipment exits the first network slice group, if the utilization rate of the second set priority resource in the first network slice group is lower than the resource idle threshold, then the first network slice group releases the fifth resource to the shared resource; wherein, the second set priority resource is all priority resources in the first network slice group; the fourth resource is the second resource, and the fifth resource is the first resource; or the resource quantity of the fourth resource is equal to the resource quantity of the second resource, and the resource quantity of the fifth resource is equal to the resource quantity of the first resource.

[0017] Preferably, the first network slice group is provided with a first resource release retention threshold, and the remaining priority resources after the first network slice group releases the fourth and fifth resources are greater than the first resource release retention threshold. By setting the resource release retention threshold, the minimum priority resources in the network slice group can be guaranteed, preventing the priority resources in the network slice group from being too few.

[0018] Preferably, before the first network slice group releases the third resource to the shared resource, the method further includes: determining that the time during which the utilization rate of the second priority resource in the first network slice group is lower than a resource idle threshold is greater than or equal to the evaluation period. By setting an evaluation period, it is possible to prevent the network slice group from frequently requesting and releasing resources, which could cause instability in system operation.

[0019] Another aspect of the present invention includes a resource dynamic adjustment device, characterized in that the adjustment device is applied to adjust first wireless network resources, the first wireless network resources including shared resources and first priority resources allocated to a first network slice group, the adjustment device including a resource request unit and an adjustment unit; wherein, when a first user equipment accesses the first network slice group, if the utilization rate of a first set priority resource of the first network slice group exceeds a resource overload threshold, the resource request unit requests the first resource from the shared resources as a second priority resource of the first network slice group; the adjustment unit is used to adjust the priority resources of the first network slice group according to the resource request request of the resource request unit.

[0020] The network slice group resource dynamic adjustment device of the present invention has the following advantages: (1) It can adjust the priority resources in real time according to the priority resource utilization of each network slice group, thereby improving the utilization rate of the total resources of the cell; when the priority resource utilization rate of a certain network slice group is too high, the priority resources of the network slice group are increased; (2) It can increase the number of configured network slice groups, because the network slice group priority resource dynamic adjustment device can dynamically adjust its priority resources according to the actual usage of each network slice group, and the configuration of the network slice group will no longer completely depend on the initial priority resource configuration.

[0021] Preferably, the adjustment device includes a resource release unit; wherein, the resource release unit is used to request the release of a third resource from the shared resource when the utilization rate of the second priority resource of the first network slice group is lower than the resource idle threshold; the adjustment unit is used to adjust the priority resource of the first network slice group according to the resource release request of the resource release unit.

[0022] Preferably, the adjustment unit is further configured to set a first resource release retention threshold for the first network slice group, wherein the amount of priority resources remaining after the first network slice group releases the third resource is greater than the first resource release retention threshold.

[0023] Preferably, in the network slice group resource dynamic adjustment device according to claim 12, the adjustment unit is further configured to set the evaluation period of the network slice group, and before the resource release unit requests the release of the third resource from the shared resource, the time during which the utilization rate of the second set priority resource of the first network slice group is lower than the resource idle threshold is longer than the evaluation period of the network slice group.

[0024] In another aspect, the present invention provides an electronic device, characterized in that it includes: a memory and a processor; the memory is used to store program code used during the operation of the electronic device; the processor is used to execute the program code to implement the resource dynamic adjustment method as described above.

[0025] In another aspect, the present invention provides a storage medium, characterized in that, when the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is able to perform the resource dynamic adjustment method as described above. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of the overall architecture of the network slice group.

[0027] Figure 2 This is a schematic diagram of resource allocation for network slice groups in a traditional wireless network cell.

[0028] Figure 3 This is a data example diagram illustrating resource allocation using traditional network slice groups.

[0029] Figure 4 This is a diagram illustrating the traditional allocation of network slice group resources.

[0030] Figure 5 The flowchart illustrates the method for dynamically adjusting priority resources in network slice groups provided by this invention.

[0031] Figure 6 This is a flowchart of how a network slice group requests priority resources from a shared resource in this invention.

[0032] Figure 7 This is a flowchart illustrating how network slice groups release priority resources to shared resources in this invention.

[0033] Figure 8 This is a schematic diagram illustrating how a network slice group requests and releases priority resources from shared resources in this invention.

[0034] Figure 9 This is a schematic diagram of the method for dynamically adjusting priority resources of network slice groups in this invention.

[0035] Figure 10 This is a schematic diagram of the network slice group priority resource dynamic adjustment device in this invention. Detailed Implementation

[0036] Please refer to Figure 1 As shown, Figure 1This is a schematic diagram of the overall architecture of a network slice group. Each network slice is composed of core network subslices, radio network subslices, and transport network subslices, and is managed uniformly through an end-to-end network slice management system. The core network supports key technologies such as network slice construction, intelligent selection of network slices, opening of network slice capabilities, and isolation of network slices. In the core network, typical network slicing deployments include the Network Slice Selection Function (NSSF) and the Network Repository Function (NRF), which serve as public services in the 5G core network and are deployed on a per-PLMN basis. Network functions such as the Access and Mobility Management Function (AMF), Policy Control Function (PCF), and Unified Data Management (UDM) can be shared to provide services to multiple network slices. Functions like the Session Management Function (SMF) and User Plane Function (UPF) can provide individual network functions for each network slice based on its different requirements for latency, bandwidth, and security. Wireless network sub-slicing requires flexible customization based on the different Service Level Agreements (SLAs) for different services issued by the end-to-end network slice orchestration management system. This invention primarily focuses on the allocation of wireless network resources; the resources described below refer to wireless network resources, which are mainly time-frequency resources.

[0037] Please refer to Figure 2 As shown, Figure 2 This is a schematic diagram illustrating the allocation of network slice group resources in a traditional cell. Cell resources are divided into non-network slice group resources and network slice group resources. Figure 2The resource allocation diagram for a cell network slice group includes three network slice groups: Network Slice Group 1, Network Slice Group 2, and Network Slice Group 3. Each network slice group is allocated dedicated resources, priority resources, and maximum resources. Dedicated resources are allocated only for users within that network slice group. Priority resources prioritize the services of users within the network slice group, such as Guaranteed Bit Rate (GBR) and Non-Guaranteed Bit Rate (Non-GBR) services. When priority resources are available, users outside the network slice group can also use them. Shared resources are used fairly by all users based on QoS. When allocating Non-GBR resources based on scheduling levels, the resource usage of dedicated and priority resources by users in the slice user group is not considered. The remaining resources in the cell's network slice group, excluding the dedicated and priority resources of each network slice group, are collectively referred to as shared resources. When allocating shared resources, maximum resources can also be set for certain network slice groups. Maximum resources represent the maximum resource limit that users in a network slice group can use. Maximum resources include dedicated resources, priority resources, and resources requested from shared resources. For example... Figure 1 As shown, maximum resources are set for network slice group 1, network slice group 2, and network slice group 3, respectively. Apart from the resources already used by network slice group 1, network slice group 2, and network slice group 3, the remaining resources can be allocated to users outside the network slice group.

[0038] Existing network slice groups typically allocate resources with fixed configurations for dedicated resources, priority resources, and maximum resources. Please refer to [reference needed]. Figure 3 As shown, Figure 3 This is a data example diagram illustrating resource allocation using traditional network slice groups. Figure 3In this scenario, the total resources of a cell are assumed to be 1000M, with 100M allocated to non-network slice group resources and the remaining resources to network slice group resources, allocated to six network slice groups. Initially, each network slice group is configured with fixed dedicated resources, priority resources, and maximum resources. Specifically, network slice group 1 is allocated 50M of dedicated resources, 50M of priority resources, and a maximum resource of 150M; network slice group 2 is allocated 50M of dedicated resources, 0M of priority resources, and has no maximum resource limit (i.e., the maximum resource of network slice group 2 is capped at the maximum resource it can obtain from shared resources); network slice group 3 is allocated 50M of dedicated resources, 50M of priority resources, and has no maximum resource limit; network slice group 4 is allocated 50M of dedicated resources, 0M of priority resources, and a maximum resource of 120M; network slice group 5 is allocated 50M of dedicated resources, 0M of priority resources, and has no maximum resource limit; and network slice group 6 is allocated 50M of dedicated resources, 430M of priority resources, and has no maximum resource limit. User Equipment (UE) UE1 in network slice group 1 requires 120M of resources. After allocation, both dedicated and priority resources are exhausted, leaving 0M remaining. It also requests 20M of resources from shared resources, leaving a maximum resource of 30M. Next, UE2 in network slice group 1 requires 60M of resources. Because there are no dedicated or priority resources left in network slice group 1, and the shared resources are insufficient to allocate to UE2, and its remaining maximum resource is less than the requested resource, UE2's request is rejected. Meanwhile, in network slice group 6, its allocated priority resources of 430M remain unused, indicating significant resource idleness and waste.

[0039] Please refer to Figure 4 As shown, Figure 4 This is a diagram illustrating the traditional allocation of network slice group resources. Figure 4 The allocation of resources is represented by the percentage of total community resources allocated to that resource. From... Figure 4 As can be seen, the dedicated and priority resources in network slice groups A, B, and C are all statically configured. If the dedicated and priority resources allocated to a network slice group are exhausted, resources can only be requested from shared resources, and the requested resources cannot exceed the maximum resource limit. Priority resources in each network slice group will not be allocated to other network slice groups, and the allocation of priority resources will not be adjusted based on service access volume.

[0040] Therefore, this method of statically configuring dedicated resources, priority resources, and maximum resources has the following disadvantages: (1) Although some network slice groups are configured with priority resources, no users or services utilize these reserved resources, resulting in idle and wasted resources; in other network slice groups, because the configured resources are too few, while the number of users and services accessing the network is relatively large, the users and services that expect to access the network are rejected after the reserved resources are used up; the resource allocation of the entire network slice group is not based on the actual needs of service access, but is statically allocated, resulting in the insufficient utilization of the resources of the entire cell. (2) Because each network slice group is allocated fixed dedicated resources and priority resources, the number of supported network slice groups is limited.

[0041] To address the aforementioned problems, this invention provides a method for dynamically adjusting priority resources of network slice groups. Before describing this method, the relevant parameters used in the method will be explained.

[0042] Initial Priority Resource Ratio (InitPreceResource): The percentage of the cell's total resources allocated to the initial priority resource configuration.

[0043] Resource Overload Threshold: When the utilization rate of priority resources within a network slice group exceeds the resource overload threshold, additional priority resources for that network slice group must be requested from shared resources.

[0044] Resource Apply Rate: The proportion of resource applications in a network slice group, representing the ratio of priority resources to initial priority resources that are ready to be applied for.

[0045] Resource ApplyReduceIndex: A parameter that indicates the priority of resource applications decreases with each subsequent request, starting from the second request.

[0046] Resource request count: Records the number of times each network slice group requests priority resources from the shared resource. When the network slice group requests priority resources, the resource request count is incremented by 1; when the network slice group releases priority resources, the resource request count is decremented by 1.

[0047] Maximum number of resource requests (ResourceApplyNumber): Specifies the maximum number of times each network slice group can request priority resources.

[0048] Resource idle threshold: When the utilization rate of priority resources within a network slice group falls below the resource idle threshold, the priority resources allocated to that network slice group should be released to shared resources.

[0049] Resource Retain Threshold (ResourceRetainThr): When the utilization rate of priority resources in a network slice group is lower than the resource idle threshold, the proportion of priority resources that need to be retained when priority resources are released is the proportion of the initial priority resources.

[0050] Evaluation Period: When the utilization rate of priority resources within a network slice group falls below the resource idle threshold for more than the evaluation period, the priority resources allocated to that network slice group should be released to shared resources.

[0051] Please refer to Figure 5 As shown, Figure 5 This is a flowchart of a method for dynamically adjusting priority resources in a network slice group, provided by the present invention. The method includes: S1: Configuring an initial priority resource ratio for each network slice group; this can be set according to the performance characteristics of each network slice group. For network slice groups with high traffic, the initial priority resource ratio is set larger; for network slice groups with low traffic, the initial priority resource ratio is set smaller. S2: Determining whether the UE device is joining or leaving a network slice group; if the UE device joins, proceed to S3; if the UE device leaves, proceed to S5. S3: Determining whether the priority resource utilization rate in the network slice group joined by the UE device exceeds a resource overload threshold; if it exceeds the threshold, proceed to S4; if it does not exceed the threshold, proceed to S2. S4: The network slice group requests priority resources from shared resources; after the request is completed, proceed to S2. S5: Determining whether the priority resource utilization rate in the network slice group after the UE leaves is lower than a resource idle threshold; if it is lower, proceed to S6; if it is not lower than the threshold, proceed to S2. S6: The network slice group releases resources to the shared resource. After the release is complete, S2 is executed.

[0052] The network slice group priority resource dynamic adjustment method provided in this invention has the following advantages: (1) Priority resources can be adjusted in real time according to the priority resource utilization in each network slice group to improve the utilization rate of the total resources of the cell; when the priority resource utilization rate is too high, priority resources are requested from the shared resources; when the priority resource utilization rate is too low, priority resources are released to the shared resources; (2) The number of network slice groups can be increased because the priority resources of each network slice group are dynamically adjusted according to the actual usage. Priority resources of each network slice group can be dynamically allocated or released according to the actual situation. The configuration of network slice groups will no longer completely depend on the initial priority resource configuration; (3) By setting a resource overload threshold, the future priority resource usage can be predicted according to the past priority resource usage in the network slice group, and priority resources can be requested in advance to improve network operation efficiency.

[0053] Please refer to Figure 6 As shown, Figure 6 This is a flowchart illustrating how a network slice group requests priority resources from a shared resource in this invention. In step S4, when a network slice group requests priority resources from a shared resource, the process includes: S4-1: querying the number of times the network slice group requests priority resources from the shared resource; S4-2: requesting priority resources from the shared resource based on the resource request ratio corresponding to the number of resource requests. The resource request count value records the number of times the network slice group has obtained priority resources from the shared resource. When a network slice group requests priority resources from the shared resource, the resource request count value is incremented by 1. If the network slice group cannot obtain the requested priority resources from the shared resource, the incremented request count is decremented accordingly. When the network slice group releases priority resources from the shared resource, the request count value is decremented by 1. The resource request ratio corresponding to the number of resource requests decreases as the number of resource requests increases; that is, the larger the resource request count value, the less resources are requested. By setting a gradually decreasing resource request amount, it is possible to prevent a single network slice group from obtaining too many resources in a short period, causing resource shortages when other network slice groups request resources.

[0054] The resource application ratio corresponding to the number of resource applications can be set in advance, creating a table that maps resource application frequency to resource application ratio. For example, the first application might request 80% of the resources; the second application, 70%; the third application, 55%, and so on. The percentage in the requested resource amount represents the proportion of priority resources requested relative to the initial priority resources.

[0055] The resource request ratio corresponding to the number of resource requests can be calculated. For example, a ratio coefficient can be set so that the resource request quantity gradually decreases as the number of resource requests increases; for example, if the number of resource requests is k, the corresponding resource request ratio is a. k The value range of a is (0, 1), and the preferred value range is [0.6, 0.8].

[0056] The resource application ratio corresponding to the number of resource applications can also be calculated using other methods, such as the ResourceApplyRate. k =ResourceApplyRate k-1 *(1-α)+α*X*ResourceApplyRate k-1Where k represents the number of resource requests, α is the resource request decrement index, and the value range of α is (0, 1); X is the selection coefficient. If k = 1, then X = 1. If k ≠ 1, then X = 0; ResourceApplyRate0 is set by the user according to specific needs, such as ResourceApplyRate0 = 70%, and the value range of ResourceApplyRate0 is (0, 1]. Preferably, the value range of ResourceApplyRate0 is [0.6, 0.8].

[0057] In the above embodiments, we determine the resource request ratio for each request by setting a resource request ratio corresponding to the number of resource requests. This invention does not limit the method by which network slice groups request priority resources from shared resources. When a network slice group requests priority resources, it can determine the amount of priority resources requested this time by using the resource request ratio corresponding to the number of requests; it can also determine the amount of priority resources requested this time based on business demand; or it can negotiate with shared resources to determine the amount of priority resources requested this time.

[0058] Below, we illustrate the process of a network slice group requesting priority resources from shared resources using an example. Taking network slice group A as an example, assume that the ResourceApplyRate0 of network slice group A is 70%, the resource request reduction coefficient α is 20%, and the initial priority resource of network slice group A is the first priority resource. First, it is determined that the utilization rate of the priority resources of network slice group A exceeds the first resource overload threshold of network slice group A. When the priority resources in network slice group A only include the initial priority resource, the first set priority resource is the initial priority resource; the first resource overload threshold is a certain value, such as a certain value between 60% and 90%. At this time, network slice group A will request resources from shared resources. In the first request, ResourceApplyRate1 = ResourceApplyRate0 * (1 - 20%) + 20% * 1 * ResourceApplyRate0 = 70%, that is, network slice group A requests the first resource from shared resources. The resource amount of the first resource is 70% of the first priority resource, and the requested first resource is used as the second priority resource of network slice group A. Network slice group A continues to operate. When the first UE device connects and the priority resource utilization rate of network slice group A exceeds the second resource overload threshold of the first set priority resource of network slice group A again, network slice group A will request priority resources from the shared resources again. When the priority resources include both the initial priority resources and priority resources requested from the shared resources, the first set priority resource can be the sum of all priority resources in network slice group A, that is, the sum of the first priority resource and the second priority resource; the first set priority resource can also be the priority resource requested from the shared resources, that is, the second priority resource; the first set priority resource can also be the priority resource last requested from the shared resources, which in this embodiment is also the second priority resource. The second resource overload threshold can be set separately, or it can have the same value as the first resource overload threshold, that is, the value of the second resource overload threshold can be the same as or different from the value of the first resource overload threshold. This application does not restrict the first resource overload threshold and the second resource overload threshold. When the first priority resource is a priority resource applied for from shared resources, or a priority resource obtained from the last application from shared resources, the priority resource should be used first when it is allocated. In the second application, ResourceApplyRate2 = ResourceApplyRate1 * (1 - 20%) + 20% * 0 = 56%. Network slice group A applies for a second resource from shared resources. The amount of this second resource is 56% of the first priority resource. This applied second resource becomes the third priority resource for network slice group A.Network slice group A continues to operate, a second UE device accesses the network, and the utilization rate of the first set priority resource of network slice group A exceeds the third resource overload threshold corresponding to network slice group A. Similar to before, this is because the priority resources in network slice group A now include both the initial priority resources and priority resources requested from shared resources. Therefore, the first set priority resource can be the sum of all priority resources in network slice group A, i.e., the sum of the first priority resource, the second priority resource, and the third priority resource; the first set priority resource can also be the priority resource requested from shared resources, i.e., the sum of the second priority resource and the third priority resource; the first set priority resource can also be the priority resource last requested from shared resources, which in this embodiment is the third priority resource. The value of the third resource overload threshold can be the same as the value of the first resource overload threshold, or the value of the third resource overload threshold can be the same as the value of the second resource overload threshold, or the value of the third resource overload threshold can be the same as or different from both the values ​​of the first and second resource overload thresholds; this application does not impose any limitations on this. Because the utilization rate of the first priority resource of network slice group A exceeds the overload threshold of the third resource corresponding to network slice group A, network slice group A will request resources from the shared resource again. On the third request, ResourceApplyRate3 = ResourceApplyRate2 * (1 - 20%) + 20% * 0 = 44.8%. Network slice group A requests the third resource from the shared resource, and the amount of this third resource is 44.8% of the first priority resource. The requested third resource becomes the fourth priority resource of network slice group A. Similarly, if network slice group A only requests priority resources from the shared resource three times, then the total priority resources allocated to network slice group A are: 1 + 70% + 56% + 44.8% = 270.8%, that is, the priority resources allocated to network slice group A are 270.8% of the initial priority resources. In this embodiment, the amount of the second priority resource is greater than the amount of the third priority resource, and the amount of the third priority resource is greater than the amount of the fourth priority resource.

[0059] As can be seen from the above embodiments, the network slice group priority resource dynamic adjustment scheme provided in this invention does not limit the priority resources of each network slice group to the initially allocated priority resources. Instead, it dynamically adjusts the priority resources according to the access UE devices. When the priority resource utilization rate in the network slice group is high, it will apply for priority resources from the shared resources to expand the priority resources of the network slice group and improve the resource utilization of the entire cell.

[0060] To better balance the allocation of priority resources among each network slice group, we can set a maximum value for the number of resource requests. By limiting the maximum number of resource requests, we can control the maximum amount of priority resources that a single network slice group can request, preventing a single network slice group from obtaining too many priority resources. Following S4-1, there is also S4-1-1: determining whether the number of resource requests exceeds the maximum number of resource requests. If it does not exceed the maximum number of resource requests, then execute S4-2. For example, in the above embodiment, we can set the maximum number of resource requests to 3. When the priority resource utilization rate of network slice group A still exceeds the resource overload threshold, it will no longer request resources from the shared resource. Alternatively, the shared resource can decide whether to allocate resources to network slice group A. When the shared resource determines that the number of resource requests by network slice group A has exceeded the set maximum value of 3, it will no longer allocate resources to network slice group A. By setting a maximum number of resource requests, we can limit the maximum priority resources that network slice group A can obtain to 270.8% of the initial priority resources, preventing network slice group A from obtaining too many priority resources.

[0061] In the above embodiments, by setting the number of resource requests, a maximum priority resource limit for a certain network slice group is set, thereby limiting a single network slice group from obtaining excessive resources. The maximum number of resource requests for different network slice groups can be the same or different, and this application does not impose any limitation. By setting the number of resource requests, such as setting the maximum number of resource requests for the first network slice group to 3, the first priority resource limit for the first network slice group can be determined. The first priority resource limit indicates that the amount of priority resources in the first network slice group must be less than or equal to the first priority resource limit. Of course, we can also directly define a certain resource quantity value as the maximum priority resource limit for a certain network slice group, such as defining the first priority resource limit for the first network slice group and the second priority resource limit for the second network slice group. The first priority resource limit and the second priority resource limit can be the same or different. When the priority resources in the first network slice group exceed the first priority resource limit, even if the utilization rate of the set priority resources in the first network slice group has exceeded the resource overload threshold, the first network slice group will no longer request resources from the shared resources; or when the priority resources in the first network slice group exceed the first priority resource limit, the first network slice group will still request resources from the shared resources, but the shared resources will no longer allocate resources to the first network slice group.

[0062] Please refer to Figure 7 As shown, Figure 7This is a flowchart illustrating the process of a network slice group releasing priority resources to shared resources in this invention. In step S6, when a network slice group releases priority resources to shared resources, the process includes: S6-1: querying the number of resource requests made by the network slice group when releasing priority resources to shared resources; S6-2: releasing priority resources to shared resources according to the resource request ratio corresponding to the number of resource requests. The resource request ratio corresponding to the number of resource requests decreases as the number of resource requests increases; that is, the more resource releases, the more resources are released each time. Specifically, resource release is performed in reverse order of request, with later-requested resources released first, ensuring that idle resources are gradually released after the UE device exits.

[0063] Please refer to Figure 8 As shown, Figure 8 This is a schematic diagram illustrating how network slice groups request and release priority resources from shared resources in this invention. Figure 8 In this example, an initial priority resource and priority resources requested in installments from the shared resource are distinguished. The first request requests 70% of the resources; the second request requests 56%; and the third request requests 44.8%. This example illustrates the release process when priority resources are available.

[0064] First, it is determined that the utilization rate of the priority resources in network slice group A is lower than the second set priority resource idle threshold of network slice group A. Similar to the first set priority resource, the second set priority resource can also be one of the following: when network slice group A only includes the initial priority resource, the second set priority resource is the initial priority resource; when network slice group A includes both the initial priority resource and priority resources requested from shared resources, the second set priority resource can be the sum of all priority resources in network slice group A; the second set priority resource can also be a priority resource requested from shared resources; the second set priority resource can also be the priority resource last requested from shared resources. Different resource idle thresholds can be selected for different second set priority resources. For example, when the second priority resource is a priority resource obtained from the last request among shared resources, the resource availability threshold can be relatively low, such as 10%-20%; when the second priority resource is a priority resource requested from shared resources, the resource availability threshold can be slightly higher, such as 40%-50%; when the second priority resource is the sum of all priority resources in network slice group A, the resource availability threshold can be even higher, such as 70%-80%. The type of the second priority resource can be the same as the type of the first priority resource, or the type of the second priority resource can be different from the type of the first priority resource.

[0065] Below, we take the second priority resource setting as the sum of all priority resources in network slice group A as an example, assuming that the resource idle threshold of network slice group A is 80%. When it is determined that the priority resource utilization rate of network slice group A is lower than the second set priority resource idle threshold of network slice group A, that is, the second set priority resource utilization is less than 216.64% of all priority resources in network slice group A (based on the fact that the sum of all priority resources at this time is the sum of the first priority resource, the second priority resource, the third priority resource, and the fourth priority resource, which is 270.8% of the first priority resource, the first release threshold value is 270.8% * 80% = 216.64%), then network slice group A will release priority resources to shared resources. At this time, the resource request count k=3 of network slice group A is queried, and the resource request ratio corresponding to k=3 is found to be 44.8% of the initial priority resources. It is checked whether the remaining priority resources after release are greater than the current priority resource utilization. If the remaining priority resources after release are less than the current priority resource utilization, no release is performed this time; if the remaining priority resources after release are greater than the current priority resource utilization, the resource amount of the fourth priority resource allocated for the third time is released. When releasing priority resources, if the principle of "first-come, first-served" applies during resource usage, the released priority resource becomes the fourth priority resource. If no priority resource usage is configured during resource usage, the released priority resource has the same resource quantity as the fourth priority resource. After release, the total priority resource quantity of network slice group A is 270.8% - 44.8% = 226%. Network slice group A continues to operate, and the third UE device exits. This third UE device can be the first UE device, the second UE device, or any other UE device that is neither the first nor the second UE device; this application does not impose any limitations on this. When the third UE device exits and the priority resource utilization rate of network slice group A falls below the second set priority resource idle threshold of 80% again (i.e., the priority resource utilization is less than 180.8% of the first priority resource utilization), network slice group A will release priority resources to the shared resources. Since it has already been released once, the resource request count k becomes 2, and the resource request ratio corresponding to k=2 is found to be 56% of the initial priority resource utilization. It is then checked whether the remaining priority resources after release are greater than the current priority resource utilization. If the remaining priority resources after release are less than the current priority resource utilization, no release will be performed this time; if the remaining priority resources after release are greater than the current priority resource utilization, the second allocated third priority resource utilization will be released.When releasing priority resources, if the principle of "first-come, first-served" applies during resource usage, the released priority resource will be the third priority resource. If no priority resource usage is specified during resource usage, the released priority resource will have the same amount as the third priority resource. After release, the total priority resource amount for network slice group A is 226% - 56% = 170%. Network slice group A continues to operate. When the fourth UE device exits, and the priority resource utilization rate of network slice group A falls below 80% of the second priority resource idle threshold (i.e., the resource utilization is less than 136% of the initial priority resources) again, network slice group A will release priority resources to shared resources. Since the total priority resources of network slice group A at this time are the sum of the first and second priority resources (i.e., 170% of the first priority resources), the third release threshold is 170% * 80% = 136%. At this point, network slice group A will release priority resources to shared resources. Because two releases have already occurred, the resource request count k becomes 1, and the resource request ratio corresponding to k = 1 is found to be 70% of the initial priority resources. It checks whether the remaining priority resources after release are greater than the current priority resource utilization. If the remaining priority resources after release are less than the current priority resource utilization, no release is performed this time; if the remaining priority resources after release are greater than the current priority resource utilization, the first 70% of the allocated resources are released. After the release, the total priority resources of network slice group A are 170% - 70% = 100%. When releasing priority resources, if the principle of "first-allocated priority resources first-used" applies during resource usage, then the released priority resource becomes the second priority resource. If no priority resource usage is specified during resource usage, then the released priority resource has the same quantity as the third priority resource. Based on the above, it can be seen that when releasing shared resources, if the principle of "first-allocated priority resources first-used" applies, then the released resources correspond one-to-one with the previously allocated resources. Of course, if the principle of "first-allocated priority resources first-used" does not apply, then the released resources only correspond one-to-one with the previously allocated resources in terms of quantity. This invention does not limit the method of using and releasing resources. In the above embodiments, each time it is determined whether the utilization rate of the priority resource of network slice group A is lower than the resource idle threshold of the second priority resource set by network slice group A, the value of the resource idle threshold is always 80%. These are the same. Of course, different values ​​of the resource idle threshold can also be determined according to the amount of priority resource. For example, when the amount of priority resource is large, the value of the resource idle threshold can be set to a larger value, such as a value within the range of 60%-90%. When the amount of priority resource is small, the value of the resource idle threshold can be set to a smaller value, such as a value within the range of 40%-60%. Priority resources will only be released when the utilization rate is lower than this value.

[0066] As can be seen from the above examples, through three release processes, all previously requested priority resources will be released, and the released priority resources will become the initial priority resources. Furthermore, the amount of priority resources released in each of the three releases increases progressively. If a network slice releases resources consecutively, we can predict that its resource demand is decreasing, and more resources can be released in the next release. Subsequently, based on the user access and resource usage in network slice group A, we can continue to allocate and release resources for network slice group A.

[0067] In the above embodiments, the need to release priority resources is determined by checking whether the utilization rate of the second set priority resource is lower than the resource idle threshold. In other embodiments, idle priority resources in network slice group A can also be monitored to determine whether priority resources need to be released. Taking network slice group A, which has made three priority resource requests, as an example, the release process when there are idle priority resources in network slice group A is explained. In the first request, the resource request ratio is 70%; in the second request, the resource request ratio is 56%; and in the third request, the resource request ratio is 44.8%. When the third UE device exits network slice group A, it is determined whether the idle resources of priority resources in network slice group A are greater than the priority resource request ratio of 44.8% in the third request. If it is greater than the priority resource request ratio of 44.8% in the third request, the amount of the fourth priority resource is released. Similar to before, if the priority resources are used first according to the principle of first-allocated priority resources, then the priority resources released this time are the fourth priority resources; if the use of priority resources is not set during resource use, then the amount of priority resources released this time is the same as the fourth priority resources. Network slice group A continues to operate. When the fourth UE device leaves network slice group A, it is determined whether the idle resources of the priority resources in network slice group A are greater than the priority resource request ratio of 56% during the second request. If it is greater than the priority resource request ratio of 56% during the second request, the resources of the third priority resources are released. Network slice group A continues to operate. When the fifth UE device leaves network slice group A, it is determined whether the idle resources of the priority resources in network slice group A are greater than the priority resource request ratio of 70% during the first request. If it is greater than the priority resource request ratio of 70% during the first request, the resources of the second priority resources are released.

[0068] In the two embodiments above, the amount of resources released corresponds one-to-one with the amount of resources requested. In some embodiments, the amount of resources released may not correspond to the amount of resources requested. For example, if the amount of resources released each time is the difference between the total amount of priority resources and the resource release threshold, then the release can be performed directly without needing to determine whether the released resources are currently in use. Alternatively, the amount of resources released each time can be the total amount of priority resources requested from the shared resources divided by the number of times priority resources were requested from the shared resources. In this embodiment, the total amount of priority resources requested from the shared resources is the sum of the second, third, and fourth priority resources, and the number of requests is three. That is, the amount of priority resources released each time is one-third of the sum of the second, third, and fourth priority resources, and the amount of resources released each time is the same. Resources requested from the shared resources can be released through multiple releases.

[0069] In the embodiment of network slice group A above, network slice group A first requests priority resources from the shared resource, and then releases the priority resources to the shared resource. The following uses another network slice group, B, as an example to illustrate the process of network slice groups releasing priority resources first.

[0070] When a UE device accesses network slice group B, the utilization rate of priority resources never reaches the initial priority resource overload threshold. When a UE device exits network slice group B, or when the priority resource utilization rate is queried according to a set time period and is lower than the resource idle threshold, the initial priority resources of network slice group B are queried. If network slice group B is allocated fewer initial priority resources, no priority resources are released. If network slice group B is allocated more initial priority resources, it releases priority resources to shared resources. When network slice group B needs to release priority resources to shared resources, it releases them only once. The release ratio can be preset, set to a fixed specific value, such as a release ratio of 30%. Alternatively, a resource release retention threshold can be set, such as a 20% threshold, meaning that more than 20% of the resources must be retained after release. By setting a resource release retention threshold, a minimum number of priority resources in the network slice group can be guaranteed, preventing the priority resources in the network slice group from becoming too few. If a resource release reservation threshold is set, the proportion of resources released can be the difference between the resource overload threshold and the resource release reservation threshold. Assuming that the resource overload threshold of network slice group B is also 70%, the release proportion is 50%. If, during subsequent working hours, network slice group B needs to request priority resources from shared resources, the proportion of resources requested initially will be the same as the proportion of resources previously released.

[0071] After all the priority resources requested from the shared resources are released by network slice group A, if more UE devices continue to exit and priority resources need to be released to the shared resources, the release method is the same as that of network slice group B.

[0072] To improve system stability, some embodiments include an evaluation period. The evaluation period indicates that the time during which a network slice group releases priority resources from shared resources must be greater than or equal to the evaluation period before the priority resource utilization rate is lower than the resource idle threshold. Following step S6-1, step S6-1-1 is added: determining whether the time during which the network slice group's priority resource utilization rate is lower than the resource idle threshold is greater than or equal to the evaluation period. If it is, step S6-2 is executed; otherwise, the priority resource is not released. Adding an evaluation period prevents network slice groups from frequently requesting and releasing resources, which could lead to system instability.

[0073] Please refer to Figure 9 As shown, Figure 9 This is a schematic diagram of the method for dynamically adjusting priority resources in network slice groups according to the present invention. Figure 9 As can be seen, the resources in the wireless network include dedicated resources and priority resources for each network slice group, as well as shared resources. The dedicated resources in each network slice group are fixed and allocated according to the needs of each network slice group; these dedicated resources are allocated in a fixed manner. The priority resources in each network slice group are configured with initial priority resources, but these priority resources can be dynamically adjusted based on the accessed UE devices and resource usage. When the priority resource utilization rate is high, priority resources can be requested from shared resources; when the priority resource utilization rate is low, priority resources can be released from shared resources.

[0074] Therefore, the network slice group priority resource dynamic adjustment method in this invention has the following advantages: (1) Priority resources can be adjusted in real time according to the priority resource utilization of each network slice group, thereby improving the utilization rate of the total resources of the cell; when the priority resource utilization rate is too high, priority resources are applied for from the shared resources; when the priority resource utilization rate is too low, priority resources are released from the shared resources; (2) The number of configured network slice groups can be increased, because the priority resources of each network slice group are dynamically adjusted according to the actual usage. Priority resources of each network slice group can be dynamically allocated or released according to the actual situation, and the configuration of network slice groups will no longer completely depend on the initial priority resource configuration; (3) By setting the rules for network slice groups to apply for dynamic resources and release priority resources, priority resources can be applied for in descending order and released in ascending order, which can make the order of network slice groups applying for and releasing priority resources more in line with the actual application rules.

[0075] In another aspect, the present invention provides a device for dynamically adjusting priority resources of network slice groups, please refer to... Figure 10 As shown. Figure 10 This is a schematic diagram of the network slice group priority resource dynamic adjustment device of the present invention. The network slice group priority resource dynamic adjustment device includes an allocation unit, a resource request unit, a resource release unit and an adjustment unit.

[0076] The allocation unit is used to configure the initial priority resource ratio value for each network slice group. It can be set according to the performance characteristics of each network slice group. For network slice groups with high traffic, the initial priority resource ratio value is set to be larger; for network slice groups with low traffic, the initial priority resource ratio value is set to be smaller.

[0077] The resource request unit is used when the UE device accesses the first network slice group and the utilization rate of the priority resources of the first network slice group exceeds the resource overload threshold, the resource request unit requests the first resource from the shared resources as the second priority resource of the first network slice group.

[0078] The resource release unit is used to request the release of the third resource from the sharing unit when the priority resource utilization rate of the first network slice group is lower than the resource idle threshold.

[0079] The adjustment unit is used to adjust the priority resources of the network slice group according to the resource request from the resource requesting unit or the release request from the resource releasing unit. Specifically, if the resource requesting unit requests resources from the shared resource, the adjustment unit increases the priority resources of the first network slice group according to the amount of resources requested; if the resource releasing unit requests to release resources from the shared unit, the adjustment unit decreases the priority resources of the first network slice group according to the amount of resources released.

[0080] The network slice group priority resource dynamic adjustment device provided in this invention has the following advantages: (1) It can adjust the priority resources in real time according to the priority resource utilization of each network slice group, thereby improving the utilization rate of the total resources of the cell; when the priority resource utilization rate of a certain network slice group is too high, the priority resources of the network slice group are increased; when the priority resource utilization rate of a certain network slice group is too low, the priority resources of the network slice group are decreased; (2) It can increase the number of configured network slice groups, because the network slice group priority resource dynamic adjustment device can dynamically adjust the priority resources of each network slice group according to the actual usage of each network slice group, and the configuration of the network slice group will no longer completely depend on the initial priority resource configuration.

[0081] When a resource requesting unit requests resources from a shared resource, the requested resource amount is the proportion corresponding to the number of resource requests made by that network slice group. The higher the resource request count, the lower the proportion. When a resource release unit requests resources from a shared resource, the released resource amount is the proportion corresponding to the number of resource requests made by that network slice group. The resource request count is used to record the number of times a network slice group requests priority resources from a shared resource. When a network slice group requests priority resources, the resource request count is incremented by 1. If the network slice group cannot obtain the requested priority resources from the shared resource, the incremented count is decremented accordingly. When a network slice group releases priority resources from a shared resource, the count is decremented by 1. The resource requesting and release units adjust according to the amount of resources the network slice group needs to adjust each time, i.e., requesting resources in descending order and releasing resources in ascending order, which makes the order of resource requesting and releasing by the network slice group more consistent with the actual network conditions.

[0082] The adjustment unit can also be used to set the maximum number of resource requests for each network slice group and determine whether the number of resource requests exceeds the maximum number of resource requests. When the number of resource requests for a network slice group exceeds the maximum number of resource requests, the priority resources of that network slice group will no longer be increased. By setting the maximum number of resource requests, the maximum priority resources that a network slice group can obtain can be limited, preventing a single network slice group from obtaining too many priority resources and affecting the resource usage of other network slice groups.

[0083] Of course, the resource request unit can also set a maximum number of resource requests for each network slice group and determine whether the number of resource requests exceeds the maximum number of resource requests. When the number of resource requests for a certain network slice group exceeds the maximum number of resource requests, it will no longer request resources from the shared resources.

[0084] The adjustment unit can also be used to set a resource release retention threshold for network slice groups. When the resource request and release unit requests the release of priority resources, it determines whether the remaining priority resources of the network slice group after resource release are greater than or equal to the resource release retention threshold. If the remaining priority resources of the network slice group after resource release are less than the resource release retention threshold, the priority resources of the network slice group will not be reduced further. By setting a resource release retention threshold, it is possible to prevent the amount of priority resources in a network slice group from being too small, thus affecting the capacity of the network slice group.

[0085] The adjustment unit can also be used to set the evaluation period for network slice groups. When the resource release unit requests the release of priority resources, it determines whether the time during which the priority resource utilization rate of the network slice group is lower than the resource idle threshold is greater than or equal to the evaluation period. If the time during which the priority resource utilization rate of the network slice group is lower than the resource idle threshold is less than the evaluation period, then the priority resources of the network slice group will not be reduced. By setting the evaluation period, the adjustment unit can prevent network slice groups from frequently requesting and releasing priority resources, thus preventing system instability.

[0086] This application also provides an electronic device, including: a memory and a processor:

[0087] The memory is used to store the program code used by the electronic device during operation;

[0088] The processor is used to execute the program code to implement the method for dynamically adjusting network slice group priority resources as described above.

[0089] This application also provides a storage medium that, when the instructions in the storage medium are executed by the processor of an electronic device, enables the electronic device to perform the method for dynamically adjusting network slice group priority resources as described above.

[0090] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] This application is described with reference to flowchart illustrations and / or block diagrams of methods, electronic devices (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing electronic device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing electronic device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0092] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing electronic device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0093] These computer program instructions can also be loaded onto a computer or other programmable data processing electronic device to cause a series of operational steps to be performed on the computer or other programmable electronic device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable electronic device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0094] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for dynamic resource adjustment, characterized in that, The resource dynamic adjustment method is applied to a first wireless network resource, which includes shared resources, at least one first dedicated resource allocated to at least one first network slice group, and at least one first priority resource allocated to the at least one first network slice group. The shared resources are the remaining resources in the first wireless network resource that can be shared by the at least one first network slice group, excluding the at least one first dedicated resource and the at least one first priority resource. The method includes: When a first user equipment accesses a first network slice group, if the utilization rate of a first set priority resource in the first network slice group exceeds a first resource overload threshold, the first network slice group requests a first resource from the shared resources as a second priority resource for the first network slice group; wherein, the first set priority resource is the first priority resource.

2. The resource dynamic adjustment method according to claim 1, characterized in that, The method further includes: when the second user equipment accesses the first network slice group, if the utilization rate of the first set priority resource of the first network slice group exceeds the second resource overload threshold, the first network slice group requests the second resource from the shared resources as the third priority resource of the first network slice group; wherein, the first set priority resource is the sum of the first priority resource and the second priority resource, or is the second priority resource.

3. The resource dynamic adjustment method according to claim 2, characterized in that, The amount of the second priority resource is greater than the amount of the third priority resource.

4. The resource dynamic adjustment method according to claim 2, characterized in that, The sum of the resources of the first priority resource, the second priority resource, and the third priority resource is less than the upper limit of the first priority resource, which is the maximum amount of priority resources that the first network slice group can obtain.

5. The resource dynamic adjustment method according to claim 1, characterized in that, The resource dynamic adjustment method also includes: When a third user equipment leaves the first network slice group, if the utilization rate of the second priority resource in the first network slice group is lower than the resource idle threshold, the first network slice group releases the third resource to the shared resources. The second priority resource is all priority resources in the first network slice group.

6. The resource dynamic adjustment method according to claim 5, characterized in that, The third resource is the first resource, or the resource quantity of the third resource is equal to the resource quantity of the first resource.

7. The resource dynamic adjustment method according to claim 2, characterized in that, The method further includes: when a fourth user equipment exits the first network slice group, if the utilization rate of the second set priority resource in the first network slice group is lower than the resource idle threshold, then the first network slice group releases the fourth resource to the shared resource; when a fifth user equipment exits the first network slice group, if the utilization rate of the second set priority resource in the first network slice group is lower than the resource idle threshold, then the first network slice group releases the fifth resource to the shared resource; wherein, the second set priority resource is all priority resources in the first network slice group; the fourth resource is the second resource, and the fifth resource is the first resource; or the resource quantity of the fourth resource is equal to the resource quantity of the second resource, and the resource quantity of the fifth resource is equal to the resource quantity of the first resource.

8. The resource dynamic adjustment method according to claim 7, characterized in that, The first network slice group is set with a first resource release retention threshold. After the first network slice group releases the fourth and fifth resources, the remaining priority resources are greater than the first resource release retention threshold.

9. The resource dynamic adjustment method according to claim 5, characterized in that, Before the first network slice group releases the third resource to the shared resource, it further includes: determining that the time during which the utilization rate of the second priority resource in the first network slice group is lower than the resource idle threshold is greater than or equal to the evaluation period.

10. A resource dynamic adjustment device, characterized in that, The adjustment device is used to adjust first wireless network resources, which include shared resources, at least one first dedicated resource allocated to at least one first network slice group, and at least one first priority resource allocated to the at least one first network slice group. The shared resources are the remaining resources in the first wireless network resources that can be shared by the at least one first network slice group, excluding the at least one first dedicated resource and the at least one first priority resource. The adjustment device includes a resource request unit and an adjustment unit. The resource request unit is used to request the first resource from the shared resources as the second priority resource of the first network slice group when the first user equipment accesses the first network slice group and the utilization rate of the first set priority resource of the first network slice group exceeds the first resource overload threshold. The adjustment unit is used to adjust the priority resources of the first network slice group according to the resource request of the resource request unit.

11. The resource dynamic adjustment device according to claim 10, characterized in that, The adjustment device includes a resource release unit; wherein... The resource release unit is used to request the release of a third resource from the shared resource when the utilization rate of the second priority resource of the first network slice group is lower than the resource idle threshold. The adjustment unit is used to adjust the priority resources of the first network slice group according to the resource release request of the resource release unit.

12. The resource dynamic adjustment device according to claim 11, characterized in that, The adjustment unit is further configured to set a first resource release retention threshold for the first network slice group, wherein the amount of priority resources remaining after the first network slice group releases the third resource is greater than the first resource release retention threshold.

13. The resource dynamic adjustment device according to claim 11, characterized in that, The adjustment unit is also used to set the evaluation period of the network slice group. Before the resource release unit requests the release of the third resource from the shared resource, the time when the utilization rate of the second priority resource of the first network slice group is lower than the resource idle threshold is longer than the evaluation period of the network slice group.

14. An electronic device, characterized in that, include: Memory and processor; The memory is used to store the program code used by the electronic device during operation; The processor is used to execute the program code to achieve the functionality described in claim 1. The resource dynamic adjustment method described in any one of the 9.

15. A storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the operation as claimed in claim 1. The resource dynamic adjustment method described in any one of the 9.

Images