CN116456470A - Method and device for determining frequency domain resources, terminal and network equipment - Google Patents

Abstract

The application discloses a method and a device for determining frequency domain resources, a terminal and network equipment, wherein the method comprises the following steps: the method comprises the steps that a terminal receives Downlink Control Information (DCI) sent by network equipment, wherein the DCI carries a frequency domain resource allocation domain, and the size of the frequency domain resource allocation domain is determined based on a first bandwidth or a second bandwidth; the DCI indicates a slot offset value; and the terminal determines the frequency domain resource of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation domain.

Description

A method and device for determining frequency domain resources, terminal, and network equipment

Technical Field

The present application relates to the field of wireless communication technology, and in particular to a method and apparatus for determining frequency domain resources, a terminal, and a network device.

Background Art

At present, the terminal can only support one activated bandwidth part (Band Width Part, BWP), and the bandwidth size of this activated bandwidth part is fixed. The size of the frequency domain resource allocation (Frequency Domain Resource Assignment, FDRA) field in the downlink control information (Downlink Control Information, DCI) is also determined according to this fixed bandwidth size. For flexible duplex scenarios, an activated BWP with a dynamically changing bandwidth size can be configured for the terminal to dynamically adapt to the needs of business volume. However, if the current DCI size is designed, the DCI size of the same format of the terminal will be different. In addition, at a certain scheduling moment, the terminal does not know whether the physical shared channel scheduled by the DCI is located in a narrower bandwidth or a wider bandwidth. The terminal needs to detect two DCI sizes, which increases the number of terminal blind detections.

Summary of the invention

In order to solve the above technical problems, the embodiments of the present invention provide a method and apparatus for determining frequency domain resources, a terminal, a network device, a chip, and a computer-readable storage medium.

The method for determining frequency domain resources provided in the embodiment of the present application includes:

The terminal receives a DCI sent by a network device, where the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value;

The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation field.

The method for determining frequency domain resources provided in the embodiment of the present application includes:

The network device sends a DCI to the terminal, where the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value.

The device for determining frequency domain resources provided in an embodiment of the present application is applied to a terminal, and the device includes:

A receiving unit, configured to receive a DCI sent by a network device, wherein the DCI carries a frequency domain resource allocation domain, a size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value;

A determining unit is used to determine the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation domain.

The device for determining frequency domain resources provided in the embodiment of the present application is applied to a network device, and the device includes:

A sending unit is used to send DCI to a terminal, where the DCI carries a frequency domain resource allocation domain, and the size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value.

The terminal provided in the embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned methods for determining frequency domain resources.

The network device provided in the embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned methods for determining frequency domain resources.

The chip provided in the embodiment of the present application includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes any one of the above methods.

The core computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above methods.

In the technical solution of the embodiment of the present application, on the one hand, the size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth, that is, the size of the frequency domain resource allocation domain is fixed, so the size of the DCI is fixed. When the size of the BWP changes over time, since the size of the DCI is fixed, the terminal does not need to perform additional blind detection. On the other hand, the terminal determines which bandwidth to use to interpret the frequency domain resource allocation domain according to the time slot offset value in the DCI, so that different bandwidth sizes can be scheduled using the same frequency domain resource allocation domain.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

FIG2 is a schematic diagram of frequency domain resource distribution of a TDD band;

FIG3 is a schematic diagram of a flow chart of a method for determining frequency domain resources provided in an embodiment of the present application;

FIG4 is a schematic diagram of the first structure of a device for determining frequency domain resources provided in an embodiment of the present application;

FIG5 is a second schematic diagram of the structure of the device for determining frequency domain resources provided in an embodiment of the present application;

FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.

DETAILED DESCRIPTION

The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in Fig. 1, the communication system 100 may include a terminal 110 and a network device 120. The network device 120 may communicate with the terminal 110 via an air interface. The terminal 110 and the network device 120 support multi-service transmission.

It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine Type Communications (eMTC) system, 5G communication system (also called New Radio (NR) communication system), or future communication systems, etc.

In the communication system 100 shown in Fig. 1, the network device 120 may be an access network device that communicates with the terminal 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal 110 (eg, UE) located in the coverage area.

The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

The terminal 110 may be any terminal, including but not limited to a terminal connected to the network device 120 or other terminals by wire or wireless connection.

