Architecture for signaling response coordination

Abstract

A user equipment (UE) may communicate with a base station (e.g., gNodeB) via multiple transmit-receive points. The base station may send multiple redundant or partially redundant DCIs (downlink channel information). Redundant DCIs may trigger redundant signaling responses. The UE may access predetermined content within the DCI to determine coordination of responses, thereby avoiding signaling response redundancy.

Description

Technical Field

[0001] The present disclosure relates to an architecture for downlink channel information signaling response coordination. Background Art

[0002] Wireless communication technology is moving towards rapidly increasing network connectivity. High-speed and low-latency wireless communication relies on effective network resource management and allocation between user mobile stations and radio access network nodes (including but not limited to radio base stations). Unlike traditional circuit-switched networks, effective radio access networks may not rely on dedicated user channels. Instead, wireless network resources (such as carrier frequencies and transmission time slots) for sending voice or other types of data from mobile stations to radio access network nodes may be allocated using information sent on the channel itself. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1 An example base station is shown.

[0004] Figure 2 An example communication environment is shown.

[0005] Figure 3 An example multiple transmit-receive point (TRP) environment is shown.

[0006] Figure 4 A second example multi-TRP environment is shown.

[0007] Figure 5 Example coordination logic is shown.

[0008] Figure 6 Example scheduling logic is shown. DETAILED DESCRIPTION

[0009] In various telecommunication systems, multiple transmit-receive points (TRPs) may communicate with a single user equipment (UE). Multiple downlink channel information (DCI) may be used to signal a physical downlink control channel. Therefore, if the transmission of one DCI is blocked, other DCIs in the multiple DCIs may be received and the scheduling of signaling may be allowed. In other words, multiple DCIs may be used to trigger the same signal. In some cases, different redundant DCIs may be sent via different TRPs. Therefore, if the UE has unblocked transmissions from any one (or more) of the multiple different TRPs, the UE may successfully receive the relevant DCI. This may provide a technical solution to the technical problem of improving the reliability of the physical downlink control channel (PDCCH).

[0010] In some implementations, predetermined content of multiple DCIs may be used to coordinate a signaling set in response to multiple (and in some cases redundant) DCIs. For example, the predetermined content may be used to indicate a timing offset that has a corresponding relationship with the DCI in which the predetermined content is received. Thus, each of the different DCIs may have a corresponding timing offset so that responses to each of the multiple DCIs may be coordinated (e.g., scheduled) in time. For example, to avoid redundant response signaling, the same (or additionally redundant) response signaling triggered by multiple DCIs may be coordinated so that each of the redundant responses is scheduled for transmission in the same time unit. Thus, the redundant response may be sent once, rather than once for each of the multiple DCI triggers.

[0011] In some implementations, the predetermined content may satisfy a similarity condition that the UE may identify.When the similarity condition is satisfied between the multiple DCIs, the UE may determine to omit a signaling response for one DCI (or a subset of the multiple DCIs) among the multiple DCIs.

[0012] The above can provide a technical solution for the technical problem of waste of time domain and frequency domain resources caused by redundant response signaling.

[0013] Figure 1 An example base station 102 is shown. An example base station (e.g., a gNodeB (gNB)) may use one or more TRPs 103 and include radio Tx / Rx circuitry 113 to receive from and transmit to UE 104. The base station may also include network interface circuitry 116 to couple the base station to a core network 110, such as via an optical or wired interconnect, Ethernet, and / or other data transmission media / protocols.

[0014] The base station may also include system circuitry 122. System circuitry 122 may include processor 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130. Operations 128 may include instructions for execution on one or more processors 124 to support functionality of the base station. For example, the operations may process DCI transmissions to UEs. Control parameters 130 may include parameters or support execution of operations 128. For example, control parameters may include network protocol settings, DCI format rules, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0015] Figure 2An example communication environment 200 is shown. In the communication environment 200, the UE 104 can communicate with a base station via the TRP 103 to receive DCI 252. In this example, the UE 104 supports one or more subscriber identity modules (SIMs), such as SIM1 202. The electrical and physical interface 206 connects SIM1 202 to the rest of the user equipment hardware, such as through a system bus 210.

