WO2020030253A1

WO2020030253A1 - Reducing dci payload

Info

Publication number: WO2020030253A1
Application number: PCT/EP2018/071399
Authority: WO
Inventors: Xiaohui Liu; Neng Wang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2018-08-07
Filing date: 2018-08-07
Publication date: 2020-02-13

Abstract

Before a client device can receive data via a physical downlink shared channel, PDSCH, the client device needs to identify which frequency resources the PDSCH uses. The client device may obtain this information from downlink control information, DCI, and the client device can receive the DCI via a physical downlink control channel, PDSCH. It is an object to provide a procedure for reducing DCI payload in wireless radio communication. The DCI may indicate a relation between PDCCH frequency resources and PDSCH frequency resources. The client device may use the DCI in combination with a priori information about the PDCCH frequency resources to deduce the PDSCH frequency resources. A client device, a network access device, methods, and a computer program are described.

Description

REDUCING DCI PAYLOAD

TECHNICAL FIELD

The disclosure relates to a field of wireless radio communications, and more particularly to a client device, a network device, and a procedure for reducing DCI payload. Furthermore, the disclosure relates to corresponding methods and a computer program.

BACKGROUND

In New Radio, NR, enhanced Mobile Broad Band, eMBB, and Ultra Reliable and Low Latency Communication, URLLC, are intended for different type of scenarios with respect to target block error rate, BLER, and latency even though they can be unified into the same framework. eMBB may provide greater data bandwidth complemented by moderate latency improvement compared to 4G LTE. The target BLER for eMBB may be 10 ¹ which is the same as in LTE. URLLC is designed for mission critical applications that can be especially latency- sensitive, and the target BLER for URLLC can be 10 ⁵, which may be more challenging to achieve than the 10 ¹ target in eMBB.

Before a client device can receive data via a physical downlink shared channel, PDSCH, in eMBB or URLLC, the client device needs to identify which frequency resources the PDSCH uses. The client device may obtain this information from downlink control information, DCI, and the client device can receive the DCI via a physical downlink control channel, PDSCH.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

It is an object to provide a procedure for reducing DCI payload in wireless radio communication. The object is achieved by the features of the independent claims. Further implementation forms are provided in the dependent claims, the description and the figures.

According to a first aspect, a network access device is configured to: assign a first plurality of frequency resources for a physical downlink control channel, PDCCH; assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH; transmit a downlink control information, DCI, to a client device via the PDCCH, wherein the DCI indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources; and transmit PDSCH data via the PDSCH to the client device. With these configurations, the network access device can, for example, reduce the DCI payload. Since the relation between the PDCCH and the PDSCH is used to indicate the frequency resources, reduced amount of information may need to be transmitted in the DCI.

In an implementation form of the first aspect, the network access device is further configured to: schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the relation. With these configurations, the network access device can, for example, efficiently use the reduced DCI payload to schedule frequency resources for the PDSCH and the PDCCH.

In a further implementation form of the first aspect, the network access device is further configured to: indicate the relation in the DCI using a field. With these configurations, the network access device can, for example, indicate the relation with increased flexibility.

In a further implementation form of the first aspect, the network access device is further configured to: indicate the relation in the DCI using a frequency domain resource assignment, FDRA, field. With these configurations, the network access device can, for example, indicate the relation with increased flexibility and compatibility.

In a further implementation form of the first aspect, the network access device is further configured to: in response to the first plurality of frequency resources and the second plurality of frequency resources being the same, omitting a frequency domain resource assignment, FDRA, field from the DCI. With these configurations, the network access device can, for example, indicate the frequency resources for the PDSCH even without transmitting the FDRA field in the DCI. This may further reduce DCI payload.

In a further implementation form of the first aspect, the FDRA field includes a frequency offset parameter, wherein the frequency offset parameter indicates a frequency offset between the first and the second pluralities of frequency resources. With these configurations, the network access device can, for example, indicate the frequency resources with reduce DCI payload even if there is little or no overlap between the first and second pluralities of frequency resources.

In a further implementation form of the first aspect, the FDRA field includes a range scaling parameter, wherein the range scaling parameter indicates a frequency range scale between the first and the second pluralities of frequency resources. With these configurations, the network access device can, for example, indicate the frequency resource with reduced DCI payload even if the first and second pluralities of frequency resources comprise different amounts of frequency resources.

