Signaling unavailability of uplink and downlink resources

Abstract

Apparatuses, methods, and systems are disclosed for unified signaling for DL PI and UL CI. An apparatus (1300) in a mobile communication network includes a processor (1305) and a transceiver (1325) that receives (1505) first signaling information from a radio access network ("RAN") device to schedule first communication resources and receives (1510) second signaling information after receiving the first signaling information. Here, the processor (1305) determines, according to the second signaling information, unavailability of at least one set of uplink resources and unavailability of at least one set of downlink resources on the scheduled first communication resources.

Description

[0001] Cross-referencing of related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 051,786, entitled “Unified DCI Format for UL Cancellation Indication and DL Preemption Indication”, filed July 14, 2020, for Ankit Bhamri, Hossein Bagheri, Hyejung Jung, Karthikeyan Ganesan, Alexander Golitschek, and Ali Ramadan Ali, which is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed herein generally relates to wireless communication, and more specifically to unified signaling that indicates the cancellation of at least some portion of a scheduled uplink transmission and also indicates the preemption of at least some portion of a scheduled downlink transmission. Background Technology

[0004] In some wireless communication networks, multiple downlink control information formats can be used to indicate associations with multiple downlink and uplink transmissions. Such networks may require equipment to monitor these multiple downlink control information formats, which may require considerable equipment processing and capabilities. Summary of the Invention

[0005] A process for unified signaling for downlink (“DL”) preemption indication (“PI”) and uplink (“UL”) cancellation indication (“CI”) is disclosed. The process can be implemented by an apparatus, system, method, or computer program product.

[0006] A method for a user equipment (“UE”) includes receiving first signaling information from a radio access network (“RAN”) device to schedule first communication resources and receiving second signaling information after receiving the first signaling information, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resources.

[0007] A method for a RAN node includes transmitting first signaling information to a UE to schedule first communication resources and transmitting second signaling information to the UE after transmitting the first signaling information, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resources. Attached Figure Description

[0008] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only a few embodiments and should therefore not be considered as limiting the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0009] Figure 1 This is a schematic block diagram illustrating an embodiment of a wireless communication system with unified signaling for downlink (“DL”) preemption indication (“PI”) and uplink (“UL”) cancellation indication (“CI”);

[0010] Figure 2 This is a block diagram illustrating one embodiment of the 5G New Radio (“NR”) protocol stack;

[0011] Figure 3 This is a diagram illustrating one embodiment of the downlink control information (“DCI”) format used for unified signaling of DL PI and UL CI;

[0012] Figure 4A This is a diagram illustrating one embodiment of the time period associated with UL CI and DL PI;

[0013] Figure 4B This is a diagram illustrating another embodiment of the time region associated with UL CI and DL PI;

[0014] Figure 5 A diagram depicts an embodiment of receiving a unified DCI for DL ​​PI and UL CI on an unassigned DL symbol in the middle of a DL / UL transmission scheduled across multiple TTIs.

[0015] Figure 6 A diagram depicts an embodiment of a unified DCI for DL ​​PI and UL CI applicable to a single DL slot and a single UL slot from multiple scheduling slots;

[0016] Figure 7 A diagram depicts an embodiment of a unified DCI for different DL preemption indications and UL cancellation indications applicable to multiple scheduling DL and UL time slots;

[0017] Figure 8 A diagram depicts an embodiment of a unified DCI for common DL preemption indication and UL cancellation indication applicable to multiple scheduling DL and UL time slots;

[0018] Figure 9A diagram illustrating one embodiment of a unified DCI for DL ​​PI and UL CI across multiple DL and UL time slots is shown.

[0019] Figure 10 This is a diagram illustrating one embodiment of the PreemptionCancellation information element;

[0020] Figure 11 A diagram depicts one embodiment of a cancellation mechanism for UL transmissions that at least partially overlap with the indicated time-frequency region;

[0021] Figure 12 A diagram depicts an embodiment of a cancellation mechanism for UL transmissions that follows a TTI that at least partially overlaps with the indicated time-frequency region and includes all TTIs of that TTI;

[0022] Figure 13 This is a block diagram illustrating one embodiment of a user equipment device that can be used for unified signaling of DL PI and UL CI;

[0023] Figure 14 This is a block diagram illustrating one embodiment of a network device apparatus that can be used for unified signaling of DL PI and UL CI;

[0024] Figure 15 This is a block diagram illustrating an embodiment of a first method for unified signaling for DL ​​PI and UL CI; and

[0025] Figure 16 This is a block diagram illustrating an embodiment of a second method for unified signaling for DL ​​PI and UL CI. Detailed Implementation

[0026] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining aspects of both software and hardware.

[0027] For example, the disclosed embodiments can be implemented as hardware circuitry that includes custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0028] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device employs only signals for accessing the code.

[0029] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0030] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0031] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0032] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0033] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0034] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more of…” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of…” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes combinations of A, B, and C. As used herein, “selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0035] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that individual blocks in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0036] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0037] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0038] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0039] It should also be noted that in some alternative implementations, the functions marked in the boxes may not appear in the order shown in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods that are equivalent in function, logic, or effect to one or more boxes or portions thereof shown in the figures can be contemplated.

[0040] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0041] The description of the elements in each figure can be referenced to the elements in the preceding figures. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0042] Generally, this disclosure describes systems, methods, and apparatuses for a new unified downlink control information (“DCI”) format for instructing the cancellation of at least a portion of a scheduled (or ongoing) uplink transmission and for instructing the preemption of at least a portion of a scheduled (or ongoing) downlink transmission to a user equipment (“UE”). In some embodiments, the new unified DCI format is used at high subcarrier spacings (such as 480 kHz, 960 kHz, or higher). In some embodiments, these methods can be performed using computer code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0043] To support the 3GPP 5G New Radio (“NR”) between 52.6 GHz and 71 GHz (or even higher frequencies), the number of parameters used at higher radio frequencies may be increased, including subcarrier spacing (“SCS”) and / or channel bandwidth (“BW”). However, at the physical layer, one or more new parameter sets (i.e., the μ values ​​in 3GPP TS 38.211) used for operation in this frequency range have an impact on physical signals / channels and may further affect time-related aspects appropriate to each new parameter set, such as BWP and beam switching times for Physical Downlink Shared Channel (“PDSCH”), Physical Uplink Shared Channel (“PUSCH”), Sounding Reference Signal (“SRS”), and Channel State Information (“CSI”), Hybrid Automatic Repeat Request (“HARQ”) scheduling, UE processing, preparation, and computation time, respectively.

[0044] This disclosure addresses the monitoring problem of the Physical Downlink Control Channel (“PDCCH”) in DCI format when using higher subcarrier spacing values ​​such as 480 kHz, 960 kHz, and higher. When using high SCS, PDCCH monitoring can become very frequent due to the shorter time slot duration. In particular, PDCCH monitoring capacity decreases considerably with increasing subcarrier spacing. Since operation at 52.6 GHz or higher frequencies will likely require even higher subcarrier spacing values ​​(e.g., 480 kHz, 960 kHz, and higher), PDCCH monitoring capability is expected to be significantly reduced compared to NR operation.

[0045] This disclosure addresses how to reduce PDCCH monitoring of group common DCI for cancellation indications to UEs transmitting to ULs with lower priority scheduling and for preemption indications to UEs transmitting to DLs with lower priority scheduling when higher priority transmissions are scheduled to be transmitted on overlapping resources.

[0046] DCI transmits downlink control information for one or more cells with one RNTI. The DCI format defined in Table 7.3.1-1 is supported in NR.

[0047] Table 1: DCI Format

[0048]

[0049] The fields defined in the following DCI format are mapped to information bits a0 to a1 as follows. A-1 .

[0050] Each field is mapped in the order it appears in the description, including zero-padding bits (if any), wherein the first field is mapped to the lowest-order information bit a0, and each consecutive field is mapped to a higher-order information bit. The most significant bit of each field is mapped to the lowest-order information bit of that field; for example, the most significant bit of the first field is mapped to a0.

[0051] If the number of information bits in the DCI format is less than 12 bits, zeros should be appended to the DCI format until the payload size is equal to 12.

[0052] The size of each DCI format is determined by the configuration of the corresponding active bandwidth portion of the scheduled cell and can be adjusted as necessary.

[0053] In some embodiments, DCI format 2_1 is used to indicate preemption of DL resources to accommodate high-priority (i.e., URLLC) transmission / reception. Regarding the process of monitoring PDCCH candidates in DCI format 2_1, if the UE is provided with a DownlinkPreemption information element (“IE”), the UE is configured with an INT-RNTI provided by the parameter int-RNTI for monitoring PDCCHs conveying DCI format 2_1. Additionally, the UE:

[0054] • Configure the serving cell set via the parameter iht-ConfigurationPerServingCell, which includes the serving cell index set provided by the parameter corresponding servingCellId and the corresponding position set of the fields in DCI format 2_1 via the parameter positionInDCI.

[0055] • Configure the payload size of DCI format 2_1 information via parameter dci-PayloadSize

[0056] • Configure the granularity of time-frequency resource indication via the timeFrequencySet parameter.

[0057] If the UE detects the DCI format 2_1 of a serving cell from the configured serving cell set, the UE can assume that there is no transmission to the UE in the PRBs from the physical resource block (“PRB”) set and symbol set of the last monitoring period, and in the symbols indicated by DCI format 2_1. The indication via DCI format 2_1 does not apply to the reception of synchronization signal / physical broadcast channel (“SS / PBCH”) blocks. This PRB set is equal to the active DL BWP and includes B INT One PRB.

[0058] If the UE detects DCI format 2_1 in the PDCCH transmitted in a control resource set (“CORESET”) within a time slot, then that symbol set is the last symbol before the first symbol of the CORESET within the time slot. Symbol, where T INT The PDCCH monitoring periodicity is provided by the value of the parameter monitoringSlotPeriodicityAndOffset. μ is the number of symbols per time slot, and μ is the SCS configuration of the serving cell with mappings to the corresponding fields in DCI format 2_1. INT This refers to the SCS configuration of the UE receiving the DL BWP with the PDCCH in DCI format 2_1. If the UE is provided with tdd-UL-DL-ConfigurationCommon, then from the last symbol before the first symbol of the CORESET in the time slot... Symbols excluded are those indicated as uplink by tdd-UL-DL-ConfigurationCommon. The resulting symbol set includes those represented as NI. NT Multiple symbols.

[0059] UE does not expect to be provided The value of μ is not an integer. INT and T INT The value of . The UE does not expect to configure more than one PDCCH monitoring opportunity for DCI format 2_1 in a time slot via the parameter monitoringSymbolsWithinSlot. The parameter timeFrequencySet provides the UE with the indication granularity of the PRB set and symbol set.

[0060] If the value of the parameter timeFrequencySet is 'set0', then the 14 bits of the MSB from the field in DCI format 2_1 have a one-to-one mapping with 14 consecutive groups of symbols from the symbol set, where the first Each of the symbol groups includes One symbol, finally Each of the symbol groups includes A symbol is represented by a bit value of 0, indicating a transmission to the UE in the corresponding symbol group, and a bit value of 1, indicating no transmission to the UE in the corresponding symbol group.

[0061] If the value of timeFrequencySet is 'set1', then the 7 pairs of bits of the MSB from the field in DCI format 2_1 have a one-to-one mapping with 7 groups of consecutive symbols, where the first Each of the symbol groups includes One symbol, finally Each of the symbol groups includes The first bit of the bit pair in the symbol group applies to the symbol from B. INT The first set of PRBs A subset of PRBs, the second bit of the bit pair in the symbol group applies to the bit from B INT The last of the PRB sets A subset of PRBs, with a bit value of 0 indicating a transmission to the UE in the corresponding symbol group and PRB subset, and a bit value of 1 indicating no transmission to the UE in the corresponding symbol group and PRB subset.

