CN114900896A

CN114900896A - Resource allocation method and device

Info

Publication number: CN114900896A
Application number: CN202210531514.4A
Authority: CN
Inventors: 耿超
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2022-05-13
Filing date: 2022-05-13
Publication date: 2022-08-12

Abstract

The application provides a resource allocation method and a device, wherein the resource allocation method comprises the following steps: determining terminal equipment of resources to be allocated, wherein the terminal equipment at least comprises first type terminal equipment and second type terminal equipment; determining the expected quantity of resources required by each terminal device; and based on the estimated resource quantity, allocating resources to each terminal device according to a Type0 resource allocation mode.

Description

Resource allocation method and device

Technical Field

The present application relates to wireless communication technologies, and in particular, to a method and an apparatus for resource allocation.

Background

With the pursuit of speed, delay, high speed mobility, energy efficiency, and the diversity and complexity of services in future life, the 3GPP international standards organization has begun to develop a fifth Generation Mobile Communication Technology (5th Generation Mobile Communication Technology, 5G). The main application scenarios of 5G include Low Latency high reliability Communications (URLLC); therefore, how to reduce the transmission delay is a constantly pursued goal in the field of wireless communication technology.

Disclosure of Invention

The embodiment of the application provides a resource allocation method and device, which can reduce transmission delay.

The technical scheme of the embodiment of the application is realized as follows:

in a first aspect, an embodiment of the present application provides a resource allocation method, including: determining terminal equipment of resources to be allocated, wherein the terminal equipment at least comprises first type terminal equipment and second type terminal equipment;

determining the expected quantity of resources required by each terminal device;

and based on the estimated resource quantity, allocating resources to each terminal device according to a Type0 resource allocation mode.

In some optional embodiments, the determining the expected number of resources required by each of the terminal devices includes:

and determining the expected resource quantity required by each terminal device based on the quantity of the allocable resources, the service type corresponding to each terminal device and the quantity of the terminal devices of the resources to be allocated.

In some optional embodiments, before allocating resources to each of the terminal devices according to Type0 resource allocation based on the predicted number of resources, the method further includes:

determining a service quality parameter corresponding to the service type corresponding to each terminal device;

and sequencing all the terminal devices based on the service quality parameters corresponding to the service types corresponding to the terminal devices.

In some optional embodiments, the quality of service parameter comprises at least one of:

priority, resource type, and packet data delay budget.

In some optional embodiments, said allocating resources for each of said terminal devices according to a Type0 resource allocation manner based on said predicted number of resources includes:

and according to the sequencing results of all the terminal devices, sequentially allocating resources matched with the predicted resource quantity corresponding to the terminal device to each terminal device according to a Type0 resource allocation mode.

In some optional embodiments, the allocating resources to each terminal device according to the Type0 resource allocation manner includes:

allocating resources with continuous predicted resource quantity corresponding to the terminal equipment to each terminal equipment;

or allocating the resources with the distributed expected resource quantity corresponding to the terminal equipment to each terminal equipment.

In a second aspect, an embodiment of the present application provides a resource allocation apparatus, including:

the system comprises a first determining module, a second determining module and a resource allocating module, wherein the first determining module is used for determining terminal equipment of resources to be allocated, and the terminal equipment at least comprises first type terminal equipment and second type terminal equipment;

a second determining module, configured to determine an expected number of resources required by each terminal device;

and the resource allocation module is used for allocating resources to each terminal device according to the Type0 resource allocation mode based on the estimated number of resources.

In some optional embodiments, the second determining module is configured to determine an expected number of resources required by each terminal device based on the number of allocable resources, the service type corresponding to each terminal device, and the number of terminal devices to which resources are to be allocated.

In some optional embodiments, the second determining module is further configured to determine a quality of service parameter corresponding to a service type corresponding to each terminal device;

priority, resource type, and packet data delay budget.