[0016] UE 104 includes a communication interface 212, a system logic 214, and a user interface 218. System logic 214 may include any combination of hardware, software, firmware, or other logic. System logic 214 may be implemented using, for example, one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System logic 214 is part of the implementation of any desired functionality in UE 104. In this regard, system logic 214 may include logic that facilitates: for example, decoding and playing music and videos, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, for example, Internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 218. User interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of input 228 include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0017] The system logic 214 may include one or more processors 216 and memory 220. The memory 220 stores, for example, control instructions 222 that the processor 216 executes to implement the desired functions of the UE 104. The control parameters 224 provide and specify configuration and operating options for the control instructions 222. The memory 220 may also store any BT, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 will send or receive through the communication interface 212.

[0018] In various implementations, system power may be provided by a power storage device such as battery 282 .

[0019] In the communication interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuits 230 handle the transmission and reception of signals through one or more antennas 232. The communication interface 212 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium.

[0020] The signals transmitted and received may follow any of an array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 212 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below may be applied to other wireless communication technologies, whether from the Third Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards groups.

[0021] Figure 3 An example multi-TRP environment 300 is shown. In the example multi-TRP environment 300, two TRPs 303, 304 transmit to the UE 104 at a given time (e.g., for communication of multiple layers). For example, layer 0 is transmitted from TRP0 303, and layer 1 is transmitted from TRP1 304. In order to support backhaul between TRP0 303 and TRP1 304, a single DCI (e.g., DCI0) can be used to schedule a physical downlink shared channel (PDSCH) across multiple layers (e.g., from two TRPs). A single DCI can be sent from TRP0 or TRP1. Even if a layer from one of the two TRPs is blocked, if the layer transmission from the other TRP is not blocked, the PDSCH can still be correctly detected. Therefore, the transmission of PDSCH from multiple TRPs can increase the reliability of the PDSCH.

[0022] However, if a single DCI is blocked, the UE 104 may not have to correctly decode the PDSCH. The DCI is used to inform the UE of scheduling information for the PDSCH, such as time / frequency resource locations, modulation and coding scheme (MCS), and / or other scheduling information. Therefore, the multi-TRP type reliability of the PDSCH depends on the existence of similar reliability of the PDCCH (e.g., DCI reception). Therefore, the UE 104 may include the ability to receive and coordinate responses to multiple DCIs.

[0023] In some implementations, PDCCH reliability may be increased via redundancy. Figure 4 A second example multi-TRP environment 400 is shown. In the second example, DCI0 403 and DCI1 404 are sent from TRP0 303 and TRP1 404, respectively, and they are both used to schedule PDSCH0 412. In this case, multiple PDCCHs for scheduling the same PDSCH can be configured with independent TCI states, where one TCI state corresponds to a beam. Even if only one beam is not blocked, PDSCH0 412 can be successfully decoded. Similarly, physical uplink shared channel scheduling (or any other signaling scheduling processed by PDCCH) can increase its reliability. For example, sounding reference signaling (SRS) request scheduling and / or channel state information (CSI) scheduling can increase its reliability. In some cases, the redundancy discussed here can be used to support common DCI signaling. Therefore, slot format indicators, preemption indications, transmit power control (TPC) commands, cancellation indications and other signal scheduling can have increased reliability.

[0024] In an illustrative scenario, an SRS request in a DCI in time unit n (e.g., a specific DCI in a specific time unit) includes a request to trigger one or more SRS resource sets. The UE receiving the DCI will send the triggered SRS resource or resource set in time unit n+k, where k is configured by high-layer signaling (the high layer is, for example, a layer above the physical layer in the communication stack, such as a radio resource control (RRC) layer or a media access control element (MACCE) layer). "k" may refer to a signal time offset defined for the content of the signaling response. For example, k may be configured for a given SRS resource and / or SRS resource set, but by different other signaling triggered by the DCI, such as CSI signaling. In NR Rel-15, k is a slotOffset configured for an SRS resource or resource set. Because k may be defined by high-layer signaling, in some implementations, k may be determined independently of the configuration information of the DCI, which may be used to coordinate redundant signaling responses (e.g., by response scheduling or response omission). DCI may convey values ​​set via higher layer signaling, but such values ​​may not necessarily be used for adjustment of signaling scheduling coding purposes. A time unit may refer to a time slot, a symbol, a plurality of time / frequency resources, an effective time slot for information sent over a plurality of time slots, or other time measurements for DCI and / or signaling responses. The configuration information of DCI refers to some parameters configured for the CORESET or search space of DCI via higher layer signaling (e.g., RRC signaling). In some cases, the configuration information of DCI refers to RRC parameters configured for the CORESET or search space of DCI.