For example, the terminal 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolution network, etc.

The terminal 110 may be used for device to device (D2D) communication.

The wireless communication system 100 may also include a core network device 130 for communicating with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

The various functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

For example, the terminal establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

FIG1 exemplarily shows a base station, a core network device and two terminals. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminals within its coverage area, which is not limited in the embodiments of the present application.

It should be noted that FIG. 1 is only an example of the system to which the present application is applicable. Of course, the method shown in the embodiment of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and/or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiment of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, B can be obtained through C; it can also mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiment of the present application can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that the relationship between indicating and being indicated, configuring and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminals and network devices), and the present application does not limit its specific implementation method. For example, predefined may refer to the definition in the protocol. It should also be understood that in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

Currently, the terminal only supports one activated BWP with a fixed bandwidth size, and the base station uses DCI to dynamically schedule the physical shared channel. The size (i.e., bit length) of the frequency domain resource allocation field used to schedule the physical shared channel in the DCI is related to the bandwidth size of the activated BWP, which ensures that the size of the DCI of the same format in the same BWP of the terminal is fixed, reducing the terminal's blind detection complexity and terminal complexity.

In the flexible duplex scenario, as shown in Figure 2, uplink (UL) frequency domain resources can be added between the downlink (DL) frequency domain resources of the time division duplex band (TDD band) to improve the uplink throughput of the TDD band and reduce the uplink delay.

Since the terminal can only support one activated BWP, in order to support resource configuration under flexible duplex, an activated BWP with a dynamically changing bandwidth size can be configured for the terminal. However, if the size of the frequency domain resource allocation domain in the current DCI is designed, the DCI size of the same format of the terminal will be different. In addition, at a certain scheduling moment, the terminal does not know whether the physical shared channel scheduled by the DCI is located in a narrower bandwidth or a wider bandwidth. The terminal needs to detect two DCI sizes, resulting in an increase in the number of terminal blind detections.

To this end, the following technical solutions of the embodiments of the present application are proposed. The technical solutions of the embodiments of the present application propose a method for determining frequency domain resources, which implements the use of DCI with a fixed DCI size to indicate the frequency domain resource allocation of the physical shared channel when the bandwidth size of the BWP changes, thereby reducing the number of DCI sizes and blind detection complexity of the terminal.

To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

It should be noted that the physical shared channel in the embodiment of the present application can be a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) or a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH).

In the technical solution of this embodiment, for the network side, the size (i.e., bit length) of the frequency domain resource allocation field in the DCI is determined with reference to the first bandwidth or the second bandwidth, wherein the first bandwidth or the second bandwidth is associated with the same BWP or has an associated relationship. For the terminal side, the terminal determines the frequency domain resource position of the physical channel scheduled by the DCI according to the time slot offset value and the frequency domain resource allocation field in the DCI.

FIG3 is a flow chart of a method for determining frequency domain resources provided in an embodiment of the present application. As shown in FIG3 , the method for determining frequency domain resources includes the following steps:

Step 301: The terminal receives a DCI sent by a network device, where the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on a first bandwidth or a second bandwidth; and the DCI indicates a time slot offset value.

In an embodiment of the present application, a network device sends a DCI to a terminal, and accordingly, the terminal receives the DCI sent by the network device. The DCI carries a frequency domain resource allocation domain, the size of which is determined based on the first bandwidth or the second bandwidth, and the DCI indicates a time slot offset value. Here, the network device may be a base station.

In some optional implementations, the time slot offset value may be K0, where K0 represents the time slot interval between the DCI and the PDSCH scheduled by the DCI. The terminal may determine the time slot where the PDSCH scheduled by the DCI is located based on the time slot where the DCI is received and K0. Here, for ease of description, the time slot where the PDSCH scheduled by the DCI is located may be referred to as the scheduling time slot.

In some optional implementations, the time slot offset value may be K2, where K2 represents the time slot interval between the DCI and the PUSCH scheduled by the DCI. The terminal may determine the time slot where the PUSCH scheduled by the DCI is located based on the time slot where the DCI is received and K2. Here, for ease of description, the time slot where the PUSCH scheduled by the DCI is located may be referred to as the scheduling time slot.