In some optional embodiments, the resource allocation module is specifically configured to, according to the sorting results of all the terminal devices, sequentially allocate, according to a Type0 resource allocation manner, to each terminal device, resources that are matched with the expected number of resources corresponding to the terminal device.

In some optional embodiments, the resource allocation module is configured to allocate, to each terminal device, resources whose expected number of resources corresponding to the terminal device is continuous;

In a third aspect, an embodiment of the present application provides an electronic device, including:

a memory for storing executable instructions;

and the processor is used for realizing the resource allocation method provided by the embodiment of the application when the processor executes the executable instructions stored in the memory.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores executable instructions for implementing the resource allocation method provided in the embodiment of the present application when executed by a processor.

The resource allocation method provided by the embodiment of the application determines terminal equipment of resources to be allocated, wherein the terminal equipment at least comprises first type terminal equipment and second type terminal equipment; determining the expected quantity of resources required by each terminal device; and based on the estimated resource quantity, allocating resources to each terminal device according to a Type0 resource allocation mode. Therefore, resources can be allocated to all terminal equipment only by once resource allocation; the secondary resource allocation generated when the resource is allocated to the second Type terminal equipment (the terminal equipment in the network slice) according to the Type1 resource allocation mode is avoided, the cycle consumption in one TTI can be reduced, the system time delay is further reduced, and the efficiency of resource scheduling is improved.

Drawings

FIG. 1 is a schematic diagram of a resource pool of a 5G system including a sliced user group and a non-sliced user group;

FIG. 2 is a flowchart illustrating a process of allocating resources to a sliced user and a non-sliced user according to a Type1 resource allocation manner;

FIG. 3 is a schematic diagram of a Type1 resource allocation manner provided in an embodiment of the present application;

fig. 4 is a schematic flowchart of an alternative resource allocation method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a Type0 resource allocation manner provided in an embodiment of the present application;

fig. 6 is a schematic diagram of an alternative processing flow for sorting terminal devices according to an embodiment of the present application;

fig. 7 is a detailed alternative flowchart of a resource allocation method provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a resource allocation apparatus according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an application system provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

In the following description, references to the terms "first \ second \ third" are only to distinguish similar objects and do not denote a particular order, but rather the terms "first \ second \ third" are used to interchange specific orders or sequences, where appropriate, so as to enable the embodiments of the application described herein to be practiced in other than the order shown or described herein. In the following description, the term "plurality" referred to means at least two.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

Before the embodiments of the present application are described in detail, the resource pool of the 5G system is briefly described.

In the related art, a schematic diagram of resource pools of a 5G system including a slice user group and a non-slice user group is shown in fig. 1, and includes a dedicated resource pool and a priority resource pool corresponding to the slice user group, and a shared resource pool shared by the slice user group and the non-slice user group. If the slicing user group comprises: slice user group 1 and slice user group 2; the resource pools of the 5G system include a dedicated resource pool of the slice user group 1, a priority resource pool of the slice user group 1, a dedicated resource pool of the slice user group 2, a priority resource pool of the slice user group 2, and a shared resource pool common to the slice user group 1, the slice user group 2, and the non-slice user group. Wherein, users in the slicing user group transmit data through the slicing network; users within a non-slicing group of users transmit data over a normal network (which may also be referred to as a non-slicing network).

And if the user groups comprise a slicing user group and a non-slicing user group, allocating resources for all users according to a Type1 resource allocation mode. Specifically, resources in each Resource pool are configured by configuring a dedicated Resource pool of a slice user group, a priority Resource pool of the slice user group, and the number of Resource Blocks (RBs) in a shared Resource pool shared by the slice user group and a non-slice user group; when configuring the resources in each resource pool, the actual starting position and the key position of the RB are not configured, and the number of RBs configured for each resource pool may be modified in the configuration table.

As shown in fig. 2, the process flow of allocating resources to a slice user and a non-slice user according to a Type1 resource allocation manner includes:

step S101, judging whether the service is a network slicing service.

Specifically, if the determination result is yes, step S102 is executed; if not, the resources are distributed according to the resource distribution mode of the non-slice network.

If the service is a network slicing service, representing that the user corresponding to the service belongs to a slicing user group.

Step S102, distributing the resources in the special resource pool of the user corresponding to the service for the network slice service.

Step S103, determining whether the resource in the dedicated resource pool can carry the data stream corresponding to the network slicing service.

Specifically, if the determination result is negative, step S104 is executed. If yes, go to step S104'.

Step S104', the number of the remaining resources in the resource pool is updated.

Step S104, distributing the resources in the priority resource pool of the user corresponding to the service for the network slice service.

Step S105, determining whether the resources in the dedicated resource pool and the resources in the priority resource pool can carry the data stream corresponding to the network slicing service.

Specifically, if the determination result is negative, step S106 is executed. If yes, go to step S104'.

And step S106, distributing the resources in the shared resource pool for the network slicing service and the non-network slicing service.

Specifically, according to the priority of the network slicing user corresponding to the network slicing service and the priority of the non-network slicing user corresponding to the non-network slicing service, resources in the shared resource pool are allocated to the network slicing service and the non-network slicing service.

Step S107, judging whether the resources allocated for the network slicing service can bear the data flow corresponding to the network slicing service.

Specifically, if the determination result is negative, step S108 is executed. If yes, go to step S104'.

And step S108, distributing the residual resources with lower priority to the network slice service.

Specifically, if there are no remaining resources, the process is ended.

It should be noted that resources are allocated to the network slicing service, which may also be referred to as allocating resources to terminal devices or slicing users corresponding to the network slicing service; and allocating resources for the non-network slicing service, which can also be referred to as allocating resources for terminal equipment or non-slicing users corresponding to the non-network slicing service.

The resource allocation scheme shown in fig. 2 is to allocate resources to services according to Type1 resource allocation. In the schematic diagram of Type1 Resource allocation manner, as shown in fig. 3, the resources allocated according to the Type1 Resource allocation manner are always continuous Virtual Resource Blocks (VRBs). If the resources allocated for the network slice service for the first time through steps S101 to S105 are not enough to schedule the data of the network slice service, the resources need to be further allocated for the network slice service for the second time through step S106. The applicant finds that when the resource is allocated for the second time, shared resources required by the remaining data to be scheduled in the network slicing service may be occupied by the non-network slicing service, so that the data scheduled by the slicing service is smaller. In addition, in a Transmission Time Interval (TTI), the secondary resource allocation for the network slice service occupies a long period (cycle), which increases the Time delay of the system, resulting in a reduction in the processing capability of the system.

The embodiment of the application provides a resource allocation method and device, which can reduce the time delay of a system and improve the processing capacity of the system.

The following describes a resource allocation method provided in an embodiment of the present application in detail.

Referring to fig. 4, fig. 4 is an alternative flowchart of a resource allocation method provided in an embodiment of the present application, which will be described with reference to the steps shown in fig. 4.

Step S201, determining terminal equipment of resources to be allocated, wherein the terminal equipment at least comprises first type terminal equipment and second type terminal equipment.

In some embodiments, there may be multiple users for one communication network, such as a 5G network, with each user corresponding to one terminal device. The terminal device may include at least two types, a first type and a second type. The first type terminal device may be a terminal device in a common network, and the second type terminal device may be a terminal device in a network slice; alternatively, the second type terminal device may be a terminal device in a normal network, and the first type terminal device may be a terminal device in a network slice. Network slicing is a networking on demand manner, and enables an operator to separate a plurality of virtual end-to-end networks on a unified infrastructure.

In some embodiments, the terminal device having the data transmission requirement is a terminal device to which resources are to be allocated, and the resources allocated to the terminal device are used for scheduling or transmitting data. Or the terminal device with the service to be executed is the terminal device to which the resource is to be allocated, and the resource allocated to the terminal device is used for scheduling or transmitting the data of the service to be executed.