[0025] However, in some cases, DCI 0 and DCI 1: (A) can be sent in different time units, for example, in time unit n (e.g., a specific time unit) and time unit n+j (a specific time unit different from the specific time unit), respectively; (B) can both trigger the same SRS resource set, and (C) can both be correctly received by the UE. In this case, the UE can send the triggered SRS resources or resource sets in time units n+k and n+j+k, respectively. This may result in redundant SRS transmissions. For these illustrative scenarios, n, j, and k can be non-negative integers, where k is the time offset between the DCI and the SRS transmission scheduled by the DCI.

[0026] In some implementations, redundant SRS transmissions may be avoided.

[0027] In some implementations, as described above, signaling responses may be coordinated between multiple DCIs (e.g., via differentiated scheduling that takes into account the different arrivals of multiple DCIs). In other words, the total time unit offset between the DCI and the scheduled signaling response (e.g., such as an SRS transmission) may be based on the configuration information of the DCI (e.g., "information B" within the DCI). The configuration information of the DCI may include various types of PDCCH information. For example, as described above, in some cases, different redundant DCIs may have different TCIs to account for their transmission from geographically different TRPs. Thus, different TCIs may include different offsets corresponding to different DCIs. In some implementations, the configuration information includes a configuration for a CORESET and / or a configuration for a search space. In other words, the configuration information may include: beam information, including TCI and / or a spatial relationship for a PDCCH; time domain resources used by a PDCCH, including a PDCCH opportunity index, a slot index or a symbol index used by a PDCCH; a CORESET pool index configured per CORESET; and / or other high-level parameters for a PDCCH.

[0028] In an example implementation, each redundant DCI may be assigned a corresponding time unit offset (e.g., a specific offset for a specific DCI). An example scenario with two time slot offsets is discussed below. However, the techniques and architectures may be applied to any number of DCIs and corresponding offsets. Configuration information within the DCI (e.g., information B) may be used to determine the corresponding offset for each DCI.

[0029] In an illustrative example, beam information is used to determine the corresponding offsets for two DCIs (e.g., a specific DCI and a concrete DCI). In this example, two time unit offsets are configured for each signaling response resource set: k(0)=6, k(1)=5. Based on the predetermined configuration of the UE, the use of TCI0 ​​for DCI results in a time unit offset k(0), while the use of TCI1 for DCI results in a time unit offset k(1). As described above, DCI0 is sent in time unit n, and DCI1 is sent in time unit n+j. Therefore, for the case of j=1, TCI0 ​​is used by DCI0 and TCI1 is used by DCI1, and redundant signaling response transmissions with reference to the DCI can be avoided because the UE can schedule responses to DCI0 and DCI1 in time unit n+6. Other time unit values ​​may be used.

[0030] In the illustrative example, the time unit offset is based on the time domain resources used by the DCI. In this example, the DCI can be placed into two offset groups based on the parity of the time unit in which the DCI is sent. For example, two time slot offsets are configured for each SRS resource set: k(0)=6, k(1)=5. If the DCI is sent in an even time slot, k(0) is assigned. If the DCI is sent in an odd time slot, k(1) is assigned. The group can be assigned by the function mod(timeunitDCI, G), where timeunitDCI is the time unit in which the DCI is sent and G is the number of groups. In short, multiple time unit offsets are configured and finally a time unit offset is selected based on the time domain resources used by the DCI. The time unit offset is the time interval between the DCI and the scheduled SRS transmission.

[0031] The illustrative example is based on a CORESET pool index configured per TRP. The time unit offset is based on the CORESET pool index, where each CORESET pool index corresponds to a TRP. In this example, two time slot offsets may be configured for each signal response resource or resource set, and the UE will select one time slot offset based on the CORESET pool index configured for the DCI that schedules the SRS.

