Patent Description:
In the fourth generation (<NUM>) or Long Term Evolution (LTE) system, time duration of Physical Downlink Control Channels (PDCCHs) is known by all user equipment (UEs). This time duration typically occupies the first <NUM> to <NUM> symbols across a system bandwidth (BW), which is indicated by a Control Format Indicator (CFI) broadcast in a Physical control format indicator channel (PCFICH) every Transmission Time Interval (TTI). The other symbols across the system bandwidth are used for Physical Downlink Shared Channels (PDSCHs).

In the fifth generation (<NUM>) New Radio (NR), division of control resources and data resources is more flexible in the system bandwidth. The control resources comprise at least one UE-specific control resource set configured for the individual UEs and a common control resource set configured for all the UEs. The symbols and subcarriers occupied by the control resources are dynamically allocated in a time domain and a frequency domain. Typically, control resource sets occupy a small part of the bandwidth.

Physical resource sharing between the PDCCHs and the PDSCHs is proposed for <NUM> NR. Many agreements for this physical resource sharing are reached from vendors and service providers, but some key capabilities still remain FFS (for further study). <CIT> discloses rate matching of data transmission in control resource region.

In general, example embodiments of the present disclosure provide a device, method, apparatus and computer readable storage medium for reusing control resources for data transmission. Examples which may not be covered by the claims are provided for the understanding of the invention.

In a first aspect, a device is provided comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the device to in response to downlink data to be transmitted to a terminal device, determine, at a network device, a control resource set associated with the terminal device in a control resource region. The device is caused to select, from the control resource set, localized control resources for control information associated with the downlink data and select data resources for the downlink data in both the control resource region and a data resource region.

The device is further caused to transmit the control information to the terminal device by using the localized control resources and transmit the downlink data to the terminal device by using the data resources.

In some example embodiments, the control resource set may be determined by searching a database for a record indicating the association of the control resource set and the terminal device. In some example embodiments, if the terminal device attaches to the network device, the control resource set may be associated with the terminal device, and an indication of the association of the control resource set and the terminal device may be added in the record. In some example embodiments, if the terminal device detaches from the network device, the indication of the association of the control resource set and the terminal device may be removed from the record.

In some example embodiments, it may be determined, based on at least one of a data type and a priority associated with the downlink data, whether the downlink data is allowed to be transmitted in the control resource set. If the downlink data is allowed to be transmitted in the control resource set, the data resources may be selected in the control resource set.

In some example embodiments, when selecting the data resources, a default data resource block for the downlink data may be selected in both the control resource region and the data resource region. Resources in the default data resource block may be more than the data resources. Further, at least one skipped part of the default data resource block may be determined based on used resources in the default data resource block, and the data resources may be determined from the default data resource block by excluding the at least one skipped parts of the default data resource block.

In some example embodiments, the at least one skipped part of the default data resource block may be indicated to the terminal device by dedicated control information specific to the terminal device. In some example embodiments, at least one of frequency domain resource assignment and time domain resource assignment of the at least one skipped part of the default data resource block may be indicated to the terminal device.

In a second aspect, a method is provided. In the method, if downlink data is to be transmitted to a terminal device, a network device determines a control resource set associated with the terminal device in a control resource region. The network device selects, from the control resource set, localized control resources for control information associated with the downlink data, and selects data resources for the downlink data in both the control resource region and a data resource region. The network device transmits the control information to the terminal device by using the localized control resources, and transmits the downlink data to the terminal device by using the data resources.

In a third aspect, there is provided an apparatus comprising means for performing the method according to the second aspect.

In a fourth aspect, there is provided a computer readable storage medium that stores a computer program thereon. The computer program, when executed by a processor of a device, causes the device to perform the method according to the second aspect.

It is to be understood that the summary section is not intended to identify key or essential features of example embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure.

It is to be understood that these example embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. In particular, <FIG> and <FIG> and the related paragraphs in the description describe embodiments of the invention, whereas the other figures are presented for a better understanding of the invention.

As used herein, the term "network device" refers to a device capable of providing services to a terminal device in a communication network. The network device may include an access network device via which the terminal device can access the communication network. Examples of the access network device include a relay, an access point (AP), a transmission point (TRP), a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a New Radio (NR) NodeB (gNB), a Remote Radio Module (RRU), a radio header (RH), a remote radio head (RRH), a low power node such as a femto, a pico, and the like.

The network device may also include a core network device capable of communicating with the access network device and providing services to the terminal device in a core network. As an example, the core network device may include Mobile Switching Centers (MSCs), MMEs, Operation and Management (O&M) nodes, Operation Support System (OSS) nodes, Self-Organization Network (SON) nodes, positioning nodes, such as Enhanced Serving Mobile Location Centers (E-SMLCs), and/or Mobile Data Terminals (MDTs).

As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communications with each other or with the base station. The communications may involve transmitting and/or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information over air. In some example embodiments, the UE may be configured to transmit and/or receive information without direct human interaction. For example, the UE may transmit information to the network device on predetermined schedules, when triggered by an internal or external event, or in response to requests from the network side.

Examples of the UE include, but are not limited to, user equipment (UE) such as smart phones, wireless-enabled tablet computers, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), any wireless-enabled devices, any industry sensors/machines/robotics, and/or wireless customer-premises equipment (CPE). For the purpose of discussion, some example embodiments will be described with reference to UEs as examples of the terminal devices, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure.

As used herein, the terms "first", "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. For example, a first element could be referred to as a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.

In the <NUM> or LTE system, across the system bandwidth, the time duration of the PDCCHs typically occupies the first <NUM> to <NUM> symbols, and the other symbols are used for the PDSCHs. <FIG> shows a conventional example of <NUM> or LTE downlink resource configuration. As shown, in one subframe <NUM> of <NUM>, the first several symbols are PDCCH symbols <NUM> and the following symbols are PDSCH symbols <NUM> across subcarriers in a system bandwidth <NUM>.

In <NUM> NR, at least one UE-specific control resource set will be configured for each UE in addition to a common control resource set which can be obtained from a Master Information Block (MIB) or a System Information Block (SIB). The time duration of the UE-specific control resource set is configured by dedicated Radio Resource Control (RRC) signaling and may be different between UEs.

<FIG> shows a conventional example of resource configuration of <NUM> NR in downlink and uplink. In this example, the control resource sets in downlink occupy a small part of the bandwidth in the frequency domain and the dynamic number of symbols in the time domain. NR downlink data can use all the resources except for control resources used for Dedicated Control Information (DCI), including common DCI and UE-specific DCI, so as to achieve high frequency efficiency.

In order to improve the system efficiency, physical resource sharing between the PDCCHs and the PDSCHs is proposed for <NUM> NR.

