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

Abstract

This application discloses a method, apparatus, terminal, and network device for determining frequency domain resources. The method includes: a terminal receiving downlink control information (DCI) sent by a network device, wherein the DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth; the DCI indicating a time slot offset value; and the terminal determining 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.

Description

Technical Field

[0001] This 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 network equipment. Background Technology

[0002] Currently, terminals can only support one active bandwidth part (BWP), and the bandwidth size of this active bandwidth part is fixed. The size of the frequency domain resource allocation (FDRA) field in the downlink control information (DCI) is also determined based on this fixed bandwidth size. For flexible duplex scenarios, an active BWP with a dynamically changing bandwidth size can be configured for the terminal to dynamically adapt to traffic demands. However, if the current DCI size design is followed, it will result in different DCI sizes for the same format on the terminal. 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, increasing the number of blind detections. Summary of the Invention

[0003] To address the aforementioned technical problems, 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.

[0004] The method for determining frequency domain resources provided in this application includes:

[0005] The terminal receives a DCI sent by the network device. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value.

[0006] 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 domain.

[0007] The method for determining frequency domain resources provided in this application includes:

[0008] The network device sends a DCI to the terminal. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value.

[0009] The frequency domain resource determination device provided in this application embodiment is applied to a terminal, and the device includes:

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

[0011] The 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.

[0012] The frequency domain resource determination apparatus provided in this application embodiment is applied to a network device, and the apparatus includes:

[0013] A transmitting unit is used to transmit a DCI to a terminal. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value.

[0014] The terminal provided in this 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 of the frequency domain resource determination methods described above.

[0015] The network device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the frequency domain resource determination methods described above.

[0016] The chip provided in this application includes a processor for calling and running a computer program from a memory, causing a device on which the chip is installed to perform any of the methods described above.

[0017] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the methods described above.

[0018] In the technical solution of this application embodiment, on the one hand, the size of the frequency domain resource allocation domain is determined based on a first bandwidth or a second bandwidth, that is, the size of the frequency domain resource allocation domain is fixed, and thus 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 based on the time slot offset value in the DCI, which can realize the scheduling of different bandwidth sizes using the same frequency domain resource allocation domain. Attached Figure Description

[0019] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0020] Figure 2 This is a schematic diagram of the frequency domain resource distribution of the TDD band;

[0021] Figure 3 This is a flowchart illustrating the method for determining frequency domain resources provided in an embodiment of this application;

[0022] Figure 4 This is a schematic diagram of the structure of the frequency domain resource determination device provided in the embodiments of this application. Figure 1 ;

[0023] Figure 5 This is a schematic diagram of the structure of the frequency domain resource determination device provided in the embodiments of this application. Figure 2 ;

[0024] Figure 6 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0025] Figure 7 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0027] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0028] like Figure 1 As shown, the communication system 100 may include a terminal 110 and a network device 120. The network device 120 can communicate with the terminal 110 via an air interface. Multi-service transmission is supported between the terminal 110 and the network device 120.

[0029] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this 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 known as New Radio (NR) communication system), or future communication systems, etc.

[0030] exist Figure 1 In the communication system 100 shown, network device 120 can be an access network device that communicates with terminal 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal 110 (e.g., UE) located within that coverage area.

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

[0032] Terminal 110 can be any terminal, including but not limited to terminals that are connected to network device 120 or other terminals via wired or wireless connections.

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

[0034] Terminal 110 can be used for device-to-device (D2D) communication.

[0035] The wireless communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the aforementioned core network device may also be called by other names, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0036] The various functional units in the communication system 100 can also establish connections and communicate with each other through the next generation (NG) interface.

[0037] For example, the terminal establishes an air interface connection with the access network equipment 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 NG interface 1 (N1); the access network equipment, such as the next-generation radio access base station (gNB), can establish a user plane data connection with the UPF through NG interface 3 (N3); the access network equipment can establish a control plane signaling connection with the AMF through NG interface 2 (N2); the UPF can establish a control plane signaling connection with the SMF through NG interface 4 (N4); the UPF can interact with the data network to exchange user plane data through NG interface 6 (N6); the AMF can establish a control plane signaling connection with the SMF through NG interface 11 (N11); and the SMF can establish a control plane signaling connection with the PCF through NG interface 7 (N7).

[0038] Figure 1 An exemplary embodiment 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. This application embodiment does not limit this.

