Resource allocation method, communication device, communication system, storage medium, and program product

Abstract

Disclosed in the present application are a resource allocation method, a communication device, a communication system, a storage medium, and a program product. The method comprises: receiving first information sent by a network device, wherein the first information is used for determining a resource allocation mode corresponding to a terminal, the resource allocation mode comprising at least one of the following: a resource allocation mode based on sub-physical resource blocks (sub-PRBs), a resource allocation mode based on resource blocks (RBs), and a resource allocation mode with dynamic switching. By means of introducing a resource allocation mechanism based on sub-PRBs (i.e., parts of a physical resource block), a terminal can flexibly request and utilize smaller resource units on the basis of actual requirements, which not only reduces the complexity of terminal design, but also increases uplink transmission capacity, thereby improving system communication efficiency and overall performance.

Description

Resource allocation methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This application relates to the field of communication technology, and in particular to resource allocation methods, communication equipment, communication systems, storage media, and program products. Background Technology

[0002] In non-terrestrial networks (NTNs), to address the challenges of limited frequency band resources, low data rate transmission, and increased user numbers due to wide coverage, uplink capacity enhancement is considered to serve more users simultaneously. However, related technologies may increase the implementation complexity of terminals when implementing uplink capacity enhancement. Summary of the Invention

[0003] This application provides resource allocation methods, communication devices, communication systems, storage media, and program products.

[0004] The first aspect of this application proposes a resource allocation method, which is executed by a terminal, and the method includes:

[0005] Receive first information sent by the network device, the first information being used to determine the resource allocation method corresponding to the terminal;

[0006] The resource allocation method includes at least one of the following:

[0007] Resource allocation based on sub-PRB (sub-physical resource block);

[0008] Resource allocation method based on resource blocks (RB);

[0009] Dynamically switching resource allocation methods.

[0010] A second aspect of this application provides a resource allocation method, which is executed by a network device, and the method includes:

[0011] Send first information to the terminal, the first information being used to determine the resource allocation method corresponding to the terminal;

[0012] The resource allocation method includes at least one of the following:

[0013] Resource allocation based on sub-PRB (sub-physical resource block);

[0014] Resource allocation method based on resource blocks (RB);

[0015] Dynamically switching resource allocation methods.

[0016] A third aspect of this application provides a terminal, the terminal comprising:

[0017] The transceiver module is used to receive first information sent by the network device, wherein the first information is used to determine the resource allocation method corresponding to the terminal;

[0018] The resource allocation method includes at least one of the following:

[0019] Resource allocation based on sub-PRB (sub-physical resource block);

[0020] Resource allocation method based on resource blocks (RB);

[0021] Dynamically switching resource allocation methods.

[0022] A fourth aspect of this application provides a network device, which includes:

[0023] The transceiver module is used to send first information to the terminal, wherein the first information is used to determine the resource allocation method corresponding to the terminal;

[0024] The resource allocation method includes at least one of the following:

[0025] Resource allocation based on sub-PRB (sub-physical resource block);

[0026] Resource allocation method based on resource blocks (RB);

[0027] Dynamically switching resource allocation methods.

[0028] The solution proposed in this application receives first information sent by a network device, which is used to determine the resource allocation method corresponding to the terminal. The resource allocation method includes at least one of the following: a resource allocation method based on a sub-Physical Resource Block (sub-PRB); a resource allocation method based on a Resource Block (RB); and a dynamically switched resource allocation method. By introducing a sub-PRB (sub-Physical Resource Block) resource allocation mechanism, the terminal can flexibly request and use smaller resource units according to actual needs, which not only simplifies the complexity of terminal design but also enhances the uplink transmission capacity and improves system communication efficiency and overall performance. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments or background art of this application, the following description of the accompanying drawings is provided. The following drawings are merely some embodiments of this application and do not impose specific limitations on the scope of protection of this application.

[0030] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0031] Figure 1B is a schematic diagram of an orthogonal overlay code multiplexing transmission scheme based on pre-discrete Fourier transform;

[0032] Figure 2A is an interactive schematic diagram of a resource allocation method provided in an embodiment of this application;

[0033] Figure 3A is an interactive schematic diagram of a resource allocation method provided in an embodiment of this application;

[0034] Figure 3B is a schematic diagram of dynamic switching of resource allocation methods provided in an embodiment of this application;

[0035] Figures 3C-3D are interactive schematic diagrams of a resource allocation method provided in an embodiment of this application;

[0036] Figure 4A is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0037] Figure 4B is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0038] Figure 5A is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0039] Figure 5B is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0040] This application provides resource allocation methods, communication devices, communication systems, storage media, and program products.

[0041] In a first aspect, embodiments of this application propose a resource allocation method, the method comprising:

[0042] Receive first information sent by the network device, wherein the first information is used to determine the resource allocation method corresponding to the terminal;

[0043] The above resource allocation methods include at least one of the following:

[0044] Resource allocation based on sub-PRB (sub-physical resource block);

[0045] Resource allocation method based on resource blocks (RB);

[0046] Dynamically switching resource allocation methods.

[0047] In the above embodiments, by introducing a sub-PRB (i.e., a part of a physical resource block) resource allocation mechanism, the terminal can flexibly request and use smaller resource units according to actual needs, which not only simplifies the complexity of terminal design, but also enhances the uplink transmission capacity and improves system communication efficiency and overall performance.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the above-described resource allocation method based on sub-PRB uses the resource unit (RE) as the basic resource granularity;

[0049] The above-mentioned RB-based resource allocation method uses RB as the basic resource granularity.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the above-described sub-PRB-based resource allocation method includes at least one of the following:

[0051] Resource allocation based on RE;

[0052] Resource allocation methods based on RB and RE.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0054] Send a second message to the aforementioned network device, the second message being used to indicate the capabilities of the aforementioned terminal.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the capabilities of the aforementioned terminal include at least one of the following:

[0056] The above terminals support partial bandwidth BWP configurations;

[0057] The resource granularity and resource allocation methods supported by the above terminals;

[0058] Does the aforementioned terminal support resource allocation based on frequency domain reference points, wherein the aforementioned frequency domain resource reference points are used to determine the starting frequency domain position of the aforementioned resources allocated to the aforementioned terminal?

[0059] The size of the resource allocation unit supported by the above terminals;

[0060] The spectrum bandwidth supported by the aforementioned terminals;

[0061] The maximum number of Physical Resource Blocks (PRBs) supported by the aforementioned terminals.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the resource allocation unit includes Q REs, where Q is a positive integer.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned first information is Radio Resource Control (RRC) signaling.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used to determine the resource allocation method based on sub-PRB corresponding to the terminal; the method further includes:

[0065] The third information sent by the aforementioned network device is received, and the third information is used to determine the resource allocation type corresponding to the aforementioned terminal.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments,

[0067] The aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the BWP, wherein the resource allocation unit is allocated continuously or discretely;

[0068] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the aforementioned at least one RB, wherein the resource allocation unit is allocated continuously or discretely.

[0069] The aforementioned third information is used to indicate the starting RE of the resources allocated to the aforementioned terminal on the BWP, as well as the length of the aforementioned resources;

[0070] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the starting RE of the resource allocated to the aforementioned terminal on the aforementioned at least one RB, as well as the length of the aforementioned resource.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the above-mentioned terminal supports dynamically switching resource allocation methods;

[0072] The first information mentioned above is RRC signaling, which is used to configure the resource allocation method of the terminal.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal supports dynamically switching resource allocation methods; the method further includes:

[0074] Receive RRC signaling sent by the aforementioned network device, the aforementioned RRC signaling being used to configure the resource allocation method corresponding to the aforementioned terminal;

[0075] Based on the aforementioned first piece of information, the resource allocation method is switched.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0077] Receive RRC signaling sent by the aforementioned network device, the aforementioned RRC signaling being used to configure the resource allocation method corresponding to the aforementioned terminal;

[0078] The resource allocation method determined by the first piece of information is different from the resource allocation method configured by the RRC signaling.

[0079] The resource allocation method corresponding to the above terminals is determined to be the resource allocation method configured in the above RRC signaling.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, the first information mentioned above includes a field for indicating the resource allocation method;

[0081] Different resource allocation methods correspond to different values ​​of the aforementioned first piece of information;

[0082] Different resource allocation methods correspond to different scrambled radio network temporary identifiers (RNTIs).

[0083] Different resource allocation methods correspond to different demodulation reference signal DMRS patterns or DMRS sequences.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the size of the aforementioned first information differs for different resource allocation methods; the method further includes:

[0085] The target resource allocation method is determined based on the magnitude of one of the primary pieces of information.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments, the resources allocated to the aforementioned terminal are used for at least one of the following channels or signals:

[0087] Downlink channel or downlink signal;

[0088] Uplink channel or uplink signal;

[0089] Control channel;

[0090] Data channel.

[0091] Secondly, embodiments of this application propose a resource allocation method, the method comprising:

[0092] Send first information to the terminal, wherein the first information is used to determine the resource allocation method corresponding to the terminal;

[0093] The above resource allocation methods include at least one of the following:

[0094] Resource allocation based on sub-PRB (sub-physical resource block);

[0095] Resource allocation method based on resource blocks (RB);

[0096] Dynamically switching resource allocation methods.

[0097] In the above embodiments, by introducing a sub-PRB (i.e., a part of a physical resource block) resource allocation mechanism, the terminal can flexibly request and use smaller resource units according to actual needs, which not only simplifies the complexity of terminal design, but also enhances the uplink transmission capacity and improves system communication efficiency and overall performance.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the above-described resource allocation method based on sub-PRB uses the resource unit (RE) as the basic resource granularity;

[0099] The above-mentioned RB-based resource allocation method uses RB as the basic resource granularity.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, the above-described resource allocation method based on sub-PRB includes at least one of the following:

[0101] Resource allocation based on RE;

[0102] Resource allocation methods based on RB and RE.

[0103] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0104] The second information sent by the aforementioned terminal is received, and the second information is used to indicate the capabilities of the aforementioned terminal.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, the capabilities of the aforementioned terminal include at least one of the following:

[0106] The above terminals support partial bandwidth BWP configurations;

[0107] The resource granularity and resource allocation methods supported by the above terminals;

[0108] Does the aforementioned terminal support resource allocation based on frequency domain reference points, wherein the aforementioned frequency domain resource reference points are used to determine the starting frequency domain position of the aforementioned resources allocated to the aforementioned terminal?

[0109] The size of the resource allocation unit supported by the above terminals;

[0110] The spectrum bandwidth supported by the aforementioned terminals;

