CN111034299A - Data multiplexing on control resources in new radio technologies - Google Patents

Abstract

A method for enabling a wireless communication device to access a service provided by a radio access network in a communication between first and second wireless communication devices, wherein the communication comprises at least a control region comprising a group of physical resource blocks, the method comprising: multiplexing data within at least a portion of the control region to free space in the control region such that the freed space is available for data transmission.

Description

Data multiplexing on control resources in new radio technologies

Technical Field

Embodiments of the present invention relate generally to wireless communication systems, and more particularly, to an apparatus and method for enabling a wireless communication device, such as a User Equipment (UE) or a mobile device, to Access a Radio Access Technology (RAT) or a Radio Access Network (RAN), and particularly, but not exclusively, to data multiplexing on control resources in New Radio (NR) technology.

Background

Wireless communication systems are well known, such as the third generation mobile telephony standards and technologies, which have been developed by the third generation partnership project (3GPP) and generally to the extent that they support macrocell mobile telephony communications, communication systems and networks have evolved towards broadband and mobile systems.

The third generation partnership project has developed a so-called Long Term Evolution (LTE) system, evolved universal mobile telecommunications system terrestrial radio access network (E-UTRAN), for a mobile access network of one or more macro cells supported by base stations called enodebs or enbs (evolved nodebs). Recently, LTE has further evolved towards so-called 5G or NR (new radio) systems, one or more cells of which are supported by base stations called gnbs.

The 5G standard will support a number of different services, each with very different requirements. These services include enhanced mobile broadband (eMBB) technology for high-speed data transmission, ultra-reliable low-latency communication (URLLC) technology for devices requiring low latency and high link reliability, and large-scale machine type communication (mtc) technology for communications requiring high energy efficiency, long lifetime, to support a large number of low-power devices.

In order to maintain the requirements of different levels of quality of service (QoS) required to meet a large number of services, the 5G standard must allow a flexible and scalable design to support these different requirements simultaneously.

NR supports time slot based scheduling and communication in a "taste" or manner very close to LTE. In addition, in NR, a small slot (mini-slot) has been standardized to meet the requirements of low delay and/or small size packets. When data for the URLLC service appears after the gNB scheduler makes a slot scheduling decision (and has prepared Downlink Control Information (DCI)), the data may be transmitted in small slots following its control information in order to meet low latency requirements. Since the time-frequency resources available for a small slot are relatively small, it is important to multiplex data in the control region of the small slot.

In NR systems, the use of COntrol REsource SETs (countrol resources SET, CORESET) has been agreed. This is a set of Physical Resource Blocks (PRBs) for a certain number of Orthogonal Frequency Division Multiplexing (OFDM) symbols to carry control information from the gNB to the user. Since the carrier bandwidth available for NR is wide, the portion of time and/or frequency to spread the CORESET may be important and, if not used, may reduce the system spectral efficiency. This requires multiplexing of data (e.g., Physical Downlink Shared Channel (PDSCH)) over these resources to improve spectral efficiency.

In LTE technology, there is a significant time interval between the Control (Physical Dedicated Control Channel (PDCCH) region) and the data (PDSCH). In contrast to LTE, in NR technology, control information is sent to users via different CORESETs in the control region. Due to the availability of large wideband carriers in NR, CORESET may not always occupy the entire control region. In order to obtain good spectral efficiency, NR techniques have agreed to multiplex data on the control resources. However, the user will not know the existence and precise location of the CORESET that is not configured for him. Similarly, CORESET may be composed of certain time-frequency resources to potentially accommodate control information for several users. Since these users do not necessarily have the relevant control information in the CORESET during each scheduling interval, this will result in a partially used CORESET, which also means an inefficient use of time-frequency system resources.

In the NR technique, one slot is defined as 7 or 14 OFDM symbols for the same subcarrier spacing up to 60kHz with a normal Cyclic Prefix (CP); whereas for the same subcarrier spacing above 60kHz with a normal CP, one slot is defined as 14 OFDM symbols. One slot may contain all downlinks, all uplinks, or at least one downlink part and at least one uplink part. Time slot aggregation is also supported, i.e., data transmissions may be scheduled to span one or more time slots. Also defined is a mini-slot with a length that supports a mini-slot of 1 symbol for at least 6GHz and above; for lengths from 2 to slot length-1, at least 2 symbols are supported for URLLC. For at least 6GHz and above, a mini-slot may start from any one OFDM symbol. A mini-slot contains a Demodulation Reference Signal (DMRS) at a position(s) relative to the start of the mini-slot.

There are many protocols for CORESET and search space in standard documents, which are readily available to those skilled in the art. These protocols list the requirements and functions that need further investigation. Protocols have also produced a series of proposals to address various issues and problems.

The present invention seeks to solve at least some of the outstanding problems in the art.

It is an object of the present invention to enable efficient data multiplexing on so-called control resources on both slot-based and mini-slot based scheduling use cases without the problems of the previous methods and schemes.

Disclosure of Invention

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 as an aid in determining the scope of the claimed subject matter.

According to a first aspect of the present invention, there is provided a method for enabling a wireless communication device to access a service provided by a radio access network in a communication between first and second wireless communication devices, wherein the communication comprises at least a control region comprising a group of physical resource blocks, the method comprising: multiplexing data within at least a portion of the control region to free space in the control region such that the freed space is available for data transmission.

Preferably, the group of physical resource blocks includes CORESET.

Preferably, the first communication device comprises a base station and the second device comprises a UE; and wherein the base station configures data for the UE in the control region of the transmission.