[0039] It should be noted that, Figure 1This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminals and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0040] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0041] Currently, the terminal only supports one active BWP with a fixed bandwidth size. The base station uses DCI for dynamic scheduling of the physical shared channel. The size (i.e., bit length) of the frequency domain resource allocation field used for scheduling the physical shared channel in the DCI is related to the bandwidth size of the active BWP. This ensures that the size of the DCI of the same format within the same BWP is fixed, reducing the terminal's blind detection complexity and overall terminal complexity.

[0042] In flexible duplex scenarios, such as Figure 2 As shown, uplink (UL) frequency domain resources can be added in the middle of the downlink (DL) frequency domain resources of the time division duplex (TDD) band to improve the uplink throughput of the TDD band and reduce uplink latency.

[0043] Since a terminal can only support one active BWP, to support resource configuration under flexible duplex conditions, an active BWP with dynamically changing bandwidth can be configured for the terminal. However, if the current design follows the size of the frequency domain resource allocation domain in the DCI, it will result in different DCI sizes for the same format across the terminal. Furthermore, at a given scheduling moment, the terminal does not know whether the physical shared channel scheduled by the DCI is located within a narrower or wider bandwidth; the terminal needs to detect two DCI sizes, increasing the number of blind detections.

[0044] Therefore, the following technical solutions are proposed in the embodiments of this application. The technical solutions in the embodiments of this application propose a method for determining frequency domain resources, which realizes the allocation of frequency domain resources of the physical shared channel when the bandwidth of the BWP changes by using a DCI of fixed size, thereby reducing the number of DCI sizes in the terminal and the complexity of blind detection.

[0045] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0046] It should be noted that the physical shared channel in the embodiments of this application can be a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH).

[0047] In this embodiment, for the network side, the size (i.e., bit length) of the frequency domain resource allocation field in the DCI is determined by referring to a first bandwidth or a 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 location of the physical channel scheduled by the DCI based on the time slot offset value and the frequency domain resource allocation field in the DCI.

[0048] Figure 3 This is a flowchart illustrating the method for determining frequency domain resources provided in an embodiment of this application, as shown below. Figure 3 As shown, the method for determining the frequency domain resources includes the following steps:

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

[0050] In this embodiment, the network device sends a DCI to the terminal, and the terminal receives the DCI sent by the network device. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. Furthermore, the DCI indicates a time slot offset value. Here, the network device can be a base station.

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

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

[0053] In this embodiment, the size (i.e., bit length) of the frequency domain resource allocation domain in the DCI is determined based on a first bandwidth or a second bandwidth, wherein the first bandwidth and the second bandwidth are different. In some alternative embodiments, the first bandwidth is smaller than the second bandwidth.

[0054] Here, the first bandwidth and the second bandwidth are associated with the same bandwidth portion BWP or frequency domain resource; or, the first BWP or first frequency domain resource having the first bandwidth and the second BWP or second frequency domain resource having the second bandwidth are associated.

[0055] 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 domain.

[0056] Option 1

[0057] Case 1-1: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, then the terminal determines the frequency domain resource of the physical shared channel in the first manner.

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

[0059] The frequency domain resource allocation domain indicates the resource block group (RGB) allocated to the terminal, and the size of the RGB is determined based on the bandwidth of the terminal's BWP or frequency domain resources in the time slot determined according to the time slot offset value;

[0060] The frequency domain resource allocation field includes a resource indication value (RIV), which indicates the starting resource block (RB) and the length of consecutive RBs.

[0061] 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, the size of the RGB being determined based on the bandwidth (i.e., the first bandwidth) of the terminal's BWP or frequency domain resources 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 a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs, here, optionally, the granularity of the length of consecutive RBs is 1 Physical Resource Block (PRB).

[0062] Case 1-2: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the terminal's BWP or frequency domain resource has the second bandwidth in the time slot determined according to the time slot offset value, then the terminal determines the frequency domain resource of the physical shared channel in the second manner.

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

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

[0065] The frequency domain resource allocation domain includes a RIV, which is used to indicate the starting RB and the length of consecutive RBs.

[0066] 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, the size of the RBG being determined based on the second bandwidth; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs, where, optionally, the granularity of the length of consecutive RBs is at least 1 PRB.

[0067] In some alternative implementations, for the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal,

[0068] 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, then each bit of the frequency domain resource allocation field is used to indicate whether the RBG corresponding to that bit is allocated to the terminal.

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

[0070] Furthermore, in some optional embodiments, when the number of the first RBG is less than the number of the second RBG, each bit in the first part of the bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of the 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 RBG and the number of the second RBG. 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 RBG, and the number of the second RBG. The number of the second part of bits is determined based on the number of the first RBG and the number of the first part of bits.