[0032] In various implementations, the time unit offset T may be configured or predefined for different configuration information of the DCI. The total time unit offset between the DCI and the signaling response may be based on the additional time slot offset T configured per SRS resource or resource set and the traditional signal time unit offset k (which may be assigned based on the signaling content). In other words, the total time unit offset is k+T. Assuming that the DCI is sent in time unit n and the digital basic configuration (e.g., subcarrier spacing) of the SRS and PDCCH is the same, the signaling response such as SRS transmission is performed in time unit n+k+T.

[0033] For example, assuming that the additional time slot offset T0=0 for TCI0, assuming that the additional time slot offset T1=-1 for TCI1, and assuming that the time slot offset k for the configuration of the SRS resource set is k=6, the total offset for TCI1 will be k+T1=5, and the total offset for TCI0 ​​will be k+T0=6. When DCI0 with TCI0 ​​and DCI1 with TCI1 are sent in time slots n and n+1, both of them will trigger the sending of the SRS resource set in time slot n+6. Accordingly, the UE will determine that two identical SRS resource sets will be sent in time slot n+6, and then the UE will only send one of them and redundant DCI response signaling is avoided.

[0034] In various implementations, the T value is configured for each CORESET. For SRS transmissions scheduled by DCI associated with a CORESET, the total time unit offset is k+T, where T is the configured value for the CORESET. For example, T0=2 is configured for CORESET 1 and T1=3 is configured for CORESET 2. If the SRS is scheduled by DCI from CORESET 1, the final time slot offset is k+T0. If the SRS is scheduled by DCI from CORESET 2, the final time slot offset is k+T1. More generally, additional time unit offsets are configured for a CORESET or search space, and the total time unit offset is based on the additional time unit offsets and k. The final SRS transmission time unit is then based on the time unit of the DCI and the total time unit offset.

[0035] In various implementations, two T values ​​may be configured, each associated with a CORESET pool index. If SRS is scheduled by a DCI associated with a CORESET pool index i (i=0 or 1), the final slot offset is k+Ti. Ti is the T value corresponding to the CORESET pool index i.

[0036] In various implementations, the techniques and architectures discussed herein can be applied to various DCI response signaling. For example, DCI response coordination can be applied to time-related information indicated by DCI. For example, the time offset between DCI and PDSCH / PUSCH response, or the time offset between DCI and triggered RS, or the time offset between DCI and triggered CSI report can be configured. The traditional time offset k between PDCCH and data (including PDSCH and PUSCH) is indicated by the time domain resource allocation (TDRA) field in DCI. Therefore, k can be adjusted using the additional time offset T as described above. Alternatively, a custom T can be configured using configuration information of DCI similar to the above k(0) value and k(1) value. These techniques are actually applicable to any signaling response offset. The signaling response may include any one or any combination of PDSCH, PUSCH, CSI-RS, SRS, CSI report, and other signals indicated / triggered by DCI. The signaling response time unit of PDSCH, PUSCH, CSI-RS, SRS, CSI report and other signals indicated / triggered by DCI is the transmission time unit of PDSCH, PUSCH, CSI-RS, SRS, CSI report and other signals respectively. The k value used for PDSCH or PUSCH or CSI-RS or CSI report can be the time offset between the DCI and the PDSCH or PUSCH or CSI-RS or CSI report transmission scheduled by the DCI.

[0037] In various implementations, the techniques and architectures discussed here can be applied to various DCI response signaling. For example, the DCI is a common group DCI, including DCI formats 2_0, 2_1, 2_2, 2_3, 2_4... 2_n. The common group DCI is a DCI different from DCI formats 0_i, 1_i, where i = 0, 1, 2...n. The signaling response may include any signaling indicated by the common group DCI, for example, a slot format indicator notified by DCI format 2_0, a pre-emption indication notified by DCI format 2_1. The time unit of the signaling response is the valid time unit indicated by the signaling in the common group DCI. In the traditional NR mechanism, the valid time unit indicated by the signaling notified by the common group DCI is the same as the time unit of the DCI transmission. Taking into account the additional time unit offset T, the valid time unit indicated by the signaling notified by the common group DCI should be based on T. Specifically, it should be T time units after the DCI transmission.