According to a second aspect, a client device is configured to: receive a downlink control information, DCI, from a network access device via a physical downlink control channel, PDCCH, using a first plurality of frequency resources, wherein the DCI indicates a relation between the first plurality of frequency resources and a second plurality of frequency resources; deduce the second plurality of frequency resources using the first plurality of frequency resources and the relation indicated in the DCI; and receive a physical downlink shared channel, PDSCH, data from the network access device via a PDSCH using the second plurality of frequency resources. With these configurations, the client device can, for example, deduce the second plurality of frequency resources from the first plurality of frequency resources and the reduced DCI payload.

According to a third aspect, a network access device is configured to: assign a first plurality of frequency resources for a physical downlink control channel, PDCCH; assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH; transmit by a downlink control information, DCI, or radio resource control, RRC, information to a client device, wherein the DCI or RRC information comprises a granularity parameter, wherein the granularity parameter indicates a granularity of the second plurality of frequency resources; and transmit PDSCH data via the PDSCH to the client device. With these configurations, the network access device can, for example, reduce the DCI or RRC payload.

In an implementation form of the third aspect, the DCI or RRC information further indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources. With these configurations, the network access device can, for example, use both the relation between the frequency resources and the granularity in order to reduce the DCI or RRC payload even further.

In a further implementation form of the third aspect, the network access device is further configured to schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the granularity parameter and/or the relation. With these configurations, the network access device can, for example, efficiently use the reduced DCI or RRC payload to schedule frequency resources for the PDSCH and the PDCCH.

According to a fourth aspect, a client device is configured to: receive a downlink control information, DCI, or radio resource control, RRC, information from a network access device, using a first plurality of frequency resources, wherein the DCI or RRC information comprises a granularity parameter, wherein the granularity parameter indicates a granularity of a second plurality of frequency resources; receive a physical downlink shared channel, PDSCH, data from the network access device via the PDSCH using the second plurality of frequency resources. With these configurations, the client device can, for example, deduce the frequency resources based on the reduced DCI or RRC payload.

According to a fifth aspect, a method comprises: assigning a first plurality of frequency resources for a physical downlink control channel, PDCCH; assigning a second plurality of frequency resources for a physical downlink shared channel, PDSCH; transmitting a downlink control information, DCI, to a client device via the PDCCH, wherein the DCI indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources; and transmitting PDSCH data via the PDSCH to the client device.

According to a sixth aspect, a method comprises: receiving a downlink control information, DCI, from a network access device via a physical downlink control channel, PDCCH, using a first plurality of frequency resources, wherein the DCI indicates a relation between the first plurality of frequency resources and a second plurality of frequency resources; deducing the second plurality of frequency resources using the first plurality of frequency resources and the relation indicated in the DCI; and receiving a physical downlink shared channel, PDSCH, data from the network access device via a PDSCH using the second plurality of frequency resources.

According to the seventh aspect, a computer program is provided, comprising program code configured to perform a method according to the fifth aspect or the sixth aspect when the computer program is executed on a computer.

Many of the attendant features will be more readily appreciated as they become better understood by reference to the following detailed description considered in connection with the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

The present description will be better understood from the following detailed description read in light of the accompanying drawings, wherein:

FIG. 1 illustrates a schematic representation of a client device configured for reduced DCI payload according to an embodiment;

FIG. 2 illustrates a schematic representation of a network access device configured reduced DCI payload according to an embodiment; FIG. 3 illustrates a schematic representation of a time- frequency diagram according to an embodiment;

FIG. 4 illustrates a schematic representation of a time- frequency diagram according to another embodiment;

FIG. 5 illustrates a schematic representation of frequency resource assignment according to a comparative example;

FIG. 6 illustrates a schematic representation of frequency resource assignment according to an embodiment;

FIG. 7 illustrates a schematic representation of frequency resource assignment according to another embodiment;

FIG. 8 illustrates a schematic representation of frequency domain resource assignment using a range scale parameter according to an embodiment; and

FIG. 9 illustrates a schematic representation of frequency domain resource assignment using an offset parameter according to an embodiment.

Like references are used to designate like parts in the accompanying drawings.

DETAILED DESCRIPTION