Preferably, if all frequency carriers allocated to the UE are not configured for any CORESET, the base station configures data for the UE in the control region of the transmission.

Preferably, the base station configures data for the UE in the control region, and the frequency resources allocated by the user in the control region partially or completely overlap with their own CORESET.

Preferably, the base station configures data for a UE in the control region, and the frequency resources allocated by the user in the control region may include any number of known CORESETs, including common, group common, and user-specific CORESETs to which they are allocated.

Preferably, the base station multiplexes data for a UE that extends its frequency allocation in the control section, where the control section is configured with a CORESET that is unknown to the particular user but does not currently include any control data.

Preferably, the base station may configure data for one user in the control portion, so that the frequency carrier of the user is using resources around the CORESET of other users, and the gNB sends the resource occupancy of the CORESET to the user.

Preferably, the base station configures resources for a user in the control portion, the control portion allowing irregularities around an unknown CORESET by communicating limited information about the boundaries of the unknown CORESET.

Preferably, the limited information about the boundary of the unknown CORESET includes at least one of a last PRB of the CORESET and a first available PRB of the user, and further includes information about a length of the CORESET.

Preferably, the information about the boundary of the unknown CORESET is transmitted with higher granularity than PRB to reduce signaling overhead.

Preferably, the information about the length of the CORESET includes one of an absolute length or a relative length from a start of the scheduling data of the user.

Preferably, the base station uses one of a set of predefined CORESET patterns.

Preferably, the base station may activate more than one pattern simultaneously.

Preferably, the base station may also send a bitmap that conveys the activation status of the CORESET for one active CORESET pattern.

Preferably, the activation information is sent as one of cell-specific data or group-specific data.

Preferably, if one or more symbols within one core set of frequency resources for one user are not used in the current scheduling interval, the base station may configure data for the user within the core set for its allocated PRBs.

Preferably, the base station may configure data for one user in one CORESET with one or more OFDM symbols in which CCEs of the user exist in the symbol.

Preferably, the CCEs may be time or frequency first mapping, and may exist locally or in a distributed manner in the CORESET.

Preferably, the base station can configure data for one user by extending its frequency resources for one or more OFDM symbols in one CORESET when there are unknown CCEs from at least one user.

Preferably, the base station provides location information to the user to enable data to be wrapped around the CCE of the unknown user.

Preferably, the base station provides limited location information indicating that the user knows a frequency location from which data has been multiplexed within a CORESET.

Preferably, the frequency location information represents the number of PRBs or a higher granularity for a group of PRBs to reduce signaling overhead.

Preferably, the radio access network is a new radio/5G network.

According to a second aspect of the invention there is provided a base station adapted to perform the method of a further aspect of the invention.

According to a third aspect of the present invention there is provided a UE adapted to perform the method of a further aspect of the present invention.

According to a fourth aspect of the invention, there is provided a non-transitory computer readable medium having stored thereon computer readable instructions for execution by a processor to perform the method of the further aspect of the invention.

The non-transitory computer readable medium may include at least one of the group consisting of: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memories, programmable read-only memories, erasable programmable read-only memories, electrically erasable programmable read-only memories, and flash memories.

Drawings

Further details, aspects and embodiments of the invention are described below, by way of example only, with reference to the accompanying drawings. For simplicity and clarity of illustration, elements in the figures are illustrated and not necessarily drawn to scale. The same reference numerals are included in the respective drawings for ease of understanding.

Fig. 1 shows a simplified diagram of the CORESET level sharing of control resources for data according to an embodiment of the present invention.

Fig. 2 shows a simplified diagram of enhanced CORESET-level data reuse according to an embodiment of the present invention.

Fig. 3 shows a simplified diagram of an exemplary set of CORESET patterns in accordance with an embodiment of the present invention.

Fig. 4 shows a simplified diagram of enhancing the use of control resources by restricted signaling according to an embodiment of the invention.

Fig. 5 shows a simplified diagram of control resource reuse for CCE levels of data comprising frequency-first localized CCE mappings according to an embodiment of the present invention.

Fig. 6 shows a simplified diagram of control resource reuse for CCE levels of data comprising time-first localized CCE mappings according to an embodiment of the present invention.

Fig. 7 shows a simplified diagram of CCE level reuse of control resources for data according to an embodiment of the present invention.

Fig. 8 shows a simplified diagram of enhanced CCE level RE reuse for data around an unknown CCE, according to an embodiment of the present invention.

Fig. 9 shows a simplified diagram of data multiplexing on control resources for minislots according to an embodiment of the invention.

Fig. 10 shows a simplified diagram of small slot data multiplexing within the CORESET around unknown CCEs of other users according to an embodiment of the present invention.

Detailed Description

Those skilled in the art will recognize and appreciate that the specific details of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable in a variety of alternative configurations.

The present invention relates to a method and system for data transmission using unutilized control resources that increases the spectral efficiency of the system. This may be used to increase the available resources for data transmission in e.g. the DL direction. This, in turn, may increase the throughput of the user. The use of more time-frequency resources for data may be used to reduce the coding rate for a given information block, thereby improving reliability.

The present invention surpasses the state of the art in both CORESET level reuse and CCE/DCI level reuse. For CORESET level reuse, it provides a technique to use unknown CORESET surrounding resources and efficient signaling to achieve this. Further, a pattern-based technique is provided that has a hierarchical refinement function or change with an additional bitmap indicating configured and unconfigured CORESET. Similarly, for data multiplexing inside the CORESET at the DCI/CCE level, the present invention provides techniques to implement data multiplexing around CCEs of other users that are not typically known to the UE.

