Resource Allocation Method, Apparatus and Processor-Readable Storage Medium

By calculating the resource occupation and scheduling and allocation of resources of sliced ​​user groups and determining isolated resource parameters, the problem of inaccurate statistics and guaranteeing the resource ratio of sliced ​​user groups in the prior art is solved, and the balance and priority of resource allocation are achieved.

CN114521022BActive Publication Date: 2025-06-27DATANG MOBILE COMM EQUIP CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202011311583.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-11-20
Publication Date
2025-06-27
Estimated Expiration
2040-11-20

AI Technical Summary

Technical Problem

The prior art cannot accurately count the resource ratio that has been allocated for each slice user group, resulting in the inability to ensure that each slice user group needs to be at least the resource ratio that is guaranteed to be preferred for each slice user group.

Method used

By acquiring the number of PRBs of the media access control protocol data unit MAC PDU and the scheduling allocation physical resource blocks of each slice user group, calculate the uplink average actual PRB number and uplink average scheduling allocation resources of each slice user group, determine the isolation resource parameters, and perform resource allocation based on these parameters.

Benefits of technology

It ensures that at least the proportion of allocated resources needs to be guaranteed first, which solves the problem of uneven resource allocation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114521022B_ABST
    Figure CN114521022B_ABST
Patent Text Reader

Abstract

An embodiment of the present application provides a resource allocation method, apparatus, and processor-readable storage medium. The method includes: obtaining a Media Access Control Protocol Data Unit (MAC PDU) and the number of Physical Resource Blocks (PRBs) scheduled and allocated to each slice user group; determining the average actual occupied PRB number of each slice user group according to the MAC PDU; determining the average scheduled and allocated resources of each slice user group according to the scheduled and allocated PRB number; determining the isolation resource parameter of each slice user group according to the average actual occupied PRB number and / or the average scheduled and allocated resources; and performing resource allocation for each slice user group according to the isolation resource parameter. This method ensures that each slice user group has at least a resource ratio that needs to be preferentially guaranteed for allocation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of wireless communication technologies. Specifically, this application relates to a resource allocation method, apparatus, and processor-readable storage medium. Background Art

[0002] Due to the requirements of mobile communication differentiated services, the network slicing technology is proposed. After introducing the slicing concept into the network, resource isolation is implemented between slices. The reasons for resource isolation between slices mainly come from two aspects: on the one hand, to maintain the exclusivity of each slice's resources, ensure the normal communication of slice services within a certain capacity limit, and avoid one slice affecting other slices due to resource shortage; on the other hand, to maintain the security within the slice and avoid one slice affecting other slices when it is threatened by security.

[0003] When scheduling at the MAC (Media Access Control) layer, it is necessary to schedule based on the resource isolation parameters of the slice user group. A very important resource isolation parameter for scheduling is the minimum resource allocation ratio rRMPolicyMinRatio that each slice user group needs to prioritize to ensure when the data in the slice user group is sufficient. During uplink scheduling, the base station needs to send DCI (Downlink Control Information) for uplink scheduling, and carry scheduling authorization information in the DCI to indicate the uplink time-frequency domain and MCS (Modulation and Coding Scheme) that the UE (User Equipment) can use to send data. However, currently in the protocol, the relationship between the current authorization and the slice user group cannot be specified in the uplink scheduling authorization information. After receiving the authorization, which logical channel data the UE sends on the authorized resources depends on the implementation mechanism of the UE. When there are different LCGs (Logical Channel Groups) of the same UE belonging to different slice user groups in the network, it is impossible to accurately count the resource allocation ratio of each slice user group, and thus it is impossible to ensure the minimum resource allocation ratio rRMPolicyMinRatio that each slice user group needs to prioritize to ensure. Summary of the Invention

[0004] In view of the deficiencies of the existing methods, this application proposes a resource allocation method, apparatus, and processor-readable storage medium to solve the above technical defects.

[0005] In a first aspect, a resource allocation method is provided, which is applied to a network node and includes:

[0006] Obtain the Media Access Control Protocol Data Unit (MAC PDU) and the number of Physical Resource Blocks (PRBs) scheduled and allocated for each slice user group;

[0007] Determine the average uplink actual occupied PRB number for each slice user group according to the MAC PDU;

[0008] Determine the average uplink scheduled and allocated resources for each slice user group according to the scheduled and allocated PRB number;

[0009] Determine the isolation resource parameter for each slice user group according to the average uplink actual occupied PRB number and / or the average uplink scheduled and allocated resources;

[0010] Allocate resources for each slice user group according to the isolation resource parameter.

[0011] Optionally, obtaining the MAC PDU and the scheduled and allocated PRB number for each slice user group includes:

[0012] Obtain the MAC PDU and the scheduled and allocated PRB number for each slice user group within at least one preset statistical period.

[0013] Optionally, determining the average uplink actual occupied PRB number for each slice user group according to the MAC PDU includes:

[0014] Determine the PRB number actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU;

[0015] Determine the instantaneous uplink actual occupied PRB number for each slice user group according to the PRB number actually occupied by the logical channel and the uplink time slots included in each statistical period of at least one statistical period. The instantaneous uplink actual occupied PRB number is the instantaneous uplink actual occupied resource;

[0016] Determine the average uplink actual occupied PRB number for each slice user group through smoothing filtering processing according to the instantaneous uplink actual occupied PRB number.

[0017] Optionally, determining the average uplink scheduled and allocated resources for each slice user group according to the scheduled and allocated PRB number includes:

[0018] Determine the average uplink scheduled and allocated resources for each slice user group according to the scheduled and allocated PRB number and the uplink time slots included in each statistical period of at least one statistical period;

[0019] Determine the average uplink scheduled and allocated resources for each slice user group according to the scheduled and allocated PRB number and the uplink time slots included in each statistical period of the at least one statistical period, including:

[0020] Determine the instantaneous uplink scheduling allocated PRB quantity according to the scheduled allocated PRB quantity and the uplink time slots included in each statistical period. The instantaneous uplink scheduling allocated PRB quantity is the instantaneous uplink scheduling allocated resource;

[0021] According to the instantaneous uplink scheduling allocated PRB quantity, through smoothing filtering processing, determine the uplink average scheduling allocated resource for each slice user group. The uplink average scheduling allocated resource is the uplink average actual scheduled allocated PRB quantity.

[0022] Optionally, the uplink average scheduling allocated resource includes the uplink average actual scheduled allocated PRB quantity. Determine the isolation resource parameter for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocated resource, including:

[0023] When the uplink average actual occupied PRB quantity is less than the pre - configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduled allocated PRB quantity is greater than the pre - configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre - configured PRB quantity for priority guarantee allocation, increase the pre - configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameter.

[0024] Optionally, determine the isolation resource parameter for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocated resource, including:

[0025] When the uplink average actual occupied PRB quantity is not less than the pre - configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre - configured PRB quantity for priority guarantee allocation, decrease the pre - configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameter.

[0026] Optionally, the uplink average scheduling allocated resource includes the uplink average actual scheduled allocated PRB quantity. Determine the isolation resource parameter for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocated resource, including:

[0027] When the uplink average actual occupied PRB quantity is less than the pre - configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduled allocated PRB quantity is not greater than the pre - configured PRB quantity for priority guarantee allocation, then determine the pre - configured PRB quantity for priority guarantee allocation as the isolation resource parameter for each slice user group.

[0028] Optionally, the pre - configured PRB quantity for priority guarantee allocation is determined by the required priority guarantee allocation resource ratio rRMPolicyMinRatio of each slice user group and the preset maximum supported uplink PRB quantity of the system.

[0029] Optionally, resource allocation is performed for each slice user group according to the isolation resource parameter, including:

[0030] When the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum number of physical resource blocks (PRBs) supported by the system for uplink, the isolation resource parameter of each slice user group in all slice user groups is adjusted to obtain the adjusted isolation resource parameter;

[0031] Resource allocation is performed for each slice user group according to the adjusted isolation resource parameter.

[0032] In a second aspect, a resource allocation method is provided, which is applied to a network node and includes:

[0033] Sending downlink control information (DCI) for uplink scheduling to a user equipment (UE), where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information;

[0034] Receiving data sent by the UE according to the slice user group information.

[0035] In a third aspect, a resource allocation method is provided, which is applied to a UE and includes:

[0036] Receiving downlink control information (DCI) for uplink scheduling sent by a network node, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information;

[0037] Determining the resources allocated by the network node to the slice user group according to the slice user group information;