[0111] The maximum number of Physical Resource Blocks (PRBs) supported by the aforementioned terminals.

[0112] In conjunction with some embodiments of the second aspect, in some embodiments, the resource allocation unit mentioned above includes Q REs, where Q is a positive integer.

[0113] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned first information is Radio Resource Control (RRC) signaling.

[0114] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used to determine the resource allocation method based on sub-PRB corresponding to the terminal; the method further includes:

[0115] Send third information to the aforementioned terminal, the third information being used to determine the resource allocation type corresponding to the aforementioned terminal.

[0116] In conjunction with some embodiments of the second aspect, in some embodiments, the above-mentioned resource allocation type includes at least one of the following:

[0117] The aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the BWP, wherein the resource allocation unit is allocated continuously or discretely;

[0118] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the aforementioned at least one RB, wherein the resource allocation unit is allocated continuously or discretely.

[0119] The aforementioned third information is used to indicate the starting RE of the resources allocated to the aforementioned terminal on the BWP, as well as the length of the aforementioned resources;

[0120] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the starting RE of the resource allocated to the aforementioned terminal on the aforementioned at least one RB, as well as the length of the aforementioned resource.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the above-mentioned terminal supports dynamically switching resource allocation methods;

[0122] The first information mentioned above is RRC signaling, which is used to configure the resource allocation method of the terminal.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal supports dynamically switching resource allocation methods; the terminal is used to switch the resource allocation method based on the parsing of the first information.

[0124] The above methods also include:

[0125] Send RRC signaling to the aforementioned terminal. The RRC signaling is used to configure the resource allocation method corresponding to the aforementioned terminal.

[0126] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal supports dynamically switching resource allocation methods; the terminal is used to switch the resource allocation method based on the parsing of the first information.

[0127] The above methods also include:

[0128] Send RRC signaling to the aforementioned terminal. The RRC signaling is used to configure the resource allocation method corresponding to the aforementioned terminal.

[0129] In conjunction with some embodiments of the second aspect, in some embodiments, the size of the first information corresponding to different resource allocation methods is different; the terminal is used to parse the received first information based on the size of one of the first information types.

[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the resources allocated to the aforementioned terminal are used for at least one of the following channels or signals:

[0131] Downlink channel or downlink signal;

[0132] Uplink channel or uplink signal;

[0133] Control channel;

[0134] Data channel.

[0135] Thirdly, embodiments of this application propose a terminal, which includes a transceiver module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0136] Fourthly, embodiments of this application propose a network device, which includes a transceiver module; wherein the first network element is used to execute the second aspect and the optional implementation of the second aspect.

[0137] Fifthly, embodiments of this application propose a terminal, which includes one or more processors; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0138] In a sixth aspect, embodiments of this application provide a network device comprising: one or more processors; wherein the network device is configured to execute the second aspect and optional implementations thereof.

[0139] In a seventh aspect, embodiments of this application provide a communication device for executing the first aspect and optional implementations of the first aspect, as well as the second aspect and optional implementations of the second aspect.

[0140] Eighthly, embodiments of this application propose a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the network device is configured to perform the method described in the second aspect and optional implementations thereof.

[0141] Ninthly, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0142] In a tenth aspect, embodiments of this application provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the first aspect and its optional implementation, the second aspect and its optional implementation.

[0143] In one aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its optional implementations, the second aspect and its optional implementations.

[0144] In a twelfth aspect, embodiments of this application provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.

[0145] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, and program products are all used to execute the methods proposed in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0146] This application provides resource allocation methods, communication devices, communication systems, storage media, and program products. In some embodiments, the terms resource allocation method, communication method, information processing method, and data processing method can be used interchangeably.

[0147] The embodiments in this application are not exhaustive, but merely illustrative of some embodiments, and are not intended to limit the scope of protection of this application. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In the embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0148] The terminology used in the embodiments of this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application.

[0149] In the embodiments of this application, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun after the article can be understood as either a singular expression or a plural expression.

[0150] In the embodiments of this application, "multiple" refers to two or more.

[0151] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0152] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0153] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0154] The prefixes "first," "second," etc., used in the embodiments of this application are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0155] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0156] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0157] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0158] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0159] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0160] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0161] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0162] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0163] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, various embodiments of this application can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0164] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0165] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0166] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0167] Furthermore, each element, each row, or each column in the table of this application embodiment can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0168] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of this application.

[0169] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a core network device 102.

[0170] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, narrowband Internet of Things (NB-IoT) device, satellite communication device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and red-capped terminal, but is not limited thereto.

[0171] In some embodiments, the core network device 102 may be a single device, including a first network element 1021, a second network element 1022, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1021, the second network element 1022, etc. Network elements may be virtual or physical. The core network may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC).

[0172] In some embodiments, the first network element 1021 is, for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a User Plane Function (UPF).

[0173] In some embodiments, the first network element 1021 is used for "terminal access management and mobility management", "terminal authentication, authorization and registration management", "processing user service sessions", "forwarding and processing service data", etc., and the name is not limited to these.

[0174] In some embodiments, the second network element 1022 is, for example, a Subscription Management Function (SMF) or a Unified Data Management (UDM).

[0175] In some embodiments, the second network element 1022 is used for "storing and managing user subscription data", "participating in user authentication and authorization", etc., and the name is not limited to these.

[0176] In some embodiments, the communication system 100 may further include access network equipment, wherein the access network equipment is, for example, a node or device that connects a terminal to a wireless network. The network equipment may include, but is not limited to, at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a next-generation RAN node (NG-RAN node), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a radio backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system.

[0177] In some embodiments, the technical solutions of this application can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this application can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0178] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0179] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions proposed in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this application are also applicable to similar technical problems.

[0180] The following embodiments of this application can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0181] The embodiments of this application can be applied to Non-terrestrial Networks (NTN), Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0182] In some embodiments, the Physical Downlink Shared Channel (PDSCH) supports two allocation methods in the frequency domain: Type 0 and Type 1, and supports both dynamic and static configuration. Dynamic configuration is indicated by Downlink Control Information (DCI), while static configuration is indicated by the resourceAllocation parameter in the Information Element (IE) pdsch-Config (PDSCH configuration).

[0183] When `resourceAllocation` is set to 'resourceAllocationType0', it indicates that downlink frequency domain resource allocation uses scheme Type 0; when it is set to 'resourceAllocationType1', it indicates that downlink frequency domain resource allocation uses scheme Type 1. When the value is 'dynamicSwitch', it means that the frequency domain resource allocation method is controlled by DCI, following the instructions below:

[0184] For DCI format 1_0, 4_0 or 4_1 scheduling of PDSCH, use downlink resource allocation type 1.

[0185] When scheduling PDSCH for DCI Format1_1, the pdsch-Config higher-level parameter resourceAllocation is set to 'dynamicSwitch'; for DCI Format1_2, the pdsch-Config higher-level parameter resourceAllocationDCI-1-2 is set to 'dynamicSwitch'; for DCI Format1_3, the pdsch-Config higher-level parameter resourceAllocationDCI-1-3 is set to 'dynamicSwitch'; and for DCI Format4_2, the pdsch-ConfigMulticast higher-level parameter resourceAllocation is set to 'dynamicSwitch'. Downlink resource frequency domain allocation uses type0 / type1 allocation mode, specifically according to the DCI field definition.

[0186] If the (Bandwidth Part, BWP) indicator field is not configured in the scheduling DCI, or if the UE does not support changing the active BWP by the DCI, then the RB index for downlink type 0 and type 1 resource allocation is determined within the UE's active BWP. If the BWP indicator field is configured in the scheduling DCI and the UE supports changing the active BWP by the DCI, then the (Resource Block, RB) index for downlink type 0 and type 1 resource allocation is determined within the UE's BWP, as indicated by the value of the BWP indicator field in the DCI. When the UE detects a Physical Downlink Control Channel (PDCCH) expected to be used for the UE, it first determines the downlink carrier BWP, and then determines the resource allocation within the BWP.

[0187] For a PDSCH scheduled by DCI format 1_0 in any type of PDCCH Common Search Space (CSS), regardless of which BWP is active, the RB numbering starts from the lowest RB of the receiving DCI CORESET (Control-resource set); otherwise, the RB numbering starts from the lowest RB in the determined downlink BWP.

[0188] In some embodiments, in type 0 downlink resource allocation, the Frequency Domain Resource Assignment (FDRA) is a bitmap indicating the RBGs allocated to the scheduled UE. In type 0, allocation is done at the granularity of RB Groups (RBGs). An RBG is a contiguous set of Virtual Resource Blocks (VRBs), and its size (P) is determined by the RRC configuration (Configuration 1 and Configuration 2) and the BWP bandwidth (Bandwidth Part Size), as shown in Table 1 below. Configuration 1 or Configuration 2 is indicated by the higher-layer parameter rbg-Size configured in PUSCH-Config (when scheduling DCI format 1_1 / 1_2) or the higher-layer parameter rbg-SizeDCI-1-3 configured in PUSCH-ConfigDCI-0-3 (when scheduling DCI format 1_3). If rbg-size / rbg-SizeDCI-1-3 is not configured, the default value is Configuration 1; BWP uses a bitmap to indicate which RBGs are allocated to the UE, with each RBG corresponding to 1 bit.

[0189] Type 0 supports both contiguous and non-contiguous resource allocation.

[0190] Table 1. Nominal RBG size P in downlink resource allocation

[0191] A size of The total number of RBGs (N) in the downlink BWP(i) of each PRB. RBG It can be expressed by the following formula:

[0192] in,

[0193] The size of the first RBG is

[0194] if The size of the last RBG is Otherwise, the size of the last RBG is P.

[0195] The size of all other remaining RBGs is P.

[0196] The size of the bitmap mentioned above is N. RBGEach bit in the bitmap corresponds to an RBG, making each RBG addressable. RBGs are indexed in ascending frequency order, starting from the lowest frequency in the bandwidth portion. The RBG bitmap is ordered from MSB to LSB, from RBG 0 to RBG N. RBG -1 mapping. If the value of the corresponding bit in the bitmap is 1, then RBG is assigned to the UE; otherwise, it is not assigned.

[0197] In some embodiments, in Type 1 downlink resource allocation, FDRA instructs the scheduled UE to allocate a set of consecutively allocated non-interleaved or non-interleaved VRBs within the active BWP, with a size of One PRB.

[0198] The resource allocation field consists of a RIV, the value of which corresponds to the starting VRB (RB). start ) and the number L of consecutively allocated RB RBs .

[0199] RIV is defined as follows:

[0200] if but,

[0201] otherwise,

[0202] Where L RBs ≥1 and should not exceed

[0203] This means that when the number of RBs allocated is less than half of the resources in the BWP, the RIV is calculated using equation ①; otherwise, equation ② is used to calculate the RIV.

[0204] When different DCI sizes occur, for example, DCI 1_0 in USS is derived from DCI 1_0 in CSS, its size is... However, the actual DCI size of the currently activated BWP is different from that of CSS; its size is... At this point, the previous RIV process needs to be scaled proportionally, with the scaling factor being K. The downlink Type 1 resource block allocation field consists of a field corresponding to the starting resource block. The length of the RIV and the RB in virtual contiguous allocation. composition.

[0205] In some embodiments, the Physical Uplink Shared Channel (PUSCH) supports three allocation methods in the frequency domain: Type 0, Type 1, and Type 2. The difference is that Type 0 only supports transformation precoding is disabled, while Type 1 and Type 2 support either transformation precoding being enabled or disabled. The specific transmission mode used is controlled by the PUSCH-Config high-level parameter `resourceAllocation`.

[0206] When `resourceAllocation` is set to 'resourceAllocationType0', it indicates that the uplink frequency domain resource allocation uses the Type 0 scheme; when it is set to 'resourceAllocationType1', it indicates that the uplink frequency domain resource allocation uses the Type 1 scheme. When the value is 'dynamicSwitch', it means that the frequency domain resource allocation method is controlled by DCI, following the instructions below:

[0207] 1) When scheduling PUSCH for DCI Format0_1, set the higher-level parameter resourceAllocation in pusch-Config to 'dynamicSwitch'; for DCI Format0_2, set the higher-level parameter resourceAllocationDCI-0-2 in pusch-Config to 'dynamicSwitch'; for DCI Format0_3, set the higher-level parameter resourceAllocationDCI-0-3 in pusch-Config to 'dynamicSwitch', and use Type0 / Type1 allocation mode for uplink resource frequency domain allocation.

[0208] When scheduling PUSCH for DCI format 0_1, set the BWP-UplinkDedicated higher-layer parameter useInterlacePUSCH-Dedicated to 'enabled', and use Type 2 allocation mode for uplink resource frequency domain allocation.

[0209] 3) When scheduling PUSCH for DCI format 0_0, the uplink resource frequency domain allocation uses the Type 1 allocation mode.

[0210] 4) For setting the higher-layer parameter useInterlacePUCCH-PUSCH of BWP-UplinkCommon or the higher-layer parameter useInterlacePUCCH-PUSCH of BWP-UplinkDedicated to 'enabled' (UE expects either neither to be configured, or both BWP-UplinkCommon and BWP-UplinkDedicated to be configured with useInterlacePUCCH-PUSCH), the uplink resource frequency domain allocation uses the Type 2 allocation mode.

[0211] In some embodiments, in Type 0 uplink resource allocation, the frequency domain resource assignment is a bitmap indicating the RBGs allocated to the scheduled UE. In Type 0, allocation is done at the RBG granularity. An RBG is a contiguous set of VRBs, and its size (P) is determined by the RRC configuration (Configuration 1 and Configuration 2) and the BWP bandwidth (Bandwidth Part Size), as shown in Table 2 below. Configuration 1 or Configuration 2 is indicated by the higher-layer parameter rbg-Size configured in PUSCH-Config (when scheduling in DCI format 0_1 / 0_2) or the higher-layer parameter rbg-SizeDCI-0-3 configured in PUSCH-ConfigDCI-0-3 (when scheduling in DCI format 0_3). If rbg-size / rbg-SizeDCI-0-3 is not configured, it defaults to Configuration 1; the BWP indicates which RBGs are allocated to the UE in a bitmap format, with each RBG corresponding to 1 bit.

[0212] Type 0 supports both contiguous and non-contiguous resource allocation.

[0213] Table 2 shows the RBG size P in the uplink resource allocation.

[0214] A size of The total number of RBGs (N) in the uplink BWP(i) of each PRB. RBG It can be expressed by the following formula:

[0215] in,

[0216] The size of the first RBG is

[0217] if The size of the last RBG is Otherwise, the size of the last RBG is P.

[0218] The size of all other remaining RBGs is P.

[0219] In some embodiments, in Type 1 uplink resource allocation, frequency domain resource assignment instructs the scheduled UE to allocate a set of consecutively distributed non-interleaved VRBs within the active BWP, with a size of PRBs.

[0220] An uplink Type 1 resource allocation field consists of a RIV, the value of which corresponds to the starting VRB (RB). start ) and the number L of consecutively allocated RB RBs .

[0221] RIV is defined as follows

[0222] if but,

[0223] otherwise,

[0224] Where L RBs ≥1 and should not exceed

[0225] This means that when the number of RBs allocated is less than half of the resources in the BWP, the RIV is calculated using equation ①; otherwise, equation ② is used to calculate the RIV.

[0226] When different DCI sizes occur, for example, DCI 1_0 in USS is derived from DCI 1_0 in CSS, its size is... However, the actual DCI size of the currently activated BWP is different from that of CSS; its size is... At this point, the previous RIV process needs to be scaled proportionally, with the scaling factor being K. The downlink Type 1 resource block allocation field consists of a field corresponding to the starting resource block. The length of the RIV and the RB in virtual contiguous allocation. composition.

[0227] When different DCI sizes occur, for example, DCI 0_0 in USS is derived from DCI 0_0 in CSS, its size is... However, the actual DCI size of the currently activated BWP is different from that of CSS; its size is... At this point, the previous RIV process needs to be scaled proportionally, with the scaling factor being K. The uplink Type 1 resource block allocation field consists of a field corresponding to the starting resource block. The length of the RIV and the RB in virtual contiguous allocation. composition.

[0228] RIV is defined as follows:

[0229] if but,

[0230] otherwise,

[0231] in, And L′ RBs It should not exceed

[0232] if, K is a set {1, 2, 4, 8} that satisfies The maximum value; otherwise K = 1.

[0233] For DCI format 0_2 or 0_3 scheduling, the uplink type 1 resource allocation field consists of the RIV corresponding to the starting resource block group RBGstart = 0, 1, ..., NRBG-1 and the length LRBGs = 1, ..., NRBG in units of virtual contiguous allocation of RBGs, where the resource block group is defined according to 6.1.2.2.1, and P is indicated by the higher-layer parameter resourceAllocationType1GranularityDCI-0-2 (for DCI format 0_2 scheduling) or resourceAllocationType1GranularityDCI-0-3 (for DCI format 0_3 scheduling) (if the UE is configured with these parameters); otherwise, P = 1.

[0234] That is, RBGs are first grouped according to type 0, and then the starting RBG index and the length of the allocated consecutive RBGs are represented by type 1 RIV to allocate resources.

[0235] RIV is defined as follows:

[0236] if Then, RIV = N RBG (L RBGs -1)+RBGstart ;

[0237] Otherwise, RIV = N RBG (N RBG -L RBGs +1)+(N RBG -1-RBG start ).

[0238] Where L RBGs ≥1 and should not exceed N RBG -RBG start .

[0239] In some embodiments, Type 1 only supports continuous resource allocation.

[0240] In some embodiments, in type 2 uplink resource allocation, frequency domain resource assignment indicates a maximum of M interlace indices for the UE. For DCI format 0_0 monitored in a UE-specific search space and DCI formats 0_1, 0_3, it indicates a maximum of... RB sets.

[0241] In non-terrestrial networks (NTNs), uplink capacity enhancement is considered for the following reasons in order to serve more users simultaneously:

[0242] 1. Limited frequency band resources are available for NTN networks;

[0243] 2. NTN networks primarily transmit data at low rates, resulting in smaller data packets and payloads, and thus requiring fewer resources.

[0244] 3. Satellite coverage typically covers a larger cell radius, and the number of users within a single cell is greater than that of a terrestrial network (TN).

[0245] In some embodiments, an uplink capacity enhancement is achieved using a transmission scheme based on pre-Discrete Fourier Transform (pre-DFT) Orthogonal Cover Code (OCC) multiplexing, as shown in Figure 1B. This scheme enables multiple UEs to share a single resource block (RB), allowing more UEs to access the network and thus enhancing uplink capacity. However, this scheme requires OOC spreading of modulation symbols and multiplexing of OOC sequences at the terminal transmitter, making the processing flow complex and consequently increasing the complexity of the terminal design.

[0246] To reduce terminal design complexity while enhancing uplink capacity, a sub-PRB resource allocation scheme can be considered in some embodiments. This scheme is particularly suitable for low data rate transmission scenarios because the transport block (TB) size is relatively small in these scenarios, so resource allocation based on sub-PRB has little impact on transmission integrity.

[0247] The resource allocation method, communication equipment, communication system, storage medium, and program products provided in this application will be described in detail below with reference to the accompanying drawings.

[0248] Figure 2A is an interactive schematic diagram of a resource allocation method according to an embodiment of this application. As shown in Figure 2A, this application embodiment relates to a resource allocation method, which includes:

[0249] In step S2101, terminal 101 sends the second information.

[0250] In some embodiments, network device 102 receives the second information sent by terminal 101.

[0251] In some embodiments, the second information described above is used to indicate the capabilities of the terminal.

[0252] Optionally, the aforementioned terminal capability (UE capability) can be a mandatory capability (i.e., a capability that the terminal must support and report) or an optional capability (i.e., a capability that the terminal supports but does not need to report). The terminal 101 can choose whether to report these capabilities to the network device 102.

[0253] In some embodiments, the capabilities of the aforementioned terminal include at least one of the following:

[0254] The above terminals support partial bandwidth BWP configurations;

[0255] The resource granularity and resource allocation methods supported by the above terminals;

[0256] Does the aforementioned terminal support resource allocation based on frequency domain reference points, wherein the aforementioned frequency domain resource reference points are used to determine the starting frequency domain position of the aforementioned resources allocated to the aforementioned terminal?

[0257] The size of the resource allocation unit supported by the above terminals;

[0258] The spectrum bandwidth supported by the aforementioned terminals;

[0259] The maximum number of Physical Resource Blocks (PRBs) supported by the aforementioned terminals.

[0260] In some embodiments, the resource granularity and resource allocation methods supported by the above-mentioned terminal include at least one of the following:

[0261] The resource granularity supported by the above terminals is the resource element (RE), and the resource allocation method supported by the above terminals is the RE-level resource allocation method based on sub-PRB.

