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

Abstract

The present application discloses a resource switching method, a communication device, a communication system, a storage medium, and a program product. The method comprises: receiving indicating information sent by a network device, wherein the indicating information is used for instructing a terminal to switch from a first bandwidth part (BWP) to a second BWP, and the first BWP is a currently activated BWP; receiving, on the first BWP, first information sent by the network device; determining, on the basis of the first information, a frequency domain resource allocated to the terminal on the second BWP, such that the terminal can perform corresponding BWP switching on the basis of the indicating information sent by the network device, and can determine, on the basis of the first information sent by the network device and received on the BWP prior to switching, a frequency domain resource allocated to the terminal on the BWP after switching, without the terminal having to perform additional resource searching or negotiation on the BWP after switching, thereby improving system communication efficiency and accuracy, and enhancing uplink coverage.

Description

Resource switching methods, communication equipment, communication systems, storage media and program products Technical Field

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

[0002] In non-terrestrial networks (NTNs), to address issues such as frequency band resource limitations, low data rate transmission characteristics, and the increased number of users due to wide coverage, uplink capacity enhancement can be considered to serve more users simultaneously. Summary of the Invention

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

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

[0005] The terminal receives an indication message sent by a network device, the indication message being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0006] Receive the first information sent by the network device on the first BWP;

[0007] Based on the first information, the frequency domain resources allocated to the terminal on the second BWP are determined.

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

[0009] Send indication information to the terminal, the indication information being used to instruct the terminal to switch from a first portion bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0010] Send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP.

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

[0012] The transceiver module is used to receive indication information sent by the network device. The indication information is used to instruct the terminal to switch from the first bandwidth BWP to the second BWP, where the first BWP is the currently active BWP.

[0013] The transceiver module is further configured to receive first information sent by the network device on the first BWP;

[0014] The processing module is configured to determine, based on the first information, the frequency domain resources allocated to the terminal on the second BWP.

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

[0016] The transceiver module is used to send indication information to the terminal, the indication information being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0017] The transceiver module is further configured to send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP based on the first information.

[0018] The solution proposed in this application involves receiving indication information sent by a network device, which instructs the terminal to switch from a first bandwidth BWP to a second BWP, where the first BWP is the currently active BWP. The terminal receives first information sent by the network device on the first BWP. Based on the first information, the terminal determines the frequency domain resources allocated to the terminal on the second BWP. This enables the terminal to perform corresponding BWP switching based on the indication information sent by the network device, and to determine the frequency domain resources allocated to the terminal on the switched-off BWP based on the first information received on the BWP before the switch. The terminal does not need to perform additional resource searches or negotiations on the switched-off BWP, thus improving system communication efficiency and accuracy, and enhancing uplink coverage. Attached Figure Description

[0019] 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.

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

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

[0022] Figure 2A is an interactive schematic diagram of a resource switching method according to an embodiment of this application;

[0023] Figures 2B-2I are schematic diagrams illustrating resource switching methods according to embodiments of this application;

[0024] Figures 3A-3C are interactive schematic diagrams illustrating the resource switching method according to embodiments of this application;

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

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

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

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

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

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

[0031] The terminal receives an indication message sent by a network device, the indication message being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0032] Receive the first information sent by the network device on the first BWP;

[0033] Based on the first information, the frequency domain resources allocated to the terminal on the second BWP are determined.

[0034] In the above embodiments, the terminal is able to perform corresponding BWP handover based on the indication information sent by the network device, and can determine the frequency domain resources allocated to the terminal on the BWP after handover based on the first information received on the BWP before handover from the network device. The terminal does not need to perform additional resource search or negotiation on the BWP after handover, thereby improving system communication efficiency and accuracy and enhancing uplink coverage.

[0035] In conjunction with some embodiments of the first aspect, some embodiments include at least one of the following:

[0036] The first BWP and the second BWP are of different sizes;

[0037] The resource allocation methods corresponding to the first BWP and the second BWP are different;

[0038] The resource allocation granularity corresponding to the first BWP and the second BWP is different;

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

[0040] The resource allocation method based on sub-PRBs uses resource units (REs) as the basic resource granularity.

[0041] The resource allocation method based on resource blocks (RB) uses RB as the basic resource granularity.

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

[0043] Resource allocation based on RE;

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

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, determining the frequency domain resources allocated to the terminal on the second BWP based on the first information includes:

[0046] On the second BWP, the first information is parsed based on the first number of bits to determine the frequency domain resources allocated to the terminal;

[0047] The size of the first information is determined based on the first BWP.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first number of bits is fixed; or,

[0049] The first number of bits is determined based on the second BWP.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the first number of bits is fixed;

[0051] The fixed first bit number is determined based on the BWP size and resource allocation method supported by the terminal, and the fixed first bit number is the maximum value among multiple sizes corresponding to the second information supported by the terminal;

[0052] The second information is used to determine the frequency domain resources allocated to the terminal.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the first number of bits is fixed; the method further includes:

[0054] The size of the first information is less than the number of bits. The first information is padded with zeros based on the number of bits, and the size of the first information after processing is equal to the number of bits.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the first number of bits is determined based on the second BWP; the method further includes:

[0056] If the size of the first information is less than the first number of bits, the first information is padded with zeros based on the first number of bits, and the size of the processed first information is equal to the first number of bits; or...

[0057] The size of the first information is greater than the first number of bits. The first information is pruned based on the first number of bits, and the size of the first information after the pruning is equal to the first number of bits.

[0058] Secondly, embodiments of this application propose a resource switching method, the method comprising:

[0059] Send indication information to the terminal, the indication information being used to instruct the terminal to switch from a first portion bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0060] Send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP.

[0061] In the above embodiments, the terminal is able to perform corresponding BWP handover based on the indication information sent by the network device, and can determine the frequency domain resources allocated to the terminal on the BWP after handover based on the first information received on the BWP before handover from the network device. The terminal does not need to perform additional resource search or negotiation on the BWP after handover, thereby improving system communication efficiency and accuracy and enhancing uplink coverage.

[0062] In conjunction with some embodiments of the second aspect, at least one of the following is included in some embodiments:

[0063] The first BWP and the second BWP are of different sizes;

[0064] The resource allocation methods corresponding to the first BWP and the second BWP are different;

[0065] The resource allocation granularity corresponding to the first BWP and the second BWP is different;

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

[0067] The resource allocation method based on sub-PRBs uses resource units (REs) as the basic resource granularity.

[0068] The resource allocation method based on resource blocks (RB) uses RB as the basic resource granularity.

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

[0070] Resource allocation based on RE;

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

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is parsed on the second BWP based on a first number of bits, and the first information is used to determine the frequency domain resources allocated to the terminal;

[0073] The size of the first information is determined based on the first BWP.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the first number of bits is fixed; or,

[0075] The first number of bits is determined based on the second BWP.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the first number of bits is fixed;

[0077] The fixed first bit number is determined based on the BWP size and resource allocation method supported by the terminal, and the fixed first bit number is the maximum value among multiple sizes corresponding to the second information supported by the terminal;

[0078] The second information is used to determine the frequency domain resources allocated to the terminal.

[0079] Thirdly, embodiments of this application propose a resource switching method. This method is used in a communication system, which includes a terminal and network equipment. The method includes:

[0080] The network device sends an instruction message to the terminal, the instruction message being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP;

[0081] The network device sends first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP;

[0082] The terminal receives first information sent by the network device on the first BWP, and determines the frequency domain resources allocated to the terminal on the second BWP based on the first information.

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

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

[0085] In a sixth aspect, embodiments of this application provide 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.

[0086] In a seventh aspect, embodiments of this application provide a network device, wherein the terminal includes one or more processors; wherein the terminal is used to execute the second aspect and optional implementations of the second aspect.

[0087] Eighthly, 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.

[0088] Ninthly, embodiments of this application propose a communication system, which includes: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.

[0089] In a tenth aspect, 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.

[0090] In the eleventh aspect, embodiments of this application provide a program product that, when executed by a communication device, causes 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.

[0091] In a twelfth 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.

[0092] In a thirteenth 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.

[0093] 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.

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

[0095] 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.

[0096] 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.

[0097] 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.

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

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

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

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

[0105] 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.

[0106] 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”.

[0107] 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.

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

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

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

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

[0115] 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.

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

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

[0118] 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.

[0119] 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).

[0120] 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).

[0121] 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.

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

[0123] 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.

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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).

[0130] 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).

[0131] 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:

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

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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 Radio Resource Control Message (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 in DCI format 1_1 / 1_2) or the higher-layer parameter rbg-SizeDCI-1-3 configured in PUSCH-ConfigDCI-0-3 (when scheduling in 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.

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

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

[0139] 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:

[0140] in,

[0141] The size of the first RBG is

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

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

[0144] The size of the bitmap mentioned above is N. RBG Each 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.

[0145] 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.

[0146] The resource allocation field consists of a Resource Indication Value (RIV), which corresponds to the initial VRB (RB). start ) and the number L of consecutively allocated RB RBs .

[0147] RIV is defined as follows:

[0148] if but,

[0149] otherwise,

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

[0151] 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.

[0152] When different DCI sizes exist, 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.