The detailed description provided below in connection with the appended drawings is intended as a description of the embodiments and is not intended to represent the only forms in which the embodiment may be constructed or utilized. However, the same or equivalent functions and structures may be accomplished by different embodiments.

FIGs 1 and 2 schematically illustrate a client device 100, such as a wireless device, in a wireless communication system according to an embodiment. The client device 100 comprises a processor 101, a transceiver 102, and memory 103. The client device 100 may be configured to perform the functionalities and operations relating to it as described in the embodiments. The wireless communication system also comprises a network device 200, such as a transmission and reception point, TRP, or a 5G base station, gNB, which may also comprise a processor 201 and a transceiver 202. The network device 200 may also be configured to perform the functionalities and operations relating the network device 200 as described in the embodiments.

According to an embodiment, the client device 100 is configured to receive a downlink control information, DCI, from the network access device 200 via a physical downlink control channel, PDCCH, using a first plurality of frequency resources. The DCI can indicate a relation between the first plurality of frequency resources and a second plurality of frequency resources. The client device 100 can deduce the second plurality of frequency resources using the first plurality of frequency resources and the relation indicated in the DCI. The client device 100 can then receive a physical downlink shared channel, PDSCH, data from the network access device 200 via a PDSCH using the second plurality of frequency resources.

According to an embodiment, the network access device 200 is configured to assign a first plurality of frequency resources for a physical downlink control channel, PDCCH and assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH. The network access device can transmit a downlink control information, DCI, to the client device 100 via the PDCCH, wherein the DCI indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources. The network access device can then transmit PDSCH data via the PDSCH to the client device 100.

Since the DCI may indicate a relation between the first and second pluralities of frequency resources, DCI payload may be reduced. Using the relation and the first plurality of frequency resources, the client device 100 can deduce the second plurality of frequency resources. Thus, the relation may be used to limit the possible bandwidth using a priori information. The a priori information can be the first plurality of frequency resources. Since the client device 100 comprises the a priori information, less information may be needed to be transmitted in the DCI.

The network access device 200 can also be configured to schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the relation.

The network access device 200 can indicate the relation in the DCI using, for example, a field. In some embodiments, the field can be a frequency domain resource assignment, FDRA, field. A field may refer to for example, any data structure.

The client device 100 and the network access device 200 may further comprise other components that are not illustrated in FIGs 1 and 2. The client device 100 may communicate with, for example, the network access device 200 using the transceiver 102. The network access device 200 may communicate with, for example, a single or a plurality of client devices 100 using the transceiver 202. The client device 100 may communicate with, for example, a single or a plurality of network access devices 200 using the transceiver 102. The client device 100 may also comprise a plurality of transceivers 102 and communicate with the plurality of network access devices 200 using the plurality of transceivers 102. For example, the client device 100, such as a mobile phone, can be served by one gNodeB or multiple gNodeBs. For example, in dual connectivity, the client device 100 can be served by two gNodeBs. In carrier aggregation, the client device 100 can be served by more than one carrier. The client device 100 may be any of a User Equipment (UE) in Long Term Evolution (LTE) or 5G new radio (NR), mobile station (MS), wireless terminal, or mobile terminal which is enabled to communicate wirelessly in a wireless communication system, sometimes also referred to as a cellular radio system. The client device 100 may further be referred to as a mobile telephone, a cellular telephone, a computer tablet or a laptop with wireless capability. The client device 100 in the present context may be, for example, a portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice or data, via a radio access network, with another entity, such as another receiver or a server. The client device 100 can be a Station (STA) which is any device that contains an IEEE 802.11 -conformant Media Access Control (MAC) and Physical Layer (PHY) interface to the Wireless Medium (WM).

The network access device 200 may be a transmission or reception point, TRP, or a NR 5G base station, gNB. The network access device 200 may be a base station, a (radio) network node or an access node or an access point or a base station, e.g., a Radio Base Station (RBS), which in some networks may be referred to as a transmitter,“eNB”,“eNodeB”,“gNB”, “gNodeB”,“NodeB”, or“B node”, depending on the technology and terminology used. The radio network nodes may be of different classes such as, e.g., macro eNodeB, home eNodeB or pico base station, based on transmission power and thereby also cell size. The radio network node can be a Station (STA) which is any device that contains an IEEE 802.11 -conformant Media Access Control (MAC) and Physical Layer (PHY) interface to the Wireless Medium (WM).