[0262] The resource granularity supported by the above-mentioned terminal is RE, and the resource allocation method supported by the above-mentioned terminal is RB+RE-level resource allocation method based on sub-PRB. In the resource allocation process, RB-level resource allocation is performed first, and then RE-level resource allocation is performed.

[0263] The resource granularity supported by the above-mentioned terminals is RB, and the resource allocation method supported by the above-mentioned terminals is RB-level resource allocation method based on RB.

[0264] Optionally, if terminal 101 supports sub-PRB resource allocation, terminal 101 also needs to indicate to network device 102 whether it supports different resource allocation methods under sub-PRB resource allocation.

[0265] Normally, the default frequency domain reference point for resource allocation is RB#0 and RE#0 of a portion of the bandwidth (BWP). In some embodiments, the above-mentioned frequency domain resource reference point may be specified in the following ways, including but not limited to: RE#0 of the frequency domain starting point Point A CRB0, or RE#0 within a certain RB, etc.

[0266] It should be noted that the starting position of the allocated frequency domain resources is based on the offset of the frequency domain reference point mentioned above, and this offset must ensure that the allocated frequency domain resources are contained within the BWP.

[0267] In some embodiments, the resource allocation unit includes Q REs, where Q is a positive integer.

[0268] Optionally, for the design of resource units in sub-PRBs, RE can be considered as a basic granularity, with Q*RE as a RE unit, where Q is a positive integer, and Q can be a protocol preset or a network device configuration.

[0269] In some embodiments, the name of the second information is not limited, and it may be, for example, "capability reporting request", "terminal capability reporting request", etc.

[0270] In step S2102, network device 102 sends the first information.

[0271] In some embodiments, terminal 101 receives the first information sent by network device 102.

[0272] In some embodiments, the first information is used to determine the resource allocation method corresponding to the terminal.

[0273] In some embodiments, the above resource allocation method includes at least one of the following:

[0274] Resource allocation based on sub-PRB (sub-physical resource block);

[0275] Resource allocation method based on resource blocks (RB);

[0276] Dynamically switching resource allocation methods.

[0277] In some embodiments, the resource allocation method based on sub-PRB uses resource units (REs) as the basic resource granularity; the resource allocation method based on RB uses RBs as the basic resource granularity.

[0278] In some embodiments, resource allocation based on sub-PRB includes at least one of the following:

[0279] Resource allocation based on RE;

[0280] Resource allocation methods based on RB and RE.

[0281] In some embodiments, the first information mentioned above is Radio Resource Control (RRC) signaling.

[0282] Optionally, the following resource allocation method can be configured via Radio Resource Control (RRC) higher-layer signaling:

[0283] RRCresourceUnit::=ENUMERATED{RBresourceAllocation, sub-PRBresourceAllocation, dynamicSwitch}

[0284] Among them, RBresourceAllocation is a frequency domain resource allocation method based on RB-level resource allocation, which is configured by the corresponding network device B according to different channels or determined by the protocol preset; sub-PRBresourceAllocation is a sub-PRB-based RE-level resource allocation method or a sub-PRB-based RB+RE-level resource allocation method; dynamicSwitch indicates that it can dynamically switch between sub-PRB-based resource allocation method and RB-based resource allocation method.

[0285] Optionally, after the RRC signaling or network device has indicated or configured a resource allocation method based on sub-PRB, the following resource allocation method based on sub-PRB can be configured via RRC higher-layer signaling:

[0286] sub-PRBresourceAllocation::=ENUMERATED{sub-PRBresourceAllocationtypeA, sub-PRBresourceAllocationtypeB, sub-PRBresourceAllocationtypeC}

[0287] Among them, sub-PRBresourceAllocationtypeA, sub-PRBresourceAllocationtypeB, and sub-PRBresourceAllocationtypeC are three different resource allocation methods based on sub-PRB.

[0288] In some embodiments, the first information mentioned above may also be downlink control information (DCI) or other downlink signaling.

[0289] In some embodiments, the resources allocated to the aforementioned terminal are used for at least one of the following channels or signals:

[0290] Downlink channel or downlink signal;

[0291] Uplink channel or uplink signal;

[0292] Control channel;

[0293] Data channel.

[0294] In some embodiments, the name of the first information is not limited, and may be, for example, “resource allocation request”, “resource allocation method request”, “resource allocation”, “resource allocation method”, “sub-PRB resource allocation”, “RB resource allocation”, “frequency domain resource allocation”, “frequency domain resource allocation method”, etc.

[0295] In step S2103, network device 102 sends third information.

[0296] In some embodiments, terminal 101 receives the aforementioned third information sent by network device 102.

[0297] In some embodiments, the third information is used to determine the resource allocation type corresponding to the terminal.

[0298] In some embodiments, the first information is used to determine the resource allocation method based on sub-PRB corresponding to the terminal. The network device 102 may also send third information to the terminal 101 to determine the resource allocation type corresponding to the terminal 101.

[0299] In the embodiments of this application, the above-mentioned resource allocation type refers to the types included in the resource allocation method based on sub-PRB.

[0300] It is understood that the resource allocation methods described in the embodiments of this application are classified based on the basic granularity of resource allocation, and may include resource allocation methods based on sub-PRB, resource allocation methods based on RB, and dynamically switching resource allocation methods, etc. The aforementioned resource allocation types are classified based on specific allocation methods under a basic granularity of resource allocation. For example, resource allocation may be performed by indicating discrete or continuous resource allocation units, or by indicating the starting frequency domain position and length of the resource for continuous allocation, etc.

[0301] In some embodiments, the RB-based resource allocation method includes two resource allocation types: type0 and type1.

[0302] In some embodiments, the resource allocation method based on sub-PRB may include at least one of the four resource allocation types type A to type D.

[0303] In some embodiments, the above resource allocation types include at least one of the following:

[0304] The aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the BWP, wherein the resource allocation unit is allocated continuously or discretely;

[0305] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the resource allocation unit allocated to the aforementioned terminal on the aforementioned at least one RB, wherein the resource allocation unit is allocated continuously or discretely.

[0306] The aforementioned third information is used to indicate the starting RE of the resources allocated to the aforementioned terminal on the BWP, as well as the length of the aforementioned resources;

[0307] The aforementioned third information is used to indicate at least one RB allocated to the aforementioned terminal on the BWP, and the aforementioned third information is used to indicate the starting RE of the resource allocated to the aforementioned terminal on the aforementioned at least one RB, as well as the length of the aforementioned resource.

[0308] Optionally, after RRC signaling or network devices have indicated or configured resource allocation methods based on sub-PRB, it may be considered to indicate different resource allocation types through third-party information.

[0309] In some embodiments, the aforementioned third information is downlink control information (DCI) signaling.

[0310] Alternatively, different resource allocation types can be indicated through the Frequency domain resource allocation field in the DCI signaling.

[0311] In some embodiments, the frequency domain resource allocation field in DCI signaling directly indicates RE-level resource allocation. That is, the frequency domain resource allocation field in DCI signaling does not allocate resources in units of traditional PRB (Physical Resource Block), but is refined directly to the RE (Resource Unit) level.

[0312] Optionally, the above resource allocation type can be denoted as typeA.

[0313] Optionally, sub-PRBs can be allocated discretely or continuously on the BWP using a REG bitmap. That is, sub-PRBs (resource blocks smaller than a full PRB) can be allocated discretely or continuously within the BWP using a method called a REG bitmap. Here, a REG is a set of REs, representing the smallest unit of resource allocation. This set can contain one or more REs. The size and number of REGs are determined by the size of the BWP and its starting position in the spectrum. The frequency domain resource allocation field in DCI signaling is actually an indicator of a bitmap. Each bit in this bitmap corresponds to a REG. If a bit is set to 1, it means that the corresponding REG has been allocated to the UE; if a bit is set to 0, it means that the corresponding REG has not been allocated to the UE. In other words, by parsing this bitmap in the DCI signaling, the UE can know which REGs (and the REs they contain) have been allocated to it, thus enabling it to perform corresponding data transmission or reception operations. This RE-level resource allocation method makes resource utilization more flexible and efficient.

[0314] In this approach, the bit overhead of the "Frequency domain resource assignment" field in DCI is calculated as follows:

[0315] The REresource unit size is Q (in RE), and for each size... The BWP (unit: RE) has a total of REGs: If 1 bit is allocated to each RE for allocation status indication, then the bit overhead occupied by the "Frequency domain resource assignment" field in the DCI is:

[0316] Taking a BWP width of 100 RBs as an example, the bit overhead is calculated as follows: Q = 12, the total number of REGs is 100 * 12 / 12 = 100, the total bit overhead of FDRA is B_DCI = 100, the additional bits m = 2, and the total bit overhead = 100 + 100 * 2 = 300.

[0317] In some embodiments, the frequency domain resource allocation field in the DCI signaling first provides resource allocation indication based on Resource Blocks (RBs), and then provides resource allocation indication based on Sub-PRBs. That is, the frequency domain resource allocation field in the DCI signaling adopts a hierarchical resource allocation strategy: First, it provides resource allocation indication based on RBs (resource blocks), determining which RBs will be allocated to the UE. Subsequently, within these allocated RB resources, the DCI further provides resource allocation indication based on Sub-PRBs (i.e., resource blocks smaller than a full PRB).

[0318] Optionally, the above resource allocation type can be denoted as typeB.

[0319] Optionally, sub-PRBs are allocated discretely or continuously on allocated RB-level resources using a REG bitmap. That is, sub-PRBs (resource blocks smaller than a full PRB) can be allocated discretely or continuously on allocated RB-level resources using a method called a REG bitmap. A REG is a set of one or more resource elements (REs), representing the smallest unit of resource allocation. The size and number of REGs are determined by the starting position and length of the allocated RB resources. The frequency domain resource allocation field in DCI signaling is actually an indicator of a bitmap. Each bit in this bitmap corresponds to a REG. If a bit is set to 1, it indicates that the corresponding REG has been allocated to the UE (User Equipment); if a bit is set to 0, it indicates that the corresponding REG has not been allocated to the UE. In other words, by using the frequency domain resource allocation field in the DCI signaling, it is first determined which RB resources will be allocated to the UE. Then, within these RB resources, the resource allocation is further refined through the REG bitmap, clarifying which REGs (and the REs they contain) are allocated to the UE, thereby achieving flexible and efficient resource utilization.

[0320] In this approach, when the RB-based resource allocation indication scheme is type 0, the bit overhead of the "Frequency domain resource assignment" field in the DCI is calculated as follows:

[0321] Bit overhead of the RB-level "Frequency domain resource assignment" field in DCI:

[0322] The RB resource unit size is P×12 (unit: RE). For each size... The total number of BWPs (unit: RE) and RBGs is: If 1 bit is allocated to each RB for allocation status indication, then the bit overhead of the RB-level "Frequency domain resource assignment" field in the DCI is as follows:

[0323] Bit overhead of the RE-level "Frequency domain resource assignment" field in DCI:

[0324] The RE resource unit size is Q (in REs). For each RBG of size P×12, the total number of REGs is: If 1 bit is allocated to each RE for allocation status indication, then the bit overhead occupied by the RE-level "Frequency domain resource assignment" field in the DCI is:

[0325] RB-level total bit overhead: Assuming each RBG requires m1 additional bits to represent additional information such as modulation scheme, the total bit overhead is:

[0326] RE-level total bit overhead: Assuming each REG requires m² additional bits to represent additional information such as modulation scheme, then the total bit overhead is:

[0327] The RB-based resource allocation scheme can be type 0 or type 1, or it can simply indicate a starting RB position, with RE#0 of this RB as the reference point, and then perform resource allocation indication (REG) based on sub-PRB.

[0328] Taking a BWP width of 100 RBs as an example, the bit overhead is calculated as follows: P = 10, the total number of RBGs is 100 / 10 = 10, the total bit overhead of RB level FDRA is 10, Q = 12, the total number of REGs in one RBG is 10 * 12 / 12 = 10.

[0329] 1) Assuming that only one RBG is given a resource allocation instruction based on sub-PRB, then:

[0330] Sub-PRB level FDRA total bit cost = 10, additional bits m1 = m2 = 2, total bit cost = 10 + 2*10 + 10 + 2*10 = 60;

[0331] 2) Assuming that resource allocation instructions are based on sub-PRB for all RBGs, then:

[0332] The total bit cost of sub-PRB level FDRA is 10*10=100, with additional bits m1=m2=2, and the total bit cost is 10+2*10+10*10+2*10*10=330.

[0333] In some embodiments, the frequency domain resource allocation field in the DCI signaling directly indicates the location of the sub-PRB resource unit in the BWP. Alternatively, the location of the sub-PRB resource unit in the BWP can be indicated by a Resource Indication Value (RIV) that indicates the sub-PRB resource unit with RE as the smallest granularity in the uplink transmission, which includes the start position Start RE and the length of the RE unit.

[0334] Optionally, the above resource allocation type can be denoted as typeC.

[0335] The Start RE parameter identifies the starting position of the sub-PRB resource unit within the allocated RB resources. By specifying the Start RE, the UE can be precisely told which RE its uplink transmission should begin from. The RE unit length parameter specifies the number of REs covered by the sub-PRB resource unit. By specifying the length of the RE unit, the amount of data transmitted by the UE uplink can be controlled, thereby meeting different transmission requirements and quality of service requirements.

[0336] Optionally, Start RE can be specified in the following two ways:

[0337] Option 1: Start RE is the offset of RE#0 relative to the frequency domain starting point Point A CRB0;

[0338] Option 2: Start RE is the offset relative to a frequency domain reference point within a certain range, such as the offset relative to a certain RE within a certain RB.

[0339] Option 1 describes a global specification method: Start RE is defined as an offset relative to the entire frequency domain starting point (i.e., RE#0 of PointA CRB0). This means that regardless of the location of the sub-PRB resource unit in the BWP, its starting point can be uniquely determined by this global offset.

[0340] Option 2 offers a more localized specification method: Start RE is an offset relative to a frequency domain reference point within a specific range. This frequency domain reference point can be an RE within any RB within the BWP, the specific choice depending on the system design and actual requirements. This approach allows for more flexible specification of the starting position of sub-PRB resource units without altering the global frequency domain structure.

[0341] In summary, DCI provides precise indication of the location of sub-PRB resource units in BWP by offering Start RE and RIV of RE unit length, as well as flexible Start RE specification methods (global or local).

[0342] In this approach, the bit overhead of the "Frequency domain resource assignment" field in DCI is calculated as follows:

[0343] The total number of REs within BWP is:

[0344] The bit overhead of RIV for Start RE:

[0345] RIV for RE unit length L RE Bit overhead:

[0346] Assuming the total additional bits for information such as modulation scheme are m, then the total bit overhead is:

[0347] Taking a BWP width of 100 RBs as an example, the bit overhead is calculated as follows: Total number of REs = 100 * 12 = 1200, Bit overhead for Start RE = log2(1200) rounded up = 11, L_RE = 640, Bit overhead for L_RE = log2(640) rounded up = 10, Additional bits m = 100, Total bit overhead = 11 + 10 + 100 = 121.

[0348] In some embodiments, the frequency domain resource allocation field in the DCI signaling first provides resource allocation indication based on Resource Blocks (RBs), and then provides resource allocation indication based on Sub-PRBs. That is, the frequency domain resource allocation field in the DCI signaling adopts a hierarchical resource allocation strategy: First, it provides resource allocation indication based on RBs (resource blocks), determining which RBs will be allocated to the UE. Subsequently, within these allocated RB resources, the DCI further provides resource allocation indication based on Sub-PRBs (i.e., resource blocks smaller than a full PRB).

[0349] Optionally, the above resource allocation type can be denoted as typeD.

[0350] Optionally, the location of a sub-PRB resource unit on allocated RB-level resources is indicated by a RIV containing the start position (Start RE) and the RE unit length. That is, a sub-PRB (a resource block smaller than a full PRB) can be located on allocated RB-level resources via a RIV containing the start position (Start RE) and the RE unit length. Here, Start RE indicates the starting RE position of the sub-PRB resource unit within the allocated RB; the RE unit length indicates the number of REs contained in the sub-PRB resource unit. In other words, the frequency domain resource allocation field in DCI signaling first determines which RB resources the UE will be allocated to. Then, within these RB resources, the resource allocation is further refined using a RIV containing the start position (Start RE) and the RE unit length, clarifying on which specific REs the UE will perform uplink transmissions and the number of REs occupied by each transmission unit, thereby achieving flexible and efficient resource utilization.

[0351] Optionally, Start RE can be specified in the following two ways:

[0352] Opt.1Start RE is the offset of RE#0 relative to the frequency domain start point Point A CRB0;

[0353] Opt.2Start RE is the offset relative to a frequency domain reference point within a certain range, such as the offset relative to the starting position of a certain RBG, or the offset relative to RE#0 in the first RB within the BWP to perform frequency domain resource configuration.

[0354] In this approach, Start RE is the offset relative to RB#0RE#0 within the BWP. When the RB-based resource allocation indication scheme is type 1, the bit overhead of the "Frequency domain resource assignment" field in the DCI is calculated as follows:

[0355] Bit overhead of the RB-level "Frequency domain resource assignment" field in DCI:

[0356] The total number of RBs within BWP is:

[0357] RIV for Start RB position RB start Bit overhead:

[0358] RIV for RE unit length L RB Bit overhead:

[0359] Bit overhead of the RE-level "Frequency domain resource assignment" field in DCI:

[0360] The total number of REs within the allocated RB is: N RE =L RB ×12;

[0361] The bit overhead of RIV for Start RE:

[0362] RIV for RE unit length L RE Bit overhead:

[0363] Total bit overhead of RB-level: Assuming the total additional bits for additional information such as RB-level modulation scheme are m1, then the total bit overhead is:

[0364] RE-level total bit overhead: Assuming the total additional bits for RE-level modulation and other additional information is m2, then the total bit overhead is:

[0365] Among them, the resource allocation scheme based on RB can be type0 or type1, or it can simply indicate a starting RB position, with RE#0 of this RB as the reference point, and then perform resource allocation instructions based on sub-PRB.

[0366] Taking a BWP width of 100 RBs as an example, the bit overhead is calculated as follows: Total number of RBs = 100, bit overhead for Start RB = log2(100) rounded up = 7, L_RB = 64, bit overhead for L_RB = log2(64) rounded up = 6, total bit overhead for RB level FDRA = 7 + 6 = 13, total number of REs = 6 * 12 = 72, bit overhead for Start RE = log2(72) rounded up = 7, L_RE = 64, bit overhead for L_RE = log2(64) = 6, total bit overhead for sub-PRB level FDRA = 7 + 6 = 13, additional bits m1 = m2 = 100, total bit overhead = 13 + 100 + 13 + 100 = 226.

[0367] In some embodiments, the name of the aforementioned third information is not limited, and may be, for example, "resource allocation request", "resource allocation type request", etc.

[0368] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.

[0369] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

[0370] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0371] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0372] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0373] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0374] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0375] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0376] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0377] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0378] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0379] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0380] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0381] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0382] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0383] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0384] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0385] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0386] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0387] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0388] The resource allocation method involved in the embodiments of this application may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2101+S2102 may be implemented as an independent embodiment, step S2102+S2103 may be implemented as an independent embodiment, step S2101+S2103 may be implemented as an independent embodiment, step S2101+S2102+S2103 may be implemented as an independent embodiment, and so on, but not limited thereto.

[0389] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.

[0390] Figure 3A is an interactive schematic diagram illustrating a resource allocation method according to an embodiment of this application. As shown in Figure 3A, this application embodiment relates to a resource allocation method, which includes:

[0391] In step S3101, terminal 101 sends the second information.

[0392] The optional implementation of step S3101 can be found in the optional implementation of step S2102 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0393] In step S3102, network device 102 sends the first information.

[0394] In some embodiments, terminal 101 receives the first information sent by network device 102.

[0395] In some embodiments, the first information is used to determine the resource allocation method corresponding to the terminal.

[0396] In some embodiments, the above resource allocation method includes at least one of the following:

[0397] Resource allocation based on sub-PRB (sub-physical resource block);

[0398] Resource allocation method based on resource blocks (RB);

[0399] Dynamically switching resource allocation methods.

[0400] In some embodiments, the resource allocation method based on sub-PRB uses resource units (REs) as the basic resource granularity; the resource allocation method based on RB uses RBs as the basic resource granularity.

[0401] In some embodiments, resource allocation based on sub-PRB includes at least one of the following:

[0402] Resource allocation based on RE;

[0403] Resource allocation methods based on RB and RE.

[0404] In some embodiments, the first information mentioned above is Radio Resource Control (RRC) signaling.

[0405] Optionally, the following resource allocation method can be configured via Radio Resource Control (RRC) higher-layer signaling:

[0406] RRCresourceUnit::=ENUMERATED{RBresourceAllocation, sub-PRBresourceAllocation, dynamicSwitch}