The inventors notice that there is still a problem of how to allocate resources in a control resource region for data transmission. For example, it is whether and how much resources are available in the control resource region, what type of data can be allocated into the control resource region. There is a further problem of how to indicate the starting positions of the data resources that will overlap with the control resource sets.

Example embodiments of the present disclosure provide a novel scheme of reusing control resources for data transmission to manage reusable resources in a control resource region. With this scheme, if there is downlink data to be transmitted to a terminal device, a network device determines a control resource set associated with the terminal device in a control resource region. The network device selects localized control resources for control information associated with the downlink data (for example, DCI) from the control resource set. The network device further selects data resources for the downlink data in the control resource region and a data resource region. Then, the network device transmits the control information and the downlink data using the selected control and data resources, respectively.

The management of reusable control resources is a key challenge for PDCCH and PDSCH sharing in <NUM> NR. According to example embodiments of the present disclosure, reusable resources in the control resource region may be allocated when the network device counters, allocates, and manages resources during cell setup, attachment and detachment of the terminal device, and data transmissions, for example. The reusable resources can be used by one or multiple terminal devices. As such, control resources may be reused for data transmission effectively and efficiently.

<FIG> shows an example environment <NUM> in which example embodiments of the present disclosure can be implemented. The environment <NUM>, which is a part of a communication network, includes a terminal device <NUM> and a network device <NUM>. It is to be understood that the numbers of terminal devices and network devices are shown in <FIG> only for the purpose of illustration, without suggesting any limitation to the scope of the present disclosure. The environment <NUM> may include any suitable number of terminal devices and network devices.

The terminal device <NUM> may communicate with the network device <NUM> or with another terminal device (not shown) directly or via the network device <NUM>. The communication may follow any suitable communication standards or protocols such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), evolved Long Term Evolution (eLTE), the fifth generation (<NUM>) NR, Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, and machine type communication (MTC), enhanced mobile broadband (eMBB), massive machine type communication (mMTC), Narrow Band Internet of thing (NB-IoT), and ultra-reliable low latency communication (URLLC) technologies.

As shown, the network device <NUM> may comprise a downlink scheduler <NUM> for scheduling downlink control and data resources, and a database manager <NUM> for managing database. The downlink scheduler <NUM> is connected and exchanges with the database manager <NUM>. The downlink scheduler <NUM> and the database manager <NUM> are functionality entities or modules in the network device <NUM>. These functionality entities or modules may be implemented by a single physical entity or different physical entities. The network device <NUM> may comprise any other suitable functionality entities as needed.

In some example embodiments, the database manager <NUM> may manage the database containing record items or entries related to control resource configuration of the network device <NUM>. The usage of control resources may be dynamically recorded in the database for the network device <NUM> to manage the overall reusable resources.

It is to be understood that the maintenance or management of the database by the database manager <NUM> within the network device <NUM> is only illustrative but not limited. In some other example embodiments, the environment <NUM> may comprise a server or device which is separate from or outside of the network device <NUM> for maintaining or managing the database which may be accessed by the network device <NUM>. The network device <NUM> can communicate with the server or device and have access to the database.

In the environment <NUM>, the network device <NUM> maintains a control resource region and a data resource region. The control resource region may comprise control resources for control information transmission, and the data resource region may comprise data resources for data transmission. The resources may comprise time, frequency and/or code resources.

In various example embodiments of the present disclosure, at least a part of the control resource region can be reused for data transmission. For control information transmission, the network device <NUM> selects localized control resources from a control resource set, to improve re-usage of the control resources for the data transmission. Moreover, the localization of the control resources may reduce the complexity of data resource indications and thereby reduce signaling overhead.

<FIG> shows a flowchart of an example method <NUM> in accordance with some example embodiments of the present disclosure. The method <NUM> can be implemented at the network device <NUM> as shown in <FIG>. For the purpose of discussion, the method <NUM> will be described with reference to <FIG>.

At block <NUM>, if there is downlink data to be transmitted to the terminal device <NUM>, the network device <NUM> selects a control resource set associated with the terminal device <NUM> in a control resource region. The control information may comprise common control information, such as common DCI, and control information specific to the terminal device <NUM>, such as UE-specific DCI. Accordingly, the control resource set may comprise a common control resource set and a UE-specific control resource set.

<FIG> shows example resource configuration according to some example embodiments of the present disclosure. As shown in <FIG>, the network device <NUM> maintains a control resource region <NUM> and a data resource region <NUM>. In the control resource region <NUM>, a common control resource set <NUM> is allocated for common control information for all the UEs served by the network device <NUM>. The common control resource set <NUM> may be allocated when cell setup or in other cases for example that failure occurs.

In the control resource region <NUM>, three UE-specific control resource sets <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> (collectively referred to as a UE-specific control resource set <NUM>), labeled as UE-specific Control Resource Set#<NUM>, UE-specific Control Resource Set#<NUM> and UE-specific Control Resource Set#<NUM>, are allocated to different terminal devices for control information specific to these terminal devices, such as UE-specific DCI. These resources are dedicated for the individual terminal devices. It is to be understood the number of UE-specific control resource sets <NUM> are shown in <FIG> only for the purpose of illustration without suggesting any limitation. Any number of UE-specific control resource sets <NUM> may be possible in implementations.

The UE-specific control resource sets <NUM> may be allocated during attachment of the respective terminal devices to the network device <NUM>. The UE-specific control resource sets <NUM> may be indicated by Radio Resource Control (RRC) signaling to the individual terminal devices so that each terminal device knows its own control resources. One UE-specific control resource set <NUM> may be used for one or more terminal devices. One terminal device may be assigned to one or more UE-specific control resource sets <NUM>.

In this example, as shown, all the control resource sets <NUM> and <NUM> start from the first symbol in a time domain to further decrease the complexity of the resource configuration. In implementations, the control resource sets <NUM> and <NUM> may be configured in any suitable positions in the control resource region <NUM>.

At least a part of the control resource region <NUM> may be reused for data transmission. For example, two types of resources in the control resource region <NUM> may be reusable for data transmission, where one type labeled as Type#<NUM> is non-configured resources, and the other type labeled as Type#<NUM> is configured resource, but not used for common or UE-specific control information. The network device <NUM> may select resources for data transmission from the two types of resources.

For example, in addition to the non-configured resources in the control resource region <NUM>, the UE-specific control resource sets <NUM> may be reusable for data transmission when the resources are not scheduled for the respective UEs. As another example, the common control resource set <NUM> may also be reused for data to further improve resource utilization and efficiency.