In the embodiment of the present application, the size (ie, bit length) of the frequency domain resource allocation field in the DCI is determined based on the first bandwidth or the second bandwidth, and the first bandwidth is different from the second bandwidth. In some optional implementations, the first bandwidth is smaller than the second bandwidth.

Here, the first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resources; or, the first BWP or first frequency domain resource with the first bandwidth and the second BWP or second frequency domain resource with the second bandwidth are associated.

Step 302: The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation field.

Solution 1

Case 1-1: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a first manner.

Specifically, the first method includes at least one of the following:

The frequency domain resource allocation domain indicates a resource block group (RBG) allocated to the terminal, and the size of the RBG is determined based on the bandwidth of the BWP or frequency domain resource of the terminal in the time slot determined according to the time slot offset value;

The frequency domain resource allocation field includes a resource indication value (RIV), and the RIV is used to indicate a starting resource block (RB) and a continuous RB length.

As an example: the first method includes at least one of the following: 1) for frequency domain resource allocation type 0, the frequency domain resource allocation domain indicates the RGB allocated to the terminal, and the size of the RBG is based on the BWP of the terminal or the bandwidth of the frequency domain resource (i.e., the first bandwidth) in the time slot determined according to the time slot offset value. Determine; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation domain includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the continuous RB length is 1 physical resource block (PRB).

Case 1-2: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a second manner.

Specifically, the second method includes at least one of the following:

The frequency domain resource allocation field indicates an RBG allocated to the terminal, and a size of the RBG is determined based on the second bandwidth;

The frequency domain resource allocation field includes a RIV, and the RIV is used to indicate a start RB and a continuous RB length.

As an example: the second method includes at least one of the following: 1) for frequency domain resource allocation type 0, the frequency domain resource allocation field indicates the RBG allocated to the terminal, and the size of the RBG is determined based on the second bandwidth; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the continuous RB length is at least 1 PRB.

In some optional implementations, for a case where the frequency domain resource allocation field indicates an RBG allocated to a terminal,

If the number of first RBGs determined based on the first bandwidth is greater than or equal to the number of second RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal;

If the first number of RBGs determined based on the first bandwidth is less than the second number of RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal.

Further, in some optional embodiments, for the case where the first number of RBGs is less than the second number of RBGs, each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, the values of X1 and X2 are determined based on the first number of RBGs and the second number of RBGs, the number of the first part of bits is determined based on the value of X1, the value of X2, the first number of RBGs and the second number of RBGs, and the number of the second part of bits is determined based on the first number of RBGs and the first part of bits.

Further, in some optional implementations, for the case where the frequency domain resource allocation domain includes RIV,

if So,

otherwise,

in, L _RBs is the length of consecutive RBs, RB _start is the starting RB, is the first bandwidth, It is the second bandwidth.

Solution 2

Case 2-1: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel according to the first method.

Specifically, the first method includes at least one of the following:

The frequency domain resource allocation domain indicates the RGB allocated to the terminal, and the size of the RBG is determined based on the BWP of the terminal or the bandwidth of the frequency domain resource in the time slot determined according to the time slot offset value;

The frequency domain resource allocation field includes a RIV, and the RIV is used to indicate a start RB and a continuous RB length.

As an example: the first method includes at least one of the following: 1) for frequency domain resource allocation type 0, the frequency domain resource allocation field indicates the RGB allocated to the terminal, and the size of the RBG is based on the BWP of the terminal or the bandwidth of the frequency domain resources (i.e., the second bandwidth) in the time slot determined according to the time slot offset value. Determine; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the continuous RB length is 1 PRB.

Case 2-2: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel according to the third method.

Specifically, the third method includes at least one of the following:

The frequency domain resource allocation field indicates an RBG allocated to the terminal, and a size of the RBG is determined based on the first bandwidth;

The frequency domain resource allocation field includes a RIV, and the RIV is used to indicate a start RB and a continuous RB length.

As an example: the third method includes at least one of the following: 1) for frequency domain resource allocation type 0, the frequency domain resource allocation field indicates the RBG allocated to the terminal, and the size of the RBG is determined based on the first bandwidth; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the continuous RB length is 1 PRB.

In some optional implementations, for a case where the frequency domain resource allocation field indicates an RBG allocated to a terminal,

If the second number of RBGs determined based on the second bandwidth is greater than or equal to the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal;