Step S202, determining the expected resource quantity required by each terminal device.

In some embodiments, the expected number of resources required by each terminal device may be determined based on the number of allocable resources, the traffic type corresponding to each terminal device, and the number of terminal devices to which resources are to be allocated.

In specific implementation, the service type corresponding to each terminal device to which resources are to be allocated and the number of resources required by each service type can be determined; and determining the expected resource quantity required by each terminal device according to the total number of the allocable resources and the determined quantity of the resources required by all the service types.

As an example, if the number of the terminal devices to be allocated with resources is 8, the service type corresponding to each terminal device is a sending request message, and the number of the candidate resources corresponding to each terminal device is determined to be 2 RBs. If the total number of allocable resources is 16 RBs, it can be determined that the expected number of resources required for each terminal device is 2 RBs. If the total number of allocable resources is 9 RBs, it may be determined that the predicted number of resources required by 7 terminal devices of 8 terminal devices is 1 RB, respectively, and the predicted number of resources required by 1 terminal device of 8 terminal devices is 2 RBs. In particular implementations, allocable resources may all be allocated to the terminal device.

And step S203, based on the predicted resource quantity, allocating resources to each terminal device according to the Type0 resource allocation mode.

In some embodiments, as shown in fig. 5, the positions of allocable resources may be centralized and continuous, or may be distributed; the terminal equipment can be flexibly allocated with continuous resources or scattered resources according to needs.

In some embodiments, the terminal devices to be allocated with resources may be sorted, and the resources matching the predicted number of resources corresponding to the terminal devices are sequentially allocated to each terminal device according to the sorting result of the terminal devices and the Type0 resource allocation manner. The sequencing result of the terminal equipment is characterized by the priority of the resource distributed by the terminal equipment; as an example, the resources are allocated to the terminal devices in the forward order of the sorting results of the terminal devices, or the resources are allocated to the terminal devices in the reverse order of the sorting results of the terminal devices.

In some embodiments, an optional process flow for ordering terminal devices, as shown in fig. 6, includes at least the following steps:

step S301, determining a quality of service parameter corresponding to the service type corresponding to each terminal device.

In some embodiments, the Quality of Service (QoS) parameter comprises at least one of: priority, resource type, and packet data delay budget.

In some embodiments, for a 5G network, the characteristics of QoS may be determined according to 5 QI.

Step S302, based on the service quality parameter corresponding to the service type corresponding to each terminal device, all terminal devices are sequenced.

In some embodiments, all terminal devices may be ordered according to the priority of the quality of service parameters; as an example, if the priority of the quality of service parameter corresponding to the terminal device is high, the resource is preferentially allocated to the terminal device. Wherein the priority of the quality of service parameter may be determined by 5QI, or by the priority of the logical channel.

In some embodiments, allocating resources to each of the terminal devices according to the Type0 resource allocation manner includes: allocating resources with continuous predicted resource quantity corresponding to the terminal equipment to each terminal equipment; or allocating the resources with the distributed expected resource quantity corresponding to the terminal equipment to each terminal equipment. Taking fig. 5 as an example, if the number of frequency domain resources required by the terminal device is 4 RBs, 4 consecutive RBs with frequency domain positions of 6-9 may be allocated to the terminal device, or 4 scattered RBs with frequency domain positions of 0-1 and 14-15 may be allocated to the terminal device.

As shown in fig. 7, a detailed optional flowchart of the resource allocation method provided in the embodiment of the present application at least includes the following steps:

step S401, determining a terminal device to be allocated with resources at a starting time of a TTI.

In some embodiments, terminal devices to be allocated resources may be added to the scheduling queue.

Step S402, determining the expected resource quantity required by each terminal device to be allocated with resources.