In some example embodiments, the network device <NUM> may maintain a database (for example, managed by the database manager <NUM> as shown in <FIG>) for storing information related to the configured control resource sets <NUM> and <NUM>. For example, the database contains records or record items or entries related to the configured control resource sets <NUM> and <NUM>. Each control resource set has one unique record. In this example, when determining the control resource set associated with the terminal device <NUM>, the network device <NUM> may determine the control resource set by searching the database for a record indicating the association of the control resource set <NUM> or <NUM> and the terminal device <NUM>.

<FIG> shows an example structure of a record for the control resource sets according to some example embodiments of the present disclosure. In this example, three records <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> (collectively or individually referred to as a record <NUM>), labeled as Record#<NUM>, Record#<NUM> and Record#<NUM>, are stored in the database for example in a form of a table to identify the respective control resource sets <NUM> and <NUM>. It is to be understood that three records <NUM> are shown in <FIG> only for the purpose of illustration without suggesting any limitation. The number of records depends on the number of control resource sets configured by the network device <NUM>.

The record <NUM> involves many fields, including a "Type" field <NUM>, a "Status Resource" field <NUM>, an "Associated User" field <NUM>, a "Status" field <NUM> and a "Reusable Resource" field <NUM>.

The notes of these fields are illustrated in Table <NUM>.

As shown, the "Type" field <NUM> indicates the type of control resource set corresponding to the record <NUM>. As indicated by the "Type" field <NUM>, the record <NUM>-<NUM> corresponds to the common control resource set <NUM>, and the records <NUM>-<NUM> and <NUM>-<NUM> correspond to the UE-specific control resource sets <NUM>. In addition, the "Associated User" field <NUM> records identifiers (IDs) of the terminal devices (such as UE IDs) associated with the corresponding control resource set. The association of the control resource set and the terminal device <NUM> is indicated by the "Associated User" field <NUM>. Accordingly, with the "Associated User" field <NUM>, the association of the control resource sets and the terminal devices can be determined.

The indication of the association of the control resource set and the terminal device <NUM> may be added in the record for the control resource set when the terminal device <NUM> attaches to the network device <NUM>. For example, upon the attachment, the network device <NUM> may associate the control resource set with the terminal device <NUM> and add the indication of this association (for example, the ID of the terminal device <NUM>) in the record. Further, if the terminal device <NUM> detaches from the network device <NUM>, the network device <NUM> may remove this indication.

It is to be understood that the above fields are illustrative but not limited. It is unnecessary to contain all of these fields in the record <NUM>. Further, any other suitable fields may be contained in the record <NUM> to identify the corresponding control resource set.

The record <NUM> may be updated dynamically in the database. For example, the record <NUM> be created or inserted in the database when the corresponding control resource <NUM> or <NUM> is configured. If a control resource set <NUM> or <NUM> is deleted, the corresponding record <NUM> may be deleted from the database. Example processes for updating the records <NUM> in the database will be discussed below with reference to <FIG> and <FIG>.

<FIG> shows an example database operation process <NUM> during cell setup in accordance with some example embodiments of the present disclosure. As shown, an Operations Administration and Maintenance (OAM) <NUM> sends (<NUM>) a cell setup request to the downlink scheduler <NUM>. As an example, the OAM <NUM> may be an internal functionality entity of the network device <NUM> having a function of initiating cell setup. As another example, the OAM <NUM> may be a separate device maintained by a network operator.

Based on the cell setup request from the OAM <NUM>, the downlink scheduler <NUM> allocates (<NUM>) resources for a common control resource set <NUM>. The downlink scheduler <NUM> inserts (<NUM>) the common control resource set <NUM> into the control resource region <NUM> and sends (<NUM>) an insertion request to the database manager <NUM>. The database manager <NUM> creates (<NUM>) a database for the cell to record the control resource configuration. The database manager <NUM> inserts (<NUM>) a record <NUM> of the common control resource set <NUM> into the database.

As shown, the database may be created at the time of cell setup. After resources are allocated for the common control resource set, the corresponding record may be inserted into the database.

<FIG> shows an example database operation process <NUM> during attachment and detachment procedures in accordance with some example embodiments of the present disclosure. As shown, when the terminal device <NUM> sends (<NUM>) an attachment request, the downlink scheduler <NUM> allocates (<NUM>) resources for one or more UE-specific control resource sets <NUM> to the terminal device <NUM> and inserts (<NUM>) the UE-specific control resource sets <NUM> into the control resource region <NUM>. The downlink scheduler <NUM> sends (<NUM>) an insertion request to the database manager <NUM>. The database manager <NUM> inserts (<NUM>) a record <NUM> of the UE-specific control resource set <NUM> into the database.

When the terminal device <NUM> sends (<NUM>) a detachment request to the network device <NUM>, the downlink scheduler <NUM> fetches (<NUM>) resources from the associated UE-specific control resource set <NUM> and deletes (<NUM>) the associated UE-specific control resource set <NUM> in the control resource region <NUM>. Then, the downlink scheduler <NUM> sends (<NUM>) a deletion request to the database manager <NUM>. The database manager <NUM> deletes (<NUM>) the record <NUM> of the UE-specific control resource set <NUM>.

As shown, during the attachment procedure of the terminal device <NUM>, the associated UE-specific control resource set may be allocated to the terminal device <NUM>, and the corresponding record <NUM> may be inserted into the database. When the terminal device <NUM> detaches from the cell, the associated UE-specific control resource set may be deleted, and the record <NUM> may be removed from the database.

In some example embodiments, if the control resource set is used for more terminal devices, the record <NUM> may be updated by adding and removing the association with the terminal device <NUM>. For example, in the example embodiments where the "Associated User" field <NUM> in the record <NUM> is used to record the ID of the associated terminal devices, the ID of the terminal device <NUM> may be added into this field during the attachment procedure and removed from this field during the detachment procedure.

Example processes for inserting and deleting the record <NUM> of the control resource set as shown in <FIG> will be discussed below with reference to <FIG>.

<FIG> shows a flow chart of an example process for inserting the record <NUM> of the control resource set in accordance with some example embodiments of the present disclosure. As shown, when deciding (<NUM>) to insert the record <NUM>, it is determined (<NUM>) whether the control resource set is existed. If the control resource set is not existed, a new record is created (<NUM>) for the control resource set. Then, the ID of the terminal device (for example, UE_ID) <NUM> is added (<NUM>) into the record <NUM>.