[0038] In various implementations, the signaling response time unit is constant. The DCI transmission time unit is assumed to be T time units after the time unit in which the real DCI is received or sent. In other words, the UE receives the DCI in time unit n, but when the UE calculates the signaling response time unit in which the signaling is scheduled by the DCI, the UE assumes that the DCI is sent in n+T.

[0039] The time offset between the PDCCH transmission and the signal response triggered by the PDCCH is associated with the information B of the PDCCH. Furthermore, an additional time offset T may be configured or predefined for different information B. The final time offset between the PDCCH and the signal response scheduled by the PDCCH is then associated with the additional time offset.

[0040] In some implementations, the predetermined content may satisfy a similarity condition (e.g., condition A), and the UE may identify the similarity condition in order to determine that multiple DCIs schedule the same signaling. When the similarity condition is satisfied between multiple DCIs, the UE may determine to omit the signaling response for all DCIs except one DCI (or a subset thereof) in the multiple DCIs. For example, the similarity condition may include the same (or similar, such as a series of continuous values ​​or other predetermined similarity levels) value within the predetermined content. For example, a hybrid automatic repeat request (HARQ) process number, a new data indicator (NDI), time and frequency resources allocated by the DCI, or a combination of these items may constitute the predetermined content within the DCI. When multiple DCIs have the same (or similar) value for the predetermined content, the similarity condition for multiple DCIs may be satisfied. For example, three of the four received DCIs may satisfy the similarity condition. Therefore, the UE will omit the response to two of the three matching DCIs and provide response signaling for the other two DCIs.

[0041] In an illustrative example, if the UE receives two DCIs that meet the similarity condition based on its predetermined content, the UE will only send response signaling (e.g., SRS) for the first DCI received. Now referring to DCI0 and DCI1 discussed above, DCI0 and DCI1 trigger signaling responses (SRS transmissions) in time unit n+k and time unit n+j+k, respectively. In this case, the UE sends in time unit n+k and omits the signaling response in time unit n+j+k. Alternatively, the UE can be configured to send in response to the second DCI received. In the above scenario, the UE will omit its response in time unit n+k and send a signaling response in time unit n+j+k. For a larger DCI group that meets the similarity condition, the UE can be configured to respond to the third, fourth...nth DCI. In some cases, the UE can be configured to respond to the last received DCI that meets the similarity condition. In some cases, the selection of the DCI used can be predefined or configured by using RRC signaling or other high-level signaling. DCI0 and DCI1 are from different TRPs and correspond to different CORESET pool indexes. The predetermined content may include some of the DCI parameters.

[0042] The predetermined content may include various DCI parameters, such as a hybrid automatic repeat request (HARQ) process number, a new data indicator (NDI), time domain resources allocated for specific signaling, frequency domain resources allocated for specific signaling, a carrier indicator, a BWP indicator, or a combination thereof.

[0043] The predetermined content may include various DCI parameters, for example, any parameter in the DCI except the downlink allocation index (DAI). Optionally, the predetermined content may include all parameters in the DCI except the downlink allocation index (DAI) and the time domain resource allocation (TDRA). Optionally, the predetermined content may include all parameters in the DCI except the downlink allocation index (DAI), the time domain resource allocation (TDRA) and the carrier indicator.

[0044] For Type II HARQ codebook determination, the DAI may be used to determine the ACK / NACK order and number of bits. Therefore, the DAI in the two DCIs may be different for DCI0 and DCI1. Therefore, the UE may send feedback ACK / NACK bits for DCI0 and DCI1 (even if another signaling response for one of the two DCIs is omitted in response to satisfying the similarity condition).

[0045] In some cases, only one of the two redundant DCIs may be correctly received by the UE. In the case where the UE receives only one of the two, the base station (e.g., gNB) may not necessarily determine which one was received before the signaling response from the UE. Therefore, in the example with DCI0 and DCI1, the UE will send a signaling response in time unit n+k or n+j+k, but the base station may not know which one. Therefore, the base station may listen (e.g., perform blind detection) twice: once in time unit n+k and once in time unit n+j+k.

