Type 1 HARQ-ACK Codebook with Relative SLIV

Abstract

According to some embodiments, a method is performed by a wireless device capable of operating in a wireless network in which physical downlink control channel (PDCCH) monitoring occasions vary by slot. The method includes obtaining a starting symbol S of a physical downlink shared channel (PDSCH), where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled, deriving a type-1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook based on the starting symbol S, and transmitting one or more HARQ-ACKs to a network node based on the HARQ-ACK codebook.

Description

[Technical field]

[0001] SUMMARY OF THE DISCLOSURE Embodiments of the present disclosure are directed to wireless communications, and more particularly, to a Type-1 Hybrid Automatic Repeat Request (HARQ) acknowledgement codebook with a relative start and length indicator (SLIV). [Background technology]

[0002] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding other steps, and / or unless it is implicit that a step must follow or precede other steps. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, whenever appropriate. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0003] The 3rd Generation Partnership Project (3GPP) New Radio (NR) provides services for multiple use cases, such as enhanced Mobile Broadband (eMBB), ultra-reliable low latency communications (URLLC), and machine-type communications (MTC). Each of the services has different technical requirements. For example, the general requirements for eMBB are high data rates with moderate latency and moderate coverage, while URLLC services require low latency and reliable transmission, but perhaps for moderate data rates.

[0004] One of the solutions to low latency data transmission is a shorter transmission time interval. In NR, in addition to transmission in slots, minislot communication is also allowed to reduce latency. Minislot is a concept used in scheduling, where in the downlink, a minislot can consist of 2, 4 or 7 Orthogonal Frequency Division Multiplexing (OFDM) symbols, and in the uplink, a minislot can be any number of OFDM symbols from 1 to 14. The concept of slots and minislots is not specific to a particular service, which means that minislots can be used for either eMBB, URLLC, or other services.

[0005] 1 is a time-frequency diagram illustrating example radio resources in NR. The horizontal axis represents time and the other axis represents frequency with a subcarrier spacing of 15 kHz.

[0006] In the 3GPP NR standard, downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH) indicates downlink data related information, uplink related information, power control information, slot format indication, etc. There are different formats of DCI associated with each of these control signals, and the UE distinguishes between them based on different Radio Network Temporary Identifiers (RNTIs).

[0007] The UE is configured by higher layer signaling to monitor DCI on different resources with different periodicities, etc. DCI formats 1_0, 1_1, and 1_2 are used to schedule downlink data sent in the Physical Downlink Shared Channel (PDSCH) and include time and frequency resources for downlink transmission, as well as modulation and coding information, HARQ (Hybrid Automatic Repeat Request) information, etc.

[0008] For downlink semi-persistent scheduling (SPS) and uplink configured grant type 2, part of the scheduling, including periodicity, is provided by higher layer configuration, and the rest of the scheduling information, such as time-domain and frequency-domain resource allocation, modulation and coding, is provided by DCI in the PDCCH.

[0009] The UE may indicate the capability to monitor the PDCCH according to one or more of the combinations (X, Y) = (2, 2), (4, 3), and (7, 3) for each subcarrier spacing (SCS) configuration of μ = 0 and μ = 1. The span is the number of consecutive symbols in a slot for which the UE is configured to monitor the PDCCH. Each PDCCH monitoring occasion is within one span. If the UE monitors the PDCCH on a cell according to the combination (X, Y), the UE supports PDCCH monitoring occasions in any symbol of the slot with a minimum time separation of X symbols between the first symbols of two consecutive spans, including those spanning the slot. The span starts at the first symbol where the PDCCH monitoring occasion starts and ends at the last symbol where the PDCCH monitoring occasion ends, where the number of symbols in the span is up to Y.

[0010] If the UE indicates a capability to monitor the PDCCH according to multiple (X, Y) combinations, and the configuration of a search space set in the UE for PDCCH monitoring on a cell results in a separation of any two consecutive PDCCH monitoring spans that is equal to or greater than the value of X for one or more of the multiple combinations (X, Y), the UE shall The UE monitors the PDCCH on the cell according to a combination (X, Y) from one or more combinations (X, Y) associated with the highest maximum number of TIFF0007602633000001.tif9170. The UE expects to monitor the PDCCH according to the same combination (X, Y) in every slot on the active downlink bandwidth portion (BWP) of the cell.

[0011] Uplink Control Information (UCI) is control information sent by the UE to the gNB. UCI consists of Hybrid ARQ Acknowledgement (HARQ-ACK), which is feedback information corresponding to a received downlink transport block about whether the transport block reception was successful or not, Channel State Information (CSI), which is related to downlink channel conditions, providing the gNB with channel related information useful for downlink scheduling, including information for multiple antennas and beamforming schemes, and Scheduling Request (SR), which indicates the need for uplink resources for uplink data transmission.

[0012] UCI is typically transmitted on a physical uplink control channel (PUCCH). However, if a UE is transmitting data on a PUSCH with valid PUSCH resources that overlap with the PUCCH, UCI may be multiplexed with the uplink data and transmitted on the PUSCH instead if the timeline requirements for UCI multiplexing are met.

[0013] The Physical Uplink Control Channel (PUCCH) is used by the UE to transmit HARQ-ACK feedback messages corresponding to the reception of downlink data transmissions. The PUCCH is also used by the UE to send channel state information (CSI) or to request an uplink grant for transmitting uplink data.

[0014] NR includes multiple PUCCH formats that support different UCI payload sizes. PUCCH formats 0 and 1 support up to 2 bits of UCI, while PUCCH formats 2, 3, and 4 can support 3 or more bits of UCI. With respect to PUCCH transmission duration, PUCCH formats 0 and 2 are considered short PUCCH formats that support a PUCCH duration of 1 or 2 OFDM symbols, while PUCCH formats 1, 3, and 4 are considered long formats and can support a PUCCH duration from 4 symbols to 14 symbols.

[0015] The HARQ feedback is used for error correction and control. The procedure for receiving a downlink transmission is as follows: the UE first receives a downlink transmission in slot n+K. 0 The first step is to monitor and decode the PDDCH in slot n, which refers to the downlink data scheduled in that slot (K 0 (wherein n is greater than or equal to 0). The UE then decodes the data in the corresponding PDSCH.

[0016] Based on the result of the decoding, the UE selects the time slot n+K 0 +K 1 In the case of slot aggregation, n+K 0 is replaced by the slot in which the PDSCH ends). 0 and K. 1 Both will be indicated during the DCI.

[0017] The resource for sending the acknowledgement is indicated by the PUCCH Resource Indicator (PRI) field in the DCI, which points to one of the PUCCH resources configured by higher layers.

[0018] Depending on the downlink / uplink slot configuration, or whether carrier aggregation or per-code block group (CBG) transmission is used in the downlink, feedback for several PDSCHs may need to be multiplexed into one feedback. This is done by configuring a HARQ-ACK codebook. In NR, the UE may be configured to multiplex the A / N bits using a semi-static or dynamic codebook.

[0019] A type 1 or semi-static codebook consists of a bit sequence where each element contains the A / N bits from a possible allocation in a slot, carrier, or transport block (TB). When the UE is configured with a CBG and / or a time domain resource allocation (TDRA) table with multiple entries, multiple bits are generated per slot and TB. It is important to note that the codebook is derived regardless of the actual PDSCH scheduling. The size and format of the semi-static codebook are pre-configured based on the above parameters. The disadvantage of a semi-static HARQ ACK codebook is that the size is fixed and bits are reserved in the feedback matrix regardless of whether there is a transmission or not.

[0020] When a UE has a TDRA table with multiple time domain resource allocation entries, the table is pruned (in other words, entries are removed based on a specified algorithm) to derive a TDRA table containing only non-overlapping time domain allocations. Then, one bit is reserved in the HARQ codebook for each non-overlapping entry (assuming the UE is capable of supporting reception of multiple PDSCHs in a slot).