<FIG> shows a flow chart of an example process for deleting the record <NUM> of the control resource set in accordance with some example embodiments of the present disclosure. When deciding (<NUM>) to delete the record <NUM>, it is determined (<NUM>) whether the control resource set is existed. If the control resource set is existed, the ID of the terminal device <NUM> (for example, UE_ID) is deleted (<NUM>) from the record <NUM> for the control resource set. Then, it is determined (<NUM>) whether no ID of the terminal device <NUM> is associated with the record <NUM>. If yes, the record <NUM> is deleted (<NUM>), and then the process <NUM> ends (<NUM>). Otherwise, the process <NUM> ends (<NUM>). If it is determined (<NUM>) that the control resource set is not existed, an alert "ERROR" is presented (<NUM>).

In the case that the control resource configuration of the network device <NUM> is maintained by the records <NUM> in the database, the network device <NUM> may search the database for a record indicating association of a control resource set and the terminal device <NUM> to determine the control resource set associated with the terminal device <NUM>. In the embodiments where the terminal device <NUM> is assigned to more than one control resource set, the network device <NUM> can first determine all of the associated control resource sets and select one of the UE-specific control resource sets for the terminal device <NUM>. The selection of one of the UE-specific control resource sets may be based on the usage of the UE-specific control resource sets indicated by the "Reusable Resource" field <NUM> in the record <NUM>, for example.

Still with reference to <FIG>, at block <NUM>, the network device <NUM> selects, from the control resource set, localized control resources for control information associated with the downlink data. The control information may be common or UE-specific DCI for indicating configuration related to the downlink data. The localization of the control resources may improve the resource utilization and efficiency.

In some example embodiments, the localized control resources may comprise a plurality of continuous resource elements. Examples of the resource elements include Control Channel Elements (CCEs) and resource element groups (REGs). In this way, the remaining resources in the control resource set may be continuous as well, which may be reused for the data transmission more effectively and efficiently.

In some example embodiments, in order to further improve the resource utilization and efficiency, the plurality of continuous resource elements may be selected starting from starting time and/or starting frequency of the control resource set. As such, more continuous control resources may be available to the data transmission.

<FIG> shows example resource configuration in the control resource set according to some example embodiments of the present disclosure.

As shown, the control resource set comprises multiple symbols <NUM> in the time domain and several physical resource blocks (PRBs) <NUM> in the frequency domain. For the control information associated with the downlink data to be transmitted to the terminal device <NUM>, the network device <NUM> selects several REGs <NUM> from the starting frequency (for example, the first PRB) of the control resource set. A REG may be a resource unit scheduled for the control information such as DCI. In this example, one REG comprises one PRB in the frequency domain and several symbols in the time domain. Accordingly, a bottom part <NUM> of the control resource set may be reused for the data transmission.

As another example, the control resources may be selected starting from the first symbol in the control resource set. Then, a right part of the control resource set may be available for the data transmission. It is also possible that the control resources are localized in a middle part of the control resource set, and an upper part and a bottom part of the control resource set are left.

In the example embodiments where the usage of the control resource set is stored by the corresponding record <NUM> in the database, the network device <NUM> may update the record <NUM> after allocating the control resources. For example, the control resources may be removed from the reusable resources indicated by the "Reusable Resource" set <NUM> in the record <NUM>. In some example embodiments, after the common resources have been used, the record <NUM> may be updated by adding the common resources back into the reusable resources.

<FIG> shows an example database operation process <NUM> for updating the record <NUM> in accordance with some example embodiments of the present disclosure.

In this example, in addition to the downlink scheduler <NUM> and the database manager <NUM>, the network device <NUM> comprises a Packet Data Convergence Protocol (PDCP) or Radio Resource Control (RRC) entity <NUM>, as shown. The PDCP or RRC entity <NUM> sends (<NUM>) a data packet to the downlink scheduler <NUM>. The downlink scheduler <NUM> decides (<NUM>) to fetch the control resource sets (for example, the UE-specific control resource sets) associated with the terminal device <NUM>, and then sends.

(<NUM>) a fetching request containing the ID of the terminal device <NUM> to the database manager <NUM> to fetch the control resource sets associated with the terminal device <NUM>. The database manager <NUM> returns (<NUM>) a fetching result indicating the associated control resource sets, including Control Resource Set#<NUM>, Control Resource Set#<NUM> and Control Resource Set#<NUM>, as shown.

The downlink scheduler <NUM> selects (<NUM>) one of the control resource sets for DCI related to the data packet. Then, the downlink scheduler <NUM> allocates (<NUM>) PRBs for the DCI within the selected resource set. The downlink scheduler <NUM> sends (<NUM>) an update request containing the record number and the used resources to the database manager <NUM>. The database manager <NUM> updates (<NUM>) the record <NUM> and sends (<NUM>) a positive acknowledgement (for example, ACK) to the downlink scheduler <NUM>. In this way, the downlink scheduler <NUM> can get the reusable resources from the database, and updates records after DCI is generated.

As shown in <FIG>, the downlink scheduler <NUM> transmits (<NUM>) the DCI as well as the data packet to the terminal device <NUM>. The terminal device <NUM> sends (<NUM>) an ACK to the downlink scheduler <NUM>. Further, the downlink scheduler <NUM> decides (<NUM>) to release the PRBs for the DCI, and then sends (<NUM>) another update request containing the record number and the released resources to the database manager <NUM>. The database manager <NUM> updates (<NUM>) the record and sends (<NUM>) an ACK to the downlink scheduler <NUM>.

<FIG> shows a flow chart of an example process <NUM> of updating the record <NUM> in accordance with some example embodiments of the present disclosure.

When deciding (<NUM>) to update the record <NUM>, the type of the updating is determined (<NUM>). If the updating is used to allocate PRBs for the DCI, it is determined (<NUM>) whether unused resources are enough. If yes, the PRBs for the DCI are removed (<NUM>) from the reusable resources, and then an ACK response is sent (<NUM>). If no, a negative acknowledgement (or NACK) response is sent (<NUM>). If it is determined (<NUM>) that the updating of the record is used to release the PRBs for the DCI, the PRBs are added (<NUM>) back to the reusable resources, and then an ACK response is sent (<NUM>).

As shown in <FIG> and <FIG>, during the data transmission, the downlink scheduler <NUM> may select a control resource set and further select PRBs from the control resource set for DCI, including common and UE-specific DCI. Then, the reusable resources in the corresponding record <NUM> in the database are updated by removing the PRBs for the DCIs. When the HARQ procedure for the transmission is completed (including ACKed by UE, HARQ failure, and the like), the DCI resources may be released, and the corresponding record <NUM> may be updated.

Next, still with reference to <FIG>, after the control resources are selected, the network device <NUM> selects data resources for the downlink data in both the control resource region <NUM> and the data resource region <NUM> at block <NUM>. For example, as shown in <FIG>, the data resources may be selected from the reusable control resources in the control resource region <NUM> and the data resources in the data resource region <NUM>. In some example embodiments, the control resources may be allocated in the control resource region <NUM>, and the data resources may be allocated in the data resource region <NUM>.