[0153] 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 transformation precoding being enabled or disabled. The specific transmission mode used is controlled by the PUSCH-Config high-level parameter `resourceAllocation`.

[0154] 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:

[0155] 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.

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

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

[0158] 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.

[0159] 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.

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

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

[0162] 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:

[0163] in,

[0164] The size of the first RBG is

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

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

[0167] 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.

[0168] 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 .

[0169] RIV is defined as follows

[0170] if but,

[0171] otherwise,

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

[0173] 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.

[0174] When different DCI sizes exist, 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.

[0175] 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.

[0176] RIV is defined as follows:

[0177] if but,

[0178] otherwise,

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

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

[0181] 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.

[0182] 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.

[0183] RIV is defined as follows:

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

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

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

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

[0188] 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.

[0189] In some embodiments, a BWP is a contiguous Common Resource Block (CRB) within a resource grid. NTN transmission has a large bandwidth, but larger bandwidth requires higher power consumption. Therefore, it's unnecessary for the UE to always support the entire bandwidth; instead, it can selectively support a portion of the bandwidth. The BWP is designed based on this concept, effectively reducing UE power consumption when the full bandwidth is not needed. Furthermore, the BWP design allows for more flexible scheduling of bandwidth size and frequency band location. This flexibility not only adapts to diverse service requirements but also effectively addresses challenges such as frequency-selective fading.

[0190] In some embodiments, the BWP configuration includes: Initial BWP, active BWP, and default BWP.

[0191] The Initial BWP includes the Initial DL BWP (Initial Uplink BWP) and the Initial UL BWP (Initial Downlink BWP), which are configured in SIB1. If the Initial BWP is not configured, it defaults to CORESET0. The Initial BWP is mainly used for the initial access process, such as receiving data in SIB1, receiving RAR and Msg4 during random access, and sending preamble and Msg4 data.

[0192] An active BWP is a BWP that is activated after initial access is completed. Specifically, it refers to the BWP configured for the UE after initial access is complete. After initial access is complete, the UE will have various service requirements, so the bandwidth of an active BWP is generally larger than that of an initial BWP.

[0193] The default BWP is used when the UE has no service requirements for a long time. It allows the UE to switch from the high-bandwidth active BWP to a default BWP with a smaller bandwidth, thereby reducing power consumption.

[0194] In some embodiments, BWP has the following four switching scenarios:

[0195] 1) Fast switching of DCI indications accompanying data scheduling (DCI-based BWP switching)

[0196] 2) Timer-based BWP switching when there is no service scheduling for an extended period of time.

[0197] 3) Switching from the initial BWP to the first active BWP during RRC (re)configuration and activation of the SCell (RRC-based BWP switching)

[0198] 4) If there is no PRACH resource in the active BWP during the random access process, the UE will automatically switch to the initial BWP (BWP handover during the random access process).

[0199] DCI-based BWP handover is indicated by the Bandwidth part indicator field in the DCI. DCI-based handover is used to quickly switch BWPs when data is scheduled. DCI formats 0_1, 1_1, etc., can be used for DCI handover, but are not exclusively used for it. If the active BWP indicated in the DCI received by the UE differs from the current one, a DCI handover is triggered. However, it's important to note that when a UE performs a DCI-based BWP handover, the data scheduled by the DCI needs to be transmitted on the new BWP. Therefore, the size of the information field in the current DCI may not be the same as the size required for the new BWP to parse that information field. Thus, zero padding or removing a few bits may be necessary during parsing.

[0200] Timer-based BWP handover is used when the UE has not been performing service transmission or reception for an extended period (meaning the UE may have little service demand). In this case, the UE switches to a lower-bandwidth default BWP to save energy. (Note that in the current protocol, only downlink BWPs require Timer-based BWP handover; uplinks do not, as downlink BWPs generally have higher bandwidth and consume more power.) The specific timeout period is indicated by the parameter `bwp-InactivityTimer`, and the specific default DL BWP is indicated to the UE by the parameter `defaultDownlinkBWP-Id`. If `defaultDownlinkBWP-Id` is not configured, the default DL BWP is the initial DL BWP. During the timer period, whether there is service demand is determined by whether DCI scheduling has occurred, not by whether data transmission or reception has taken place.

[0201] RRC-based BWP handover is used after the UE completes initial access and enters RRC connected state, or after RRC reconfiguration or SCell activation. It allows the UE to immediately enter a suitable BWP for service transmission and reception, instead of remaining in the initial BWP. During the initial access process, the UE uses the initial BWP, meaning that SIB and RA-related operations are typically completed within the initial BWP. Once initial access is complete and the UE enters RRC connected state, the base station can activate BWPs other than the initial BWP using firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, which usually have a larger bandwidth than the initial BWP.

[0202] BWP handover during random access refers to the automatic handover of the UE to the initial UL BWP if no PRACH resource is available on the active UL BWP during the random access process. The corresponding DL BWP also needs to switch to its pair with the UL BWP. In other words, if the handover is to the initial UL BWP, the active DL BWP also switches to the initial DL BWP. If the handover is not to the initial BWP, the ID of the active DL BWP must be the same as the ID of the active UL BWP; otherwise, the active DL BWP needs to be switched. Furthermore, if the UE receives a BWP handover indication from the DCI during random access, whether to switch BWPs depends on the UE's own behavior: either switch to the new BWP to restart random access or ignore the handover indication. However, if the UE receives a BWP handover indication from the RRC configuration or reconfiguration during random access, the UE needs to stop the current random access process and perform a BWP handover.

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

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

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

[0206] 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).

[0207] In some embodiments, an uplink capacity enhancement is achieved using a pre-Discrete Fourier Transform (pre-DFT) based Orthogonal Cover Code (OCC) multiplexing transmission scheme, as shown in Figure 1B. This scheme enables multiple UEs to share a single 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.

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

[0209] In some embodiments, DCI format 0_1 / 2, 1_1 / 2, and other signaling are used to schedule data and indicate BWP handover. If the active BWP indicated in the DCI received by the UE is different from the current one, a DCI handover is triggered. However, it should be noted that when the UE performs a DCI-based BWP handover, the data scheduled by the DCI must be transmitted on the new BWP. In this case, when using a sub-PRB-based resource allocation method, the FDRA field size determined in the DCI based on the current active BWP may not be the same as the size required for the BWP to interpret the FDRA field due to at least one of the following reasons: the BWP size before and after the handover may not be the same; the resource allocation method corresponding to the BWP before and after the handover may not be the same; or the resource allocation granularity corresponding to the BWP before and after the handover may not be the same. Therefore, the interpretation of the FDRA field in the DCI involves the issue of insufficient or redundant FDRA field bits.

[0210] 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.

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

[0212] In step S2101, network device 102 sends an instruction message.

[0213] In some embodiments, network device 102 sends the aforementioned instruction information to terminal 101.

[0214] In some embodiments, terminal 101 receives indication information sent by network device 102.

[0215] In some embodiments, the above-mentioned indication information is used to instruct terminal 101 to switch from a first portion bandwidth BWP to a second BWP, wherein the first BWP is the currently active BWP.

[0216] In some embodiments, the first BWP and the second BWP described above include at least one of the following:

[0217] The first BWP mentioned above is different in size from the second BWP mentioned above;

[0218] The resource allocation methods corresponding to the first BWP and the second BWP mentioned above are different;

[0219] The resource allocation granularity corresponding to the first BWP and the second BWP mentioned above is different;

[0220] The above-mentioned resource allocation methods include at least one of the following:

[0221] The resource allocation method based on sub-PRB uses the resource element (RE) as the basic resource granularity.

[0222] Resource allocation based on resource blocks (RBs) uses RBs as the basic resource granularity.

[0223] The fact that the two BWPs are different in size means that they occupy different bandwidths in the frequency domain, that is, these two BWPs are two different BWPs.

[0224] As an example, if the first BWP has a bandwidth of 40MHz and a subcarrier spacing of 15kHz, and the second BWP has a bandwidth of 10MHz and a subcarrier spacing of 15kHz (but these can also be different, depending on the system configuration and terminal requirements), then the first BWP and the second BWP are different in size and are two different BWPs.

[0225] The two BWPs have different resource allocation methods, meaning that they are configured or determined to use different resource allocation methods. The two BWPs have different basic granularity of resource allocation, meaning that they use different minimum resource units when allocating resources, including but not limited to the size and quantity of the minimum resource units.

[0226] As an example, if the first BWP is configured or determined to use a sub-PRB-based resource allocation method, and the second BWP is configured or determined to use an RB-based resource allocation method, or if the first BWP is configured or determined to use an RB-based resource allocation method, and the second BWP is configured or determined to use a sub-PRB-based resource allocation method, where the first BWP is the currently active BWP, and if network device 102 sends an instruction to terminal 101, instructing terminal 101 to switch from the first BWP to the second BWP, it can be seen from the resource allocation methods configured or determined for the first BWP and the second BWP that the resource allocation methods corresponding to the first BWP and the second BWP are different. Moreover, if the sub-PRB-based resource allocation method uses RE as the basic resource granularity, and the RB-based resource allocation method uses RB as the basic resource granularity, then the basic resource allocation granularity used by the first BWP and the second BWP is also different.

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