[0021] To avoid reserving unnecessary bits in the semi-static HARQ codebook, in NR, the UE may be configured to use a Type 2 or dynamic HARQ codebook, where the A / N bit is present only if there is a corresponding transmission scheduled. To avoid confusion between the gNB and the UE, a counter downlink allocation indicator (DAI) field is present in the downlink allocation regarding the number of PDSCHs for which the UE must send feedback, which represents the cumulative number of {serving cell, PDCCH occasion} pairs for which a PDSCH has been scheduled to the UE up to the current PDCCH. Additionally, a total DAI field, when present, indicates the total number of {serving cell, PDCCH occasion} up to (and including) all PDCCHs of the current PDCCH monitoring occasion. The timing for sending the HARQ feedback is determined based on the PDCCH slot (K 0 ) and the PUCCH slots containing HARQ feedback (K 1 ) is determined based on both the

[0022] Figure 2 illustrates the transmission timeline in a simple scenario with two PDSCHs and one HARQ feedback. In the illustrated example, there are a total of four PUCCH resources configured, and the PRI indicates that PUCCH2 should be used for HARQ feedback. The following explains how PUCCH2 is selected from the four PUCCH resources based on the procedure in Rel-15.

[0023] In general, a UE is scheduled to receive a PDSCH by a DCI where the time domain resource allocation of the PDSCH is indicated by a Start and Length Indicator (SLIV) in the DCI, which indicates the starting symbol (S) and length (L) of the PDSCH, where S is with respect to a slot boundary.

[0024] In Rel-16, the UE may be configured with the RRC parameter referenceOfSLIVForDCI-Format1-2-r16, which indicates a possible new reference for S in the indicated SLIV.

[0025] When the UE is configured with referenceOfSLIVForDCI-Format1-2-r16 and the UE is scheduled to receive PDSCH with DCI format 1_2 with C-RNTI, MCS-C-RNTI, CRC scrambled by CS-RNTI, with slot offset K0=0 and PDSCH mapping type B, the start symbol S of the pointed to SLIV is relative to the start symbol S0 of the PDCCH monitoring occasion where DCI format 1_2 is detected. Otherwise the start symbol S is relative to the start of the slot, in other words use S0=0.

[0026] The UE shall use S for normal cyclic prefix. 0 +S+L ≤ 14, and S for extended cyclic prefix 0Combinations of S and L specified in Table 5.1.2.1-1 of TS 38.214 where +S+L≦12 shall be considered as valid PDSCH allocations.

[0027] Currently, some challenges exist. For example, for Type 1 HARQ-ACK codebook configuration, the current NR specification does not take into account that the set of possible PDCCH monitoring occasions may vary from slot to slot when the reference for SLIV is applied to PDSCH time domain resource allocation (TDRA). 0 When applied with .DELTA..times ... 0 This is in response to. Summary of the Invention

[0028] Based on the above description, currently, some challenges exist with respect to type 1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook configuration. Some aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, certain embodiments include a method for enabling the use of a type 1 HARQ-ACK codebook when a new reference for a start and length indicator (SLIV) may be configured in the UE in general.

[0029] In some embodiments, when a UE is configured with a new reference for SLIV, a common set R containing associated time domain resource allocation (TDRA) entries with possible starting symbols of physical downlink control channel (PDCCH) monitoring occasions is derived and used in the Type 1 HARQ-ACK codebook determination for all slots. Alternatively, the application of the Type 1 HARQ-ACK codebook is regulated in some cases depending on the configuration of the new reference for SLIV and / or PDCCH monitoring occasions.

[0030] In some embodiments, the set R containing the associated TDRA entries with different possible starting symbols of the PDCCH monitoring occasions is allowed to vary across slots depending on the configuration of the PDCCH monitoring occasions.

[0031] According to some embodiments, a method is performed by a wireless device capable of operating in a wireless network in which physical PDCCH monitoring occasions vary by slot. The method includes obtaining a starting symbol S of a physical downlink shared channel (PDSCH), where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled, deriving a type-1 HARQ-ACK codebook based on the starting symbol S, and transmitting one or more HARQ-ACKs to a network node based on the HARQ-ACK codebook.

[0032] In a particular embodiment, deriving the Type 1 HARQ-ACK codebook includes deriving a set R containing TDRA entries for PDSCH reception with possible starting symbols of PDCCH monitoring occasions.

[0033] In certain embodiments, the set R is common for all slots. In some embodiments, all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in all slots, and the starting symbol S is for the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled. In some embodiments, the type 1 HARQ-ACK codebook is derived only if the starting symbol of the PDCCH monitoring occasion is set to the same in all slots. If a PDCCH monitoring occasion is absent in some slots, the type 1 HARQ-ACK codebook may be derived only if the starting symbol of the PDCCH monitoring occasion, if not absent, is set to the same in all slots. In some embodiments, the set R includes entries derived from all starting symbols of the PDCCH monitoring occasions across all slots.

[0034] In a particular embodiment, the set R varies across slots.

[0035] In certain embodiments, deriving the set R may include being based on monitoring limits of the wireless device and / or avoiding entries that result in overlapping PDSCH reception candidates.

[0036] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0037] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, which when executed by a processing circuit is operable to perform any of the methods performed by the wireless device described above.

[0038] According to some embodiments, a method is performed by a network node capable of operating in a wireless network in which PDCCH monitoring occasions vary by slot, the method including transmitting a starting symbol S of a PDSCH to the wireless device, where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled, and receiving a HARQ-ACK from the wireless device based on a HARQ-ACK codebook and the starting symbol S.

[0039] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0040] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code that, when executed by a processing circuit, is operable to perform any of the methods performed by the network node described above.

[0041] Some embodiments may provide one or more of the following technical advantages: For example, certain embodiments enable the use of a Type 1 HARQ-ACK codebook when a UE is configured with a new reference for SLIV and the UE is scheduled with DCI format 1_2.

[0042] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: [Brief description of the drawings]

[0043] [Figure 1] FIG. 1 is a time-frequency diagram illustrating example radio resources in New Radio (NR). [Diagram 2]FIG. 1 illustrates a transmission timeline in a simple scenario with two physical downlink shared channels (PDSCHs) and one hybrid automatic repeat request (HARQ) feedback. [Diagram 3] FIG. 13 is a timing diagram illustrating an example of configured monitoring occasions, where each slot has a monitoring occasion with a different starting symbol. [Figure 4] FIG. 13 is a timing diagram illustrating an example of configured monitoring occasions, where each slot has a monitoring occasion with the same starting symbol. [Diagram 5] 1 is a timing diagram illustrating an example of configured monitoring occasions, where each slot has a monitoring occasion with the same starting symbol if the monitoring occasion is present in the slot. [Figure 6] FIG. 1 is a block diagram illustrating an example wireless network. [Figure 7] FIG. 1 illustrates an example user equipment according to some embodiments. [Figure 8] 1 is a flowchart illustrating an example method in a wireless device according to some embodiments. [Figure 9] 1 is a flowchart illustrating an example method in a network node according to some embodiments. [Figure 10] 1 is a schematic block diagram of a wireless device and a network node in a wireless network according to some embodiments. [Figure 11] FIG. 1 illustrates an exemplary virtualization environment, according to some embodiments. [Figure 12] FIG. 1 illustrates an exemplary communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 13] FIG. 1 illustrates an example host computer communicating with user equipment via a base station over a partially wireless connection in accordance with some embodiments. [Figure 14] 1 is a flowchart illustrating a method implemented according to some embodiments. [Figure 15] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments. [Figure 16] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments. [Figure 17] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0044] As described above, currently, some challenges exist with respect to type 1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook configuration. Some aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, certain embodiments include a method for enabling the use of a type 1 HARQ-ACK codebook when a new reference for a start and length indicator (SLIV) may be configured in the UE in general.