[0407] Among them, RBresourceAllocation is a frequency domain resource allocation method based on RB-level resource allocation, which is configured by the corresponding network device B according to different channels or determined by the protocol preset; sub-PRBresourceAllocation is a sub-PRB-based RE-level resource allocation method or a sub-PRB-based RB+RE-level resource allocation method; dynamicSwitch indicates that it can dynamically switch between sub-PRB-based resource allocation method and RB-based resource allocation method.

[0408] Optionally, after the RRC signaling or network device has indicated or configured a resource allocation method based on sub-PRB, the following resource allocation method based on sub-PRB can be configured via RRC higher-layer signaling:

[0409] sub-PRBresourceAllocation::=ENUMERATED{sub-PRBresourceAllocationtypeA, sub-PRBresourceAllocationtypeB, sub-PRBresourceAllocationtypeC}

[0410] Among them, sub-PRBresourceAllocationtypeA, sub-PRBresourceAllocationtypeB, and sub-PRBresourceAllocationtypeC are three different resource allocation methods based on sub-PRB.

[0411] In some embodiments, the resources allocated to the aforementioned terminal are used for at least one of the following channels or signals:

[0412] Downlink channel or downlink signal;

[0413] Uplink channel or uplink signal;

[0414] Control channel;

[0415] Data channel.

[0416] In some embodiments, the name of the first information is not limited, and it may be, for example, "resource allocation request", "resource allocation method request", etc.

[0417] In some embodiments, terminal 101 supports dynamically switching resource allocation methods.

[0418] In some embodiments, the first information is RRC signaling, and the first information is used to configure the resource allocation method of the terminal.

[0419] In some embodiments, the resource allocation methods that support dynamic switching include, but are not limited to, the following:

[0420] Scenario 1: Configuration via RRC higher-level signaling only

[0421] 1) Configure different resource allocation methods via RRC higher-level signaling:

[0422] RRCresourceUnit::=ENUMERATED{RBresourceAllocation, sub-PRBresourceAllocation, dynamicSwitch}

[0423] The configuration of "dynamicSwitch" indicates that it can dynamically switch between sub-PRB-based resource allocation and RB-based resource allocation.

[0424] 2) When network device 102 is configured for sub-PRB-based resource allocation, the resource allocation unit is no longer a complete RB, but a more granular sub-PRB. Dynamic switching is achieved by allocating a resource unit to n*12 REs, where allocating a resource unit to n*12 REs is equivalent to allocating n RBs (each RB contains 12 REs), where n is a positive integer. n can be a predefined fixed value or flexibly configured by network device 102 based on network conditions and user needs.

[0425] This configuration approach offers high flexibility and adaptability, enabling it to meet resource allocation requirements under different business scenarios and user needs.

[0426] Scenario 2: Only through terminal signaling parsing or default configuration

[0427] 1) Network device 102 can use dynamic switching by default without any RRC configuration, which means it can dynamically switch between sub-PRB-based resource allocation and RB-based resource allocation.

[0428] 2) Network device 102 can switch dynamically without any RRC configuration, only through terminal signaling parsing.

[0429] Terminal 101's default RB-based resource allocation scheme capability is mandatory. Therefore, the prerequisite for switching to a sub-PRB-based resource allocation scheme is either: if the terminal capability is optional, the terminal has already reported this capability; or, the terminal defaults to a mandatory capability. That is, if terminal 101 has a default RB-based resource allocation scheme capability (mandatory), it can naturally support switching to a sub-PRB-based scheme without additional reporting. However, if the sub-PRB-based capability is optional, terminal 101 must have previously reported this capability for network device 102 to recognize and allow the switch. Alternatively, if terminal 101 defaults to considering this capability necessary (even if it may actually be optional, it is enabled by default for compatibility reasons), it can also support the switch.

[0430] This configuration method emphasizes the role of terminal 101 in the dynamic switching process of resource allocation. Through the capability report and signaling parsing of terminal 101, network device 102 can flexibly adjust the resource allocation strategy to adapt to different business needs and user scenarios.

[0431] Scenario 3: When RRC higher-level signaling is configured or sub-PRB is not configured, terminal signaling parsing or default configuration is used.

[0432] 1) Network device 102 performs RRC configuration and configures the resource allocation method to be based on sub-PRB through the higher-layer signaling RRCresourceUnit. It can also be dynamically switched through terminal signaling parsing. If network device 102 does not configure the resource allocation method to be based on sub-PRB, then resource allocation is performed based on RB.

[0433] That is, when network device 102 performs RRC configuration, it can explicitly specify the resource allocation method as sub-PRB-based resource allocation through higher-layer signaling RRC Resource Unit. However, even in this case, network device 102 still retains the possibility of dynamic switching through terminal signaling parsing. This means that even if network device 102 has been configured with sub-PRB-based resource allocation, it can still flexibly adjust to other resource allocation methods (such as RB-based resource allocation) based on terminal signaling feedback. If network device 102 does not configure the resource allocation method as sub-PRB-based in the RRC configuration, it will default to RB-based resource allocation.

[0434] 2) Network device 102 does not perform RRC configuration based on sub-PRB resource allocation method, and can also perform dynamic switching through terminal signaling parsing (prerequisites are the same as in case 2-2).

[0435] That is, even without relying on RRC configuration to configure the resource allocation method to be based on sub-PRB, network device 102 can still dynamically switch the resource allocation method by parsing terminal signaling. This switching requires that terminal 101 meet certain capability conditions:

[0436] If terminal 101 has a default RB-based resource allocation method (which is usually mandatory), then it can naturally support possible switching operations.

[0437] For resource allocation based on sub-PRB, if it is optional, terminal 101 must have previously reported this capability so that network device 102 can recognize it and allow the corresponding handover. Alternatively, if for compatibility reasons, terminal 101 assumes this capability is necessary by default (although it may actually be optional), then it can also support the handover operation.

[0438] This configuration method emphasizes the complementary roles of RRC configuration and terminal signaling parsing in the resource allocation scheme determination process, as well as the importance of terminal capabilities in dynamic handover decisions. It can flexibly adjust the resource allocation method to meet the resource allocation requirements under different business scenarios and user needs.

[0439] In some embodiments, network device 102 configures a resource allocation method (e.g., a sub-PRB-based resource allocation method or an RB-based resource allocation method) via RRC signaling. Simultaneously, network device 102 also sends first information, and the resource allocation method determined by the first information is different from the resource allocation method configured by the RRC signaling. Terminal 101 may not parse the first information, or in other words, terminal 101 ignores the first information. Terminal 101 determines that the corresponding frequency domain resource allocation method is the method configured by the RRC signaling, and then determines the corresponding frequency domain resources according to the resource allocation method configured by the RRC signaling.

[0440] Optionally, in the above embodiments, terminal 101 may support dynamically switched resource allocation methods, or terminal 101 may not support dynamically switched resource allocation methods.

[0441] The tree diagram summarizing the situations mentioned above is shown in Figure 3B.

[0442] In step S3103, network device 102 sends third information.

[0443] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0444] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0445] Figure 3C is an interactive schematic diagram illustrating a resource allocation method according to an embodiment of this application. As shown in Figure 3C, this application embodiment relates to a resource allocation method, which includes:

[0446] In step S3201, terminal 101 sends the second information.

[0447] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0448] In step S3202, network device 102 sends the first message.

[0449] The optional implementation of step S3201 can be found in step S2102 of Figure 2A, the optional implementation of step S3102 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0450] In step S3203, network device 102 sends third information.

[0451] The optional implementation of step S3203 can be found in the optional implementation of step S2103 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0452] In step S3204, terminal 101 determines the resource allocation method corresponding to the terminal based on the parsing of the first information.

[0453] In some embodiments, the terminal supports dynamically switching resource allocation methods.

[0454] In some embodiments, the first information includes a field for indicating the resource allocation method.

[0455] Different resource allocation methods correspond to different values ​​of the aforementioned first piece of information;

[0456] Different resource allocation methods correspond to different scrambled radio network temporary identifiers (RNTIs).

[0457] Different resource allocation methods correspond to different demodulation reference signal DMRS patterns or DMRS sequences.

[0458] In some embodiments, the terminal 101 supports dynamically switching resource allocation methods. When determining the resource allocation method corresponding to the terminal based on the parsing of the first information, since there are different switching situations, it is necessary to consider the distinction between different situations in order to determine the resource allocation method that is finally dynamically switched to.

[0459] Alternatively, the following methods can be used for differentiation:

[0460] 1) The aforementioned first information includes a field for indicating the aforementioned resource allocation method. Optionally, a 1-bit DCI indicator field may be reserved in the aforementioned first information. If this bit is set to 0, it indicates that the resource allocation method based on sub-PRB is used; if this bit is set to 1, it indicates that the resource allocation method based on RB is used; or, if this bit is set to 0, it indicates that the resource allocation method based on RB is used; if this bit is set to 1, it indicates that the resource allocation method based on sub-PRB is used.

[0461] 2) The size of the first information mentioned above differs depending on the resource allocation method. Optionally, assuming the first information is DCI signaling, different DCI sizes can be defined for different resource allocation methods. Terminal 101 distinguishes the resource allocation method used through blind DCI detection. For example, different DCI sizes can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the defined DCI size for RB-based resource allocation is smaller than the DCI size for sub-PRB-based resource allocation, the terminal will determine the smaller DCI size as the RB-based resource allocation method during blind detection; or, if the defined DCI size for RB-based resource allocation is larger than the DCI size for sub-PRB-based resource allocation, the terminal will determine the larger DCI size as the RB-based resource allocation method during blind detection.

[0462] 3) Different resource allocation methods correspond to different scrambled Radio Network Temporary Identifiers (RNTIs). Optionally, different scrambled RNTIs can be defined for different resource allocation methods, and the terminal 101 uses the RNTI to distinguish between different resource allocation methods during parsing. For example, different scrambled RNTIs can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the RNTI for RB-based resource allocation is defined as 'a' and the RNTI for sub-PRB-based resource allocation is defined as 'b', then when the terminal performs parsing, it can determine that RNTI = a is used for RB-based resource allocation, and RNTI = b is used for sub-PRB-based resource allocation.

[0463] 4) Different resource allocation methods correspond to different Demodulation Reference Signal (DMRS) patterns or DMRS sequences. Optionally, different DMRS patterns or sequences can be defined for different resource allocation methods. When the terminal 101 performs parsing, it distinguishes between different resource allocation methods using the DMRS pattern or sequence. For example, different DMRS patterns or sequences can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the DMRS pattern / sequence for RB-based resource allocation is defined as 'a' and the DMRS pattern / sequence for sub-PRB-based resource allocation is defined as 'b', then when the terminal performs parsing, it can determine that DMRS pattern / sequence = a is the RB-based resource allocation method and DMRS pattern / sequence = b is the sub-PRB-based resource allocation method.

