CN116456470A

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

Info

Publication number: CN116456470A
Application number: CN202210002119.7A
Authority: CN
Inventors: 杨拓
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2022-01-04
Filing date: 2022-01-04
Publication date: 2023-07-18

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

Method and device for determining frequency domain resources, terminal and network equipment

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a method and apparatus for determining a frequency domain resource, a terminal, and a network device.

Background

Currently, a terminal can only support one active bandwidth Part (BWP), and the bandwidth size of the active bandwidth Part is fixed, and the size of the frequency resource allocation (Frequency Domain Resource Assignment, FDRA) domain in the downlink control information (Downlink Control Information, DCI) is also determined according to the fixed bandwidth size. For the flexible duplex scenario, an active BWP with a dynamically changing bandwidth size may be configured for the terminal to dynamically adapt to the traffic demand. However, if the design is according to the current DCI size, the DCI of the same format of the terminal may be different. In addition, at a certain scheduling time, the terminal does not know whether the physical shared channel scheduled by the DCI is located in a narrower bandwidth or a wider bandwidth, and the terminal needs to detect two DCI sizes, so that the blind detection frequency of the terminal is increased.

Disclosure of Invention

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

The method for determining the frequency domain resource provided by the embodiment of the application comprises the following steps:

the method comprises the steps that a terminal receives 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.

the network equipment sends DCI to the terminal, 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.

The device for determining the frequency domain resource provided by the embodiment of the application is applied to a terminal, and the device comprises:

a receiving unit, configured to receive 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; the DCI indicates a slot offset value;

And the determining unit is used for determining 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.

The device for determining the frequency domain resource provided by the embodiment of the application is applied to network equipment, and comprises:

a sending unit, configured to send DCI to a 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 a first bandwidth or a second bandwidth; the DCI indicates a slot offset value.

The terminal provided by the embodiment of the application comprises: the processor is used for calling and running the computer program stored in the memory, and executing any one of the frequency domain resource determining methods.

The network device provided by the embodiment of the application comprises: the processor is used for calling and running the computer program stored in the memory, and executing any one of the frequency domain resource determining methods.

The chip provided by the embodiment of the application comprises: and a processor for calling and running the computer program from the memory, so that the device on which the chip is mounted performs any one of the methods described above.

The core computer readable storage medium provided in the embodiments of the present application is configured to store a computer program, where the computer program causes a computer to execute any one of the methods described above.

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 that the size of the DCI is fixed, and when the size of the BWP changes with time, since the size of the DCI is fixed, no additional blind detection is required by the terminal. On the other hand, the terminal determines which bandwidth is used for explaining the frequency domain resource allocation domain according to the time slot offset value in the DCI, so that different bandwidth sizes can be scheduled by using the same frequency domain resource allocation domain.

Drawings

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

FIG. 2 is a schematic diagram of frequency domain resource distribution for TDD band;

fig. 3 is a flowchart illustrating a method for determining a frequency domain resource according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a determining apparatus for frequency domain resources according to an embodiment of the present application;

fig. 5 is a schematic diagram ii of the structural composition of the determining device for frequency domain resources provided in the embodiment of the present application;

Fig. 6 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 of an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal 110 and a network device 120. Network device 120 may communicate with terminal 110 over the air. Multi-service transmission is supported between the terminal 110 and the network device 120.

It should be understood that the present embodiments are illustrated by way of example only with respect to communication system 100, but the present embodiments are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminals 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal 110 may be any terminal including, but not limited to, a terminal that employs a wired or wireless connection with network device 120 or other terminals.

