Patent Description:
In wireless communication, repetition of control information may cause degraded operation of a wireless communication device or UE. Conventional UE cannot identify or distinguish repetition of control information or transmission information with sufficient effectiveness. Thus, a technological solution for determining transmission information is desired.

The example implementations disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various implementations, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these implementations are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present invention is defined by the scope of the appended claims.

Aspects of the present invention are defined in the independent claims and further detailed in the dependent claims.

Various example implementations of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example implementations of the present solution to facilitate the reader's understanding of the present solution.

Various example implementations of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made. The scope of the present invention is defined by the scope of the appended claims.

<FIG> illustrates an example wireless communication network, and/or system, <NUM> in which techniques disclosed herein may be implemented, in accordance with an implementation of the present disclosure. " Such an example network <NUM> includes a base station <NUM> (hereinafter "BS <NUM>") and a user equipment device <NUM> (hereinafter "UE <NUM>") that can communicate with each other via a communication link <NUM> (e.g., a wireless communication channel), and a cluster of cells <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> overlaying a geographical area <NUM>.

Such communication nodes may be capable of wireless and/or wired communications, in accordance with various implementations of the present solution.

<FIG> illustrates a block diagram of an example wireless communication system <NUM> for transmitting and receiving wireless communication signals, e.g., OFDM/OFDMA signals, in accordance with some implementations of the present solution. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative implementation, system <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment <NUM> of <FIG>, as described above.

Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the implementations disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.

In accordance with some implementations, the UE transceiver <NUM> may be referred to herein as an "uplink" transceiver <NUM> that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna <NUM>. Similarly, in accordance with some implementations, the BS transceiver <NUM> may be referred to herein as a "downlink" transceiver <NUM> that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna <NUM>. The operations of the two transceiver modules <NUM> and <NUM> can be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna <NUM> for reception of transmissions over the wireless transmission link <NUM> at the same time that the downlink transmitter is coupled to the downlink antenna <NUM>. In some implementations, there is close time synchronization with a minimal guard time between changes in duplex direction.

In some illustrative implementations, the UE transceiver <NUM> and the base station transceiver <NUM> are configured to support industry standards such as the Long Term Evolution (LTE) and emerging <NUM> standards, and the like.

In accordance with various implementations, the BS <NUM> may be an evolved node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station, for example. In some implementations, the UE <NUM> may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA), tablet, laptop computer, wearable computing device, etc. The processor modules <NUM> and <NUM> may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.

Furthermore, the steps of a method or algorithm described in connection with the implementations disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules <NUM> and <NUM>, respectively, or in any practical combination thereof. In some implementations, the memory modules <NUM> and <NUM> may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules <NUM> and <NUM>, respectively.

<FIG> illustrates a wireless communication device performing a first determination that a second downlink control information is a repeat of first downlink control information, in accordance with some implementations of the present disclosure. As illustrated by way of example in <FIG>, example wireless communication <NUM> extends in an x-axis time direction and a y-axis frequency direction, and includes CSS1 <NUM> arranged in a first monitoring occasion <NUM>, a second monitoring occasion <NUM>, and a third monitoring occasion <NUM>. In some implementations, the CSS1 <NUM> includes downlink control information <NUM>, <NUM>, <NUM> and <NUM>.

In some implementations, the wireless communication device adds a new field in the DCI formats with CRC scrambled by at least one of INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, and PS-RNTI. Thus, in some implementations, the wireless communication device adds a new field for common DCI formats <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, or <NUM>-<NUM>. In some implementations, the new field is applied for each UE. In some implementations, each codepoint in the field contains an index X. In some implementations, X is an integer, X ≥ <NUM>. In some implementations, if X is not configured, the UE assumes that the DCI for the UE is not repeated.