[0464] In some embodiments, the size of the first information is different for different resource allocation methods, so the terminal 101 can parse the received first information based on the size of one of the first information.

[0465] In some embodiments, during the switching between different resource allocation methods using DCI (Downlink Control Information) dynamic signaling parsing, in order to reduce the increase in the number of blind detections caused by inconsistent DCI sizes (inconsistent DCI sizes may lead to a double number of blind detections), it is necessary to ensure the alignment of DCI bit lengths.

[0466] Alternatively, the following alignment method can be used:

[0467] Option 1: Alignment of Frequency Domain Resource Assignment (FDRA) Fields in DCI

[0468] 1) Align the FDRA field length to a given scheduling scheme:

[0469] If the length of the FDRA field in the resource allocation scheme based on sub-PRB / RB is less than the length of the FDRA field in the resource allocation scheme based on RB / sub-PRB, then padding with several 0 bits is added to a specific position (Most Significant Bit, MSB or Least Significant Bit, LSB) of the FDRA field in the sub-PRB / RB handover scheme until the two are equal. If the length of the FDRA field in the resource allocation scheme based on sub-PRB / RB is greater than the length of the FDRA field in the resource allocation scheme based on RB / sub-PRB, then several MSBs or LSBs of the FDRA field in the resource allocation scheme based on RB / sub-PRB are truncated until the two are equal.

[0470] That is, when a handover scheme is adopted, if its FDRA field length is shorter than that of another handover scheme, an appropriate number of zero padding bits are added to specific positions (MSB bits or LSB bits) of the FDRA field of the shorter scheme until the two lengths are the same. Conversely, if the FDRA field length of the current handover scheme is longer, the MSB bits or LSB bits of the FDRA field of the longer scheme need to be truncated until it matches the shorter scheme.

[0471] 2) Align with the length of the longer FDRA field:

[0472] If the FDRA field lengths of the resource allocation scheme based on sub-PRB / RB are not equal, then several 0 padding bits are added to a specific position (MSB bit or LSB bit) of the shorter FDRA field until the two lengths are equal.

[0473] 3) Align with shorter FDRA field lengths:

[0474] If the lengths of the FDRA fields scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then the MSB or LSB bits of several long FDRA fields are truncated until they are equal.

[0475] Option 2: DCI total length alignment

[0476] 1) Aligning the DCI length to a given scheme:

[0477] If the DCI length of the resource allocation scheme based on sub-PRB / RB is less than the DCI length of the resource allocation scheme based on RB / sub-PRB, then padding with several 0 bits at specific positions (MSB or LSB bits) of the DCI based on sub-PRB / RB is performed until the two are equal. If the DCI length of the resource allocation scheme based on sub-PRB / RB is greater than the DCI length of the resource allocation scheme based on RB / sub-PRB, then truncating several MSB or LSB bits of the DCI based on RB / sub-PRB is performed until the two are equal.

[0478] 2) Align with the longer DCI length:

[0479] If the DCI lengths scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then padding bits with 0s are added at specific positions (MSB bits or LSB bits) of the shorter DCI until the two lengths are equal.

[0480] 3) Align with shorter DCI lengths:

[0481] If the DCI lengths scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then truncate the MSB or LSB bits of several long DCIs until they are equal.

[0482] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0483] Figure 3D is an interactive schematic diagram illustrating a resource allocation method according to an embodiment of this application. As shown in Figure 3D, this application embodiment relates to a resource allocation method, which includes:

[0484] Step S3301: Terminal 101 sends the second information.

[0485] The optional implementation of step S3301 can be found in the optional implementation of step S2102 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0486] In step S3302, network device 102 sends the first message.

[0487] The optional implementation of step S3301 can be found in step S2102 of Figure 2A, the optional implementation of step S3102 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0488] In step S3303, network device 102 sends third information.

[0489] The optional implementation of step S3203 can be found in the optional implementation of step S2103 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0490] In step S3304, network device 102 sends RRC signaling.

[0491] In some embodiments, the RRC signaling is used to configure the resource allocation method corresponding to the terminal.

[0492] In step S3305, terminal 101 switches the resource allocation method based on the parsing of the first information.

[0493] In some embodiments, the terminal supports dynamically switching resource allocation methods.

[0494] In some embodiments, terminal 101 supports dynamically switching resource allocation methods. Terminal 101 can switch the resource allocation methods based on the parsing of the first information.

[0495] Alternatively, the resource allocation method after the switch can be determined in the following ways:

[0496] 1) The aforementioned first information includes a field for indicating the aforementioned resource allocation method. Optionally, a 1-bit DCI indicator field may be reserved in the aforementioned first information. If this bit is set to 0, it indicates that the resource allocation method based on sub-PRB is used; if this bit is set to 1, it indicates that the resource allocation method based on RB is used; or, if this bit is set to 0, it indicates that the resource allocation method based on RB is used; if this bit is set to 1, it indicates that the resource allocation method based on sub-PRB is used.

[0497] 2) The size of the first information mentioned above differs depending on the resource allocation method. Optionally, assuming the first information is DCI signaling, different DCI sizes can be defined for different resource allocation methods. Terminal 101 distinguishes the resource allocation method used through blind DCI detection. For example, different DCI sizes can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the defined DCI size for RB-based resource allocation is smaller than the DCI size for sub-PRB-based resource allocation, the terminal will determine the smaller DCI size as the RB-based resource allocation method during blind detection; or, if the defined DCI size for RB-based resource allocation is larger than the DCI size for sub-PRB-based resource allocation, the terminal will determine the larger DCI size as the RB-based resource allocation method during blind detection.

[0498] 3) Different resource allocation methods correspond to different scrambled Radio Network Temporary Identifiers (RNTIs). Optionally, different scrambled RNTIs can be defined for different resource allocation methods, and the terminal 101 uses the RNTI to distinguish between different resource allocation methods during parsing. For example, different scrambled RNTIs can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the RNTI for RB-based resource allocation is defined as 'a' and the RNTI for sub-PRB-based resource allocation is defined as 'b', then when the terminal performs parsing, it can determine that RNTI = a is used for RB-based resource allocation, and RNTI = b is used for sub-PRB-based resource allocation.

[0499] 4) Different resource allocation methods correspond to different Demodulation Reference Signal (DMRS) patterns or DMRS sequences. Optionally, different DMRS patterns or sequences can be defined for different resource allocation methods. When the terminal 101 performs parsing, it distinguishes between different resource allocation methods using the DMRS pattern or sequence. For example, different DMRS patterns or sequences can be defined for RB-based resource allocation and sub-PRB-based resource allocation. If the DMRS pattern / sequence for RB-based resource allocation is defined as 'a' and the DMRS pattern / sequence for sub-PRB-based resource allocation is defined as 'b', then when the terminal performs parsing, it can determine that DMRS pattern / sequence = a is the RB-based resource allocation method and DMRS pattern / sequence = b is the sub-PRB-based resource allocation method.

[0500] In some embodiments, the size of the first information is different for different resource allocation methods, so the terminal 101 can parse the received first information based on the size of one of the first information.

[0501] In some embodiments, during the switching between different resource allocation methods using DCI (Downlink Control Information) dynamic signaling parsing, in order to reduce the increase in the number of blind detections caused by inconsistent DCI sizes (inconsistent DCI sizes may lead to a double number of blind detections), it is necessary to ensure the alignment of DCI bit lengths.

[0502] Alternatively, the following alignment method can be used:

[0503] Option 1: Alignment of Frequency Domain Resource Assignment (FDRA) Fields in DCI

[0504] 1) Align the FDRA field length to a given scheduling scheme:

[0505] If the length of the FDRA field in the resource allocation scheme based on sub-PRB / RB is less than the length of the FDRA field in the resource allocation scheme based on RB / sub-PRB, then padding with several 0 bits is added to a specific position (Most Significant Bit, MSB or Least Significant Bit, LSB) of the FDRA field in the sub-PRB / RB handover scheme until the two are equal. If the length of the FDRA field in the resource allocation scheme based on sub-PRB / RB is greater than the length of the FDRA field in the resource allocation scheme based on RB / sub-PRB, then several MSBs or LSBs of the FDRA field in the resource allocation scheme based on RB / sub-PRB are truncated until the two are equal.

[0506] That is, when a handover scheme is adopted, if its FDRA field length is shorter than that of another handover scheme, an appropriate number of zero padding bits are added to specific positions (MSB bits or LSB bits) of the FDRA field of the shorter scheme until the two lengths are the same. Conversely, if the FDRA field length of the current handover scheme is longer, the MSB bits or LSB bits of the FDRA field of the longer scheme need to be truncated until it matches the shorter scheme.

[0507] 2) Align with the length of the longer FDRA field:

[0508] If the FDRA field lengths of the resource allocation scheme based on sub-PRB / RB are not equal, then several 0 padding bits are added to a specific position (MSB bit or LSB bit) of the shorter FDRA field until the two lengths are equal.

[0509] 3) Align with shorter FDRA field lengths:

[0510] If the lengths of the FDRA fields scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then the MSB or LSB bits of several long FDRA fields are truncated until they are equal.

[0511] Option 2: DCI total length alignment

[0512] 1) Aligning the DCI length to a given scheme:

[0513] If the DCI length of the resource allocation scheme based on sub-PRB / RB is less than the DCI length of the resource allocation scheme based on RB / sub-PRB, then padding with several 0 bits at specific positions (MSB or LSB bits) of the DCI based on sub-PRB / RB is performed until the two are equal. If the DCI length of the resource allocation scheme based on sub-PRB / RB is greater than the DCI length of the resource allocation scheme based on RB / sub-PRB, then truncating several MSB or LSB bits of the DCI based on RB / sub-PRB is performed until the two are equal.

[0514] 2) Align with the longer DCI length:

[0515] If the DCI lengths scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then padding bits with 0s are added at specific positions (MSB bits or LSB bits) of the shorter DCI until the two lengths are equal.

[0516] 3) Align with shorter DCI lengths:

[0517] If the DCI lengths scheduled based on the sub-PRB / RB resource allocation scheme are not equal, then truncate the MSB or LSB bits of several long DCIs until they are equal.