[0038] Sending data to the network node in a logical channel corresponding to the slice user group according to the resources of the slice user group.

[0039] In a fourth aspect, a resource allocation device is provided, which is applied to a network node and includes a memory, a transceiver, and a processor:

[0040] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0041] Obtaining a media access control protocol data unit (MAC PDU) and the number of scheduled allocated physical resource blocks (PRBs) for each slice user group;

[0042] Determining the average actual occupied PRB number of each slice user group according to the MAC PDU;

[0043] Determine the average uplink scheduled allocation resources for each slice user group according to the scheduled allocated PRB quantity.

[0044] Determine the isolation resource parameter for each slice user group according to the average uplink actually occupied PRB quantity and / or the average uplink scheduled allocation resources.

[0045] Perform resource allocation for each slice user group according to the isolation resource parameter.

[0046] Optionally, obtain the MAC PDU and the scheduled allocated PRB quantity for each slice user group, including:

[0047] Obtain the MAC PDU and the scheduled allocated PRB quantity for each slice user group within at least one preset statistical period.

[0048] Optionally, determine the average uplink actually occupied PRB quantity for each slice user group according to the MAC PDU, including:

[0049] Determine the PRB quantity actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU.

[0050] Determine the instantaneous uplink actually occupied PRB quantity for each slice user group according to the PRB quantity actually occupied by the logical channel and the uplink time slots included in each statistical period of at least one statistical period. The instantaneous uplink actually occupied PRB quantity is the instantaneous uplink actually occupied resource.

[0051] Determine the average uplink actually occupied PRB quantity for each slice user group through smoothing filtering processing according to the instantaneous uplink actually occupied PRB quantity.

[0052] Optionally, determine the average uplink scheduled allocation resources for each slice user group according to the scheduled allocated PRB quantity, including:

[0053] Determine the average uplink scheduled allocation resources for each slice user group according to the scheduled allocated PRB quantity and the uplink time slots included in each statistical period of at least one statistical period.

[0054] Determine the average uplink scheduled allocation resources for each slice user group according to the scheduled allocated PRB quantity and the uplink time slots included in each statistical period of the at least one statistical period, including:

[0055] Determine the instantaneous uplink scheduled allocation PRB quantity according to the scheduled allocated PRB quantity and the uplink time slots included in each statistical period. The instantaneous uplink scheduled allocation PRB quantity is the instantaneous uplink scheduled allocation resource.

[0056] Allocate the number of PRBs according to the instantaneous uplink scheduling, and determine the average uplink scheduling allocated resources for each slice user group through smoothing filtering. The average uplink scheduling allocated resources are the average actual scheduled allocated PRB numbers for the uplink.

[0057] Optionally, the average uplink scheduling allocated resources include the average actual scheduled allocated PRB numbers for the uplink. Determine the isolation resource parameters for each slice user group according to the average actual occupied PRB numbers for the uplink and / or the average uplink scheduling allocated resources, including:

[0058] When the average actual occupied PRB numbers for the uplink are less than the pre-configured PRB numbers for priority guarantee allocation, and the average actual scheduled allocated PRB numbers for the uplink are greater than the pre-configured PRB numbers for priority guarantee allocation, then adjust up the pre-configured PRB numbers for priority guarantee allocation according to the average actual occupied PRB numbers for the uplink and the pre-configured PRB numbers for priority guarantee allocation to obtain the isolation resource parameters.

[0059] Optionally, determine the isolation resource parameters for each slice user group according to the average actual occupied PRB numbers for the uplink and / or the average uplink scheduling allocated resources, including:

[0060] When the average actual occupied PRB numbers for the uplink are not less than the pre-configured PRB numbers for priority guarantee allocation, then adjust down the pre-configured PRB numbers for priority guarantee allocation according to the average actual occupied PRB numbers for the uplink and the pre-configured PRB numbers for priority guarantee allocation to obtain the isolation resource parameters.

[0061] Optionally, the average uplink scheduling allocated resources include the average actual scheduled allocated PRB numbers for the uplink. Determine the isolation resource parameters for each slice user group according to the average actual occupied PRB numbers for the uplink and / or the average uplink scheduling allocated resources, including:

[0062] When the average actual occupied PRB numbers for the uplink are less than the pre-configured PRB numbers for priority guarantee allocation, and the average actual scheduled allocated PRB numbers for the uplink are not greater than the pre-configured PRB numbers for priority guarantee allocation, then determine the pre-configured PRB numbers for priority guarantee allocation as the isolation resource parameters for each slice user group.

[0063] Optionally, the pre-configured PRB numbers for priority guarantee allocation are determined by the resource allocation ratio rRMPolicyMinRatio that needs to be preferentially guaranteed for each slice user group and the preset maximum supported PRB numbers for the system uplink.

[0064] Optionally, perform resource allocation for each slice user group according to the isolation resource parameters, including:

[0065] When the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum number of physical resource blocks (PRBs) supported by the system for uplink, adjust the isolation resource parameters of each slice user group in all slice user groups to obtain the adjusted isolation resource parameters;

[0066] Allocate resources to each slice user group according to the adjusted isolation resource parameters.

[0067] In a fifth aspect, a resource allocation device is provided, which is applied to a network node and includes a memory, a transceiver, and a processor:

[0068] The memory is used for storing computer programs; the transceiver is used for transceiving data under the control of the processor; the processor is used for reading the computer programs in the memory and performing the following operations:

[0069] Send downlink control information (DCI) for uplink scheduling to a user equipment (UE), where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used for allocating resources to the slice user group corresponding to the slice user group information;

[0070] Receive data sent by the UE according to the slice user group information.

[0071] In a sixth aspect, a resource allocation device is provided, which is applied to a UE and includes a memory, a transceiver, and a processor:

[0072] The memory is used for storing computer programs; the transceiver is used for transceiving data under the control of the processor; the processor is used for reading the computer programs in the memory and performing the following operations:

[0073] Receive downlink control information (DCI) for uplink scheduling sent by a network node, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used for allocating resources to the slice user group corresponding to the slice user group information;

[0074] Determine the resources allocated by the network node to the slice user group according to the slice user group information;

[0075] Send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

[0076] In a seventh aspect, the present application provides a resource allocation device, which is applied to a network node and includes:

[0077] A first processing unit, configured to obtain a media access control protocol data unit (MAC PDU), and the number of physical resource blocks (PRBs) scheduled and allocated to each slice user group;

[0078] A second processing unit, configured to determine the average number of actually occupied PRBs in the uplink for each slice user group according to the MAC PDU;

[0079] A third processing unit, configured to determine the average scheduled allocated resources in the uplink for each slice user group according to the scheduled allocated number of PRBs;

[0080] A fourth processing unit, configured to determine the isolation resource parameter for each slice user group according to the average number of actually occupied PRBs in the uplink and / or the average scheduled allocated resources in the uplink;

[0081] A fifth processing unit, configured to perform resource allocation for each slice user group according to the isolation resource parameter.

[0082] In an eighth aspect, the present application provides a resource allocation device, which is applied to a network node and includes:

[0083] A sixth processing unit, configured to send downlink control information DCI for uplink scheduling to a user equipment UE, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information;

[0084] A seventh processing unit, configured to receive data sent by the UE according to the slice user group information.

[0085] In a ninth aspect, the present application provides a resource allocation device, which is applied to a UE and includes:

[0086] An eighth processing unit, configured to receive downlink control information DCI for uplink scheduling sent by a network node, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information;

[0087] A ninth processing unit, configured to determine the resources allocated by the network node to the slice user group according to the slice user group information;

[0088] A tenth processing unit, configured to send data to the network node in a logical channel corresponding to the slice user group according to the resources of the slice user group.

[0089] In a tenth aspect, there is provided a processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the methods described in the first aspect, the second aspect, and the third aspect.

[0090] The technical solutions provided by the embodiments of the present application have at least the following beneficial effects:

[0091] Obtain a Media Access Control Protocol Data Unit (MAC PDU) and the number of Physical Resource Blocks (PRBs) scheduled and allocated for each slice user group; determine the average actual occupied PRB number for each slice user group's uplink according to the MAC PDU; determine the average scheduled and allocated resources for each slice user group's uplink according to the scheduled and allocated PRB number; determine the isolation resource parameter for each slice user group according to the average actual occupied PRB number and / or the average scheduled and allocated resources for the uplink; perform resource allocation for each slice user group according to the isolation resource parameter. In this way, it is ensured that each slice user group has at least the resource ratio that needs to be preferentially guaranteed for allocation.