In some implementations, the UE monitors PDCCH. Further, in some implementations, if received common DCIs during the predefined time period have the same format and contain the same index value X in the new field, the UE assumes that these DCIs are repeated. In response, in some implementations, the UE drops one repeated DCI. As one example, the UE can adopt the former one and drop the later one. In some implementations, a predefined time period mentioned above is N symbols or N slots defined in at least one of RRC parameter SearchSpace or ControlResourceSet. Alternatively, in some implementations for DCI format <NUM>-<NUM> and <NUM>-<NUM>, the predefined time period is the time period that the TPC command for the latest PUSCH, PUCCH or SRS are accumulated. As one example, if DCI <NUM> and DCI <NUM> contains the same value <NUM> in the new field, the UE assumes DCI <NUM> and DCI <NUM> are repeated DCIs. Thus, in this example, the UE only accumulates a TPC command in DCI <NUM>, DCI <NUM> and DCI <NUM> for the latest PUSCH, and ignores DCI <NUM>.

<FIG> illustrates a wireless communication device performing a second determination that a second downlink control information is a repeat of first downlink control information, in accordance with some implementations of the present disclosure. As illustrated by way of example in <FIG>, example wireless communication <NUM> extends in an x-axis time direction and a y-axis frequency direction, and includes CSS1 <NUM> arranged in a first monitoring occasion <NUM>, a second monitoring occasion <NUM>, a third monitoring occasion <NUM>, a fourth monitoring occasion <NUM>, and a fifth monitoring occasion <NUM>. In some implementations, the CSS1 <NUM> includes downlink control information <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>.

In some implementations, the wireless communication device adds a new field in the DCI formats with CRC scrambled by at least one of INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, and PS-RNTI. In some implementations, the wireless communication device adds a new field for common DCI format <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, or <NUM>-<NUM>. In some implementations, each codepoint in the field contains an index X. In some implementations, X equals to <NUM> or <NUM>. In some implmentations, gNB configures the repeated one common DCI format with the same index X and transmits them continuously. In some implementations, transmitting continuously is transmitting two adjacent DCIs with the same format with no other DCI with the other format transmitted by the BS or received by the UE therebetween. In some implementations, if the UE receives several continuous DCIs with the same DCI format in the predefined time period with the same index X, the UE assumes those DCIs are repeated DCIs. As one example, a single common DCI format is in the predefined time period, and the index X of <NUM> continuous DCIs with the same DCI format is reversed. In this example, where an X value changes from <NUM> to <NUM>, or changes from <NUM> to <NUM>, a UE assumes that it has received a new transmission. As another example, two continuous DCIs <NUM> and <NUM> have the same DCI format <NUM>-<NUM> as DCI <NUM> and DCI <NUM>. Further, in this example, DCIs <NUM> and <NUM> have the same index <NUM>, and the UE assumes DCIs <NUM> and <NUM> are repeated. Thus, in this example, the UE adopts the TPC command in DCI <NUM> and ignores the TPC command in DCI <NUM>.

<FIG> illustrates a wireless communication device effecting a first relationship between corresponding SS sets based on a first monitoring period, in accordance with some implementations of the present disclosure. As illustrated by way of example in <FIG>, example wireless communication <NUM> extends in an x-axis time direction and a y-axis frequency direction, and includes CSS1 <NUM> and CSS2 <NUM>. In some implementations, CSS1 <NUM> is arranged in a first monitoring occasion <NUM> and a second monitoring occasion <NUM> in a first monitoring period <NUM>. In some implementations, CSS1 <NUM> is arranged in a third monitoring occasion <NUM> and a fourth monitoring occasion <NUM> in a second monitoring period <NUM>. In some implementations, CSS2 <NUM> is arranged in a first monitoring occasion <NUM>, a second monitoring occasion <NUM>, and a third monitoring occasion <NUM>, in the first monitoring period <NUM>. In some implementations, CSS2 <NUM> is arranged in a fourth monitoring occasion <NUM>, a fifth monitoring occasion <NUM>, and a sixth monitoring occasion <NUM> in the second monitoring period <NUM>.