[0062] DCI format 2_1 is used to notify PRB and OFDM symbols, where the UE may assume that no transmission is expected for the UE.

[0063] The following information is transmitted using DCI format 2_1 with CRC scrambling via INT-RNTI:

[0064] • Preemption instruction 1, preemption instruction 2, ..., preemption instruction N.

[0065] The size of DCI format 2_1 can be configured by higher layers up to 126 bits. Each preemption indicator is 14 bits.

[0066] In some embodiments, DCI format 2_4 is used to indicate the cancellation of a scheduled UL transmission to accommodate a high-priority URLLC transmit / receive. Regarding the process of monitoring PDCCH candidates for DCI format 2_4, if an UplinkCancellation IE is provided to the UE, a CI-RNTI is provided to the UE via the ci-RNTI parameter for monitoring PDCCH candidates for DCI format 2_4. The UplinkCancellation IE additionally provides the UE with the following:

[0067] • The serving cell set via the parameter ci-ConfigurationPerServingCell, which includes the serving cell index set and the corresponding position set of fields in DCI format 2_4 via the parameter positionInDCI.

[0068] • Through multiple fields in DCI format 2_4 of the parameter positionInDCI-forSUL, this parameter is used for each serving cell with an SUL carrier if the serving cell is configured with an SUL carrier, and for the SUL of the serving cell if the serving cell is configured with an SUL.

[0069] • The payload size is indicated by the parameter dci-PayloadSize-forCI in DCI format 2_4.

[0070] • Indication of time-frequency resources via the parameter timeFrequencyRegion

[0071] For a serving cell that has the association field in DCI format 2_4, the field is represented by the following items:

[0072] ·N CI The number of bits provided by the parameter CI-PayloadSize

[0073] ·B CI The number of PRBs provided by the frequencyRegionforCI parameter in timeFrequencyRegion IE.

[0074] ·T CI The number of symbols provided by the timeDurationforCI parameter in timeFrequencyRegion IE, excluding symbols used to receive SS / PBCH blocks and DL symbols indicated by patdd-UL-DL-ConfigurationCommon.

[0075] ·G CIThe T parameter provided by the timeGranularityforCI parameter in timeFrequencyRegion IE is used. CI Number of partitions for symbols

[0076] From N CI G bits CI A set of bits and G CI Each symbol group has a one-to-one mapping, where the first Each in the group includes One symbol, and the remaining Each in the group includes Symbol. The UE determines the symbol duration for the SCS configuration of the active DL BWP, where the UE monitors the PDCCH for DCI format 2_4 detection.

[0077] For a symbol group, N from each bit set BI =N CI / G CI bits and N BI The group PRB has a one-to-one mapping, where the first Each in the group includes One PRB, and the remaining Each in the group includes One PRB. The UE receives the offset RB from the 3GPP TS 38.214 specification. start and length L RB As the frequencyRegionforCI of RIV, and the O from the SCS configuration indicating the active DL BWP carrier In the FrequencyInfoUL-SIB, offsetToCarrier determines the first PRB index as... And the number of consecutive RBs is determined as The UE monitors the PDCCH for DCI format 2_4 detection.

[0078] The indication of DCI format 2_4 for the serving cell applies to PUSCH or SRS transmissions on the serving cell. For the serving cell, the UE determines T CI The first symbol in the set is the T symbol representing the start of the period from which the UE detects the end of the PDCCH reception of DCI format 2_4. proc,2 The first symbol after +d. T proc,2 Corresponding to hypothesis d 2,1=0 PUSCH processing capability 2, where μ is the minimum SCS configuration between PDCCH and PUSCH transmissions or SRS transmissions on the serving cell. The UE does not expect T after the last symbol of the CORESET in which the UE detects DCI format 2_4. proc,2 Cancel PUSCH or SRS transmission before the corresponding symbol.

[0079] If a UE with DCI format 2_4 of the serving cell is detected to cancel PUSCH transmission, or if PUSCH transmission has duplicates, then the duplicate PUSCH transmission is canceled, or if SRS transmission on the serving cell is canceled under the following conditions respectively:

[0080] ·From T CI The symbol group in DCI format 2_4 has a corresponding bit value '1' and includes symbols for PUSCH transmissions (repetitions) or SRS transmissions, and

[0081] ·From B CI Each PRB group has a corresponding bit value '1' in DCI format 2_4 and includes symbols for either PUSCH transmission (repetition) or SRS transmission.

[0082] in

[0083] Cancellation of a PUSCH transmission (repetition) includes all symbols starting from the earliest symbol of the PUSCH transmission (repetition), which are in one or more symbol groups with a corresponding bit value '1' in DCI format 2_4;

[0084] Cancellation of SRS transmissions only includes symbols in one or more symbol groups that have a corresponding bit value '1' in DCI format 2_4.

[0085] The currently supported DCI formats for group common indications to the UE for UL transmission cancellation indications and DL transmission preemption indications are specified as follows:

[0086] DCI format 2_4 is used to notify the UE to cancel the corresponding UL transmission of PRB and OFDM symbols from the UE.

[0087] The following information is transmitted using DCI format 2_4 with CRC scrambling via CI-RNTI:

[0088] Cancel instruction 1, cancel instruction 2, ..., cancel instruction N.

[0089] The size of DCI format 2_4 can be configured by the higher-level parameter dci-PayloadSize-forCI, which can be up to 126 bits. The number of bits for each cancellation indication can be configured by the higher-level parameter CI-PayloadSize. For the UE, there is at most one cancellation indication on the UL carrier.

[0090] This paper describes a novel DCI format for signaling both downlink preemption indications and uplink cancellation indications to allow higher-priority downlink and uplink transmissions on resources that partially or completely overlap with already scheduled downlink and uplink transmissions, respectively. DL preemption and UL preemption techniques for multi-slot DL and / or UL transmissions are also described.

[0091] Beneficially, the new DCI format reduces PDCCH monitoring of separate DCIs used for DL ​​preemption and UL cancellation when high SCS values ​​are utilized, and the UE is configured to monitor a unified DCI used to signal both DL PI and UL CI.

[0092] Figure 1 A wireless communication system 100 for unified signaling of DL PI and UL CI according to embodiments of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may consist of a basic unit 121, with the remote unit 105 communicating with the basic unit 121 using a wireless communication link 123. Even in Figure 1 A specific number of remote units 105, basic units 121, wireless communication links 123, RAN 120, and mobile core network 140 are depicted, but those skilled in the art will recognize that any number of remote units 105, basic units 121, wireless communication links 123, RAN 120, and mobile core network 140 may be included in the wireless communication system 100.

[0093] In one implementation, RAN 120 conforms to the 5G system specified in the 3rd Generation Partnership Project (“3GPP”) specifications. For example, RAN 120 may be a next-generation radio access network (“NG-RAN”) that implements a new radio (“NR”) radio access technology (“RAT”) and / or a long-term evolution (“LTE”) RAT. In another example, RAN 120 may include a non-3GPP RAT (e.g., Or an IEEE 802.11 series compliant WLAN. In another embodiment, RAN 120 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 can implement some other open or proprietary communication networks (such as Global Microwave Access Interoperability (“WiMAX”) or IEEE 802.16 series standards) and other networks. This disclosure is not intended to limit itself to the implementation of any particular wireless communication system architecture or protocol.

[0094] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., TVs connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art. In various embodiments, remote unit 105 includes a subscriber identity and / or identification module (“SIM”) and a mobile device (“ME”) that provides mobile terminal functions (e.g., radio transmission, handover, voice encoding and decoding, error detection and correction, signaling and access to the SIM). In some embodiments, the remote unit 105 may include a terminal device (“TE”) and / or be embedded in an appliance or device (e.g., a computing device as described above).

[0095] Remote unit 105 can communicate directly with one or more basic units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Alternatively, UL and DL communication signals can be carried via wireless communication link 123. Here, RAN 120 is an intermediate network providing access to mobile core network 140 for remote unit 105. As described in more detail below, basic unit 121 can send UL and / or DL ​​grants 125 to remote unit 105 that schedules communication resources. However, basic unit 121 can later send a unified UL cancellation and DL preemption indication 127, indicating both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resources.

[0096] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Voice over Internet Protocol (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0097] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0098] In the context of a 5G system (“5GS”), the term “PDU session” refers to a data connection that provides an end-to-end (“E2E”) user plane (“UP”) connection between a remote unit 105 and a specific data network (“DN”) via UPF 141. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0099] In the context of 4G / LTE systems such as Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides an end-to-end (E2E) connection between a remote unit and the PDN. The PDN connection process establishes an EPS bearer, i.e., a tunnel between the remote unit 105 in the mobile core network 140 and the packet gateway (“PGW”, not shown). In some embodiments, a one-to-one mapping exists between the EPS bearer and a QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS class identifier (“QCI”).

[0100] Basic unit 121 may be distributed across a geographical area. In some embodiments, basic unit 121 may also be referred to as an access terminal, access point, base station, base station, node B (“NB”), evolved node B (abbreviated as eNodeB or “eNB”, also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) node B), 5G / NR node B (“gNB”), home node B, relay node, RAN node, or any other term used in the art. Basic unit 121 is typically part of a RAN such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding basic units 121. These and other elements of the radio access network are not illustrated but are generally well known to those skilled in the art. Basic unit 121 is connected to mobile core network 140 via RAN 120.

[0101] Basic unit 121 can provide services to multiple remote units 105 within a service area (e.g., a cell or cell sector) via wireless communication link 123. Basic unit 121 can communicate directly with one or more remote units 105 via communication signals. Typically, basic unit 121 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried via wireless communication link 123. Wireless communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 123 facilitates communication between one or more remote units 105 and / or one or more basic units 121. Note that during NR operation on unlicensed spectrum (referred to as "NR-U"), basic unit 121 and remote units 105 communicate via unlicensed (i.e., shared) radio spectrum.

[0102] In one embodiment, the mobile core network 140 is a 5GC or evolved packet core network (“EPC”), which may be coupled to a packet data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”). This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0103] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes at least one UPF 141. Mobile core network 140 also includes multiple control plane (“CP”) functions, including but not limited to Access and Mobility Management Functions (“AMF”) 143, Session Management Functions (“SMF”) 145, Policy Control Functions (“PCF”) 147, Unified Data Management Functions (“UDM”), and User Data Repository (“UDR”) serving RAN 120. Although Figure 1 A specific number and type of network functions are described, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140.

[0104] UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting data networks (DN) in the 5G architecture. AMF 143 is responsible for NAS signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. SMF 145 is responsible for session management (i.e., session establishment, modification, and release), remote unit (i.e., UE) IP address allocation and management, DL data notification, and traffic steering configuration of UPF 141 for appropriate service routing.

[0105] PCF 147 is responsible for unifying the policy framework, thereby providing policy rules to CP functions and accessing subscription information used for policy decisions in the UDR. UDM is responsible for generating authentication and key protocol (“AKA”) credentials, handling user identifiers, granting access, and managing subscriptions. The UDR is a repository of subscriber information and can be used to provide services for many network functions. For example, the UDR can store subscription data, policy-related data, subscriber-related data that can be exposed to third-party applications, etc. In some embodiments, the UDM and UDR are co-located and depicted as a combined entity “UDM / UDR” 149.

[0106] In various embodiments, the mobile core network 140 may also include a network repository function (“NRF”) (which provides network function (“NF”) service registration and discovery, enabling NFs to identify the appropriate services among themselves and communicate with each other via application programming interfaces (“APIs”), a network exposure function (“NEF”) (which is responsible for enabling customers and network partners to easily access network data and resources), an authentication server function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF can act as an authentication server and / or authentication proxy, thereby allowing AMF 143 to authenticate remote unit 105. In some embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0107] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") services. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication ("URLLC") services. In other examples, network slices may be optimized for machine-type communication ("MTC") services, massive MTC ("mMTC") services, and Internet of Things ("IoT") services. In still other examples, network slices may be deployed for specific application services, vertical services, specific use cases, etc.