For example, the terminal 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle 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 further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (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 appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form a new network entity by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.

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

Fig. 1 illustrates one base station, one core network device, and two terminals, and optionally, the wireless communication system 100 may include a plurality of base station devices and may include other numbers of terminals within the coverage area of each base station, which is not limited in this embodiment of the present application.

It should be noted that fig. 1 illustrates, by way of example, a system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication that there is an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that, in the embodiments of the present application, reference to "corresponding" may mean that there is a direct correspondence or an indirect correspondence between the two, or may mean that there is an association between the two, or may be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners in which related information may be indicated in devices (e.g., including terminals and network devices), and the present application is not limited to a specific implementation thereof. Such as predefined may refer to what is defined 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, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

Currently, a terminal supports only one active BWP with a fixed bandwidth size, and a base station performs dynamic scheduling of a physical shared channel using DCI. The size (i.e., bit length) of the frequency domain resource allocation domain used for scheduling the physical shared channel in the DCI is related to the bandwidth size of the active BWP, so that the size of the DCI in the same format of the terminal in the same BWP can be ensured to be fixed, and the blind detection complexity and the terminal complexity of the terminal are reduced.

In the flexible duplex scenario, as shown in fig. 2, an Uplink (UL) frequency domain resource may be added in the middle of a Downlink (DL) frequency domain resource of a time division duplex (TDD band), so as to improve uplink throughput of the TDD band and reduce uplink delay.

Since a terminal can only support one active BWP, in order to support resource allocation in flexible duplex, the terminal can be configured with one active BWP having a dynamically varying bandwidth size. However, if the size of the frequency resource allocation domain is designed according to the current DCI, the DCI of the same format of the terminal may be caused to be different in size. In addition, at a certain scheduling time, the terminal does not know whether the physical shared channel scheduled by the DCI is located in a narrower bandwidth or a wider bandwidth, and the terminal needs to detect two DCI sizes, so that the blind detection frequency of the terminal is increased.

For this reason, the following technical solutions of the embodiments of the present application are proposed. According to the technical scheme, the method for determining the frequency domain resources is provided, the frequency domain resource allocation of the physical shared channel when the bandwidth of BWP is changed is indicated by DCI with fixed DCI size, and the DCI size number and blind detection complexity of the terminal are reduced.

In order 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 may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

Note that, the physical shared channel in the embodiment of the present application may 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 a network side, a size (i.e., a bit length) of a frequency domain resource allocation domain in DCI is determined with reference to a first bandwidth or a second bandwidth, where the first bandwidth or the second bandwidth is associated with the same BWP or has an association 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 domain in the DCI.

Fig. 3 is a flowchart of a method for determining a frequency domain resource according to an embodiment of the present application, as shown in fig. 3, where the method for determining a frequency domain resource includes the following steps:

step 301: the method comprises the steps that a terminal receives 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.

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

In some alternative embodiments, the slot offset value may be K0, where K0 represents the slot spacing between the DCI and the PDSCH scheduled by the DCI. The terminal can determine the time slot of the PDSCH scheduled by the DCI according to the time slot of the received DCI and K0. Here, for convenience of description, a slot in which the PDSCH scheduled by the DCI is located may be referred to as a scheduling slot.

In some alternative embodiments, the slot offset value may be K2, where K2 represents the slot spacing between the DCI and the PUSCH scheduled by the DCI. And the terminal can determine the time slot of the PUSCH scheduled by the DCI according to the time slot of the received DCI and the time slot of K2. Here, for convenience of description, a slot in which a PUSCH scheduled by DCI is located may be referred to as a scheduled slot.

In this embodiment of the present application, 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, where the first bandwidth is different from the second bandwidth. In some alternative embodiments, the first bandwidth is less than the second bandwidth.

Here, the first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resource; or, the first BWP or the first frequency domain resource having the first bandwidth and the second BWP or the second frequency domain resource having the second bandwidth have an association relationship.

Step 302: 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.

Scheme one

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

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

the frequency domain resource allocation domain indicates a set of resource blocks (Resource Block Group, RGB) allocated to a terminal, the size of the RBG being determined based on a bandwidth possessed by BWP or frequency domain resources of the terminal at a slot determined according to the slot offset value;

The frequency domain Resource allocation domain includes a Resource indication value (Resource Indication Value, RIV) for indicating a starting Resource Block (RB) and a contiguous RB length.

As an example: the first mode includes at least one of the following: 1) For a frequency domain resource allocation type 0, the frequency domain resource allocation field indicating RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth (i.e., the first bandwidth) that BWP of the terminal or frequency domain resources have at a slot determined according to the slot offset value; 2) For frequency domain resource allocation type 1, the frequency domain resource allocation domain includes an RIV for indicating a starting RB and a consecutive RB length, where, optionally, the granularity of the consecutive RB length is 1 physical resource block (Physical Resource Block, PRB).