[0228] Resource allocation based on RE;

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

[0230] Among them, the RE-based resource allocation method refers to the terminal supporting resource granularity of RE and the resource allocation method supported by the terminal being RE-level resource allocation based on sub-PRB; the RB and RE-based resource allocation method refers to the terminal supporting resource granularity of RE and the resource allocation method supported by the terminal being RB+RE-level resource allocation based on sub-PRB, wherein RB-level resource allocation is performed first, followed by RE-level resource allocation.

[0231] As an example, if both the first BWP and the second BWP are configured or determined to use a sub-PRB-based resource allocation method, where the first BWP is the currently active BWP, and if network device 102 sends an instruction to terminal 101, instructing terminal 101 to switch from the first BWP to the second BWP, even though both the first BWP and the second BWP are configured or determined to use a sub-PRB-based resource allocation method, if the first BWP is configured or determined to use a RE-based resource allocation method, while the second BWP is configured or determined to use a RB and RE-based resource allocation method, then the resource allocation methods used by the first BWP and the second BWP are different.

[0232] 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.

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

[0234] In some embodiments, the aforementioned indication information may be DCI, or it may be other downlink signaling, etc.

[0235] As an example, when the indication information is DCI, the terminal 101 can be instructed to switch from the first BWP to the second BWP by configuring the BWP indication field in the DCI format. The first BWP is the currently active BWP. Specifically, if the DCI format contains a Bandwidth part indicator field, which indicates which BWP the UE uses for data transmission or reception, and the UE supports DCI-based BWP handover (i.e., the UE can switch the currently used BWP based on the value of the Bandwidth part indicator field in the DCI format), and the newly indicated UL BWP / DL BWP by the Bandwidth part indicator field is different from the active UL BWP / DL BWP, then the gNB can instruct the UE to perform a BWP handover by sending a DCI message with the Bandwidth part indicator field configured to the UE.

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

[0237] In some embodiments, network device 102 sends the aforementioned first information to terminal 101.

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

[0239] In some embodiments, the first information is used by terminal 101 to determine the frequency domain resources allocated to terminal 101 on the second BWP.

[0240] In some embodiments, the first information mentioned above may be DCI, or it may be other downlink signaling, etc.

[0241] It should be noted that when the first piece of information mentioned above is DCI, the DCI includes a Frequency Domain Resource Allocation (FDRA) field (or information field). The FDRA field in the DCI indicates the location and size of the frequency domain resources allocated to the UE. These resources are used for data transmission, including downlink data transmission (such as PDSCH) and uplink data transmission (such as PUSCH). Through the FDRA field, the UE can know in which frequency range it receives or transmits data.

[0242] The FDRA field typically contains specific information about frequency domain resource allocation, such as:

[0243] Starting position of the resource block: Indicates the index of the starting RB of the allocated frequency domain resource;

[0244] Number of resource blocks: Indicates the number of RBs allocated in the frequency domain.

[0245] This information is typically encoded and transmitted in RIV format to efficiently represent large amounts of resource allocation information within a limited number of bits.

[0246] In some embodiments, the above-mentioned indication information and the above-mentioned first information may be the same DCI or different DCIs, and this application does not impose any restrictions on this.

[0247] In step S2103, terminal 101 determines the frequency domain resources allocated to terminal 101 on the aforementioned second BWP.

[0248] In some embodiments, terminal 101 may determine the frequency domain resources allocated to terminal 101 on the second BWP based on the first information described above.

[0249] In some embodiments, terminal 101 can determine the frequency domain resources allocated to terminal 101 on the second BWP by parsing the first information described above.

[0250] In some embodiments, the terminal 101 parses the first information based on the first number of bits on the second BWP to determine the frequency domain resources allocated to the terminal 101; wherein the size of the first information is determined based on the first BWP.

[0251] The size of the first information is determined based on the first BWP, meaning that during transmission, the first information is determined based on the currently active BWP (i.e., the first BWP).

[0252] Wherein, the terminal 101 parses the first information based on the first number of bits on the second BWP, means that after receiving the first information, the terminal 101 parses the first information on the switched BWP (i.e., the second BWP) based on the first number of bits.

[0253] In other words, during transmission, the first information is determined based on the currently active BWP (first BWP), but during parsing, the first information is parsed by terminal 101 on the switched BWP (second BWP) based on the first number of bits.

[0254] Optionally, when the first information is DCI and the DCI includes an FDRA field, the size of the FDRA field in the DCI is determined based on the first BWP during transmission. However, when the terminal 101 parses the FDRA field in the DCI on the switched BWP, it needs to determine the size of the FDRA field in the DCI based on the first number of bits.

[0255] As an example, assuming the first information is DCI, and the DCI includes an FDRA field, the actual bit width carried by the FDRA field in the DCI sent by the gNB is determined based on the current active BWP. However, when the UE parses the FDRA field in the DCI on the BWP after handover, it needs to determine the size of the FDRA field in the DCI based on the first bit count, and then determine the frequency domain resources allocated to the UE.

[0256] In some embodiments, the first number of bits is fixed.

[0257] As an example, suppose the first information is DCI, and the DCI includes an FDRA field. Considering that at least one of the following reasons may lead to different FDRA field sizes: different BWP sizes, different resource allocation methods based on Sub-PRB, and different resource allocation granularities used by different BWPs, the UE uniformly determines the FDRA field size according to a fixed first bit number when parsing the FDRA field in the DCI on the BWP after handover. Optionally, the size of the FDRA field can be determined to be a fixed first bit number. In this case, the determined FDRA field size is fixed and does not change with BWP handover. The fixed first bit number can be the maximum FDRA field bit number, i.e., the maximum FDRA field size.

[0258] In some embodiments, the number of the first bits is fixed;

[0259] The aforementioned fixed first bit number is determined based on the BWP size and resource allocation method supported by the aforementioned terminal, and the aforementioned fixed first bit number is the maximum value among multiple sizes corresponding to the second information supported by the aforementioned terminal;

[0260] The second piece of information is used to determine the frequency domain resources allocated to the terminal.

[0261] In other words, when the number of first bits is fixed, the method for determining the fixed number of first bits is as follows: based on the BWP size and resource allocation method supported by the terminal, multiple sizes corresponding to the second information supported by the terminal under the above BWP size and resource allocation method are pre-calculated, and the maximum value is selected as the first number of bits. The second information is used to determine the frequency domain resources allocated to the terminal.

[0262] Similarly, the second piece of information mentioned above can be DCI, or it can be other downlink signaling, etc.

[0263] Similarly, when the second piece of information mentioned above can be a DCI, the DCI includes the FDRA field.

[0264] Optionally, if the second information is a DCI and the DCI includes an FDRA field, then the multiple sizes corresponding to the second information are the multiple sizes of the FDRA field.

[0265] As an example, assuming the number of the first bit is fixed, then the number of the first bit can be the maximum FDRA field size. Alternatively, the maximum FDRA field size can be determined based on at least one of the following factors:

[0266] 1) BWP size supported by the terminal;

[0267] 2) Resource allocation methods corresponding to the BWP supported by the terminal;

[0268] 3) The resource allocation granularity corresponding to the BWP supported by the terminal.

[0269] Considering at least one of 1), 2), and 3), the length of the FDRA field depends on the size of the active BWP and the resource allocation method, wherein the resource allocation method includes, but is not limited to, one of the following:

[0270] I. Resource allocation method based on Sub-PRB:

[0271] Type A: The FDRA field in DCI directly indicates RE-level resource allocation, and sub-PRBs are 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 FDRA field in DCI is actually a bitmap indicator. Each bit in this bitmap corresponds to a REG. If a bit is set to 1, it means the corresponding REG has been allocated to the UE; if a bit is set to 0, it means 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.

[0272] The bit overhead of the FDRA field is:

[0273] Wherein, the REresource unit size is Q (in RE), and the BWP size is...

[0274] Type B: In DCI, the FDRA field first provides resource allocation instructions based on RB, then provides resource allocation instructions based on sub-PRB. The sub-PRB allocates resources discretely or continuously on the allocated RB-level resources using a REG bitmap. The RB-based resource allocation scheme can be type 0 or type 1, or it can simply indicate a starting RB position, using the RE#0 of this RB as a reference point, before providing resource allocation instructions based on sub-PRB (REG method).

[0275] The bit overhead of the FDRA field is:

[0276] The REresource unit size is Q (in REs). For each RBG of size P×12, the total number of REGs is: BWP size is

[0277] Type C: The FDRA field in DCI 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 RIV containing the start position Start RE and the length of the RE unit, which indicates the sub-PRB resource unit with RE as the smallest granularity in the uplink transmission.

[0278] The bit overhead of the FDRA field is:

[0279] The total number of REs within BWP is: The RE unit has a length of L. RE .

[0280] Type D: In DCI, the FDRA field first performs RB-based resource allocation indication, then performs sub-PRB-based resource allocation indication. The position of the sub-PRB resource unit on the allocated RB-level resources is indicated by a RIV containing the start position (Start RE) and the RE unit length. The RB-based resource allocation scheme can be type 0 or type 1, or it can simply indicate a start RB position, using RE#0 of this RB as the reference point, before performing sub-PRB-based resource allocation indication (RIV method).

