System and method for coexistence of low-latency and delay-tolerant communications
By sending group public preemption instructions on the group common physical downlink control channel of the wireless communication system, the problem of low-latency and delay tolerance communication coexistence is solved, and efficient resource utilization and data transmission efficiency are achieved.
Patent Information
- Application Number
- CN201880029713.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-03-01
- Filing Date
- 2018-04-03
- Publication Date
- 2025-02-18
- Estimated Expiration
- 2038-04-03
AI Technical Summary
Existing wireless communication systems are difficult to coexist between low-latency and delay-tolerant communications, especially in terms of resource allocation and scheduling, affecting the efficiency and reliability of data transmission.
By sending a group public preemption indication on the group public physical downlink control channel, indicating which resources are preempted, the coexistence of low-latency and delay-tolerant communication is achieved. The method includes sending a preemption indication every K symbols or time slots indicating which resources in the previous K symbols or time slots are preempted.
The coexistence of low-latency and delay-tolerant communication is achieved, the system's resource utilization rate and data transmission efficiency are improved, and different requirements for delay and reliability of different user equipment are met.
Smart Images

Figure CN110603883B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 62 / 500,904, filed on May 3, 2017, entitled “SYSTEM AND METHOD FOR COEXISTENCE OF LOW-LATENTION AND DELAY-TOLER COMMUNICATIONS,” and U.S. Patent Application No. 15 / 909,399, filed on March 1, 2018, entitled “SYSTEM AND METHOD FOR COEXISTENCE OF LOW-LATENTION AND DELAY-TOLER COMMUNICATIONS,” the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present application relates to a system and method for coexistence of low-latency and delay-tolerant communications. Background Art
[0004] In some wireless communication systems, user equipments (UE) communicate wirelessly with one or more base stations. Wireless communication from UE to base station is generally called uplink communication. Wireless communication from base station to UE is called downlink communication. Various resources are required to complete uplink or downlink link communication. For example, a base station can wirelessly send data to a UE at a specific frequency and a specific duration. The frequency and duration are examples of resources.
[0005] The base station allocates resources for downlink communication to the UE served by the base station. Such downlink communication can be achieved by sending orthogonal frequency-division multiplexing (OFDM) symbols.
[0006] Some UEs served by a base station may need to have lower latency in receiving data from the base station than other UEs served by the base station. For example, a base station may serve multiple UEs, including a first UE and a second UE. The first UE may be a mobile device carried by a person who is browsing the Internet using the first UE. The second UE may be loaded on an autonomous driving vehicle traveling on a highway. Although the base station serves two UEs, the latency for the second UE to receive data may need to be lower than that for the first UE. And the reliability of the second UE receiving data may also need to be higher than that for the first UE. The second UE may be an ultra-reliable low latency communication (URLLC) UE, and the first UE may be an enhanced mobile broadband (eMBB) UE.
[0007] UEs served by a base station and requiring low-latency downlink communication are referred to as "low-latency UEs". Other UEs served by the base station are referred to as "delay-tolerant UEs". Data transmitted by a base station to a low-latency UE is referred to as "low-latency data", and data transmitted by a base station to a delay-tolerant UE is referred to as "delay-tolerant data". A single UE may use both low-latency and delay-tolerant communications, in which case "low-latency UE" will specifically refer to the activities of the single UE for the purpose of low-latency communication, while "delay-tolerant UE" will specifically refer to the activities of the single UE for the purpose of delay-tolerant communication.
[0008] It is desirable to have a base station and framework structure that enables low-latency UEs and delay-tolerant UEs to use the same time-frequency resources. Summary of the invention
[0009] According to one aspect of the present invention, a method is provided, comprising: sending a group common pre-emption indication for a group of K symbols or time slots on a group common physical downlink control channel every K symbols or time slots, the group of K symbols or time slots being before the symbol or time slot including the group common pre-emption indication; the group common pre-emption indication indicating which resources in the group of K symbols or time slots are preempted.
[0010] Optionally, sending the group of common preemption indications includes sending using a control resource set in the group of common physical downlink control channels.
[0011] Optionally, the method also includes sending configuration of the value of K.
[0012] Optionally, for each group common preemption indication sent, the group of K symbols or time slots is the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
[0013] Optionally, the method further includes sending signaling, wherein the signaling configures the control resource set used to send the preemption indication.
[0014] Optionally, the group of common preemption indications includes N bits, each bit indicating preemption of a granularity defined in time and / or frequency.
[0015] Optionally, the method further includes sending signaling for configuring the defined granularity.
[0016] Optionally, the group of common preemption indications includes multiple fields; the method also includes sending signaling to the UE, the signaling indicating which of the multiple fields is related to the UE.
[0017] Optionally, the method further comprises sending a group common preemption indication for each of the plurality of bandwidth portions respectively.
[0018] Optionally, when the preemption indication is one of a first value set, the preemption indication indicates adjacent preempted resources; and when the preemption indication is one of a second value set, the preemption indication indicates non-adjacent preempted resources.
[0019] According to another aspect of the present invention, a method in a user equipment (UE) is provided, the method comprising: receiving a group common preemption indication for a group of K symbols or time slots on a group common physical downlink control channel every K symbols or time slots, the group of K symbols or time slots being before the symbol or time slot including the group common preemption indication; the group common preemption indication indicating which resources in the group of K symbols or time slots are preempted.
[0020] Optionally, receiving the group of common preemption indications includes receiving using a control resource set in the group of common physical downlink control channels.
[0021] Optionally, the method further includes receiving a configuration of a value of K.
[0022] Optionally, for each received group common preemption indication, the group of K symbols or time slots is the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
[0023] Optionally, the method further includes receiving signaling, which configures the control resource set used to send the preemption indication.
[0024] Optionally, the group of common preemption indications includes N bits, each bit indicating preemption of a granularity defined in time and / or frequency.
[0025] Optionally, the method further includes receiving signaling for configuring the granularity of the definition.
[0026] Optionally, the group of common preemption indications includes multiple fields; the method also includes receiving signaling, which indicates which of the multiple fields is related to the UE receiving the signaling.
[0027] Optionally, a group common preemption indication is sent for each of the multiple bandwidth parts respectively, and the method also includes the UE monitoring any group common preemption indication related to the bandwidth part used by the UE.
[0028] Optionally, when the preemption indication is one of a first value set, the preemption indication indicates adjacent preempted resources; and when the preemption indication is one of a second value set, the preemption indication indicates non-adjacent preempted resources.
[0029] According to another aspect of the present invention, a base station is provided, comprising a transmitting chain, configured to send a group common preemption indication for a group of K symbols or time slots on a group common physical downlink control channel every K symbols or time slots, the group of K symbols or time slots being before the symbol or time slot including the group common preemption indication; the group common preemption indication indicates which resources in the group of K symbols or time slots are preempted.
[0030] Optionally, the base station also includes a scheduler for scheduling resources for the first downlink service; the sending chain is also configured to send the scheduled first downlink service without violating the preemption, and to send the second downlink service by preempting the resources used for the first downlink service.
[0031] Optionally, the sending chain is used to send the group of common preemption indications using a control resource set in the group of common physical downlink control channels.
[0032] Optionally, the base station is also used to send the configuration of the K value.
[0033] Optionally, for each group common preemption indication sent, the group of K symbols or time slots is the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
[0034] Optionally, the base station is further used to send signaling, and the signaling configures the control resource set used to send the preemption indication.
[0035] Optionally, the group of common preemption indications includes N bits, each bit indicating preemption of a granularity defined in time and / or frequency.
[0036] Optionally, the base station is also used to send signaling for configuring the defined granularity.
[0037] Optionally, the group of common preemption indications includes multiple fields; the base station is further used to send signaling to the UE, where the signaling indicates which of the multiple fields is related to the UE.
[0038] Optionally, the base station is further configured to send a group common preemption indication for each of the multiple bandwidth parts respectively.
[0039] Optionally, when the preemption indication is one of a first value set, the preemption indication indicates adjacent preempted resources; and when the preemption indication is one of a second value set, the preemption indication indicates non-adjacent preempted resources.
[0040] According to another aspect of the present invention, a user equipment (UE) is provided, the user equipment comprising a receiving chain for receiving a group common preemption indication for a group of K symbols or time slots on a group common physical downlink control channel every K symbols or time slots, the group of K symbols or time slots being before the symbol or time slot including the group common preemption indication; the group common preemption indication indicates which resources in the group of K symbols or time slots are preempted.
[0041] Optionally, the receiving chain is used to receive downlink scheduling information for scheduling a first downlink service for the UE; the receiving chain includes a subcarrier demapper, which performs subcarrier demapping based on the received downlink scheduling information and also takes into account the received group of common preemption indications.
[0042] Optionally, the receiving chain is used to receive the group of common preemption indications by receiving using a control resource set in the group of common physical downlink control channels.
[0043] Optionally, the user equipment is further used to receive configuration of a K value.
[0044] Optionally, for each received group common preemption indication, the group of K symbols or time slots is the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
[0045] Optionally, the user equipment is further configured to receive signaling, which configures the control resource set used to send the preemption indication.
[0046] Optionally, the group of common preemption indications includes N bits, each bit indicating preemption of a granularity defined in time and / or frequency.
[0047] Optionally, the user equipment is further configured to receive signaling for configuring the defined granularity.
[0048] Optionally, the group of common preemption indications includes multiple fields; the user equipment is further used to receive signaling, which indicates which of the multiple fields is related to the UE receiving the signaling.
[0049] Optionally, a group common preemption indication is sent for each of the multiple bandwidth parts respectively, and the user equipment is further configured to monitor any group common preemption indication related to the bandwidth part used by the UE.
[0050] Optionally, when the preemption indication is one of a first value set, the preemption indication indicates adjacent preempted resources; and when the preemption indication is one of a second value set, the preemption indication indicates non-adjacent preempted resources.
[0051] According to another aspect of the present invention, a method in a user equipment is provided, the method comprising: receiving downlink control information including a preemption indicator, the preemption indicator having at least: a hybrid automatic retransmission request (HARQ) process identifier, and N bits, wherein the N bits indicate a time-frequency region of a previously scheduled transmission affected by the preemption.
[0052] In some embodiments, the method further includes receiving a configuration of N.
[0053] In some embodiments, the preemption indicator is received only for affected transmissions that have subsequent transmissions.
[0054] In some embodiments, the downlink control information includes a HARQ process identifier and / or resource allocation to schedule the subsequent transmission.
[0055] In some embodiments, the presence of a preemption indicator may also be used to indicate that the subsequent transmission is not a new transmission.
[0056] In some embodiments, the downlink control information also includes resource allocations and / or a HARQ process identifier for the new transmission.
[0057] According to another aspect of the present invention, a method is provided, comprising: receiving downlink control information including a redundancy version index, the downlink control information indicating preemption for a previously scheduled transmission.
[0058] In some embodiments, each redundancy version index is respectively for a redundancy version consisting of one or more code block groups (CBGs).
[0059] In some embodiments, the received redundancy version index indicates a redundancy version that best matches the affected set of code blocks.
[0060] In some embodiments, the redundant version index is one of K options, wherein M options among the K options indicate subsequent transmission at a transport block (TB) level, and KM options among the K options indicate subsequent transmission based on CBG.
[0061] According to another aspect of the present invention, a method in a user equipment is provided, the method comprising: receiving downlink control information including a redundant version index; wherein for a new transmission, the redundant version index indicates a transmission block level transmission, wherein the redundant version corresponds to a set of coded bits forming a transmission block; wherein for a retransmission, the redundant version index references a CBG level retransmission, wherein different redundant versions are mapped to different combinations of CBGs.
[0062] In some embodiments, when the redundant version index is received for preempted resources, the redundant version index serves as a preemption indication to indicate the preempted resources; when the redundant version is accepted for receiving a retransmission based on HARQ feedback, the redundant version serves as an indication of which CBGs are retransmitted after the initial transmission.
[0063] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving downlink control information for retransmission, the downlink control information comprising: a first field indicating whether the retransmission is based on preemption; when the first field indicates preemption, the second field indicates the preempted resources; when the first field does not indicate preemption, the second field is used for TB-level transmission to indicate which redundant version is sent, or to indicate which CBG is retransmitted.
[0064] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving a single downlink control information, which includes scheduling of one or more combinations of the following: one or more retransmissions due to preemption; one or more retransmissions based on HARQ feedback; one or more new transmissions.
[0065] In some embodiments, the DCI includes: an indication of a HARQ process ID for the retransmission HARQ and the new transmission HARQ processes; and / or redundant version information for the retransmission HARQ and the new transmission HARQ processes.
[0066] In some embodiments, the DCI also includes: an indication of which CBGs or symbols of the previously transmitted content are retransmitted; and / or a new data indicator (NDI) bit for CBG-based retransmission.
[0067] According to another aspect of the present invention, a method in a UE is provided, the method comprising: monitoring a group common physical downlink control channel (PDCCH) transmitted every K symbols or time slots or every X milliseconds, the group common PDCCH comprising preemption information for a group of UEs.
[0068] In some embodiments, the listening performed by the UE is based on one of the following listening periods: UE-specific, cell-specific, and group-specific.
[0069] In some embodiments, the preemption information indicates a preempted / affected region transmitted on a set of symbols occurring before symbols including the set of common PDCCHs.
[0070] In some embodiments, the set of common PDCCHs includes an indication of pre-emption information related to transmissions over the previous K symbols.
[0071] In some embodiments, the set of common PDCCHs is sent every K symbols to inform the transmitting UE that some portions of scheduled resources on a subsequent set of symbols have been preempted and allocated to another downlink (DL) transmission.
[0072] In some embodiments, the set of common PDCCHs includes M UE-specific fields.
[0073] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving downlink control information (DCI) of a transport block having at least a first part and a second part; wherein the first part of the DCI provides scheduling information for the transport block and is received at the start of a transmission interval or duration; wherein the second part of the DCI notifies the UE whether preemption has occurred during the scheduled transmission of the transport block; the method also comprises: if the second part does notify that a preemption has occurred, monitoring a group common PDCCH in one or more subsequent symbols to obtain more detailed preemption information.
[0074] In some embodiments, the group of common PDCCHs falls within a packet data shared channel of eMBB transmission, and the UE is configured with the following behaviors: the UE blindly detects the group of common PDCCHs in a preconfigured search space available for PDSCH; or the group of common PDCCHs are in a reserved position in a preconfigured control resource set area not used for PDSCH scheduling; or the group of common PDCCHs are superimposed with PDSCH transmissions.
[0075] In some embodiments, multiple input multiple output (MIMO) transmission is used in the region of overlap between the set of common PDCCH and PDSCH transmissions.
[0076] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving a transmission that may or may not be interfered with by a transmission to another UE on another MIMO layer; receiving an indication message including beam-related information for the transmission, the indication message indicating that the transmission is affected by a transmission in another MIMO layer.
[0077] In some embodiments, the preemption indication message also indicates the affected time and / or frequency resources.
[0078] In some embodiments, the preemption indication message includes beamforming information and / or interference channel information to facilitate interference cancellation of the UE.
[0079] In some embodiments, the method further includes performing beamforming based on the beamforming information, and / or performing interference cancellation based on the interfering channel information.
[0080] In some embodiments, the interference channel information includes information related to a demodulation reference signal (DM-RS) used by the base station to send to another UE on another MIMO layer.
[0081] In some embodiments, the interference channel information includes at least one of time, frequency, code, and sequence resources used to send the DM-RS, so that the UE can detect the DM-RS.
[0082] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving a transmission that may or may not be interfered with by a transmission to a different UE on another MIMO layer; performing blind detection of a DM-RS transmission on the transmission to the different UE on the other MIMO layer, and when the DM-RS is detected, performing beamforming or interference cancellation based on the detected DM-RS.
[0083] In some embodiments, performing blind detection includes: based on a set of possible DM-RS ports, the UE attempts to perform DM-RS blind decoding on each possible DM-RS port.
[0084] According to another aspect of the present invention, a method in a UE is provided, the method comprising: receiving downlink control information, the downlink control information comprising an indication of a starting position and / or duration for a symbol-based transmission, the symbol-based transmission may affect the time-frequency resources of the UE's transmission.
[0085] In some embodiments, the indication includes: a starting position field of log2K bits, used to indicate one of the K possible starting positions; and a length field of log2M bits, used to indicate the length.
[0086] In some embodiments, the method further includes receiving a granularity indication for the length field, which may be received as part of downlink control information in current layer or higher layer signaling.
[0087] According to another aspect of the present invention, a method in a UE is provided, the method comprising executing any one or a combination of two or more of the methods described herein.
[0088] According to another aspect of the present invention, a UE is provided for executing the method summarized above or described herein.
[0089] According to another aspect of the present invention, a base station is provided, which is used to send to delay tolerant and delay intolerant UEs simultaneously according to any one or a combination of more than two of the methods described herein. BRIEF DESCRIPTION OF THE DRAWINGS
[0090] Embodiments of the present disclosure will now be described with reference to the accompanying drawings, in which:
[0091] Figure 1 is a block diagram of a base station and a UE according to an embodiment of the present invention;
[0092] Figure 2 is a schematic block diagram of a base station according to some embodiments of the present disclosure;
[0093] Figure 3 is a schematic block diagram of a wireless device according to some embodiments of the present disclosure;
[0094] Figure 4 is a block diagram of a base station including a transmit chain;
[0095] Figure 5 is a block diagram of a UE generally including a transmit chain;
[0096] Figure 6 is an example of a group common signaling structure;
[0097] Figure 7 is an example of transmitting a group-common PDCCH at the beginning of a slot in each slot;
[0098] Figure 8 is an example in which a group-common PDCCH is transmitted at the beginning of every other slot;
[0099] Fig. 9 is an example of sending a preemption indication in a subsequent eMBB transmission to indicate overlap between different MIMO layers in a previous eMBB transmission;
[0100] Fig.10 is an example of a preemption indication, in which 9 symbols are indicated and the starting position is the 6th symbol of the time slot;
[0101] Fig.11 is an example of a preemption indication, in which 16 symbols are indicated and the starting position is the 4th symbol of the time slot;
[0102] Fig.12 is an example of a mini-slot structure in which control resources are reserved every other symbol; and
[0103] Fig.13 is an example of a mini-slot control region where eMBB services can use resources that overlap with unused control resources. DETAILED DESCRIPTION
[0104] In general, embodiments of the present disclosure provide a method and system for coexistence of low-latency and delay-tolerant communications. For the sake of brevity and clarity of description, reference numerals in the accompanying drawings may be reused when indicating corresponding or similar devices. Many details are provided to provide an understanding of the embodiments described herein. These examples may also be practiced without these details. In other examples, well-known methods, steps, and components are not described in detail to avoid hindering the understanding of the described embodiments. This specification should not be considered to be limited to the scope of the embodiments described herein.
[0105] In the following detailed embodiments, it is assumed that the low-latency service is URLLC and the delay-tolerant service is eMBB, but it should be understood that these embodiments are generally applicable to low-latency services and delay-tolerant services.
[0106] The examples mentioned below are applicable to any duplex system, frequency division duplex, time division duplex, unified duplex, etc.
[0107] Figure 1 1 is a block diagram of a base station 100 and four UEs 102a, 102b, 104a, and 104b served by the base station 100 according to an embodiment. UEs 102a and 102b are low-latency UEs, while UEs 104a and 104b are delay-tolerant UEs. That is, UEs 102a and 102b require lower latency downlink communications than UEs 104a and 104b. For example, UEs 102a and 102b may be URLLC user equipments, while UEs 104a and 104b may be eMBB user equipments. Although Figure 1 The base station 100 in the example only serves four UEs, but in practice the base station 100 may serve more UEs. It is also contemplated that a single UE may be served by more than one base station 100. Downlink transmissions to delay tolerant UEs are typically grant-based, but may be grant-free. Similarly, downlink transmissions to low latency UEs may also be grant-based or grant-free.
[0108] The base station 100 includes a queue 108 for storing data to be sent to the UE served by the base station 100. The queue 108 can be implemented by a memory, such as a physical register. The base station 100 also includes a scheduler 110 for scheduling the UE on available resources. The base station 100 also includes processing blocks for implementing a downlink physical layer, such as an error control encoder 114, a rate matcher 116, a modulator 118, and a resource mapper 120. The downlink physical layer of the base station 100 may include other processing blocks, but for clarity, they have been omitted.
[0109] The scheduler 110, the error control encoder 114, the rate matcher 116, the modulator 118, and the resource mapper 120 may all be implemented by a processor that executes instructions, and the execution of these instructions causes the processor to perform the operations of the scheduler 110, the error control encoder 114, the rate matcher 116, the modulator 118, and the resource mapper 120. Each of the scheduler 110, the error control encoder 114, the rate matcher 116, the modulator 118, and the resource mapper 120 may be implemented using the same or different processors. Alternatively, the scheduler 110, the control encoder 114, the rate matcher 116, the modulator 118 and / or the resource mapper 120 may also be implemented using a dedicated integrated circuit, such as an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or a programmed field programmable gate array (FPGA) to perform the functions of the scheduler 110, the error control encoder 114, the rate matcher 116, the modulator 118 and / or the resource mapper 120.
[0110] The base station 100 also includes one or more antennas 122 to wirelessly transmit signals carrying data for the UEs 102a, 102b, 104a, and 104b. Only one antenna 122 is shown. The base station 100 may also include other circuits and / or modules for performing other functions, such as for uplink communication, but these have been omitted for clarity.
[0111] The term "base station" covers any device that wirelessly communicates with a UE using uplink and downlink communications. Therefore, in some embodiments, the base station 100 may have other names, such as a transmit and receive point (TRP), a base transceiver station, a wireless base station, a network node, a transceiver node, a node B, an eNodeB (eNB), a gNB, a relay station, or a remote radio head. Moreover, in some embodiments, parts of the base station 100 may be distributed. For example, some modules / processing blocks of the base station 100 may be located away from the device that houses the antenna of the base station 100 and may be coupled to the device that houses the antenna via a communication link (not shown). Therefore, in some embodiments, the term "base station 100" may also refer to modules / processing blocks that perform processing operations on the network side, such as scheduling and downlink control signal generation, and these modules / processing blocks are not necessarily part of the device that houses the antenna. The modules / processing blocks may also be coupled to other base stations. In some embodiments, the base station 100 may actually be a plurality of base stations that operate together to serve the UE, for example, through coordinated multi-point transmission.
[0112] UE 102a, 102b, 104a, 104b are intended to illustrate any end-user equipment that may be configured as disclosed herein for uplink / downlink communications with BS 100. Examples of user equipment include wireless transmit / receive units (WTRUs), mobile stations, wireless devices, fixed or mobile subscriber units, cellular phones, personal digital assistants (PDAs), smart phones, laptops, computers, touch pads, wireless sensors, and consumer electronic devices.
[0113] As described above, UE 102a, 102b is a UE that may need low latency and have sporadic service requirements, while UE 104a, 104b does not have such strict latency requirements and may have more consistent service requirements, at least when activated. In a more specific embodiment, UE 102a, 102b applies orthogonal frequency division multiplexing (OFDM) to send URLLC services. It is contemplated that OFDM can be used in combination with orthogonal multiple access and non-orthogonal multiple access schemes, such as sparse code multiple access (SCMA), interleave-grid multiple access (IGMA), multi-user shared access (MUSA), low code rate extension, frequency domain extension, non-orthogonal coded multiple access (NCMA), pattern division multiple access (PDMA), resource spread multiple access (RSMA), low density spreading with signature vector extension (LDS-SVE), low code rate and signature based shared access (LSSA), non-orthogonal coded access (NOCA), interleave division multiple access (IDMA), repetition division multiple access (RDMA) and group orthogonal coded access (GMAC). For example, UE 104a, 104b transmits enhanced mobile broadband (eMBB) services. UE 104a, 104b may also use OFDM in conjunction with orthogonal multiple access or non-orthogonal multiple access schemes.
[0114] When the base station 100 has data to send to the UE 102a, 102b, 104a and / or 104b, the base station 100 sends the data in one or more downlink transmissions using the allocated resources. A set of time-frequency resources 126 is divided into coexistence bandwidth partitions 128 and delay-tolerant bandwidth partitions 130. The resources within the coexistence partitions 128 are used for transmission of both low-latency downlink traffic and delay-tolerant downlink traffic, while the delay-tolerant partitions are used for transmission of delay-tolerant downlink traffic.
[0115] In operation, data to be sent from the base station 100 to the UE is stored in the queue 108. For a specific downlink transmission, the scheduler 110 allocates available resources to the UEs served by the base station 100 respectively. Low-latency data sent to low-latency UEs are sent in low-latency resources 128, and delay-tolerant data sent to delay-tolerant UEs are sent in delay-tolerant resources 130 and / or low-latency resources 128. The scheduler 110 uses an algorithm to decide which resources should be allocated to which UE. An example of an algorithm that may be used by the scheduler 110 to allocate resources for low-latency services is a delay-based algorithm that takes into account potential constraints of low-latency services. When only delay-tolerant services exist, a proportionally fair (PF) scheduling algorithm can be used. When a resource partition is allocated to a UE, an appropriate number of bits corresponding to the UE are removed from the queue and sent to the downlink physical layer. The error control encoder 114 encodes these bits using an error control code to generate coded bits. An example of an error control code that can be applied by the error control encoder 114 is a Turbo code. The coded bits output from the error control encoder 114 can be rate matched in a rate matcher 116. The rate matcher 116 can match the number of bits in the transport block with the number of bits that can be sent in a given allocation, and the rate matching can involve sub-block interleaving, bit collection and / or pruning. The modulator 118 then modulates the coded bits to produce modulation symbols. The resource mapper 120 maps the modulated symbols to the resources allocated to the UE.
[0116] An example implementation of UE 104a is Figure 1104a, and also includes one or more antennas 152 for receiving downlink transmissions 124. Only one antenna 152 is shown. UE 104a includes a receiver 154 for processing the received downlink transmissions 124. For example, the receiver 154 can implement downlink physical layer processing, such as decoding and demodulation, to extract data, pilot sequences and signaling destined for UE 104a. A decoder 155 for performing decoding is shown. Both the receiver 154 and the decoder 155 can be implemented by a processor that executes instructions that cause the processor to perform the operations of the receiver 154 and the decoder 155. Each of the receiver 154 and the decoder 155 can be implemented using the same or different processors. Alternatively, the receiver 154 and / or the decoder 155 can be implemented using a dedicated integrated circuit, such as an ASIC, a GPU or an FPGA to implement the functions of the receiver 154 and / or the decoder 155. UE 104b has a similar structure to UE 104a.
[0117] Figure 2 is a schematic block diagram of a BS 12 according to some embodiments of the present disclosure. As shown, BS1 includes a control system 34 configured to perform the network-side functions described herein. In some implementations, the control system 34 takes the form of a circuit configured to perform network-side functions. In other embodiments, the control system or circuit 34 includes one or more processors 36 (e.g., CPU, ASIC, FPGA, etc.) and a memory 38, as well as a possible network interface 40. BS12 also includes one or more radio frequency units 42, each of which includes one or more transmitters 44, and one or more receivers 46 coupled to one or more antennas 48. In some other embodiments, the functions of the BS 12 described herein may be implemented in whole or in part in software or modules, such as software or modules stored in the memory 38 and executed by the processor 36.
[0118] In other embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the BS 12 according to any embodiment described herein. In other embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium, such as a memory).
[0119] Figure 3is a schematic block diagram of a wireless device according to some embodiments of the present disclosure. As shown, the wireless device includes a circuit 18 configured to perform the wireless device functions described herein. In some embodiments, the circuit 18 includes one or more processors 20 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.) and a memory 22. The wireless device 14 also includes one or more transceivers 24, each transceiver 24 including one or more transmitters 26 and one or more receivers 28 coupled to one or more antennas 30. In some other embodiments, the functions of the wireless device 14 described herein may be implemented in whole or in part by software or modules, such as software or modules stored in the memory 22 and executed by the processor 20.
[0120] In other embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the wireless device 14 according to any embodiment described herein. In other embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium, such as a memory).
[0121] Figure 4 is another example of a base station, wherein a transmit chain is generally indicated at 900 and a receive chain of the base station is generally indicated at 903.
[0122] The transmission chain 900 includes a constellation mapper 910, a subcarrier mapping and grouping block 911, an inverse fast Fourier transform (IFFT) 912, a pilot symbol and cyclic prefix insertion 914, and a frequency positioning operator 916 (e.g., filtering, subband filtering, windowing, subband windowing). A downlink scheduler 950 that performs downlink scheduling is also shown.
[0123] In operation, the constellation mapper 910 receives UE data (more generally, UE content including data and / or signaling) for downlink transmission to K1 UEs, where K1>=1. The constellation mapper 910 maps the UE data for each of the K1 UEs to a corresponding constellation symbol stream and outputs it at 920. The number of UE bits per symbol depends on the specific constellation adopted by the constellation mapper 910. In the example of quadrature amplitude modulation (QAM), 2 bits from each UE are mapped to a corresponding QAM symbol.
[0124] For each OFDM symbol period, the subcarrier mapping and grouping block 911 groups and maps the constellation symbols generated by the constellation mapper 910 to at most P inputs of the IFFT 912 at 922. The grouping and mapping are performed in accordance with the resource block definition and allocation defined for the content of the K1 UEs processed in the transmit chain 900 based on the downlink scheduling information received from the downlink scheduler 950. As described above, downlink transmissions are usually scheduled for all UEs. P is the size of the IFFT 912. Not all P inputs must be used for each OFDM symbol period. The IFFT 912 receives at most P symbols and outputs P time domain samples at 924. Then, in some embodiments, time domain pilot symbols are inserted in box 914 and a cyclic prefix is added. The frequency location operator 916 can, for example, apply a filter that limits the spectrum at the output of the transmit chain 900.
[0125] The receiving chain 903 includes a frequency location operator 930, a cyclic prefix removal and pilot symbol processing 932, a fast Fourier transform (FFT) 934, a subcarrier demapping 936, and an equalizer 938. Each element in the receiving chain performs an inverse operation corresponding to the operation in the transmitting chain. The receiving chain 903 receives an uplink signal generated according to the scheduling information and / or resource allocation information generated by the scheduler and / or resource allocator 960. The subcarrier demapping device 936 also uses the scheduler information and / or resource allocation information from the scheduler and / or resource allocator 960.
[0126] When multiple basic parameter sets (numerologies) are supported, according to the embodiments described in detail below, there may be corresponding multiple instances of the transmission chain 900 and the reception chain 903 in the base station.
[0127] Figure 5 5 is an example of a UE having a transmit chain generally indicated at 500 and a receive chain generally indicated at 503. The transmitter and receiver of the UE may be similar to the transmitter and receiver of the base station, but there is no scheduler in the UE. Instead, the UE will receive scheduling information and / or resource allocation information and will receive downlink transmissions according to the received scheduling information.
[0128] For efficient resource sharing, the same or overlapping time-frequency resources can be used to schedule the transmission of delay-tolerant communications and delay-sensitive communications.
[0129] In order to allow lower delay for delay-sensitive services than for delay-tolerant services, delay-tolerant services have a longer scheduling interval than delay-sensitive services.
[0130] The scheduling of delay-sensitive services can be achieved by preempting resources originally scheduled for delay-tolerant services. When preemption occurs, a preemption indication can be dynamically sent to inform the UE receiving the delay-tolerant service that part of its scheduled services have been preempted or postponed. Figure 1 , Figure 2 and Figure 4 The base station is configured to generate and send a preemption indication as described herein. The base station schedules services for the UE and may choose to preempt these scheduled services to send delay-sensitive services. When preemption occurs, the base station sends a preemption indication. Figure 1 , Figure 3 and Figure 5 The UE is configured to receive and process a preemption indication as described herein. The UE receives scheduled traffic. The UE also receives a preemption indication, and when the preemption indication indicates that the traffic scheduled by the UE has been preempted, the UE adjusts its reception of the received scheduled traffic to take into account the preemption. Detailed examples of base station and UE functionality are provided below.
[0131] The preemption indication may be sent when delay-sensitive traffic arrives, near the end of a scheduling interval or near the beginning of the next interval within a scheduling interval for delay-tolerant traffic, or at the beginning of another subsequent interval, for example when a retransmission is scheduled after HARQ feedback.
[0132] The preemption indication may be explicit or implicit and may be UE-specific or group-common. For example, the group-common indication may be broadcast or multicast. The eMBB UE may be configured to listen for the preemption indication. The eMBB UE may be configured via RRC signaling, or the group-common PDCCH may inform a group of UEs whether they need to listen for the preemption indication.
[0133] The preemption indication may indicate preemption at any granularity of time and / or frequency.
[0134] In addition, delay-sensitive communication services can use mini-slots (i.e., the number of symbols is smaller than the time slot) for transmission scheduling.
[0135] For a given UE, the transmission resources, such as the time-frequency resources scheduled for transmission of a TB, can be preempted in their entirety for delay-sensitive services. In this case, the specific time-frequency resources are said to be preempted. Alternatively, a portion of the time-frequency resources can be preempted for time-sensitive services, such as a portion of a specific OFDM symbol. In this case, the specific time-frequency resources or the specific symbol are said to be affected by preemption. In either case, the propagation of the TB is affected by preemption.
[0136] Reference is made to preemption in the following discussion, but it should be understood that in alternative embodiments, the provided methods may be applied to those affected by preemption, or to both preemption and those affected by preemption.
[0137] For the purpose of this description, a subsequent transmission may refer to any transmission after an initial transmission, and a subsequent transmission may be scheduled before or after HARQ feedback. Sometimes, a subsequent transmission is also referred to as a retransmission. Alternatively, a subsequent transmission that is scheduled only after HARQ feedback is referred to as a retransmission. The embodiments described below are not limited to any specific definition of subsequent transmission or retransmission, and are generally applicable to any transmission after an initial transmission of a packet / TB or HARQ process.
[0138] UE-specific downlink control information (DCI) format design
[0139] The first embodiment provides a format design of downlink control information for indicating preemption.
[0140] According to this embodiment, a preemption indication is sent for the affected resources of a transmission only if a subsequent transmission is scheduled after the affected transmission. If no subsequent transmission is scheduled, no preemption indication is sent.
[0141] A UE-specific downlink control information (DCI) format is provided, which includes a field for indicating time-frequency information of the location of an affected / preempted region of a previous transmission.
[0142] The provided DCI format indicates the resources preempted in the previous transmission with the same HARQ process ID. A HARQ process includes the initial transmission and any retransmissions or subsequent transmissions.
[0143] The DCI format includes a preemption indicator, which includes at least the following fields:
[0144] HARQ process ID;
[0145] An N-bit field indicating the time-frequency region of the previously transmitted data that is preempted. The value of N is configurable.
[0146] In some embodiments, the preemption indicator is sent only if there is a subsequent transmission after the affected transmission. The DCI also schedules the subsequent transmission, and in some embodiments, the presence of the preemption indicator is also used to indicate that the subsequent transmission is not a new transmission. Therefore, optionally, the new data indicator (NDI) field can be omitted from the DCI format.
[0147] The fields in the DCI format may also be expanded to schedule subsequent transmissions together with the new transmission. In this case, the DCI format allocates resources for the subsequent and new transmissions. Therefore, according to an embodiment of the present invention, the DCI format explicitly or implicitly indicates one or more of the following:
[0148] The time and / or frequency resources of the preempted / affected region of the previous transmission; for example, the symbol index of the affected transmission. As described above, an N-bit field may be used to provide preemption information.
[0149] Time-frequency resource allocation and / or HARQ ID for partial / subsequent / retransmission of the preempted / affected transport block (TB); for example, resource allocation over a set of resource blocks (RBs) and symbols / slots.
[0150] Time-frequency resource allocation and / or HARQ ID for new transmission; for example, resource allocation over a set of RBs and symbols / slots.
[0151] A transmission to a given UE (whether an initial transmission or a retransmission) consists of one or more transport blocks. Transport blocks are sent using resource blocks (RBs), each of which is a defined time-frequency resource. Optionally, resource blocks are organized into resource block groups (RBGs). In addition, in some embodiments, a TB is divided into code blocks (CBs). Optionally, each code block is organized into code block groups (CBGs).
[0152] Example 1:
[0153] In a first embodiment, there is a dedicated preemption indication field. The field may be, for example, an N-bit field (N is configurable) indicating preemption according to a defined indication granularity. For example, the indication granularity may be one of the following:
[0154] Code Block (CB);
[0155] Code Block Group (CBG);
[0156] symbol;
[0157] Symbol and resource block group / bandwidth parts;
[0158] For example, in the case where the granularity is a code block group, the N bits indicate which of the N code block groups is preempted. Note that a CBG can also be a CB, depending on the size of the TB.
[0159] Any of the above granularities may be used to convey preemption information about the UE's affected transmissions. This information may be provided via a UE-specific DCI or a UE-specific field or part of a group common signal / channel. Examples of group common channels and / or structures will be provided later.
[0160] Example 2:
[0161] In a second example, the preemption indication is not a dedicated field, but is based on one or more fields with other purposes, such as modulation and coding scheme (MCS), redundancy version (RV), etc. For example, the initial transmission can use a first MCS, which is one of 28 MCS levels represented by a 5-bit MCS field. Please note that 28 MCSs are mentioned here only as an example. For retransmissions, a reduced set of MCS levels is also possible and can be represented using less than the above five bits. In this case, the unused bits can be used for some or all preemption indications.
[0162] In another example, the RV field is used to indicate a preemption with respect to a previously scheduled transmission. The RV of a TB includes a portion of the coded bits. When data is encoded, the coded bits may be divided into different sets that may overlap with each other. Each group is a different RV. For example, some RVs may have more parity bits than other RVs. Each RV is identified by an RV index (e.g., RV 0, RV 1, RV 2, ..., etc.). One of the RV indexes is then indicated in the RV field. If the configured RV includes a preemption region, the RV can be indicated without other explicit indications.
[0163] However, if the number of preemptions is small and / or the configured RV does not match the pattern or number of preemptions, sending the RV of the TB based on the preempted area may be inefficient. In this case, the number of bits in the RV field can be increased, and more RV definitions or configurations can be supported to better match the preempted area. In some embodiments, the configuration of the RV is based on a code block group. In one example, the RV can consist of one or more code block groups. If CBG-based preemption indication is supported, the RV that best matches the area of the affected CBG can be sent.
[0164] In one example, even if the UE decodes the affected CBG in the previous transmission, if the affected CBG is sent in the scheduled subsequent transmission, the UE can update the decoding status of the affected CBG based on the decoding of the subsequent transmission and send HARQ feedback with the updated CBG decoding status.
[0165] In one example, the RV field may indicate one of K options, where K is an integer greater than or equal to 1. M of the K options may be used for TB-level retransmission or subsequent transmission, and KM options may be used for CBG-based retransmission or subsequent transmission. If some RVs are constructed / configured as a function of CBG, high-level signaling (e.g., RRC) may inform the UE of the mapping between CBG and RV, i.e., which CBG(s) a certain indicated RV is associated with. This may achieve a unified RV field structure that may be used for both CBG-level retransmission and TB-level retransmission. In another example, all K options may be used to indicate CBG-based RV configuration.
[0166] In one example, there are four bits in the RV field. The combination of the four bits can refer to different RV sets for new transmissions and retransmissions. For example, if it is a new transmission, the four bits can refer to a certain RV set. If it is a retransmission, the four bits can refer to a different RV set. These configurations are notified to the UE in advance, possibly via RRC signaling.
[0167] In another example, the DCI format has a 4-bit RV field. The 4-bit RV field of the new transmission can indicate a TB-level transmission, where the RV corresponds to a set of coded bits that form a TB, as in LTE. For retransmissions, the 4-bit RV field can refer to CBG-level retransmissions, where different RVs are mapped to different CBG combinations. For example, RV2={CBG2, CBG3}. If the UE supports CBG-level transmission and / or CBG-level HARQ feedback, it can be configured to read the RV field in this way. The number of bits in the RV field can be the maximum number of CBGs supported or less. Based on the resource allocation field and MCS, the UE can determine the size of the transmission; however, there may be some ambiguity as to which CBGs are retransmitted after the initial transmission. Indications through the RV field can help resolve this ambiguity.
[0168] In another example, an explicit N-bit indication field informs which CBGs are preempted. The RV field can correspond to each CBG or the entire transmission.
[0169] In another example, one or more bits in the RV field and one or more bits in the MCS field can together provide preemption indication information at a configuration granularity, such as a CBG or symbol. Alternatively, these bits can also indicate which CBGs are retransmitted. As described above, a high dynamic range of the MCS may not be required, and some bits can be used for preemption indication or CBG indication purposes.
[0170] Example 3:
[0171] In a third example, the preemption indication is sent in a combination of a dedicated field and one or more fields with other purposes. For example, an explicit N-bit field and an RV field can provide information about the preempted / affected time and / or frequency resources together. The affected / preempted portion can be scheduled to a subsequent transmission.
[0172] In a specific example, there is a dedicated 1-bit field to indicate whether the retransmission is based on preemption. Then, in the case of preemption, one or more other new or existing fields will be used to indicate the preemption information. For example, if a retransmission is to occur after a preempted transmission, the field providing the preemption information can be based on the granularity of symbols or symbols and RBGs or other granularities mentioned above. If the retransmission follows HARQ feedback, the field can provide information about which CBGs or which RVs are sent. In a specific example, if the retransmission is based on preemption or is scheduled before HARQ feedback, the RV field can indicate a set of symbols that are preempted, while for other cases, the RV field can be used in a conventional manner for TB-level transmissions or CBG-based transmissions, or to indicate which CBGs are being transmitted. This may be useful if subsequent transmissions can be based on a granularity different from CBG.
[0173] Example 4
[0174] In a further example, only 1 bit indicates whether preemption occurred.
[0175] Unified UE-specific DCI format
[0176] In some embodiments, the above-mentioned UE-specific preemption indication is used both to indicate preemption and to indicate or promote retransmission based on received HARQ feedback. In a specific example, if CBG is selected as the granularity of the indication, this can be used as a unified indication. This can be used to indicate which CBGs are being retransmitted. What is called "unified" means that at different times, the same DCI format is used to indicate the set of CBGs that have been preempted (and therefore will be retransmitted), and the set of CBGs that are retransmitted, such as the set of CBGs that are retransmitted based on previously received HARQ feedback. HARQ feedback can be multi-bit feedback, where each bit corresponds to the decoding status of a CBG. Therefore, the DCI can be used before a preemption-based ACK / NACK, or when there is no preemption-based ACK / NACK, or after receiving an ACK / NACK. It should be noted that in the event of an error in the received ACK / NACK, the UE can use this indication in the DCI to identify which CBGs are retransmitted, and the retransmitted CBGs can be different from the failed CBGs.
[0177] The indication of which CBGs to send in retransmissions is available in both uplink and downlink grants.
[0178] In another example, separate DCI formats are provided for new transmissions and retransmissions. The DCI for retransmissions may include fields for CBG and / or preemption indication, which may not be required in the DCI for scheduling new transmissions. Similarly, the RV field in the DCI for retransmissions may be used differently from the RV field in the DCI for new transmissions. This is because the RV field configuration may be different for new transmissions and retransmissions; the RV configuration for retransmissions may be based on the CBG configuration. The RV field may have the same or different number of bits in the two DCIs for new transmissions and retransmissions. In this case, the NDI bit may not be required because separate DCIs are used for new transmissions and retransmissions.
[0179] DCI design when two processes are scheduled by the same grant
[0180] As described above, in some embodiments, multiple HARQ processes of a UE are scheduled with a single DCI. For example, this can be CBG-based, or symbol-based or RB-based. These can include scheduling one or a combination of the following:
[0181] One or more retransmissions due to preemption;
[0182] One or more retransmissions based on HARQ feedback;
[0183] One or more new transfers.
[0184] This approach may be more efficient than separate scheduling. For example, a single grant may schedule retransmissions / subsequent transmissions for HARQ process i and new TBs for HARQ process j, where j≠i.
[0185] For this embodiment, the DCI format supports at least the following contents:
[0186] Indication of HARQ process IDs for retransmission HARQ processes and new transmission HARQ processes;
[0187] Redundancy version information used for retransmission HARQ process and new transmission HARQ process;
[0188] For example, an indication of which CBGs or previously transmitted symbols are retransmitted (optional);
[0189] NDI bit for CBG based retransmission (optional).
[0190] The DCI may include an MCS and resource allocation field that is common between multiple schedulings of the HARQ process. It should be noted that multiple HARQ processes may be retransmitted along with multiple new HARQ processes, for example, via MIMO transmission. In this case, configuration details related to MIMO transmission also need to be communicated for each HARQ process.
[0191] For example, the DCI may indicate the number of allocated RBs. The UE will know which CBGs under a specific HARQ ID have failed, and based on this, apply mapping rules to determine where the CBGs for retransmission are located. For example, the previously transmitted CBG may be sent in the first part of the time slot. In this case, some padding may be applied so that the CBGs for retransmission fill an integer number of REs so that the bits of the two HARQ process IDs are not included in the REs. Based on the RV field, with or without the optional indication field and mapping rules, the UE knows where the CBG resource allocation ends within the time slot and can determine the allocated REs for retransmission. The resources for the new TB start immediately after the resources for retransmission.
[0192] In another example, if an explicit indication is provided of which CBGs or symbols of a previously transmitted transmission are to be retransmitted, the RV field for retransmission may be omitted.
[0193] In another example, separate and / or explicit MCS and / or RV and / or time-frequency allocation and / or NDI are provided in the DCI for retransmission and new transmission.
[0194] Multiple group common signaling for preemption indication
[0195] In another embodiment, a group common physical downlink control channel (PDCCH) is sent every K symbols / time slots or every X milliseconds to notify the preemption indication information. K is a positive integer. The group common PDCCH is used for multiple UEs. The listening period can be cell-specific or group-specific or UE-specific and configurable. In some embodiments, the position is not tied to any specific symbol or symbol group in the time slot, can be any symbol, and is configurable. The group common PDCCH may have UE-specific fields, or common information read by all UEs listening to the group common PDCCH. X and / or K can be configured by high-level signaling. Although the group common PDCCH is discussed here, it should be understood that the examples of how the content of the group common PDCCH or the resources in the group common signal are configured / partitioned can be applied to any group common signal / channel regardless of its structure. Examples of group common signaling are disclosed in co-pending U.S. patent application Ser. No. 62 / 475,762, filed on Mar. 23, 2017, and entitled “SYSTEM AND METHOD FOR SERVICE MULTIPLEXING,” which is incorporated herein by reference.
[0196] One group common PDCCH may be sent for the entire cell to notify the preemption indication. In one example, if the group common PDCCH is sent every K symbols, the indication related to the preempted / affected transmission area may be included on a group of symbols that appear before the symbol including the group common PDCCH. In one example, the group common PDCCH may include an indication of the preemption information related to the transmission on the last K symbols.
[0197] In another example, if a group-common PDCCH is sent every K symbols, a UE with ongoing transmission may be notified that a portion of the scheduling resources in a subsequent symbol group (which may include symbols including the group-common PDCCH) has been preempted and allocated to another DL transmission.
[0198] Depending on the length or duration of a transmission, the UE may monitor several group-common PDCCHs, where each group-common PDCCH provides pre-emption information for a portion of the duration of the scheduled transmission.
[0199] In some embodiments, there are multiple group-common PDCCHs in a cell, and some UEs are configured to observe one or more group-common PDCCHs to collect preemption indication information for the UE. The UE can monitor multiple group PDCCHs for collecting preemption information in the same or different symbols. In some embodiments, the eMBB UE is configured in this way to monitor the relevant signaling.
[0200] In a specific example, the group common signaling has Figure 6The structure depicted in FIG. 1 includes N bits 1000 and a CRC check indicating a radio network temporary identifier (RNTI). The RNTI indicates that the purpose of the PDCCH is to be used as a preemption indicator. The N bits include time domain / frequency domain preemption of a defined or configured granularity for multiple UEs. The granularity can be time domain only, or time domain and frequency domain. The time domain information can be based on symbols. The frequency domain information can be RB groups or bandwidth parts or subbands. It should be noted that these granularities can be used for any group common signal or channel.
[0201] In some embodiments, the N bits including preemption information are divided into M fields, one or more of which may be UE-specific. In this case, a given UE only needs to process the fields for itself. If one or more fields are UE-specific, different granularity options may be used to indicate, for example, code block groups, symbols, symbol and RB groups, symbol and bandwidth parts, etc. Alternatively, as in the previous embodiments, one or more fields are not UE-specific but resource-specific. A UE that is aware of its scheduled resources can use these fields to identify whether there is a preemption in a portion of its scheduled resources.
[0202] In some embodiments, previously sent signaling (e.g., RRC signaling) is used to inform each UE which parts of the N-bit field include indications for the UE, or which fields in the group PDCCH belong to the UE. Alternatively, the information can be dynamically represented. The UE can receive in its DCI which (which) fields in one or more subsequent group common PDCCHs are indications for the UE. In another embodiment, a predetermined mathematical relationship is used to determine where / which field in the group common PDCCH the indication information is sent to each UE. In a specific example, the group common signal includes M fields.
[0203] For a given UE k The information is expressed by the following formula:
[0204] mod(i k ,M)+shift k
[0205] where i k is assigned to UE k The position of the first resource block or reference resource block (RB) in the RB, and shift kis the UE-specific shift applied. The shift is applied so that each UE has a different position corresponding to the modulo M operation. The shift can be indicated dynamically in the DCI. If there are M or fewer UEs scheduled, each UE has a unique position within the DCI by using a shift. Since the group-common PDCCH in this embodiment has M fields, the BS can configure up to M UEs to listen to the group-common PDCCH. The shift applied is shift k It can be 0 to M-1, and log2M bits can be used as the field.
[0206] In one example, the transmitted DCI may have multiple parts or stages. In one example, the DCI may have two parts. The first part of the DCI provides scheduling information for the transmission block and appears at the beginning of the transmission interval or duration. The second part of the DCI may appear near the end of the interval, notifying the UE of any preemption that occurs during the scheduled transmission. If a preemption notification is received, the UE can monitor the group-common PDCCH in one or more subsequent symbols, otherwise no monitoring is required. If no dedicated field is configured for the UE in the group-common PDCCH that provides information about the preempted time and / or frequency region, the second part of the DCI may also include the aforementioned shift information. If the group-common PDCCH has M fields, the BS can notify up to M UEs in the event of a preemption.
[0207] In another example, the preemption indication of the affected time and / or frequency region may be provided in a subsequently transmitted DCI of the UE.The first and second parts of the DCI may also include other information or fields necessary for proper uplink and / or downlink transmission.
[0208] In some embodiments, multiple such group common PDCCHs may be sent in each time slot or after each cycle with a given duration. In some embodiments, the same content is sent on each of the multiple PDCCHs sent in each time slot. Alternatively, each PDCCH may include different content, which is more efficient for UEs with limited UE bandwidth (BW).
[0209] In some embodiments, the cell bandwidth is divided into bandwidth partitions, and a corresponding group common PDCCH is sent for each of the multiple bandwidth partitions. The UE's transmission may occupy frequency resources of one or more portions of the multiple bandwidth partitions. A given UE only needs to monitor the PDCCH for bandwidth partitions that overlap with the given UE's transmission. In this case, different content may be sent on each common PDDCH including L bits of time-frequency information according to the granularity defined or configured in the time domain and / or frequency domain.
[0210] Figure 7 An example is shown where each slot transmits a group-common PDCCH at the beginning of the slot. Slots 1100, 1102, 1104, 1106, 1108 are shown including group-common PDCCHs 1120, 1122, 1124, 1126, 1128. eMBB UE 1 (UE with resource allocation 1140) will need to monitor the group-common PDCCHs 1122, 1124. eMBB UE 2 (UE with resource allocation 1142) will need to listen to the group-common PDCCHs 1122, 1124, 1126, 1128. eMBB UE 3 (UE with resource allocation 1146) will need to listen to the group-common PDCCH 1126.
[0211] Figure 8 An example is shown where a group common PDCCH is sent at the beginning of the slot every two slots. Slots 1100, 1102, 1104, 1106, 1108 are shown. The first, third and fifth slots include group common PDCCHs 1220, 1222, 1224. eMBB UE 1 (UE with resource allocation 1140) will need to listen to the group common PDCCH 1222. eMBB UE 2 (UE with resource allocation 1142) will need to listen to the group common PDCCHs 1222, 1224. eMBB UE 3 (UE with resource allocation 1146) will need to listen to the group common PDCCH 1224.
[0212] Location for sending group-common PDCCH
[0213] In some embodiments, any symbol may have a configured PDCCH region. In some embodiments, one or more group-common PDCCH messages are sent every K symbols. The location of the group-common PDCCH message may be inside or outside a PDCCH region defined separately in the time slot, for example, in a symbol of the time slot that includes a packet data shared channel (PDSCH).
[0214] Multiple group common PDCCH message sets may be sent at different periods. For example, a first set may be sent every K1 symbols, while a second set may be sent every K2 symbols. One group of UEs may monitor once every K1 symbols, while another group of UEs may monitor once every K2 symbols.
[0215] More generally, some control resource sets may be configured every K symbols to include a group common PDCCH for sending a preemption indication. The control resource set for the group common DCCH may be located within the PDCCH region of the symbol. The symbol may include a control resource set for slot-based transmission. The symbol may include a control resource set for mini-slot-based or symbol-based transmission. The symbol may include both of the above.
[0216] In some embodiments, the group-common PDCCH falls within the PDSCH of an eMBB transmission and the UE is configured with the following behavior:
[0217] The UE blindly detects the indication in the pre-configured search space available for PDSCH transmission; or
[0218] Avoiding reserved addresses and pre-configured control resource set areas in PDSCH scheduling; or
[0219] The group common PDCCH and PDSCH transmission overlap. MIMO transmission can be used in the overlapping area, or
[0220] Use power domain non-orthogonal multiple access (NoMA) or code domain NoMA.
[0221] Other possible structures for the group common channel
[0222] In one example, a group common channel including preemption information may be sent to a group of UEs, as in a conventional PDCCH message, without a CRC attached. Instead, the group common channel may be based on a sequence. Some examples include a channel structure of a PUCCH or a PHICH or a PCFICH. Similar to a group common PDCCH channel, a group common channel having a structure different from that of a PDCCH may have common information sent to a group of UEs, or a group common signal may have UE-specific fields or bits. If it is sequence-based, a codeword including preemption information may be generated. The codeword may include common information for a group of UEs, or the codeword may be divided into a set of multiple bits, each of which includes preemption information for a UE. As previously described, one or more group common signals / channels may be configured to appear in any symbol and may be sent in a configured search space, which may or may not overlap with data transmission.
[0223] It is noted that the group common signal / channel may span one symbol or a group of consecutive (ie, contiguous) or non-consecutive symbols.
[0224] Multi-user Multiple input multiple output (MU-MIMO) transmission
[0225] Existing DL multiplexing methods are based on preemption methods or power domain superposition. In another embodiment, preemption is no longer used, but MU-MIMO transmission is used so that multiple MIMO layers can be used to send delay-tolerant and delay-intolerant services. The network can jointly send delay-tolerant and delay-sensitive services on different MIMO layers on shared time-frequency resources. As long as there are delay-intolerant services on one or more layers, the performance of delay-tolerant services may be affected. For example, the eNB can send URLLC services on different MIMO layers in a time-frequency region that overlaps with the eMBB transmission. URLLC UEs may not be affected because the BS knows that there is an ongoing transmission scheduled in the overlapping time-frequency region, and will configure its beamforming matrix accordingly based on known interference scenarios. However, eMBB UEs may be affected because the beamforming matrix configured for the duration of the eMBB transmission may not be suitable for the affected area.
[0226] In some embodiments, an indication message is sent to the eMBB UE to convey information about the time and / or frequency and / or beam of the affected area. This message may also provide updates on beamforming and / or interference channel information to facilitate interference cancellation for the eMBB UE.
[0227] In some embodiments, information about the demodulation reference signal (DM-RS) used by the BS to send data to the URLLC UE is indicated to the eMBB user so that the latter can offset the interference caused by the URLLC transmission to the affected eMBB transport block (TB). This information may include the time, frequency, code, and sequence resources used to send the URLLC DM-RS. In some cases, if the eMBB UE blindly detects the URLLC DM-RS, less signaling overhead may be required. For example, if the eMBB UE already knows the set of possible DM-RS ports, it can assume all of these possibilities to perform blind decoding without passing the DM-RS port used for the URLLC transmission, at the cost of more complex decoding on the eMBB UE.
[0228] In some embodiments, beam-related information is indicated to the UE, such as information about which transmit beam (e.g., beam index) the transmitter used to send URLLC data. Beam-related information may also relate to the receive beam at the UE, especially in high-frequency situations where beamforming is typically performed simultaneously on the transmitter and receiver sides to achieve better link quality. In this case, the beam-related information may actually indicate to the UE which receive beam can be used to reduce the impact caused by URLLC transmission.
[0229] Fig. 9 An example is shown in FIG. 1300 resources scheduled for eMBB transmissions are shown. Later, resources 1302 are scheduled for URLLC traffic. This is not preemptive, but a different MIMO layer is used. However, the presence of URLLC traffic will affect the ability of the eMBB UE to receive its transmissions. An indication 1304 is sent at the beginning of a subsequent eMBB transmission 1305. The location of the indication shown here is only an example.
[0230] In another example, the indication may be located in any symbol, such as at the symbol where the URLLC service arrives, or in any other subsequent symbol within or outside the duration of the affected transmission. All possible locations of the UE-specific PDCCH or group PDCCH discussed above may apply here. If the indication appears in the form of a UE-specific PDCCH, it may arrive when the UE receives its next PDCCH.
[0231] DCI format design for indicating duration
[0232] In another embodiment, a DCI format is provided for indicating the starting position and / or duration of a signal-based and / or slot-based transmission. Existing DCI formats for indicating signal-based transmissions indicate the length, but the starting position is predefined, such as starting from the next symbol after the control is located. The length can also be indicated by a higher layer.
[0233] However, in some embodiments, the data may start from the control symbol or some other symbol later. In another embodiment, a DCI format is provided for indicating the starting position and the length. In some embodiments, the K possible values of the starting position are configured by higher layer signaling, wherein a specific one is notified to the UE in the DCI. Alternatively, the starting position is notified by higher layer signaling and is not included in the DCI. The length indicates the duration from the starting position. The length may be expressed as a number of symbols, a number of time slots, or a combination of symbols and / or number of time slots.
[0234] The following is a specific example of a format that indicates the starting position and length by symbol or slot (although the same approach can be used for other granularities, such as groups of adjacent symbols or groups of adjacent slots):
[0235] A log2K-bit field indicating one of K possible starting positions, where K may be configurable, or
[0236] Alternatively, the start position can be sent in another field; (optionally, the start position can also be notified by the upper layer)
[0237] A field indicating the granularity - for example, a flag bit: 0 / 1, where 0 → granularity is symbol, 1 → granularity is time slot;
[0238] This flag bit indicates the granularity used for length indication and may be sent in DCI or notified through higher layer signaling (e.g., RRC signaling);
[0239] A field consisting of log2M bits, representing the length at the granularity indicated by the flag. M is configurable.
[0240] The field including the starting position is an optional field. If the starting position is preconfigured, it does not need to be notified in the DCI. The K starting position may also indicate the position of the symbol or time slot where the data duration starts. The UE may be configured via higher layers to understand whether the notification of the value sent in the starting position field indicates a symbol or a time slot. In one example, two K=2 options may be indicated, indicating whether the data may start from the same symbol as the control or from the next symbol, in which case 1 bit is sufficient. In another example, in the case of slot aggregation transmission, two K=2 options may be indicated, indicating whether the data starts from the same time slot where the control is received or from the next time slot. K may also include a combination of symbol and time slot positions. In one example, K=4 options are supported as the starting position. K={1,2,3,4}
[0241] K=1 Data starts at the same symbol as control K=2 Data starts at the next symbol after control K=3 Data starts at the second symbol after the control K=4 Data starts at the next time slot
[0242] In another embodiment, a DCI is provided that indicates the length in terms of signal, time slot, or a combination of both. The DCI includes the following fields:
[0243] log2 K A bit field to indicate the starting point, K may be configurable (optional field, may also be pre-configured or notified by a higher layer);
[0244] A field including log2J bits to indicate the length, with a granularity of time slots, J may be configurable;
[0245] A field of log2N bits is included to indicate the length, the granularity is symbols, N may be configurable.
[0246] This example may indicate the length in terms of any combination of symbols and slots.
[0247] Example 1:
[0248] In a first example, the slot length is 7 symbols, the maximum number of symbols is 6 (configurable), and the maximum number of slots that can be aggregated is 4 (configurable). Indications of durations greater than 7 are represented as aggregations of from 1 to 6 symbols plus slots. Fig.10 An example is shown where 9 symbols are indicated and the starting position is the 6th symbol of the slot. The indication refers to a mini-slot 1400 and a slot 1402 including two symbols.
[0249] Example 2:
[0250] In the second embodiment, the time slot length is still 7 symbols, the maximum number of symbols is 12, and the maximum number of time slots is 4 (configurable). Fig.11 An example is shown where 16 symbols are indicated and the starting position is the 4th symbol of the time slot. The indication references 9 symbols and 1 time slot. In this case, the 9 signals are separated between the first mini-time slot 1500 and the second mini-time slot 1504 before and after the time slot 1502.
[0251] The second format can support the length indication of mini-slot+timeslot or mini-slot+timeslot+mini-slot. Since the UE knows the location of its control resource set and the location of the slot boundary, the length indication is sufficient and the exact order of symbols or time slots does not need to be indicated.
[0252] Unified scheduling format
[0253] In some embodiments, the DCI format used for symbol-based transmission and slot-based transmission is unified.One or more of the following fields for slot-based or symbol-based scheduling may be configurable.
[0254] Length / Data Duration Indicator (K1 option)
[0255] DM-RS configuration or antenna port indication (K2 options)
[0256] Indication of the start position of the data duration, or the timing between the DL grant allocation and the start time of DL data transmission (K3 options)
[0257] Timing indication between UL grant allocation and UL data transmission start time (K4 options)
[0258] Timing indication (K5 options) between DL data reception and related acknowledgement / negative acknowledgement (ACK / N-ACK, A / N), where Ki (i={1,2,,..,5}) options for various situations are selected from a set of values configured by the higher layer. In one example, both symbol-based services and slot-based services can receive the same DCI, where the A / N timing indication is pointed out from the K5 options. The actual options may be different for mini-slot-based and slot-based services. The UE is configured by the higher layer to map which option to which value. For example, option 2 may correspond to a delay of 2 symbols in a mini-slot-based service, but a delay of 2 slots in a slot-based service. If the UE supports both mini-slot-based and slot-based services, its K5 options are configured so that some of the options may reference symbol-based timing, while some of the options may reference slot-based timing. Similar examples can also be used for the other four categories mentioned above.
[0259] Modifying prior grant using DL control signaling
[0260] In one embodiment, the network sends a first DL control signaling, which includes a UL or DL transmission grant for a group or UE. At least a second DL control signaling is then sent to modify the grant previously allocated to the same group or UE. The second DL control signaling may arrive before or after the UL or DL transmission is scheduled to start. The first DL control signaling may be UE-specific or group-common, i.e., broadcast or multicast. The modification of the allocated grant may be to discard the grant for the entire scheduled transmission, to modify the original allocation of time-frequency resources for the entire or part of the scheduled transmission, to preempt or postpone part of the resources allocated to the scheduled transmission, to adjust the transmission parameters, such as MCS, power or RV or number of repetitions. The UE may be configured to monitor (e.g., via RRC signaling) at least one subsequent control signaling that may be sent to modify the previous allocated grant.
[0261] Micro-slot scheduling
[0262] In some existing systems, scheduling is performed in a way that avoids reserved resources. For example, the eMBB bandwidth may also include channels containing important system information, such as PS, SS, BCH, SIB, and paging. URLLC UEs that are expected to be scheduled in this BW can be notified of these reserved resources, for example via high-layer or other broadcast signaling. The UE may receive this information through initial configuration or through RRC signaling. Therefore, the UE receives data in an area that includes some reserved resources, the UE does not expect data transmission on the reserved resources, and the data transmission can be rate matched around the reserved RE / symbol.
[0263] In some embodiments, the DCI of the mini-slot can dynamically avoid scheduling mini-slot services on the REs of reserved resources. This is to avoid the frequency band allocated to common channels, such as synchronization channels and broadcast channels. Here, the mini-slot refers to symbol-based transmission.
[0264] Signaling may be sent to indicate the location of pre-reserved frequency resources for common channels. The signaling may also be used to notify the URLLC UE of the eMBB control and / or DMRS location and to notify the UE that its data cannot preempt these resources.
[0265] Avoid mini-slot control by using slotted traffic
[0266] In some embodiments, a mini-slot based service (e.g., URLLC) may be scheduled in an ongoing slot based transmission (e.g., eMBB). Every n symbols of the slot may include a slot based set of UE control resources (n=1, 2, 3, etc.). Fig.12 , where a control resource 1600 is reserved every other symbol.
[0267] In some embodiments, when a time slot based service is scheduled, the time slot based service is scheduled to include a mini time slot control area. If a mini time slot service is scheduled, a preemption indication is sent to indicate which area is controlled by the mini time slot and / or preempted by the mini time slot service.
[0268] In another embodiment, when a time slot-based service is scheduled, the mini-time slot control area is avoided. In this case, some locations for mini-time slot control monitoring signals can be pre-configured and broadcast to all UEs in a semi-static manner. This can also be notified through RRC signaling.
[0269] The slot-based UE receives the broadcast information and knows the location of the mini-slot control resource set. If the slot-based UE is scheduled in overlapping resources, the slot-based UE assumes that there is no data transmission in these areas. The mini-slot control resource set can include UE-specific and group-common controls (e.g., A / N for unlicensed transmission).
[0270] In another embodiment, a flexible mini-slot scheduling method is provided. In this embodiment, a control region, such as a control region in a PDCCH or PDSCH region, can be reused or avoided based on whether the region is used. Pre-configured regions for control in PDSCH, such as system information, indication signaling, DMRS, etc., are avoided.
[0271] Mini-slot DCI can allocate resources according to physical resource block (RPB) granularity and symbol granularity.
[0272] Example: 12 RBs are used in the first symbol and 10 RBs are used in the second symbol. Therefore, time and frequency resource allocation can be expressed using a bitmap, where the granularity of the bitmap in time and frequency can be configurable, such as symbol or symbol group and RB or RBG.
[0273] This may result in increased overhead, but may be required if the mini-slot based UE is not aware of the skipped resources. For example, the preemption indication may be notified at the end of the slot, and when the mini-slot is scheduled, it may be necessary to dynamically avoid the preemption indication REs. In another example, mini-slot scheduling assumes that the REs including the preemption indication are reserved, so the mini-slot based UE may not receive data on these REs even if these areas are included in the resource allocation, that is, if these areas are already known in advance, then there is no need for dynamic indications to avoid these REs.
[0274] Fig.13 The example shown in shows a time slot of 7 symbols. There is an unused mini-slot control region - region 1700, and a used mini-slot control region - region 1702. In this case, the eMBB service can use resources overlapping with the unused control region 1700, but should avoid resources overlapping with the used control region 1702. A preemption indication is sent at 1704 to indicate that the eMBB service in region 1702 is preempted.
[0275] Many modifications and variations of the present disclosure are possible in light of the above teachings.It is therefore to be understood that within the scope of the appended claims, the present disclosure may be practiced otherwise than as specifically described herein.
Claims
1. A method for a base station, comprising: Every K symbols or time slots, the base station sends a group common preemption indication for a group of K symbols or time slots to the user equipment UE on a group common physical downlink control channel, wherein the group of K symbols or time slots is before the symbol or time slot including the group common preemption indication, wherein K is a positive integer; The group common preemption indication indicates which resources in the group of K symbols or time slots are preempted; The group common signaling on the group common physical downlink control channel includes the group common preemption indication and a CRC check indicating a radio network temporary identifier RNTI, and the RNTI is used to indicate the group common physical downlink control channel as a preemption indication. 2 . The method of claim 1 , wherein sending the group-common preemption indication comprises sending using a set of control resources in the group-common physical downlink control channel.
3. The method according to claim 1 or 2, further comprising: The configuration of the K value is sent via higher layer signaling.
4. The method according to claim 1 or 2, wherein for each group common preemption indication sent, the group of K symbols or time slots are the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
5. The method according to claim 2, further comprising: Sending signaling, wherein the signaling configures the control resource set used to send the preemption indication.
6. The method of claim 1, wherein the group common preemption indication comprises N bits, each bit indicating preemption to a granularity defined in time and / or frequency.
7. The method according to claim 6, further comprising: Send signaling to configure the defined granularity.
8. The method of claim 1, wherein: The group common preemption indication includes a plurality of fields; The method further comprises sending signaling to a user equipment UE, the signaling indicating which of the plurality of fields is relevant to the user equipment UE.
9. The method according to claim 1 or 2, further comprising: A group common preemption indication is sent for each of the plurality of bandwidth portions.
10. The method according to claim 1 or 2, wherein: When the preemption indication is one of the first set of values, the preemption indication indicates adjacent preempted resources; and When the preemption indication is one of a second set of values, the preemption indication indicates non-contiguous preempted resources.
11. The method according to claim 1 or 2, wherein: The group common preemption indication includes a plurality of resource specific fields.
12. A method in a user equipment UE, the method comprising: Every K symbols or time slots, receiving, by the user equipment UE from a base station on a group common physical downlink control channel, a group common preemption indication for a group of K symbols or time slots, the group of K symbols or time slots being before the symbol or time slot including the group common preemption indication, wherein K is a positive integer; The group common preemption indication indicates which resources in the group of K symbols or time slots are preempted; The group common signaling on the group common physical downlink control channel includes the group common preemption indication and a CRC check indicating a radio network temporary identifier RNTI, and the RNTI is used to indicate the group common physical downlink control channel as a preemption indication.
13. The method of claim 12, wherein receiving the group common preemption indication comprises receiving using a set of control resources in the group common physical downlink control channel.
14. The method according to claim 12 or 13, further comprising: The configuration of the value of K is received through higher layer signaling.
15. The method according to claim 12 or 13, wherein for each received group common preemption indication, the group of K symbols or time slots are the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
16. The method according to claim 12 or 13, further comprising: Receive signaling, wherein the signaling configures the set of control resources used to send the preemption indication.
17. The method of claim 12, wherein the group common preemption indication comprises N bits, each bit indicating preemption to a granularity defined in time and / or frequency.
18. The method according to claim 17, further comprising: Signaling configuring the defined granularity is received.
19. The method according to claim 12 or 13, wherein: The group common preemption indication includes a plurality of fields; The method further comprises receiving signalling indicating which of the plurality of fields is relevant to a user equipment UE receiving the signalling.
20. The method according to claim 12 or 13, wherein a group common preemption indication is sent for each of a plurality of bandwidth parts respectively, the method further comprising the user equipment UE listening to any group common preemption indication related to a bandwidth part used by the user equipment UE.
21. The method according to claim 12 or 13, wherein: When the preemption indication is one of the first set of values, the preemption indication indicates adjacent preempted resources; and When the preemption indication is one of a second set of values, the preemption indication indicates non-contiguous preempted resources.
22. The method according to claim 12 or 13, wherein: The group common preemption indication includes a plurality of resource specific fields.
23. A base station, comprising: a transmission chain, configured to send, on a group common physical downlink control channel, to a user equipment UE, a group common preemption indication for a group of K symbols or time slots every K symbols or time slots, the group of K symbols or time slots being before a symbol or time slot including the group common preemption indication, wherein K is a positive integer; The group common preemption indication indicates which resources in the group of K symbols or time slots are preempted; The group common signaling on the group common physical downlink control channel includes the group common preemption indication and a CRC check indicating a radio network temporary identifier RNTI, and the RNTI is used to indicate the group common physical downlink control channel as a preemption indication.
24. The base station according to claim 23, further comprising: A scheduler, configured to schedule resources for a first downlink service; The sending chain is further used to send the scheduled first downlink service without violating the preemption, and to send the second downlink service by using the preempted resources of the first downlink service.
25. The base station according to claim 23 or 24, wherein the transmission chain is used to transmit the group common preemption indication using a set of control resources in the group common physical downlink control channel.
26. The base station according to claim 23 or 24, further configured to send the configuration of the value of K through high-layer signaling.
27. The base station according to claim 23 or 24, wherein for each group common preemption indication sent, the group of K symbols or time slots are the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
28. The base station according to claim 25 is further used to send signaling, wherein the signaling configures the control resource set used to send the preemption indication.
29. The base station according to claim 23 or 24, wherein the group common preemption indication comprises N bits, each bit indicating preemption to a granularity defined in time and / or frequency.
30. The base station according to claim 29, further configured to send signaling for configuring the defined granularity.
31. The base station of claim 23, wherein: The group common preemption indication includes a plurality of fields; The base station is further configured to send signaling to a user equipment UE, where the signaling indicates which of the multiple fields is related to the user equipment UE.
32. The base station of claim 23 or 24, further configured to send a group common preemption indication for each of a plurality of bandwidth parts respectively.
33. The base station according to claim 23 or 24, wherein: When the preemption indication is one of the first set of values, the preemption indication indicates adjacent preempted resources; and When the preemption indication is one of a second set of values, the preemption indication indicates non-contiguous preempted resources.
34. The base station according to claim 23 or 24, wherein: The group common preemption indication includes a plurality of resource specific fields.
35. A user equipment UE, the user equipment comprising: a receiving chain for receiving, every K symbols or time slots, a group common preemption indication for a group of K symbols or time slots preceding a symbol or time slot including the group common preemption indication from a base station on a group common physical downlink control channel, wherein K is a positive integer; The group common preemption indication indicates which resources in the group of K symbols or time slots are preempted; The group common signaling on the group common physical downlink control channel includes the group common preemption indication and a CRC check indicating a radio network temporary identifier RNTI, and the RNTI is used to indicate the group common physical downlink control channel as a preemption indication.
36. The user equipment according to claim 35, wherein: The receiving chain is used to receive downlink scheduling information for scheduling a first downlink service for the user equipment UE; The receiving chain comprises a subcarrier demapper, which performs subcarrier demapping based on the received downlink scheduling information and also taking into account the received group common preemption indication.
37. The user equipment according to claim 35 or 36, wherein the receiving chain is configured to receive the group common preemption indication by receiving using a set of control resources in the group common physical downlink control channel.
38. The user equipment according to claim 35 or 36, further configured to receive the configuration of the value of K through higher layer signaling.
39. The user equipment according to claim 35 or 36, wherein for each received group common preemption indication, the group of K symbols or time slots are the last K symbols or time slots before the symbol or time slot including the group common preemption indication.
40. The user equipment according to claim 35 or 36 is further used to receive signaling, and the signaling configures the control resource set used to send the preemption indication.
41. The user equipment according to claim 35 or 36, wherein the group common preemption indication comprises N bits, each bit indicating preemption to a granularity defined in time and / or frequency.
42. The user equipment according to claim 41 is further used to receive signaling for configuring the defined granularity.
43. The user equipment according to claim 35 or 36, wherein: The group common preemption indication includes a plurality of fields; The user equipment is further configured to receive signaling, wherein the signaling indicates which of the plurality of fields is related to a user equipment UE receiving the signaling.
44. The user equipment according to claim 35 or 36, wherein a group common preemption indication is sent for each of a plurality of bandwidth parts respectively, and the user equipment is further configured to monitor any group common preemption indication related to a bandwidth part used by the user equipment UE.
45. The user equipment according to claim 35 or 36, wherein: When the preemption indication is one of the first set of values, the preemption indication indicates adjacent preempted resources; and When the preemption indication is one of a second set of values, the preemption indication indicates non-contiguous preempted resources.
46. The user equipment according to claim 35 or 36, wherein: The group common preemption indication includes a plurality of resource specific fields.
47. A computer-readable storage medium having stored thereon a computer program comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to claim 1 or 12.