Cases 1-2: the size of the frequency domain resource allocation domain is determined based on the first bandwidth, and if the BWP or frequency domain resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a second manner.

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

The frequency domain resource allocation domain indicates RBGs allocated to terminals, the size of the RBGs being determined based on the second bandwidth;

the frequency domain resource allocation domain includes an RIV for indicating a starting RB and a consecutive RB length.

As an example: the second mode includes at least one of the following: 1) For a frequency domain resource allocation type 0, the frequency domain resource allocation domain indicating an RBG allocated to a 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 domain includes an RIV for indicating a starting RB and a consecutive RB length, where, optionally, the granularity of the consecutive RB length is at least 1 PRB.

In some alternative embodiments, for the case where the frequency domain resource allocation domain indicates an RBG allocated to the terminal,

if the number of the first RBGs determined based on the first bandwidth is greater than or equal to the number of the second RBGs determined according to the second bandwidth, each bit of the frequency domain resource allocation domain is used for indicating whether one RBG corresponding to the bit is allocated to a terminal;

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

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

Further, in some alternative embodiments, for the case where the frequency domain resource allocation domain comprises a RIV,

if it isThen (I)>

Otherwise the first set of parameters is selected,

wherein, the liquid crystal display device comprises a liquid crystal display device,L _RBs is a continuous RB length, RB _start Is the start RB of the radio bearer,is the first bandwidth, < >>Is the second bandwidth.

Scheme II

Case 2-1: the size of the frequency domain resource allocation domain is determined based on the second bandwidth, and if the BWP or the frequency domain resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel according to the first mode.

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

the frequency domain resource allocation domain indicates RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth possessed by BWP or frequency domain resources of the terminal at a slot determined according to the slot offset value;

As an example: the first mode includes at least one of the following: 1) For a frequency domain resource allocation type 0, the frequency domain resource allocation field indicating RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth (i.e., the second bandwidth) that BWP of the terminal or frequency domain resources have at a slot determined according to the slot offset value; 2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes an RIV for indicating a starting RB and a consecutive RB length, where, optionally, the granularity of the consecutive RB length is 1 PRB.

Case 2-2: the size of the frequency domain resource allocation domain is determined based on the second bandwidth, and if the BWP or the frequency domain resource of the terminal has the first bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel according to a third mode.

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

the frequency domain resource allocation domain indicates RBGs allocated to terminals, and the sizes of the RBGs are determined based on the first bandwidth;

As an example: the third mode includes at least one of the following: 1) For a frequency domain resource allocation type 0, the frequency domain resource allocation domain indicating an RBG allocated to a 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 an RIV for indicating a starting RB and a consecutive RB length, where, optionally, the granularity of the consecutive RB length is 1 PRB.

if the second RBG number determined based on the second bandwidth is greater than or equal to the first RBG number determined according to the first bandwidth, each bit of the frequency domain resource allocation domain is used for indicating whether one RBG corresponding to the bit is allocated to a terminal;

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

Further, in some optional embodiments, for the case that the second RBG number is smaller than the first RBG number, each bit in the first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, 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 RBG number and the second RBG number, the number of first part of bits is determined based on the value of X1, the value of X2, the first RBG number and the second RBG number, and the number of second part of bits is determined based on the second RBG number and the number of first part of bits.

According to the technical scheme, on one hand, the size of the frequency domain resource allocation domain is determined based on one bandwidth of the first bandwidth and the second bandwidth, namely the size of the frequency domain resource allocation domain is fixed, so that the size of DCI is fixed, and when the size of BWP changes along with time, the size of DCI is fixed, so that the terminal does not need to perform additional blind detection. On the other hand, the terminal determines which bandwidth is used for explaining the frequency domain resource allocation domain according to the time slot offset value in the DCI, so that different bandwidth sizes can be scheduled by using the same frequency domain resource allocation domain.