In some implementations, the wireless communication device effects at least one association relationship between multiple SS sets. In some implementations, multiple monitoring occasions are associated within multiple SS sets <NUM> and <NUM>. In some implementations, SS sets <NUM> and <NUM> are CSS sets or USS sets. In some implementations, a bitmap is configured in RRC signaling. In some implementations, the bitmap contains X bits, where X equals the number of monitoring occasions in one monitoring period in the first SS set <NUM> multiplied by the number of monitoring occasions in one monitoring period in the second SS set <NUM>. In some implementations, each bit denotes one combination of the <NUM> monitoring occasions in <NUM> SS sets in one monitoring period. In some implementations, if the bit value is <NUM>, then <NUM> corresponding monitoring occasions are associated. Similarly, in some implementations, if the bit value is <NUM>, then <NUM> corresponding monitoring occasions are not associated. In some implementations, the RRC signaling mentioned above is associated with at least one of the SS sets <NUM> and <NUM>, and a new RRC parameter. In some implementations, if the bitmap is configured in one of the SS sets, then an SS set ID of the other SS set is also configured. In some implementations, the UE expects the same monitoring period <NUM> for the <NUM> SS sets <NUM> and <NUM>.

In some implementations, if <NUM> DCIs are detected blindly in <NUM> associated monitoring occasions, the UE assumes those <NUM> DCIs are repeated. In some implementations, the UE assumes DCI are repeated based on one or more conditions. Under a first condition, the <NUM> DCIs have the same DCI format. Under a second condition, the <NUM> DCIs are a common DCI having the same DCI format and the same payload. Under a third condition, the <NUM> DCIs are UE-specified DCIs, having the same DCI format and scheduled at the same PDSCH/PUSCH. If one or more DCIs are repeated, the UE can drop <NUM> repeated DCI. As one example, the UE can ignore the later received DCI.

In some implementations, the wireless communication device effects at least one relationship between multiple SS sets. In some implementations, multiple monitoring occasions are associated within multiple SS sets <NUM> and <NUM>. In some implementations, the SS sets <NUM> and <NUM> are CSS sets or USS sets. In some implementations, gNB configures the relationship between the SS <NUM> and <NUM> sets and a time offset T. In some implementations, T is an integer and T ≥ <NUM>. In some implementations, the time offset T can be T symbols, or T slots, or T monitoring occasions, or the like. It is to be understood that the time offset is optional, and that if the time offset T is not configured, the UE assumes that the T value is <NUM>. In a first offset configuration, the ID of the smallest indexed SS set and the time offset T are configured in the largest indexed SS set, in RRC parameter SearchSpace. In a second offset configuration, a new RRC parameter contains the related <NUM> SS sets ID and the time offset T.

In some implementations, the UE expects that multiple SS sets <NUM> and <NUM> have the same configured monitoring period <NUM>. In some implementations, for each monitoring period <NUM>, the multiple associated PDCCH monitoring occasions are in <NUM> SS sets <NUM> and <NUM>. In some implementations, if the time offset T is T MOs, the calculated associated MO index in the largest indexed SS set equals the same MO index in the smallest indexed SS set + T. In some implementations, if the time offset is T symbols or T slots, the calculated time location of associated MO in the largest indexed SS set equals the time location of the MO in the smallest indexed SS set + T. Thus, in some implementations, the calculated time location of the associated monitoring occasion does not cross the boundary of the monitoring period.

In some implementations, the example wireless communication <NUM> includes no actual configured monitoring occasion on the calculated time location of the associated monitoring occasion. Further, in some implementations, the calculated associated MO index is not included in the largest indexed SS set. Thus, in some implementations, the UE assumes the nearest actual monitoring occasion is the associated PDCCH monitoring occasion. In some implementations, the nearest actual monitoring occasion is a predetermined monitoring location. A first predetermined monitoring occasion is after the calculated time location of the associated monitoring occasion in the corresponding SS set <NUM> or <NUM>, and nearest to it, in one monitoring period. A second predetermined monitoring occasion is before the calculated time location of the associated monitoring occasion in the corresponding SS set, and nearest to it, in one monitoring period. In some implementations, a monitoring occasion in the largest indexed SS set can only be associated with <NUM> monitoring occasion in the smallest indexed SS set. In some implementations, <NUM> monitoring occasion in the largest indexed SS set can be associated with at most N monitoring occasions in the smallest indexed SS set. In some implementations, N is an integer. For example, N equals to <NUM>. In some implementations, the smaller indexed MO in the smallest indexed SS set has the higher priority to associate with the other MO than the larger indexed MO.