[0046] Figure 5 Example coordination logic 500 for DCI signaling response coordination is shown, which can be implemented on a specifically configured circuit (e.g., within a UE 104). The coordination logic 500 can receive a specific DCI in a specific time unit (502). The coordination logic 500 can determine a specific time offset for specific signaling based on predetermined content within the specific DCI (504). The coordination logic 500 can perform the specific signaling (506). In some implementations, the specific signaling can be performed according to the specific time offset and / or the specific time unit.

[0047] Figure 6 Example scheduling logic 600 for DCI signaling response coordination is shown, which can be implemented on a specifically configured circuit (e.g., within a base station 102). The scheduling logic 600 can send a specific DCI to be received in a specific time unit to a UE (602). The specific DCI can be configured to schedule specific signaling. The scheduling logic 600 uses predetermined content within the specific DCI to indicate a specific time offset (604). The scheduling logic can listen for specific signaling in response to the DCI (606). In some implementations, the specific signaling can be scheduled according to a specific time offset and / or a specific time unit.

[0048] Reference again Figure 4In some implementations, different TCI states may be configured for DCI0 and DCI1, where both DCI0 and DCI1 are associated with the same CORESET. In other words, one CORESET may be configured with two TCI states. The time domain resources may be divided into two groups, and each group is associated with one of the two TCI states. At the same time, when the beam involves a spatial relationship or the TCI state is not configured or activated to the SRS resource, a default beam may be used. The default beam is based on the beam of the CORESET with the lowest CORESET ID. However, if the lowest CORESET has two beams, the UE may not necessarily be able to send SRS because, in some cases, the UE may lack two-beam capability. For example, some implementations may define a mapping between the two beams of the lowest CORESET and the SRS resources to allow an alternative to two-beam SRS transmission. For codebook-based SRS transmission, two resources may be configured within one SRS resource set. Then, the i-th beam of the lowest CORESET is used for the i-th SRS resource of the SRS resource set, where the use of the SRS resource set is a codebook.

[0049] Table 1 shows a list of acronyms that may be used herein.

[0050]

[0051]

[0052] The methods, apparatus, processes, circuits, and logic described above and below may be implemented in many different ways and in many different combinations of hardware and software. For example, all or part of the implementation may be a circuit including an instruction processor, such as a central processing unit (CPU), a microcontroller, or a microprocessor; or as an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA); or as a circuit including discrete logic or other circuit components, including analog circuit components, digital circuit components, or both; or any combination thereof. As examples, the circuit may include discrete interconnected hardware components, or may be combined on a single integrated circuit die, distributed among multiple integrated circuit dies, or implemented in a multi-chip module (MCM) of multiple integrated circuit dies in a common package.

[0053] Thus, the circuit may store or access instructions for execution, or may implement its functionality solely in hardware. Instructions may be stored in a tangible storage medium other than a transient signal, such as flash memory, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM); or on a magnetic disk or optical disk, such as a compact disk read-only memory (CDROM), a hard disk drive (HDD) or other magnetic disk or optical disk; or in or on other machine-readable media. The medium may consist of a single (e.g., single) storage device, multiple storage devices, distributed storage devices, or other storage configurations. A product such as a computer program product may include a storage medium and instructions stored in or on the medium, and when these instructions are executed by circuits in the device, these instructions may cause the device to implement any of the processes described above or shown in the accompanying drawings.

[0054] These implementations can be distributed. For example, the circuit can include multiple different system components, such as multiple processors and memories, and can span multiple distributed processing systems. Parameters, databases, and other data structures can be stored and managed separately, can be merged into a single memory or database, can be logically and physically organized in many different ways, and can be implemented in many different ways. Example implementations include linked lists, program variables, hash tables, arrays, records (e.g., database records), objects, and implicit storage mechanisms. Instructions can form parts of a single program (e.g., subroutines or other code segments), can form multiple separate programs, can be distributed on multiple memories and processors, and can be implemented in many different ways. Example implementations include stand-alone programs, and as part of a library, such as a shared library like a dynamic link library (DLL). For example, a library can contain shared data and one or more shared programs, and the shared program includes instructions that perform any processing described above or shown in the accompanying drawings when executed by the circuit.