[0108] Network slice instances can be identified by Single Network Slice Selection Auxiliary Information (“S-NSSAI”), while the set of network slices authorized for use by remote unit 105 is identified by Network Slice Selection Auxiliary Information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In some embodiments, various network slices may include individual instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, Figure 1 Different network slices are not shown, but support for them is assumed.

[0109] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the embodiments of unified signaling for DL ​​PI and UL CI described are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular networks), General Packet Radio Service (“GPRS”), General Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, etc.

[0110] Furthermore, in the LTE variant of the mobile core network 140 where EPC is used, the described network functions can be replaced by appropriate EPC entities, such as the Mobility Management Entity (“MME”), Serving Gateway (“SGW”), PGW, Home Subscriber Server (“HSS”), etc. For example, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0111] In the following description, the term "RAN node" is used for a base station, but it can be replaced by any other radio access node, such as a gNB, ng-eNB, eNB, base station ("BS"), access point ("AP"), etc. Furthermore, these operations are primarily described in the context of 5G NR. However, the solutions / methods described below are equally applicable to other mobile communication systems that support unified signaling for DL ​​PI and UL CI.

[0112] Figure 2 An NR protocol stack 200 according to an embodiment of this disclosure is depicted. Although Figure 2 The diagram illustrates UE 205, RAN node 210, and AMF 215 in a 5G core network (“5GC”), but they represent a group of remote units 105 interacting with basic unit 121 and mobile core network 140. As depicted, protocol stack 200 includes user plane protocol stack 201 and control plane protocol stack 203. User plane protocol stack 201 includes physical (“PHY”) layer 220, medium access control (“MAC”) sublayer 225, radio link control (“RLC”) sublayer 230, packet data convergence protocol (“PDCP”) sublayer 235, and service data adaptation protocol (“SDAP”) layer 240. Control plane protocol stack 203 includes physical layer 220, MAC sublayer 225, RLC sublayer 230, and PDCP sublayer 235. Control plane protocol stack 203 also includes radio resource control (“RRC”) layer 245 and non-access stratum (“NAS”) layer 250.

[0113] The AS layer (also referred to as the "AS protocol stack") of the user plane protocol stack 201 consists of at least the SDAP, PDCP, RLC, and MAC sublayers and the physical layer. The AS layer of the control plane protocol stack 203 consists of at least the RRC, PDCP, RLC, and MAC sublayers and the physical layer. Layer 2 ("L2") is divided into SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") includes the RRC sublayer 245 and the NAS layer 250 for the control plane, and includes, for example, the Internet Protocol ("IP") layer and / or the PDU layer (not depicted) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and above (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers."

[0114] Physical layer 220 provides a transport channel to MAC sublayer 225. Physical layer 220 may perform clear channel assessment and / or listen-before-talk (“CCA / LBT”) procedures using energy detection thresholds, as described herein. In some embodiments, physical layer 220 may send a notification of UL listen-before-talk (“LBT”) failure to the MAC entity at MAC sublayer 225. MAC sublayer 225 provides a logical channel to RLC sublayer 230. RLC sublayer 230 provides an RLC channel to PDCP sublayer 235. PDCP sublayer 235 provides radio bearers to SDAP sublayer 240 and / or RRC layer 245. SDAP sublayer 240 provides QoS flows to the core network (e.g., 5GC). RRC layer 245 provides carrier aggregation and / or dual connectivity addition, modification, and release. RRC layer 245 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRB”) and data radio bearers (“DRB”).

[0115] NAS layer 250 is located between UE 205 and 5GC 215. NAS messages are transparently transmitted through the RAN. NAS layer 250 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 205 when UE 205 moves between different cells in the RAN. Conversely, AS layer is located between UE 205 and the RAN (i.e., RAN node 210) and carries information through the radio portion of the network.

[0116] For very high SCS such as 480kHz and 960kHz, the PDCCH monitoring capability of UE 205 is problematic. If UE 205 is required to monitor multiple DCI formats in each time slot with high SCS, further increased UE capability may be necessary. However, to avoid impacting UE capability, alternative solutions are being sought to limit PDCCH monitoring requirements.

[0117] Figure 3 Example scenario 300 is depicted using the new unified DCI format defined herein for UL cancellation indication (“CI”) and DL preemption indication (“PI”). This new unified DCI format can be used with high subcarrier spacing (e.g., 480kHz, 960kHz) to indicate / trigger cancellation of at least a portion of an uplink transmission that has been scheduled or is in progress, and also to indicate preemption of at least a portion of a downlink transmission to the UE that has been scheduled or transmitted.

[0118] In scenario 300, a UE such as UE 205 receives DCI 305 in symbols 0 and 1 of time slot N, wherein DCI 305 schedules resources 315 for DL ​​transmission (e.g., PDSCH) in time slot N+1 and resources 320 for UL transmission (e.g., PUSCH) in time slot N+2. The received DCI is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource grants and DL resource grants. In other embodiments, the first signaling information includes two separate DCIs that schedule UL and DL respectively.

[0119] The use of a single uniform DCI comprising both UL resource licenses and DL resource licenses is described in co-pending international application PCT / IB2021 / 055778 entitled “CONTOL INFORMATION THAT SCHEDULES OR ACTIVATES MULTIPLETRANSMISSIONS” filed on 28 June 2021 for Ankit Bhamri, Alexander Golitschek, Karthikeyan Ganesan, Hyejung Jung and Ali Ramadan Ali, which is incorporated herein by reference. The use of a single uniform DCI that incorporates both UL resource licenses and DL resource licenses is also described in the co-pending international application PCT / IB2021 / 055767 entitled “RESTRICTIONS BASED ON ACONFIGURED NUMEROLOGY” filed on 28 June 2021 for Ankit Bhamri, Hyejung Jung, Alexander Golitschek, Karthikeyan Ganesan and Ali Ramadan Ali, which is incorporated herein by reference.

[0120] Additionally, UE 205 also receives a new unified DCI format 310 in symbols 12 and 13 of time slot N for preemption and cancellation indications, which indicates to UE 205 both A) at least one grid 325 for time-frequency resources (i.e., the area indicated by the DL PI) for DL ​​preemption and B) at least one additional grid 330 for time-frequency resources (i.e., the area indicated by the UL PI) for UL cancellation. Here, DL preemption may be due to another higher-priority UE being scheduled for DL ​​reception on resources overlapping with those scheduled for UE 205 in DCI 305. Similarly, UL cancellation may be due to another higher-priority UE being scheduled for UL transmission on resources overlapping with those scheduled for UE 205 in DCI 305.

[0121] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning the entire time slot N+1, in other embodiments, scheduled / licensed DL resources may be used only for a portion of time slot N+1. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning the entire time slot N+2, in other embodiments, scheduled / licensed UL resources may be used only for a portion of time slot N+2.

[0122] Although in the above description, DL resource 315 (PDSCH) and UL resource 320 (PUSCH) are each dynamically licensed using DCI 305, in other embodiments, one or both of DL resource 315 (PDSCH) and UL resource 320 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the new DCI format 310 indicating the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0123] According to an embodiment of the first solution, when other high-priority services DL and UL are scheduled for other UEs on partially or fully overlapping time-frequency resources, a new group common unified DCI format is used to signal both a DL preemption indication (“DL PI”) and a UL cancellation indication (“UL CI”) to UE 205 (which has already scheduled DL and UL transmissions). In the example, the presence of UL CI and / or DL ​​PI in the unified GC-DCI format can be configurable for the search space.

[0124] In an example of reducing the DCI size, the frequency granularity of the cancel / preemption indication for SCSs larger than a threshold (e.g., SCSs greater than 480 kHz) is the entire BWP or half of the BWP. In a related example, compared to the case where the DCI indicates only one of UL CI or DL ​​PI (where the frequency granularity can be finer (e.g., half of the BWP)), when the DCI indicates both UL CI and DL PI, the frequency granularity of the cancel / preemption indication for SCSs larger than a threshold (e.g., SCSs greater than 480 kHz) is coarser (e.g., the entire BWP).

[0125] In one example, UE 205 is configured to monitor the group common unified DCI format when the UL SCS and DL SCS associated with the group common DCI are substantially the same or similar (e.g., the ratio of UL SCS to DCI SCS is less than a predetermined threshold). In another example, UE 205 is configured to monitor the group common unified DCI format when the ratio of UL SCS to DL SCS is greater than a predetermined threshold.

[0126] Figure 4A A time zone 400 associated with UL CI and DL PI according to the first solution is depicted. The DL PI time zone is defined as the symbol between two GC-DCI monitoring moments, wherein the end of the DL PI time zone is the first symbol in which the control resource set (“CORESET”) receiving the DL PI indication in the GC-DCI is received. The UL CI time zone is defined as the symbol starting from the first symbol after the end of the GC-DCI reception in GC-DCI format where “T” symbols have been detected by UE 205 (“T” is an offset parameter depending on the UL processing timeline).

[0127] The following is an example of the group's common unified DCI format based on the first solution.

[0128] In Example 'A', the time region to which the DL PI applies (referred to as the first time region or DL ​​PI time region) indicated by the unified GC-DCI is derived from the periodicity of the unified GC-DCI or based on the first RRC configuration, and the time region to which the UL CI applies (referred to as the second time region or UL CI time region) indicated by the unified GC-DCI is derived from the periodicity of the unified GC-DCI or based on the second RRC configuration.

[0129] In the relevant example 'Alt.A', the first and second RRC configurations are the same (e.g., the same configuration parameters, such as the duration of a single time zone signaled via RRC signaling, apply to both DL PI and UL CI).

[0130] In Example "B" (which is also related to Example "A"), the end of the first time zone is determined based on GC-DCI reception (e.g., the start / end of reception) / GC-DCI monitoring timing / resources for monitoring GC-DCI / CORESET of GC-DCI transmission (e.g., the last / first symbol of the CORESET), and the start of the second time zone is determined based on GC-DCI reception (e.g., the end / start of reception) / GC-DCI monitoring timing / resources for monitoring GC-DCI / CORESET of GC-DCI transmission (e.g., the first / last symbol of the CORESET) (and possibly an additional time offset after GC-DCI reception).

[0131] In example 'C', depending on the UL-DL configuration / arrangement of the symbol (e.g., as indicated by tdd-UL-DL-ConfigurationCommon), the GC-DCI may contain only one of the UL CI and DL PI for the serving cell. For example, in the diagram below, GC-DCI 0 indicates only the DL PI, GC-DCI 1 indicates both the DL PI and UL CI, and GC-DCI 2 indicates only the UL CI.

[0132] In one implementation, UE 205 does not expect to receive GC-DCI 0, which indicates a cancellation indication of a subset of symbols, rather than the entire symbol set of the associated UL CI time region.

[0133] In another implementation, the UL CI field in GC-DCI 0 can be reused to indicate a more fine-grained DLPI indication (e.g., the DL PI field provides a time indication for the preempted DL symbol separately, and the UL PI field indicates for which half of the BWP DL preemption is applicable). In the example, the DL PI field in GC-DCI 2 can be used to indicate UCLI for a secondary carrier. In another example, the DL PI field in GC-DCI 2 can be used to indicate UCLI for another serving cell.

[0134] In one implementation, the field lengths of UL CI and DL PI are related (e.g., the UL CI field size is equal to the DL PI size + delta, where delta can be '0', a fixed positive integer value, or a fixed negative integer value). In another example, a joint field exists for DL ​​PI and UL CI. In one example, the DL PI indication and UL CI indication appear consecutively in the GC-DCI (e.g., there is a positionInDCI RRC field for each serving cell).