One feature of the invention is reuse around unknown CORESET. To overcome the signaling burden, a signaling strategy is provided that can exploit most of the multiplexing gain with a limited number of bits by only indicating the unknown CORESET boundaries. Data multiplexing at CCE/DCI level may be in a similar manner. Another important feature relates to placing the CORESET configuration pattern on top of the unoccupied CORESET and sending a bitmap about the unoccupied CORESET to inform the UE.

In fourth generation mobile communication systems, such as LTE and LTE-Advanced, there is a clear division in the control region at the beginning of the subframe and the data region on the remaining symbols. This control region includes three physical control channels, namely a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), and a PDCCH. The PCFICH provides the size of the control region within which users can then search for their associated control information based on system configuration and their identity.

Since the carrier bandwidth can be very large in NR systems, significant waste of resources can result by dedicating the first few symbols to control to maintain a clear time division between the control region and the data region. Thus, it has been recognized that a portion of the control resources may be used for data transmission. In 3GPP, an agreement has been reached that each user is not configured to search through the control area for its associated control information, but rather may be configured with one or more CORESET for its control information.

CORESET is a combination of consecutive Resource Element Groups (REGs) of duration 1, 2 or 3 OFDM symbols. Furthermore, after reading the Master Information Block (MIB), the user may know at least one core set. As with the common CORESET, there may be a group of common PDCCH transmissions that a group of users hear. Thus, each user in the system may be configured to listen to at least one or more CORESET. Most likely these CORESET do not define a completely regular rectangle at the beginning of the slot, which means that there may be time-frequency resources available at the beginning of the slot, i.e. in the so-called control region.

According to the protocols of 3GPP on the use of control resources to enable data transmission, a variety of solutions with different granularities of different gains and different signaling requirements can be employed to implement these mechanisms. For this reason, 3GPP has agreed that the start symbol of the data transmission may be dynamically indicated, and possibly the length of the allocation.

The first level of sharing is when the gNB configures the start of data for a user within the control region, but configures this reuse only if all PRBs allocated to that user can be spread in time to the control region without overlapping any configured configuration. The next level of sharing of control resources may be achieved when the gNB configures the UE with PRBs starting from a certain OFDM symbol, where the region of PDSCH allocation overlaps with one or more CORESET known to the UE. With knowledge of resource allocation of CORESET, the UE can accurately determine time-frequency resources that may carry its data in the control region.

With respect to the figures, it should be noted that for continuous (frequency localized) CORESET in the frequency domain, these ideas can also be directly applied to discontinuous CORESET in the frequency domain, which means a single CORESET mapped onto non-adjacent or discontinuous frequencies.

Fig. 1 shows an example illustrating two levels of control resource sharing. Fig. 1a on the left shows a conventional arrangement. A slot includes a control region at the beginning followed by a data region. The control area includes one common CORESET and three other CORESETs. Three users, denoted UE 1.1, 1.2 and 1.3, are configured and scheduled by CORESET 1. CORESET2 schedules UE 2.1. No users are scheduled for CORESET3 in this time slot. In conventional scheduling schemes, in this case, the gNB schedules users only in the data region.

Fig. 1b shows a first level of reuse of control resources for data, where the gNB indicates the first data symbol of a user, which is the first symbol whose PRB does not overlap with any CORESET. This shows that UE 1.1 and UE 2.1 obtain the symbol time of the resource corresponding to their allocated PRB. In the time-frequency grid, there is still a lot of resource waste in the control area. The resources obtained by this step are already represented in a horizontal shadow fill.

Fig. 1c shows the case where the gNB configures the user with data starting with an OFDM symbol, in which case they may overlap with any known CORESET. The gNB may choose to puncture (puncturing) or rate-matching (rate-matching) around these CORESET. With respect to rate matching, the gNB may select a target code rate for the PDSCH. One side with respect to puncturing, it uses a lower code rate to compensate for puncturing around CORESET. In general, puncturing may facilitate the gNB operation as compared to rate matching, in which case puncturing requires rate matching according to data resources that can be reused for particular users in the control portion. And, gNB is configured at UE1.2, to receive PDSCH from the first symbol of this slot. Its allocated PRB overlaps its CORESET1 so it only successfully takes resource elements to transmit data after leaving the CORESET1 resources. Similarly, UE 1.3 has been allocated PRBs that overlap in frequency with CORESET1 and the region of common CORESET known to all users in the cell. The gbb has configured the PDSCH of UE 1.3 from the first symbol of this slot. Thus, UE 1.3 may not take into account the resources occupied by CORESET1 and the common CORESET, while the remaining resource elements carry their data. The resources obtained in this step for UE1.2 and UE 1.3 are already expressed in a vertical shadow fill.

It should be noted that the network does not require signaling beyond other than an indication on the starting symbol of the data (which is agreed by 3 GPP).

Fig. 2 is essentially an extension of fig. 1, showing two additional arrangements. In fig. 2a, it is assumed that the CORESET3 is a common CORESET known at least to UE 1.1 and UE 2.1 of the group, or that the gNB has at least a resource allocation known to these users via this CORESET. Under this assumption, the gbb may configure the PDSCH starting symbols for UE 1.1 and UE 2.1 as the first symbol of the slot, puncturing or rate matching around CORESET3 for UE 1.1 data, and puncturing/rate matching around CORESET2 and 3 for UE 2.1 data. The square-filled PDSCH region of the pattern shows that additional PDSCH resources become available through this enhancement.