[0281] The bit overhead of the FDRA field is:

[0282] The total number of RBs within BWP is: The total number of REs within the allocated RB is: N RE =L RB ×12, RE unit length is L RE .

[0283] II. Resource allocation method based on RB:

[0284] Type0:

[0285] The bit overhead of the FDRA field is:

[0286] Wherein, the RB resource unit size is P (in RV), and the BWP size is... (Unit: RB)

[0287] Type 1:

[0288] The bit overhead of the FDRA field is:

[0289] The total number of RBs within BWP is: The length of the RB unit is L RB .

[0290] Therefore, based on the BWP size and resource allocation method that may be scheduled in all transmissions, all possible values ​​of FDRA field size under the above BWP size and resource allocation method can be pre-calculated and compared, and the maximum value can be selected as the maximum FDRA field size.

[0291] In some embodiments, the first number of bits is fixed. If the size of the first information is less than the first number of bits, the terminal 101 can also pad the first information with zeros based on the first number of bits, so that the size of the first information after processing is equal to the first number of bits.

[0292] As an example, if a Bandwidth part indicator field is configured in the DCI format, which indicates which BWP the UE uses for data transmission or reception, and the UE supports DCI-based BWP handover (i.e., the UE can switch the currently used BWP based on the value of the Bandwidth part indicator field in the DCI format), and the newly indicated UL BWP / DL BWP by the Bandwidth part indicator field is different from the active UL BWP / DL BWP, and the DCI includes an FDRA field, which indicates the location and size of the frequency domain resources allocated to the UE, then the gNB can send the DCI to the UE to instruct the UE to perform BWP handover and to help the UE determine the frequency domain resources allocated to the UE on the new BWP. Considering the differences in BWP size and / or Sub-PRB-based resource allocation methods and / or the different granularities of resource allocation used by different BWPs, which may result in different FDRA field sizes, the UE should perform the following operations when parsing the FDRA field in the DCI on the switched BWP after receiving the DCI from the gNB, and set the active UL BWP / DL BWP to the UL BWP / DL BWP newly indicated by the Bandwidth part indicator field in the DCI format:

[0293] The size of the FDRA field in DCI is determined by a fixed first number of bits.

[0294] In the above process, the actual bit width carried by the FDRA field in the DCI sent by the gNB is determined based on the current active BWP, specifically based on the size of the current active BWP and / or the resource allocation method and / or the resource allocation granularity corresponding to the current active BWP (see the relevant description of the determination process of the maximum FDRA field size above). However, for different BWPs, the bit width when the UE parses the FDRA field in the DCI on the BWP after handover is consistent, and the size of the FDRA field is determined according to a fixed first number of bits.

[0295] The fixed first bit number can be the maximum FDRA field bit number, i.e., the maximum FDRA field size.

[0296] Assuming the actual bit width of the FDRA field in the DCI sent by the gNB is determined based on the current active BWP and is y bits, and the length of the FDRA field in the DCI when the UE parses the BWP after handover is a fixed first bit number, x bits, where the fixed first bit number is the maximum FDRA field bit number, that is, x bits is the maximum possible FDRA field size. Therefore, there will only be two cases: the actual bit width y of the FDRA field in the DCI sent by the gNB is less than the fixed first bit number x, and the actual bit width y of the FDRA field in the DCI sent by the gNB is equal to the fixed first bit number x. There will not be a case where the actual bit width y of the FDRA field in the DCI sent by the gNB is greater than the fixed first bit number x.

[0297] Specifically, if the actual bit width y carried by the FDRA field in the DCI sent by the gNB is less than the fixed first number of bits x, then when the UE parses the FDRA field in the DCI on the BWP after handover, a certain (xy) bit of the FDRA field in the DCI is actually padded with zeros. This certain (xy) bit is determined based on the protocol preset and can be either the high (xy) bit or the low (xy) bit.

[0298] If the actual bit width y carried by the FDRA field in the DCI sent by the gNB is equal to the fixed first number of bits x, then the actual bit width carried by the FDRA field in the DCI sent by the gNB and the length of the FDRA field in the DCI when parsing by the BWP after the handover are both x bits, then no zero-padding is required.

[0299] To more clearly illustrate the resource switching process when the first number of bits is fixed, an example is provided below.

[0300] Figure 2B is a schematic diagram of a resource switching method according to an embodiment of this application.

[0301] Assuming a switch from BWP1 to BWP2, or from BWP2 to BWP1, the fixed first bit number x = 17 bits, where the fixed first bit number is the maximum FDRA field bit number, i.e., the maximum FDRA field size, and:

[0302] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type B resource allocation type. First, an RB-based resource allocation instruction (type 0 method) is given. The RB resource unit size is P×12 (unit: RE), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0303] Next, resource allocation instructions (REG method) based on sub-PRB are executed, with the REresource unit size being Q (in REs), and the total number of REGs being: The bit overhead of the FDRA field in DCI is as follows:

[0304] Assuming BWP 1 size is 30RB, P=10, Q=24, then the FDRA field size corresponding to BWP 1 is 15 bits.

[0305] BWP 2 is configured or determined to use RB-based resource allocation, and uses type 0 resource allocation type. The RB resource unit size is P (in RBs), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0306] Assuming BWP 2 size is 100RB and P = 10, then the FDRA field size corresponding to BWP 2 is 10 bits.

[0307] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2B:

[0308] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2B, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 2), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2B, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 2 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 2 redundant bits. During parsing, the FDRA field is 0 0011 0010 1001 1001.

[0309] To switch from BWP2 to BWP1, see Schedule 2 in Figure 2B:

[0310] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 10 bits. Assuming the FDRA field during transmission is as shown in Figure 2B, it is 10 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 1), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (10 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2B, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 7 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 7 redundant bits. During parsing, the FDRA field is 0 00000010 1001 1001.

[0311] Figure 2C is a schematic diagram of a resource switching method according to an embodiment of this application.

[0312] Assuming a switch from BWP1 to BWP2, or from BWP2 to BWP1, the fixed first bit number x = 17 bits, where the fixed first bit number is the maximum FDRA field bit number, i.e., the maximum FDRA field size, and:

[0313] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type A resource allocation type, directly based on sub-PRB resource allocation instructions (REG method), with a REresource unit size of Q (in REs), and a total number of REGs: The bit overhead of the FDRA field in DCI is as follows:

[0314] Assuming BWP 1 size is 30RB and Q = 40, then the FDRA field size corresponding to BWP 1 is 9 bits.

[0315] BWP 2 is configured or determined to use RB-based resource allocation and uses type 1 resource allocation type.

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

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

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

[0319] Assuming BWP 2 size is 100RB, L RB =64, then the FDRA field size corresponding to BWP 2 is 7+6=13 bits.

[0320] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2C:

[0321] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 9 bits. Assuming the FDRA field during transmission is as shown in Figure 2C, it is 0 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 2), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (9 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2C, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 8 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 8 redundant bits. During parsing, the FDRA field is 0 00000000 1001 1001.

[0322] To switch from BWP2 to BWP1, see Schedule 2 in Figure 2C:

[0323] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 13 bits. Assuming the FDRA field during transmission is as shown in Figure 2C, it is 1 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 1), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (13 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2C, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 4 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 4 redundant bits. During parsing, the FDRA field is 0 0001 0010 1001 1001.

[0324] Figure 2D is a schematic diagram of a resource switching method according to an embodiment of this application.

[0325] Assuming a switch from BWP1 to BWP2, or from BWP2 to BWP1, the fixed first bit number x = 17 bits, where the fixed first bit number is the maximum FDRA field bit number, i.e., the maximum FDRA field size, and:

[0326] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type C resource allocation type, directly based on sub-PRB resource allocation indication (RIV method).

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

[0328] RIV for Start RB position RE start Bit overhead:

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

[0330] Assuming BWP 1 size is 30RB, L RE =64, then the FDRA field size corresponding to BWP 1 is 9 + 6 = 15 bits.

[0331] BWP 2 is configured or determined to use RB-based resource allocation, and uses type 0 resource allocation type. The RB resource unit size is P (in RBs), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0332] Assuming BWP 2 size is 100RB and P = 10, then the FDRA field size corresponding to BWP 2 is 10 bits.

[0333] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2D:

[0334] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2D, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 2), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2D, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 2 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 2 redundant bits. During parsing, the FDRA field is 0 0011 0010 1001 1001.

[0335] To switch from BWP2 to BWP1, see Schedule 2 in Figure 2D:

[0336] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 10 bits. Assuming the FDRA field during transmission is as shown in Figure 2D, it is 10 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 1), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (10 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2D, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 7 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 7 redundant bits. During parsing, the FDRA field is 0 00000010 1001 1001.

[0337] Figure 2E is a schematic diagram of a resource switching method according to an embodiment of this application.

[0338] Assuming a switch from BWP1 to BWP2, or from BWP2 to BWP1, the fixed first bit number x = 17 bits, where the fixed first bit number is the maximum FDRA field bit number, i.e., the maximum FDRA field size, and:

[0339] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type A resource allocation type, directly based on sub-PRB resource allocation instructions (REG method), with a REresource unit size of Q (in REs), and a total number of REGs: The bit overhead of the FDRA field in DCI is as follows:

[0340] Assuming BWP 1 size is 30RB and Q = 24, then the FDRA field size corresponding to BWP 1 is 15 bits.

[0341] BWP 2 is configured or determined to use a sub-PRB-based resource allocation method and a type C resource allocation type.

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

[0343] RIV for Start RB position RE start Bit overhead:

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

[0345] Assuming BWP 2 size is 100RB, L RE =64, then the FDRA field size corresponding to BWP 2 is 11 + 6 = 17 bits.

[0346] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2E:

[0347] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2E, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 2), but rather according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2E, when the UE parses the FDRA field in the DCI on the switched BWP, it can pad the high 2 bits of the transmitted FDRA field with zeros. Therefore, the FDRA field size during parsing... The field size remains the same as the FDRA field during transmission, except for 2 redundant bits. During parsing, the FDRA field is 0 0011 0010 1001 1001.

[0348] Switching from BWP2 to BWP1, see Schedule 2 in Figure 2E:

[0349] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 17 bits. Assuming the FDRA field during transmission is as shown in Figure 2E, it is 1 1011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs based on the Bandwidth part indicator field, it needs to uniformly determine the FDRA field size according to the maximum FDRA field bit count when interpreting the FDRA field. That is, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it does not calculate the FDRA field size according to the current active BWP (i.e., BWP 1), but rather determines the FDRA field size according to the maximum FDRA field bit count. Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (17 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is equal to the FDRA field size determined during parsing (17 bits) (i.e., the fixed first bit count). As shown in Figure 2E, when the UE parses the FDRA field in the DCI on the switched BWP, it does not need to pad the transmitted FDRA field with zeros; the FDRA field during parsing and the FDRA field during transmission are the same. The fields are the same, both being 1 1011 0010 1001 1001.

[0350] In some embodiments, the first number of bits is determined based on the second BWP.

[0351] As an example, assuming the first information is DCI, and DCI includes an FDRA field, considering the different BWP sizes and / or different resource allocation methods based on Sub-PRB and / or different resource allocation granularities adopted by different BWPs, the size of the FDRA field may differ. Therefore, when the UE parses the FDRA field in the DCI on the handed-over BWP, it uniformly determines the size of the FDRA field according to the first number of bits determined based on the handed-over BWP (i.e., the second BWP). Optionally, the size of the FDRA field can be determined as the first number of bits determined based on the handed-over BWP. In this case, the determined size of the FDRA field is not fixed and varies with the size of the current active BWP (i.e., the handed-over active BWP).

[0352] In some embodiments, the first number of bits is determined based on the second BWP. If the size of the first information is less than the first number of bits, the terminal 101 may also perform zero-padding on the first information based on the first number of bits, so that the size of the first information after processing is equal to the first number of bits; or, if the size of the first information is less than the first number of bits, the terminal may perform pruning on the first information based on the first number of bits, so that the size of the first information after processing is equal to the first number of bits.

[0353] As an example, if a Bandwidth part indicator field is configured in the DCI format, which indicates which BWP the UE uses for data transmission or reception, and the UE supports DCI-based BWP handover (i.e., the UE can switch the currently used BWP based on the value of the Bandwidth part indicator field in the DCI format), and the newly indicated UL BWP / DL BWP by the Bandwidth part indicator field is different from the active UL BWP / DL BWP, and the DCI includes an FDRA field, which indicates the location and size of the frequency domain resources allocated to the UE, then the gNB can send the DCI to the UE to instruct the UE to perform BWP handover and to help the UE determine the frequency domain resources allocated to the UE on the new BWP. Considering the differences in BWP size and / or Sub-PRB-based resource allocation methods and / or the different granularities of resource allocation used by different BWPs, which may result in different FDRA field sizes, the UE should perform the following operations when parsing the FDRA field in the DCI on the switched BWP after receiving the DCI from the gNB, and set the active UL BWP / DL BWP to the UL BWP / DL BWP newly indicated by the Bandwidth part indicator field in the DCI format:

[0354] For the FDRA field in the DCI, if the actual bit width y carried by the FDRA field in the DCI transmitted by the gNB is less than the bit width x (i.e., the first number of bits) of the FDRA field determined by the BWP after handover based on the Bandwidth part indicator field in the current DCI (i.e., the DCI transmitted by the gNB), then when the UE parses the FDRA field in the DCI on the BWP after handover, it needs to first pad some (yx) bits of the FDRA field bit width x with zeros. The processed FDRA field bit width x is equal to the bit width y, and then the FDRA field is parsed. This some (yx) bit is determined based on the protocol preset and can be either the high (yx) bit or the low (yx) bit.

[0355] If the actual bit width y carried by the FDRA field in the DCI sent by the gNB is less than the bit width x (i.e., the first number of bits) of the FDRA field determined by the BWP after handover based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), then when the UE parses the FDRA field in the DCI on the BWP after handover, it needs to first perform a pruning process on a certain (xy) bit of the FDRA field bit width x. The pruned FDRA field bit width x is equal to the bit width y, and then the FDRA field is parsed. This certain (xy) bit is determined based on the protocol preset and can be either the high (xy) bit or the low (xy) bit.

[0356] If the actual bit width y carried by the FDRA field in the DCI sent by the gNB is equal to the bit width x (i.e., the first number of bits) of the FDRA field determined by the BWP after the handover based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), then when the UE parses the FDRA field in the DCI on the BWP after the handover, it can directly parse the FDRA field without any processing.

[0357] In the above process, the actual bit width carried by the FDRA field in the DCI sent by the gNB is determined based on the current active BWP, specifically based on the size of the current active BWP and / or the resource allocation method and / or the resource allocation granularity corresponding to the current active BWP (see the relevant description of the determination process of the maximum FDRA field size above).

[0358] To more clearly illustrate the resource switching process when the first number of bits is fixed, an example is provided below.

[0359] Figure 2F is a schematic diagram of a resource switching method according to an embodiment of this application.

[0360] Suppose we switch from BWP 1 to BWP 2, or from BWP 2 to BWP 1, and:

[0361] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type B resource allocation type. First, an RB-based resource allocation instruction (type 0 method) is given. The RB resource unit size is P×12 (unit: RE), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0362] Next, resource allocation instructions (REG method) based on sub-PRB are executed, with the REresource unit size being Q (in REs), and the total number of REGs being: The bit overhead of the FDRA field in DCI is as follows:

[0363] Assuming BWP 1 size is 30RB, P=10, Q=24, then the FDRA field size corresponding to BWP 1 is 15 bits.

[0364] BWP 2 is configured or determined to use RB-based resource allocation, and uses type 0 resource allocation type. The RB resource unit size is P (in RBs), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0365] Assuming BWP 2 size is 100RB and P = 10, then the FDRA field size corresponding to BWP 2 is 10 bits.

[0366] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2F:

[0367] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2F, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it determines the FDRA field size according to the current active BWP (i.e., BWP 2). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 10 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is greater than the FDRA field size determined during parsing (10 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2F, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the field, the high 5 bits of the transmitted FDRA field can be pruned to obtain a 10-bit FDRA field. As shown in Figure 2F, the 10-bit FDRA field is 10 1001 1001. Therefore, by pruning the high 5 bits, frequency domain scheduling instructions can be given to the current active BWP (i.e., BWP 2) based on the 10-bit FDRA field.

[0368] To switch from BWP2 to BWP1, see Schedule 2 in Figure 2F:

[0369] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 10 bits. Assuming the FDRA field during transmission is as shown in Figure 2F, it is 10 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it determines the FDRA field size according to the current active BWP (i.e., BWP 1). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 15 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (10 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (15 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2F, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the FDRA field, the high 5 bits of the transmitted FDRA field can be padded with zeros to obtain a 15-bit FDRA field. As shown in Figure 2F, the 15-bit FDRA field is 000 0010 1001 1001. Therefore, by padding the high 5 bits with zeros, frequency domain scheduling instructions for the current active BWP (i.e., BWP 1) can be implemented based on the 15-bit FDRA field. Furthermore, the size of the parsed FDRA field remains the same as the transmitted FDRA field, with only 5 redundant bits.

[0370] Figure 2G is a schematic diagram illustrating a resource switching method according to an embodiment of this application.

[0371] Suppose we switch from BWP 1 to BWP 2, or from BWP 2 to BWP 1, and:

[0372] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type A resource allocation type, directly based on sub-PRB resource allocation instructions (REG method), with a REresource unit size of Q (in REs), and a total number of REGs: The bit overhead of the FDRA field in DCI is as follows:

[0373] Assuming BWP 1 size is 30RB and Q = 40, then the FDRA field size corresponding to BWP 1 is 9 bits.

[0374] BWP 2 is configured or determined to use RB-based resource allocation and uses type 1 resource allocation type.

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

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

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

[0378] Assuming BWP 2 size is 100RB, L RB =64, then the FDRA field size corresponding to BWP 2 is 7+6=13 bits.

[0379] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2G:

[0380] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 9 bits. Assuming the FDRA field during transmission is as shown in Figure 2G, it is 1 0100 1100. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it determines the FDRA field size according to the current active BWP (i.e., BWP 2). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 13 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (9 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (13 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2G, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the FDRA field, the high 4 bits of the transmitted FDRA field can be padded with zeros to obtain a 13-bit FDRA field. As shown in Figure 2G, the 13-bit FDRA field is 0 0001 0100 1100. Therefore, by padding the high 4 bits with zeros, frequency domain scheduling instructions for the current active BWP (i.e., BWP 2) can be implemented based on the 13-bit FDRA field. Furthermore, the size of the parsed FDRA field remains the same as the transmitted FDRA field, with only a 4-bit redundancy.

[0381] Switching from BWP2 to BWP1, see Schedule 2 in Figure 2G:

[0382] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 13 bits. Assuming the FDRA field during transmission is as shown in Figure 2G, it is 1 1001 0100 1100. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it determines the FDRA field size according to the current active BWP (i.e., BWP 1). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 9 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (13 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is greater than the FDRA field size determined during parsing (9 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2G, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the field, the high 4 bits of the transmitted FDRA field can be pruned to obtain a 9-bit FDRA field. As shown in Figure 2G, the 9-bit FDRA field is 1 0100 1100. Thus, by pruning the high 4 bits, frequency domain scheduling instructions can be given to the current active BWP (i.e., BWP 1) based on the 9-bit FDRA field.

[0383] Figure 2H is a schematic diagram of a resource switching method according to an embodiment of this application.

[0384] Suppose we switch from BWP 1 to BWP 2, or from BWP 2 to BWP 1, and:

[0385] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type C resource allocation type, directly based on sub-PRB resource allocation indication (RIV method).

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

[0387] RIV for Start RB position RE start Bit overhead:

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

[0389] Assuming BWP 1 size is 30RB, L RE =64, then the FDRA field size corresponding to BWP 1 is 9 + 6 = 15 bits.

[0390] BWP 2 is configured or determined to use RB-based resource allocation, and uses type 0 resource allocation type. The RB resource unit size is P (in RBs), and the total number of RBGs is: The bit overhead of the FDRA field in DCI is as follows:

[0391] Assuming BWP 2 size is 100RB and P = 10, then the FDRA field size corresponding to BWP 2 is 10 bits.

[0392] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2H:

[0393] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2H, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it determines the FDRA field size according to the current active BWP (i.e., BWP 2). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 10 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is greater than the FDRA field size determined during parsing (10 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2H, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the field, the high 5 bits of the transmitted FDRA field can be pruned to obtain a 10-bit FDRA field. As shown in Figure 2H, the 10-bit FDRA field is 10 1001 1001. Therefore, by pruning the high 5 bits, frequency domain scheduling instructions can be given to the current active BWP (i.e., BWP 2) based on the 10-bit FDRA field.

[0394] Switching from BWP2 to BWP1, see Schedule 2 in Figure 2H:

[0395] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 10 bits. Assuming the FDRA field during transmission is as shown in Figure 2H, it is 10 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it determines the FDRA field size according to the current active BWP (i.e., BWP 1). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 15 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (10 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (15 bits) (i.e., the bit width of the FDRA field determined based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2H, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the FDRA field, the high 5 bits of the transmitted FDRA field can be padded with zeros to obtain a 15-bit FDRA field. As shown in Figure 2H, the 15-bit FDRA field is 000 0010 1001 1001. Therefore, by padding the high 5 bits with zeros, frequency domain scheduling instructions for the current active BWP (i.e., BWP 1) can be implemented based on the 15-bit FDRA field. Furthermore, the size of the parsed FDRA field remains the same as the transmitted FDRA field, with only 5 redundant bits.

[0396] Figure 2I is a schematic diagram of a resource switching method according to an embodiment of this application.

[0397] Suppose we switch from BWP 1 to BWP 2, or from BWP 2 to BWP 1, and:

[0398] BWP 1 is configured or determined to use a sub-PRB-based resource allocation method, and adopts type A resource allocation type, directly based on sub-PRB resource allocation instructions (REG method), with a REresource unit size of Q (in REs), and a total number of REGs: The bit overhead of the FDRA field in DCI is as follows:

[0399] Assuming BWP 1 size is 30RB and Q = 24, then the FDRA field size corresponding to BWP 1 is 15 bits.

[0400] BWP 2 is configured or determined to use a sub-PRB-based resource allocation method and a type C resource allocation type.

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

[0402] RIV for Start RB position RE start Bit overhead:

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

[0404] Assuming BWP 2 size is 100RB, L RE =64, then the FDRA field size corresponding to BWP 2 is 11 + 6 = 17 bits.

[0405] To switch from BWP 1 to BWP 2, see Schedule 1 in Figure 2I:

[0406] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 1). Based on the above description, if switching from BWP 1 to BWP 2, the size of the FDRA field calculated according to BWP 1 during transmission is 15 bits. Assuming the FDRA field during transmission is as shown in Figure 2I, it is 011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches the BWP according to the Bandwidth part indicator field, it needs to determine the FDRA field size according to the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 2), it determines the FDRA field size according to the current active BWP (i.e., BWP 2). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 2 is 17 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (15 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is less than the FDRA field size determined during parsing (17 bits) (i.e., the bit width of the FDRA field determined by the switched BWP based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2I, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the FDRA field, the high 2 bits of the transmitted FDRA field can be padded with zeros to obtain a 17-bit FDRA field. As shown in Figure 2I, the 17-bit FDRA field is 0 0011 0010 1001 1001. Therefore, by padding the high 2 bits with zeros, frequency domain scheduling instructions for the current active BWP (i.e., BWP 2) can be implemented based on the 17-bit FDRA field. Furthermore, the size of the parsed FDRA field remains the same as the transmitted FDRA field, with only a 2-bit redundancy.

[0407] To switch from BWP2 to BWP1, see Schedule 2 in Figure 2I:

[0408] When scheduling the current DCI (i.e., the DCI in the gray square in scheduling 1), the size of the FDRA field during transmission is still calculated according to the current active BWP (i.e., BWP 2). Based on the above description, if switching from BWP 2 to BWP 1, the size of the FDRA field calculated according to BWP 2 during transmission is 17 bits. Assuming the FDRA field during transmission is as shown in Figure 2I, it is 1 1011 0010 1001 1001. However, when the UE receives the DCI scheduling information and switches BWPs according to the Bandwidth part indicator field, it needs to determine the FDRA field size based on the current active BWP (i.e., BWP 2) when interpreting the FDRA field. In other words, when the UE parses the FDRA field in the DCI on the switched BWP (i.e., BWP 1), it determines the FDRA field size according to the current active BWP (i.e., BWP 1). Based on the above description, the FDRA field size determined by the UE when parsing the FDRA field in the DCI on BWP 1 is 15 bits. At this time, the FDRA field size calculated according to BWP 1 during transmission (17 bits) (i.e., the actual bit width carried by the FDRA field in the DCI sent by the gNB) is greater than the FDRA field size determined during parsing (15 bits) (i.e., the bit width of the FDRA field determined by the switched BWP based on the Bandwidth part indicator field in the current DCI (i.e., the DCI sent by the gNB), which is also the first number of bits). Therefore, as shown in Figure 2I, the UE interprets the FDRA field in the DCI on the switched BWP... When parsing the field, the high 2 bits of the transmitted FDRA field can be removed to obtain a 15-bit FDRA field. As shown in Figure 2H, the 15-bit FDRA field is 011 0010 1001 1001. Therefore, by removing the high 2 bits, frequency domain scheduling instructions can be given to the current active BWP (i.e., BWP 1) based on the 10-bit FDRA field.

[0409] It should be noted that in the above examples and / or embodiments, if the Bandwidth part indicator field is not configured in the DCI format or the UE does not support DCI-based BWP handover, the FDRA field and frequency domain resources are determined within the BWP currently activated by the UE.

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

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

[0412] 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.

[0413] 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".

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

[0415] 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".

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

[0417] 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.

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

[0419] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0420] 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.”

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

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

[0423] 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.

[0424] 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.

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

[0426] 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.

[0427] 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.

[0428] 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.

[0429] 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.

[0430] The resource switching 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 S2101+S2103 may be implemented as an independent embodiment, step S2102+S2103 may be implemented as an independent embodiment, and so on, but not limited thereto.

[0431] In some embodiments, steps S2101 and S2102 are optional and may be omitted or substituted in different embodiments.

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

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

[0434] In step S3101, network device 102 sends an instruction message.

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

[0436] In step S3103, terminal 101 parses the first information based on the first number of bits on the second BWP to determine the frequency domain resources allocated to terminal 101; wherein the size of the first information is determined based on the first BWP.

[0437] In some embodiments, the terminal 101 parses the first information based on the first number of bits on the second BWP to determine the frequency domain resources allocated to the terminal 101; wherein the size of the first information is determined based on the first BWP.

[0438] The size of the first information is determined based on the first BWP, meaning that during transmission, the first information is determined based on the currently active BWP (i.e., the first BWP).

[0439] Wherein, the terminal 101 parses the first information based on the first number of bits on the second BWP, means that after receiving the first information, the terminal 101 parses the first information on the switched BWP (i.e., the second BWP) based on the first number of bits.

[0440] In other words, during transmission, the first information is determined based on the currently active BWP (first BWP), but during parsing, the first information is parsed by terminal 101 on the switched BWP (second BWP) based on the first number of bits.

[0441] Optionally, when the first information is DCI and the DCI includes an FDRA field, the size of the FDRA field in the DCI is determined based on the first BWP during transmission. However, when the terminal 101 parses the FDRA field in the DCI on the switched BWP, it needs to determine the size of the FDRA field in the DCI based on the first number of bits.

[0442] As an example, assuming the first information is DCI, and the DCI includes an FDRA field, the actual bit width carried by the FDRA field in the DCI sent by the gNB is determined based on the current active BWP. However, when the UE parses the FDRA field in the DCI on the BWP after handover, it needs to determine the size of the FDRA field in the DCI based on the first bit count, and then determine the frequency domain resources allocated to the UE.

[0443] 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.

[0444] Figure 3B is an interactive schematic diagram of a resource switching method according to an embodiment of this application. As shown in Figure 3B, this application embodiment relates to a resource switching method, which includes:

[0445] In step S3201, network device 102 sends an instruction message.

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

[0447] In step S3203, terminal 101 parses the first information based on the first number of bits on the second BWP to determine the frequency domain resources allocated to terminal 101; wherein the size of the first information is determined based on the first BWP.

[0448] In step S3204, the first number of bits is fixed, and the size of the first information is less than the first number of bits. The terminal 101 performs zero-padding on the first information based on the first number of bits, and the size of the first information after processing is equal to the first number of bits.

[0449] In some embodiments, the first number of bits is fixed.

[0450] As an example, assuming the first information is DCI, and the DCI includes an FDRA field, considering the different BWP sizes and / or the different resource allocation methods based on Sub-PRB and / or the different granularity of resource allocation used by different BWPs, the size of the FDRA field may differ. Therefore, when the UE parses the FDRA field in the DCI on the BWP after handover, it uniformly determines the size of the FDRA field according to a fixed first bit number. Optionally, the size of the FDRA field can be determined to be a fixed first bit number. In this case, the determined size of the FDRA field is fixed and does not change with BWP handover. The fixed first bit number can be the maximum FDRA field bit number, i.e., the maximum FDRA field size.

[0451] In some embodiments, the number of the first bits is fixed;

[0452] The aforementioned fixed first bit number is determined based on the BWP size and resource allocation method supported by the aforementioned terminal, and the aforementioned fixed first bit number is the maximum value among multiple sizes corresponding to the second information supported by the aforementioned terminal;

[0453] The second piece of information is used to determine the frequency domain resources allocated to the terminal.

[0454] In other words, when the number of first bits is fixed, the method for determining the fixed number of first bits is as follows: based on the BWP size and resource allocation method supported by the terminal, multiple sizes corresponding to the second information supported by the terminal under the above BWP size and resource allocation method are pre-calculated, and the maximum value is selected as the first number of bits. The second information is used to determine the frequency domain resources allocated to the terminal.

[0455] Similarly, the second piece of information mentioned above can be DCI, or it can be other downlink signaling, etc.

[0456] Similarly, when the second piece of information mentioned above can be a DCI, the DCI includes the FDRA field.

[0457] Optionally, if the second information is a DCI and the DCI includes an FDRA field, then the multiple sizes corresponding to the second information are the multiple sizes of the FDRA field.

[0458] 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.

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

[0460] In step S3301, network device 102 sends an instruction message.

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

[0462] In step S3303, terminal 101 parses the first information based on the first number of bits on the second BWP to determine the frequency domain resources allocated to terminal 101; wherein the size of the first information is determined based on the first BWP.

[0463] In step S3304, the first bit count is determined based on the second BWP. The size of the first information is less than the first bit count. The terminal 101 performs zero-padding on the first information based on the first bit count. The size of the first information after processing is equal to the first bit count.

[0464] In some embodiments, the first number of bits is determined based on the second BWP.

[0465] As an example, assuming the first information is DCI, and DCI includes an FDRA field, considering the different BWP sizes and / or different resource allocation methods based on Sub-PRB and / or different resource allocation granularities adopted by different BWPs, the size of the FDRA field may differ. Therefore, when the UE parses the FDRA field in the DCI on the handed-over BWP, it uniformly determines the size of the FDRA field according to the first number of bits determined based on the handed-over BWP (i.e., the second BWP). Optionally, the size of the FDRA field can be determined as the first number of bits determined based on the handed-over BWP. In this case, the determined size of the FDRA field is not fixed and varies with the size of the current active BWP (i.e., the handed-over active BWP).

[0466] In some embodiments, the first number of bits is determined based on the second BWP. If the size of the first information is less than the first number of bits, the terminal 101 can perform zero-padding on the first information based on the first number of bits, and the size of the first information after processing is equal to the first number of bits.

[0467] In step S3305, the first number of bits is determined based on the second BWP. The size of the first information is greater than the first number of bits. The terminal 101 performs a pruning process on the first information based on the first number of bits. The size of the first information after processing is equal to the first number of bits.

[0468] In some embodiments, the first number of bits is determined based on the second BWP. If the size of the first information is greater than the first number of bits, the terminal 101 can perform a pruning process on the first information based on the first number of bits, and the size of the first information after processing is equal to the first number of bits.

[0469] 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.

[0470] The following is an exemplary description of the methods described in the above embodiments.

[0471] In some embodiments, when a UE performs a DCI-based BWP handover, the data scheduled by the DCI needs to be transmitted on the new BWP. In this case, when using a sub-PRB-based resource allocation method, the FDRA field size in the DCI determined based on the current active BWP may not be the same as the size required for the BWP to interpret the FDRA field due to at least one of the following reasons: the BWP size before and after the handover may not be the same; the resource allocation method corresponding to the BWP before and after the handover may not be the same; or the resource allocation granularity corresponding to the BWP before and after the handover may not be the same. Therefore, it is necessary to consider how to align the FDRA field size in the DCI sent by the gNB with the size required for the UE to parse the FDRA field in the DCI on the new BWP, where the FDRA field size in the DCI sent by the gNB is determined based on the current active BWP (i.e., the BWP before the handover).

[0472] Option 1: Considering that at least one of the following reasons may lead to different FDRA field sizes: different BWP sizes, different resource allocation methods based on Sub-PRB, and different resource allocation granularities adopted by different BWPs, the number of bits reserved is uniformly based on the maximum possible FDRA field size, that is, the FDRA field does not change with BWP switching.

[0473] Optionally, if the Bandwidth part indicator field is configured in the DCI format, and the UE supports DCI-based BWP handover, and the new UL BWP / DL BWP indicated by the BWP indicator field is different from the active UL BWP / DL BWP, then the UE should perform the following operations when interpreting the FDRA field and set the active UL BWP / DL BWP to the new UL BWP / DL BWP indicated by the DCI format Bandwidth part indicator field.

[0474] For the FDRA field in the DCI format:

[0475] Reserve x bits according to the maximum possible FDRA field size.

[0476] In the DCI format, the FDRA field is determined based on the maximum bandwidth and / or resource allocation method, but for different BWPs, the bit width x of the FDRA field is consistent when it is interpreted in DCI.

[0477] Assuming the actual bit width of the DCI FDRA field transmitted by the gNB is determined by the current active BWP and is y bits, and the length of the DCI FDRA field during parsing by the switched BWP is always the reserved number of bits x bits, then:

[0478] If the actual bit width y carried in the active BWP DCI is less than the reserved number of bits x, then when the UE performs FDRA interpretation on the switched BWP, a certain (xy) bit in the DCI FDRA field is actually padded with zeros. This certain (xy) bit, determined based on the protocol preset, can be either the high (xy) bit or the low (xy) bit.

[0479] If the actual bit width y carried in the active BWP DCI is equal to the number of reserved bits x, and there are no redundant bits, the length of the DCI FDRA field sent by the gNB side and the length of the DCI FDRA field when the current active BWP is parsed are both x bits.

[0480] In some embodiments, the determination of the maximum FDRA field size is considered based on at least one of the following factors:

[0481] 1) BWP size supported by the terminal;

[0482] 2) Resource allocation methods corresponding to the BWP supported by the terminal;

[0483] 3) The resource allocation granularity corresponding to the BWP supported by the terminal.

[0484] Considering at least one of 1), 2), and 3), the length of the FDRA field depends on the size of the active BWP and the resource allocation method, wherein the resource allocation method includes, but is not limited to, one of the following:

[0485] I. Resource allocation method based on Sub-PRB:

[0486] Type A:

[0487] The bit overhead of the FDRA field is:

[0488] Wherein, the REresource unit size is Q (in RE), and the BWP size is...

[0489] Type B:

[0490] The bit overhead of the FDRA field is:

[0491] The REresource unit size is Q (in REs). For each RBG of size P×12, the total number of REGs is: BWP size is

[0492] Type C:

[0493] The bit overhead of the FDRA field is:

[0494] The total number of REs within BWP is: The RE unit has a length of L. RE.

[0495] Type D:

[0496] The bit overhead of the FDRA field is:

[0497] The total number of RBs within BWP is: The total number of REs within the allocated RB is: N RE =L RB ×12, RE unit length is L RE .

[0498] II. Resource allocation method based on RB:

[0499] Type0:

[0500] The bit overhead of the FDRA field is:

[0501] Wherein, the RB resource unit size is P (in RV), and the BWP size is... (Unit: RB)

[0502] Type 1:

[0503] The bit overhead of the FDRA field is:

[0504] The total number of RBs within BWP is: The length of the RB unit is L RB .

[0505] Based on the BWP size and resource allocation method that may be scheduled in all transmissions, all possible values ​​of FDRA field size under the above BWP size and resource allocation method are pre-calculated and compared, and the maximum value is selected as the maximum FDRA field size.

[0506] Option 2: The size of the FDRA field changes with the size of the current active BWP (i.e., the active BWP after the switch).

[0507] Optionally, if the Bandwidth part indicator field is configured in the DCI format, and the UE supports DCI-based BWP handover, and the new UL BWP / DL BWP indicated by the BWP indicator field is different from the active UL BWP / DL BWP, then the UE should perform the following operations when interpreting the FDRA field and set the active UL BWP / DL BWP to the new UL BWP / DL BWP indicated by the DCI format Bandwidth part indicator field:

[0508] For the FDRA field in the DCI format:

[0509] If the bit width x of the FDRA field determined by the BWP to which the current DCI Bandwidth part indicator field is switched (to be switched) is greater than the actual bit width y carried in the active BWP DCI, then when the UE interprets the FDRA on the switched BWP, it needs to pad some (xy) bits of the FDRA field bit width y with zeros until its size is the bit width x, and then interpret the DCI format FDRA field. This (xy) bit, determined by the protocol preset, can be either the high (xy) bit or the low (xy) bit.

[0510] If the bit width x of the FDRA field determined by the BWP to which the current DCI Bandwidth part indicator field is switched is less than or equal to the actual bit width y carried in the active BWP DCI, then when the UE interprets the FDRA on the switched BWP, it needs to prune a certain bit (yx) of the FDRA field bit width y until its size is the bit width x, and then interpret the DCI format FDRA field. This certain bit (yx) is determined based on the protocol preset and can be either the high bit (yx) or the lowest bit (yx).

[0511] It should be noted that for DCI format 0_3 / DCI format 1_3, and for FDRA fields containing multiple blocks, the above procedure applies to each block of the FDRA field respectively.

[0512] In some embodiments, if the Bandwidth part indicator field is not configured in the DCI format or the UE does not support DCI-based BWP handover, the FDRA field and frequency domain resources are determined within the BWP currently activated by the UE.

[0513] In some embodiments, unless contradictory, the optional implementations in this embodiment can be implemented as independent embodiments, and the optional implementations in this embodiment can also be combined arbitrarily. The technical features of different feasible implementations in this embodiment can be combined to form new optional implementations based on their inherent logical relationships.

[0514] 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.

[0515] 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.

[0516] 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.

[0517] 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).

[0518] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of this application. The terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, the 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 indication information sent by a network device, the indication information being used to instruct the terminal to switch from a first portion bandwidth BWP to a second BWP, the first BWP being the currently active BWP; the transceiver module 4101 is also used to receive first information sent by the network device on the first BWP; the processing module 4102 is used to determine the frequency domain resources allocated to the terminal on the second BWP based on the first information. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., S2101, S2102, S3101, S3102, S3201, S3202, S3301, S3302, 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 is used to execute at least one of the other steps (e.g., S2103, S3103, S3203, S3204, S3303, S3304, S3305, but not limited thereto) performed by the terminal 101 in any of the above methods, which will not be elaborated here.

[0519] Figure 4B is a schematic diagram of the network device proposed in an embodiment of this application. The network device 4200 is used to perform 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 indication information to a terminal, the indication information being used to instruct the terminal to switch from a first portion bandwidth BWP to a second BWP, the first BWP being the currently active BWP; the transceiver module 4201 is also used to send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP based on the first information. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., S2101, S2102, S3101, S3102, S3201, S3202, S3301, S3302, etc., 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.

[0520] 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.

[0521] 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.

[0522] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0523] 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.

[0524] 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.

[0525] 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 method (e.g., steps S2101, S2102, S3101, S3102, S3201, S3202, S3301, S3302, 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. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0526] 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.

[0527] 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.

[0528] 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.

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

[0530] 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.

[0531] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S3101, S3102, S3201, S3202, S3301, S3302, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing 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 the other steps.

[0532] 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.

[0533] 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.

[0534] 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.

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

Claims

A resource switching method, characterized in that, The method is executed by a terminal, and the method includes: The terminal receives an indication message sent by a network device, the indication message being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP; Receive the first information sent by the network device on the first BWP; Based on the first information, the frequency domain resources allocated to the terminal on the second BWP are determined. The method according to claim 1, characterized in that, Includes at least one of the following: The first BWP and the second BWP are of different sizes; The resource allocation methods corresponding to the first BWP and the second BWP are different; The resource allocation granularity corresponding to the first BWP and the second BWP is different; The resource allocation method includes at least one of the following: The resource allocation method based on sub-PRBs uses resource units (REs) as the basic resource granularity. The resource allocation method based on resource blocks (RB) uses RB as the basic resource granularity. The method according to claim 2, characterized in that, 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. The method according to any one of claims 1-3, characterized in that, The step of determining the frequency domain resources allocated to the terminal on the second BWP based on the first information includes: On the second BWP, the first information is parsed based on the first number of bits to determine the frequency domain resources allocated to the terminal; The size of the first information is determined based on the first BWP. The method according to claim 4, characterized in that, The first number of bits is fixed; or, The first number of bits is determined based on the second BWP. The method according to claim 5, characterized in that, The first number of bits is fixed; The fixed first bit number is determined based on the BWP size and resource allocation method supported by the terminal, and the fixed first bit number is the maximum value among multiple sizes corresponding to the second information supported by the terminal; The second information is used to determine the frequency domain resources allocated to the terminal. The method according to any one of claims 4-6, characterized in that, The first number of bits is fixed; the method further includes: The size of the first information is less than the number of bits. The first information is padded with zeros based on the number of bits, and the size of the first information after processing is equal to the number of bits. The method according to claim 4 or 5, characterized in that, The first number of bits is determined based on the second BWP; the method further includes: If the size of the first information is less than the first number of bits, the first information is padded with zeros based on the first number of bits, and the size of the processed first information is equal to the first number of bits; or... The size of the first information is greater than the first number of bits. The first information is pruned based on the first number of bits, and the size of the first information after the pruning is equal to the first number of bits. A resource switching method, characterized in that, The method is performed by a network device, and the method includes: Send indication information to the terminal, the indication information being used to instruct the terminal to switch from a first portion bandwidth BWP to a second BWP, the first BWP being the currently active BWP; Send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP. The method according to claim 9, characterized in that, Includes at least one of the following: The first BWP and the second BWP are of different sizes; The resource allocation methods corresponding to the first BWP and the second BWP are different; The resource allocation granularity corresponding to the first BWP and the second BWP is different; The resource allocation method includes at least one of the following: The resource allocation method based on sub-PRBs uses resource units (REs) as the basic resource granularity. The resource allocation method based on resource blocks (RB) uses RB as the basic resource granularity. The method according to claim 10, characterized in that, 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. The method according to any one of claims 9-11, characterized in that, The fixed first information is parsed on the second BWP based on the first number of bits, and the fixed first information is used to determine the frequency domain resources allocated to the terminal; The size of the first information is determined based on the first BWP. The method according to claim 12, characterized in that, The first number of bits is fixed; or, The first number of bits is determined based on the second BWP. The method according to claim 13, characterized in that, The first number of bits is fixed; The first number of bits is determined based on the BWP size and resource allocation method supported by the terminal, and the first number of bits is the maximum value among multiple sizes corresponding to the second information supported by the terminal; The second information is used to determine the frequency domain resources allocated to the terminal. A terminal, characterized in that, The terminal includes: The transceiver module is used to receive indication information sent by the network device. The indication information is used to instruct the terminal to switch from the first bandwidth BWP to the second BWP, where the first BWP is the currently active BWP. The transceiver module is further configured to receive first information sent by the network device on the first BWP; The processing module is configured to determine, based on the first information, the frequency domain resources allocated to the terminal on the second BWP. A network device, characterized in that, The network device includes: The transceiver module is used to send indication information to the terminal, the indication information being used to instruct the terminal to switch from a first bandwidth BWP to a second BWP, the first BWP being the currently active BWP; The transceiver module is further configured to send first information to the terminal, the first information being used by the terminal to determine the frequency domain resources allocated to the terminal on the second BWP. A terminal, characterized in that, The terminal includes: One or more processors; The terminal is used to execute the resource switching method according to any one of claims 1-8. A network device, characterized in that, The network device includes: One or more processors; The network device is used to execute the resource switching method according to any one of claims 9-14. A communication device, characterized in that, The communication device is used to execute the resource switching method according to any one of claims 1-8 and 9-14. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the resource switching method according to any one of claims 1-8, and the network device is configured to implement the resource switching method according to any one of claims 9-14. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the resource switching method as described in any one of claims 1-8 and 9-14. 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, the resource switching method of any one of claims 1-8 and 9-14 is implemented.

Images