[0135] The GC-DCI may contain fields indicating whether the UL CI or DL ​​PI field is applicable (e.g., or for another purpose). For example, RAN node 210 may indicate in GC-DCI 0 that the UL CI field is not applicable.

[0136] Figure 4B An example of a time zone 450 associated with the UL CI and DL PI of the serving cell according to a first solution is depicted. In the depicted example, GC-DCI 0 indicates only the DL PI, GC-DCI 1 indicates both the UL CI and the DL PI, and GC-DCI 2 indicates only the UL CI. In one implementation, the GC-DCI containing the uniform DLPI / ULCI includes explicit fields indicating the presence or absence of the DLPI and UL CI. In another implementation, invalid fields for the DLPI / ULCI can be used to indicate their absence.

[0137] In one example, the payload size in the unified DCI format (referred to as "dci-PayloadSize-forCIPI") is signaled (e.g., via RRC). In another example, the payload size in the unified DCI format is determined based on the payload size of the DL PI (e.g., dci-PayloadSize) and the payload size of the UL CI (e.g., dci-PayloadSize-forCI). For example, the payload size in the unified DCI format is the sum of the payload sizes of the DL PI and the UL CI.

[0138] In the example, UE 205 determines the location of the DLPI / ULCI field based on one or more of dci-PayloadSize-forCIPI, dci-PayloadSize, dci-PayloadSize-forCI, and the size of the serving cell's UL cancellation indicator (e.g., CI-PayloadSize). In one implementation, UE 205 determines the location of the DLPI field in the unified DCI format based on dci-PayloadSize-forCIPI and dci-PayloadSize, and UE 205 determines the location of the ULCI field based on dci-PayloadSize-forCIPI, dci-PayloadSize-forCI, and CI-PayloadSize.

[0139] In one example, in Unified GC-DCI, the UL CI field payload size (e.g., the UL CI field payload size indicated by dci-PayloadSize-forCI / CI-PayloadSize in Release 16) is less than / greater than a threshold. For example, the UL CI field payload size is not greater than the DL PI field size plus an offset (e.g., the offset can be fixed, configurable, and determined from UE 205 capability signaling). In another example, in Unified GC-DCI, it is impossible to have a UL CI field payload size larger than the value specified in Rel-16 / DCI format 2_4.

[0140] In one example, UL CI applies to UL transfers that have resources that overlap with the resources indicated in the UL CI, regardless of the priority of the UL transfer.

[0141] In one example, if the UL transmission is scheduled via a DCI sent before the UL CI, then the UL CI is only applicable to the UL transmission.

[0142] In an alternative embodiment, when UE 205 is scheduled for DL ​​and UL transmissions across multiple TTIs in one or more time slots, the uniform DCI format for DL ​​PI and UL CI is UE-specific, wherein only the specific UE 205 needs to monitor the DCI, receives a first time-frequency resource set consisting of one or more time-frequency resources for one or more TTIs preempted by DL in the corresponding TTI, and receives a second time-frequency resource set consisting of one or more time-frequency resources for one or more TTLs canceled by UL in the corresponding TTI.

[0143] According to an embodiment of the second solution, UE 205 may need to monitor the unified DCI for DL ​​PI and UL CI only when the subcarrier spacing (“SCS”) is higher than a specific threshold for both DL and UL, wherein the subcarrier spacing threshold can be configured / indicated to UE 205 by RAN node 210. In an alternative embodiment, MAC CE instructions are used to activate and / or deactivate monitoring of the unified DCI for DL ​​PI and UL CI. In another embodiment, monitoring of the unified DCI format for DL ​​PI and UL CI depends on monitoring of other DCI formats. For example, when UE 205 is configured / indicated to monitor the unified DCI format used for scheduling DL and UL transmissions, UE 205 also monitors new unified DCI formats for DL ​​PI and UL CI.

[0144] In one example implementation of the second embodiment, whenever the UE 205 is configured / instructed to monitor the unified DCI for DL ​​PI and UL CI, the UE 205 is not required to monitor at least two other DCI formats, including format 2_1 (DL PI) and format 2_4 (UL CI).

[0145] In the example, UE 205 is configured to monitor the unified DCI format for DL ​​PI and UL CI in a first search space and DCI format 2_1 / 2_4 in a second search space. In this example, the search spaces should not overlap. In another example, the search spaces may overlap (e.g., in time or time-frequency).

[0146] Figure 5 An example scenario 500 is depicted, according to an embodiment of the second solution, where a unified DCI for DL ​​PI and UL CI is received on an unallocated DL symbol during the middle of scheduled DL / UL transmissions across multiple TTIs (e.g., time slots). Whenever UE 205 is configured / instructed to monitor the unified DCI for DL ​​PI and UL CI and UE 205 is scheduled with multiple DL and UL transmissions across multiple TTIs / time slots, UE 205 monitors for a new DCI format for the PDCCH, i.e., carrying the unified DCI for DL ​​PI and UL CI in the middle of these scheduled DL / UL transmissions. In various embodiments, UE 205 monitors for a new unified DCI format during unallocated DL symbols across multiple TTIs / time slots, if any, such as Figure 5 As shown.

[0147] In scenario 500, UE 205 receives DCI 505 in time slot N (e.g., in symbols 0 and 1 of time slot N), wherein DCI 505 schedules resources 510 for DL ​​transmission (e.g., PDSCH) in time slot N+1 and resources 515 for UL transmission (e.g., PUSCH) in time slot N+2. DCI 505 also schedules resources 520 for DL ​​transmission (e.g., PDSCH) in time slot N+4 and resources 525 for UL transmission (e.g., PUSCH) in time slot N+5. The received DCI 505 is an example of first signaling information sent from RAN node 210 that schedules communication resources. In the described embodiment, the first signaling information is a single unified DCI that includes both UL resource grants and DL resource grants. In other embodiments, the first signaling information may include separate DCIs that schedule UL and DL respectively.

[0148] No DL resources were allocated to UE 205 in time slot N+3, therefore UE 205 monitors the new unified DCI format 530 for preemption and cancellation indication. The unified DCI format 530 for preemption and cancellation indication received in time slot N+3 indicates to UE 205 both A) at least one grid 535 for time-frequency resources (i.e., the area indicated by DL PI) for DL ​​preemption and B) at least one additional grid 540 for time-frequency resources (i.e., the area indicated by UL PI) for UL cancellation.

[0149] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning an entire time slot, in other embodiments, scheduled / licensed DL resources may be used only for a portion of the time slot. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning an entire time slot, in other embodiments, scheduled / licensed UL resources may be used only for a portion of the time slot.

[0150] Although in the above description, DL resources 510, 520 (PDSCH) and UL resources 515, 525 (PUSCH) are each dynamically licensed using DCI 505, in other embodiments, one or both of DL resources 510, 520 (PDSCH) and UL resources 515, 525 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource indicated by the new DCI format 530.

[0151] In an example implementation of the second solution, whenever UE 205 is configured / instructed to monitor the unified DCI 530 for DLPI and UL CI and may be additionally configured to monitor DCI format 2_1 and / or format 2_4, UE 205 is also configured with a new RNTI for scrambling the CRC of the new unified DCI, wherein the size of the new unified DCI is different from the size of DCI format 2_1 and format 2_4.

[0152] In another example implementation of the second solution, when the UE 205 is configured / instructed to monitor the unified DCI 530 for DLPI and UL CI, the identifier INT-RNTI (i.e., for DL ​​preemption indication) is used to scramble the CRC of the new DCI 530, and the size of the new unified DCI 530 is the same as the size of DCI format 2_1 (i.e., only used to signal DL preemption).

[0153] In another example implementation of the second solution, when the UE 205 is configured / instructed to monitor the unified DCI 530 for DLPI and UL CI, the identifier CI-RNTI (i.e., for UL cancellation indication) is used to scramble the CRC of the new DCI 530, and the DCI size is the same as the size of DCI format 2_4 (i.e., only used to signal UL cancellation).

[0154] According to an embodiment of the third solution, a first time-frequency resource set is designated for DL ​​preemption, and a second time-frequency resource set is designated for UL CI.

[0155] Figure 6 An example scenario 600 of a unified DCI for DL ​​PI and UL CI respectively applicable to a single DL and ULTTI (time slot) according to an implementation of a third solution is shown. In scenario 600, a UE such as UE 205 receives DCI 605 in time slot N (e.g., in symbols 0 and 1 of time slot N), wherein DCI 605 schedules resources 615 for DL ​​transmission (e.g., PDSCH) in time slot N+1 and resources 620 for UL transmission (e.g., PUSCH) in time slot N+2. DCI 605 further schedules resources 625 for DL ​​transmission (e.g., PDSCH) in time slot N+4 and resources 630 for UL transmission (e.g., PUSCH) in time slot N+4. The received DCI 605 is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI containing both UL resource grants and DL resource grants. In other embodiments, the first signaling information may include separate DCIs that schedule the UL and DL respectively.

[0156] In addition, UE 205 also receives a new unified DCI format 610 for preemption and cancellation indication in time slot N (e.g., in symbols 12 and 13 of time slot N), which indicates to UE 205 both A) at least one grid 635 for time-frequency resources (i.e., the area indicated by DL PI) for DL ​​preemption and B) at least one additional grid 640 for time-frequency resources (i.e., the area indicated by UL PI) for UL cancellation.

[0157] In the depicted scenario 600, a first time-frequency resource set in the DCI 610 indicating preemption for DL ​​is used to determine a preemption region 635 for a single TTI instance only. Similarly, a second time-frequency resource set in the DCI 610 indicating cancellation for UL is used to determine a cancellation region 640 for a single TTI instance only. In the depicted embodiment, DL and UL are scheduled across multiple TTIs (slots), but the PI and CI are signaled only for one DL TTI and one UL TTI, respectively. Furthermore, while the indicated preemption region 635 is in slot N+1 and the indicated cancellation region 640 is in slot N+2, in other embodiments, the indicated preemption region 635 may be in slot N+3 and the indicated cancellation region 640 may be in slot N+4.

[0158] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning the entire time slot N+1, in other embodiments, scheduled / licensed DL resources may be used only for a portion of time slot N+1. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning the entire time slot N+2, in other embodiments, scheduled / licensed UL resources may be used only for a portion of time slot N+2.

[0159] Although in the above description, DL resources 615, 625 (PDSCH) and UL resources 620, 630 (PUSCH) are each dynamically licensed using DCI 605, in other embodiments, one or both of DL resources 615, 625 (PDSCH) and UL resources 620, 630 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the new DCI format 610 indicating the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0160] Figure 7An example 700 of a unified DCI for DL ​​PI and UL CI, according to an alternative implementation of a third solution, is shown. This DCI is applicable to multiple individual DLs and ULTTIs (time slots) (separate time-frequency region indications for each TTI of each DL and UL). In scenario 700, a UE such as UE 205 receives DCI 705 in time slot N (e.g., in symbols 0 and 1 of time slot N), where DCI 705 schedules resources 715 for DL ​​transmissions (e.g., PDSCH) in time slot N+1 and resources 720 for UL transmissions (e.g., PUSCH) in time slot N+2. DCI 705 further schedules resources 725 for DL ​​transmissions (e.g., PDSCH) in time slot N+4 and resources 730 for UL transmissions (e.g., PUSCH) in time slot N+4. The received DCI 705 is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource licenses and DL resource licenses. In other embodiments, the first signaling information may include separate DCIs that schedule UL and DL respectively.