FIG. 3 illustrates a schematic representation of time-frequency diagram for downlink, DL, transmission in eMBB according to an embodiment. In FIG. 3 and in similar figures herein, time runs along the horizontal direction, and frequency runs along the vertical direction. Each square in FIG. 3 may correspond to a single orthogonal frequency-division multiplexing, OFDM, subcarrier frequency in the frequency dimension and a single OFDM symbol in the time dimension. Each such square may be referred to as a resource element. FIG. 3 comprises 14 OFDM symbols. Such collection of OFDM symbols may be referred to as a subframe.

Each resource element may be assigned for a certain function. For example, in FIG. 3, first two OFDM symbols (0 and 1) are assigned for a physical downlink control channel, PDCCH, 301. OFDM symbol 2 is assigned for reference signals, RS, and the reference signals are divided into code division multiplexing, CMD, group 0 303 and CDM group 1 302. The reference signals may be, for example, dedicated demodulation reference signals, DMRSs. Some resource elements are also assigned for data 304. The data 304 may be, for example, physical downlink shared channel, PDSCH, data.

FIG. 4 illustrates a schematic representation of time-frequency diagram for downlink, DL, transmission in URLLC according to another embodiment. The time-frequency diagram presented in FIG. 4 may be similar to that presented for eMBB in FIG. 3. However, the diagram in FIG. 4 comprises only 7 OFDM symbols. Such collection of OFDM symbols may be referred to as a resource block. Each subframe may comprise two resource blocks. URLLC may have only one DMRS symbol 302 for channel estimation due to overhead considerations. Other DMRSs may be configured, for example, on OLDM symbol 4. This may only be desirable for edge cases with extremely high Doppler shift due to the additional 20% DMRS overhead. Lurthermore, less OLDM symbol may be assigned for PDSCH data 304 in URLLC compared to eMBB as can be seen by comparing LIG. 3 with LIG. 4.

In order to decode the PDSCH data 304, the client device 100 may need to first decode the PDCCH data 301 in order to obtain related control information of DMRS 302, 303 and PDSCH 304. The control information may comprise, for example, frequency domain resource assignment which may indicate where the DMRS 302, 303 and PDSCH 304 are allocated in frequency.

LIG. 5 illustrates a schematic representation of frequency domain resource assignment according to a comparative example. In LIG. 5 the indicated subcarriers have been assigned for PDSCH data 304. LIG. 5 only illustrates resource elements for a selected bandwidth part, BWP, 501. In order for the client device 100 to be able to receive and decode the PDSCH data 304, the network access device 200 may indicate the location of the PDSCH data 304 to the client device 100. In this example, the network access device 200 needs to indicate the whole BWP 501 counted, for example, in physical resource blocks. The network access device 200 can use, for example, the frequency domain resource assignment, LDRA, field in the DCI to indicate the location of the PDSCH data 304. The network access device 200 may transmit the DCI to the client device 100 via the PDCCH 301. Alternatively, the network access device 200 may use radio resource control, RRC, to indicate the location of the PDSCH 304 to the client device 100.

DCI formats for scheduling the physical uplink shared channel, PUSCH, may be referred to as Pormat 0 0 and Pormat 0 1. DCI formats for scheduling the PDSCH may be referred to as Pormat 1 0 and Pormat 1 1.

The number of bits required for the LDRA field in the aforementioned formats in the example of PIG. 5 may be expressed as

or

N_RB ^BWP '^s the size of the active DL bandwidth parts, P is the size of the resource block group, and \x] indicates the ceiling function.

FIG. 6 illustrates a schematic representation of frequency domain resource assignment according to an embodiment. In this embodiment, PDSCH 304 occupies the same frequency resources 601 as PDCCH 301. Therefore, the DCI format can be defined without a FDRA field. The network access device 200 can, for example, transmit the DCI to the client device 100 without the FDRA field. Based on the absence of the FDRA field, the client device 100 can deduce that the PDSCH 304 uses the same radio resources as the PDCCH 301. Based on the smaller DCI format without this field, the network access device 200 can schedule PDSCH 304 and PDCCH 301 with the same frequency resources. The client device 100 can directly find PDSCH based on frequency resources where PDCCH 301 is decoded and cyclic redundancy check, CRC, is passed.