[0071] Furthermore, in some alternative implementations, when the frequency domain resource allocation domain includes RIV,

[0072] if So,

[0073] otherwise,

[0074] in, L RBs It is the length of continuous RB, RB start It is the starting RB. It is the first bandwidth. It is the second bandwidth.

[0075] Option 2

[0076] Case 2-1: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the terminal's BWP or frequency domain resource has the second bandwidth in the time slot determined according to the time slot offset value, then the terminal determines the frequency domain resource of the physical shared channel in the first manner.

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

[0078] The frequency domain resource allocation domain indicates the RGB allocated to the terminal, and the size of the RGB is determined based on the bandwidth of the terminal's BWP or frequency domain resources in the time slot determined according to the time slot offset value.

[0079] The frequency domain resource allocation domain includes a RIV, which is used to indicate the starting RB and the length of consecutive RBs.

[0080] 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, the size of the RGB being determined based on the bandwidth (i.e., the second bandwidth) of the terminal's BWP or frequency domain resources in a 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 a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs, here, optionally, the granularity of the length of consecutive RBs is 1 PRB.

[0081] Case 2-2: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, then the terminal determines the frequency domain resource of the physical shared channel in a third manner.

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

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

[0084] The frequency domain resource allocation domain includes a RIV, which is used to indicate the starting RB and the length of consecutive RBs.

[0085] 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, the size of the RBG being determined based on the first bandwidth; 2) for frequency domain resource allocation type 1, the frequency domain resource allocation field includes RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs, here, optionally, the granularity of the length of consecutive RBs is 1 PRB.

[0086] In some alternative implementations, for the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal,

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

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

[0089] Furthermore, in some optional embodiments, when the number of the second RBG is less than the number of the first RBG, each bit in the first part of the bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of the 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 RBG and the number of the second RBG. The number of the first part of the bits is determined based on the value of X1, the value of X2, the number of the first RBG, and the number of the second RBG. The number of the second part of the bits is determined based on the number of the second RBG and the number of the first part of the bits.

[0090] The technical solution of this application embodiment, on the one hand, determines the size of the frequency domain resource allocation domain based on one of the first bandwidth and the second bandwidth, that is, the size of the frequency domain resource allocation domain is fixed, and thus 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 based on the time slot offset value in the DCI, which can realize the scheduling of different bandwidth sizes using the same frequency domain resource allocation domain.

[0091] The technical solutions of the embodiments of this application are illustrated below with specific application examples.

[0092] Application Example 1: Determine the bit length of the frequency domain resource allocation field in DCI by referring to the smaller bandwidth size.

[0093] In DCI, the bit length of the frequency domain resource allocation field is related to the first bandwidth, which is less than the second bandwidth. Specifically, the first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or, a first BWP or first frequency domain resource with the first bandwidth and a second BWP or second frequency domain resource with the second bandwidth are associated.

[0094] The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI based on 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.

[0095] Case 1-1: If the terminal's BWP or frequency domain resources have a first bandwidth in the scheduling slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel in a first manner.

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

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

[0098] 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 RGB is determined based on the bandwidth (i.e. the first bandwidth) of the terminal's BWP or frequency domain resource in the time slot determined according to the time slot offset value.

[0099] 2) For frequency domain resource allocation type 1, the frequency domain resource allocation domain includes RIV, which is used to indicate the starting RB and the length of consecutive RBs. Optionally, the granularity of the length of consecutive RBs is 1 PRB.

[0100] Case 1-2: If the terminal's BWP or frequency domain resources have a second bandwidth in the scheduling slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel in the second manner.

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

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

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

[0104] Specifically, if the number of first RBGs N1 determined based on the first bandwidth is greater than or equal to the number of second RBGs N2 determined based on the second bandwidth, the frequency domain resource allocation domain uses each bit to indicate whether the corresponding RBG is allocated to the terminal.

[0105] If the number of first RBGs N1 determined based on the first bandwidth is less than the number of second RBGs N2 determined based on the second bandwidth, each bit of the frequency domain resource allocation domain indicates whether one or more corresponding RBGs are allocated to the terminal. Here, M bits correspond to X1 RBGs, and N1-M bits correspond to X2 RBGs. or

[0106] M·X1+(N1-M)·X2=N2;

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

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

[0109] Specifically, if So,

[0110] otherwise,

[0111] in, It is the first bandwidth. It is the second bandwidth.