In some implementations, if <NUM> DCIs are detected blindly in <NUM> associated monitoring occasions, the UE assumes those <NUM> DCIs are repeated based on one or more conditions. Under a first condition, <NUM> DCIs have the same DCI format. Under a second condition, <NUM> DCIs are a common DCI, having the same DCI format and the same payload. Under a third condition, <NUM> DCIs are UE-specified DCI, having the same DCI format and schedule at the same PDSCH/PUSCH. If one or more DCIs are repeated, the UE drops <NUM> repeated DCI. As one example, the UE can ignore the later received DCI. As one example, the time offset is configured as <NUM> monitoring occasion, so MO1 <NUM> and <NUM> and MO2 <NUM> and <NUM> in SS1 <NUM> are respectively associated within the same monitoring period with MO2 <NUM> and <NUM> and MO3 <NUM> and <NUM> in SS2 <NUM>, by associations <NUM>, <NUM>, <NUM> and <NUM>.

<FIG> illustrates a wireless communication device effecting at least one relationship between corresponding SS sets based on a first monitoring period and a second monitoring period, in accordance with some implementations of the present disclosure. As illustrated by way of example in <FIG>, example wireless communication <NUM> extends in an x-axis time direction and a y-axis frequency direction, and includes CSS1 <NUM> and CSS2 <NUM>. In some implementations, CSS1 <NUM> is arranged in a first monitoring occasion <NUM>, a second monitoring occasion <NUM>, and a third monitoring occasion <NUM> in a first monitoring period <NUM>. In some implementations, CSS2 <NUM> is arranged in a first monitoring occasion <NUM> and a second monitoring occasion <NUM> in a second monitoring period <NUM>. In some implementations, CSS1 <NUM> includes time offset T <NUM> and a detection window <NUM>.

In some implementations, the wireless communication device effects a relationship between multiple SS sets. In some implementations, multiple monitoring occasions are associated within these multiple SS sets. In some implementations, the SS sets <NUM> and <NUM> are CSS sets or USS sets. In some implementations, gNB configures one or more of a relationship between multiple SS sets, and a time offset T <NUM>. In some implementations, T is an integer and T ≥ <NUM>. In some implementations, the time offset T <NUM> can be T symbols, or T slots, or T monitoring occasions. In some implementations, the wireless communication device defines a detection window <NUM>. In some implementations, a time length of the detection window <NUM> is the monitoring period of the largest indexed SS set, or the smallest indexed SS set. In some implementations, the configurations in RRC signaling may be configured according to one or more configurations. In a first offset configuration, the ID of the smallest indexed SS set and the time offset T are configured in the larger indexed SS set, in RRC parameter SearchSpace. In a second offset configuration, a new RRC parameter contains the related <NUM> SS sets ID and the time offset T.

In some implementations, multiple associated PDCCH monitoring occasions are in multiple SS sets. In some implementations, a monitoring occasion in the smallest indexed SS set is associated with the monitoring occasions on a one-to-one basis in the detection window <NUM> in the largest indexed SS set. In some implementations, the start time of the detection window <NUM> is the time location of the first monitoring occasion or the first symbol of the monitoring period in the smallest indexed SS set plus the configured time offset T <NUM>.

In some implementations, <NUM> monitoring occasion in the largest indexed SS set can only be associated with <NUM> monitoring occasion in the smallest indexed SS set. In some implementations, <NUM> monitoring occasion in the largest indexed SS set is associated with at most N monitoring occasions in the smallest indexed SS set. In some implementations, N is an integer. For example, N equals <NUM>. In some implementations, the smaller indexed MO has a higher priority to associate with the MO than the larger indexed MO.

In some implementations, if <NUM> DCIs are detected blindly in <NUM> associated monitoring occasions, the UE assumes those <NUM> DCIs are repeated. In some implementations, the UE assumes DCI are repeated based on one or more conditions. Under a first condition, the <NUM> DCIs have the same DCI format. Under a second condition, the <NUM> DCIs are a common DCI having the same DCI format and the same payload. Under a third condition, the <NUM> DCIs are UE-specified DCIs, having the same DCI format and scheduled at the same PDSCH/PUSCH, or SRS, or CSI report and so on. If one or more DCIs are repeated, the UE drops <NUM> repeated DCI. As one example, the UE can ignore the later received DCI.