[0092] Additional aspects and advantages of the present application will be given in part in the following description, which will become apparent from the following description, or can be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] To more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments of the present application.

[0094] Figure 1 It is a schematic diagram of the system architecture provided for the embodiments of the present application;

[0095] Figure 2 It is a schematic flowchart of a resource allocation method provided for the embodiments of the present application;

[0096] Figure 3 It is a schematic flowchart of another resource allocation method provided for the embodiments of the present application;

[0097] Figure 4 It is a schematic flowchart of yet another resource allocation method provided for the embodiments of the present application;

[0098] Figure 5 It is a schematic flowchart of yet another resource allocation method provided for the embodiments of the present application;

[0099] Figure 6 It is a schematic diagram of the structure of a resource scheduling device provided for the embodiments of the present application;

[0100] Figure 7 It is a schematic diagram of the structure of a resource scheduling device provided for the embodiments of the present application.

[0101] Figure 8 It is a schematic diagram of the structure of a resource scheduling device provided for the embodiments of the present application;

[0102] Figure 9 It is a schematic diagram of the structure of a resource scheduling device provided for the embodiments of the present application.

[0103] Figure 10Schematic structural diagram of the resource scheduling device provided by the embodiment of the present application;

[0104] Figure 11 Schematic structural diagram of the resource scheduling device provided by the embodiment of the present application. Detailed implementation manners

[0105] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, in which the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary only for explaining the present application and should not be construed as limiting the present application.

[0106] Those skilled in the art of the present technology can understand that unless specifically stated otherwise, the singular forms "a", "an", "the" and "said" used herein may also include the plural forms. It should be further understood that the term "including" used in the specification of the present application means the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups. It should be understood that when we say that an element is "connected" or "coupled" to another element, it can be directly connected or coupled to other elements, or there may also be intermediate elements. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The phrase "and / or" used herein includes all or any unit and all combinations of one or more of the associated listed items.

[0107] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. In the embodiments of the present application, the term "plural" means two or more, and other quantifiers are similar thereto.

[0108] To better understand and illustrate the solutions of the embodiments of the present disclosure, some technical terms involved in the embodiments of the present disclosure will be briefly described below.

[0109] After resource isolation is implemented between slices, resource isolation parameters will be configured for each slice user group. According to the TS28.541 protocol and CR S5-202368, the cell slice isolation strategy and resource isolation parameters are shown in Table 1 below.

[0110] Table 1 Resource isolation parameters

[0111]

[0112]

[0113] The technical solutions provided by the embodiments of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable systems can be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G New Radio (NR) systems, etc. Both terminal devices and network devices are included in these various systems. The system may also include a core network part, such as an evolved packet system (EPS), 5G system (5GS), etc.

[0114] One or more antennas can be used respectively between the network device and the terminal device for multi-input multi-output (MIMO) transmission. The MIMO transmission can be single user MIMO (SU-MIMO) or multiple user MIMO (MU-MIMO). According to the form and number of the combined antennas, the MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, and can also be diversity transmission, precoding transmission, beamforming transmission, etc.

[0115] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0116] A schematic diagram of a network architecture provided by an embodiment of the present application is as Figure 1 shown. The network architecture includes: a UE and a network node. Among them, the UE is, for example, Figure 1 UE110 and UE120 in Figure 1 , and the network node is, for example,

[0117] the network node 130 in

[0118] The network node is deployed in the access network. For example, the network node 130 is deployed in the access network NG-RAN (New Generation-Radio Access Network) of the 5G system. The UE and the network node communicate with each other through a certain air interface technology. For example, they can communicate with each other through cellular technology.

[0117] The UE involved in the embodiments of the present application may be a device that provides voice and / or data connectivity to users, a handheld device with wireless connection functions, or other processing devices connected to a wireless modem, etc. The types of UEs include mobile phones, vehicle user terminals, tablet computers, laptop computers, personal digital assistants, mobile Internet devices, wearable devices, etc.

[0118] The network node involved in the embodiments of the present application can be a base station, which may include multiple cells that provide services to UEs. Depending on specific application scenarios, the base station can also be referred to as an access point, or it can be a device in the access network that communicates with UEs through one or more sectors over the air interface, or have other names. The network node can be used to mutually replace the received air frames with Internet Protocol (IP) packets and act as a router between the UE and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network node can also coordinate the management of the attributes of the air interface. For example, the network node involved in the embodiments of the present application can be a network device (Base Transceiver Station, BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolved network device (evolutional Node B, eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), or a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc. The embodiments of the present application do not limit this. In some network architectures, the network node can include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit can also be geographically separated.

[0119] To make the objectives, technical solutions, and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0120] An embodiment of the present application provides a resource allocation method, which is applied to a network node. The schematic flowchart of this method is as Figure 2 shown, and this method includes:

[0121] Step S101, obtain a Media Access Control Protocol Data Unit (MAC PDU), and the number of Physical Resource Blocks (PRBs) scheduled and allocated to each slice user group.

[0122] Optionally, obtain the MAC PDU and the number of PRBs scheduled and allocated for each slice user group, including:

[0123] Within at least one preset statistical period, obtain the MAC PDU and the number of PRBs scheduled and allocated for each slice user group.

[0124] Step S102, determine the average uplink actual occupied PRB number for each slice user group according to the MAC PDU.

[0125] Optionally, determining the average uplink actual occupied PRB number for each slice user group according to the MAC PDU includes:

[0126] Determine the number of PRBs actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU;

[0127] According to the number of PRBs actually occupied by the logical channel and the uplink time slots included in each statistical period of the at least one statistical period, determine the instantaneous uplink actual occupied PRB number for each slice user group, and the instantaneous uplink actual occupied PRB number is the instantaneous uplink actual occupied resource;

[0128] According to the instantaneous uplink actual occupied PRB number, determine the average uplink actual occupied PRB number for each slice user group through smoothing filtering.

[0129] Step S103, determine the average uplink scheduled and allocated resource for each slice user group according to the scheduled and allocated PRB number.

[0130] Optionally, determining the average uplink scheduled and allocated resource for each slice user group according to the scheduled and allocated PRB number includes:

[0131] Determine the average uplink scheduled and allocated resource for each slice user group according to the scheduled and allocated PRB number and the uplink time slots included in each statistical period of the at least one statistical period;

[0132] Determine the average uplink scheduled and allocated resource for each slice user group according to the scheduled and allocated PRB number and the uplink time slots included in each statistical period of the at least one statistical period, including:

[0133] Determine the instantaneous uplink scheduled and allocated PRB number according to the scheduled and allocated PRB number and the uplink time slots included in each statistical period, and the instantaneous uplink scheduled and allocated PRB number is the instantaneous uplink scheduled and allocated resource;

[0134] According to the instantaneous uplink scheduled and allocated PRB number, determine the average uplink scheduled and allocated resource for each slice user group through smoothing filtering, and the average uplink scheduled and allocated resource is the average uplink actual scheduled and allocated PRB number.

[0135] Step S104: Determine the isolation resource parameters for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduled allocated resources.

[0136] Optionally, the uplink average scheduled allocated resources include the uplink average actual scheduled allocated PRB quantity. Determining the isolation resource parameters for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduled allocated resources includes:

[0137] When the uplink average actual occupied PRB quantity is less than the pre-configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduled allocated PRB quantity is greater than the pre-configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre-configured PRB quantity for priority guarantee allocation, increase the pre-configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameters.

[0138] Optionally, determining the isolation resource parameters for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduled allocated resources includes:

[0139] When the uplink average actual occupied PRB quantity is not less than the pre-configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre-configured PRB quantity for priority guarantee allocation, decrease the pre-configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameters.

[0140] Optionally, the uplink average scheduled allocated resources include the uplink average actual scheduled allocated PRB quantity. Determining the isolation resource parameters for each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduled allocated resources includes:

[0141] When the uplink average actual occupied PRB quantity is less than the pre-configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduled allocated PRB quantity is not greater than the pre-configured PRB quantity for priority guarantee allocation, then determine the pre-configured PRB quantity for priority guarantee allocation as the isolation resource parameters for each slice user group.

[0142] Optionally, the pre-configured PRB quantity for priority guarantee allocation is determined by the required priority guarantee allocation resource ratio rRMPolicyMinRatio of each slice user group and the preset maximum supported PRB quantity of the system uplink.

[0143] Step S105: Allocate resources to each slice user group according to the isolation resource parameters.

[0144] Optionally, resource allocation is performed for each slice user group according to the isolation resource parameter, including:

[0145] When the sum of the isolation resource parameters among all slice user groups is greater than the preset maximum number of physical resource blocks (PRBs) supported by the system for uplink, the isolation resource parameter of each slice user group in all slice user groups is adjusted to obtain the adjusted isolation resource parameter;

[0146] Resource allocation is performed for each slice user group according to the adjusted isolation resource parameter.

[0147] In the embodiments of the present application, a media access control protocol data unit (MAC PDU) is obtained, as well as the number of physical resource blocks (PRBs) scheduled and allocated for each slice user group; according to the MAC PDU, the average actual occupied PRB number for the uplink of each slice user group is determined; according to the scheduled and allocated PRB number, the average scheduled and allocated resource for the uplink of each slice user group is determined; according to the average actual occupied PRB number for the uplink and / or the average scheduled and allocated resource for the uplink, the isolation resource parameter of each slice user group is determined; and resource allocation is performed for each slice user group according to the isolation resource parameter. In this way, it is ensured that each slice user group has at least a resource ratio that needs to be preferentially guaranteed for allocation.

[0148] In the embodiments of the present application, a resource allocation method is provided, which is applied to a network node. The schematic flow diagram of this method is as Figure 3 shown, and this method includes:

[0149] Step S201: Send downlink control information (DCI) for uplink scheduling to a user equipment (UE). The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information.

[0150] Step S202: Receive data sent by the UE according to the slice user group information.

[0151] In the embodiments of the present application, it is ensured that each slice user group has at least a resource ratio that needs to be preferentially guaranteed for allocation.

[0152] In the embodiments of the present application, a resource allocation method is provided, which is applied to the UE. The schematic flow diagram of this method is as Figure 4 shown, and this method includes:

[0153] Step S301: Receive downlink control information (DCI) for uplink scheduling sent by a network node. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information.

[0154] Step S302: Determine the resources allocated by the network node to the slice user group according to the slice user group information.

[0155] Step S303: Send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

[0156] In the embodiment of the present application, it is ensured that each slice user group has at least a resource ratio that needs to be preferentially guaranteed.

[0157] The resource configuration method of the above embodiment of the present application will be comprehensively and elaborately introduced through the following embodiments:

[0158] In an embodiment of the present application:

[0159] Monitoring and slow adjustment mechanism for slice isolation resources: After the base station receives the MAC PDU (Protocol Data Unit) at the MAC layer, it can accurately obtain the data volume sent by each logical channel, so as to count the actual uplink occupied resources of each slice user group. And compare with the slice isolation resource configuration parameters of the corresponding slice user group, and slowly adjust the slice isolation resource configuration parameters, so as to achieve the purpose of statistically meeting the configured slice isolation resource requirements for a long time.

[0160] An embodiment of the present application provides a resource scheduling method, which is applied to a base station. The method includes:

[0161] Step 1: Statistically calculate the instantaneous uplink actual occupied resources of each slice user group in each period based on the MAC PDU, and perform a smoothing filtering process on the instantaneous uplink actual occupied resources of each slice user group to obtain the uplink average actual occupied resources of each slice user group.

[0162] Optionally, every time the base station receives a MAC PDU submitted by the physical layer, it analyzes the MAC subheader contained therein to determine which logical channels the data is transmitted through and the transmission data length. According to the ID of the logical channel, query the slice user group to which it belongs, calculate the number of PRBs actually occupied by the logical channel, and accumulate the number of PRBs actually occupied by the logical channel to the uplink actually occupied PRB number of the slice user group to which it belongs.

[0163] Among them: The instantaneous uplink actual occupied PRB number of slice user group j is InstantActualPrbnum_per_Group j ;

[0164] The number of PRBs actually occupied by logical channel i (quantity) is ActualPrbnum_per_LC i ;

[0165] The number of uplink time slots included in each statistical period is NSlot_per_Period.

[0166] When receiving the MAC PDU x submitted by the physical layer, the sum of the data lengths in all MAC subheaders included in this MAC PDU is datalen_sum_per_macpdu x , where the data length in the MAC subheader corresponding to logical channel i is datalen_LC i , and this logical channel belongs to slice user group j. The number of PRBs allocated for the successful transmission of this MAC PDU (including initial transmission and retransmission) is TotalPRB_HARQ x ; then the number of PRBs actually occupied by logical channel i, ActualPrbnum_per_LC i is updated according to formula (1) as follows:

[0167]

[0168] The instantaneous uplink actual occupied PRB number of slice user group j, InstantActualPrbnum_per_Group j is updated according to formula (2) as follows:

[0169]

[0170] The average uplink actual occupied PRB number of slice user group j, ActualPrbnum_per_Group j is updated according to formula (3) as follows:

[0171]

[0172] where NT is the cumulative number of statistical periods.

[0173] Step 2: Statistically calculate the instantaneous uplink scheduling allocation resources for each slice user group in each period, and perform a smoothing filtering process on the instantaneous uplink scheduling allocation resources of each slice user group to obtain the average uplink scheduling allocation resources of each slice user group.

[0174] Among them: The instantaneous uplink scheduling allocated PRB number of slice user group j is InstantSchPrbnum_per_Group j .

[0175] Optionally, after each uplink scheduling, the scheduled allocated PRB number of slice user group j, SchPrbnum_per_Group, can be obtained j, the number of PRBs instantaneously scheduled and allocated for the slice user group j, InstantSchPrbnum_per_Group j Update according to formula (4) as follows:

[0176]

[0177] The average number of PRBs actually scheduled and allocated for the slice user group j, AveSchPrbnum_per_Group j Update according to formula (5) as follows:

[0178]

[0179] Where, NT is the number of cumulative statistical periods.

[0180] Step 3, calculate the adjusted isolation resource parameter value for each slice user group. The isolation parameter specifically refers to the resource ratio rRMPolicyMinRatio that the slice user group needs to prioritize for allocation.

[0181] Optionally, Step 3 includes Steps A1 - A2; Steps A1 - A2 are as follows:

[0182] Step A1, sequentially determine each slice user group to check whether its corresponding isolation resource parameter needs to be adjusted.

[0183] Optionally, assume the currently judged slice user group is j, the resource ratio rRMPolicyMinRatio that this slice user group is configured to prioritize for allocation, and the maximum number of PRBs supported by the system uplink is TotalPrbNum ul , then the PRB resources prioritized for allocation by the slice user group j are as shown in formula (6), and formula (6) is as follows:

[0184] Config_Ensure_Prbnum_per_Group j = rRMPolicyMinRatio × TotalPrbNum ul Formula (6)

[0185] Assume the number of PRBs prioritized for allocation after adjustment for the slice user group j is Ensure_PrbNum_per_Group j .

[0186] Optionally, for the slice user group j, if the average number of PRBs actually occupied by its uplink is less than the number of PRBs prioritized for allocation configured for it, that is, ActualPrbnum_per_Group j < Config_Ensure_PrbNum_per_Groupj , it indicates that the slice user group does not meet the required isolated resource occupancy. It is necessary to further judge:

[0187] If the average number of actually scheduled and allocated PRBs in the uplink is greater than the number of PRBs AveSchPrbnum_per_Group allocated with priority guarantee configured for it j >Config_Ensure_PrbNum_per_Group j , it indicates that the data volume of the slice user group is sufficient, and it is necessary to increase the isolated resource parameters of the slice user group. The adjusted number of PRBs Ensure_PrbNum_per_Group allocated with priority guarantee for the adjusted slice user group j j As shown in formula (7), formula (7) is as follows:

[0188] Ensure_PrbNum_per_Group j =2×Config_Ensure_PrbNum_per_Group j -ActualPrbNum_per_Group j Formula (7)

[0189] Otherwise, it indicates that the data volume of the slice user group is insufficient and there is no need to adjust the slice isolation parameters. As shown in formula (8):

[0190] Ensure_PrbNum_per_Group j =Config_Ensure_PrbNum_per_Group j Formula (8)

[0191] Optionally, for slice user group j, if the average number of actually occupied PRBs in the uplink is not less than the number of PRBs allocated with priority guarantee configured for it, that is, ActualPrbnum_per_Group j ≥Config_Ensure_PrbNum_per_Group j , it indicates that the actual resource usage of the slice user group reaches or even exceeds the required isolated resource occupancy, and it is necessary to appropriately reduce the slice isolation parameters. The adjusted number of PRBs Ensure_PrbNum_per_Group allocated with priority guarantee for the adjusted slice user group j j As shown in formula (7), formula (7) is as follows:

[0192] Ensure_PrbNum_per_Group j =2×Config_Ensure_PrbNum_per_Groupj -ActualPrbNum_per_Group j Formula (7)

[0193] Step A2, calculate the sum of the adjusted isolation resource parameters of all slice user groups, Ensure_PrbNum_per_Group_sum. If MaxPrbNum_per_Group_sum > TotalPrbNum ul , then further adjust the isolation resource parameters of each slice user group as shown in Formula (9), and Formula (9) is as follows:

[0194]

[0195] where, TotalPrbNum ul is the maximum number of PRBs supported by the system for uplink, and SliceGroupNum is the total number of current slice user groups.

[0196] Step 4, the base station uses the adjusted isolation resource parameters of each slice user group (the number of PRBs preferentially guaranteed to be allocated for each slice user group) for uplink scheduling, and this parameter is required in the scheduling to allocate resources for each slice user group.

[0197] The technical solution provided by the embodiments of the present application has at least the following beneficial effects:

[0198] It is possible to accurately count the resource ratio already allocated to each slice user group by monitoring the slice user group to which the actually transmitted data belongs, and then compare it with the resource ratio rRMPolicyMinRatio that each slice user group needs to at least preferentially guarantee to be allocated, and slowly adjust the resource ratio rRMPolicyMinRatio that each slice user group needs to at least preferentially guarantee to be allocated, so as to ensure the resource ratio rRMPolicyMinRatio that each slice user group needs to at least preferentially guarantee to be allocated.

[0199] In an embodiment of the present application:

[0200] Assume that the terminal has concurrent logical channel 1 and logical channel 2, and they belong to slice user group 1 and slice user group 2 respectively. Assume that there is only logical channel 1 in slice user group 1 and only logical channel 2 in slice user group 2.

[0201] The slice user group information corresponding to the authorization cannot be carried in the uplink scheduling DCI.

[0202] Suppose the proportion of resources that need to be preferentially guaranteed for slice user group 1 configured by the base station is 20%, and the proportion of resources that need to be preferentially guaranteed for slice user group 2 is 20%. The maximum available uplink resources are 100 PRBs. Then, the resources that need to be preferentially guaranteed for slice user group 1 are 20 PRBs, and the resources that need to be preferentially guaranteed for slice user group 1 are 20 PRBs.

[0203] Suppose that in each period, the base station will schedule and allocate resources for logical channel 1 and logical channel 2 respectively once, and send uplink scheduling DCI (20 PRBs are scheduled each time for logical channel 1, and 20 PRBs are scheduled each time for logical channel 2). The terminal always sends the MAC PDU composed of the service data in logical channel 2.

[0204] An embodiment of the present application provides a resource scheduling method, which is applied to a base station. The method includes:

[0205] Step 11, when the base station receives the MAC PDU, if it is analyzed based on the MAC subheader that the MAC PDU corresponds to the data of logical channel 2, then the 20 PRBs occupied by the transmission of the MAC PDU are accumulated into the instantaneous uplink actual occupied resources of slice user group 2.

[0206] After smoothing filtering processing, the average uplink actual occupied resources of slice user group 1 can be obtained as 0, and the average uplink actual occupied resources of slice user group 2 are 40.

[0207] Step 12, count the instantaneous uplink scheduled and allocated resources of each slice user group. When the base station schedules and allocates 20 PRB resources for logical channel 1, the 20 PRB resources scheduled and allocated are accumulated into the instantaneous uplink scheduled and allocated resources of slice user group 1. When the base station schedules and allocates 20 PRB resources for logical channel 2, the 20 PRB resources scheduled and allocated are accumulated into the instantaneous uplink scheduled and allocated resources of slice user group 2.

[0208] After smoothing filtering processing, the average number of actually scheduled and allocated PRBs of slice user group 1 in the uplink is 20, and the average actually occupied resources of slice user group 2 in the uplink are 20.

[0209] Step 13, sequentially judge slice user group 1 and slice user group 2, and judge whether the corresponding isolation resource parameters need to be adjusted.

[0210] For slice user group 1, the average number of actually occupied PRBs in the uplink 0 is less than the configured preferentially guaranteed allocated PRB number 20, and the average number of actually scheduled and allocated PRBs in the uplink 20 is not less than the configured preferentially guaranteed allocated PRB number 20. Then, it is considered that the data volume of this slice user group is sufficient, and the isolation resource parameters of this slice user group need to be increased. The adjusted preferentially guaranteed allocated PRB number for slice user group 2 is 2×20 - 0 = 40.

[0211] For slice user group 2, if the average number of actually occupied PRBs in the uplink, which is 40, is not less than the number of PRBs allocated with priority guarantee configured for it, which is 20, it is considered that the actual resource usage of this slice user group reaches or even exceeds the required isolated resource occupancy, and then the slice isolation parameter needs to be appropriately reduced. The adjusted number of PRBs allocated with priority guarantee for slice user group 1 is 2×20 - 40 = 0.

[0212] Step 14: The uplink scheduling allocates resources for each slice user group based on the adjusted slice user group isolation resource parameters.

[0213] The base station will schedule 40 PRBs for slice user group 1 each time. No resource scheduling and allocation will be performed for slice user group 2.

[0214] When there is no data left in logical channel 2 on the terminal side, when the base station schedules slice user group 1, the terminal will use 40 PRBs to send the data in logical channel 1, and then slice user group 1 can gradually meet the requirement of the configured number of PRBs allocated with priority guarantee.

[0215] In an embodiment of the present application:

[0216] The scheduling authorization information carried in the uplink scheduling DCI specifies the slice user group corresponding to the current authorization.

[0217] An embodiment of the present application provides a resource scheduling method, which includes:

[0218] Step 21: In the uplink scheduling DCI format, add the slice user group information corresponding to the current authorization.

[0219] Step 22: After receiving the uplink authorization, the terminal only selects the logical channel data in the slice user group specified by this authorization for transmission on this authorization.

[0220] In an embodiment of the present application:

[0221] Carry the slice user group information corresponding to the current authorization in the uplink scheduling DCI.

[0222] Assume that the terminal has concurrent logical channel 1 and logical channel 2, which belong to slice user group 1 and slice user group 2 respectively.

[0223] An embodiment of the present application provides a resource allocation method, and the schematic flow diagram of this method is as Figure 5 shown, and this method includes:

[0224] Step S401: The base station sends DCI for uplink scheduling to the UE.

[0225] Optionally, carry the scheduling authorization information of slice user group 1 corresponding to the authorization in the uplink authorization DCI.

[0226] Step S402: The UE sends the service data corresponding to logical channel 1 to the base station.

[0227] Optionally, if PRB (Physical Resource Block) resources are allocated to logical channel 1 of the terminal during scheduling, the scheduling authorization information for slice user group 1 corresponding to the authorization is carried in the uplink grant DCI. After the UE receives the uplink grant, it only selects the service data in logical channel 1 for transmission.

[0228] Step S403: The base station sends DCI for uplink scheduling to the UE.

[0229] Optionally, the scheduling authorization information for slice user group 2 corresponding to the authorization is carried in the uplink grant DCI.

[0230] Step S404: The UE sends the service data corresponding to logical channel 2 to the base station.

[0231] Optionally, if PRB resources are allocated to logical channel 2 of the terminal during scheduling, the scheduling authorization information for slice user group 2 corresponding to the authorization is carried in the uplink grant DCI. After the UE receives the uplink grant, it only selects the service data in logical channel 2 for transmission.

[0232] The technical solution provided by the embodiments of the present application has at least the following beneficial effects:

[0233] If the scheduling authorization information carried in the uplink scheduling DCI specifies the slice user group corresponding to the current authorization, and the UE also sends data according to the specified slice user group, then the accurate statistics of the resource ratio already allocated to each slice user group can be simply performed according to the relationship between the authorization and the slice user group determined during scheduling.

[0234] Based on the same inventive concept, the embodiments of the present application also provide a resource configuration device, which is applied to a network node. The structural schematic diagram of the device is as Figure 6 shown. The transceiver 1200 is used to receive and send data under the control of the processor 1210.

[0235] Among them, in Figure 6Among them, the bus architecture may include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors represented by processor 1210 and memories represented by memory 1220 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and thus will not be further described herein. The bus interface provides an interface. The transceiver 1200 may be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission media include wireless channels, wired channels, optical fiber cables and other transmission media. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 when executing operations.

[0236] The processor 1210 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0237] The processor 1210 is used to read the computer program in the memory and perform the following operations:

[0238] Obtain a media access control protocol data unit MAC PDU, and the number of scheduled allocated physical resource blocks PRBs for each slice user group;

[0239] Determine the average actual occupied PRB number of each slice user group according to the MAC PDU;

[0240] Determine the average scheduled allocated resources of each slice user group according to the scheduled allocated PRB number;

[0241] Determine the isolation resource parameter of each slice user group according to the average actual occupied PRB number of the uplink and / or the average scheduled allocated resources of the uplink;

[0242] Perform resource allocation for each slice user group according to the isolation resource parameter.

[0243] Optionally, obtaining the MAC PDU, and the number of scheduled allocated PRBs for each slice user group includes:

[0244] Obtain the MAC PDU, and the number of scheduled allocated PRBs for each slice user group within at least one preset statistical period.

[0245] Optionally, according to the MAC PDU, determine the average actual occupied PRB quantity of each slice user group, including:

[0246] According to the MAC PDU, determine the PRB quantity actually occupied by the logical channel corresponding to each slice user group;

[0247] According to the PRB quantity actually occupied by the logical channel and the uplink time slots included in each of at least one statistical period, determine the instantaneous uplink actually occupied PRB quantity of each slice user group, where the instantaneous uplink actually occupied PRB quantity is the instantaneous uplink actually occupied resource;

[0248] According to the instantaneous uplink actually occupied PRB quantity, through smoothing filtering processing, determine the average actual occupied PRB quantity of each slice user group.

[0249] Optionally, according to the scheduled allocated PRB quantity, determine the average uplink scheduled allocated resource of each slice user group, including:

[0250] According to the scheduled allocated PRB quantity and the uplink time slots included in each of at least one statistical period, determine the average uplink scheduled allocated resource of each slice user group;

[0251] According to the scheduled allocated PRB quantity and the uplink time slots included in each of the at least one statistical period, determine the average uplink scheduled allocated resource of each slice user group, including:

[0252] According to the scheduled allocated PRB quantity and the uplink time slots included in each statistical period, determine the instantaneous uplink scheduled allocated PRB quantity, where the instantaneous uplink scheduled allocated PRB quantity is the instantaneous uplink scheduled allocated resource;

[0253] According to the instantaneous uplink scheduled allocated PRB quantity, through smoothing filtering processing, determine the average uplink scheduled allocated resource of each slice user group, and the average uplink scheduled allocated resource is the average actual scheduled allocated PRB quantity.

[0254] Optionally, the average uplink scheduled allocated resource includes the average actual scheduled allocated PRB quantity. According to the average actual occupied PRB quantity and / or the average uplink scheduled allocated resource, determine the isolation resource parameter of each slice user group, including:

[0255] When the average number of actually occupied PRBs in the uplink is less than the pre-configured number of PRBs for priority guarantee allocation, and the average number of actually scheduled and allocated PRBs in the uplink is greater than the pre-configured number of PRBs for priority guarantee allocation, then according to the average number of actually occupied PRBs in the uplink and the pre-configured number of PRBs for priority guarantee allocation, the pre-configured number of PRBs for priority guarantee allocation is increased to obtain the isolation resource parameter.

[0256] Optionally, according to the average number of actually occupied PRBs in the uplink and / or the average scheduled and allocated resources in the uplink, determine the isolation resource parameter for each slice user group, including:

[0257] When the average number of actually occupied PRBs in the uplink is not less than the pre-configured number of PRBs for priority guarantee allocation, then according to the average number of actually occupied PRBs in the uplink and the pre-configured number of PRBs for priority guarantee allocation, the pre-configured number of PRBs for priority guarantee allocation is decreased to obtain the isolation resource parameter.

[0258] Optionally, the average scheduled and allocated resources in the uplink include the average number of actually scheduled and allocated PRBs in the uplink. According to the average number of actually occupied PRBs in the uplink and / or the average scheduled and allocated resources in the uplink, determine the isolation resource parameter for each slice user group, including:

[0259] When the average number of actually occupied PRBs in the uplink is less than the pre-configured number of PRBs for priority guarantee allocation, and the average number of actually scheduled and allocated PRBs in the uplink is not greater than the pre-configured number of PRBs for priority guarantee allocation, then the pre-configured number of PRBs for priority guarantee allocation is determined as the isolation resource parameter for each slice user group.

[0260] Optionally, the pre-configured number of PRBs for priority guarantee allocation is determined by the resource allocation ratio rRMPolicyMinRatio that needs to be preferentially guaranteed for each slice user group and the preset maximum number of supported PRBs in the system uplink.

[0261] Optionally, according to the isolation resource parameter, perform resource allocation for each slice user group, including:

[0262] When the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum number of supported PRBs in the system uplink, then adjust the isolation resource parameter of each slice user group in all slice user groups to obtain the adjusted isolation resource parameter;

[0263] Perform resource allocation for each slice user group according to the adjusted isolation resource parameter.

[0264] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0265] Based on the same inventive concept, an embodiment of the present application also provides a resource allocation device, which is applied to a network node. The schematic structural diagram of the device is as follows Figure 7 shown. The transceiver 1300 is used to receive and send data under the control of the processor 1310.

[0266] Among them, in Figure 7 , the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1310 and the memory represented by the memory 1320 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits together, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 1300 may be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, and other transmission mediums. The processor 1310 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1310 when performing operations.

[0267] The processor 1310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0268] The processor 1310 is used to read the computer program in the memory and perform the following operations:

[0269] Send downlink control information DCI for uplink scheduling to the user equipment UE. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information;

[0270] Receive data sent by the UE according to the slice user group information.

[0271] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0272] Based on the same inventive concept, an embodiment of the present application further provides a resource allocation device, which is applied to a UE. The structural schematic diagram of the device is as Figure 8 shown. The transceiver 1400 is used to receive and send data under the control of the processor 1410.

[0273] Among them, in Figure 8 , the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1410 and the memory represented by the memory 1420 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 1400 may be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical cables, and other transmission mediums. For different user devices, the user interface 1430 may also be an interface capable of externally or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0274] The processor 1410 is responsible for managing the bus architecture and general processing, and the memory 1420 can store the data used by the processor 1410 when performing operations.

[0275] Optionally, the processor 1410 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field - Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi - core architecture.

[0276] The processor is used to execute the method described in the third aspect provided by the embodiments of the present application by calling the computer program stored in the memory according to the obtained executable instructions. The processor and the memory may also be physically separated.

[0277] The processor 1410 is used to read the computer program in the memory 1420 and perform the following operations:

[0278] Receive downlink control information DCI for uplink scheduling sent by a network node. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, which is used to allocate resources to the slice user group corresponding to the slice user group information;

[0279] Determine the resources allocated by the network node to the slice user group according to the slice user group information;

[0280] Send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

[0281] It should be noted here that the above device provided in the embodiment of the present invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. The same parts and beneficial effects as those in the method embodiment will not be specifically described in this embodiment.

[0282] Based on the same inventive concept as the foregoing embodiments, an embodiment of the present application further provides a resource configuration device, which is applied to a network node. The structural schematic diagram of the device is as Figure 9 shown. Based on the resource configuration device 30, it includes a first processing unit 301, a second processing unit 302, a third processing unit 303, a fourth processing unit 304, and a fifth processing unit 305.

[0283] The first processing unit 301 is configured to obtain a media access control protocol data unit MAC PDU and the number of scheduled allocated physical resource blocks PRBs for each slice user group;

[0284] The second processing unit 302 is configured to determine the average actual occupied PRB number of each slice user group according to the MAC PDU;

[0285] The third processing unit 303 is configured to determine the average scheduled allocated resources of each slice user group according to the scheduled allocated PRB number;

[0286] The fourth processing unit 304 is configured to determine the isolation resource parameter of each slice user group according to the average actual occupied PRB number and / or the average scheduled allocated resources of the uplink;

[0287] The fifth processing unit 305 is configured to allocate resources to each slice user group according to the isolation resource parameter.

[0288] Optionally, the first processing unit 301 is specifically configured to obtain the MAC PDU and the number of scheduled allocated PRBs for each slice user group within at least one preset statistical period.

[0289] Optionally, the second processing unit 302 is specifically configured to determine the number of PRBs actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU; determine the instantaneous uplink actual occupied PRB number of each slice user group according to the number of PRBs actually occupied by the logical channel and the uplink time slots included in each statistical period of at least one statistical period, where the instantaneous uplink actual occupied PRB number is the instantaneous uplink actual occupied resource; and determine the uplink average actual occupied PRB number of each slice user group through smoothing filtering processing according to the instantaneous uplink actual occupied PRB number.