[0045] Certain embodiments are more fully described with reference to the accompanying drawings, however, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0046] The embodiments described herein may be applied to both dynamically scheduled Physical Downlink Shared Channel (PDSCH) HARQ-ACK feedback and downlink Semi-Persistent Scheduling (SPS) HARQ-ACK feedback. The embodiments are also applicable to HARQ-ACK with slot-based and sub-slot-based HARQ-ACK codebooks.

[0047] "PDCCH monitoring occasions" in the existing specification are interpreted as monitoring occasions in each slot. The spanning pattern does not have to be the same across slots. However, the same (X, Y) is satisfied across slots.

[0048] There is a restriction on the set to define a common set R for all slots. Currently, when relative SLIV is used, the reference point S for the start symbol S is 0 is specified based on the physical downlink control channel (PDCCH) monitoring occasion determined as follows: 0 When receiving a PDSCH scheduled by DCI format 1_2 with C-RNTI, MCS-C-RNTI, CRC scrambled by CS-RNTI with 0 and PDSCH mapping type B, the start symbol S is the start symbol S of the PDCCH monitoring occasion in which DCI format 1_2 is detected. 0 This is in response to.

[0049] However, the monitoring occasions are RRC configured according to a search space set configuration for PDCCH monitoring, and one monitoring span may include multiple different starting symbols of the monitoring occasions.

[0050] An extension is needed to have a common set R for all slots. When a common set R is constructed for all slots, the set R can be constructed, stored, and applied for the type-1 HARQ-ACK codebook configuration for any slot. That is, the set R does not need to be constructed in real time when a type-1 HARQ-ACK codebook is needed for a slot.

[0051] The first group of embodiments includes a start symbol S 0In some embodiments, for a type 1 HARQ-ACK codebook, the number of rows in the set R is determined by the number of rows whose starting symbol S0 is the starting symbol S of a monitoring span that includes a PDCCH monitoring occasion where DCI format 1_2 is detected. 0 This effectively requires the gNB to configure all monitoring occasions of a span to start at the same symbol, and the same span pattern to repeat in every slot.

[0052] For example, the slot offset K for PDSCH reception, which is associated with the active downlink bandwidth portion (BWP) and described in TS 38.214 0 a set of table row indices R specifying a respective set of time domain resource allocation table row indices for a DCI format c, where the table row indices R are provided by a set of time domain resource allocation table row indices for a DCI format, and the UE is configured to monitor the PDCCH for a serving cell c, if the UE is provided with ReferenceofSLIV-ForDCIFormat1_2, a slot offset K in the set of table row indices for DCI format 1_2 0 = 0 and for each row index with PDSCH mapping type B [TS 38.214], with a different start symbol in the slot where the UE monitors the PDCCH for DCI format 1_2, the start symbol S 0 For each PDCCH monitoring occasion in the set of PDCCH monitoring occasions with >0, S + S for the normal cyclic prefix 0 +L≦14 and S+S for extended cyclic prefix 0 If +L≦12, the start symbol S of the row index is S+S 0 Add a new row index to the set of row indexes of the table by replacing S 0is the start symbol S of a monitoring span including a PDCCH monitoring occasion where DCI format 1_2 is detected 0 It is.

[0053] A second group of embodiments restricts the applicable scenarios of the Type 1 HARQ-ACK codebook. In some embodiments, the applicable scenarios of the Type 1 HARQ-ACK codebook are restricted to some cases depending on the configuration of new references for SLIV and / or PDCCH monitoring occasions.

[0054] In some embodiments, the gNB configures the Type 1 HARQ-ACK codebook only if relative SLIV is not applied, i.e., the UE is not provided with ReferenceofSLIV-ForDCIFormat1_2.

[0055] In some embodiments, the gNB configures a type 1 HARQ-ACK codebook with relative SLIV only if the starting symbol of the PDCCH monitoring occasion is set to the same in all slots. In a particular embodiment, the monitoring occasion is allowed to be absent in a given slot, and the starting symbol of the PDCCH monitoring occasion is set to the same in all slots if not absent. This variation is illustrated in FIG. 5, which is described in more detail below.

[0056] FIG. 3 is a timing diagram illustrating an example of configured monitoring occasions, where each slot has a monitoring occasion with a different starting symbol (arrow), which may cause the set R to become very large when using relative SLIV. FIG. 3 illustrates monitoring occasions in three slots (slots j, (j+1), (j+2)). The number of monitoring occasions in each slot, as well as the starting symbols of the monitoring occasions in each slot, are all different. This may cause the set R to become very large when using relative SLIV.

[0057] FIG. 4 is a timing diagram illustrating an example of monitoring occasions that are configured, where each slot has a monitoring occasion with the same starting symbol (e.g., symbols 1, 5, 10), without unnecessarily causing R to become large. As shown, constraints are applied to the CORESET and / or search space configuration so that the starting symbols of the monitoring occasions in each slot are the same. Note that the ending symbols of the monitoring occasions in each slot do not have to be the same. For example, monitoring occasions with starting symbol=1 in three slots end at symbols #3, #1, and #2, respectively.

[0058] A third group of embodiments forms the set R by dividing all possible starting symbols S of the PDCCH monitoring occasions in all slots. 0 In some embodiments, for a Type 1 HARQ-ACK codebook, the set R is a set of all possible starting symbols S of a PDCCH monitoring occasion according to all search space set configurations across slots. 0 The row index derived from the slot offset K 0 For each row index in the TDRA table for DCI format 1_2 with PDSCH mapping type B and PDCCH monitoring occasions in the search space set of DCI format 1_2, 0 For row index start symbol S, let S+S 0 Add a new row index by replacing

[0059] Here, the difference from the existing specification is that all start symbols S of the PDCCH monitoring occasion according to all search space set configurations across slots are 0 Note that, instead of only those from within the slot,

[0060] For example, the slot offset K for PDSCH reception associated with an active downlink BWP and described in [TS 38.214] 0 a set of table row indices R specifying a respective set of time domain resource allocation table row indices for a DCI format c, where the table row indices R are provided by a set of time domain resource allocation table row indices for a DCI format, and the UE is configured to monitor the PDCCH for a serving cell c, if the UE is provided with ReferenceofSLIV-ForDCIFormat1_2, a slot offset K in the set of table row indices for DCI format 1_2 0 For each row index with PDSCH mapping type B and DCI format 1_2, the UE monitors the PDCCH for DCI format 1_2 with a different start symbol [TS 38.214]. 0 For each PDCCH monitoring occasion in the set of PDCCH monitoring occasions over slots with >0, S + S 0 +L≦14 and S+S for extended cyclic prefix 0 If +L≦12, the start symbol S of the row index is S+S 0 Add a new row index into the set of row indexes for the table by replacing

[0061] Some embodiments support set R varying from slot to slot. For example, set R is not required to be the same across slots. Instead, set R can vary from slot to slot based on the monitoring occasion configuration in each slot. This is versatile, but results in the number of HARQ-ACK bits in each slot varying for a given component carrier.

[0062] In this method, when configuring a HARQ-ACK codebook for a given slot, set R is custom built based on the monitoring occasion setting of the relevant downlink slot, where the downlink slot contains a potential PDSCH to which the HARQ-ACK responds. This prevents the UE from preparing and storing set R in advance and using set R for any slot. That is, set R needs to be built in real time when a Type 1 HARQ-ACK codebook is needed for a particular slot.

[0063] For example, the slot offset K for PDSCH reception associated with an active downlink BWP and described in [TS 38.214] 0 , for a set of table row indices R′ specifying a respective set of start and length indicators SLIV, and PDSCH mapping types, where the table row indices R′ are provided by a set of time domain resource allocation table row indices for a DCI format, the UE is configured to monitor a PDCCH for a serving cell c, set j=0 - an index of an occasion for candidate PDSCH reception or SPS PDSCH release, set B=φ , JPEG0007602633000002.jpg33170 In descending order of slot timing value, If the UE is not provided with ca-SlotOffset for the serving cell of the PDSCH reception and for the serving cell of the corresponding PUCCH transmission with HARQ-ACK information, JPEG0007602633000004.jpg set to set of 42170 lines R .