[0161] In addition, UE 205 also receives a new unified DCI format 710 for preemption and cancellation indication in time slot N (e.g., in symbols 12 and 13 of time slot N), which indicates to UE 205 both A) at least one grid of the first time-frequency resource 735 (i.e., the area indicated by DL PI-1) and the second time-frequency resource 745 (i.e., the area indicated by DL PI-2) for DL ​​preemption and B) at least one additional grid of the first time-frequency resource 740 (i.e., the area indicated by UL PI-1) and the second time-frequency resource 750 (i.e., the area indicated by UL PI-2) for UL cancellation.

[0162] In the depicted scenario 700, a first set of time-frequency resources in a DCI 710, consisting of multiple time-frequency resources indicating preemption for DL, is used to determine preemption regions 735 and 745 for multiple TTI instances. Similarly, a second set of time-frequency resources in a DCI 710, consisting of multiple time-frequency resources indicating cancellation for UL, is used to determine cancellation regions 740 and 750. In this depicted embodiment, DL and UL are scheduled across multiple TTIs (time slots), and the PI and CI are signaled respectively for multiple DLTTIs and UL TTIs.

[0163] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning the entire time slot N+1, in other embodiments, scheduled / licensed DL resources may be used only for a portion of time slot N+1. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning the entire time slot N+2, in other embodiments, scheduled / licensed UL resources may be used only for a portion of time slot N+2.

[0164] Although in the above description, DL resources 715, 725 (PDSCH) and UL resources 720, 730 (PUSCH) are each dynamically licensed using DCI 705, in other embodiments, one or both of DL resources 715, 725 (PDSCH) and UL resources 720, 730 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the new DCI format 710 indicating the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0165] Figure 8 Example 800 of a unified DCI for DL ​​PI and ULCI, respectively applicable to multiple individual DL and UL TTIs (time slots) (with the same time-frequency region indication repeated for each TTI of each DL and UL), is shown according to another implementation of a third solution. In scenario 800, a UE such as UE 205 receives DCI 805 in time slot N (e.g., in symbols 0 and 1 of time slot N), wherein DCI 805 schedules resources 815 for DL ​​transmission (e.g., PDSCH) in time slot N+1 and resources 820 for UL transmission (e.g., PUSCH) in time slot N+2. DCI 805 further schedules resources 825 for DL ​​transmission (e.g., PDSCH) in time slot N+4 and resources 830 for UL transmission (e.g., PUSCH) in time slot N+4. The received DCI 805 is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource licenses and DL resource licenses. In other embodiments, the first signaling information may include separate DCIs that schedule UL and DL respectively.

[0166] Additionally, UE 205 also receives a new unified DCI format 810 for preemption and cancellation indication in time slot N (e.g., in symbols 12 and 13 of time slot N), which indicates to UE 205 both A) at least one grid of the first time-frequency resource 835 (i.e., the area indicated by DL PI-1) and the second time-frequency resource 845 (i.e., the area indicated by DL PI-2) for DL ​​preemption and B) at least one additional grid of the first time-frequency resource 840 (i.e., the area indicated by UL PI-1) and the second time-frequency resource 850 (i.e., the area indicated by UL PI-2) for UL cancellation.

[0167] In the depicted scenario 800, a first set of time-frequency resources in a DCI 810, consisting of a time-frequency resource indicating DL preemption, is used to determine a preemption region (e.g., region 835) for a TTI instance and a preemption region (e.g., region 845) for subsequent instances having the same time-frequency region as the first TTI instance. Similarly, a second set of time-frequency resources in a DCI 810, consisting of a time-frequency resource indicating UL cancellation, is used to determine a preemption region (e.g., region 840) for a TTI instance and a preemption region (e.g., region 850) for subsequent instances having the same time-frequency region as the first TTI instance.

[0168] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning the entire time slot N+1, in other embodiments, scheduled / licensed DL resources may be used only for a portion of time slot N+1. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning the entire time slot N+2, in other embodiments, scheduled / licensed UL resources may be used only for a portion of time slot N+2.

[0169] Although in the above description, DL resources 815, 825 (PDSCH) and UL resources 820, 830 (PUSCH) are each dynamically licensed using DCI 805, in other embodiments, one or both of DL resources 815, 825 (PDSCH) and UL resources 820, 830 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the new DCI format 810 indicating the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0170] Figure 9 Example 900 of a unified DCI for DL ​​PI and UL CI, according to a further implementation of the third solution, is shown. (DCI refers to a single time-frequency region spanning more than one TTI for each DL and UL, and is applicable to multiple individual DLs and UL TTIs (time slots).)

[0171] In scenario 900, a UE such as UE 205 receives DCI 905 in time slot N (e.g., in symbols 0 and 1 of time slot N), wherein DCI 905 schedules resources 915 for DL ​​transmission (e.g., PDSCH) in time slot N+1 and resources 920 for DL ​​transmission (e.g., PSSCH) in time slot N+2. DCI 905 also schedules resources 925 for UL transmission (e.g., PUSCH) in time slot N+4 and resources 930 for UL transmission (e.g., PUSCH) in time slot N+4. The received DCI 905 is an example of first signaling information sent from RAN node 210 that schedules communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource grants and DL resource grants. In other embodiments, the first signaling information may include separate DCIs that schedule UL and DL respectively.

[0172] Additionally, UE 205 also receives a new unified DCI format 910 for preemption and cancellation indication in time slot N (e.g., in symbols 12 and 13 of time slot N), which indicates to UE 205 both A) at least one grid of the first time-frequency resource 935 (i.e., the area indicated by DL PI-1) for DL ​​preemption and B) at least one additional grid of the first time-frequency resource 940 (i.e., the area indicated by ULPI-1) for UL cancellation.

[0173] In the depicted scenario 900, a first set of time-frequency resources in a DCI 910, consisting of a time-frequency resource indicated for DL ​​preemption, can span more than one TTI and can be used to determine a preemption region 935 across multiple TTIs (DL). Similarly, a second set of time-frequency resources in a DCI 910, consisting of a time-frequency resource indicated for UL cancellation, can span more than one TTI and can be used to determine a preemption region 940 across multiple TTIs (UL).

[0174] While the depicted embodiments illustrate a slot-based time-frequency resource grid, the described principles are also applicable to other intervals, such as subframes, microslots, time slots, or other transmission time intervals (“TTI”). Furthermore, although the depicted examples illustrate scheduled / licensed DL resources spanning the entire time slot N+1, in other embodiments, scheduled / licensed DL resources may be used only for a portion of time slot N+1. Similarly, although the depicted examples illustrate scheduled / licensed UL resources spanning the entire time slot N+2, in other embodiments, scheduled / licensed UL resources may be used only for a portion of time slot N+2.

[0175] Although in the above description, DL resources 915, 925 (PDSCH) and UL resources 920, 930 (PUSCH) are each dynamically licensed using DCI 905, in other embodiments, one or both of DL resources 915, 925 (PDSCH) and UL resources 920, 930 (PUSCH) may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Here, the same principle applies to both the new DCI format 910 indicating the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0176] According to an embodiment of the fourth solution, only one set of time-frequency resources is indicated, wherein a single time-frequency resource can indicate an area for both DL PI and / or UL CI. In an example implementation of this solution, the time-frequency resource indicates an area across two TTIs, wherein one TTI is scheduled with PDSCH and the other TTI is scheduled with PUSCH; therefore, the area in the PDSCH TTI can be determined for DL ​​PI, and the area in the PUSCH TTI can be determined for UL CI.

[0177] In one implementation of the fourth solution, for potential DL preemption and UL cancellation, UE 205 is configured with a single DCI field for each serving cell (if no SUL carrier is configured for the serving cell), wherein the single DCI field addresses a reference time-frequency region that includes at least one semi-statically configured DL symbol and at least one semi-statically configured UL symbol. UE 205 is also configured with two DCI fields for each serving cell (if an SUL carrier is configured for the serving cell), wherein one of the two DCI fields addresses a reference time-frequency region that includes at least one semi-statically configured DL symbol and at least one semi-statically configured UL symbol. For resources indicated from multiple reference time-frequency regions, UE 205 determines whether to apply UL cancellation (e.g., not transmitting scheduled PUSCH and SRS) or DL ​​preemption (i.e., assuming no transmission to UE 205) based on PDSCH / PUSCH scheduling information, semi-static UL / DL configuration, and PUSCH processing time.

[0178] In one example, UE 205 at least from the end of the T-wave period after UE 205 detects the end of the PDCCH reception of DCI format 2_x. proc,2 After +d, the UL cancellation is applied to PUSCH / SRS. proc,2 Corresponding to hypothesis d 2,1 =0 PUSCH processing capability 2, where μ is the minimum SCS configuration between PDCCH and PUSCH transmissions or SRS transmissions on the serving cell. UE205 does not expect T after the last symbol of CORESET in DCI format 2_x, where UE205 detects... proc,2 Cancel PUSCH or SRS transmission before the corresponding symbol.

[0179] In another implementation of the fourth solution, UE 205 flexibly determines the reference time region among symbols in the serving cell based on configuration parameters in the PCI configuration and / or dynamic indications in the DCI field of DCI format 2_x, wherein detected preemption and cancellation indications (“PCI”) apply. For example, in one configuration, all symbols in the reference time region are earlier than the first symbol in which a CORESET of DCI format 2_x is detected. In another configuration, [X] symbols in the reference time region are earlier than the first symbol in which a CORESET of DCI format 2_x is detected, and [NX] symbols in the reference time region are on or after the first symbol of the CORESET, where N is the number of symbols in the reference time region and can be indicated in the PCI configuration. In other configurations, the reference time region comprises at least two non-contiguous time windows. In one example, [Y] symbols in the reference time region are earlier than the first symbol in which a CORESET of DCI format 2_x is detected, and [NY] symbols in the reference time region are after the last symbol of the CORESET. The DCI field of DCI format 2_x indicates the selected configuration.

[0180] In one example, if PreemptionCancellation is provided to UE 205, UE 205 is configured with a preemption and cancellation indication (PCI)-RNTI provided by pci-RNTI to monitor the PDCCH conveying DCI format 2_x. UE 205 is also configured with the following:

[0181] • The serving cell set via pci-ConfigurationPerServingCell, which includes the serving cell index set provided by the corresponding servingCellId and the corresponding position set of fields in DCI format 2_x via positionInDCI.

[0182] • If the serving cell is configured with a SUL carrier, then the number of fields in the DCI format 2_x for each serving cell using the SUL carrier via positionInDCI-forSUL.

[0183] • Information on payload size via dci-PayloadSizeForPCI DCI format 2_x

[0184] • Indication of time-frequency resources via timeFrequencyRegion

[0185] For a serving cell that has the association field in DCI format 2_x, the field is represented by the following items:

[0186] ·NPCI The number of bits provided by pci-PayloadSize;

[0187] ·B PCI The number of PRBs provided by the frequencyRegionforPCI in the timeFquencyRegion;

[0188] ·T PCI The number of symbols provided by timeDurationforPCI in timeFrequencyRegion, excluding symbols used to receive SS / PBCH blocks; and

[0189] ·G PCI The T provided by timeGranularityforPCI in timeFrequencyRegion PCI The number of partitions for the symbol.

[0190] Here, from NP CI G bits PCI A set of bits and G PCI Each symbol group has a one-to-one mapping, where the first Each in the group includes One symbol, and the remaining Each in the group includes Symbols. UE 205 determines the symbol duration for the SCS configuration of the active DL BWP, wherein UE 205 monitors the PDCCH for DCI format 2_x detection.

[0191] For a symbol group, N from each bit set BI =N PCI / G pCI bits and N BI The group PRB has a one-to-one mapping, where the first Each in the group includes One PRB, and the remaining Each in the group includes One PRB. The UE receives the offset RB from the TS 38.214 instruction. start and length L RB As the frequencyRegionforCI of RIV, and the O from the SCS configuration indicating the active DL BWP carrier In the FrequencyInfoUL-SIB, offsetToCarrier determines the first PRB index as... And the number of consecutive RBs is determined as Among them, UE 205 monitors PDCCH for DCI format 2_4 detection.