If CORESET3 is not configured or does not carry any information during this slot right, the gNB may configure the PDSCH of these UEs 1.1 and UW2.1 from the first symbol of the slot without the need for rate matching around CORESET 3. This extension of additional PDSCH resources is shown as a cross-patterned area. The region of interest here is the region occupied by CORESET3 shown in fig. 2 a. Here, if nothing happens to be carried, the gNB may configure the user on that area.

Fig. 2 has demonstrated that the knowledge of CORESET at the UE can enable the control resources of the data to be used efficiently. Unfortunately, typically each user may only know the CORESET configured for him. Informing all UEs of all active CORESET locations (time and frequency regions) may significantly increase the signaling load. It may be necessary to inform each user separately about the CORESET that may have control information plus the CORESET of other UEs so that data multiplexing is achieved on the control resources, or common signaling (cell-level or group-level) may be required.

To reduce the signaling load required to implement data multiplexing in the control area, one possibility is to pre-define a set of CORESET patterns. The gNB can then dynamically select an appropriate pattern for use based on the network and the user. Fig. 3 shows an example set of predefined CORESET patterns. Such a CORESET pattern may be defined for different system/carrier bandwidths. The gNB may inform the users in the cell which pattern is currently configured by common or group common control signaling. This will make possible the use of time-frequency resources for data in the control area, which are not part of any CORESET.

Since the size and periodicity requirements of the CORESET configuration may vary widely, either the set of patterns may contain multiple patterns, and the gNB selects the pattern best suited for the current load and dynamic variations in a semi-static manner to handle such variations. Another possibility is to have a relatively small number of simple patterns in the group, while the gNB may activate one or more patterns simultaneously. This may provide some flexibility when the gNB needs to scale up or down the number of CORESET without any changes to the currently active CORESET and configured users.

One enhancement contemplated to the CORESET pattern may be the use of a layered pattern. One or more base patterns may exist, and the gNB may optimize or adjust these patterns. This may further reduce the amount of signalling since it is not expected that the pattern used will change drastically from one slot/subframe to the next. This may also ensure that if the gNB needs to scale up or down the CORESET resources due to changes in network/user dynamics, then there is no need to cancel the allocation first and then reallocate the currently active users.

Another strategy is that for data multiplexing, dynamic use of control resources can be implemented. For only a few active CORESET slots in the configured CORESET pattern, the gNB may send a bitmap for the configured/active CORESET. This is more applicable in the case of a single active pattern, since the more patterns, the dynamic information related to all patterns may be a problem. This information may be cell specific and sent to all users. The information may also be sent to a group of users in a group-specific manner or be user-specific. In the latter case, for example, for users that are currently requesting high throughput in the DL direction and are actively scheduled. After informing the relevant user of the bitmap of the current CORESET activity, the gNB may configure the user from the first symbol of the slot, and the user who knows the active CORESET may be able to use the resource elements in the control area (not part of the CORESET) plus the resource elements corresponding to the unconfigured or inactive CORESET. This may improve the system spectral efficiency despite the need for dynamic signaling.

Instead of using the CORESET pattern and associated signaling to implement data multiplexing in the control region, another alternative is to have the gsb configure the CORESET if it deems it appropriate. In this way, data multiplexing in the control region can be achieved by the gNB sending limited control information to the user being scheduled whose data schedule can be extended in the control region to overlap some unknown CORESET. This limited information may be sent to a group of users, rather than only to the single user in question. In one example, there may be a group of users that are currently active. Referring to fig. 4, an explanation is given thereto, and fig. 4 shows only a single scheduled user for convenience of description.

Figure 4a shows a classical way of control and data separation. If the gNB allows data resource allocation in the vicinity of the known CORESET, the result is shown in FIG. 4 b. This is achieved by indicating the start symbol as the second symbol of the slot. The UE knows that the gNB rate matches its data around CORESET1 and the common CORESET. Thus, the scheduling location of PDSCH data by both the gNB and the UE is well understood. Because CORESET2 is unknown to the UE, the gNB cannot start with the user's data from the first symbol. As shown in fig. 4c, using resources from the first symbol may require the gNB to signal the CORESET2 area to the UE. This may increase signaling overhead. Spectral efficiency approaching this can be achieved by applying the following rules: the gNB can only allow a single irregularity/notch in the rectangular block, which is not caused by the known CORESET. This situation is shown in fig. 4 d. Thus, the gNB may inform the UE about the PRB location at the end of the CORESET2 or the first PRB that UE 1.1 may use after CORESET 2. In order to be able to use the resources correctly, the UE must obtain knowledge of the duration of the unknown CORESET in addition to the frequency location of the unknown CORESET. Since only 1, 2, or 3 symbols can be configured for CORESET in time, this information can be easily conveyed with 1 or 2 bits of information. The CORESET duration may be indicated in the first symbol relative to the slot, or in the PDSCH starting symbol relative to the user being configured to use these resources. In addition to the known CORESET at one corner, fig. 4d also shows a notch or irregularity in the user's PRB. It is very straightforward to convey the notch information at one corner, since only one PRB needs to be indicated. In case the indentation occurs in the middle part of the user PRB, then the start and end positions, or one position plus the CORESET length, need to be communicated to the user. The gNB may choose to configure data on the unknown CORESET only at the corners of the allocated PRBs, thereby limiting the information that needs to be transmitted. Another way to further reduce the bits of signaling needed to indicate the boundary PRBs is to employ a higher granularity in terms of PRBs by considering a certain number of adjacent PRBs that make up a group. Thus, instead of indicating PRBs, the gNB needs to indicate the boundary of the unknown CORESET from the perspective of the group PRB, which requires fewer bits than indicating from the perspective of the PRB.