[0518] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0519] This application also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0520] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0521] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0522] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of this application. Terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to receive first information sent by a network device, the first information being used to determine the resource allocation method corresponding to the terminal; the resource allocation method includes at least one of the following: a resource allocation method based on sub-Physical Resource Blocks (sub-PRBs); a resource allocation method based on Resource Blocks (RBs); and a dynamically switched resource allocation method. Optionally, the transceiver module described above is used to perform at least one of the communication steps (e.g., S2101, S2102, S2103, S3101, S3102, S3103, S3201, S3202, S3203, S3301, S3302, S3303, S3304, but not limited thereto) performed by the terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module described above is used to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be elaborated here.

[0523] Figure 4B is a schematic diagram of the network device proposed in an embodiment of this application. The network device 4200 is used to execute any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send first information to a terminal, the first information being used to determine the resource allocation method corresponding to the terminal; the resource allocation method includes at least one of the following: a resource allocation method based on sub-physical resource blocks (sub-PRBs); a resource allocation method based on resource blocks (RBs); and a dynamically switched resource allocation method. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., S2101, S2102, S2103, S3101, S3102, S3103, S3201, S3202, S3203, S3301, S3302, S3303, S3304, but not limited thereto) performed by the network device 1021 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the network device 102 in any of the above methods, which will not be elaborated here.

[0524] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0525] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0526] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0527] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this application. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0528] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0529] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S3101, S3102, S3103, S3104, S3201, S3202, S3203, S3204, S3301, S3302, S3303, S3304, S3305, but not limited thereto), and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0530] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.

[0531] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this application is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0532] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this application. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0533] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0534] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0535] In some embodiments, the interface circuit 5202 performs communication steps such as sending and / or receiving in the above-described method, for example, at least one of steps S2101, S2102, S2103, S3101, S3102, S3103, S3104, S3201, S3202, S3203, S3204, S3301, S3302, S3303, S3304, and S3305. For example, the interface circuit 5202 performing communication steps such as sending and / or receiving in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps.

[0536] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0537] This application also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0538] This application also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0539] This application also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A resource allocation method, characterized in that, The method is executed by a terminal, and the method includes: Receive first information sent by the network device, the first information being used to determine the resource allocation method corresponding to the terminal; The resource allocation method includes at least one of the following: Resource allocation based on sub-PRB (sub-physical resource block); Resource allocation method based on resource blocks (RB); Dynamically switching resource allocation methods.

2. The method according to claim 1, characterized in that, The resource allocation method based on sub-PRB uses the resource unit (RE) as the basic resource granularity. The RB-based resource allocation method uses RB as the basic resource granularity; The resource allocation method based on sub-PRB includes at least one of the following: Resource allocation based on RE; Resource allocation methods based on RB and RE.

3. The method according to any one of claims 1-2, characterized in that, The method further includes: Send a second message to the network device, the second message being used to indicate the capabilities of the terminal; The capabilities of the terminal include at least one of the following: The terminal supports a portion of the bandwidth BWP configuration; The terminal supports the resource granularity and resource allocation methods; Does the terminal support resource allocation based on frequency domain reference points, wherein the frequency domain resource reference points are used to determine the starting frequency domain position of the resources allocated to the terminal? The terminal supports the size of resource allocation units; The terminal supports a certain spectrum bandwidth; The terminal supports a maximum number of Physical Resource Blocks (PRBs).

4. The method according to any one of claims 1-3, characterized in that, The resource allocation unit comprises Q REs, where Q is a positive integer.

5. The method according to any one of claims 1-4, characterized in that, The first information is Radio Resource Control (RRC) signaling.

6. The method according to claim 5, characterized in that, The first information is used to determine the resource allocation method based on sub-PRB corresponding to the terminal; the method further includes: The third information sent by the network device is received, and the third information is used to determine the resource allocation type corresponding to the terminal.

7. The method according to claim 6, characterized in that, The third information is used to indicate the resource allocation unit allocated to the terminal on the BWP, wherein the resource allocation unit is allocated continuously or discretely; The third information is used to indicate at least one RB allocated to the terminal on the BWP, and the third information is used to indicate the resource allocation unit allocated to the terminal on the at least one RB, wherein the resource allocation unit is allocated continuously or discretely; The third information is used to indicate the starting RE of the resource allocated to the terminal on the BWP, and the length of the resource; The third information is used to indicate at least one RB allocated to the terminal on the BWP, and the third information is used to indicate the starting RE of the resource allocated to the terminal on the at least one RB, as well as the length of the resource.

8. The method according to any one of claims 1-7, characterized in that, The terminal supports dynamically switching resource allocation methods; The first information is RRC signaling, which is used to configure the resource allocation method of the terminal.

9. The method according to any one of claims 1-4, characterized in that, The terminal supports dynamically switching resource allocation methods; the method further includes: The system receives RRC signaling sent by the network device, wherein the RRC signaling is used to configure the resource allocation method corresponding to the terminal. The resource allocation method is switched based on the first information.

10. The method according to any one of claims 1-4, characterized in that, The method further includes: The system receives RRC signaling sent by the network device, wherein the RRC signaling is used to configure the resource allocation method corresponding to the terminal. The resource allocation method determined by the first information is different from the resource allocation method configured by the RRC signaling; The resource allocation method corresponding to the terminal is determined to be the resource allocation method configured by the RRC signaling.

11. The method according to claim 9 or 10, characterized in that, The first information includes fields used to indicate the resource allocation method; The size of the first information varies depending on the resource allocation method. Different resource allocation methods correspond to different scrambled radio network temporary identifiers (RNTIs). Different resource allocation methods correspond to different demodulation reference signal DMRS patterns or DMRS sequences.

12. The method according to claim 13, characterized in that, The size of the first information varies depending on the resource allocation method; the method further includes: The target resource allocation method is determined based on the magnitude of one of the first pieces of information.

13. A resource allocation method, characterized in that, The method is performed by a network device, and the method includes: Send first information to the terminal, the first information being used to determine the resource allocation method corresponding to the terminal; The resource allocation method includes at least one of the following: Resource allocation based on sub-PRB (sub-physical resource block); Resource allocation method based on resource blocks (RB); Dynamically switching resource allocation methods.

14. The method according to claim 13, characterized in that, The resource allocation method based on sub-PRB uses the resource unit (RE) as the basic resource granularity. The RB-based resource allocation method uses RB as the basic resource granularity; The resource allocation method based on sub-PRB includes at least one of the following: Resource allocation based on RE; Resource allocation methods based on RB and RE.

15. The method according to any one of claims 13-14, characterized in that, The method further includes: Receive second information sent by the terminal, the second information being used to indicate the capabilities of the terminal; The capabilities of the terminal include at least one of the following: The terminal supports a portion of the bandwidth BWP configuration; The terminal supports the resource granularity and resource allocation methods; Does the terminal support resource allocation based on frequency domain reference points, wherein the frequency domain resource reference points are used to determine the starting frequency domain position of the resources allocated to the terminal? The terminal supports the size of resource allocation units; The terminal supports a certain spectrum bandwidth; The terminal supports a maximum number of Physical Resource Blocks (PRBs).

16. The method according to any one of claims 13-15, characterized in that, The resource allocation unit comprises Q REs, where Q is a positive integer.

17. The method according to any one of claims 13-16, characterized in that, The first information is Radio Resource Control (RRC) signaling.

18. The method according to claim 17, characterized in that, The first information is used to determine the resource allocation method based on sub-PRB corresponding to the terminal; the method further includes: A third piece of information is sent to the terminal, the third piece of information being used to determine the resource allocation type corresponding to the terminal.

19. The method according to claim 18, characterized in that, The resource allocation type includes at least one of the following: The third information is used to indicate the resource allocation unit allocated to the terminal on the BWP, wherein the resource allocation unit is allocated continuously or discretely; The third information is used to indicate at least one RB allocated to the terminal on the BWP, and the third information is used to indicate the resource allocation unit allocated to the terminal on the at least one RB, wherein the resource allocation unit is allocated continuously or discretely; The third information is used to indicate the starting RE of the resource allocated to the terminal on the BWP, and the length of the resource; The third information is used to indicate at least one RB allocated to the terminal on the BWP, and the third information is used to indicate the starting RE of the resource allocated to the terminal on the at least one RB, as well as the length of the resource.

20. The method according to any one of claims 13-19, characterized in that, The terminal supports dynamically switching resource allocation methods; The first information is RRC signaling, which is used to configure the resource allocation method of the terminal.

21. The method according to any one of claims 13-16, characterized in that, The terminal supports dynamically switching resource allocation methods; The terminal is used to switch the resource allocation method based on the first information; The method further includes: An RRC signaling message is sent to the terminal, the RRC signaling message being used to configure the resource allocation method corresponding to the terminal.

22. The method according to claim 21, characterized in that, The first information includes fields used to indicate the resource allocation method; The size of the first information varies depending on the resource allocation method. Different resource allocation methods correspond to different scrambled radio network temporary identifiers (RNTIs). Different resource allocation methods correspond to different demodulation reference signal DMRS patterns or DMRS sequences.

23. The method according to claim 23, characterized in that, The size of the first information varies depending on the resource allocation method; the terminal is used to determine the target resource allocation method based on the size of one of the first information methods.

24. A terminal, characterized in that, The terminal includes: The transceiver module is used to receive first information sent by the network device, the first information being used to determine the resource allocation method corresponding to the terminal; The resource allocation method includes at least one of the following: Resource allocation based on sub-PRB (sub-physical resource block); Resource allocation method based on resource blocks (RB); Dynamically switching resource allocation methods.

25. A network device, characterized in that, The network device includes: The transceiver module is used to send first information to the terminal, wherein the first information is used to determine the resource allocation method corresponding to the terminal; The resource allocation method includes at least one of the following: Resource allocation based on sub-PRB (sub-physical resource block); Resource allocation method based on resource blocks (RB); Dynamically switching resource allocation methods.

26. A terminal, characterized in that, The terminal includes: One or more processors; The terminal is used to execute the resource allocation method according to any one of claims 1-12.

27. A network device, characterized in that, The network device includes: One or more processors; The first network device is used to execute the resource allocation method according to any one of claims 13-23.

28. A communication device, characterized in that, The communication device is used to execute the resource allocation method according to any one of claims 1-12 and 13-23.

29. A communication system, characterized in that, The system includes a terminal and a network device, wherein the terminal is configured to implement the resource allocation method according to any one of claims 1-12, and the network device is configured to implement the resource allocation method according to any one of claims 13-23.

30. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the resource allocation method as described in any one of claims 1-12, 13-23.

31. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the resource allocation method according to any one of claims 1-12 and 13-23.

Images