<FIG> shows example resource configuration for the control information and the data in accordance with some example embodiments of the present disclosure.

In this example, the control information is implemented by the UE-specific DCI. As shown, there are downlink data to be transmitted to three terminal devices, labeled as UE#<NUM>, UE#<NUM> and UE#<NUM>, respectively. A control resource block <NUM> is allocated to the DCI for UE#<NUM> in the UE-specific control resource set <NUM>-<NUM>, labeled as UE-specific control resource set#<NUM>. Control resource blocks <NUM> and <NUM> are allocated to the DCI for UE#<NUM> and UE#<NUM> in the UE-specific control resource set <NUM>-<NUM>, labeled as UE-specific control resource set#<NUM>. Data resource blocks <NUM>, <NUM> and <NUM> allocated to data for UE#<NUM>, UE#<NUM> and UE#<NUM> are located in the data domain <NUM>.

In some other example embodiments, in order to further reduce the resource fragment and thereby improve the resource utilization and efficiency, the data resources may be selected preferentially from the reusable control resources in the control resource region <NUM>. The preferential use of the reusable control resources of the control resource set may depend from the priorities of the downlink data related to a service type, Quality of Experience (QoE), latency requirements and the like. The priorities may be predefined for different service criteria and policies. As an example, the policies and criteria may comprise a data type and/or a priority associated with the downlink data. Those policies and criteria may be configurable in a network so that the network device <NUM> can dynamically determine the downlink data with optimization usage of the control resource sets in the control resource region <NUM>. Based on the policies and criteria, it may be determined whether the downlink data is allowed to be transmitted in the control resource set for control information.

For example, in <NUM> URLLC services (and mMTC services), lots of frequent and short data packets are transmitted. These short packets only use few resources but require high reliability, which is similar to DCI. Accordingly, a higher priority may be configured by the network device <NUM> for the short packets with the network policies and criteria. Therefore, the reuse of the control resource set may be prioritized for these packets. For example, the short packets may be scheduled in Type#<NUM> reusable control resource (which is configured, but not used for DCIs). Thus, the resource fragments may be decreased, and more resources may be used for the high traffic service.

In some example embodiments, the data resources may be allocated in the control resource set where the control resources are selected. For example, after the control resources are selected from the control resource set, the network device <NUM> may determine whether reusable control resources of the control resource set are sufficient to accommodate the downlink data. If the reusable control resources are sufficient, the network device <NUM> selects the data resources from the control resource set. In addition, one modulation and coding scheme (MCS) may be applied to both the control information and the downlink data to further improve transmission efficiency.

<FIG> shows example resource configuration for the control information and the data in accordance with some example embodiments of the present disclosure in accordance with some other example embodiments of the present disclosure.

Similar to the configuration as shown in <FIG>, control resources <NUM> for the DCI of UE#<NUM> are allocated in the UE-specific control resource set <NUM>-<NUM>, labeled as UE-specific control set#<NUM>, and control resources <NUM> and <NUM> for the DCI of UE#<NUM> and UE#<NUM> are allocated in the UE-specific control resource set <NUM>-<NUM>, labeled as UE-specific control set#<NUM>. Different from the configuration in <FIG>, data resources <NUM> allocated to the data for UE#<NUM> follows the control resources for the DCI of UE#<NUM> in the UE-specific control resource set <NUM>-<NUM>, and data resources <NUM> allocated to the data for UE#<NUM> follows the control resources for the DCI of UE#<NUM> in the UE-specific control resource set <NUM>-<NUM>. Data resources <NUM> are allocated to the data for UE#<NUM> in the data resource region <NUM>. In this case, the DCI and the data for UE#<NUM> may use the same MCS, and the DCI for UE#<NUM> and UE#<NUM> and the data for UE#<NUM> may use the same MCS.

<FIG> shows a flow chart of an example process <NUM> of allocating resources in accordance with some example embodiments of the present disclosure. The process <NUM> can be implemented by the downlink scheduler <NUM>.

As shown, the downlink scheduler <NUM> selects (<NUM>) the downlink data to be prioritized in the reusable resources in the control resource set for the DCI based on the predefined criteria and policies. The downlink scheduler <NUM> fetches (<NUM>) the control resource sets associated with the terminal device <NUM> from the database. Then, the downlink scheduler <NUM> receives (<NUM>) an ACK response containing indications of the associated control resource sets such as Control Resource Set#<NUM>, Control Resource Set#<NUM>, and the like.

The downlink scheduler <NUM> obtains (<NUM>) Channel State Information (CSI) for a downlink channel and determines (<NUM>) a Modulation and Coding Scheme (MCS) for data transmission based on the CSI. The downlink scheduler <NUM> calculates (<NUM>) an available Transmission Block Size (TBS) for reusable resources in one of the control resource set.

The downlink scheduler <NUM> determines (<NUM>) whether the TBS is sufficient for both the DCI and the data. If the TBS is enough, the downlink scheduler <NUM> allocates (<NUM>) PRBs for the DCI in the control resource set and then updates (<NUM>) the reusable resources in the control resource set. Then, the downlink scheduler <NUM> allocates (<NUM>) PRBs for the data following the PRBs for the DCI in the control resource set, and updates (<NUM>) the control resource set. If the TBS is insufficient, the downlink scheduler <NUM> allocates (<NUM>) PRBs for the DCI in the control resource set and updates (<NUM>) the reusable resources in the control resource set. For the data, the downlink scheduler <NUM> allocates (<NUM>) PRBs in the data resource region <NUM>. In this way, if the reusable resources in the control resource set are enough for data transmission, the downlink scheduler <NUM> will decide to transmit the data following DCI in the control resource set.

In some example embodiments, the network device <NUM> may try to transmit data in both the data resource region <NUM> and reusable resources in the control resource region <NUM> to further increase the resource utilization and efficiency. For example, the network device <NUM> may select a default data resource block for the downlink data in the control resource region <NUM> and the data resource region <NUM>. The default data resource block is overbooked compared to the required data resources. For example, the resources in the default data resource block may be more than the resources required for the downlink data. The overbooking may be implemented by a multiplier factor to a TBS for the data. The factor may be a customized parameter with a predetermined value larger than <NUM>. For example, <NUM> means that <NUM>% additional resources are overbooked. In the default data resource block, the network device <NUM> determines used resources to determine at least one skipped part of the default data resource block. The data resources for the downlink data may be determined from the default data resource block by removing the at least one skipped parts of the default data resource block.

<FIG> show an example mechanism of overbooking the data resources in accordance with some example embodiments of the present disclosure.