Reuse of control resources at the DCI or CCE level in CORESET for data transmission will now be discussed.

The multiplexing of data over the control resources within the CORESET will now be discussed. There may be common, group common and UE-specific CORESET. A user may be configured with a UE-specific CORESET through higher layer signaling, but may not know whether other users are configured with the same CORESET. This also implies that the specific mapping of Control Channel Elements (CCEs) of other users in the CORESET may not be known, if they happen to exist. CCE mapping within CORESET may be time/frequency first located or distributed. This location (and hopping to the next CCE) is typically a function of the UE identity.

One of the simplest settings for using control resources within the CORESET is that when the gNB is configuring certain users and allocating frequency resources for a particular user, one or more symbols in the CORESET happen to be unused for CCEs. In this case, the gNB may configure this data by indicating the allocated starting symbol for the user within the CORESET (with unused CORESET ofdm symbols), rather than being very easy to multiplex within the CORESET. An example is shown in fig. 5. The figure shows a simple case where only one CORESET spans three OFDM symbols. This is followed by 11 OFDM data symbols, but the duration is here exemplary and can be any allowed length in these regions. In fig. 5, CCE mapping is frequency-first and positioning is done for both UEs. Fig. 5a shows such a setup that there are unused OFDM symbols in CORESET1, but the data for users 1.1 and 1.2 start after CORESET. Fig. 5b shows a simple multiplexing over CORESET, where the frequency allocations of two users have been spread in time over the unused CORESET symbols. Additional resource gain is shown in the area filled by the vertical line pattern.

When the gNB indicates the starting symbol of the data in a slot, which contains even its own CCE, the position of the starting symbol must be known to the UE, and the next level of data multiplexing within the CORESET may be enforced. The gNB may apply puncturing/rate matching of data resources around the CCEs of the users in the CORESET, although it should not be confused at the UE end whether rate matching is used or puncturing is used at all. This is shown in fig. 5c, where the gNB configures UE 1.1 and UE1.2 starting from the first symbol of the slot without any additional information. The frequency allocation of each UE overlaps with the location of its CCEs known to each UE. Thus, after obtaining the scheduling command from this first symbol and knowing its CCE location, each user knows that the gbb has scheduled its data around its CCE and can therefore successfully identify the data resource elements from the CCE. Other additional resources available for data multiplexing are shown in the plus-filled pattern on the first symbol in fig. 5 c.

Fig. 6 shows the same strategy applied to the case of multiplexing data on CORESET resources when CCEs are mapped with time preference in a regionalized manner. Fig. 6a shows a conventional scheduling approach, where no data is multiplexed on the CORESET. Fig. 6b shows the case where the gNB allows data scheduling on unused CORESET symbols. Due to the time-first CCE mapping, CCEs occupy Resource Element Groups (REGs) for the duration of CORESET. Therefore, this alternative does not allow for the addition of data resource elements for any user. Fig. 6c shows the case where the gbb employs a data scheduling policy around CCEs known to the user. Thus, the gNB schedules each user's data starting from the first symbol of the slot by puncturing or rate matching around the CCEs of each user. Since each user knows the exact location of its CCE, after receiving the scheduling command from the gNB with the start symbol as the first symbol of the slot, it knows the data multiplexing around its CCE without any need for signaling. This may improve the spectral efficiency of the system. The additional resources made available by this scheme are shown in the plus-filled pattern in fig. 6 c.

Fig. 7 shows the case of distributed mapping of CCEs. The upper graph shows a frequency-first mapping, while the lower graph shows a time-first mapping. Fig. 7a shows a scenario where the CORESET contains CCEs for UEs 1.1 and 1.2, which are scheduled outside the CORESET. Fig. 7b shows a scenario that allows the gNB to perform CORESET reuse of data for a particular UE if all PRBs of that user are not used on one or more symbols of the CORESET. For the frequency first mapping case, this allows the gNB to schedule data for two users with two symbols in CORESET, shown as vertical line pattern symbols in the figure. This, in contrast, does not improve any time-first mapping case, since the CCE extends and uses all CORESET symbols. Fig. 7c shows the case where the gNB schedules users on known CCEs. This allows the UE1.2 to make additional use of control resources in terms of its frequency resources, only its own CCEs being present in the CORESET. This additional area is shown in a horizontal line pattern.

Reuse of enhanced CCE level control resources in CORESET for data transmission will now be discussed.

Now consider the case of active (aggregate) data multiplexing on CORESET resources, which may overlap with CCEs that are unknown around the user whose scheduling is being performed. This may be achieved by the gNB communicating certain information to the user.

One way to achieve such a surrounding resource sharing of unknown user CCEs may be to enforce certain CCE patterns, similar to the way proposed for CORESET in fig. 3. These patterns may be different for different system bandwidths. To enable data multiplexing for a particular user around the CCE of another user, the gNB may inform the particular user of a pattern related to the other user and may schedule data by puncturing or rate matching around the CCE pattern. Once this pattern is known, the user can take data multiplexes around other user CCEs.

Another way is to inform the user being scheduled of the location of the other user CCEs. This may require additional signaling if only CCEs of one or two other users are present in the locally present user frequency resources, but conveys complete information if the distributed mapping may burden DL signaling. Thus, the use of such multiplexing may not be optimal. The DL signaling burden of informing the user about other unknown CCEs can be tolerated by only sending limited information about the boundaries of other user CCEs.