The following describes the technical solutions of the embodiments of the present application by way of example with reference to specific application examples.

Application example one: the bit length of the frequency domain resource allocation domain in the DCI is determined with reference to the smaller bandwidth size.

The bit length of the frequency resource allocation field in the DCI is associated with a first bandwidth that is less than a second bandwidth. Wherein the first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or, the first BWP or the first frequency domain resource having the first bandwidth and the second BWP or the second frequency domain resource having the second bandwidth have an association relationship.

And the terminal determines the frequency domain resource 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 domain in the DCI. Here, the slot offset value in DCI is used to indicate a scheduled slot.

Case 1-1: if the BWP or the frequency domain resource of the terminal has a first bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resource of the physical shared channel according to a first mode.

It should be noted that, the BWP or frequency domain resource of the terminal herein has a first bandwidth, which may be: the BWP or frequency domain resource of the terminal includes a first bandwidth and a second bandwidth, and the BWP or frequency domain resource of the terminal may be a first BWP or first frequency domain resource having the first bandwidth.

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

1) For a frequency domain resource allocation type 0, the frequency domain resource allocation field indicating RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth (i.e., the first bandwidth) that BWP of the terminal or frequency domain resources have at a slot determined according to the slot offset value;

2) For frequency domain resource allocation type 1, the frequency domain resource allocation field includes an RIV for indicating a starting RB and a consecutive RB length, where, optionally, the granularity of the consecutive RB length is 1 PRB.

Cases 1-2: if the BWP or the frequency domain resource of the terminal has the second bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resource of the physical shared channel according to the second mode.

It should be noted that, the BWP or frequency domain resource of the terminal herein has the second bandwidth, which may be: the BWP or frequency domain resource of the terminal includes a first bandwidth and a second bandwidth, and the BWP or frequency domain resource of the terminal may be a second BWP or second frequency domain resource having the second bandwidth.

Specifically, the second mode 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 a terminal, the RBG being sized 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 domain indicates whether a corresponding one of the RBGs is allocated to the terminal by using each bit.

If the first number of RBGs N1 determined according to the first bandwidth is smaller than the second number of RBGs N2 determined according to the second bandwidth, each bit of the frequency domain resource allocation domain is utilized to indicate whether a corresponding one or more RBGs are allocated to the terminal. Wherein M bits correspond to X1 RBGs and N1-M bits correspond to X2 RBGs, whereinOr alternatively

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 domain includes an RIV for indicating a starting RB (RB _start ) And a continuous RB length (L _RBs ) Here, optionally, the granularity of the consecutive RB length is at least 1 PRB.

In particular, ifThen (I)>

Otherwise the first set of parameters is selected,

wherein, the liquid crystal display device comprises a liquid crystal display device,is the first bandwidth, < >>Is the second bandwidth.

Application example two: the bit length of the frequency domain resource allocation domain in the DCI is determined with reference to the larger frequency domain bandwidth size.

The bit length of the frequency resource allocation field in the DCI is related to a second bandwidth, the first bandwidth being smaller than the second bandwidth. Wherein the first bandwidth and the second bandwidth are associated with the same BWP or frequency domain resource; or, the first BWP or the first frequency domain resource having the first bandwidth and the second BWP or the second frequency domain resource having the second bandwidth have an association relationship.

Case 2-1: if the BWP or the frequency domain resource of the terminal has the second bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resource of the physical shared channel according to the first mode.

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

1) For a frequency domain resource allocation type 0, the frequency domain resource allocation field indicating RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth (i.e., the second bandwidth) that BWP of the terminal or frequency domain resources have at a slot determined according to the slot offset value;

Case 2-2: if the BWP or the frequency domain resource of the terminal has the first bandwidth in the scheduling time slot indicated by the DCI, the terminal determines the frequency domain resource of the physical shared channel according to a third mode.