If the second number of RBGs determined based on the second bandwidth is less than the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal.

Further, in some optional embodiments, for the case where the number of the second RBGs is less than the number of the first RBGs, each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, the values of X1 and X2 are determined based on the number of the first RBGs and the number of the second RBGs, the number of the first part of bits is determined based on the value of X1, the value of X2, the first number of RBGs and the second number of RBGs, and the number of the second part of bits is determined based on the number of the second RBGs and the number of the first part of bits.

The technical solution of the embodiment of the present application is that, on the one hand, the size of the frequency domain resource allocation domain is determined based on one of the first bandwidth and the second bandwidth, that is, the size of the frequency domain resource allocation domain is fixed, so the size of the DCI is fixed. When the size of the BWP changes over time, since the size of the DCI is fixed, the terminal does not need to perform additional blind detection. On the other hand, the terminal determines which bandwidth to use to interpret the frequency domain resource allocation domain according to the time slot offset value in the DCI, so that different bandwidth sizes can be scheduled using the same frequency domain resource allocation domain.

The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

Application example 1: Determine the bit length of the frequency domain resource allocation field in the DCI with reference to a smaller bandwidth size.

The bit length of the frequency domain resource allocation field in the DCI is related to the first bandwidth, and the first bandwidth is smaller than the second bandwidth. The first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or the first BWP or first frequency domain resource with the first bandwidth and the second BWP or second frequency domain resource with the second bandwidth are associated.

The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI according to the time slot offset value indicated by the DCI and the frequency domain resource allocation field in the DCI. Here, the time slot offset value in the DCI is used to indicate the scheduling time slot.

Case 1-1: If the BWP or frequency domain resources of the terminal have the first bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel according to the first method.

It should be noted that the BWP or frequency domain resources of the terminal here have a first bandwidth, which may be: the BWP or frequency domain resources of the terminal include the first bandwidth and the second bandwidth, or the BWP or frequency domain resources of the terminal are the first BWP or first frequency domain resources with the first bandwidth.

Specifically, the first method includes at least one of the following:

1) For frequency domain resource allocation type 0, the frequency domain resource allocation field indicates the RGB allocated to the terminal, and the size of the RBG is determined based on the BWP of the terminal or the bandwidth of the frequency domain resource (i.e., the first bandwidth) in the time slot determined according to the time slot offset value;

2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the length of continuous RBs is 1 PRB.

Case 1-2: If the BWP or frequency domain resources of the terminal have the second bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel according to the second method.

It should be noted that the BWP or frequency domain resources of the terminal here have a second bandwidth, which can be: the BWP or frequency domain resources of the terminal include the first bandwidth and the second bandwidth, or the BWP or frequency domain resources of the terminal are the second BWP or second frequency domain resources with the second bandwidth.

Specifically, the second method includes at least one of the following:

1) For frequency domain resource allocation type 0, the frequency domain resource allocation field indicates an RBG allocated to the terminal, and a size of the RBG is determined based on the second bandwidth.

Specifically, if the first RBG number N1 determined according to the first bandwidth is greater than or equal to the second RBG number N2 determined according to the second bandwidth, the frequency domain resource allocation field uses each bit to indicate whether a corresponding RBG is allocated to the terminal.

If the first RBG number N1 determined according to the first bandwidth is less than the second RBG number N2 determined according to the second bandwidth, the frequency domain resource allocation domain uses each bit to indicate whether the corresponding one or more RBGs are allocated to the terminal. Among them, M bits correspond to X1 RBGs, N1-M bits correspond to X2 RBGs, and or

M·X1+(N1-M)·X2＝N2;

As an example: assuming N1=6, N2=10, then according to the above formula, X1=2, X2=1, M=4.

2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate a starting RB (RB _start ) and a continuous RB length (L _RBs ). Here, optionally, the granularity of the continuous RB length is at least 1 PRB.

Specifically, if So,

otherwise,

in, is the first bandwidth, It is the second bandwidth.

Application example 2: Determine the bit length of the frequency domain resource allocation field in the DCI with reference to a larger frequency domain bandwidth size.

The bit length of the frequency domain resource allocation field in the DCI is related to the second bandwidth, and the first bandwidth is smaller than the second bandwidth. The first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or the first BWP or first frequency domain resource with the first bandwidth and the second BWP or second frequency domain resource with the second bandwidth are associated.