[0192] Figure 10 An example of a PreemptionCancellation information element 1000 for configuring UE 205 to monitor PDCCH for PCI-RNTI is depicted. The following parameters used in the PreemptionCancellation information element 1000 are defined:

[0193] • pci-ConfigurationPerServingCell: Indicates the location of the pci-PayloadSize bit PCI value (per serving cell) within the DCI payload.

[0194] • pci-RNTI: RNTI used to indicate cancellation in UL and preemption in DL

[0195] ·dci-PayloadSizeForPCI: Total length of the DCI payload scrambled with PCI-RNTI.

[0196] • pci-PayloadSize: Configures (identified by the parameter servingCellId) the field size of each UL cancellation and DL preemption indicator for this serving cell.

[0197] • frequencyRegionForPCI: Configures the reference frequency region to which the detected PCI applies. It is defined in the same way as the locationAndBandwidth parameter.

[0198] • positionInDCI: The starting position (in bits) of the PCI-PayloadSize bit PCI value for the SUL of the serving cell within the DCI payload (identified by the parameter servingCellId).

[0199] • positionInDCI-ForSUL: The starting position (in bits) of the PCI value of the parameter pci-PayloadSize for the serving cell within the DCI payload (identified by the parameter servingCellId).

[0200] • timeDurationForPCI: Configures the duration for which the detected PCI applies to the reference time zone in the symbols of the serving cell (identified by the parameter servingCellId).

[0201] • timeWindowForPCI: Configures a list of time window positions relative to where a CORESET of DCI format 2_x is detected.

[0202] • timeFrequencyRegion: Configures the reference time and frequency region (identified by the servingCellId parameter) for which the detected PCI applies.

[0203] • timeGranularityForPCI: Configures (identified by the parameter servingCellId) the number of partitions in the time region of the serving cell.

[0204] According to an embodiment of the fifth solution, when multiple or a single UL transmission (i.e., TB) are scheduled in a continuous manner across multiple TTIs and the UE 205 is indicated for a time-frequency region for cancellation, the UL transmission is fully or partially cancelled only for TTIs that have at least partial overlap with the indicated time-frequency region for cancellation.

[0205] Figure 11 An example of a cancellation mechanism for UL transmissions only on TTIs (e.g., time slots) that at least partially overlap with the indicated time-frequency region, according to one implementation of the fifth solution, is shown. In scenario 1100, UE 205 receives DCI 1105 in time slot N (e.g., in symbols 0 and 1 of time slot N), where DCI 1105 schedules resources 1115 for UL transmissions (e.g., PUSCH) in time slot N+1 and resources 1120 for UL transmissions (e.g., PUSCH) in time slot N+2. The received DCI is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource grants and DL resource grants. In other embodiments, the first signaling information includes two separate DCIs that schedule UL and DL respectively.

[0206] Furthermore, UE 205 also receives a new unified DCI format 1110 in time slot N (e.g., in symbols 12 and 13 of time slot N) for preemption and cancellation indication, which indicates to UE 205 at least one grid 1125 of time-frequency resources (i.e., the area indicated by the UL PI) for UL cancellation. In the depicted example, when multiple or single UL transmissions (TBs) are scheduled in a continuous manner across multiple TTIs and UE 205 is indicated with a time-frequency area for cancellation, the UL transmission is partially cancelled only for TTIs that have at least partial overlap with the time-frequency area indicated for cancellation. Therefore, the remaining UL resources 1130 in time slot N+1 are cancelled.

[0207] Although UL resources 1115 and 1120 (PUSCH) are each dynamically licensed using DCI 1105 in the description above, in other embodiments, one or both of UL resources 1115 and 1120 may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Furthermore, the new unified DCI format 1110 can be used to indicate both the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0208] Figure 12 An example of a cancellation mechanism for UL transmissions on all TTIs (e.g., time slots) including a TTI that at least partially overlaps with the indicated time-frequency region, according to an alternative embodiment of the fifth solution, is illustrated. In scenario 1200, UE 205 receives DCI 1205 in time slot N (e.g., in symbols 0 and 1 of time slot N), wherein DCI 1205 schedules resource 1215 for UL transmissions (e.g., PUSCH) in time slot N+1 and resource 1220 for UL transmissions (e.g., PUSCH) in time slot N+2. The received DCI is an example of first signaling information sent from RAN node 210 that schedules the communication resources. In the depicted embodiment, the first signaling information is a single unified DCI that includes both UL resource grants and DL resource grants. In other embodiments, the first signaling information includes two separate DCIs that schedule UL and DL respectively.

[0209] Additionally, UE 205 also receives a new unified DCI format 1210 in time slot N (e.g., in symbols 12 and 13 of time slot N) for preemption and cancellation indication, which indicates to UE 205 at least one grid 1225 of time-frequency resources (i.e., the area indicated by the UL PI) for UL cancellation. In the depicted example, when multiple or single UL transmissions (TBs) are scheduled in a continuous manner across multiple TTIs and UE 205 is indicated with a time-frequency area for cancellation, all UL transmissions after a TTI that at least partially overlaps with the indicated time-frequency area for cancellation and in all TTIs including that TTI are cancelled. Therefore, the remaining UL resources 1230 in time slot N+1 are cancelled.

[0210] Although UL resources 1215 and 1220 (PUSCH) are each dynamically licensed using DCI 1205 in the description above, in other embodiments, one or both of UL resources 1215 and 1220 may be configured licenses (i.e., semi-static / semi-persistently scheduled resources). Furthermore, the new unified DCI format 1210 can be used to indicate both the cancellation of a scheduled UL resource and the preemption of a scheduled DL resource.

[0211] Regarding the determination of the grid for time-frequency resources used for UL CI and / or DL ​​PI, for the serving cell, UE 205 may determine that the first symbol for the time region used for UL CI is a first symbol following a first offset from which UE 205 detects the end of PDCCH reception for the unified DCI format used for UL CI and DL PI. In another example, UE 205 determines that the first symbol for the time region used for UL CI is a second symbol following a second offset from which UE 205 detects the end of PDCCH reception for DCI format 2_4. In this example, the first offset is different from the second offset. In this example, the first offset is determined based on the second offset (e.g., the first offset is the second offset plus an additional symbol). In this example, the first offset and / or the second offset are different from the offsets determined for UL CI operation in 3GPP Release 16.

[0212] According to an embodiment of the sixth solution, the new unified DCI format for UL CI and DL PI may be applicable only to certain spatial filters, beams, and / or UE panels.

[0213] In one embodiment of the sixth solution, one or more TCI states containing information about the UE's transmit spatial filter / beam / panel can be associated with the UL CI in DCI format 2_4, which notifies the UE group that the UL CI is only applicable to a subset of UEs with the indicated TCI state. In one implementation of the sixth solution, a UE receiving the UL CI based on a configured RNTI further checks the TCI state field associated with the UL CI and does not transmit the UL using the indicated TCI state. In another implementation of the sixth solution, a UE receiving the UL CI based on a configured RNTI further checks the TCI state field associated with the UL CI and does not transmit the UL using the indicated TCI state, while reducing uplink transmit power to transmit the UL using a TCI state not indicated in the UL CI.

[0214] In another embodiment of the sixth solution, one or more TCI states containing information about the UE's received spatial filter / beam / panel can be associated with a DL PI in DCI format 2_1, which only notifies the UE of the DL PI to a subset of UEs having the indicated TCI state. In one implementation of the sixth solution, a UE receiving a DL PI based on a configured RNTI further checks the TCI state field associated with the DL PI to clear the soft buffer.

[0215] In another embodiment of the sixth solution, one or more TCI states, including spatial filters / beams / panels, can be associated with DLPI and ULCI respectively using separate fields or a common field indicating the TCI states for both DLPI and ULCI. The RNTI, based on its configuration, receives a UE in a unified DCI format indicating DLPI and ULCI, which further examines the TCI state fields and performs one or more actions according to the sixth solution.

[0216] Figure 13 User equipment device 1300, which can be used for unified signaling of DL PI and UL CI according to embodiments of the present disclosure, is depicted. In various embodiments, user equipment device 1300 is used to implement one or more of the solutions described above. User equipment device 1300 may be an embodiment of the remote unit 105 and / or UE 205 described above. In addition, user equipment device 1300 may include processor 1305, memory 1310, input device 1315, output device 1320, and transceiver 1325.

[0217] In some embodiments, input device 1315 and output device 1320 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 1300 may not include any input device 1315 and / or output device 1320. In various embodiments, user equipment device 1300 may include one or more of the following: processor 1305, memory 1310, and transceiver 1325, and may not include input device 1315 and / or output device 1320.

[0218] As depicted, transceiver 1325 includes at least one transmitter 1330 and at least one receiver 1335. In some embodiments, transceiver 1325 communicates with one or more cells (or radio coverage areas) supported by one or more basic units 121. In various embodiments, transceiver 1325 may operate on unlicensed spectrum. Furthermore, transceiver 1325 may include multiple UE panels supporting one or more beams. Additionally, transceiver 1325 may support at least one network interface 1340 and / or application interface 1345. Application interface 1345 may support one or more APIs. Network interface 1340 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 1340 may be supported, as understood by those skilled in the art.

[0219] In one embodiment, processor 1305 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1305 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 1305 executes instructions stored in memory 1310 to perform the methods and routines described herein. Processor 1305 is communicatively coupled to memory 1310, input device 1315, output device 1320, and transceiver 1325.

[0220] In various embodiments, processor 1305 controls user equipment device 1300 to perform the UE behaviors described above. In some embodiments, processor 1305 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0221] In various embodiments, processor 1305 controls transceiver 1325 to receive first signaling information from RAN equipment for scheduling first communication resources. After receiving the first signaling information, transceiver 1325 further receives second signaling information (i.e., unified GC-DCI). Here, processor 1305 determines, based on the second signaling information, the unavailability of at least one set of uplink resources and at least one set of downlink resources on the scheduled first communication resources.

[0222] In some embodiments, receiving first signaling information includes receiving first scheduling information (e.g., CG or DCI) for scheduling a first uplink resource and receiving second scheduling information (e.g., CG or DCI) for scheduling a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission to configure (i.e., a semi-persistent resource).

[0223] In some embodiments, the second signaling information is transmitted via a group common unified DCI format. In such embodiments, at least one set of uplink resource unavailability indications may include uplink cancellation indications and at least one set of downlink resource unavailability indications may include downlink preemption indications. In some embodiments, the second signaling information is received on the PDCCH.

[0224] In some embodiments, processor 1305 monitors group common unified DCI in response to an uplink subcarrier spacing to downlink subcarrier spacing ratio being below a threshold. In some embodiments, processor 1305 monitors group common unified DCI in response to a subcarrier spacing associated with PDCCH being above a threshold (e.g., monitoring unified DCI for UL CI and DLPI when using high SCS).

[0225] In some embodiments, the processor 1305 suspends monitoring of specific signaling information in response to determining a common unified DCI for the monitoring group. Here, the specific signaling information may be signaling information indicating uplink cancellation transmitted via a DCI format (e.g., DCI format 2_4) and / or signaling information indicating downlink preemption transmitted via a DCI format (e.g., DCI format 2_1).

[0226] In some embodiments, the processor 1305 further controls the transceiver 1325 to communicate with the RAN using the remaining portion of the first communication resources, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0227] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0228] In some embodiments, transceiver 1325 further receives RRC configuration. In such embodiments, at least one set of uplink resource unavailability time zones can be determined based on the RRC configuration. In some embodiments, transceiver 1325 further receives RRC configuration. In such embodiments, at least one set of downlink resource unavailability time zones can be determined based on the RRC configuration.