[0112] Application Example 2: Determine the bit length of the frequency domain resource allocation field in DCI by referring to the larger frequency domain bandwidth.

[0113] In DCI, the bit length of the frequency domain resource allocation field is related to the second bandwidth, and the first bandwidth is less than the second bandwidth. Specifically, the first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or, a first BWP or first frequency domain resource with the first bandwidth and a second BWP or second frequency domain resource with the second bandwidth are associated.

[0114] The terminal determines the frequency domain resources of the physical shared channel scheduled by the DCI based on 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.

[0115] Case 2-1: If the terminal's BWP or frequency domain resources have a second bandwidth in the scheduling slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel in accordance with the first method.

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

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

[0118] 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 RGB is determined based on the bandwidth (i.e. the second bandwidth) of the terminal's BWP or frequency domain resource in the time slot determined according to the time slot offset value.

[0119] 2) For frequency domain resource allocation type 1, the frequency domain resource allocation domain includes RIV, which is used to indicate the starting RB and the length of consecutive RBs. Optionally, the granularity of the length of consecutive RBs is 1 PRB.

[0120] Case 2-2: If the terminal's BWP or frequency domain resources have a first bandwidth in the scheduling slot indicated by the DCI, the terminal determines the frequency domain resources of the physical shared channel in accordance with the third method.

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

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

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

[0124] Specifically, if the number of second RBGs N2 determined based on the second bandwidth is greater than or equal to the number of first RBGs N1 determined based on the first bandwidth, the utilization of each bit in the frequency domain resource allocation domain indicates whether the corresponding RBG is allocated to the terminal.

[0125] If the number of second RBGs N2 determined based on the second bandwidth is less than the number of first RBGs N1 determined based on the first bandwidth, each bit of the frequency domain resource allocation field indicates whether one or more corresponding RBGs are allocated to the terminal. Wherein, M bits correspond to X1 RBGs, and N2-M bits correspond to X2 RBGs. or

[0126] M·X1+(N2-M)·X2=N1;

[0127] 2) For frequency domain resource allocation type 1, the frequency domain resource allocation domain includes RIV, which is used to indicate the starting RB and the length of consecutive RBs. Optionally, the granularity of the length of consecutive RBs is 1 PRB.

[0128] Figure 4 This is a schematic diagram of the structure of the frequency domain resource determination device provided in the embodiments of this application. Figure 1 Applied to terminals, such as Figure 4 As shown, the frequency domain resource determination device includes:

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

[0130] The determining unit 402 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.

[0131] In this embodiment of the application, the first bandwidth and the second bandwidth are associated with the same bandwidth portion BWP or frequency domain resource; or, the first BWP or first frequency domain resource having the first bandwidth and the second BWP or second frequency domain resource having the second bandwidth are associated.

[0132] Option 1

[0133] Case 1-1: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, then the determining unit 402 determines the frequency domain resource of the physical shared channel in the first manner.

[0134] 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, the size of the RGB being determined based on the bandwidth of the terminal's BWP or frequency domain resources in a time slot determined according to the time slot offset value; 2) the frequency domain resource allocation domain includes a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs.

[0135] Case 1-2: The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the terminal's BWP or frequency domain resource has the second bandwidth in the time slot determined according to the time slot offset value, then the determining unit 402 determines the frequency domain resource of the physical shared channel in the second manner.

[0136] 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, the size of the RBG being determined based on the second bandwidth; 2) the frequency domain resource allocation domain includes a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs.

[0137] In some alternative implementations, for the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal,

[0138] 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, then each bit of the frequency domain resource allocation field is used to indicate whether the RBG corresponding to that bit is allocated to the terminal.

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

[0140] Furthermore, in some optional embodiments, when the number of the first RBG is less than the number of the second RBG, each bit in the first part of the bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of the 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 RBG and the number of the second RBG. 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 RBG, and the number of the second RBG. The number of the second part of bits is determined based on the number of the first RBG and the number of the first part of bits.

[0141] Furthermore, in some alternative implementations, when the frequency domain resource allocation domain includes RIV,

[0142] if So,

[0143] otherwise,

[0144] in, L RBs It is the length of continuous RB, RB start It is the starting RB. It is the first bandwidth. It is the second bandwidth.

[0145] Option 2

[0146] 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 resource of the terminal has the second bandwidth in the time slot determined according to the time slot offset value, then the determining unit 402 determines the frequency domain resource of the physical shared channel in the first manner.