<FIG> illustrates a wireless communication device effecting a second relationship between corresponding SS sets based on a first monitoring period, in accordance with some implementations of the present disclosure. As illustrated by way of example in <FIG>, example wireless communication <NUM> extends in an x-axis time direction and a y-axis frequency direction, and includes CSS1 <NUM> and CSS2 <NUM>. In some implementations, CSS1 <NUM> is arranged in a first monitoring occasion <NUM> and a second monitoring occasion <NUM> in a first monitoring period <NUM>. In some implementations, CSS1 <NUM> is arranged in a third monitoring occasion <NUM> and a fourth monitoring occasion <NUM> in a second monitoring period <NUM>. In some implementations, CSS2 <NUM> is arranged in a first monitoring occasion <NUM>, a second monitoring occasion <NUM>, and a third monitoring occasion <NUM>, in the first monitoring period <NUM>. In some implementations, CSS2 <NUM> is arranged in a fourth monitoring occasion <NUM>, a fifth monitoring occasion <NUM>, and a sixth monitoring occasion <NUM> in the second monitoring period <NUM>.

In some implementations, the wireless communication device effects at least one association relationship <NUM>, <NUM>, <NUM> and <NUM> between multiple SS sets <NUM> and <NUM>. In some implementations, multiple monitoring occasions are associated within these multiple SS sets. In some implementations, the <NUM> SS sets <NUM> and <NUM> have the same monitoring period. Thus, in some implementations, the first X monitoring occasions in <NUM> SS sets are associated on a one-to-one basis. In some implementations, X is an integer and X ≥ <NUM>. In some implementations, an X value cannot be greater than the minimum value of the number of monitoring occasions in at least one SS set. In some implementations, the configurations in RRC signaling may be configured according to one or more configurations. In a first signaling configuration, the ID of the smaller indexed SS set and the number of associated monitoring occasions X in the larger indexed SS set are configured in the larger indexed SS set, in RRC parameter SearchSpace. In a second signaling configuration, a new RRC parameter contains the related <NUM> SS sets ID, the time offset T, and the number of associated monitoring occasions X. In some implementations, X is not configured or X = <NUM>, and the wireless communication device generates no association relationship between the monitoring occasions in the <NUM> SS sets <NUM> and <NUM>.

<FIG> illustrates an example method, in accordance with some implementations of the present disclosure. In some implementations, at least one of the BS <NUM> and the UE <NUM> performs method <NUM> according to present implementations. In some implementations, the method <NUM> begins at <NUM>.

At <NUM>, the example system receives the first and second control information at the UE <NUM> from the BS <NUM>. In some implementations, <NUM> includes at least one of <NUM>, <NUM> and <NUM>. At <NUM>, the example system receives the first control information in a first format. At <NUM>, the example system receives the second control information in a second format. At <NUM>, the example system receives the first control information and the second control information continuously. The method <NUM> then continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> that the second control information is a repeat of the first control information. In some implementations, <NUM> includes <NUM>. At <NUM>, the first control information is determined based on the first format of the first control information and the second format of the second control information. The method <NUM> then continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> whether the first control information and the second control information are received in a predetermined time period. In some implementations, a predetermined time period corresponds to detection window <NUM>. In accordance with a determination that the first control information and the second control information are received in a predetermined time period, the method <NUM> continues to <NUM>. Alternatively, in accordance with a determination that the first control information and the second control information are not received in a predetermined time period, the method <NUM> continues to <NUM>. At <NUM>, the method <NUM> continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> if the first control information and the second control information are the same. In some implementations, <NUM> includes <NUM> and <NUM>. At <NUM>, the example system determines that the first format and the second format are the same. At <NUM>, the example system determines that the first index and the second index are the same. In some implementations, the method <NUM> continues to <NUM>.

<FIG> illustrates an example method, in accordance with some implementations of the present disclosure. In some implementations, at least one of the BS <NUM> and the UE <NUM> performs method <NUM> according to present implementations. In some implementations, the method <NUM> begins at <NUM>. At <NUM>, the method <NUM> continues to <NUM>.