[0229] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0230] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0231] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0232] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0233] In one embodiment, memory 1310 is a computer-readable storage medium. In some embodiments, memory 1310 includes volatile computer storage media. For example, memory 1310 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1310 includes non-volatile computer storage media. For example, memory 1310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1310 includes both volatile and non-volatile computer storage media.

[0234] In some embodiments, memory 1310 stores data related to unified signaling for DL ​​PI and UL CI. For example, memory 1310 may store various parameters, panel / beam configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 1310 also stores program code and related data, such as an operating system or other controller algorithms running on device 1300.

[0235] In one embodiment, input device 1315 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 1315 may be integrated with output device 1320, such as as a touchscreen or similar touch-sensitive display. In some embodiments, input device 1315 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 1315 includes two or more different devices, such as a keyboard and a touch panel.

[0236] In one embodiment, output device 1320 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 1320 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 1320 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic LED (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 1320 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc., that is separate from but communicatively coupled to the rest of user equipment device 1300. Furthermore, output device 1320 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0237] In some embodiments, output device 1320 includes one or more speakers for generating sound. For example, output device 1320 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 1320 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 1320 may be integrated with input device 1315. For example, input device 1315 and output device 1320 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 1320 may be located near input device 1315.

[0238] Transceiver 1325 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 1325 operates under the control of processor 1305 to transmit and receive messages, data, and other signals. For example, processor 1305 may selectively activate transceiver 1325 (or a portion thereof) at specific times to send and receive messages.

[0239] Transceiver 1325 includes at least a transmitter 1330 and at least one receiver 1335. One or more transmitters 1330 can be used to provide UL communication signals to base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 1335 can be used to receive DL communication signals from base unit 121, as described herein. Although only one transmitter 1330 and one receiver 1335 are illustrated, user equipment device 1300 can have any suitable number of transmitters 1330 and receivers 1335. Furthermore, transmitters 1330 and receivers 1335 can be of any suitable type. In one embodiment, transceiver 1325 includes a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum.

[0240] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 1325, transmitters 1330, and receivers 1335 may be implemented as physically separate components accessing shared hardware resources and / or software resources (such as, for example, network interface 1340).

[0241] In various embodiments, one or more transmitters 1330 and / or one or more receivers 1335 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other type of hardware component. In some embodiments, one or more transmitters 1330 and / or one or more receivers 1335 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 1340 or other hardware components / circuits, may be integrated with any number of transmitters 1330 and / or receivers 1335 into a single chip. In such embodiments, transmitters 1330 and receivers 1335 may be logically configured as transceivers 1325 using one or more common control signals, or configured as modular transmitters 1330 and receivers 1335 implemented in the same hardware chip or in a multi-chip module.

[0242] Figure 14A network device 1400 for unified signaling of DL PI and UL CI is depicted according to embodiments of the present disclosure. In one embodiment, the network device 1400 may be an implementation of a RAN node, such as base unit 121 and / or RAN node 210, as described above. Furthermore, the base network device 1400 may include a processor 1405, a memory 1410, an input device 1415, an output device 1420, and a transceiver 1425.

[0243] In some embodiments, input device 1415 and output device 1420 are combined into a single device, such as a touchscreen. In some embodiments, network device 1400 may not include any input device 1415 and / or output device 1420. In various embodiments, network device 1400 may include one or more of the following: processor 1405, memory 1410, and transceiver 1425, and may not include input device 1415 and / or output device 1420.

[0244] As depicted, transceiver 1425 includes at least one transmitter 1430 and at least one receiver 1435. Here, transceiver 1425 communicates with one or more remote units 145. Furthermore, transceiver 1425 may support at least one network interface 1440 and / or application interface 1445. Application interface 1445 may support one or more APIs. Network interface 1440 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 1440 may be supported, as will be understood by those skilled in the art.

[0245] In one embodiment, processor 1405 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1405 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 1405 executes instructions stored in memory 1410 to perform the methods and routines described herein. Processor 1405 is communicatively coupled to memory 1410, input device 1415, output device 1420, and transceiver 1425.

[0246] In various embodiments, network device 1400 is a RAN node (e.g., gNB) communicating with one or more UEs, as described herein. In such embodiments, processor 1405 controls network device 1400 to perform the RAN behaviors described above. When operating as a RAN node, processor 1405 may include an application processor (also referred to as the "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as the "baseband radio processor") that manages radio functions.

[0247] In various embodiments, processor 1405 controls transceiver 1425 to transmit first signaling information to the UE, scheduling first communication resources. At some point after transmitting the first signaling information, processor 1405 determines, based on second signaling information, the unavailability of at least one set of uplink resources and at least one set of downlink resources on the scheduled first communication resources. In response, processor 1405 controls transceiver 1425 to transmit second signaling information (i.e., unified GC-DCI) to the UE. Here, the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources.

[0248] In some embodiments, transmitting first signaling information includes transmitting first scheduling information (e.g., CG or DCI) for a first uplink resource and transmitting second scheduling information (e.g., DCI) for a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission for the configuration of a semi-persistent resource.

[0249] In some embodiments, the second signaling information is transmitted via a group common unified DCI format. In such embodiments, the unavailability indication of at least one set of uplink resources may include an uplink cancellation indication and the unavailability indication of at least one set of downlink resources may include a downlink preemption indication. In some embodiments, the second signaling information is received on the PDCCH. In some embodiments, the processor 1405 further communicates with the UE using the remainder of the first communication resources, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0250] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0251] In some embodiments, transceiver 1425 further transmits RRC configuration. In such embodiments, at least one set of uplink resource unavailability time zones can be determined based on the RRC configuration. In some embodiments, transceiver 1425 further transmits RRC configuration. In such embodiments, at least one set of downlink resource unavailability time zones can be determined based on the RRC configuration.

[0252] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0253] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0254] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0255] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0256] In one embodiment, memory 1410 is a computer-readable storage medium. In some embodiments, memory 1410 includes volatile computer storage media. For example, memory 1410 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1410 includes non-volatile computer storage media. For example, memory 1410 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1410 includes both volatile and non-volatile computer storage media.

[0257] In some embodiments, memory 1410 stores data related to unified signaling for DL ​​PI and UL CI. For example, memory 1410 may store parameters, configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 1410 also stores program code and related data, such as an operating system or other controller algorithms running on device 1400.

[0258] In one embodiment, input device 1415 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, input device 1415 may be integrated with output device 1420, such as as a touchscreen or similar touch-sensitive display. In some embodiments, input device 1415 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 1415 includes two or more different devices, such as a keyboard and a touch panel.

[0259] In one embodiment, output device 1420 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 1420 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 1420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 1420 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc., that is separate from but communicatively coupled to the rest of network device 1400. Furthermore, output device 1420 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0260] In some embodiments, output device 1420 includes one or more speakers for generating sound. For example, output device 1420 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 1420 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 1420 may be integrated with input device 1415. For example, input device 1415 and output device 1420 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 1420 may be located near input device 1415.

[0261] Transceiver 1425 includes at least a transmitter 1430 and at least one receiver 1435. One or more transmitters 1430 can be used to communicate with a UE, as described herein. Similarly, one or more receivers 1435 can be used to communicate with network functions in a PLMN and / or RAN, as described herein. Although only one transmitter 1430 and one receiver 1435 are shown, network device 1400 can have any suitable number of transmitters 1430 and receivers 1435. Furthermore, transmitters 1430 and receivers 1435 can be of any suitable type.

[0262] Figure 15 An embodiment of a method 1500 for unified signaling for DL ​​PI and UL CI according to embodiments of the present disclosure is described. In various embodiments, method 1500 is performed by a user equipment device in a mobile communication network, such as the remote unit 105, UE 205, and / or user equipment device 1300 described above. In some embodiments, method 1500 is performed by a processor such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0263] Method 1500 begins by receiving, 1505, first signaling information from a radio access network (“RAN”) device to schedule a first communication resource. Method 1500 includes receiving, after receiving the first signaling information, second signaling information 1510, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resource. Method 1500 ends.

[0264] Figure 16An embodiment of a method 1600 for unified signaling for DL ​​PI and UL CI according to embodiments of the present disclosure is described. In various embodiments, method 1600 is performed by a radio access network device such as the basic unit 121 described above, RAN node 210, and / or network device 1400. In some embodiments, method 1600 is performed by a processor such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0265] Method 1600 begins by transmitting first signaling information (1605) to the UE to schedule a first communication resource. Method 1600 includes transmitting second signaling information (1610) to the UE after transmitting the first signaling information, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resource. Method 1600 ends.

[0266] This document discloses a first apparatus for unified signaling for DL ​​PI and UL CI according to embodiments of the present disclosure. The first apparatus may be implemented by a user equipment apparatus in a mobile communication network, such as the aforementioned remote unit 105, UE 205, and / or user equipment apparatus 1300. The first apparatus includes a processor and a transceiver that receives first signaling information from a RAN device to schedule first communication resources and receives second signaling information (i.e., unified GC-DCI) after receiving the first signaling information. Here, the processor determines, based on the second signaling information, the unavailability of at least one set of uplink resources and at least one set of downlink resources on the scheduled first communication resources.

[0267] In some embodiments, receiving first signaling information includes receiving first scheduling information (e.g., CG or DCI) for scheduling a first uplink resource and receiving second scheduling information (e.g., CG or DCI) for scheduling a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission to configure (i.e., a semi-persistent resource).

[0268] In some embodiments, the second signaling information is transmitted via a group common unified DCI format. In such embodiments, at least one set of uplink resource unavailability indications may include uplink cancellation indications and at least one set of downlink resource unavailability indications may include downlink preemption indications. In some embodiments, the second signaling information is received on the PDCCH.

[0269] In some embodiments, the processor monitors the group common unified DCI in response to an uplink subcarrier spacing to downlink subcarrier spacing ratio falling below a threshold. In some embodiments, the processor monitors the group common unified DCI in response to a subcarrier spacing associated with the PDCCH exceeding a threshold (e.g., monitoring the unified DCI for UL CI and DL PI when utilizing high SCS).

[0270] In some embodiments, the processor suspends monitoring of specific signaling information in response to determining a common unified DCI for the monitoring group. Here, the specific signaling information may be signaling information indicating uplink cancellation transmitted via a DCI format (e.g., DCI format 2_4) and / or signaling information indicating downlink preemption transmitted via a DCI format (e.g., DCI format 2_1).

[0271] In some embodiments, the processor further uses the remainder of the first communication resources to communicate with the RAN, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0272] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0273] In some embodiments, the transceiver further receives an RRC configuration. In such embodiments, at least one set of uplink resource unavailability time zones can be determined based on the RRC configuration. In some embodiments, the transceiver further receives an RRC configuration. In such embodiments, at least one set of downlink resource unavailability time zones can be determined based on the RRC configuration.

[0274] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0275] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0276] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0277] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0278] This document discloses a first method for unified signaling for DL ​​PI and UL CI according to embodiments of this disclosure. The first method can be performed by a user equipment device in a mobile communication network, such as the remote unit 105, UE 205, and / or user equipment device 1300 described above. The first method includes receiving first signaling information from a RAN device to schedule first communication resources and receiving second signaling information after receiving the first signaling information, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resources.

[0279] In some embodiments, receiving first signaling information includes receiving first scheduling information (e.g., CG or DCI) for scheduling a first uplink resource and receiving second scheduling information (e.g., CG or DCI) for scheduling a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission for the configuration of a semi-persistent resource.

[0280] In some embodiments, the second signaling information is transmitted via a group common unified DCI format. In such embodiments, at least one set of uplink resource unavailability indications may include uplink cancellation indications and at least one set of downlink resource unavailability indications may include downlink preemption indications. In some embodiments, the second signaling information is received on the PDCCH.