[0064] If ReferenceofSLIV-ForDCIFormat1_2 is not provided, then set R is equal to set R'. Otherwise, set R is obtained from R' by adding a new row with ReferenceofSLIV-ForDCIFormat1_2. Initialize set R to R'. If the UE is provided with ReferenceofSLIV-ForDCIFormat1_2, then the slot offset K in the set of table row indexes for DCI format 1_2 0 = 0 and for each row index with PDSCH mapping type B [TS 38.214], DL slot n where the UE monitors the PDCCH for DCI format 1_2 D with different start symbols in 0 For each PDCCH monitoring occasion in the set of PDCCH monitoring occasions with >0, S + S for the normal cyclic prefix 0 +L≦14 and S+S for extended cyclic prefix 0 If +L≦12, the start symbol S of the row index is S+S 0 Add a new row index to the set of row indexes R' of the table by replacing K 0 When receiving a PDSCH scheduled by DCI format 1_2 with C-RNTI, MCS-C-RNTI, CRC scrambled by CS-RNTI with 0 and PDSCH mapping type B, the start symbol S is the start symbol S of the PDCCH monitoring occasion in which DCI format 1_2 is detected. 0 This is in response to. R Set to cardinality of C(R) , set r=0 -set R The index of the row in JPEG0007602633000005.jpg7170 Serving cell cand starting at or after a slot for an active DL BWP change on the PCell or an active UL BWP change on the PCell, JPEG0007602633000006.jpg12170 Serving cell c slot if it is before a slot for an active DL BWP change on the PCell, or a slot for an active UL BWP change on the PCell, nD = nD + 1, Otherwise, on the other hand, r<C(R) .

[0065] Due to the search space configuration by the gNB, the set of monitoring occasions may or may not be present in all slots while satisfying the requirement to monitor all slots with the same (X, Y). An example is illustrated in Figure 5.

[0066] 5 is a timing diagram illustrating an example of configured monitoring occasions, where each slot has a monitoring occasion with the same starting symbol (e.g., symbols 1, 5, and 10) if a monitoring occasion is present in the slot. A monitoring occasion is allowed to be absent in a slot. As shown, slot (j+1) does not include any monitoring occasion, and slot (j+2) does not include a monitoring occasion for starting symbol #5.

[0067] For cases involving absent monitoring occasions, in some embodiments, the collection of starting symbols of the monitoring occasions across all slots is used in constructing the set R. This allows a common set of R to be used in constructing the Type-1 HARQ-ACK codebook regardless of the slot (or sub-slot) index for the HARQ-ACK transmission when using relative SLIV. As a result, in a given downlink slot, entries are added to the set R for absent monitoring occasions even if these monitoring occasions do not exist for potential PDCCHs that may schedule PDSCH transmissions.

[0068] In some embodiments, unattended monitoring occasions are skipped when constructing set R, i.e., unattended monitoring occasions do not add any rows to set R. This controls the size of set R by filtering out useless rows. As a result, set R may vary from slot to slot.

[0069] For time division duplex (TDD) (also known as unpaired spectrum) or half-duplex frequency division duplex (FDD), the UE does not monitor configured monitoring occasions that overlap with symbols specified for downlink symbols. Such monitoring occasions are considered absent monitoring occasions and may be processed using the methods described for absent monitoring occasions.

[0070] Other reasons besides TDD and half-duplex FDD may also cause the UE to not monitor some monitoring occasions, for example pre-configured monitoring occasions that overlap with guard symbols, symbols for monitoring MIB or SIB1, etc. Such monitoring occasions may be considered as absent monitoring occasions and may be handled using the methods described for absent monitoring occasions.

[0071] Some embodiments include S 0 When constructing the Type-1 HARQ-ACK codebook, all row indices in the set R (containing all possible PDSCH reception candidates in a slot) are considered and pruned so that only non-overlapping PDSCH reception candidates contribute to the overall codebook size.

[0072] For a new relative SLIV based on the starting symbol of the PDCCH monitoring occasion, the set R is 0 It is possible that the set R contains multiple overlapping PDSCH reception candidates due to multiple possible values ​​of . This can be avoided when constructing the set R.

[0073] In some embodiments, the set of row indices R is such that the new row is 0 The set R is formed in such a way that a new row is added only if it does not result in a PDSCH reception candidate that overlaps with other PDSCH reception candidates with other possible values ​​of A. An example for forming the set R by adding new rows according to this method is provided below.

[0074] Start symbol S, length L, slot offset K 0 For each row index of the TDRA table for DCI format 1_2 with PDSCH mapping type B and 0, (in ascending order of symbol index from the set of all possible starting symbols of the PDCCH monitoring occasion in or across slots) 0 >0, S+S for normal cyclic prefix 0 +L≦14 and S+S for extended cyclic prefix 0 +L≦12, S+S 0 ≧S+S 0,previous +L (where S 0,previous But the new added row is not added to the previous S 0 , add a new row index to set R if

[0075] There are other cases where the PDCCH monitoring occasions are not actually monitored. For a given RRC configuration and search space set of CORESET, overbooking may occur in a slot where the UE monitoring limit is exceeded. The UE monitoring limit includes the blind decoding limit and the CCE limit. When the configuration causes the UE monitoring limit to be exceeded, the UE starts dropping search spaces or PDCCH candidates so that the UE does not have to monitor PDCCH candidates beyond the UE's capabilities.

[0076] When overbooking causes dropping of monitoring occasions and a monitoring occasion is no longer present at the starting symbol otherwise intended, in some embodiments, the monitoring occasions for constructing set R follow the RRC configuration and search space set of CORESET. Overbooking does not affect the configuration of set R. The advantage of this method is the simplicity of the configuration of set R; the same set of R can be constructed to cover all slots.

[0077] In some embodiments, the construction of set R takes into account starting symbols for which the UE no longer has any monitoring occasions to monitor. For example, such starting symbols and associated monitoring occasions are skipped in constructing set R. The advantage is a finely tuned set R with useless rows excluded. The consequence is the complexity of the construction of R and the likelihood that set R will vary from slot to slot.

[0078] FIG. 6 illustrates an exemplary wireless network, according to some embodiments. The wireless network may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or wireless network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, certain embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, wireless local area network (WLAN) standards, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0079] The network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0080] The network node 160 and the WD 110 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0081] As used herein, a network node refers to a device capable of, set up, configured, and / or operable to communicate, directly or indirectly, with wireless devices and / or other network nodes or equipment in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the wireless network.

[0082] Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated another way, their transmit power level), in which case they may also be referred to as femto, pico, micro, or macro base stations.

[0083] A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which may be referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may be referred to as a node in a distributed antenna system (DAS). Still further examples of network nodes include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT.

[0084] As another example, a network node may be a virtual network node, as described in more detail below, but more generally, a network node may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0085] 6, network node 160 includes processing circuitry 170, device-readable medium 180, interface 190, ancillary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIG. 6 may represent a device including the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

[0086] It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, although the components of network node 160 are depicted as a single box located within a larger box, or as a single box nested within multiple boxes, in reality a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0087] Similarly, the network node 160 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In some scenarios in which the network node 160 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some instances.

[0088] In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into network node 160. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within network node 160.

[0089] The processing circuitry 170 is configured to perform any of the decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuitry 170 may include processing information acquired by the processing circuitry 170, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored in the network node, and / or performing one or more operations based on the acquired or transformed information and as a result of the processing making a decision.