At <NUM>, an example system determines at the UE <NUM> whether the first control information is received in a first monitoring occasion. In accordance with a determination that the first control information is received in the first monitoring occasion, the method <NUM> continues to <NUM>. Alternatively, in accordance with a determination that the first control information is not received in the first monitoring occasion, the method <NUM> continues to <NUM>. A <NUM>, the example system determines at the UE <NUM> whether the second control information is received in the second monitoring occasion. In accordance with a determination that the second control information is received in the second monitoring occasion, the method <NUM> continues to <NUM>. Alternatively, in accordance with a determination that the second control information is not received in the second monitoring occasion, the method <NUM> continues to <NUM>. At <NUM>, the example system determines at the UE <NUM> whether the first monitoring occasion and the second monitoring occasion are in different SS sets. In accordance with a determination that the first monitoring occasion and the second monitoring occasion are in different SS sets, the method <NUM> continues to <NUM>. Alternatively, in accordance with a determination that the first monitoring occasion and the second monitoring occasion are not in different SS sets, the method <NUM> continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> if the first control information is a repeat of the second control information. In some implementations, <NUM> includes at least one of <NUM>, <NUM> and <NUM>. At <NUM>, the example system determines that the first format and the second format are the same. At <NUM>, the example system determines that the first control information and the second control information include the same payload. At <NUM>, the example system determines that the first control information and the second control information are scheduled at the same resource. The method <NUM> then continues to step <NUM>.

At step <NUM>, the example system determines at the UE <NUM> at least one time location of the first monitoring occasion. In some implementations, <NUM> includes at least one of <NUM> and <NUM>. At <NUM>, the example system determines the time location based at least partially on a time offset. In some implementations, the time offset corresponds to time offset <NUM>. At <NUM>, the example system determines the time location based at least partially on a time location of the second monitoring occasion. In some implementations, the method <NUM> ends at <NUM>.

<FIG> illustrates a further example method, in accordance with some implementations of the present disclosure. In some implementations, at least one of the BS <NUM> and the UE <NUM> performs method <NUM> according to present implementations. In some implementations, the method <NUM> begins at <NUM>.

At <NUM>, the example system receives the first and second control information at the UE <NUM> from the BS <NUM>. The method <NUM> then continues to <NUM>. At <NUM>, the example system determines at the UE <NUM> that the second control information is a repeat of the first control information. The method <NUM> then continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> whether the first control information and the second control information are received in a predetermined time period. In some implementations, a predetermined time period corresponds to detection window <NUM>. In accordance with a determination that the first control information and the second control information are received in a predetermined time period, the method <NUM> continues to <NUM>. Alternatively, in accordance with a determination that the first control information and the second control information are not received in a predetermined time period, the method <NUM> continues to <NUM>.

At <NUM>, the example system determines at the UE <NUM> if the first control information and the second control information are the same. The method <NUM> continues to <NUM>. At <NUM>, the example system determines at the UE <NUM> if the first control information is a repeat of the second control information. The method <NUM> then continues to step <NUM>. At step <NUM>, the example system determines at the UE <NUM> at least one time location of the first monitoring occasion. In some implementations, the method <NUM> ends at <NUM>.

While various implementations of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one implementation can be combined with one or more features of another implementation described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative implementations.

Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according implementations of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in implementations of the present solution. It will be appreciated that, for clarity purposes, the above description has described implementations of the present solution with reference to different functional units and processors.

Claim 1:
A wireless communication method, comprising:
receiving, by a wireless communication device (<NUM>) from a network (<NUM>), a first control information and a second control information, wherein:
the first control information is received in a first Monitoring Occasion, MO;
the first MO is in a first Search Space, SS, set of a plurality of SS sets;
the second control information is received in a second MO;
the second MO is in a second SS set of the plurality of SS sets; and
the first SS set has a smaller SS set index than the second SS set in the plurality of SS sets,
wherein:
the first SS set has a first monitoring period;
the second SS set has a second monitoring period; and
the first monitoring period and the second monitoring period are the same,
the wireless communication method being characterized in that:
each of a number of MOs in the first SS set has a one-to-one mapping with respective one of a number of MOs in the second SS set, and the wireless communication method further comprises:
determining, by the wireless communication device (<NUM>), that the second control information is a repeat of the first control information.