[0290] Optionally, the third processing unit 303 is specifically configured to determine the uplink average scheduled allocation resource of each slice user group according to the scheduled allocated PRB number and the uplink time slots included in each statistical period of at least one statistical period; the third processing unit 303 is specifically configured to determine the instantaneous uplink scheduled allocated PRB number according to the scheduled allocated PRB number and the uplink time slots included in each statistical period, where the instantaneous uplink scheduled allocated PRB number is the instantaneous uplink scheduled allocated resource; and determine the uplink average scheduled allocation resource of each slice user group through smoothing filtering processing according to the instantaneous uplink scheduled allocated PRB number, and the uplink average scheduled allocation resource is the uplink average actual scheduled allocated PRB number.

[0291] Optionally, when the uplink average actual occupied PRB number is less than the pre-configured PRB number for priority guarantee allocation, and the uplink average actual scheduled allocated PRB number is greater than the pre-configured PRB number for priority guarantee allocation, the fourth processing unit 304 is specifically configured to increase the pre-configured PRB number for priority guarantee allocation according to the uplink average actual occupied PRB number and the pre-configured PRB number for priority guarantee allocation to obtain the isolation resource parameter.

[0292] Optionally, when the uplink average actual occupied PRB number is not less than the pre-configured PRB number for priority guarantee allocation, the fourth processing unit 304 is specifically configured to decrease the pre-configured PRB number for priority guarantee allocation according to the uplink average actual occupied PRB number and the pre-configured PRB number for priority guarantee allocation to obtain the isolation resource parameter.

[0293] Optionally, when the uplink average actual occupied PRB number is less than the pre-configured PRB number for priority guarantee allocation, and the uplink average actual scheduled allocated PRB number is not greater than the pre-configured PRB number for priority guarantee allocation, the fourth processing unit 304 is specifically configured to determine the pre-configured PRB number for priority guarantee allocation as the isolation resource parameter of each slice user group.

[0294] Optionally, the pre-configured number of PRBs with priority guarantee allocation is determined by the ratio rRMPolicyMinRatio of the allocated resources that need to be preferentially guaranteed for each slice user group and the preset maximum number of PRBs supported by the system uplink.

[0295] Optionally, the fifth processing unit 305 is specifically configured to, when the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum number of PRBs supported by the system uplink, adjust the isolation resource parameters of each slice user group in all slice user groups to obtain the adjusted isolation resource parameters; and perform resource allocation for each slice user group according to the adjusted isolation resource parameters.

[0296] It should be noted here that the above device provided in the embodiment of the present invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiment in this embodiment will not be specifically described herein.

[0297] Based on the same inventive concept as the foregoing embodiments, an embodiment of the present application also provides a resource configuration device, which is applied to a network node. The structural schematic diagram of the device is as Figure 10 shown. Based on the resource configuration device 40, it includes a sixth processing unit 401 and a seventh processing unit 402.

[0298] The sixth processing unit 401 is configured to send downlink control information DCI for uplink scheduling to a user equipment UE. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to perform resource allocation for the slice user group corresponding to the slice user group information;

[0299] The seventh processing unit 402 is configured to receive data sent by the UE according to the slice user group information.

[0300] It should be noted here that the above device provided in the embodiment of the present invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiment in this embodiment will not be specifically described herein.

[0301] Based on the same inventive concept as the foregoing embodiments, an embodiment of the present application also provides a resource configuration device, which is applied to a UE. The structural schematic diagram of the device is as Figure 11 shown. Based on the resource configuration device 50, it includes an eighth processing unit 501, a ninth processing unit 502, and a tenth processing unit 503.

[0302] The eighth processing unit 501 is configured to receive downlink control information DCI for uplink scheduling sent by a network node. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, where the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information;

[0303] The ninth processing unit 502 is configured to determine the resources allocated by the network node to the slice user group according to the slice user group information;

[0304] The tenth processing unit 503 is configured to send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

[0305] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0306] It should be noted that the division of units in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation. In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0307] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a processor-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disc, etc., which can store program codes.

[0308] Based on the same inventive concept, an embodiment of the present application further provides a processor-readable storage medium storing a computer program, which is used to implement the steps of any resource configuration method provided in any one of the embodiments or any optional implementation manners in the embodiments of the present application when being executed by a processor.

[0309] The processor-readable storage medium can be any available medium or data storage device accessible by the processor, including but not limited to magnetic memories (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical memories (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memories (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSD)).

[0310] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories and optical memories, etc.) containing computer-usable program code.

[0311] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0312] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the processor-readable memory generate a manufactured article including an instruction device that implements the functions specified in Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0313] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus, such that a series of operation steps are executed on the computer or other programmable apparatus to generate a computer-implemented process, thereby providing instructions for implementing the steps specified in the process Figure 1 a process or processes and / or blocks Figure 1 steps for the functions specified in a block or blocks.

[0314] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to cover these modifications and variations.

Claims

1. A resource allocation method, applied to a network node, characterized in that, Including: Obtaining a Media Access Control Protocol Data Unit (MAC PDU) and the number of Physical Resource Blocks (PRBs) scheduled and allocated to each slice user group; Determining the average number of actually occupied PRBs in the uplink for each slice user group according to the MAC PDU; Determining the average scheduled and allocated resources in the uplink for each slice user group according to the scheduled and allocated number of PRBs; Determining the isolation resource parameter for each slice user group according to the average number of actually occupied PRBs in the uplink and / or the average scheduled and allocated resources in the uplink; Performing resource allocation for each slice user group according to the isolation resource parameter.

2. The method according to claim 1, characterized in that, The obtaining of the MAC PDU and the number of PRBs scheduled and allocated to each slice user group includes: Obtaining the MAC PDU and the number of PRBs scheduled and allocated to each slice user group within at least one preset statistical period.

3. The method according to claim 2, wherein The determining of the average number of actually occupied PRBs in the uplink for each slice user group according to the MAC PDU includes: Determining the number of PRBs actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU; Determining the instantaneous number of actually occupied PRBs in the uplink for each slice user group according to the number of PRBs actually occupied by the logical channel and the uplink time slots included in each statistical period of the at least one statistical period, where the instantaneous number of actually occupied PRBs in the uplink is the instantaneous actually occupied resource; Determining the average number of actually occupied PRBs in the uplink for each slice user group through smoothing filtering processing according to the instantaneous number of actually occupied PRBs in the uplink.

4. The method according to claim 2, characterized in that, The determining of the average scheduled and allocated resources in the uplink for each slice user group according to the scheduled and allocated number of PRBs includes: Determining the average scheduled and allocated resources in the uplink for each slice user group according to the scheduled and allocated number of PRBs and the uplink time slots included in each statistical period of the at least one statistical period; The determining of the average scheduled and allocated resources in the uplink for each slice user group according to the scheduled and allocated number of PRBs and the uplink time slots included in each statistical period of the at least one statistical period includes: Determining the instantaneous number of scheduled and allocated PRBs in the uplink according to the scheduled and allocated number of PRBs and the uplink time slots included in each statistical period, where the instantaneous number of scheduled and allocated PRBs in the uplink is the instantaneous scheduled and allocated resource; Determining the average scheduled and allocated resources in the uplink for each slice user group through smoothing filtering processing according to the instantaneous number of scheduled and allocated PRBs in the uplink, where the average scheduled and allocated resources in the uplink is the average actually scheduled and allocated number of PRBs.

5. The method according to claim 2, wherein The average scheduled and allocated resources in the uplink include the average actually scheduled and allocated number of PRBs. The determining of the isolation resource parameter for each slice user group according to the average number of actually occupied PRBs in the uplink and / or the average scheduled and allocated resources in the uplink includes: When the average actual occupied PRB number in the uplink is less than the pre-configured PRB number for priority guarantee allocation, and the average actual scheduled allocated PRB number in the uplink is greater than the pre-configured PRB number for priority guarantee allocation, then according to the average actual occupied PRB number in the uplink and the pre-configured PRB number for priority guarantee allocation, the pre-configured PRB number for priority guarantee allocation is increased to obtain the isolation resource parameter.

6. The method according to claim 2, wherein The determining the isolation resource parameter for each slice user group according to the average actual occupied PRB number in the uplink and / or the average scheduled allocated resource in the uplink includes: When the average actual occupied PRB number in the uplink is not less than the pre-configured PRB number for priority guarantee allocation, then according to the average actual occupied PRB number in the uplink and the pre-configured PRB number for priority guarantee allocation, the pre-configured PRB number for priority guarantee allocation is decreased to obtain the isolation resource parameter.