As shown in <FIG>, the network device <NUM> first selects default data resource blocks <NUM> and <NUM> for the data of UE#<NUM> and UE#<NUM> in both the control resource region <NUM> and the data resource region <NUM>. In this example, the default data resource blocks <NUM> and <NUM> both start from symbol#<NUM>. The default data resource block <NUM> includes a part of a control resource block <NUM> for DCI of UE#<NUM>. The default data resource block <NUM> includes a part of the control resource block <NUM> for the DCI of UE#<NUM> and a part of a control resource block <NUM> for the DCI of UE#<NUM>. Further, the network device <NUM> excludes the used resources (for example, resources allocated for DCIs, short data, and the like) from the default data resource blocks <NUM> and <NUM>.

As shown in <FIG>, for UE#<NUM>, the network device <NUM> excludes the part <NUM> of the control resource block <NUM> for the DCI of UE#<NUM> from the default data resource block <NUM> and determines the remaining data resources <NUM> of the default data resource block <NUM> for the data transmission. For UE#<NUM>, the network device <NUM> excludes the part <NUM> of the control resource block <NUM> for the DCI of UE#<NUM> and the control resource block <NUM> for the DCI of UE#<NUM> from the default data resource block <NUM> and determines the remaining data resources <NUM> of the data resources <NUM> for the data transmission. In this way, the data resource region <NUM> and the reusable resources in the control resource sets can all be used for data transmission.

The data resources may be indicated to the terminal device <NUM> so that the terminal device <NUM> may detect the downlink data. In some example embodiments, the data resources may be indicated by the DCI specific to the terminal device <NUM>. For example, in the example embodiments where the resources are configured as shown in <FIG>, the data resources <NUM> for UE#<NUM> have the same time duration with the control resources <NUM> for the DCI of UE#<NUM>. The frequency The data resources <NUM> for UE#<NUM> has the same time duration with the control resources <NUM> and <NUM> for the DCI of UE#<NUM> and UE#<NUM>. In this case, the data resources <NUM> for UE#<NUM> may be indicated by the field "Frequency domain resource assignment" in the DCI for UE#<NUM>, which is same as DCI Format1_0 and DCI Format1_1. The field "Time domain resource assignment" in the DCI for UE#<NUM> will be reused to indicate the case that the resources for the data and the DCI have the same time duration. For example, a reserved value of the field "Time domain resource assignment" may be used to indicate this special case.

For the overbook mechanism, the network device <NUM> may need to indicate the locations for the skipped parts of the default data resource block. In the DCI format for <NUM> NR, only one time-resource field "Time domain resource assignment" is contained in the DCI. This field indicates the starting position and length in time domain for all the allocated frequency resources. With the overbook mechanism, the data resources may not be a rectangle since some parts of the data resources may be skipped. In this case, more than one starting positions of the data resources may need to be indicated as shown in <FIG>. As shown in <FIG>, for the data resources <NUM>, two starting time points <NUM> and <NUM> need to be indicated, labeled as Part#<NUM> and Part#<NUM>. For the data resources <NUM>, four starting time points <NUM>, <NUM>, <NUM> and <NUM> need to be indicated, labeled as Part#<NUM> to Part#<NUM>.

These starting positions may also be indicated by the DCI specific to the terminal device <NUM>. The indication with the UE-specific DCI instead of common DCI or RRC signaling allows the terminal device <NUM> to only decode UE-specific DCI without decoding the common DCI or the RRC signal. Accordingly, the network device <NUM> may schedule resources dynamically and flexibly, for example, slot by slot since UE-specific control resource sets may be varied due to attach/detach procedure. As a result, RRC reconfigurations or common DCI broadcasting procedure may not be required, and the overhead may be significantly reduced.

In order to further reduce overhead, as another example, the network device <NUM> may indicate the skipped parts of the default data resource block, rather than a plurality of starting positions of the data resources. For example, the network device <NUM> may indicate the default data resource block as well as the corresponding skipped resource blocks to the terminal device <NUM>. An example implementation of indicating the data resources will be discussed below with reference to <FIG>.

<FIG> shows an example indication of the data resources in accordance with some example embodiments of the present disclosure.

As shown, for UE#<NUM>, the network device <NUM> may indicate the default data resource block <NUM> and the skipped resource block <NUM>. For UE#<NUM>, the network device <NUM> may indicate the default data resource block <NUM> and the skipped resource blocks <NUM> and <NUM>. The indications of the default data resource block and the skipped resource block may also be implemented by the UE-specific DCI. For example, the default resource block may be indicated by the fields "Frequency domain resource assignment" and "Time domain resource assignment" in DCI. The skipped resource block may be indicated using a new DCI format.

An example item structure of the new DCI format is illustrative as below.

As shown, in the new DCI format, the items indicating the positions of the skipped resource blocks are added.

In some example embodiments, in order to further decrease decoding complexity, the network device <NUM> may set a threshold number related to the skipped parts of the default data resource block. For example, the network device <NUM> may set a maximum number of the skipped parts to reduce the number of additional items in the DCI. As an example, at most <NUM> skipped parts are supported. Thus, the DCI size may be constant, and therefore it is easy for the terminal device <NUM> to decode the DCI.

Next, still with reference to <FIG>, at block <NUM>, the network device <NUM> transmits the control information to the terminal device <NUM> by using the localized control resources. At block <NUM>, the network device <NUM> transmits the downlink data to the terminal device <NUM> by using the data resources.

In some example embodiments, the method <NUM> described above with reference to <FIG> may be performed by an apparatus comprising means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

<FIG> is a simplified block diagram of a device <NUM> that is suitable for implementing example embodiments of the present disclosure. The device <NUM> can be implemented at or as a part of the network device <NUM> as shown in <FIG>.

As shown, the device <NUM> includes a processor <NUM>, a memory <NUM> coupled to the processor <NUM>, a communication module <NUM> coupled to the processor <NUM>, and a communication interface (not shown) coupled to the communication module <NUM>. The memory <NUM> stores at least a program <NUM>. The communication module <NUM> is for bidirectional communications, for example, via multiple antennas. The communication interface may represent any interface that is necessary for communication.

The program <NUM> is assumed to include program instructions that, when executed by the associated processor <NUM>, enable the device <NUM> to operate in accordance with the example embodiments of the present disclosure, as discussed herein with reference to <FIG>. The example embodiments herein may be implemented by computer software executable by the processor <NUM> of the device <NUM>, or by hardware, or by a combination of software and hardware. The processor <NUM> may be configured to implement various example embodiments of the present disclosure.