[0147] 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, the size of the RGB being determined based on the bandwidth of the terminal's BWP or frequency domain resources in a time slot determined according to the time slot offset value; 2) the frequency domain resource allocation domain includes a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs.

[0148] Case 2-2: The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, then the determining unit 402 determines the frequency domain resource of the physical shared channel in a third manner.

[0149] 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, the size of the RBG being determined based on the first bandwidth; 2) the frequency domain resource allocation domain includes a RIV, the RIV being used to indicate the starting RB and the length of consecutive RBs.

[0150] In some alternative implementations, for the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal,

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

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

[0153] Furthermore, in some optional embodiments, when the number of the second RBG is less than the number of the first RBG, each bit in the first part of the bits in the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of the 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 RBG and the number of the second RBG. The number of the first part of the bits is determined based on the value of X1, the value of X2, the number of the first RBG, and the number of the second RBG. The number of the second part of the bits is determined based on the number of the second RBG and the number of the first part of the bits.

[0154] Those skilled in the art should understand that Figure 4 The functions of each unit in the frequency domain resource determination device shown can be understood by referring to the relevant descriptions of the aforementioned method. Figure 4 The functions of each unit in the frequency domain resource determination device shown can be implemented by a program running on a processor or by specific logic circuits.

[0155] Figure 5 This is a schematic diagram of the structure of the frequency domain resource determination device provided in the embodiments of this application. Figure 2 Applied to network devices, such as Figure 5 As shown, the frequency domain resource determination device includes:

[0156] The transmitting unit 501 is used to transmit a DCI to the terminal. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value.

[0157] In this embodiment of the application, the first bandwidth and the second bandwidth are associated with the same bandwidth portion (BWP); or, the first BWP or first frequency domain resource having the first bandwidth and the second BWP or second frequency domain resource having the second bandwidth are associated.

[0158] Those skilled in the art should understand that Figure 5 The functions of each unit in the frequency domain resource determination device shown can be understood by referring to the relevant descriptions of the aforementioned method. Figure 5 The functions of each unit in the frequency domain resource determination device shown can be implemented by a program running on a processor or by specific logic circuits.

[0159] Figure 6 This is a schematic structural diagram of a communication device 600 provided in an embodiment of this application. The communication device can be a terminal or a network device. Figure 6The communication device 600 shown includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0160] Optionally, such as Figure 6 As shown, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to implement the methods described in this embodiment.

[0161] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0162] Optionally, such as Figure 6 As shown, the communication device 600 may also include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

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

[0164] Optionally, the communication device 600 may specifically be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0165] Optionally, the communication device 600 may specifically be a mobile terminal / terminal in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0166] Figure 7 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 7 The chip 700 shown includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0167] Optionally, such as Figure 7 As shown, chip 700 may further include memory 720. Processor 710 can retrieve and run computer programs from memory 720 to implement the methods described in this embodiment.

[0168] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0169] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0170] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0171] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0172] Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0173] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0174] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0175] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0176] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be 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 memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0177] This application also provides a computer-readable storage medium for storing computer programs.

[0178] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0179] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0180] This application also provides a computer program product, including computer program instructions.

[0181] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0182] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0183] This application also provides a computer program.

[0184] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0185] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0186] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0187] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0188] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0189] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0190] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0191] If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0192] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for determining frequency domain resources, characterized in that, The method includes: The terminal receives downlink control information (DCI) sent by the network device. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value. The first bandwidth and the second bandwidth are associated with the same bandwidth portion (BWP) or frequency domain resource. Alternatively, 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 based on the time slot offset value and the frequency domain resource allocation domain; 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; or, 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. or, 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; or, 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.

2. The method according to claim 1, characterized in that, The first method includes at least one of the following: The frequency domain resource allocation field indicates the resource block group (RBG) allocated to the terminal, the size of which is determined based on the bandwidth of the terminal's BWP or frequency domain resources in the time slot determined according to the time slot offset value. The frequency domain resource allocation domain includes a resource indicator value (RIV), which indicates the starting resource block (RB) and the length of consecutive RBs.

3. The method according to claim 1, characterized in that, The second method includes at least one of the following: 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. The frequency domain resource allocation domain includes a RIV, which is used to indicate the starting RB and the length of consecutive RBs.

4. The method according to claim 1, characterized in that, The third method includes at least one of the following: 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. The frequency domain resource allocation domain includes a RIV, which is used to indicate the starting RB and the length of consecutive RBs.