In some embodiments, the process of determining the expected number of resources required by each terminal device to be allocated with resources is the same as step S202, and is not described herein again.

And S403, sequencing the terminal devices, traversing the terminal devices according to the sequencing result of the terminal devices, and allocating resources to each terminal device according to the Type0 resource allocation mode.

In some embodiments, the process of sequencing the terminal devices is the same as the process of sequencing the terminal devices shown in fig. 6, and is not described herein again.

In the embodiment of the application, when the terminal devices are sequenced, the terminal devices are not sequenced according to the types of the terminal devices (whether the terminal devices are the terminal devices in the network slice), but sequenced according to the service quality parameters corresponding to the service types corresponding to the terminal devices; therefore, the resources can be allocated to the terminal equipment according to the actual needs of the service.

It should be noted that, in this embodiment of the present application, allocating resources for a service may also be referred to as allocating resources for a terminal device providing the service, and may also be referred to as allocating resources for a user corresponding to the terminal device.

In the embodiment of the application, when the resources are allocated to the first type terminal equipment and the second type terminal equipment, the resources can be allocated to all the terminal equipment only by once resource allocation; the secondary resource allocation generated when the resource is allocated to the second Type terminal equipment (the terminal equipment in the network slice) according to the Type1 resource allocation mode is avoided, the cycle consumption in one TTI can be reduced, the system time delay is further reduced, and the efficiency of resource scheduling is improved.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

An embodiment of the present application further provides a resource allocation apparatus, where a schematic structural diagram of the resource allocation apparatus is shown in fig. 8, and the resource allocation apparatus includes:

a first determining module 501, configured to determine terminal devices to be allocated with resources, where the terminal devices at least include a first type terminal device and a second type terminal device;

a second determining module 502, configured to determine an expected number of resources required by each terminal device;

a resource allocation module 503, configured to allocate resources to each terminal device according to a Type0 resource allocation manner based on the estimated number of resources.

In some optional embodiments, the second determining module 502 is configured to determine an expected number of resources required by each of the terminal devices based on the number of allocable resources, the service type corresponding to each of the terminal devices, and the number of terminal devices to which the resources are to be allocated.

In some optional embodiments, the second determining module 502 is further configured to determine a quality of service parameter corresponding to a service type corresponding to each terminal device;

priority, resource type, and packet data delay budget.

In some optional embodiments, the resource allocation module 503 is specifically configured to, according to the sorting results of all the terminal devices, sequentially allocate, according to a Type0 resource allocation manner, a resource that matches the expected resource quantity corresponding to the terminal device to each of the terminal devices.

In some optional embodiments, the resource allocation module 503 is configured to allocate, to each terminal device, resources whose expected number of resources corresponding to the terminal device is continuous;

It should be noted that the resource allocation method provided in the present application may be implemented by a network device, and specifically, may be implemented by a Media Access Control (MAC) unit in the network device. Correspondingly, the resource allocation apparatus provided in the embodiment of the present application may be a network device.

In the embodiment of the present application, the terminal device may be any terminal, for example, the terminal device may be a user equipment for machine type communication. That is, the terminal equipment may also be referred to as user equipment UE, Mobile Station (MS), mobile terminal (mobile terminal), terminal (terminal), etc., and the terminal equipment may communicate with one or more core networks via a Radio Access Network (RAN), for example, the terminal equipment may be a mobile phone (or referred to as a "cellular" phone), a computer with a mobile terminal, etc., and the terminal equipment may also be a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device that exchanges language and/or data with the RAN, for example. The embodiments of the present application are not particularly limited.

Optionally, the network device and the terminal device may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons and satellite vehicles. The embodiment of the application does not limit the application scenarios of the network device and the terminal device.