Specifically, the third mode 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 a terminal, the size of the RBG being 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, each bit of the frequency domain resource allocation domain indicates whether a corresponding RBG is allocated to the terminal.

If the second number of RBGs N2 determined according to the second bandwidth is smaller than the first number of RBGs N1 determined according to the first bandwidth, each bit of the frequency domain resource allocation domain is utilized to indicate whether a corresponding one or more RBGs are allocated to the terminal. Wherein M bits correspond to X1 RBGs, N2- M bits correspond to X2 RBGs, whereOr alternatively

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

Fig. 4 is a schematic structural diagram of a frequency domain resource determining apparatus provided in an embodiment of the present application, which is applied to a terminal, as shown in fig. 4, where the frequency domain resource determining apparatus includes:

a receiving unit 401, configured to receive 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; the DCI indicates a slot offset value;

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

In this embodiment of the present 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 the first frequency domain resource having the first bandwidth and the second BWP or the second frequency domain resource having the second bandwidth have an association relationship.

Scheme one

Case 1-1: the size of the frequency domain resource allocation domain is determined based on the first bandwidth, and if the BWP or frequency domain resource of the terminal has the first bandwidth in the slot determined according to the slot offset value, the determining unit 402 determines the frequency domain resource of the physical shared channel in a first manner.

Specifically, the first mode includes at least one of the following: 1) The frequency domain resource allocation domain indicates RGB allocated to a terminal, the size of the RBG being determined based on a bandwidth possessed by BWP or frequency domain resources of the terminal at a slot determined according to the slot offset value; 2) The frequency domain resource allocation domain includes an RIV for indicating a starting RB and a consecutive RB length.

Cases 1-2: the size of the frequency domain resource allocation domain is determined based on the first bandwidth, and if the BWP or frequency domain resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the determining unit 402 determines the frequency domain resource of the physical shared channel in a second manner.

Specifically, the second mode includes at least one of the following: 1) The frequency domain resource allocation domain indicates RBGs allocated to terminals, the size of the RBGs being determined based on the second bandwidth; 2) The frequency domain resource allocation domain includes an RIV for indicating a starting RB and a consecutive RB length.

if it isThen (I)>

Otherwise the first set of parameters is selected,/>

Scheme II

Case 2-1: the size of the frequency domain resource allocation domain is determined based on the second bandwidth, and if the BWP or frequency domain resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the determining unit 402 determines the frequency domain resource of the physical shared channel in the first manner.

Case 2-2: the size of the frequency domain resource allocation domain is determined based on the second bandwidth, and if the BWP or frequency domain resource of the terminal has the first bandwidth in the slot determined according to the slot offset value, the determining unit 402 determines the frequency domain resource of the physical shared channel according to a third mode.

Specifically, the third mode includes at least one of the following: 1) The frequency domain resource allocation domain indicates RBGs allocated to terminals, and the sizes of the RBGs are determined based on the first bandwidth; 2) The frequency domain resource allocation domain includes an RIV for indicating a starting RB and a consecutive RB length.

It will be appreciated by those skilled in the art that the implementation functions of the units in the frequency domain resource determining apparatus shown in fig. 4 can be understood with reference to the relevant description of the foregoing method. The functions of the units in the frequency domain resource determining apparatus shown in fig. 4 may be implemented by a program running on a processor or by a specific logic circuit.

Fig. 5 is a schematic diagram ii of the structural composition of the device for determining frequency domain resources provided in the embodiment of the present application, which is applied to a network device, as shown in fig. 5, where the device for determining frequency domain resources includes:

a transmitting unit 501, configured to transmit DCI to a 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 a first bandwidth or a second bandwidth; the DCI indicates a slot offset value.

In this embodiment of the present application, the first bandwidth and the second bandwidth are associated with the same bandwidth portion BWP; or, the first BWP or the first frequency domain resource having the first bandwidth and the second BWP or the second frequency domain resource having the second bandwidth have an association relationship.