Fig. 8 shows the case where the above-described manner is applied to resource elements inside the CORESET. Fig. 8a shows a typical setup where CORESET contains the CCEs of a local time first mapping of two users that are allocated data resources other than CORESET. Fig. 8b shows the reuse of control resources for data when scheduling UE1.2 from the first symbol of a slot without any additional information. Fig. 8c shows the case where the gNB further schedules UE 1.1 from the first symbol of the slot and performs data puncturing or rate matching of UE 1.1 around the CCEs of UE 1.2. To make this possible, the gNB informs UE 1.1 about the exact location of UE1.2 CCEs. With such active reuse, the additional resources that become available to UE 1.1 are shown in a "+" filled pattern.

From a spectral efficiency point of view, it may be the best choice to send complete information to a user about unknown CCEs of other users, which may lead to problems of control overhead when there are CCEs of multiple users mapped in a distributed manner in the CORESET. Signaling overhead can be tolerated if the gbb uses only one side of the resources around the unknown CCE for a particular user. An example is shown in fig. 8d, where the gbb schedules data of UE 1.1 from the first symbol of the slot and indicates only the first PRB after the unknown CCE. This informs the UE 1.1 that, in such an arrangement, he can use PRBs in the first symbol starting from this PRB to its last PRB. Figure 8d shows some unused resource elements that cannot be used by this limited signalling, although this strategy seems to provide a very reasonable trade-off in view of the limited signalling that is necessary to enable such data multiplexing. The following facts are an important aspect: the gNB does not need to inform the user in time about the number of symbols occupied by CCEs of other users. The CORESET may have a time-first mapping or a frequency-first mapping, so in case of a time-first mapping, the UE knows that all symbols within the CORESET will be occupied by other user CCEs in the form of resource element groups. Similarly, for the case of frequency-first mapping, it will know that the next symbol will be blank unless there are some user CCEs embedded after the first symbol, and then the gNB may need to send some information about the time boundaries of the unknown CCEs.

The discussion and figures illustrated herein are for the case of localized mapping, but are equally valid for the case of distributed CCE mapping and time and frequency first. The principle of using some part of the control resources around an unknown CCE by indicating a single boundary of the unknown CCE is also fully applicable in the case of distributed mapping of CCEs. The number of bits of signaling required to indicate the boundaries of unknown CCEs can be reduced by making the notification of the boundaries at a higher granularity than PRBs.

Reuse of control resources at the DCI or CCE level in CORESET for small slots will now be discussed. This discussion is related to a mini-slot having both a control portion and a data portion. Such small time slots may be reserved for URLLC users. The use of control resources outside and inside the CORESET around the CCE is more important for small slot based scenarios than for slot based scenarios. Due to their small size, the spectral efficiency of the small slots can be significantly improved by data multiplexing of the control resources.

Fig. 9 shows the previously described concept applied to the small slot case. Fig. 9a shows two sets of mini-slots that are scheduled controlled with different time and frequency resources in one slot. Each mini-slot control region is shown with one CORESET shown as containing CCEs for PDSCH scheduled users. Here, the PDSCH length is shown as only one symbol, but this is not a limitation, and the same applies to small slots with a data duration greater than one symbol. In fig. 9a, data is not scheduled on CORESET, although CORESET2 has been configured with fewer frequency resources than the frequency resources of the PDSCH that is configured UEy (as shown without shading). Fig. 9b shows the situation where the gNB schedules control resources for data around the CORESET. This allows more data resource elements to be provided for UE y around CORESET2, but without assistance for UE x. In fig. 9c, the gNB configures data of users from the start of a small slot and performs puncturing/rate matching around CCEs present therein. When users know their own CCEs, they can perfectly fetch their data resource elements from the CORESET. The added resources are indicated in figure 9c with a "+" sign pattern.

Fig. 9 shows the case of two sets of mini-slots, where only one user has CCEs in the CORESET. Although several URLLC users may be assigned the same CORESET, their periodicity is more frequent (e.g., every symbol or every two symbols, etc.) than slot-based CORESETs. The chance that multiple users need to communicate at the same precise instant with low delay is diminished. Thus, this scenario appears to be a typical scenario for a small slot.

Nevertheless, there may be cases where the gbb scheduler receives data from higher layers of multiple URLLC users simultaneously. The above approach is still valid for the case of multiple CORESET or CCEs of multiple users within each CORESET. The use of control resources inside the CORESET around unknown CCEs may be very relevant for small slot scenarios. This is presented in an exemplary manner in fig. 10. The left hand side of fig. 10a, 10b and 10c is for the distributed case, while the right hand side of fig. 10a, 10b and 10c is for the partial mapping case. Fig. 10a shows CORESET containing CCEs of two users, where only UE x PDSCH is shown on the same PRB. To simplify the discussion, it is assumed that UE y is being scheduled on a different time-frequency resource, or at least on a frequency resource that is completely disjoint from the frequency resource shown in the figure. Due to the unknown CCE of UE y, the gNB does not schedule data for UEx in CORESET. In fig. 10b, the gNB schedules data for UE x in the CORESET around the CCE of UE y. This may require informing UE x about the location of the CCE placement of UE y. The required signalling may be moderate for local mapping, but very cumbersome in case of distributed mapping. Fig. 10c shows the application of a restricted signaling approach, where the gNB informs UE x about the UE yCCE boundaries. This may leave some resource elements unused in CORESET, but the spectral efficiency gain of the data is very important in view of the limited signaling it requires.

Turning on or rate matching around CORESET or DCI/CCE will now be discussed.