7. The method according to claim 2, characterized in that The average scheduled allocated resource in the uplink includes the average actual scheduled allocated PRB number in the uplink. The determining the isolation resource parameter for each slice user group according to the average actual occupied PRB number in the uplink and / or the average scheduled allocated resource in the uplink includes: When the average actual occupied PRB number in the uplink is less than the pre-configured PRB number for priority guarantee allocation, and the average actual scheduled allocated PRB number in the uplink is not greater than the pre-configured PRB number for priority guarantee allocation, then the pre-configured PRB number for priority guarantee allocation is determined as the isolation resource parameter for each slice user group.

8. The method according to any one of claims 5 to 7, characterized in that The pre-configured PRB number for priority guarantee allocation is determined by the resource allocation ratio rRMPolicyMinRatio that needs to be preferentially guaranteed for each slice user group and the preset maximum supported PRB number in the system uplink.

9. The method according to claim 2, wherein The resource allocation for each slice user group according to the isolation resource parameter includes: When the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum supported PRB number in the system uplink, then the isolation resource parameter of each slice user group in all slice user groups is adjusted to obtain the adjusted isolation resource parameter; According to the adjusted isolation resource parameter, resource allocation is performed for each slice user group.

10. A resource allocation method, applied to a network node, characterized in that, Including: Sending downlink control information DCI for uplink scheduling to the user equipment UE. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used for resource allocation for the slice user group corresponding to the slice user group information; Receiving the data sent by the UE according to the slice user group information.

11. A resource allocation method, applied to a UE, characterized in that, Including: Receiving downlink control information DCI for uplink scheduling sent by the network node. The DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used for resource allocation for the slice user group corresponding to the slice user group information; Determine the resources allocated by the network node to the slice user group according to the slice user group information; Send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

12. A resource allocation device, applied to a network node, characterized in that It includes a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; The processor is used to read the computer programs in the memory and perform the following operations: Obtain the media access control protocol data unit MAC PDU and the number of scheduled allocated physical resource blocks PRBs for each slice user group; Determine the average actual occupied PRB number of the uplink of each slice user group according to the MAC PDU; Determine the average scheduled allocated resources of the uplink of each slice user group according to the scheduled allocated PRB number; Determine the isolation resource parameter of each slice user group according to the average actual occupied PRB number of the uplink and / or the average scheduled allocated resources of the uplink; Perform resource allocation for each slice user group according to the isolation resource parameter.

13. The device according to claim 12, characterized in that, The obtaining of the MAC PDU and the number of scheduled allocated PRBs for each slice user group includes: Obtain the MAC PDU and the number of scheduled allocated PRBs for each slice user group within at least one preset statistical period.

14. The device according to claim 13, characterized in that, The determining of the average actual occupied PRB number of the uplink of each slice user group according to the MAC PDU includes: Determine the number of PRBs actually occupied by the logical channel corresponding to each slice user group according to the MAC PDU; Determine the instantaneous uplink actual occupied PRB number of each slice user group according to the number of PRBs actually occupied by the logical channel and the uplink time slots included in each statistical period of the at least one statistical period, where the instantaneous uplink actual occupied PRB number is the instantaneous uplink actual occupied resource; Determine the average actual occupied PRB number of the uplink of each slice user group through smoothing filtering processing according to the instantaneous uplink actual occupied PRB number.

15. The device according to claim 13, wherein The determining of the average scheduled allocated resources of the uplink of each slice user group according to the scheduled allocated PRB number includes: Determine the average scheduled allocated resources of the uplink of each slice user group according to the scheduled allocated PRB number and the uplink time slots included in each statistical period of the at least one statistical period; The determining of the average scheduled allocated resources of the uplink of each slice user group according to the scheduled allocated PRB number and the uplink time slots included in each statistical period of the at least one statistical period includes: Determine the instantaneous uplink scheduled allocated PRB number according to the scheduled allocated PRB number and the uplink time slots included in each statistical period, where the instantaneous uplink scheduled allocated PRB number is the instantaneous uplink scheduled allocated resource; Determine the average scheduled allocated resources of the uplink of each slice user group through smoothing filtering processing according to the instantaneous uplink scheduled allocated PRB number, where the average scheduled allocated resources of the uplink is the average actual scheduled allocated PRB number.

16. The device according to claim 13, wherein The uplink average scheduling allocation resources include the uplink average actual scheduling allocation PRB quantity. Determining the isolation resource parameter of each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocation resources includes: When the uplink average actual occupied PRB quantity is less than the pre-configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduling allocation PRB quantity is greater than the pre-configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre-configured PRB quantity for priority guarantee allocation, increase the pre-configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameter.

17. The device according to claim 13, characterized in that Determining the isolation resource parameter of each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocation resources includes: When the uplink average actual occupied PRB quantity is not less than the pre-configured PRB quantity for priority guarantee allocation, then according to the uplink average actual occupied PRB quantity and the pre-configured PRB quantity for priority guarantee allocation, decrease the pre-configured PRB quantity for priority guarantee allocation to obtain the isolation resource parameter.

18. The device according to claim 13, characterized in that The uplink average scheduling allocation resources include the uplink average actual scheduling allocation PRB quantity. Determining the isolation resource parameter of each slice user group according to the uplink average actual occupied PRB quantity and / or the uplink average scheduling allocation resources includes: When the uplink average actual occupied PRB quantity is less than the pre-configured PRB quantity for priority guarantee allocation, and the uplink average actual scheduling allocation PRB quantity is not greater than the pre-configured PRB quantity for priority guarantee allocation, then determine the pre-configured PRB quantity for priority guarantee allocation as the isolation resource parameter of each slice user group.

19. The device according to any one of claims 16 - 18, characterized in that, The pre-configured PRB quantity for priority guarantee allocation is determined by the required priority guarantee allocation resource ratio rRMPolicyMinRatio of each slice user group and the preset maximum supported PRB quantity of the system uplink.

20. The device according to claim 13, characterized in that Performing resource allocation for each slice user group according to the isolation resource parameter includes: When the sum of the isolation resource parameters of all slice user groups is greater than the preset maximum supported PRB quantity of the system uplink, then adjust the isolation resource parameter of each slice user group in all slice user groups to obtain the adjusted isolation resource parameter; Perform resource allocation for each slice user group according to the adjusted isolation resource parameter.

21. A resource allocation device, applied to a network node, characterized in that Including a memory, a transceiver, and a processor: The memory is used to store a computer program; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Send downlink control information DCI for uplink scheduling to user equipment UE, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information; Receive data sent by the UE according to the slice user group information.

22. A resource allocation device, applied to a UE, characterized in that, Comprising a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Receive downlink control information DCI for uplink scheduling sent by a network node, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information; Determine the resources allocated by the network node to the slice user group according to the slice user group information; Send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

23. A resource allocation device, applied to a network node, characterized in that, Comprising: A first processing unit, configured to obtain a media access control protocol data unit MAC PDU and the number of scheduled allocated physical resource blocks PRBs of each slice user group; A second processing unit, configured to determine the average actual occupied PRB number of the uplink of each slice user group according to the MAC PDU; A third processing unit, configured to determine the average scheduled allocated resources of the uplink of each slice user group according to the scheduled allocated PRB number; A fourth processing unit, configured to determine the isolation resource parameter of each slice user group according to the average actual occupied PRB number of the uplink and / or the average scheduled allocated resources of the uplink; A fifth processing unit, configured to allocate resources to each slice user group according to the isolation resource parameter.

24. A resource allocation device, applied to a network node, characterized in that Comprising: A sixth processing unit, configured to send downlink control information DCI for uplink scheduling to user equipment UE, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information; A seventh processing unit, configured to receive data sent by the UE according to the slice user group information.

25. A resource allocation device, applied to a UE, characterized in that, Comprising: An eighth processing unit, configured to receive downlink control information DCI for uplink scheduling sent by a network node, where the DCI includes scheduling authorization information, and the scheduling authorization information includes slice user group information, and the slice user group information is used to allocate resources to the slice user group corresponding to the slice user group information; A ninth processing unit, configured to determine the resources allocated by the network node to the slice user group according to the slice user group information; A tenth processing unit, configured to send data to the network node in the logical channel corresponding to the slice user group according to the resources of the slice user group.

26. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to execute the method according to any one of claims 1 to 11.

Citation Information

Patent Citations

  • Method for initial access using signatures

    CN108886819A