The memory <NUM> may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory <NUM> is shown in the device <NUM>, there may be several physically distinct memory modules in the device <NUM>. The processor <NUM> may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.

When the device <NUM> acts as the network device <NUM> or a part of the network device <NUM>, the processor <NUM> and the communication module <NUM> may cooperate to implement the method <NUM> as described above with reference to <FIG>. All operations and features as described above with reference to <FIG> are likewise applicable to the device <NUM> and have similar effects. For the purpose of simplification, the details will be omitted.

Generally, various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. While various aspects of example embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method <NUM> as described above with reference to <FIG>. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various example embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Examples of the carrier include a signal, computer readable media.

More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features that are described in the context of separate example embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple example embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above.

Various embodiments of the present disclosure have been described. While the invention is defined by the appended claims, in addition to or as an alternative to the above, the following examples are for illustrative purposes only The features described in any of the following examples may be utilized with any of the other examples described herein.

Example <NUM>. a device comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the device to: in response to downlink data to be transmitted to a terminal device, determine, at a network device, a control resource set associated with the terminal device in a control resource region; select, from the control resource set, localized control resources for control information associated with the downlink data; select data resources for the downlink data in the control resource region and a data resource region; transmit the control information to the terminal device by using the localized control resources; and transmit the downlink data to the terminal device by using the data resources.

Example <NUM>. the device of example <NUM>, wherein the device is caused to determine the control resource set by: determining the control resource set by searching a database for a record indicating the association of the control resource set and the terminal device.

Example <NUM>. the device of example <NUM>, wherein the record is stored for the control resource set in the database.

Example <NUM>. the device of example <NUM>, wherein the device is further caused to: in response to attachment of the terminal device to the network device, associate the control resource set with the terminal device; and add an indication of the association of the control resource set and the terminal device in the record.

Example <NUM>. the device of example <NUM>, wherein the device is further caused to: in response to detachment of the terminal device from the network device, remove the indication of the association of the control resource set and the terminal device from the record.

Example <NUM>. the device of example <NUM>, wherein the record further indicates reusable control resources in the control resource set, and the device is further caused to: update the record by removing the localized control resources from the reusable control resources in the control resource set.

Example <NUM>. the device of example <NUM>, wherein the device is further caused to: in response to completion of the transmission of the downlink data, update the record by adding the localized control resources back to the reusable control resources in the control resource set.

Example <NUM>. the device of example <NUM>, wherein the localized control resources comprise a plurality of continuous resource elements.

Example <NUM>. the device of example <NUM>, wherein the plurality of continuous resource elements are selected starting from at least one of starting time and starting frequency of the control resource set.

Example <NUM>. the device of example <NUM>, wherein the control resource set is allocated from starting time of the control resource region.

Example <NUM>. the device of example <NUM>, wherein the control information is common control information, and the control resource set is a common control resource set allocated in response to cell setup.

Example <NUM>. the device of example <NUM>, wherein the control information is control information specific to the terminal device, and the control resource set is a control resource set allocated to the terminal device in response to attachment of the terminal device to the network device.

Example <NUM>. the device of example <NUM>, wherein the device is caused to select the data resources by: selecting the data resources in the control resource set.

Example <NUM>. the device of example <NUM>, wherein the device is caused to select the data resources in the control resource set by: determining, based on at least one of a data type and a priority associated with the downlink data, whether the downlink data is allowed to be transmitted in the control resource set; and in response to determining that the downlink data is allowed to be transmitted in the control resource set, selecting the data resources in the control resource set.

Example <NUM>. the device of example <NUM> or <NUM>, wherein a modulation and coding scheme is applied to both the control information and the downlink data.

Example <NUM>. the device of example <NUM> or <NUM>, wherein first time duration of the control resources is the same as second time duration of the data resources, or a first frequency band of the control resources is the same as a second frequency band of the data resources.

Example <NUM>. the device of example <NUM>, wherein the device is caused to select the data resources by: selecting a default data resource block for the downlink data in both the control resource region and the data resource region, wherein resources in the default data resource block are more than the data resources; determining at least one skipped part of the default data resource block based on used resources in the default data resource block; and determining the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the device of example <NUM>, wherein the device is caused to select the data resources from the default data resource block by: determining whether the number of skipped parts is below a threshold number; and in response to determining that the number of skipped resource blocks is below the threshold number, selecting the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the device of example <NUM> or <NUM>, wherein the device is further caused to: indicate the at least one skipped part of the default data resource block to the terminal device by dedicated control information specific to the terminal device.

Example <NUM>. the device of example <NUM>, wherein the device is caused to indicate the at least one skipped part of the default data resource block by: indicating at least one of frequency domain resource assignment and time domain resource assignment of the at least one skipped part of the default data resource block.

Example <NUM>. a method comprising: in response to downlink data to be transmitted to a terminal device, determining, at a network device, a control resource set associated with the terminal device in a control resource region; selecting, from the control resource set, localized control resources for control information associated with the downlink data; selecting data resources for the downlink data in the control resource region and a data resource region; transmitting the control information to the terminal device by using the localized control resources; and transmitting the downlink data to the terminal device by using the data resources.

Example <NUM>. the method of example <NUM>, wherein determining the control resource set comprises: determining the control resource set by searching a database for a record indicating the association of the control resource set and the terminal device.

Example <NUM>. the method of example <NUM>, wherein the record is stored for the control resource set in the database.

Example <NUM>. the method of example <NUM>, further comprising: in response to attachment of the terminal device to the network device, associating the control resource set with the terminal device; and adding an indication of the association of the control resource set and the terminal device in the record.

Example <NUM>. the method of example <NUM>, further comprising: in response to detachment of the terminal device from the network device, removing the indication of the association of the control resource set and the terminal device from the record.

Example <NUM>. the method of example <NUM>, wherein the record further indicates reusable control resources in the control resource set, and the method further comprises: updating the record by removing the localized control resources from the reusable control resources in the control resource set.

Example <NUM>. the method of example <NUM>, further comprising: in response to completion of the transmission of the downlink data, updating the record by adding the localized control resources back to the reusable control resources in the control resource set.

Example <NUM>. the method of example <NUM>, wherein the localized control resources comprise a plurality of continuous resource elements.

Example <NUM>. the method of example <NUM>, wherein the plurality of continuous resource elements are selected starting from at least one of starting time and starting frequency of the control resource set.

Example <NUM>. the method of example <NUM>, wherein the control resource set is allocated from starting time of the control resource region.

Example <NUM>. the method of example <NUM>, wherein the control information is common control information, and the control resource set is a common control resource set allocated in response to cell setup.

Example <NUM>. the method of example <NUM>, wherein the control information is control information specific to the terminal device, and the control resource set is a control resource set allocated to the terminal device in response to attachment of the terminal device to the network device.