The manner in which CORESET or DCI/CCE level is described herein for data multiplexing in the control region may result in different PRB lengths being allocated to users in a slot due to the use of resources around or at the edge of active control resource elements. This makes the processing of the gNB more complicated if it applies rate matching, since it needs to do the full rate matching. This operation may be simplified to some extent by assigning granularity to the level of the PRB group.

With such uneven lengths, punching is relatively easy. The gNB may encode user data at a slightly lower coding rate and then puncture the control resources. Although relatively simple to apply, the puncturing operation may degrade performance for large puncturing blocks even if the coding rate is reduced. One way is to apply rate matching at the CORESET level when CORESET is semi-statically configured, so the gNB can know the amount of control resources it can use as data transmission before scheduling DCI/CCE in CORESET. For DCI/CCE level multiplexing where the most modest resources will be available, puncturing may facilitate the operation of the gNB. One way is that rate matching inside the CORESET can also be applied to CCE level data multiplexing when the CORESET has CCEs for a single user. This may be useful for small slots, in which case a single active user per small slot is expected to be a typical use case.

Since NR technology allows a single CORESET to have contiguous or non-contiguous frequency resources, CORESET on non-contiguous frequency resources may also be an interesting issue. The invention is generally referred to the case of continuous frequency CORESET. However, these approaches are equally valid for other cases, such as the case of CORESET, where the frequency is not continuous. Each individual distributed CORESET can be viewed as a number of CORESETs known to the user (shared, group shared, or assigned to the user) or unknown, and then the approach is used in coordination with the user's knowledge of these CORESETs.

The present invention has been described above with reference to frequency localized PDSCH allocation. However, all the approaches related to CORESET level sharing and DCI/CCE level sharing are also applicable to distributed allocation.

An interesting situation may arise when CORESET is configured on non-contiguous frequency resources and PDSCH allocations are also distributed in frequency. This may facilitate the application of the concept proposed in the present invention for data multiplexing on control resources if the distributed CORESET and the distributed PDSCH allow similar granularity and they share all or part of the PRBs.

For simplicity of illustration, multiple DCIs (CCEs) of one UE are used for illustration, for example, one DCI (a set of CCEs) is allocated to one user, but one UE may have multiple DCIs in one or different CORESET received in the same slot. Multiple DCIs may be due to DL + UL control, DL + common, UL + common, etc. All the ways described above also apply to these scenarios.

Time slot aggregation or cross-time slot scheduling has been standardized by 3 GPP. The present invention has been illustrated using the same generalized example of time slot scheduling, but the concepts are still broadly applicable to all types of time slot aggregation or use cases of cross-time slot scheduling. For PDSCH data scheduled in a later slot than the current slot or in a slot aggregation portion in the next slot, the gNB may not know the DCI/CCE size of the upcoming slot. Thus, DCI level sharing inside CORESET may be more difficult to implement. CORESET, on the other hand, is semi-statically configured, so all concepts for CORESET level sharing can be used for future PDSCH multiplexing for time slot aggregation or cross-slot scheduling.

Many other alternatives and variations may be suitable for use and function in the various ways presented herein.

Although not shown in detail, any device or apparatus forming part of a network may comprise at least a processor, a memory unit and a communication interface, wherein the processor unit, the memory unit and the communication interface are configured to perform the method of any aspect of the invention. Further options and choices are described below.

The signal processing functions of embodiments of the present invention, and in particular the gNB and UE, may be implemented using computing systems or architectures known to those skilled in the relevant art. Computing systems such as desktop, laptop or notebook computers, handheld computing devices (PDAs, cell phones, palmtops, etc.), mainframes, servers, clients, or any other type of special or general purpose computing device as may be desired or appropriate for a given application or environment may be used. The computing system may include one or more processors, which may be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.

The computing system may also include a main memory, such as a Random Access Memory (RAM) or other dynamic memory, for storing information and instructions to be executed by the processor. Such main memory may also be used for storing temporary variables or other intermediate information to be executed by the processor during execution of instructions. The computing system may also include a Read Only Memory (ROM) or other static storage device for storing static information and instructions for the processor.

The computing system may also include an information storage system that may include, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a Compact Disk (CD) or Digital Video Drive (DVD), a read or write drive (R or RW), or other removable or fixed media drive. The storage medium may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by a media drive. The storage media may include a computer-readable storage medium having stored therein particular computer software or data.

In alternative embodiments, the information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. Such components may include, for example, removable storage units and interfaces, such as program cartridges and cartridge interfaces, removable memory (e.g., flash memory or other removable memory modules) and memory slots, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computing system.

The computing system may also include a communication interface. Such communication interfaces may be used to allow software and data to be transferred between the computing system and external devices. Examples of a communication interface may include a modem, a network interface (such as an ethernet or other NIC card), a communication port (such as, for example, a Universal Serial Bus (USB) port), a PCMCIA slot and card, and so forth. Software and data transferred via the communications interface are in the form of signals which may be electrical, electromagnetic and optical or other signals capable of being received by the communications interface medium.

In this document, the terms "computer program product," "computer-readable medium," "non-transitory computer-readable medium," and the like may be used generally to refer to tangible media, such as memory, storage devices, or storage units. These and other forms of computer-readable media may store one or more instructions for use by a processor, including a computer system, to cause the processor to perform specified operations. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of computer programs or otherwise grouped), when executed, enable the computing system to perform the functions of embodiments of the present invention. . Note that the code may directly cause the processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so

The non-transitory computer readable medium may include at least one of the group consisting of: hard disk, CD-ROM, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, electrically erasable programmable read-only memory, and flash memory.

