1111111111111111 IIIIII IIIII IIIII IIIII IIII I II Ill lllll lllll lllll lllll lllll 11111111111111111111111
`
`
`0 56 785 
`   
` 

 
`




`
`

 
` 


`  

 !
`
`
`"#$#
`%&'()&*'+,&*-./)(*/
` 0 #

1##21
`BCDEDFG
`34 #

1##
`9:;!:<9=>9:?<@?:<9=A
`H #

 II#J##K
`LMNOFNOONOPNOQNR%NP.NPLNPONPSNPTNPGNSUN
`VWXYZ[Z\]^__`a_bc
`VWXdef[Zf>:<<g?<9A
`ShNSiN%LN%jN%UN%hN%QNkENkDNlONlPNlSNlUNlDN
`VWXYZ[Zm>:<<n?<9A
`VWXdef[WX>:<<g?<9A
`lhNlBNlMNjoNjFNjlNjhNjQNjiNjpNToNTLNTON
`VWXYq[WW>:<<n?<9A
`TPNTlNTUNTBNTrNTpNTMNUoNUPNU%NUENUMN
`ETNDoNDONDPNDSNDjNDGNsoNhENhQNhiNhBNQoN
` # ##21K
`QFNQLNQONQPNQlNQjNQTNQGNQtNQpNGSNGkNGTNGUN
`DFGuR%:<9=u<v<<<n
`GhNGGNGMNioNiPNiQNiMNtFNtUNMoNMTNMB?
` #w##"K
`53 I#"I]xyz{||}~{€‚|{‚yƒ‚„…~{ƒ†‡}€{ˆ{€‰
`<Šk*&/*)‹:<9=><Š?<9?:<9=A
`Œ‚yƒ}‡€{‚}y…zŽ€}~{„~‚}y…ˆ…‚z…z{coh%DE>.BNPSN
`H w##"""K
`PTNlONjhNjQNTBNTMNUoNhBNQLNQjNQGNQMNGMN
`O&‘-+’“
`iPNMTNMBANO/)*’+*&>oTNoMN.pNlPNlMNhiNGkN
`8

1##"#
`O&‘-+’“
`GTANO/),”(*&>ojNoGN.ON.PNFSNFpNFMNLONLlN
`40

##!K
`OONOQNR%NRhNP.NPhNShNSiN%ON%QN%GNjGNjiNjtN
`TFNTlNTGNUjNUENDjNDGNhENhQNQONQ%NQlNQTN
`n:u••:Nn=n
`<vk*&/*)‹:<9@><v?<9?:<9@AiQ
`GhANEoD%>.RN.kNFRNFPNF%NFTNPoNPUNPsNPBN
`7 #K
`–  
`
`—
`˜R%uR%™š
`lTNTjNThNUONQUNGLNGPA?
`l*)*”,)''+ŠN<:n9<O’”,,>R%A?
`7 ›IK
` œID,)''+ž(--,&ž/Ÿ*9:Ng<•v<

1#I K
`l(¡”(-(>R%A?
`
`œ–#D*-,&+(¡(&)*&'*vFnN¢‚~‚y~{€y…~‚}y…z|{…€„€{Ž}€~]£€~a^b]¤cc
`¢{‡}€{~{{¥Ž‚€…~‚}y}‡~{~‚¦{z‚¦‚~‡}€…¦{yƒ‚y~{
`g<v•<E/-/>R%A?
`„z…‚¦|…yƒ~}{€{Žxz‚|{ƒ‚y~{{ˆ{y~}‡€{„{‚Ž~}‡
`73 "K
`–  
`
`—
`('*-šo)+o*)&+,N
`…¦{yƒ¦{y~|]§xz{¨©a^]cc
`%DhL(”*)'¡(&'Nl*)*ž**)+@N<:n9<O’”,,>R%A?
`5 I#"I]xyz{||}~{€‚|{‚yƒ‚„…~{ƒ†‡}€{ˆ{€‰
`Œ‚yƒ}‡y…~‚}y…zŽ€}~{„~‚}y…ˆ…‚z…z{coONoPNojNoTN
`oENoGNoiNoMN.oN..N.PN.SN.UN.hN.BN.pN.MN
`FoNFSNFjNFUNFENFhNFiNFMNLONLkNLlNLTNLEN
`H3 #KQFojo.jOROOL.oFlhODEhG%UP
`H7 1IKt*)+,/’ª,¡¡/&+ª*'+,&’‹’'(¡’¡*‹«(&(¬+'¬),¡'“(
`*””),”)+*'(ª,¡¡/&+ª*'+,&,¬*ªž&,­-(®‘(¡(&'’?R,)(¯*¡”-(N°*)+
`,/’ª,¡¡/&+ª*'+,&’‹’'(¡’N’/ª“*’U(­h*®+,N¡*‹«(&(¬+'¬),¡*
`’ª*-*«-(ª,®(«,,ž’+±(®(¬+&+'+,&+&*’ª(&*)+,­+'“®‹&*¡+ª*--‹°*)‹
`9
`+&‘*ªž&,­-(®‘(¡(&''+¡+&‘?o¡('“,®ª*&+&ª-/®()(ª(+°+&‘*'+¡+&‘
`,¬¬’('°*-/(+&*®,­&-+&ž‘)*&'>g9<A?G“(¡('“,®ª*&*-’,+&ª-/®(
`®('()¡+&+&‘*¬+)’'®,­&-+&ž'+¡(’-,'­+'“+&*¬((®«*ªž­+&®,­«*’(®
`,&'“('+¡+&‘,¬¬’('°*-/(>g:<A?
`%
`w#"
`
`905
`
`Determine Start and
`End Positions of FB
`Window
`
`915
`
`Indicate Start and/or
`End Positions to UE
`in DLGrant
`
`910
`
`980
`
`Receive Timing
`Offset in DL Grant
`
`Receive Total DAI
`Field
`
`1Iage:
`
`920
`
`Determine First DL
`Time Slot within FB
`Window
`
`950
`
`Determine last Time
`Slot of FB Window
`
`960
`
`Determine Size of
`Codebook
`
`970
`
`Transmit FB in
`Window
`
`;;;;;;;;;;;;;;
`;;;;;;;;;;;;;;
`;;;;;;;;;;;;;;
`
`-;;;;;;;;;;;;;; -
`
`- ;
`
`;;;;;;;;;;;;; -
`-;;;;;;;;;;;;;;
`
`;;;;;;;;;;;;;;
`
`1
`
`APPLE 1008
`
`

`

`WO 2018/127628
`
`PCT/FI2018/050006
`
`     
`


` 
` !

"# $$"  #%# $#$%& &

$ '
`
`


`

  $$"  &
` ( $ #)

*$
` +,

"# $$"  #%# $#+#" '#( +
`$%& &

$#   & 


`

# 

( '%$  %,

%
` ( $ $)
`-./012343526782902
`:'



 
`



#'
`
`

; <=>>?( < ?
`'%#  %

#'#
`

  =>># "% $< >@ABCBDA?&

(' '; ,  &%, 
`
`  ' % $
` #&

 #%# $#  "#%#
`

"$
`

 # "
` ACCEF):' #  ',#   '  &

$(


`

## "## 

#+

G"

$ #
` %$ # 

#&=>>
`: =H)IA=)
` JKK J>:J:EK LJ
`

`


`

"

# & '
`

# # #"

+

&

 #'" $  '
` $
`%

(#+('


`"

A "#

 ##  %
`#(

)
`"

M "#

 #*$
` # 

&

 

$E N@& <?
`((&

,

" E N@  + 

  

$$ #)
`"

= "#

 #$
`
`& $  

, "# O&&# #  #+ 

 
` 

$$ #)
`"

P "#

 ## 

( ' (,

" E N@  #+ 

  


`$$ #)
`"

Q "#

 #*$
` $
` $   $$+ 

  


`$$ #)
`"

B "#

 # '

*$
` $
` $  + 

  

$$ #)
`"

D "#

 #*$
` 

%# 

+ 

  

$$ #)
`"

H "#

 #*$
` &



#' + 

  

$$ #)
`"

I "#

 #$ ' 

  

$$ #)
`"

AC "#

 ##%# $ 

  

$$ #)
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`2
`
`

`

`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`DETAILED DESCRIPTION:
`
`2
`
`(HARQ) acknowledgment
`NR may need to support hybrid automatic repeat request
`(ACK) timing indicated dynamically via layer one (LI)
`signaling, such as downlink
`control information (DCI).
`
`Timing relationship between DL data reception and corresponding acknowledgement can
`be dynamically indicated by LI signaling (e.g., DCI), semi-statically indicated to a user
`equipment (UE) via higher layer, or a combination of indication by higher layers and
`dynamic LI signaling (e.g., DCI). There may be a minimum interval between DL data
`reception and corresponding acknowledgement. There may also be common channels, for
`example for random access.
`
`Figure 1 illustrates slot types in new radio. As shown in Figure 1, there are three slot types
`that can provide the basic support for both time division duplex (TDD) and frequency
`division duplex (FDD). For the bi-directional slots, there is either downlink data or uplink
`data transmission in each slot, as well as the corresponding downlink and uplink control.
`Bi-directional slot facilitates many TDD functionalities in the NR framestructure, such as
`link direction switching between downlink (DL) and uplink (UL), fully flexible traffic
`adaptation between DL and UL, and opportunity for low latency, provided that slot length
`is selected to be short enough.
`
`5
`
`10
`10
`
`15
`15
`
`20
`20
`
`    
`

`    !"#$% 
` &! % $$'$!%$%(#$"
`$) !*
` %$#%"#$% 
` $$%$%*%*(!( +$$
` , !'%$( )%$
` %$%*%*(!*    '$#
`%"#$% * $ $()
`- $) *
`.%/$$$#* #.%/($
`') '$-!)
`'$-.!*.+$$(#$"$"
` $(#$$%#$"$"$*
`0+$$)$ )$) (
`$"#%##$"!$",!()$$)$-$))
`#,()$#$('$$%
`$%*
`$$$( $$-%#$(1,(%2 !,
`$ $ ' $$-%$$#%)%))
`$%)$'* $$"$$
` ,!',$ $!$)$*
`$$)' $$-,,$'
` ,$%) '%,)$*
`+$$($$,$.%/*
`
` $. ($$$#$%
`  * '%-
`), ( $- )$$'
` $$$*
`$%$%)%)$-$%#
` ,+)%*)))$
`
`In all slots, multiplexing between DL control, DL/UL data, guard period (GP) and UL
`control
`is based primarily on time division multiplexing allowing fast energy efficient
`pipeline processing of control and data in the receiver. Physical uplink control channel
`(PUCCH) can be conveyed in the UL control symbol(s) located at the end ofthe slot. It is
`also possible to frequency division multiplex UL data and UL control and to convey
`PUCCH inalong format covering the entire UL portion ofthe slot.
`
`25
`25
`
`30
`30
`
`35
`35
`
`In addition to bi-directional slots, there are also DL slots and ULslots in Figure 1. These
`may be needed at least in FDD mode, but also in certain TDD scenarios to allow longer
`transmission periods in the same direction. In order to support smooth coverage extension
`for an UE, it may be possible to extend the transmission of data and control channels over
`multiple slots.
`
`LI control signaling can be configured to be flexible enough to support operation without
`predetermined TDD UL-DL configurations. This is due to the fact that different slot types
`
`3
`
`

`

`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`3
`3
`
`can be used onalink rather flexibly and, possibly, dynamically. Also, different slot types
`have different capabilities with respect to control signaling:
`DL
`slot
`and
`bi-
`directional slot have an opportunity for conveying the assignment for DL and UL data
`transmission, while by contrast UL slot and bi-directional slot have an opportunity for
`conveying the acknowledgement for DL data transmission.
`
`5
`
`  
`



 
`  
`  
`  
`

   
` 
`

 
`
`
`
` 

 

 
`
`  
`
`
`


`     


` 


`  
` 

 
`


`
`
`  

   
`
`


`     


` 

`
`    




`
`
` 

`
`
`

 
`
`
`  
`

 


`  

! 
` 
`



"
`

   
`
`
`
` 

# $


`
`$ 
`   
`

 

 
` 
`

    

  

`
`%

` 
`  

 

`  
`



"  
`&'#(%)*



`

  +%%',


`
` 

`
` 
` 

   
`-
`
`
`
` 

`
`  
` 


`
`'#(%)
`
`%

` 
` 

  
`
`
`'#(%)



`  
`-'

`  
`



" &

`#(

'#(*
` 
`
`
`






`
` #(

` 
` '#(%)
`&

   .%)*
`


` 

 
` 



  '#(
`


`&   
` 









`*'#(
`%) 
` '#(%)
`  








` 

 


` 

` /
` ,
`  


`  

`   
` 


`

 

      
` 
` /
`  
` 
`'#(%)
`
` 



    





'#(
`%)
`     



    0

   
`  1
`


`
`
` 



  

'#(%) 
`    &

 * 


`  2 34 
`    

   '#(%) 
`
` $

`
`
`  

'#(%) 
` 


` 

 
`
`
`

 



'#(%) 
` 


`  


`


` 
` 
`  
`0

 
` 
`

   

 

 
`
`




`
` 

   
`
`
`  
`

  
`

 '#(%)
`   0



  

    
`

 
` 
` 
`

.#
`



 
` 


`'#(%) 
`-5 
`



`
` 
`'#(%)
` 


` 
`    
`


` 
`

 






` 
` 
`

   
`
`Another issue complicating LI control signaling is that different services and/or UEs may
`have different requirements and capabilities in terms of Rx/Tx processing time. They may
`apply also different numerologies, such as different symbol and/or slot durations.
`
`request acknowledgment
`Certain embodiments address the hybrid automatic repeat
`(HARQ-ACK)
`reporting on UL,
`for example on PUCCH. More specifically, certain
`embodiments relate to codebook size definition in a scenario with dynamically varying
`HARQ-ACK timing. Certain embodiments relate to definition of HARQ-ACK report
`content and size. Hybrid automatic repeat request (hybrid ARQ or HARQ)is usually a
`combination of error-correcting coding and ARQ. In certain embodiments, HARQ-ACK
`(or non-acknowledgement, NACK) is transmitted for DL data with regard to the HARQ
`process at issue (data may be in the form ofa transport block, codewordor like). HARQ-
`ACKcodebook is set of HARQ-ACKbits that are are ordered in a predetermined manner
`and jointly coded. Multiple codebooks, corresponding to e.g. plurality of cells and
`determined separately for each cell may be concatenated into single joint codebook.
`
`Dynamic HARQ-ACK timing can refer to the fact that the number of reported HARQ-
`ACKbits/slot may vary from slot to slot. For example, assuming that 8 different timing
`values are supported, the number of HARQ-ACK feedback bits / slot (per cell) may vary
`between 0 and 16, assuming that each DLslot creates up to two HARQ-ACK feedback
`bits. The variation in the number of HARQ-ACK feedback bits transmitted per slot is
`increased even further when HARQ-ACK feedback bits for multiple DL cells are
`transmitted via single UL cell.
`
`10
`10
`
`15
`15
`
`20
`20
`
`25
`25
`
`30
`30
`
`From the point of view of control channel coverage and UL control signaling resource
`
`consumption, there may beasignificant difference between different HARQ-ACK
`payloads. For that reason, there may be a need to consider the following mechanisms as
`part of NR design: support for dynamically varying HARQ-ACK codebook size; and
`support for time domain bundling of HARQ-ACKbits transmitted in the same slot but
`corresponding to different DL transport blocks transmitted via different slots.
`
`35
`35
`
`4
`
`

`

`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`4
`
`Issues related to dynamically varying HARQ-ACK codebook (CB) and/or HARQ-ACK
`bundling include the following: how to facilitate dynamic HARQ-ACK CB adaptation in
`the NR,
`including determination of both codebook size as well as which HARQ-ACK
`feedback bits are included to a codebook; how to support CB adaptation for parallel
`services, such as enhanced mobile broadband (eMBB) and ultra-reliable low latency
`communication (URLLC), as well as for different component carriers; and how to avoid
`and/or minimize consequencesofvariouserror cases related to DCIfailure, covering both
`DL and ULresource allocation grants.
`
`There is a risk that when an evolved/enhanced Node B (eNB) schedules physical downlink
`shared channel (PDSCH), the UE may not detect the corresponding physical downlink
`control channel
`(PDCCH) properly. Hence,
`the corresponding component carrier
`(CC)/slot may not be considered in the HARQ-ACK codebook determination. Dynamic
`codebook adaptation may require that UE and eNB have a commonunderstanding of the
`HARQ-ACK codebook size and HARQ-ACK bit ordering within the codebook.
`Otherwise there may be higher layer error, such as HARQ data for which UE did not
`detect DL control channel properly being treated as acknowledged. Alternatively, HARQ
`data which UE did not detect properly and transmitted negative acknowledgment may be
`treated as acknowledged due to error on HARQ-ACKbit ordering. The overall probability
`of such error case should be extremely low, e.g. below 10%.
`
`     
`


`
`     
`      !     
`

"  
` #$    

       %    
`         &  "" "  " 
`   $   

    '     
`
`

  ())$      

"    &   
` 



%   *         +  $    
`+)()     ,
`-          #   #   "
`   
`   .+/$ (0


`      "  "
`   
`   .+" " 
`,  $   "  

"   
`  


`             

 ,+
`


`   " 


` *  (0 # 

    
`    %           ,
`1   


`   
`   $     (0  
`  +)   " " 
`       ,   
`$
`  (0    " " 
`

      




`
`              ,-  "   
`
` 
`      2


` $ ,,  345,
`6  7   

      

 

 ,-

 
`  $734$   

     ,-

 
`  $784$  

     

     
`   

   ,02

"    

  "    ,
`6  2

" $  * "

  

     


`    " 

      

  
`         

    ,    $  
`         

"     

 ( 
`

    ()  $        

 $
`  2

" $   


`     ()

     "  
`+)  

   ,
`-

   
`          

  2
`
`The method can
`Figure 9 illustrates a method according to certain embodiments.
`include, at 910, receiving a timing offset value in a downlink grant. The method can
`also include, at 920, determining a first downlink time slot within a feedback window
`based on the timing offset value. Examples of the determination are presented below.
`
`is
`For example, a user equipment can determine that a downlink acknowledgment
`associated to an uplink time slot or unit for a first time and that a new feedback
`window has started based on the determined association.
`In other words, when an
`access node indicates for the first time that uplink control information (UCI) shall be
`transmitted on a certain UL slot, the feedback window isstarted (the first time means,
`for example, the first time may relate to a certain UL timeslot or unit without previous
`DL acknowledgement association).
`
`The method can additionally include receiving a counter downlink assignment index
`
`5
`
`10
`10
`
`15
`15
`
`20
`20
`
`25
`25
`
`30
`30
`
`35
`35
`
`5
`
`

`

`field. The determining the first downlink time slot can be further based on the counter
`downlink assignment index field. The counter downlink assignment index is further
`clarified below.
`
`The method can further include, at 950, determining a last time slot or unit of the
`feedback window based on information of a last downlink time slot or unit for which
`
`feedback is to be reported in an uplink time slot or unit associable with the timing
`offset value.
`
`The method can also include, at 960, determining a size of a codebook for the
`feedback window. Thesize of the codebook can be determined based on the number
`
`of time slots in the feedback window. The determining the number of downlink time
`slot or unit, or codebooksize, can be further based a downlink acknowledgment being
`associated to a second uplink time slot or unit occurring later for a first time. In this
`case,
`the user equipment can determine that a new, second, feedback window has
`started based on the determined association for the first
`time, and the previous
`downlink time slot or unit is the last downlink time slot or unit contained in thefirst
`
`codebook. This may be applicable, for example, to a case in which codebooksize is
`also adapted.
`
`The method can additionally include, at 980, receiving a total downlink assignment
`index field. The determining the number of downlink time slot or unit, or codebook
`
`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`5
`9
`
`  
`  

  
`    
` 


`     


`   
`   
`
`   
`  

  
`   
`   
`    
`     
`     
`       
` 

`  
`
`   
`  

  
`  
`  
`
`
`   
`  


`  
`
`          

` 

`    
`    

   
`
`    
`
`   
`   
`      
`  
` 
`       
`      
`
`    
`     
` 
`
`   ! 
`  

 
`  "#
`     
` 

   
`
`  $%&' 
`   "# 
`
`  $%&' 


`   (#  $%&'
`    "#  
`  
` 

 
`     
`  
`
`% )*
`  
`  $%&'  "#   $%&'+*
` 
`  
`  $%&' 
`"#    (,-)%./    
` (#   

    +*
`  
` 

 
` ". 
` 
` 

`(.
` 

    
` 

   
` 
`
`  


`
`
`     
` 

 
`
`    0   

  


`
`   
`  


`  
`    
`
`The method can further include, at 970, transmitting the feedback for the feedback
`window in the ULtime unit associable with the timing offset value and based on the
`determined size of the codebook. HARQ feedback transmission on certain UL slot
`may contain HARQ acknowledgements only for DL slots that have HARQ feedback
`associated to the certain UL slot for example based on the timing offset. This is
`illustrated, by way of example,
`in embodiment A, where the eNB may start
`to
`associate HARQ feedback to a later UL slot even before the end of current HARQ FB
`window. This may be done, for example, to balance HARQ feedback codebook size
`between ULslots. In this case, DTX/NACKcanbe reported in the current codebook
`for DL slots that belong to the current codebook but are associated to the next FB
`window and codebook bythe timing offset. In an example, UCI transmission timing
`can be DCItiming plus an indicated timing offset, plus a minimum processing time, if
`not incorporated to the indicated timing offset.
`
`5
`
`10
`10
`
`15
`15
`
`20
`20
`
`25
`25
`
`30
`30
`
`35
`35
`
`6
`
`

`

`size, can be further based on the total downlink assignment
`detailed examples of the method are presented below.
`
`index field. Some further-
`
`The UE can determine the first DL time unit/slot of a HARQ-ACK FB window based on
`an indication of a HARQ-ACK timing offset value in a DL grant, for example in DCI.
`When a DL HARQ-ACK feedbackis associated to a certain UL time unit, such asslot or
`mini-slot, for the first time, the UE can determine that a new HARQ-ACK feedback (FB)
`window hasstarted.
`
`In other words, if the UE finds an indication of a timing offset value in a DL grant, the UE
`can know whether or not a new HARQ-ACK window has started. The indication can be
`the timing indicator in DCI. Based on that indication the UE can determine a tabled value
`for the timing offset.
`
`for HARQ-ACK
`indicated by the timing offset
`The UE can use the resources
`the UE may be (pre)configured to add the UE's
`transmission.
`In one embodiment,
`minimum processing time to the timing offset for determining the time slot to be used for
`ULtransmission. In another embodiment, the minimum processing time can be taken into
`consideration in the mapping oftiming offset values, which can be referred to as the tabled
`values.
`
`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`6
`6
`
`  
`

 



   

  
`


`

    



  

 
` 

 






`



  !"#!$%&'  
`  

  !"#!$%

 

(
` 

   $)
`*  !"#!$%   



 

 


`


` 


`  

 



 



 



  !"#!$% +&',
`  




`)



   

 

 

(
` 




`



  !"#!$%  



  


`

   

 $)' 



 





  

 (
`
` 

 


` 
`

 
`  

-

 

 !"#!$%
`

 )   



- + , 
` 



.
`  
` 





 



  

 


`  
`

 )

   



  
` 

 

  


`  

 

 

 

(
`      



 
`(
`  

 

    

!"#!$%&' &
`  

 

    




`  !"#!$%


` 

 

!"#!$%&'  )   

 
`/   

!/ (   -

       
`
` -

 

   
` 

 

` '-




`    

 /   

'/ (   -

   
`     -

 

  

`- 
` 

` 

`   

'- 0
`  



!) 



!) 
` 

   !"#!$%
`  

&'    
` 
` 

 !1 

 !"#!$%



 !"#!$%&'
`  

!"#!$%  

  

  
`) 

    



    

     

`
` 

 



 


`     -

  
`  

       ( 

`  
`

-  
`( 

` 
`
`The UE can determine the size of a codebook for the HARQ-ACK FB window. For
`example, the size of the codebook, which can refer to the number of HARQ-ACKbits, can
`be adapted for the HARQ-ACK FB window as follows.
`In an embodiment called
`"embodiment A" for convenience only, the size of a codebook can be defined based on
`how many DLtimeslots the access node can schedule in the window atissue. By contrast,
`in an embodimentcalled "embodiment B" for convenience only, the size of a codebook
`can be defined based on how many DLtimeslots the access node actually schedules in the
`window at issue. Embodiment B may require a total DAI-field. The total DAI-field can
`also enable time domain HARQ-ACK bundling in the FB window. Time domain bundling
`can correspond to a logical-AND-operation of HARQ-ACK bits within HARQ-ACK FB
`window, compressing the HARQ-ACK feedback into single feedback bit per a codeword.
`In certain embodiments, the size of a codebook can be determined cell-wise based on the
`number of time slots, not based on the number of carriers.
`Similarly, the size of a
`codebook can be determined cell-wise for each cell or virtual cell of a plurality of cells or
`virtualcells.
`
`5
`
`10
`10
`
`15
`15
`
`20
`20
`
`25
`25
`
`30
`30
`
`35
`35
`
`7
`
`

`

`7
`
`In embodiment A, a simple form of dynamic codebook adaptation can be based on the
`HARQ-ACK timing offset value included in DL grant.
`In this method, HARQ-ACK
`codebook size can be determined according to the number of HARQ-ACK timing options
`smaller or equal than HARQ-ACK timing offset included in the first DL grant in the
`HARQ-ACKFB window.
`
`For example, if a service provided requires short latency, the access node can configure a
`short HARQ-ACK FB window, oralternatively the access node maytry to minimize UL
`control overhead by a long HARQ-ACK FB window. The dynamics of HARQ-ACK
`
`WO 2018/127628
`WO 2018/127628
`
`PCT/FI2018/050006
`PCT/FI2018/050006
`
`    
`

       

 
`    

    


`  
`

!           

`

"     

  

  
`  #$% %
`       

`    
`

    &    


`
`    
`



 

 


` 

 

  

`



'$$ (
`  
`  

     )

`   
`
`    
` 

% #* 
`
`

 



 

*  
`


`% 
`


`  

   ) 

+), "

 ! 
`

  

      

  
`   

  
`(&    


`

 
`
`

%   -
`    

 





   
`



 .
`  
`   

      

 

 

%  
`    

#/



 * 

 
`     +#$,% %   
`
`     

%  #/
`%  
` 
`%    

  0  

   
` 

%  

 +12,

  

    
`  #$% %3  %    #$% % 
`

    
`



  


`%  
`   #$% % 

 

   (
`  3 

     



   #$% % 
`      

  %     
`+, #* 
`

 "

 
`

  
`

  #$% %
` 

    !(
`    #$% % )  

  
`
`In the method according to certain embodiments, a HARQ-ACK codebook can be defined
`separately for each virtual HARQ-ACK cell. Each componentcarrier or cell can constitute
`a virtual HARQ-ACK cell. Additionally,
`it is possible to define separate virtual cell also
`for different service types or numerologies, such as eMBB and URLLC, running in
`parallel in the same DL componentcarrier or cell. Thus, a virtual HARQ-ACK cell may
`be,
`in addition to a normal radio cell, defined for a virtual cell as well. For example,
`support for a consistent user experience, higher speed,
`lower latency, greater spectrum
`efficiency and support for Internet of Things (loT) may require using cell virtualization a
`single physical cell by dynamically dividing it into multiple virtual cells for determination
`of HARQ-ACK feedback. In this concept, UE may determine a plurality of codebooks for
`a same carrier, or radio cell, each codebook associated with certain numerology and/or
`latency configuration and transmit according to those codebooks using one or more
`transmission. With regard to carrier aggregation, a virtual cell can be defined for each
`componentcarrier separately. Certain embodiments cover different scenarios with one and
`multiple virtual HARQ-ACK cells. Figure 2 illustrates an example scenario for
`determining a HARQ-ACK feedback (FB) window for one virtual HARQ-ACK cell,
`according to certain embodiments. As shown in Figure 2, within each virtual HARQ-
`ACKcell, the following principles can be applied: HARQ-ACK corresponding to one
`physical downlink shared channel (PDSCH) slot or mini-slot may be part of only one
`HARQ-ACK FB window; HARQ-ACK within a certain HARQ-ACK FB window may be
`associated to only one DL time unit, such as slot or mini-slot, while HARQ-ACK of a
`certain HARQ-ACK FB window can be associated to and transmitted on only one UL
`time unit; and starting and ending positions of a