[0281] In some embodiments, the first method includes monitoring the group common unified DCI in response to an uplink subcarrier spacing to downlink subcarrier spacing ratio falling below a threshold. In some embodiments, the first method includes monitoring the group common unified DCI in response to a subcarrier spacing associated with the PDCCH exceeding a threshold (e.g., monitoring the unified DCI for UL CI and DL PI when utilizing a high SCS).

[0282] In some embodiments, the first method includes suspending monitoring of specific signaling information in response to determining a common unified DCI for the monitoring group. Here, the specific signaling information may be signaling information indicating uplink cancellation transmitted via a DCI format (e.g., DCI format 2_4) and / or signaling information indicating downlink preemption transmitted via a DCI format (e.g., DCI format 2_1).

[0283] In some embodiments, the first method further includes communicating with the RAN using the remainder of the first communication resources, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0284] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0285] In some embodiments, the first method includes receiving an RRC configuration. In such embodiments, at least one set of time zones where uplink resources are unavailable can be determined based on the RRC configuration. In some embodiments, the first method includes receiving an RRC configuration. In such embodiments, at least one set of time zones where downlink resources are unavailable can be determined based on the RRC configuration.

[0286] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0287] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0288] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0289] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0290] This document discloses a second apparatus for unified signaling for DL ​​PI and UL CI according to embodiments of this disclosure. The second apparatus can be implemented by a RAN node in a mobile communication network, such as the aforementioned basic unit 121, RAN node 210, and / or network device 1400. The second apparatus includes a transceiver and a processor. The transceiver transmits first signaling information to the UE to schedule first communication resources. After transmitting the first signaling information, the processor determines, based on second signaling information, the unavailability of at least one set of uplink resources and at least one set of downlink resources on the scheduled first communication resources. The transceiver transmits second signaling information (i.e., unified GC-DCI) to the UE. Here, the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources.

[0291] In some embodiments, transmitting first signaling information includes transmitting first scheduling information (e.g., CG or DCI) for a first uplink resource and transmitting second scheduling information (e.g., DCI) for a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission for the configuration of a semi-persistent resource.

[0292] In some embodiments, the second signaling information is transmitted via a group common unified DCI format. In such embodiments, the unavailability indication of at least one set of uplink resources may include an uplink cancellation indication and the unavailability indication of at least one set of downlink resources may include a downlink preemption indication. In some embodiments, the second signaling information is received on the PDCCH. In some embodiments, the processor further communicates with the UE using the remainder of the first communication resources, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0293] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0294] In some embodiments, the transceiver further transmits RRC configuration. In such embodiments, at least one set of uplink resource unavailability time zones can be determined based on the RRC configuration. In some embodiments, the transceiver further transmits RRC configuration. In such embodiments, at least one set of downlink resource unavailability time zones can be determined based on the RRC configuration.

[0295] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0296] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0297] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0298] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0299] This document discloses a second method for unified signaling for DL ​​PI and UL CI according to embodiments of this disclosure. The second method can be performed by a RAN node in a mobile communication network, such as the aforementioned basic unit 121, RAN node 210, and / or network device 1400. The second method includes transmitting first signaling information to a UE to schedule first communication resources and transmitting second signaling information to the UE after transmitting the first signaling information, wherein the second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the scheduled first communication resources.

[0300] In some embodiments, transmitting first signaling information includes transmitting first scheduling information (e.g., CG or DCI) for a first uplink resource and transmitting second scheduling information (e.g., CG or DCI) for a first downlink resource. In such embodiments, the second signaling information indicates both the unavailability of at least a portion of the first uplink resource and the unavailability of at least a portion of the first downlink resource. In one embodiment, both the first and second scheduling information are included in the same DCI, for example, using a uniform scheduling DCI format. In another embodiment, the first and second scheduling information are included in separate DCIs. In some embodiments, at least one of the first and second scheduling information is a permission for the configuration of a semi-persistent resource.

[0301] In some embodiments, second signaling information is transmitted via a group common unified DCI format. In such embodiments, the unavailability indication of at least one set of uplink resources may include an uplink cancellation indication and the unavailability indication of at least one set of downlink resources may include a downlink preemption indication. In some embodiments, the second signaling information is received on the PDCCH. In some embodiments, the second method includes communicating with the UE using the remainder of the first communication resources, wherein the first communication resources do not include at least one set of uplink resources and at least one set of downlink resources.

[0302] In some embodiments, at least one set of uplink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information. In some embodiments, at least one set of downlink resource unavailability time zones are determined based on monitoring periodicity associated with second signaling information.

[0303] In some embodiments, the second method includes transmitting an RRC configuration. In such embodiments, at least one set of time zones where uplink resources are unavailable can be determined based on the RRC configuration. In some embodiments, the second method includes transmitting an RRC configuration. In such embodiments, at least one set of time zones where downlink resources are unavailable can be determined based on the RRC configuration.

[0304] In some embodiments, at least one of the following is used to define at least one set of uplink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0305] In some embodiments, at least one of the following is used to define at least one set of downlink resource unavailability time zones: the time of receiving second signaling information, communication resources for monitoring second signaling information, the monitoring timing when second signaling information is received, and a set of control resources containing second signaling information (i.e., and possibly additional time offset).

[0306] In some embodiments, the second signaling information indicates a first time-frequency resource set where at least one set of uplink resources is unavailable, and additionally (i.e., separately) indicates a second time-frequency resource set where at least one set of downlink resources is unavailable. In other embodiments, the second signaling information indicates a first time-frequency resource set corresponding to both at least one set of uplink resources and at least one set of downlink resources.

[0307] In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of uplink resources. In such embodiments, the at least one set of uplink resources is unavailable only for the associated TCI state. In some embodiments, the second signaling information includes at least one TCI state, which contains information about spatial filters associated with at least one set of downlink resources. In such embodiments, the at least one set of downlink resources is unavailable only for the associated TCI state.

[0308] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims should be covered within their scope.

Claims

1. A user equipment ("UE"), comprising: At least one memory; At least one processor, coupled to the at least one memory, and configured to cause the UE to: Receive first signaling information from the base station to schedule first communication resources; and In response to at least one of the following, monitor the Physical Downlink Control Channel ("PDCCH") used for second signaling information: The ratio between the uplink subcarrier spacing and the downlink subcarrier spacing meets a first threshold; or The subcarrier spacing associated with the PDCCH satisfies the second threshold. The second signaling information is transmitted in the Group Common Unified Downlink Control Information ("DCI") format; Based on monitoring the PDCCH to receive the second signaling information; as well as Based on the second signaling information, at least one set of uplink resources and at least one set of downlink resources on the first communication resource are determined to be unavailable.

2. The UE according to claim 1, wherein, The unavailability indication associated with the at least one set of uplink resources includes an uplink cancellation indication, wherein the unavailability indication associated with the at least one set of downlink resources includes a downlink preemption indication.

3. The UE according to claim 1, wherein, The at least one processor is configured to cause the UE to communicate with the base station using the remaining portion of the first communication resources, wherein the remaining portion of the first communication resources does not include communication resources in a Transmission Time Interval (TTI) that at least partially overlaps with the at least one set of uplink resources and the at least one set of downlink resources.

4. The UE according to claim 1, wherein, The at least one processor is configured to cause the UE to communicate with the base station using the remaining portion of the first communication resources, wherein the remaining portion of the first communication resources does not include communication resources in the following transmission time intervals (TTIs): after a TTI that has at least partial overlap with the at least one set of uplink resources and the at least one set of downlink resources, and in the TTI that includes that TTI.

5. The UE according to claim 1, wherein, The time zones in which the at least one set of uplink resources are unavailable are determined based on the monitoring periodicity associated with the second signaling information.

6. The UE according to claim 1, wherein, The at least one processor is configured to cause the UE to receive a Radio Resource Control ("RRC") configuration, wherein the time zones in which the at least one set of uplink resources are unavailable are determined according to the RRC configuration.

7. The UE according to claim 1, wherein, Use at least one of the following to define the time zones where the at least one set of uplink resources are unavailable: The time of receiving the second signaling information, Second communication resources used to monitor the second signaling information The timing of monitoring when the second signaling information is received, and A control resource set containing the second signaling information.

8. The UE according to claim 1, wherein, The second signaling information indicates a first time-frequency resource set in which the at least one set of uplink resources is unavailable, wherein the second signaling information further indicates a second time-frequency resource set in which the at least one set of downlink resources is unavailable.

9. The UE according to claim 1, wherein, The second signaling information indicates a first time-frequency resource set corresponding to both the at least one set of uplink resources and the at least one set of downlink resources.

10. The UE according to claim 1, wherein, The second signaling information includes at least one Transport Configuration Indicator ("TCI") state containing information about spatial filters associated with the at least one set of uplink resources, wherein the at least one set of uplink resources is unavailable only for the associated TCI state.

11. The UE according to claim 1, wherein, The second signaling information includes at least one Transport Configuration Indicator ("TCI") state containing information about spatial filters associated with the at least one set of downlink resources, wherein the at least one set of downlink resources is unavailable only for the associated TCI state.

12. The UE according to claim 1, wherein, The at least one processor is configured to cause the UE to: suspend monitoring of specific signaling information in response to determining a common unified DCI for the monitoring group, wherein the specific signaling information includes at least one of the following: signaling information indicating uplink cancellation transmitted via DCI format and signaling information indicating downlink preemption transmitted via DCI format.

13. A method performed by a user equipment ("UE"), the method comprising: Receive first signaling information from the base station to schedule first communication resources; as well as In response to at least one of the following, monitor the Physical Downlink Control Channel ("PDCCH") used for second signaling information: The ratio between the uplink subcarrier spacing and the downlink subcarrier spacing meets a first threshold; or The subcarrier spacing associated with the PDCCH satisfies the second threshold. The second signaling information is transmitted in the Group Common Unified Downlink Control Information ("DCI") format; After receiving the first signaling information, the second signaling information is received; Based on the second signaling information, at least one set of uplink resources and at least one set of downlink resources on the first communication resource are determined to be unavailable.

14. A base station, comprising: At least one memory; At least one processor, coupled to the at least one memory, and configured to cause the base station to: Transmit first signaling information to the user equipment ("UE") to schedule first communication resources; and In response to at least one of the following, a second signaling message is transmitted on the Physical Downlink Control Channel ("PDCCH"): The ratio between the uplink subcarrier spacing and the downlink subcarrier spacing meets a first threshold; or The subcarrier spacing associated with the PDCCH satisfies the second threshold. The second signaling information is transmitted in the Group Common Unified Downlink Control Information ("DCI") format. The second signaling information indicates both the unavailability of at least one set of uplink resources and the unavailability of at least one set of downlink resources on the first communication resource.

15. The base station according to claim 14, wherein, The second signaling information includes at least one Transport Configuration Indicator ("TCI") state containing information about spatial filters associated with the at least one set of uplink resources, wherein the at least one set of uplink resources is unavailable only for the associated TCI state.

16. The base station according to claim 14, wherein, The second signaling information includes at least one Transport Configuration Indicator ("TCI") state containing information about spatial filters associated with the at least one set of downlink resources, wherein the at least one set of downlink resources is unavailable only for the associated TCI state.

17. The base station according to claim 14, wherein, The unavailability indication associated with the at least one set of uplink resources includes an uplink cancellation indication, wherein the unavailability indication associated with the at least one set of downlink resources includes a downlink preemption indication.

18. The base station according to claim 14, wherein, The second signaling information indicates a first time-frequency resource set in which the at least one set of uplink resources is unavailable, wherein the second signaling information further indicates a second time-frequency resource set in which the at least one set of downlink resources is unavailable.

19. The base station according to claim 14, wherein, The second signaling information indicates a first time-frequency resource set corresponding to both the at least one set of uplink resources and the at least one set of downlink resources.

Images