The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI according to the time slot offset value indicated by the DCI and the frequency domain resource allocation field in the DCI. Here, the time slot offset value in the DCI is used to indicate the scheduling time slot.

Case 2-1: If the BWP or frequency domain resources of the terminal have the second bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel according to the first method.

It should be noted that the BWP or frequency domain resources of the terminal here have a second bandwidth, which can be: the BWP or frequency domain resources of the terminal include the first bandwidth and the second bandwidth, or the BWP or frequency domain resources of the terminal are the second BWP or second frequency domain resources with the second bandwidth.

Specifically, the first method includes at least one of the following:

1) For frequency domain resource allocation type 0, the frequency domain resource allocation field indicates the RGB allocated to the terminal, and the size of the RBG is determined based on the BWP of the terminal or the bandwidth of the frequency domain resource (i.e., the second bandwidth) in the time slot determined according to the time slot offset value;

2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the length of continuous RBs is 1 PRB.

Case 2-2: If the BWP or frequency domain resources of the terminal have the first bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel according to the third method.

It should be noted that the BWP or frequency domain resources of the terminal here have a first bandwidth, which may be: the BWP or frequency domain resources of the terminal include the first bandwidth and the second bandwidth, or the BWP or frequency domain resources of the terminal are the first BWP or first frequency domain resources with the first bandwidth.

Specifically, the third method includes at least one of the following:

1) For frequency domain resource allocation type 0, the frequency domain resource allocation field indicates an RBG allocated to the terminal, and the size of the RBG is determined based on the first bandwidth.

Specifically, if the second RBG number N2 determined according to the second bandwidth is greater than or equal to the first RBG number N1 determined according to the first bandwidth, the frequency domain resource allocation field uses each bit to indicate whether a corresponding RBG is allocated to the terminal.

If the second RBG number N2 determined according to the second bandwidth is less than the first RBG number N1 determined according to the first bandwidth, the frequency domain resource allocation domain uses each bit to indicate whether the corresponding one or more RBGs are allocated to the terminal. Among them, M bits correspond to X1 RBGs, N2-M bits correspond to X2 RBGs, and or

M·X1+(N2-M)·X2＝N1;

2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs. Here, optionally, the granularity of the length of continuous RBs is 1 PRB.

FIG. 4 is a schematic diagram of a structure of a device for determining frequency domain resources provided in an embodiment of the present application. The device is applied to a terminal. As shown in FIG. 4 , the device for determining frequency domain resources includes:

A receiving unit 401 is configured to receive a DCI sent by a network device, wherein the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on a first bandwidth or a second bandwidth; and the DCI indicates a time slot offset value;

The determining unit 402 is configured to determine the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation domain.

In an embodiment of the present application, the first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resources; or, the first BWP or first frequency domain resource with the first bandwidth and the second BWP or second frequency domain resource with the second bandwidth are associated.

Solution 1

Case 1-1: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the determination unit 402 determines the frequency domain resources of the physical shared channel in a first manner.

Specifically, the first method includes at least one of the following: 1) the frequency domain resource allocation domain indicates the RGB allocated to the terminal, and the size of the RBG is determined based on the BWP of the terminal or the bandwidth of the frequency domain resource in the time slot determined according to the time slot offset value; 2) the frequency domain resource allocation domain includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs.

Case 1-2: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the determination unit 402 determines the frequency domain resources of the physical shared channel in a second manner.

Specifically, the second method includes at least one of the following: 1) the frequency domain resource allocation domain indicates the RBG allocated to the terminal, and the size of the RBG is determined based on the second bandwidth; 2) the frequency domain resource allocation domain includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs.

In some optional implementations, for a case where the frequency domain resource allocation field indicates an RBG allocated to a terminal,

If the number of first RBGs determined based on the first bandwidth is greater than or equal to the number of second RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal;

If the first number of RBGs determined based on the first bandwidth is less than the second number of RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal.

Further, in some optional embodiments, for the case where the first number of RBGs is less than the second number of RBGs, each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, the values of X1 and X2 are determined based on the first number of RBGs and the second number of RBGs, the number of the first part of bits is determined based on the value of X1, the value of X2, the first number of RBGs and the second number of RBGs, and the number of the second part of bits is determined based on the first number of RBGs and the first part of bits.