Example <NUM>. the method of example <NUM>, wherein selecting the data resources comprises: selecting the data resources in the control resource set.

Example <NUM>. the method of example <NUM>, wherein selecting the data resources in the control resource set comprises: determining, based on at least one of a data type and a priority associated with the downlink data, whether the downlink data is allowed to be transmitted in the control resource set; and in response to determining that the downlink data is allowed to be transmitted in the control resource set, selecting the data resources in the control resource set.

Example <NUM>. the method of example <NUM> or <NUM>, wherein a modulation and coding scheme is applied to both the control information and the downlink data.

Example <NUM>. the method of example <NUM> or <NUM>, wherein first time duration of the control resources is the same as second time duration of the data resources, or a first frequency band of the control resources is the same as a second frequency band of the data resources.

Example <NUM>. the method of example <NUM>, wherein selecting the data resources comprises: selecting a default data resource block for the downlink data in both the control resource region and the data resource region, wherein resources in the default data resource block are more than the data resources; determining at least one skipped part of the default data resource block based on used resources in the default data resource block; and determining the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the method of example <NUM>, wherein selecting the data resources from the default data resource block comprises: determining whether the number of skipped parts is below a threshold number; and in response to determining that the number of skipped resource blocks is below the threshold number, selecting the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the method of example <NUM> or <NUM>, further comprising: indicating the at least one skipped part of the default data resource block to the terminal device by dedicated control information specific to the terminal device.

Example <NUM>. the method of example <NUM>, wherein indicating the at least one skipped part of the default data resource block comprises: indicating at least one of frequency domain resource assignment and time domain resource assignment of the at least one skipped part of the default data resource block.

Example <NUM>. an apparatus comprising: means for in response to downlink data to be transmitted to a terminal device, determining, at a network device, a control resource set associated with the terminal device in a control resource region; means for selecting, from the control resource set, localized control resources for control information associated with the downlink data; means for selecting data resources for the downlink data in the control resource region and a data resource region; means for transmitting the control information to the terminal device by using the localized control resources; and means for transmitting the downlink data to the terminal device by using the data resources.

Example <NUM>. the apparatus of example <NUM>, wherein the means for determining the control resource set comprises: means for determining the control resource set by searching a database for a record indicating the association of the control resource set and the terminal device.

Example <NUM>. the apparatus of example <NUM>, wherein the record is stored for the control resource set in the database.

Example <NUM>. the apparatus of example <NUM>, wherein the apparatus further comprises: means for in response to attachment of the terminal device to the network device, associating the control resource set with the terminal device; and means for adding an indication of the association of the control resource set and the terminal device in the record.

Example <NUM>. the apparatus of example <NUM>, wherein the apparatus further comprises: means for in response to detachment of the terminal device from the network device, remove the indication of the association of the control resource set and the terminal device from the record.

Example <NUM>. the apparatus of example <NUM>, wherein the record further indicates reusable control resources in the control resource set, and the apparatus further comprises means for updating the record by removing the localized control resources from the reusable control resources in the control resource set.

Example <NUM>. the apparatus of example <NUM>, wherein the apparatus further comprises: means for in response to completion of the transmission of the downlink data, updating the record by adding the localized control resources back to the reusable control resources in the control resource set.

Example <NUM>. the apparatus of example <NUM>, wherein the localized control resources comprise a plurality of continuous resource elements.

Example <NUM>. the apparatus of example <NUM>, wherein the plurality of continuous resource elements are selected starting from at least one of starting time and starting frequency of the control resource set.

Example <NUM>. the apparatus of example <NUM>, wherein the control resource set is allocated from starting time of the control resource region.

Example <NUM>. the apparatus of example <NUM>, wherein the control information is common control information, and the control resource set is a common control resource set allocated in response to cell setup.

Example <NUM>. the apparatus of example <NUM>, wherein the control information is control information specific to the terminal device, and the control resource set is a control resource set allocated to the terminal device in response to attachment of the terminal device to the network device.

Example <NUM>. the apparatus of example <NUM>, wherein the means for selecting the data resources comprises: means for selecting the data resources in the control resource set.

Example <NUM>. the apparatus of example <NUM>, wherein the means for selecting the data resources in the control resource set comprises: means for determining, based on at least one of a data type and a priority associated with the downlink data, whether the downlink data is allowed to be transmitted in the control resource set; and means for in response to determining that the downlink data is allowed to be transmitted in the control resource set, selecting the data resources in the control resource set.

Example <NUM>. the apparatus of example <NUM> or <NUM>, wherein a modulation and coding scheme is applied to both the control information and the downlink data.

Example <NUM>. the apparatus of example <NUM> or <NUM>, wherein first time duration of the control resources is the same as second time duration of the data resources, or a first frequency band of the control resources is the same as a second frequency band of the data resources.

Example <NUM>. the apparatus of example <NUM>, wherein the means for selecting the data resources comprises: means for selecting a default data resource block for the downlink data in both the control resource region and the data resource region, wherein resources in the default data resource block are more than the data resources; means for determining at least one skipped part of the default data resource block based on used resources in the default data resource block; and means for determining the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the apparatus of example <NUM>, wherein the means for selecting the data resources from the default data resource block comprises: means for determining whether the number of skipped parts is below a threshold number; and means for in response to determining that the number of skipped resource blocks is below the threshold number, selecting the data resources from the default data resource block by excluding the at least one skipped parts of the default data resource block.

Example <NUM>. the apparatus of example <NUM> or <NUM>, wherein the apparatus further comprises: means for indicating the at least one skipped part of the default data resource block to the terminal device by dedicated control information specific to the terminal device.

Example <NUM>. the apparatus of example <NUM>, wherein the means for indicating the at least one skipped part of the default data resource block comprises: means for indicating at least one of frequency domain resource assignment and time domain resource assignment of the at least one skipped part of the default data resource block.

Claim 1:
A network device (<NUM>) comprising:
at least one processor (<NUM>); and
at least one memory (<NUM>) including computer program code;
the at least one memory (<NUM>) and the computer program code configured to, with the at least one processor (<NUM>), cause the device to:
in response to downlink data to be transmitted to a terminal device (<NUM>), determine (<NUM>), at the network device (<NUM>), a control resource set associated with the terminal device in a control resource region;
select (<NUM>), from the control resource set, localized control resources for control information associated with the downlink data;
select (<NUM>) data resources for the downlink data in both the control resource region and a data resource region;
transmit (<NUM>) the control information to the terminal device (<NUM>) by using the localized control resources; and
transmit (<NUM>) the downlink data to the terminal device (<NUM>) by using the data resources.