Hence, according to such an embodiment, the network access device 200 is configured to in response to the first plurality of frequency resources and the second plurality of frequency resources being the same, omit the frequency domain resource assignment, FDRA, field from the DCI.

FIG. 7 illustrates a schematic representation of frequency domain resource assignment according to another embodiment. In FIG. 7, the PDSCH 304 occupies frequency resources in the frequency region also occupied by the corresponding PDCCH 301. The PDSCH 304 may, for example, occupy a subset of the frequency resources 601 occupied by the PDCCH 301. The FDRA field can be reduced using this restriction. With the smaller DCI, the network access device 200 can schedule PDSCH 304 in a frequency region occupied by PDCCH 301. The client device 100 can find the PDSCH 304 using the FDRA field and the PDCCH frequency resources 601 where the PDCCH 301 is decoded and CRC is passed. In this embodiment, the number of bits required for the FDRA field can be expressed as

or

Here, NR ^CCH is the size of bandwidth occupied by the corresponding PDCCH 301. Thus, using the relation between the PDCCH frequency resources and the PDSCH frequency resources, the DCI payload can be reduced. The PDSCH frequency resources can be expressed in the DCI in relation to the PDCCH frequency resources. Since the client device 100 knows which frequency resources are configured for the PDCCH, the client device 100 can use this a priori information in combination with the DCI to deduce the PDSCH frequency resources.

FIG. 8 illustrates a schematic representation of frequency domain resource assignment using a range scaling parameter according to an embodiment. In this embodiment, the PDSCH 304 occupies more frequency resources than the PDCCH 301. In such cases, the FDRA field may comprise a scaling parameter X so that

. Additionally, a frequency reference point can be defined in PDCCH 301 frequency region. The reference point can be, for example, the start or middle point of the frequency resources for the PDCCH 301. For example, in the embodiment of FIG. 8, if the PDCCH 301 region are scaled to scale 801, X = 2 and frequency reference point can be the middle of the PDCCH region 301. When using the scaling parameter, the number of bits required for the FDRA field may be reduced to

The PDSCH frequency resources can be expressed in the DCI in relation to the PDCCH frequency resources using the scaling parameter X. Since the client device 100 knows which frequency resources are configured for the PDCCH, the client device 100 can use this a priori information in combination with the scaling parameter X comprised in the DCI to deduce the PDSCH frequency resources.

Hence, according to an embodiment, the FDRA field includes a range scaling parameter, wherein the range scaling parameter indicates a frequency range scale between the first and the second pluralities of frequency resources.

FIG. 9 illustrates a schematic representation of frequency domain resource assignment using an offset parameter according to an embodiment. In this embodiment, the PDSCH 304 may occupy different frequency resources from the PDCCH 301. There may even be little or no overlap between the frequency resources 901 of the PDCCH 301 and the frequency resources 902 of the PDSCH 304. This can be taken into account with a configurable offset parameter, and the frequency allocation of the PDSCH 304 can be indicated based on the FDRA field in a frequency region of PDCCH 301 plus the configured offset parameter.

The PDSCH frequency resources can be expressed in the DCI in relation to the PDCCH frequency resources using the offset parameter. Since the client device 100 knows which frequency resources are configured for the PDCCH, the client device 100 can use this a priori information in combination with the offset parameter comprised in the DCI to deduce the PDSCH frequency resources.

Hence, according to such an embodiment, the FDRA field includes a frequency offset parameter, wherein the frequency offset parameter indicates a frequency offset between the first and the second pluralities of frequency resources.

According to a further embodiment, a DCI or RRC configurable frequency granularity or unit may be used with the FDRA field. For example, the granularity or unit can be 1 resource block, RB, 2 RB, 3 RB, 4 RB, etc. For a granularity of N RB, the RBs may be grouped into groups of size N, which may reduce the payload size. For example, in case of granularity 2RB is configured in DCI formats for scheduling of PDSCH may be reduced to

Naturally, the granularity may be used in combination with any of the embodiments presented above. In such embodiments, both the advantages presented above and the advantages introduced by the granularity may be used to reduce the size of the DCI. For example, in case granularity 2RB is configured in DCI formats for scheduling of PDSCH, the number of bits required for the FDRA field may be reduced to