[0055] Various implementations have been described in detail. However, many other implementations are possible.

Claims

1. A method comprising: receiving specific downlink channel information (DCI) in a specific time unit to schedule specific signaling; performing the specific signaling in response to the specific DCI, in: The specific time offset is determined based on configuration information for the specific DCI; and The specific signaling is scheduled according to the specific time offset; Receive specific DCI; Determining that the specific DCI and the specific DCI satisfy a similarity condition; A specific signaling response to the specific DCI is omitted, wherein: the omission of the specific signaling response is performed in response to the specific DCI and the specific DCI satisfying the similarity condition.

2. The method according to claim 1, wherein the configuration information comprises: Parameters for configuring a search space for the specific DCI defined at a layer above the physical layer; Parameters for configuring a CORESET for said specific DCI defined at a layer above the physical layer; to configure parameters corresponding to the CORESET pool index of the specific DCI in which a layer above the physical layer is defined; or Any combination of the above.

3. The method according to claim 1 or 2, wherein the configuration information comprises: Beam information, where: Optionally, the beam information includes a transmission configuration index (TCI), a spatial relationship for the specific DCI, or both; The time domain resources used by the specific DCI, wherein: Optionally, the time domain resource includes a physical downlink control channel (PDCCH) opportunity index, a time slot index, a symbol index used by the PDCCH, or any combination thereof, wherein Optionally, the PDCCH opportunity index, the time slot index, the symbol index used by the PDCCH or any combination thereof; and The CORESET pool index configured for the CORESET of the specific DCI; or any combination of the above.

4. The method according to any one of claims 1 to 3, wherein a time unit for executing specific signaling is determined based on the specific time unit, the specific time offset, and a signal time offset notified for the specific signaling.

5. The method according to any one of claims 1 to 4, wherein the specific signaling comprises: a sounding reference signal (SRS) scheduled by the specific DCI; a channel state information reference signal (CSI-RS) scheduled by the specific DCI; a physical downlink shared channel (PDSCH) scheduled by the specific DCI, a physical uplink shared channel (PUSCH) scheduled by the specific DCI, a CSI report scheduled by the specific DCI, Signaling indication scheduled by group common DCI; or Any combination of the above.

6. The method according to any one of claims 1 to 5, wherein the time unit for executing the specific signaling comprises: The valid time unit of the specific signaling, the transmission time unit of the specific signaling, or both.

7. The method according to any one of claims 1 to 6, wherein: The specific time offset is determined independently of the configuration information.

8. The method according to claim 7, wherein: The specific DCI arrives before the specific DCI; and Optionally, the specific DCI arrives at a specific time unit before a specific time unit at which the specific DCI arrives.

9. The method according to claim 7 or 8, wherein: The specific DCI arrives before the particular DCI; and Optionally, the specific DCI arrives at a specific time unit before a specific time unit at which the specific DCI arrives.

10. The method according to any one of claims 7 to 9, wherein: The similarity condition includes: determining that the specific DCI is the same as predetermined content within the specific DCI; and Optionally, the predetermined content includes: Hybrid Automatic Repeat Request (HARQ) process number; New Data Indicator (NDI); time domain resources allocated for the specific signaling; frequency domain resources allocated for the specific signaling; Carrier indicator; BWP indicator; All DCI contents except the Downlink Assignment Index (DAI) and the Time Domain Resource Assignment (TDRA); or All DCI content except the Downlink Assignment Index (DAI); or Any combination of the above.

11. The method according to any one of claims 7-10, wherein the specific DCI and the concrete DCI are associated with different CORESET pool indexes.

12. The method according to any one of claims 7 to 11, further comprising: Feedback acknowledgement / negative acknowledgement (ACK / NACK) bits are sent for both the specific DCI and the particular DCI.

13. A method comprising: Sending specific downlink control information (DCI) to a user equipment (UE) in a specific time unit to schedule specific signaling; receiving specific signaling in response to the DCI, wherein: The specific time offset is configured based on configuration information for the specific DCI; and The specific signaling is scheduled according to the specific time offset; Sending a specific DCI, wherein the specific DCI and the specific DCI satisfy a similarity condition; The specific DCI and the specific DCI are selected to satisfy the similarity condition so as to enable the UE to omit a signaling response to the specific DCI.