[0090] The processing circuitry 170 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resources, or combinations of hardware, software, and / or coded logic operable to provide network node 160 functionality, either alone or in conjunction with other network node 160 components, such as device readable medium 180.

[0091] For example, processing circuitry 170 may execute instructions stored on device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

[0092] In some embodiments, the processing circuitry 170 may include one or more of a radio frequency (RF) transceiver circuitry 172 and a baseband processing circuitry 174. In some embodiments, the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or set of chips, board, or unit.

[0093] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 170 executing instructions stored in the device-readable medium 180, or in memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 170 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 170 alone, or by other components of the network node 160, but by the network node 160 as a whole, and / or by end users and wireless networks in general.

[0094] The device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory, including, but not limited to, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 170. The device readable medium 180 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 170 and utilized by the network node 160. The device readable medium 180 may be used to store any calculations performed by the processing circuit 170 and / or any data received via the interface 190. In some embodiments, the processing circuit 170 and the device-readable medium 180 may be considered to be integrated.

[0095] The interface 190 is used in wired or wireless communication of signaling and / or data between the network node 160, the network 106, and / or the WD 110. As shown, the interface 190 includes a port / terminal 194 for sending and receiving data to and from the network 106, e.g., over a wired connection. The interface 190 also includes radio front-end circuitry 192, which is coupled to the antenna 162 or, in some embodiments, may be part of the antenna 162.

[0096] The radio front-end circuit 192 comprises a filter 198 and an amplifier 196. The radio front-end circuit 192 may be connected to the antenna 162 and the processing circuit 170. The radio front-end circuit may be configured to condition signals communicated between the antenna 162 and the processing circuit 170. The radio front-end circuit 192 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of the filter 198 and / or the amplifier 196. The radio signal may then be transmitted via the antenna 162. Similarly, when receiving data, the antenna 162 may collect the radio signal, which is then converted into digital data by the radio front-end circuit 192. The digital data may be passed to the processing circuit 170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0097] In some alternative embodiments, the network node 160 may not include a separate radio front-end circuit 192; instead, the processing circuit 170 may comprise a radio front-end circuit and be connected to the antenna 162 without a separate radio front-end circuit 192. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 172 may be considered part of the interface 190. In still other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front-end circuit 192, and the RF transceiver circuit 172 as part of a radio unit (not shown), and the interface 190 may communicate with a baseband processing circuit 174 that is part of a digital unit (not shown).

[0098] The antenna 162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 162 may be coupled to the radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices in a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, the antenna 162 may be separate from the network node 160 and may be connectable to the network node 160 through an interface or port.

[0099] The antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any receiving operation and / or any acquisition operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0100] The power circuitry 187 may comprise or be coupled to a power management circuitry and is configured to supply power to the components of the network node 160 for performing the functions described herein. The power circuitry 187 may receive power from a power source 186. The power source 186 and / or the power circuitry 187 may be configured to provide power to the various components of the network node 160 in a form suitable for the respective components (e.g., at voltage and current levels required for each respective component). The power source 186 may either be included in the power circuitry 187 and / or the network node 160 or be external to the power circuitry 187 and / or the network node 160.

[0101] For example, network node 160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to power circuit 187. As a further example, power source 186 may comprise a power source in the form of a battery or battery pack connected to or integrated within power circuit 187. The battery may provide backup power in the event that the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0102] Alternative embodiments of network node 160 may include additional components other than those shown in FIG. 6 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface devices to enable input of information into network node 160 and output of information from network node 160. This may enable a user to perform diagnostics, maintenance, repair, and other administrative functions for network node 160.

[0103] As used herein, a wireless device (WD) refers to a device capable of, set up, configured, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably with user equipment (UE) herein. Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air.

[0104] In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network.

[0105] Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device.

[0106] As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node. The WD may in this case be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As an example, the WD may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.).

[0107] In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status and / or other functions associated with its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Moreover, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0108] As shown, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device-readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chips or sets of chips as other components in WD 110.

[0109] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be separate from WD 110 and connectable to WD 110 through an interface or port. Antenna 111, interface 114, and / or processing circuit 120 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuit and / or antenna 111 may be considered an interface.

[0110] As shown, the interface 114 comprises a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 comprises one or more filters 118 and an amplifier 116. The radio front-end circuit 114 is connected to the antenna 111 and the processing circuit 120 and is configured to condition signals communicated between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to or part of the antenna 111. In some embodiments, the WD 110 may not include a separate radio front-end circuit 112; rather, the processing circuit 120 may comprise a radio front-end circuit and be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered part of the interface 114.

[0111] The radio front-end circuit 112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 118 and / or amplifiers 116. The radio signal may then be transmitted via the antenna 111. Similarly, when receiving data, the antenna 111 may collect the radio signal, which is then converted into digital data by the radio front-end circuit 112. The digital data may be passed to the processing circuit 120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0112] Processing circuitry 120 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide WD 110 functionality, either alone or in conjunction with other WD 110 components, such as device readable medium 130. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored on device readable medium 130 or in memory within processing circuitry 120 to provide functionality disclosed herein.

[0113] As shown, the processing circuitry 120 includes one or more of an RF transceiver circuitry 122, a baseband processing circuitry 124, and an application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and / or different combinations of components. In some embodiments, the processing circuitry 120 of the WD 110 may comprise a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or sets of chips.

[0114] In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined into one chip or set of chips, and the RF transceiver circuitry 122 may be on a separate chip or set of chips. In further alternative embodiments, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or set of chips, and the application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 122 may be part of the interface 114. The RF transceiver circuitry 122 may condition the RF signals for the processing circuitry 120.

[0115] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by processing circuitry 120 executing instructions stored on device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner.

[0116] In any of those particular embodiments, whether or not the processing circuitry 120 executes instructions stored on a device-readable storage medium, the processing circuitry 120 may be configured to perform the described functions, and the benefits provided by such functions are enjoyed by the WD 110, and / or by end users and wireless networks generally, but not limited to the processing circuitry 120 alone or other components of the WD 110.

[0117] Processing circuitry 120 may be configured to perform any of the decision, calculation, or similar operations (e.g., some of the acquisition operations) described herein as being performed by a WD. These operations as performed by processing circuitry 120 may include processing information acquired by processing circuitry 120, for example, by transforming the acquired information to other information, comparing the acquired or transformed information to information stored by WD 110, and / or performing one or more operations based on the acquired or transformed information and as a result of said processing making a decision.

[0118] The device-readable medium 130 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 120. The device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 120. In some embodiments, the processing circuit 120 and the device-readable medium 130 may be integrated.

[0119] The user interface devices 132 may provide components that allow a human user to interact with the WD 110. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface devices 132 may be operable to produce output to a user and to allow a user to provide input to the WD 110. The type of interaction may vary depending on the type of user interface devices 132 installed on the WD 110. For example, if the WD 110 is a smartphone, the interaction may be via a touch screen, if the WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected).

[0120] The user interface device 132 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 132 is configured to enable input of information to the WD 110 and is connected to the processing circuit 120 to enable the processing circuit 120 to process the input information. The user interface device 132 may include, for example, a microphone, proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 132 is also configured to enable output of information from the WD 110 and to enable the processing circuit 120 to output information from the WD 110. The user interface device 132 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 132, the WD 110 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functionality described herein.

[0121] The auxiliary device 134 is operable to provide more specific functionality that may not typically be implemented by a WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication, such as wired communication, etc. The inclusion of components of the auxiliary device 134 and the types of components of the auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0122] The power source 136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD 110 may further include a power circuit 137 for delivering power from the power source 136 to various portions of the WD 110 that require power from the power source 136 to perform any of the functions described or indicated herein. The power circuit 137 may include a power management circuit in some embodiments.