According to an embodiment, the network access device 200 is configured to assign a first plurality of frequency resources for a physical downlink control channel, PDCCH and assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH. The network access device 200 can transmit by a downlink control information, DCI, or radio resource control, RRC, information to a client device, wherein the DCI or RRC information comprises a granularity parameter. The granularity parameter indicates a granularity of the second plurality of frequency resources. The network access device 200 can then transmit PDSCH data via the PDSCH to the client device.

In some embodiments, the DCI or RRC information further indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources.

The network access device 200 may also schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the granularity parameter and/or the relation.

According to an embodiment, the client device 100 is configured to receive a downlink control information, DCI, or radio resource control, RRC, information from the network access device 200, using a first plurality of frequency resources. The DCI or RRC information comprises a granularity parameter, and the granularity parameter indicates a granularity of a second plurality of frequency resources. The client device 100 can then receive a physical downlink shared channel, PDSCH, data from the network access device 200 via the PDSCH using the second plurality of frequency resources.

As can be seen from the embodiments above, FDRA field in the DCI can be simplified given the a priori knowledge that PDSCH is scheduled within same frequency of PDCCH instead of the whole BWP. Specifically, if PDSCH is scheduled with the same frequency of PDCCH, DCI may be defined without the FDRA field. Any of the features presented in the embodiments above may be combined in order to reduce the DCI payload.

Embodiments of the this invention can be especially useful for URLLC due to desired reduction of PDCCH payload size. However, the invention can also be applied in other scenarios like eMBB and massive machine type communications, mMTC.

Using embodiments of the invention, a more compact field of frequency domain resource assignment in DCI can be achieved, since the bandwidth union of PDCCH and PDSCH can commonly be smaller than the BWP. For example, number of bits needed assuming 100-

RB BWP and 10-RB PDSCH+PDCCH in case of Format

(bit) vs. [log₂ (l0 X iy¹)] = 6 (bit), where 7 bits can be saved. Thus, 53.8% of frequency domain resource assignment field and 17.1% of whole DCI payloads can be saved. In another example, if the same frequency resources are occupied by PDCCH and PDSCH, number of bits saved assuming 100-RB BWP in case of Format 1 0 can be (100 x 1^)1 = 13 (bit). Thus, 31.7% of the whole DCI payload can be saved. The DCIs presented in the embodiments above can be defined as new DCI formats. The client device 100 may blindly detect the DCI format. Additional signalling may not be required, but number of blind detection can increase linearly with number of new DCI formats defined.

Alternatively, the new DCIs can be defined as a configurable format, and, for example, RRC or DCI signalling can be designed to assist interpretation of each field in the configurable format. For example, a RRC signal / DCI field can be used to indicate frequency granularity of frequency resources assumed in the FDRA field. RRC signal / DCI field can be used to indicate the offset of PDSCH frequency resource relative to PDCCH. As another example, a RRC signal / DCI field can be used to indicate the scale parameter X.

Considering the possible complexity of blind detection at the client device 100, a subset of DCI formats may be configured to the client device 100 via RRC signalling.

It should be appreciated that the frequency resources of PDCCH can be configured using, for example, a control resource set, CORESET. This may comprise, for example, number of RBs in frequency domain in a CORESET (determined by RRC Parameter CORESET-freq- dom), number of symbols in time domain in a CORESET (determined by RRC Parameter CORESET-time-dur), number of REGs in a CORESET, REG Bundle Size, (set by CORESET - REG-bundle-size), precoder granularity (set by CORESET-precoder-granularity).

Therefore, in some embodiments, PDSCH can occupy frequency resources in frequency region defined by CORESET. CORESET-REG-bundle-size and CORESET-precoder- granularity may indicate bundle size and precoder granularity of PDSCH.

The functionality described herein can be performed, at least in part, by one or more computer program product components such as software components. According to an embodiment, the network access device 100 and/or the client device 200 comprise the processor 101, 201 configured by the program code when executed to execute the embodiments of the operations and functionality described. Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), Graphics Processing Units (GPUs).