Further, in some optional implementations, for the case where the frequency domain resource allocation domain includes RIV,

if So,

otherwise,

in, L _RBs is the length of consecutive RBs, RB _start is the starting RB, is the first bandwidth, It is the second bandwidth.

Solution 2

Case 2-1: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the determination unit 402 determines the frequency domain resources of the physical shared channel in the first way.

Specifically, the first method includes at least one of the following: 1) the frequency domain resource allocation domain indicates the RGB allocated to the terminal, and the size of the RBG is determined based on the BWP of the terminal or the bandwidth of the frequency domain resource in the time slot determined according to the time slot offset value; 2) the frequency domain resource allocation domain includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs.

Case 2-2: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the determination unit 402 determines the frequency domain resources of the physical shared channel according to the third method.

Specifically, the third method includes at least one of the following: 1) the frequency domain resource allocation domain indicates the RBG allocated to the terminal, and the size of the RBG is determined based on the first bandwidth; 2) the frequency domain resource allocation domain includes RIV, and the RIV is used to indicate the starting RB and the length of continuous RBs.

In some optional implementations, for a case where the frequency domain resource allocation field indicates an RBG allocated to a terminal,

If the second number of RBGs determined based on the second bandwidth is greater than or equal to the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal;

If the second number of RBGs determined based on the second bandwidth is less than the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal.

Further, in some optional embodiments, for the case where the number of the second RBGs is less than the number of the first RBGs, each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, the values of X1 and X2 are determined based on the number of the first RBGs and the number of the second RBGs, the number of the first part of bits is determined based on the value of X1, the value of X2, the first number of RBGs and the second number of RBGs, and the number of the second part of bits is determined based on the second number of RBGs and the number of the first part of bits.

Those skilled in the art should understand that the functions of each unit in the device for determining frequency domain resources shown in FIG4 can be understood by referring to the relevant description of the aforementioned method. The functions of each unit in the device for determining frequency domain resources shown in FIG4 can be implemented by a program running on a processor, or by a specific logic circuit.

FIG. 5 is a second schematic diagram of the structure of a device for determining frequency domain resources provided in an embodiment of the present application, which is applied to a network device. As shown in FIG. 5 , the device for determining frequency domain resources includes:

The sending unit 501 is used to send DCI to the terminal, where the DCI carries a frequency domain resource allocation domain, and the size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; the DCI indicates a time slot offset value.

In an embodiment of the present application, the first bandwidth and the second bandwidth are associated with the same bandwidth part BWP; or, the first BWP or first frequency domain resource with the first bandwidth and the second BWP or second frequency domain resource with the second bandwidth are associated.

Those skilled in the art should understand that the functions of each unit in the device for determining frequency domain resources shown in FIG5 can be understood by referring to the relevant description of the aforementioned method. The functions of each unit in the device for determining frequency domain resources shown in FIG5 can be implemented by a program running on a processor, or by a specific logic circuit.

Fig. 6 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device may be a terminal or a network device, and the communication device 600 shown in Fig. 6 includes a processor 610, which may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in Fig. 6, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

Optionally, as shown in FIG. 6 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

Optionally, the communication device 600 may specifically be a mobile terminal/terminal of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

Fig. 7 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in Fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

Optionally, as shown in Fig. 7, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

Optionally, the chip can be applied to the mobile terminal/terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Optionally, the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

Optionally, the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (22)