In embodiments where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into a computing system using, for example, a removable storage drive. The control module (in this example, software instructions or executable computer program code), when executed by a processor in a computer system, causes the processor to perform the functions of the invention as described herein.

Furthermore, the inventive concept may be applied to any circuit for performing signal processing functions within a network element. It is further envisioned that, for example, a semiconductor manufacturer may utilize the inventive concept in designing a stand-alone device and/or any other subsystem element of a microcontroller such as an Application Specific Integrated Circuit (ASIC) or a Digital Signal Processor (DSP).

It will be appreciated that for clarity purposes, the above description has described embodiments of the invention with reference to a single processing logic. However, the inventive concept may equally be implemented by means of a plurality of different functional units and processors to provide the signal processing functions. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented at least partly as computer software running on one or more data processors and/or digital signal processors or as configurable modular components such as FPGA devices. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the invention is limited only by the accompanying claims. Furthermore, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term "comprising" does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by e.g. a single unit or processor. Furthermore, although individual features may be included in different claims, these may possibly advantageously be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category but rather indicates that the feature is equally applicable to other claim categories as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. Furthermore, singular references do not exclude a plurality. Thus, references to "a", "an", "first", "second", etc., do not preclude a plurality.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the invention is limited only by the accompanying claims. Moreover, although certain features have been described in connection with particular embodiments, one skilled in the art will recognize that different features of the described embodiments may be combined in accordance with the invention. In the claims, the term "comprising" does not exclude the presence of other elements.

Claims (27)

1. A method for enabling a wireless communication device to access a service provided by a radio access network in a communication between first and second wireless communication devices, wherein the communication comprises at least a control region comprising a group of physical resource blocks, the method comprising:

multiplexing data within at least a portion of the control region to free space in the control region such that the freed space is available for data transmission.

2. The method of claim 1, wherein the group of physical resource blocks includes CORESET.

3. The method of claim 1 or 2, wherein the first communication device comprises a base station, the second device comprises a UE; and wherein the base station configures data for the UE in the control region of the transmission.

4. The method of claim 3, wherein the base station configures data for the UE in a control region of the transmission if all frequency carriers allocated to the UE are not configured for any CORESET.

5. The method according to any of claims 3 to 4, wherein the base station configures the UE with data in the control region where the user allocated frequency resources partially or completely overlap with its own CORESET.

6. A method according to any of claims 3 to 5, wherein the base station configures data for one UE in the control region, and the frequency resources allocated by users in the control region may comprise any number of known CORESETs including common, group common and user-specific CORESETs to which they are allocated.

7. A method according to any one of claims 3 to 6, wherein the base station multiplexes data for a UE that extends its frequency allocation in the control portion in which is configured a CORESET that is unknown to that particular user but does not currently include any control data.

8. A method according to any of claims 3 to 7, wherein the base station can configure data for one user in the control part such that the user's frequency carrier is using resources around the CORESET of the other user, and the gNB transmits the CORESET's resource occupancy to the user.

9. Method according to any of claims 3 to 8, wherein the base station configures resources for one user in the control part, which allows irregularities around an unknown CORESET by communicating limited information about its boundaries.

10. The method of claim 9, wherein the limited information about the boundary of the unknown CORESET includes at least one of a last PRB of the CORESET and a first available PRB of the user, and further includes information about a length of the CORESET.

11. The method according to claim 9 or 10, wherein the information about the unknown CORESET's boundaries is transmitted with a higher granularity than PRBs to reduce signaling overhead.

12. The method of claim 9, wherein the information about the length of the CORESET comprises one of an absolute length or a relative length from a beginning of the user's scheduling data.

13. The method according to any of claims 3 to 12, wherein the base station uses one of a set of predefined CORESET patterns.

14. The method of claim 13, wherein the base station can activate more than one pattern simultaneously.

15. The method of any of claims 3 to 14, wherein the base station may also send a bitmap conveying the activation status of the CORESET for one active CORESET pattern.

16. The method of claim 15, wherein the activation information is sent as one of cell-specific data or group-specific data.

17. The method according to any of claims 3 to 16, wherein the base station can configure data for a user within one CORESET for its allocated PRBs if one or more symbols within said CORESET of frequency resources for said user are not used in the current scheduling interval.

18. The method according to any of claims 3 to 16, wherein the base station can configure data for one user within one CORESET with one or more OFDM symbols in which CCEs of the user are present in the symbol.

19. The method of claim 18, wherein the CCEs may be time or frequency first mapping and may exist locally or distributed in the CORESET.

20. The method according to any of claims 3 to 19, wherein the base station can configure data for one user by spreading its frequency resources for one or more OFDM symbols in one CORESET when there are unknown CCEs from at least one user.

21. The method according to any of claims 3 to 20, wherein the base station provides location information to users to enable packing of data around CCEs of unknown users.

22. A method according to any one of claims 3 to 21, wherein the base station provides restricted location information indicating that a user knows a frequency location from which data has been multiplexed within a CORESET.

23. The method of claim 22, wherein the frequency location information represents a number of PRBs or a higher granularity for a group of PRBs to reduce signaling overhead.

24. The method according to any of the preceding claims, wherein the radio access network is a new radio/5G network.

25. A user equipment comprising a processor, a memory unit, and a communication interface, wherein the processor unit, memory unit, and communication interface are configured to perform the method of any one of claims 1-24.

26. A base station comprising a processor, a memory unit, and a communication interface, wherein the processor unit, memory unit, and communication interface are configured to perform the method of any one of claims 1-24.

27. A non-transitory computer readable medium having computer readable instructions stored thereon for execution by a processor to perform the method of any one of claims 1-24.

Images