It will be appreciated by those skilled in the art that the implementation functions of the units in the frequency domain resource determining apparatus shown in fig. 5 can be understood with reference to the relevant description of the foregoing method. The functions of the units in the frequency domain resource determining apparatus shown in fig. 5 may 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, where the processor 610 may call and run a computer program from a memory to implement the methods in embodiments of the present application.

Optionally, as shown in fig. 6, the communication device 600 may also include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from 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, and in particular, 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, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be specifically a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a mobile terminal/terminal in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the mobile terminal/terminal in each method in the embodiment of the present application, which is not described herein for brevity.

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

Optionally, as shown in fig. 7, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the methods in embodiments of the present application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, 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 in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal in the embodiments of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal in each method in the embodiments of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding processes implemented by the mobile terminal/terminal in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal in the methods in the embodiments of the present application, and for brevity, will not be described in detail herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of 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 in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for determining frequency domain resources, the method comprising:

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;

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the first bandwidth and the second bandwidth are associated with the same bandwidth part BWP or frequency domain resource; or alternatively, the process may be performed,

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 have an association relationship.

3. The method of 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 resource of the terminal has the first bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a first manner.

4. The method of 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 resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel according to the first mode.

5. The method of claim 3 or 4, wherein the first mode comprises at least one of:

the frequency domain resource allocation domain indicates a resource block group RBG allocated to a terminal, the RBG being sized based on a bandwidth possessed by BWP or frequency domain resources of the terminal at a slot determined according to the slot offset value;

the frequency domain resource allocation domain includes a resource indication value RIV for indicating a starting resource block RB and a consecutive RB length.

6. The method of 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 resource of the terminal has the second bandwidth in the slot determined according to the slot offset value, the terminal determines the frequency domain resource of the physical shared channel in a second manner.

7. The method of claim 6, wherein the second mode comprises at least one of:

8. The method of 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 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 according to a third mode.

9. The method of claim 8, wherein the third mode comprises at least one of:

10. The method of claim 7, wherein, for the case where the frequency domain resource allocation domain indicates an RBG allocated to the terminal,

11. The method of claim 10, wherein, for the case where the first number of RBGs is less than the second number of RBGs,

each bit in a first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, each bit in a second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, values of the X1 and the X2 are determined based on the first RBG number and the second RBG number, the number of the first part of bits is determined based on the value of the X1, the value of the X2, the first RBG number and the second RBG number, and the number of the second part of bits is determined based on the first RBG number and the number of the first part of bits.

12. The method of claim 7, wherein, for the case where the frequency domain resource allocation domain comprises a RIV,

if it isThen (I)>

Otherwise the first set of parameters is selected,

wherein, the liquid crystal display device comprises a liquid crystal display device,L _RBs is a continuous RB length, RB _start Is the start RB of the radio bearer, is the first bandwidth, < >>Is the second bandwidth.

13. The method of claim 9, wherein, for the case where the frequency domain resource allocation domain indicates an RBG allocated to the terminal,

14. The method of claim 13, wherein, for the case where the second number of RBGs is less than the first number of RBGs,

each bit in a first part of bits in the frequency domain resource allocation domain corresponds to X1 RBGs, each bit in a second part of bits in the frequency domain resource allocation domain corresponds to X2 RBGs, values of the X1 and the X2 are determined based on the first RBG number and the second RBG number, the number of the first part of bits is determined based on the value of the X1, the value of the X2, the first RBG number and the second RBG number, and the number of the second part of bits is determined based on the second RBG number and the number of the first part of bits.

15. A method for determining frequency domain resources, the method comprising:

16. The method of claim 15, wherein the step of providing the first layer comprises,

17. A device for determining frequency domain resources, applied to a terminal, the device comprising:

a receiving unit, configured to receive 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; the DCI indicates a slot offset value.

18. A device for determining frequency domain resources, the device being applied to a network device, the device comprising:

19. A terminal, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 1 to 14.

20. A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 15 to 16.

21. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 14 or the method of any one of claims 15 to 16.

22. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 14 or the method of any one of claims 15 to 16.