5. The method according to claim 3, characterized in that, For the case where the frequency domain resource allocation field 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, then each bit of the frequency domain resource allocation field is used to indicate whether the RBG corresponding to that bit is allocated to the terminal. If the number of first RBGs determined based on the first bandwidth is less than the number of second RBGs determined based on the second bandwidth, then each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to that bit are allocated to the terminal.

6. The method according to claim 5, characterized in that, When the number of the first RBG is less than the number of the second RBG. Each bit in the first part of the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of 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 RBGs. The number of the second part of bits is determined based on the number of the first RBGs and the number of the first part of bits.

7. The method according to claim 3, characterized in that, For the case where the frequency domain resource allocation domain includes RIV. if ,So, ; otherwise, ; in, , , It is the length of continuous RB. It is the starting RB. , It is the first bandwidth. It is the second bandwidth.

8. The method according to claim 4, characterized in that, For the case where the frequency domain resource allocation field indicates the RBG allocated to the terminal. If the number of second RBGs determined based on the second bandwidth is greater than or equal to the number of first RBGs determined based on the first bandwidth, then each bit of the frequency domain resource allocation field is used to indicate whether the RBG corresponding to that bit is allocated to the terminal. If the number of second RBGs determined based on the second bandwidth is less than the number of first RBGs determined based on the first bandwidth, then each bit of the frequency domain resource allocation field indicates whether one or more RBGs corresponding to that bit are allocated to the terminal.

9. The method according to claim 8, characterized in that, When the number of the second RBG is less than the number of the first RBG. Each bit in the first part of the frequency domain resource allocation domain corresponds to X1 RBGs, and each bit in the second part of 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 RBGs. 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.

10. A method for determining frequency domain resources, characterized in that, The method includes: The network device sends a DCI (Distributed Frequency Access Code) to the terminal. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value. The first bandwidth and the second bandwidth are associated with the same bandwidth portion (BWP) or frequency domain resource; or, a first BWP or first frequency domain resource with the first bandwidth and a second BWP or second frequency domain resource with the second bandwidth are associated. This allows the terminal 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 field. The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resource of the terminal has the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a first manner; or, if the BWP or frequency domain resource of the terminal has the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a second manner. or, The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the terminal's BWP or frequency domain resource has the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a first manner; or, if the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a third manner.

11. A device for determining frequency domain resources, characterized in that, Applied to a terminal, the device includes: A receiving unit is configured to receive a DCI sent by a network device, wherein the DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth; the DCI indicates a time slot offset value; the first bandwidth and the second bandwidth are associated with the same bandwidth portion BWP or frequency domain resource; or, the first BWP or first frequency domain resource having the first bandwidth and the second BWP or second frequency domain resource having the second bandwidth are associated. The determining unit 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; wherein, The size of the frequency domain resource allocation domain is determined based on the first bandwidth. The determining unit is configured to determine the frequency domain resources of the physical shared channel in a first manner 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; or, 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, determine the frequency domain resources of the physical shared channel in a second manner. or, The size of the frequency domain resource allocation domain is determined based on the second bandwidth. The determining unit is configured to determine the frequency domain resources of the physical shared channel in a first manner 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; or, 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, determine the frequency domain resources of the physical shared channel in a third manner.

12. A device for determining frequency domain resources, characterized in that, Applied to network devices, the device includes: A transmitting unit is configured to transmit a Direct Access Component (DCI) to a terminal. The DCI carries a frequency domain resource allocation field, the size of which is determined based on a first bandwidth or a second bandwidth. The DCI indicates a time slot offset value. The first bandwidth and the second bandwidth are associated with the same bandwidth portion (BWP) or frequency domain resource; or, a first BWP or first frequency domain resource having the first bandwidth and a second BWP or second frequency domain resource having the second bandwidth are associated. This enables the terminal 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 field. The size of the frequency domain resource allocation domain is determined based on the first bandwidth. If the BWP or frequency domain resource of the terminal has the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a first manner; or, if the BWP or frequency domain resource of the terminal has the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a second manner. or, The size of the frequency domain resource allocation domain is determined based on the second bandwidth. If the terminal's BWP or frequency domain resource has the second bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a first manner; or, if the terminal's BWP or frequency domain resource has the first bandwidth in the time slot determined according to the time slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a third manner.

13. A terminal, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 9.

14. A network device, characterized in that, include: A processor and a memory for storing computer programs, the processor for calling and running the computer programs stored in the memory to perform the method as described in claim 10.

15. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 9, or the method as claimed in claim 10.

16. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 9, or the method as claimed in claim 10.

Images