Any range or device value given herein may be extended or altered without losing the effect sought. Also any embodiment may be combined with another embodiment unless explicitly disallowed. Although the subject matter has been described in language specific to structural features and/or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as embodiments of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be understood that reference to 'an' item may refer to one or more of those items. The term‘and/or’ may be used to indicate that one or more of the cases it connects may occur. Both, or more, connected cases may occur, or only either one of the connected cases may occur.

The operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and scope of the subject matter described herein. Aspects of any of the embodiments described above may be combined with aspects of any of the other embodiments described to form further embodiments without losing the effect sought.

The term 'comprising' is used herein to mean including the method, blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, embodiments and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of this specification.

Claims

1. A network access device (200), configured to:

assign a first plurality of frequency resources for a physical downlink control channel, PDCCH, (301);

assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH, (304);

transmit a downlink control information, DCI, to a client device (100) via the PDCCH, wherein the DCI indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources; and

transmit PDSCH data via the PDSCH to the client device.

2. The network access device of claim 1, further configured to:

schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the relation.

3. The network access device of any preceding claim, further configured to: indicate the relation in the DCI using a field.

4. The network access device of claim 1 or 2, further configured to:

indicate the relation in the DCI using a frequency domain resource assignment, FDRA, field.

5. The network access device of claim 1 or 2, further configured to:

in response to the first plurality of frequency resources and the second plurality of frequency resources being the same, omitting a frequency domain resource assignment, FDRA, field from the DCI.

6. The network access device of claim 4, wherein the FDRA field includes a frequency offset parameter, wherein the frequency offset parameter indicates a frequency offset between the first and the second pluralities of frequency resources.

7. The network access device of claim 4 or 5, wherein the FDRA field includes a range scaling parameter, wherein the range scaling parameter indicates a frequency range scale between the first and the second pluralities of frequency resources.

8. A client device (100), configured to:

receive a downlink control information, DCI, from a network access device (200) via a physical downlink control channel, PDCCH (301), using a first plurality of frequency resources, wherein the DCI indicates a relation between the first plurality of frequency resources and a second plurality of frequency resources;

deduce the second plurality of frequency resources using the first plurality of frequency resources and the relation indicated in the DCI; and

receive a physical downlink shared channel, PDSCH (304), data from the network access device via a PDSCH using the second plurality of frequency resources.

9. A network access device (200), configured to:

assign a first plurality of frequency resources for a physical downlink control channel, PDCCH;

assign a second plurality of frequency resources for a physical downlink shared channel, PDSCH;

transmit by a downlink control information, DCI, or radio resource control, RRC, information to a client device, wherein the DCI or RRC information comprises a granularity parameter, wherein the granularity parameter indicates a granularity of the second plurality of frequency resources; and

transmit PDSCH data via the PDSCH to the client device.

10. The network access device of claim 9, wherein the DCI or RRC information further indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources.

11. The network access device of claim 9 or 10, further configured to schedule the second plurality of frequency resources for the PDSCH and the first plurality of frequency resources for the PDCCH based on the granularity parameter and/or the relation.

12.A client device (100), configured to:

receive a downlink control information, DCI, or radio resource control, RRC, information from a network access device, using a first plurality of frequency resources, wherein the DCI or RRC information comprises a granularity parameter, wherein the granularity parameter indicates a granularity of a second plurality of frequency resources; receive a physical downlink shared channel, PDSCH, data from the network access device via the PDSCH using the second plurality of frequency resources.

13. A method, comprising:

assigning a first plurality of frequency resources for a physical downlink control channel, PDCCH;

assigning a second plurality of frequency resources for a physical downlink shared channel, PDSCH;

transmitting a downlink control information, DCI, to a client device via the PDCCH, wherein the DCI indicates a relation between the first plurality of frequency resources and the second plurality of frequency resources; and

transmitting PDSCH data via the PDSCH to the client device.

14. A method, comprising:

receiving a downlink control information, DCI, from a network access device via a physical downlink control channel, PDCCH, using a first plurality of frequency resources, wherein the DCI indicates a relation between the first plurality of frequency resources and a second plurality of frequency resources;

deducing the second plurality of frequency resources using the first plurality of frequency resources and the relation indicated in the DCI; and

receiving a physical downlink shared channel, PDSCH, data from the network access device via a PDSCH using the second plurality of frequency resources.

15. A computer program comprising program code configured to perform a method according to claim 13 or claim 14 when the computer program is executed on a computer.