[0123] Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source, in which case WD 110 may be connectable to the external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. Power circuitry 137 may also be operable in some embodiments to deliver power from the external power source to power source 136. This may be for charging power source 136, for example. Power circuitry 137 may perform any formatting, conversion, or other modification on the power from power source 136 to make it suitable for the respective components of WD 110 to be powered.

[0124] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network illustrated in FIG. 6. For simplicity, the wireless network of FIG. 6 depicts only network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or through the wireless network.

[0125] FIG. 7 illustrates an example user equipment according to some embodiments. As used herein, user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE 200 illustrated in Figure 7 is an example of a WD configured for communication according to one or more communications standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 7 is a UE, the components discussed herein are equally applicable to a WD and vice versa.

[0126] In FIG. 7, UE 200 includes processing circuitry 201 operatively coupled to input / output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read only memory (ROM) 219, storage medium 221, etc., communication subsystem 231, power source 233, and / or any other components, or any combination thereof. Storage medium 221 includes operating system 223, application programs 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may use all of the components shown in FIG. 7 or only a subset of the components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0127] In Fig. 7, the processing circuit 201 may be configured to process computer instructions and data. The processing circuit 201 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), one or more stored programs, such as programmable logic with appropriate firmware, a microprocessor or digital signal processor (DSP) with appropriate software, a general-purpose processor, or any combination of the above. For example, the processing circuit 201 may include two central processing units (CPUs). The data may be information in a format suitable for use by a computer.

[0128] In the depicted embodiment, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or an input / output device. The UE 200 may be configured to use an output device via the input / output interface 205.

[0129] An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from the UE 200. An output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof.

[0130] The UE 200 may be configured to use input devices via the input / output interface 205 to allow a user to capture information into the UE 200. The input devices may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from the user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0131] In FIG. 7, the RF interface 209 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 211 may be configured to provide a communication interface to a network 243a. The network 243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another like network, or any combination thereof. For example, the network 243a may comprise a Wi-Fi network. The network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 211 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0132] RAM 217 may be configured to interface to processing circuit 201 via bus 202 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuit 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, that is stored in non-volatile memory.

[0133] The storage medium 221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 221 may be configured to include an operating system 223, an application program 225, such as a web browser application, a widget or gadget engine, or another application, and data files 227. The storage medium 221 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 200.

[0134] The storage medium 221 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 may enable the UE 200 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 221, and the storage medium 221 may comprise a device-readable medium.

[0135] In FIG. 7, the processing circuit 201 may be configured to communicate with the network 243b using the communication subsystem 231. The networks 243a and 243b may be the same network or networks or different networks or networks. The communication subsystem 231 may be configured to include one or more transceivers used to communicate with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 233 and / or a receiver 235 for implementing transmitter or receiver functions, respectively, appropriate for the RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 233 and receiver 235 of each transceiver may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0136] In the illustrated embodiment, the communication capabilities of the communication subsystem 231 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another like communication capability, or any combination thereof. For example, the communication subsystem 231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another like network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 213 may be configured to provide alternating current (AC) power or direct current (DC) power to the components of the UE 200.

[0137] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 200 or split across multiple components of the UE 200. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 231 may be configured to include any of the components described herein. Furthermore, the processing circuit 201 may be configured to communicate with any of such components over the bus 202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit 201, perform the corresponding functions described herein. In another example, the functions of any of such components may be split between the processing circuit 201 and the communication subsystem 231. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0138] 8 is a flow chart illustrating an example method in a wireless device according to some embodiments. In a particular embodiment, one or more steps of FIG. 8 may be performed by the wireless device 110 described with respect to FIG. 6. The wireless device may operate in a wireless network in which physical PDCCH monitoring occasions vary by slot.

[0139] The method begins at step 812, where a wireless device (e.g., wireless device 110) obtains a starting symbol S of a physical downlink shared channel (PDSCH), where S relates to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled. For example, the wireless device may receive a SLIV value, such as referenceOfSLIVForDCI-Format1-2-r16, from a network node, such as network node 160. The wireless device may obtain S according to any of the embodiments and examples described herein.

[0140] In step 814, the wireless device derives a type 1 HARQ-ACK codebook based on the starting symbol S. There are various options for deriving the HARQ-ACK codebook. The wireless device may derive the HARQ-ACK codebook according to any of the embodiments and examples described herein. Some examples are as follows:

[0141] In a particular embodiment, deriving a Type 1 HARQ-ACK codebook includes deriving a Type 1 HARQ-ACK codebook for PDSCH reception with possible starting symbols of PDCCH monitoring occasions (e.g., slot offset K 0 , the starting symbol for the PDSCH slot boundary and length, and the PDSCH mapping type.

[0142] In certain embodiments, the set R is common for all slots. In some embodiments, all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in all slots, and the starting symbol S is for the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled. In some embodiments, the type 1 HARQ-ACK codebook is derived only if the starting symbol of the PDCCH monitoring occasion is set to the same in all slots. If a PDCCH monitoring occasion is absent in some slots, the type 1 HARQ-ACK codebook may be derived only if the starting symbol of the PDCCH monitoring occasion, if not absent, is set to the same in all slots. In some embodiments, the set R includes entries derived from all starting symbols of the PDCCH monitoring occasions across all slots.

[0143] In a particular embodiment, the set R varies across slots.

[0144] In certain embodiments, deriving the set R may include being based on monitoring limits of the wireless device and / or avoiding entries that result in overlapping PDSCH reception candidates.

[0145] In step 916, the wireless device transmits one or more HARQ-ACKs to the network node based on the HARQ-ACK codebook.

[0146] Modifications, additions, or omissions may be made to the method 800 of Figure 8. Additionally, one or more steps in the method of Figure 8 may be performed in parallel or in any suitable order.

[0147] 9 is a flow chart illustrating an example method in a network node according to some embodiments. In a particular embodiment, one or more steps of FIG. 9 may be performed by the network node 160 described with respect to FIG. 6. The network node may operate in a wireless network in which PDCCH monitoring occasions vary by slot.

[0148] The method begins in step 912, where a network node (e.g., network node 160) transmits a starting symbol S of a PDSCH to a wireless device, where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled. An example of S is described with respect to FIG.

[0149] In step 914, the network node receives a HARQ-ACK from the wireless device based on the HARQ-ACK codebook and the starting symbol S. The HARQ-ACK codebook is described with respect to FIG.

[0150] Modifications, additions, or omissions may be made to the method 900 of Figure 9. Additionally, one or more steps in the method of Figure 9 may be performed in parallel or in any suitable order.

[0151] FIG. 10 illustrates a schematic block diagram of two apparatuses in a wireless network (e.g., the wireless network illustrated in FIG. 6). The apparatuses include a wireless device and a network node (e.g., the wireless device 110 and the network node 160 illustrated in FIG. 6). The apparatuses 1600 and 1700 are operable to perform the example methods described with reference to FIG. 8 and FIG. 9, respectively, as well as, possibly, any other processes or methods disclosed herein. It should also be understood that the methods of FIG. 8 and FIG. 9 are not necessarily performed solely by the apparatus 1600 and / or the apparatus 1700. At least some operations of the methods may be performed by one or more other entities.

[0152] The virtual devices 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory, in several embodiments, includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for implementing one or more of the techniques described herein.

[0153] In some implementations, the processing circuitry may be used to cause the acquisition module 1602, the determination module 1604, the transmission module 1606, and any other suitable units of the device 1600 to perform corresponding functions according to one or more embodiments of the present disclosure. Similarly, the processing circuitry described above may be used to cause the reception module 1702, the transmission module 1706, and any other suitable units of the device 1700 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0154] As shown in Fig. 10, the apparatus 1600 includes an acquisition module 1602 configured to acquire a starting symbol S of a PDSCH, where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled. The determination module 1604 is configured to determine a HARQ-ACK codebook according to any of the embodiments and examples described herein. The apparatus 1600 also includes a transmission module 1606 configured to transmit a HARQ-ACK to a network node according to any of the embodiments and examples described herein.