Optionally, the network device and the terminal device may communicate via a licensed spectrum (licensed spectrum), may communicate via an unlicensed spectrum (unlicensed spectrum), and may communicate via both the licensed spectrum and the unlicensed spectrum. The network device and the terminal device may communicate with each other through a frequency spectrum of less than 7 gigahertz (GHz), may communicate through a frequency spectrum of more than 7GHz, and may communicate using both a frequency spectrum of less than 7GHz and a frequency spectrum of more than 7 GHz. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

Generally, conventional communication systems support a limited number of connections and are easy to implement, however, with the development of communication technology, mobile communication systems will support not only conventional communication, but also, for example, device to device (D2D) communication, machine to machine (M2M) communication, Machine Type Communication (MTC), and vehicle to vehicle (V2V) communication, and the embodiments of the present application can also be applied to these communication systems.

Illustratively, the embodiment of the present application is applied to a communication system 100, as shown in fig. 9. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 9 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 9 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the resource allocation method described in the embodiment of the present application.

Embodiments of the present application provide a computer-readable storage medium storing executable instructions, which when executed by a processor, will cause the processor to perform the method provided by embodiments of the present application, for example, the resource allocation method as shown in fig. 3 to 7.

In some embodiments, the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

In some embodiments, executable instructions may be written in any form of programming language (including compiled or interpreted languages), in the form of programs, software modules, scripts or code, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

By way of example, executable instructions may correspond, but do not necessarily have to correspond, to files in a file system, and may be stored in a portion of a file that holds other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

By way of example, executable instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.

Fig. 10 shows a schematic block diagram of an electronic device 800 (e.g., a network device) that may be used to implement the resource allocation methods of the present disclosure. In some alternative embodiments, the electronic device 800 may implement the resource allocation method provided by the embodiments of the present application by running a computer program, for example, the computer program may be a native program or a software module in an operating system; may be a local (Native) application program (APP), i.e. a program that needs to be installed in an operating system to run; or may be an applet, i.e. a program that can be run only by downloading it to the browser environment; but also an applet that can be embedded into any APP. In general, the computer programs described above may be any form of application, module or plug-in.

As shown in fig. 10, the electronic device 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic apparatus 800 can also be stored. The calculation unit 801, the ROM802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the electronic device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, or the like; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, or the like; and a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the electronic device 800 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

Computing unit 801 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and the like. The calculation unit 801 executes the respective methods and processes described above, such as the resource allocation method. For example, in some alternative embodiments, the resource allocation method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 808. In some alternative embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 800 via the ROM802 and/or the communication unit 809. When the computer program is loaded into RAM 803 and executed by computing unit 801, one or more steps of the resource allocation methods described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured as a resource allocation method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the resource allocation methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The above description is only an example of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method of resource allocation, the method comprising:

determining terminal equipment of resources to be allocated, wherein the terminal equipment at least comprises first type terminal equipment and second type terminal equipment;

2. The method of claim 1, wherein said determining an expected number of resources required by each of said terminal devices comprises:

3. The method of claim 1, wherein prior to allocating resources for each of the terminal devices in a Type0 resource allocation based on the predicted number of resources, the method further comprises:

4. The method of claim 3, the quality of service parameters comprising at least one of:

priority, resource type, and packet data delay budget.

5. The method of claim 3, wherein the allocating resources for each of the terminal devices according to Type0 resource allocation based on the predicted number of resources comprises:

6. The method of claim 1, wherein the allocating resources to each terminal device according to the Type0 resource allocation manner comprises:

7. A resource allocation apparatus, the resource allocation apparatus comprising:

8. The apparatus according to claim 7, wherein the second determining module is configured to determine the expected number of resources required by each terminal device based on the number of allocable resources, the traffic type corresponding to each terminal device, and the number of terminal devices to which resources are to be allocated.

9. The apparatus of claim 7, wherein the second determining module is further configured to determine a quality of service parameter corresponding to a service type corresponding to each terminal device;

10. The apparatus of claim 7, the resource allocation module is configured to allocate, for each terminal device, resources whose expected number of resources corresponding to the terminal device is continuous;