14. The method according to claim 13, wherein the configuration information comprises: Parameters for configuring a search space for the specific DCI defined at a layer above the physical layer; Parameters for configuring a CORESET for said specific DCI defined at a layer above the physical layer; to configure parameters corresponding to the CORESET pool index of the specific DCI in which a layer above the physical layer is defined; or Any combination of the above.

15. The method according to claim 13 or 14, wherein the configuration information comprises: Beam information, where: Optionally, the beam information includes a transmission configuration index (TCI), a spatial relationship for the specific DCI, or both; The time domain resources used by the specific DCI, wherein: Optionally, the time domain resource includes a physical downlink control channel (PDCCH) opportunity index, a time slot index, a symbol index used by the PDCCH, or any combination thereof, wherein Optionally, the PDCCH opportunity index, the time slot index, the symbol index used by the PDCCH, or any combination thereof; and The CORESET pool index configured for the CORESET of the specific DCI; or any combination of the above.

16. The method according to any one of claims 13 to 15, wherein a time unit for executing specific signaling is determined based on the specific time unit, the specific time offset, and a signal time offset notified for the specific signaling.

17. The method according to any one of claims 13 to 16, wherein the specific signaling comprises: a sounding reference signal (SRS) scheduled by the specific DCI; a channel state information reference signal (CSI-RS) scheduled by the specific DCI; a physical downlink shared channel (PDSCH) scheduled by the specific DCI, a physical uplink shared channel (PUSCH) scheduled by the specific DCI, a CSI report scheduled by the specific DCI, Signaling indication scheduled by group common DCI; or Any combination of the above.

18. The method according to any one of claims 13 to 17, wherein the time unit for executing the specific signaling comprises: The valid time unit of the specific signaling, the transmission time unit of the specific signaling, or both.

19. The method according to any one of claims 13 to 18, wherein: The total time offset is determined independently of the configuration information.

20. The method of claim 19, wherein: The specific DCI arrives before the specific DCI; and Optionally, the specific DCI arrives in a specific time unit before a specific time unit in which the specific DCI arrives.

21. The method according to claim 19 or 20, wherein: The specific DCI arrives before the particular DCI; and Optionally, the specific DCI arrives in a specific time unit before a specific time unit in which the specific DCI arrives.

22. The method according to any one of claims 19 to 21, wherein: The similarity condition includes: determining that the specific DCI is the same as predetermined content within the specific DCI; and Optionally, the predetermined content includes: Hybrid Automatic Repeat Request (HARQ) process number; New Data Indicator (NDI); time domain resources allocated for the specific signaling; frequency domain resources allocated for the specific signaling; Carrier indicator; BWP indicator; All DCI contents except the Downlink Assignment Index (DAI) and the Time Domain Resource Assignment (TDRA); or All DCI content except the Downlink Assignment Index (DAI); or Any combination of the above.

23. The method according to any one of claims 19-22, wherein the specific DCI and the specific DCI are associated with different CORESET pool indexes.

24. The method according to any one of claims 19 to 23, further comprising: Feedback acknowledgement / negative acknowledgement (ACK / NACK) bits are received for both the specific DCI and the particular DCI.

25. An apparatus comprising circuitry configured to implement the method according to any one of claims 1-24.

26. A machine-readable medium comprising instructions configured to cause a machine to implement the method according to any one of claims 1-24, wherein: Optionally, the machine-readable medium comprises a non-transitory medium; Optionally, the machine-readable medium is a medium other than a transient signal; and Optionally, the instructions are executable.

27. A method comprising implementing any feature or any combination of features as claimed in any one of claims 1 to 26 or disclosed herein.

28. An apparatus comprising circuitry configured to implement the method of claim 27.

29. A machine-readable medium comprising instructions configured to cause a machine to implement the method according to claim 27, wherein: Optionally, the machine-readable medium comprises a non-transitory medium; Optionally, the machine-readable medium is a medium other than a transient signal; and Optionally, the instructions are executable.

Images