[0155] 10, the apparatus 1700 includes a receiving module 1702 configured to receive a HARQ-ACK from a wireless device in accordance with any of the embodiments and examples described herein. The apparatus 1700 also includes a transmitting module 1706 configured to transmit a starting symbol S of a PDSCH to the wireless device in accordance with any of the embodiments and examples described herein, where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled.

[0156] FIG. 11 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or a component of that device, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0157] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0158] The functionality may be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 are run in a virtualization environment 300, which provides hardware 330 comprising processing circuitry 360 and memory 390. The memory 390 includes instructions 395 executable by the processing circuitry 360 such that the applications 320 are operable to provide one or more of the features, functions, and / or benefits of the embodiments disclosed herein.

[0159] The virtualization environment 300 includes general-purpose or dedicated network hardware devices 330 that include a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated application specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include memory 390-1, which may be a non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device may include one or more network interface controllers (NICs), also known as network interface cards, 370, which include physical network interfaces 380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 390-2 that stores software 395 and / or instructions executable by the processing circuitry 360. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also called hypervisors), software for running virtual machines 340, and software that enables it to perform the functions, features and / or benefits described in connection with some of the embodiments described herein.

[0160] The virtual machines 340 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the virtual appliance 320 instances may be implemented on one or more of the virtual machines 340, and the implementation may be done in different ways.

[0161] During operation, the processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which is sometimes referred to as a virtual machine monitor (VMM). The virtualization layer 350 may present to the virtual machines 340 a virtual operating platform that looks like networking hardware.

[0162] 11, the hardware 330 may be a standalone network node with generic or specific components. The hardware 330 may include an antenna 3225 and may implement some functions via virtualization. Alternatively, the hardware 330 may be part of a larger cluster of hardware (e.g., as in the case of a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via a management and orchestration (MANO) 3100 that, among other things, oversees the lifecycle management of the application 320.

[0163] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0164] In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each virtual machine 340 and the portion of hardware 330 on which it runs, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of virtual machines 340, form a separate Virtual Network Element (VNE).

[0165] Further in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to application 320 in FIG. 18.

[0166] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware node 330 via one or more appropriate network interfaces and may be used in combination with a virtualization component to provide a virtual node with wireless capabilities, such as a wireless access node or base station.

[0167] In some embodiments, some signaling may be accomplished using the control system 3230, which may alternatively be used for communication between the hardware nodes 330 and the wireless unit 3200.

[0168] Referring to Fig. 12, according to an embodiment, a communication system includes a communication network 410, such as a 3GPP type cellular network, comprising an access network 411, such as a wireless access network, and a core network 414. The access network 411 comprises a number of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 over a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is configured to wirelessly connect to the corresponding base station 412c or to be paged by the corresponding base station 412c. A second UE 492 in the coverage area 413a can be wirelessly connected to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area or is connected to a corresponding base station 412.

[0169] The communication network 410 is itself connected to a host computer 430, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 430 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. The connections 421 and 422 between the communication network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430, or may proceed through an optional intermediate network 420. The intermediate network 420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 420 may be a backbone network or the Internet, if any, and in particular the intermediate network 420 may comprise two or more sub-networks (not shown).

[0170] The communication system of FIG. 12 as a whole enables connectivity between connected UEs 491, 492 and a host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. The host computer 430 and connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450 using the access network 411, the core network 414, any intermediate networks 420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 450 may be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 412 may not or need not be informed of the past routing of incoming downlink communications involving data originating from the host computer 430 to be forwarded (e.g., handed over) to the connected UE 491. Similarly, the base station 412 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 491 and destined for the host computer 430 .

[0171] FIG. 13 illustrates an exemplary host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments. Next, an exemplary implementation according to the UE, base station and host computer embodiments discussed in the previous paragraph will be described with reference to FIG. 13. In the communication system 500, the host computer 510 comprises hardware 515 including a communication interface 516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 500. The host computer 510 further comprises a processing circuit 518, which may have storage and / or processing capabilities. In particular, the processing circuit 518 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof adapted to execute instructions (not shown). The host computer 510 further comprises software 511, which is stored in or accessible by the host computer 510 and executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to a remote user, such as a UE 530 that connects via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to the remote user, the host application 512 may provide user data that is transmitted using the OTT connection 550.

[0172] The communication system 500 further includes a base station 520 provided in the communication system, the base station 520 comprising hardware 525 enabling the base station 520 to communicate with the host computer 510 and the UE 530. The hardware 525 may include a communication interface 526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 500, as well as a wireless interface 527 for setting up and maintaining at least a wireless connection 570 with a UE 530 located in a coverage area (not shown in FIG. 13) served by the base station 520. The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct, or the connection 560 may pass through a core network (not shown in FIG. 13) of the communication system and / or one or more intermediate networks outside the communication system. In the embodiment shown, the hardware 525 of the base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 520 further has software 521 stored internally or accessible via an external connection.

[0173] The communication system 500 further includes the UE 530 already mentioned. The hardware 535 of the UE 530 may include a wireless interface 537 configured to set up and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 further includes a processing circuit 538, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof adapted to execute instructions (not shown). The UE 530 further includes software 531 stored in or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to a human or non-human user via the UE 530 with the support of the host computer 510. At the host computer 510, a running host application 512 may communicate with a running client application 532 via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to a user, the client application 532 may receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 may transfer both the request data and the user data. The client application 532 may interact with the user to generate the user data that the client application 532 provides.

[0174] It should be noted that the host computer 510, base station 520 and UE 530 illustrated in Figure 13 may be similar or equivalent to the host computer 430, one of the base stations 412a, 412b, 412c, and one of the UEs 491, 492, respectively, of Figure 6. That is, the inner workings of these entities may be as shown in Figure 13, and separately, the surrounding network topology may be that of Figure 6.

[0175] 13, the OTT connection 550 is depicted abstractly to illustrate communication between the host computer 510 and the UE 530 via the base station 520, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, which may be configured to hide the routing from the UE 530 or from the service provider operating the host computer 510, or both. The network infrastructure may also decide to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 550 is active.

[0176] The wireless connection 570 between the UE 530 and the base station 520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 530 using the OTT connection 550 of which the wireless connection 570 forms the final segment. More precisely, the teachings of these embodiments may improve signaling overhead and reduce latency, thereby providing benefits such as reduced user latency, better responsiveness, and extended battery life.

[0177] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510, or in the software 531 and hardware 535 of the UE 530, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 550 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 511, 531 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 520, and the reconfiguration may be unknown or imperceptible to the base station 520. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 510 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 511 and 531 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 550 while the software 511 and 531 monitors propagation times, errors, etc.

[0178] Figure 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 12 and 13. For simplicity of the disclosure, only drawing references to Figure 14 are included in this section.

[0179] In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0180] Figure 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 12 and 13. For simplicity of the disclosure, only drawing references to Figure 15 are included in this section.

[0181] In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via a base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0182] Figure 16 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 12 and 13. For simplicity of the disclosure, only drawing references to Figure 16 are included in this section.

[0183] In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data was provided, the UE initiates transmission of the user data to the host computer in sub-step 830 (which may be optional). In method step 840, the host computer receives the user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0184] Figure 17 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 12 and 13. For simplicity of the disclosure, only drawing references to Figure 17 are included in this section.

[0185] In step 910 (which may be optional), the base station receives user data from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0186] The term unit may have its conventional meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid state and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, etc., such as those described herein.

[0187] Modifications, additions, or omissions may be made to the systems and devices disclosed herein without departing from the scope of the invention. Components of the systems and devices may be integrated or separated. Moreover, operations of the systems and devices may be performed by more, fewer, or other components. Additionally, operations of the systems and devices may be performed using any suitable logic, including software, hardware, and / or other logic. As used herein, "each" refers to each member of a set or each member of a subset of a set.