1. A method for determining frequency domain resources, characterized in that the method comprises: The terminal receives downlink control information DCI sent by the network device, where the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value; The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation field. 2. The method according to claim 1, characterized in that The first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resources; or, A first BWP or a first frequency domain resource having the first bandwidth and a second BWP or a second frequency domain resource having the second bandwidth are associated with each other. 3. The method according to claim 1, wherein the size of the frequency domain resource allocation domain is determined based on the first bandwidth, If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a first manner. 4. The method according to claim 1, characterized in that the size of the frequency domain resource allocation domain is determined based on the second bandwidth, If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a first manner. 5. The method according to claim 3 or 4, characterized in that the first method comprises at least one of the following: The frequency domain resource allocation field indicates a resource block group RBG allocated to the terminal, and the size of the RBG is determined based on the bandwidth of the BWP or frequency domain resource of the terminal in the time slot determined according to the time slot offset value; The frequency domain resource allocation field includes a resource indication value RIV, and the RIV is used to indicate a starting resource block RB and a continuous RB length. 6. The method according to claim 1, wherein the size of the frequency domain resource allocation domain is determined based on the first bandwidth, If the BWP or frequency domain resources of the terminal have the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a second manner. 7. The method according to claim 6, characterized in that the second method comprises at least one of the following: The frequency domain resource allocation field indicates an RBG allocated to the terminal, and a size of the RBG is determined based on the second bandwidth; The frequency domain resource allocation field includes a RIV, and the RIV is used to indicate a start RB and a continuous RB length. 8. The method according to claim 1, wherein the size of the frequency domain resource allocation domain is determined based on the second bandwidth, If the BWP or frequency domain resources of the terminal have the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resources of the physical shared channel in a third manner. 9. The method according to claim 8, characterized in that the third method comprises at least one of the following: The frequency domain resource allocation field indicates an RBG allocated to the terminal, and a size of the RBG is determined based on the first bandwidth; The frequency domain resource allocation field includes a RIV, and the RIV is used to indicate a start RB and a continuous RB length. 10. The method according to claim 7, characterized in that, for the case where the frequency domain resource allocation domain indicates the RBG allocated to the terminal, If the number of first RBGs determined based on the first bandwidth is greater than or equal to the number of second RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal; If the first number of RBGs determined based on the first bandwidth is less than the second number of RBGs determined based on the second bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal. 11. The method according to claim 10, characterized in that when the number of the first RBGs is less than the number of the second RBGs, Each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs. The values of X1 and X2 are determined based on the number of the first RBGs and the number of the second RBGs. The number of the first part of bits is determined based on the value of X1, the value of X2, the number of the first RBGs, and the number of the second part of bits. The number is determined based on the number of the first RBGs and the number of the first part of bits. 12. The method according to claim 7, characterized in that, for the case where the frequency domain resource allocation domain includes RIV, if So, otherwise, in, L _RBs is the length of consecutive RBs, RB _start is the starting RB, is the first bandwidth, It is the second bandwidth. 13. The method according to claim 9, characterized in that, for the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal, If the second number of RBGs determined based on the second bandwidth is greater than or equal to the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field is used to indicate whether an RBG corresponding to the bit is allocated to the terminal; If the second number of RBGs determined based on the second bandwidth is less than the first number of RBGs determined based on the first bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to the bit are allocated to the terminal. 14. The method according to claim 13, characterized in that when the number of the second RBGs is less than the number of the first RBGs, Each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs. The values of X1 and X2 are determined based on the number of the first RBGs and the number of the second RBGs. The number of the first part of bits is determined based on the value of X1, the value of X2, the number of the first RBGs, and the number of the second part of bits is determined based on the number of the second RBGs and the number of the first part of bits. 15. A method for determining frequency domain resources, characterized in that the method comprises: The network device sends a DCI to the terminal, where the DCI carries a frequency domain resource allocation domain, and a size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value. 16. The method according to claim 15, wherein: The first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resources; or, A first BWP or a first frequency domain resource having the first bandwidth and a second BWP or a second frequency domain resource having the second bandwidth are associated with each other. 17. A device for determining frequency domain resources, characterized in that it is applied to a terminal, and the device comprises: The receiving unit is used to receive DCI sent by a network device, where the DCI carries a frequency domain resource allocation domain, and the size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value. A determining unit is used to determine the frequency domain resources of the physical shared channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation domain. 18. A device for determining frequency domain resources, characterized in that it is applied to a network device, the device comprising: A sending unit is used to send DCI to a terminal, where the DCI carries a frequency domain resource allocation domain, and the size of the frequency domain resource allocation domain is determined based on the first bandwidth or the second bandwidth; and the DCI indicates a time slot offset value. 19. A terminal, characterized in that it comprises: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 14. 20. A network device, comprising: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 15 to 16. 21. A chip, characterized in that it comprises: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the method as described in any one of claims 1 to 14, or the method as described in any one of claims 15 to 16. 22. A computer-readable storage medium, characterized in that it is used to store a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 14, or the method according to any one of claims 15 to 16.