[0188] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, the steps may be performed in any suitable order.

[0189] The above description sets forth numerous specific details. However, it should be understood that the embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those skilled in the art will be able to use the included description to implement the appropriate functionality without undue experimentation.

[0190] References herein to "one embodiment," "an embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, it is submitted that when a particular feature, structure, or characteristic is described with respect to an embodiment, it is within the knowledge of one of ordinary skill in the art to implement such feature, structure, or characteristic with respect to other embodiments, whether or not explicitly described.

[0191] Although the present disclosure has been described with respect to some embodiments, modifications and substitutions of the embodiments are obvious to those skilled in the art. Therefore, the above description of the embodiments does not limit the present disclosure. Other changes, substitutions, and modifications are possible without departing from the scope of the present disclosure, which is defined by the following claims.

Claims

1. A method implemented by a wireless device capable of operating in a wireless network in which multiple physical downlink control channel (PDCCH) monitoring occasions vary by slot, the method comprising: Obtaining 812 a starting symbol S of a physical downlink shared channel (PDSCH), where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled; deriving (814) a type-1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook based on the starting symbol S, where deriving the type-1 HARQ-ACK codebook includes deriving a set R including a plurality of time domain resource allocation (TDRA) entries for PDSCH reception with possible starting symbols of a plurality of PDCCH monitoring occasions; transmitting (816) one or more HARQ-ACKs to a network node based on the HARQ-ACK codebook; A method comprising:

2. The method of claim 1 , wherein the set R is common for all slots.

3. 3. The method of claim 2, wherein all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in every slot, and the starting symbol S is relative to the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled.

4. The method of claim 2 , wherein the type-1 HARQ-ACK codebook is derived only if the starting symbols of multiple PDCCH monitoring occasions are set to the same in all slots.

5. The method described in claim 2, wherein multiple PDCCH monitoring occasions are absent in some slots and the Type 1 HARQ-ACK codebook is derived only if the start symbols of multiple PDCCH monitoring occasions, if not absent, are set to the same in all slots.

6. 3. The method of claim 2, wherein the set R includes a plurality of entries derived from all starting symbols of a plurality of PDCCH monitoring occasions across all slots.

7. The method of claim 1 , wherein the set R varies across slots.

8. The method of claim 1 , wherein deriving the set R is based on a monitoring limit of the wireless device.

9. 2. The method of claim 1, wherein deriving the set R includes avoiding multiple entries that result in multiple overlapping PDSCH reception candidates.

10. A wireless device (110) capable of operating in a wireless network in which a plurality of physical downlink control channel (PDCCH) monitoring occasions vary by slot, the wireless device comprising: Obtaining a starting symbol S of a physical downlink shared channel (PDSCH), where S is relative to a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled; deriving a type-1 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook based on the starting symbol S, wherein deriving the type-1 HARQ-ACK codebook includes deriving a set R containing a plurality of time domain resource allocation (TDRA) entries for PDSCH reception with possible starting symbols of a plurality of PDCCH monitoring occasions; transmitting one or more HARQ-ACKs to a network node based on the HARQ-ACK codebook; A wireless device (110) comprising a processing circuit (120) operable to perform the following:

11. The wireless device of claim 10 , wherein the set R is common for all slots.

12. 12. The wireless device of claim 11, wherein all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in every slot, and the starting symbol S is for the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled.

13. The wireless device of claim 11, wherein the type-1 HARQ-ACK codebook is derived only if a starting symbol of multiple PDCCH monitoring occasions is set to the same in all slots.

14. A wireless device as described in claim 11, wherein multiple PDCCH monitoring occasions are absent in some slots and the Type 1 HARQ-ACK codebook is derived only if the start symbols of multiple PDCCH monitoring occasions, if not absent, are set to the same in all slots.

15. 12. The wireless device of claim 11, wherein the set R includes a number of entries derived from all starting symbols of a number of PDCCH monitoring occasions across all slots.

16. The wireless device of claim 10 , wherein the set R varies across slots.

17. The wireless device of claim 10 , wherein deriving the set R is based on a monitoring limit of the wireless device.

18. 11. The wireless device of claim 10, wherein deriving the set R includes avoiding entries that result in overlapping PDSCH reception candidates.

19. A method implemented by a network node capable of operating in a wireless network in which multiple physical downlink control channel (PDCCH) monitoring occasions vary by slot, the method comprising: transmitting 912 a start symbol S of a physical downlink shared channel (PDSCH) to the wireless device, where S is for a reference symbol related to a scheduled PDCCH monitoring occasion for the PDSCH; receiving 914 a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) from the wireless device based on a type-1 HARQ-ACK codebook and the starting symbol S, the type-1 HARQ-ACK codebook being derived from a set R containing a plurality of time domain resource allocation (TDRA) entries for PDSCH reception with possible starting symbols of a plurality of PDCCH monitoring occasions; A method comprising:

20. 20. The method of claim 19, wherein the set R is common for all slots.

21. 21. The method of claim 20, wherein all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in every slot, and the starting symbol S is for the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled.

22. The method of claim 20, wherein the type-1 HARQ-ACK codebook is derived only if the starting symbols of multiple PDCCH monitoring occasions are set to the same in all slots.

23. The method of claim 20, wherein multiple PDCCH monitoring occasions are absent in some slots and the Type 1 HARQ-ACK codebook is derived only if the start symbols of multiple PDCCH monitoring occasions, if not absent, are set to the same in all slots.

24. 21. The method of claim 20, wherein the set R includes a number of entries derived from all starting symbols of a number of PDCCH monitoring occasions across all slots.

25. The method of claim 19 , wherein the set R varies across slots.

26. The method of claim 19 , wherein the set R is based on a monitoring limit of the wireless device.

27. 20. The method of claim 19, wherein the set R avoids multiple entries that result in multiple overlapping PDSCH reception candidates.

28. A network node (160) capable of operating in a wireless network in which a plurality of physical downlink control channel (PDCCH) monitoring occasions vary by slot, the network node comprising: transmitting a start symbol S of a physical downlink shared channel (PDSCH) to the wireless device, where S is for a reference symbol related to a PDCCH monitoring occasion for which the PDSCH is scheduled; receiving a hybrid automatic repeat request (HARQ) acknowledgement (ACK) from the wireless device based on a type-1 HARQ-ACK codebook and the starting symbol S, the type-1 HARQ-ACK codebook being derived from a set R containing a plurality of time domain resource allocation (TDRA) entries for PDSCH reception with possible starting symbols of a plurality of PDCCH monitoring occasions; A network node (160) comprising a processing circuit (170) operable to perform the following:

29. 29. A network node according to claim 28, wherein the set R is common for all slots.

30. 30. The network node of claim 29, wherein all PDCCH monitoring occasions of a span start at the same symbol, the same span pattern repeats in every slot, and the starting symbol S is for the starting symbol of the monitoring span that contains the PDCCH monitoring occasion for which the PDSCH is scheduled.

31. 30. The network node of claim 29, wherein the Type-1 HARQ-ACK codebook is derived only if a starting symbol of multiple PDCCH monitoring occasions is set to the same in all slots.

32. A network node as described in claim 29, wherein multiple PDCCH monitoring occasions are absent in some slots and the Type 1 HARQ-ACK codebook is derived only if the start symbols of multiple PDCCH monitoring occasions, if not absent, are set to the same in all slots.

33. 30. The network node of claim 29, wherein the set R includes a number of entries derived from all starting symbols of a number of PDCCH monitoring occasions across all slots.

34. 29. The network node of claim 28, wherein the set R varies across slots.

35. 29. The network node of claim 28, wherein the set R is based on monitoring limits of the wireless devices.

36. 30. The network node of claim 28, wherein the set R avoids entries that result in overlapping PDSCH reception candidates.

Images