`
`3GPP TSG RAN1 WG1 #90bis
`Prague, Czech Republic, 9-13 October 2017
`
`
`
`Agenda Item:
`
`7.3.3.4
`
`Source:
`
`Title:
`
`Ericsson
`
`On UL Data Transmission Procedure
`
`Document for:
`
`Discussion, Decision
`
`
`I.
`
`Introduction
`
`
`
`R1-1718647
`
`In this contribution, we discuss the following aspects related to UL data transmission.
` SR configuration details are discussed in section 2.1
` UL transmission without grant in section 2.2
` UL waveform selection is discussed in section 2.3
` PUSCH Frequency hopping is discussed in section 2.4
`Discussion
`
`II.
`
`A. SR Configuration
`
`In RAN1#90, the following was agreed on SR configuration
`Agreements:
`•
`It is up to RAN2 how many SR configurations the UE can be configured with.
`•
`In case of SR only, the physical layer can only transmit one SR at any given time
`•
`If multiple SR are triggered prioritization of which SR should be transmitted is decided by RAN2
`• Multiplexing of SR and HARQ feedback is supported on short-PUCCH
`• Multiplexing of SR and HARQ feedback is supported on long-PUCCH
`• An SR can be configured with a periodicity of at least equal to X OFDM symbol(s) (at least for short-PUCCH), and
`with up to the largest periodicity supported in LTE (i.e. 80 ms)
`• Working assumptions:
`• X=1, which implies short-PUCCH could be located at any OFDM symbol of a slot
`• FFS: Supported periodicity values
`• FFS: Possible limitations due to other factors
`• One configured SR can be associated with either short or long PUCCH
`
`In the previous meeting the smallest possible periodicity for SR transmission (X) was discussed and
`X=1 was agreed as a working assumption. The benefit of supporting X=1 is clear as it allows SR to
`be transmitted with smallest possible latency. We do not see any serious concerns or drawbacks
`with supporting this configuration and therefore the working assumption should be confirmed.
`Proposal 1-1
` Confirm the working assumption to support configuration allowing 1 OFDM symbol periodicity for 
`SR. 
`
`Another aspect to consider is supported periodicity values for SR and related signalling. In addition
`to the periodicities supported for LTE, some additional periodicities depending on slot duration for
`higher SCS cases can be supported as shown in Table below. It should be noted that with a slot, UE
`can be configured multiple SR resources (e.g. for short PUCCH based SR)
`Table 1- Supported periodicity for configuring per-slot SR resources
`
`
`
`APPLE 1011
`
`1
`
`

`

`SR periodicity
`(ms)
`
`SR
`PERIODICITY
`
`
`
`SR
`configuration
`Index
`SRI
`
`
`0 – 4
`5 – 14
`
`15 – 34
`
`35 – 74
`
`75 – 154
`
`155 – 156
`
`157
`
`-
`
`-
`
`-
`
`N
`
`SR slot
`offset
`
`OFFSET,SR
`SRI
`
`5SRI
`
`15SRI
`35SRI
`75SRI
`
`155
`SRI
`157SRI
`-
`
`
`
`
`
`-
`
`-
`
`
`
`
`
`
`
`SR
`configuration
`Index
`SRI
`
`
`0 – 9
`10-19
`
`20-59
`
`60-139
`
`140-299
`
`300-303
`
`304-305
`
`306
`
`-
`
`-
`
`N
`
`SR slot
`offset
`
`OFFSET,SR
`SRI
`
`SRI
`-10
`SRI
`-20
`SRI
`-60
`SRI
`-140
`SRI
`SRI
`SRI
`
`-300
`
`-304
`
`-306
`
`-
`
`-
`
`SR
`configuration
`Index
`SRI
`
`
`0 – 9
`10-19
`
`
`
`20-59
`
`60-139
`
`140-299
`
`300-315
`
`316-323
`
`324-327
`
`328-329
`
`330
`
`5
`10
`
`20
`
`40
`
`80
`
`2
`
`1
`
`0.5
`
`0.25
`
`0.125
`
`SR slot
`offset
`
`OFFSET,SR
`SRI
`4*
`
`4* SRI
`-40
`4* SRI
`4* SRI
`4* SRI
`SRI
`-300
`SRI
`SRI
`SRI
`SRI
`
`N
`
`
`
`-80
`
`-240
`
`-560
`
`-316
`
`-324
`
`-328
`
`-330
`
`
`
`
`
`
`
`Subcarrier
`spacing
`(kHz)
`15
`30
`60
`120
`240
`
`Supported periodicity of per-slot SR
`resources (ms)
`1,2,5,10,20,40,80
`0.5,1,2,5,10,20,40,80
`0.25,0.5,1,2,5,10,20,40,80
`0.125,0.25,0.5,1,2,5,10,20,40,80
`0.0625,0.125,0.25,0.5,1,2,5,10,20,40,80
`
`Table 2- Supported offsets for configuring per-slot SR resources (Example)
`15kHz SCS
`30kHz SCS
`120kHz SCS
`
`
`Configuration of SR resources can follow the same approach as LTE, i.e., a SR periodicity and
`offset is mapped to a SR resource index signalled by higher layers to identify the slots for SR
`transmission. For larger SCS, it may be enough to support SR offsets with coarser granularity than
`slot duration, especially for SR periodicities spanning multiple milliseconds. E.g., for 120kHz SCS
`case, for SR periodicity longer than 2ms, it may be sufficient to support offsets with 0.5ms
`granularity instead of supporting every possible offset with 0.125ms granularity, for example as
`shown in Table 2 above. In addition to this, the PUCCH resource(s) to be used for SR transmission
`within a slot are also configured by higher layers. For short-PUCCH, to support a periodicity of 1
`OFDM symbol as per the current working assumption, it should be possible to configure up to 14
`short-PUCCH resources per slot (i.e., one per OFDM symbol).
`Proposal 1-2
` A UE can be configured with multiple SR configurations (already agreed in RAN1#90)
` For each SR configuration, the following should be indicated via RRC 
`o A SR configuration index (that corresponds to a SR periodicity and slot offset) which 
`identifies the slots to be used for SR transmission.
`o For long‐PUCCH based SR ‐ up to 2 long‐PUCCH resource indices that identify the long‐
`PUCCH resource(s) to use for SR transmission within the slots identified by SR configuration 
`index.
`o For short‐PUCCH based SR ‐ up to 14 short‐PUCCH resource indices (i.e., up to one resource 
`every OFDM symbol) that identify the short‐PUCCH resource(s) to use for SR transmission 
`within the slots identified by SR configuration index. 
`
`2
`
`

`

`
`
` For SR periodicity, in addition to the periodicities supported for LTE, additional more frequent 
`periodicities should be supported for higher SCS cases as shown in Table 1.
`o For higher SCS, only a subset of SR offsets with coarser granularity than slot duration 
`should be supported especially for SR periodicities spanning multiple milliseconds. 
`
`Another aspect to consider is cases where a short‐PUCCH based SR is triggered but UE has an ongoing long‐
`PUCCH/PUSCH transmission and an SR resource is available for UE before the end of ongoing transmission. 
`For such cases, UE should transmit SR in the first available SR resource without an ongoing transmission. It 
`should be noted that if the UE has PUSCH immediately scheduled after the ongoing transmission, it can 
`send a BSR on the PUSCH.
`
`B. UL Transmission without UL Grant
`
`1. Configuration of K repetitions
`
`Configuration of K repetition can be done by RRC signalling. There is no strong reason to have L1
`signalling for a UE that is likely to be stationary over the course of configured transmissions. Also
`in the case of a change in path-loss, link adaptation can handle such variations without a need to
`change the repetition.
`Proposal 2-1: Repetition number K for Type 2 UL transmission without grant is configured
`only by RRC.
`
`
`Several different configurations have been discussed for repetition in transmission without UL
`grant. We believe that at least the following three different configurations can be identified (Figure
`1). It seems that options (b) and (c) in the figure can be configured with different periodicities,
`while option (a) is only applicable to periodicity of 1, which means that it should be transmitted in
`all slots, i.e. a resource is constantly dedicated for UL transmission without grant. As this is not a
`general case we think that either of the bottom two figures should be considered for the
`configuration of UL transmission without grant. One can think of (b) and (c) as scenarios that
`address different applications. One obvious advantage of option (b) over option (c) is that a full
`repetition is always performed, so the performance of option (b) is expected to be better (c).
`Another potential advantage of option (b) over option (c) is easier blind decoding, since there is
`either a UL transmission present in all repetition or none, while in option (c) the hypotheses for
`transmissions in all resources should be tested.
`
`
`
`3
`
`

`

`
`
`Figure 1 Different alternatives for configuration of repetition
`
`
`
`Proposal 2-2: Option (b) should be considered for configuration of repetition in UL
`transmission without UL grant
`
`
`As for the redundancy versions in the repetition, our understanding is that it is beneficial for both
`type 1 and type 2 to use different RVs configured by RRC. This option includes all other cases and
`also has the advantage that depending on the conditions, such as low code rate, etc., the gNB can
`configure the RV cycling based on whether different RVs can be self-decodable, etc. In RAN1 NR
`AdHoc#3 it was decided that NR supports RV cycling, however the exact RV design is not clear. It
`is therefore proposed that RV cycling for repetition is supported. The exact RVs that will be used in
`the repetition is pending further agreements in chancel coding session.
`Proposal 2-3: RV cycling for repetition is supported. RVs that will be specified is pending
`agreement on the exact RV design in the channel coding
`It has also been discussed whether repetition only applies to slots or to mini-slot as well, i.e.
`whether it is allowed to have multiple repetitions of a transport block within a slot. It is our
`understanding that within a slot it is possible to have a TB with a low code rate instead of repeating
`the same TB multiple times. The advantage of low code rate as compared to repetition is both better
`performance as well as possibility of link adaptation.
`Another aspect to consider is supported periodicity values for the UL transmission without UL grant
`(UL-TWG) resources and related signalling. Like SR we can define periodicities depending on slot
`duration for higher subcarrier spacing can be supported as shown in Table below.
`Table 3- Supported periodicity for configuring per-slot UL transmission without UL grant
`Subcarrier
`Supported periodicity of UL-TWG
`spacing
`resources (ms)
`(kHz)
`15
`1,2,5,10,20,40,80
`30
`0.5,1,2,5,10,20,40,80
`60
`0.25,0.5,1,2,5,10,20,40,80
`120
`0.125,0.25,0.5,1,2,5,10,20,40,80
`
`
`
`4
`
`

`

`240
`
`0.0625,0.125,0.25,0.5,1,2,5,10,20,40,80
`
`Table 4- Supported offsets for configuring UL-TWG resources (Example)
`15kHz SCS
`30kHz SCS
`120kHz SCS
`
`
`
`
`
`UL-TWG
`periodicity
`(ms)
`
`
`5
`10
`20
`40
`80
`2
`1
`0.5
`0.25
`0.125
`
`UL-TWG
`configuration
`Index
`
` 𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`
`0 – 4
`5 – 14
`15 – 34
`35 – 74
`75 – 154
`155 – 156
`157
`-
`-
`-
`
`UL-TWG slot
`offset
`
`
`𝑁(cid:3016)(cid:3007)(cid:3007)(cid:3020)(cid:3006)(cid:3021),(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-5
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-15
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-35
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-75
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-155
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-157
`
`-
`-
`-
`
`UL-TWG
`configuration
`Index
`
` 𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`
`0 – 9
`10-19
`20-59
`60-139
`140-299
`300-303
`304-305
`306
`-
`-
`
`UL-TWG slot
`offset
`
`
`𝑁(cid:3016)(cid:3007)(cid:3007)(cid:3020)(cid:3006)(cid:3021),(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-10
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-20
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-60
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-140
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-300
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-304
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-306
`
`-
`-
`
`UL-TWG
`configuration
`Index
`
` 𝑰𝑼𝑳(cid:2879)𝑻𝑾𝑮
`
`0 – 9
`10-19
`20-59
`60-139
`140-299
`300-315
`316-323
`324-327
`328-329
`330
`
`UL-TWG slot
`offset
`
`
`𝑵𝑶𝑭𝑭𝑺𝑬𝑻,𝑼𝑳(cid:2879)𝑻𝑾𝑮
`4*𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)
`4*𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-40
`4*𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-80
`4*𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-240
`4*𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-560
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-300
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-316
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-324
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-328
`𝐼(cid:3022)(cid:3013)(cid:2879)(cid:3021)(cid:3024)(cid:3008)-330
`
`
`For type 1 UL transmission without UL grant, it should be possible to configure time domain
`resources within each periodicity. For this purpose, a resource allocation down to UL symbol must
`be supported, i.e. up to 14 resources per slot should be configurable.
`Proposal 2-4
` For UL transmission without UL grant a UL‐TWG configuration index (that corresponds to a 
`periodicity and slot offset) should be configured by RRC. 
` For type 1 UL transmission without UL grant, resource allocation down to UL symbol must be 
`configured by RRC signalling
`2. HARQ Feedback
`
`Due to asynchronous HARQ feedback, UE does not have an exact timing for when to expect
`an UL grant for retransmission. It means that the feedback might be transmitted from gNB at any
`given time, and UE does not have a well-defined reference point for assuming no feedback is sent.
`To limit this uncertainty in NR, a maximum feedback time T can be explicitly configured for the
`UE to wait for feedback.
`
`Due to the lack of a PHICH-like channel in NR, the feedback has to be sent by PDCCH. But, to
`always send an explicit positive or negative feedback in PDCCH for each UL transmission induces
`a large signaling load in the downlink. For reduced load of the DL control channel, some feedback
`transmissions can be skipped without substantially degrading the UL transmission performance. If
`the gNB fails to decode the UL transmission, it sends UL grant to UE for retransmission. UE can
`interpret the HARQ feedback from whether the UL grant is received or not. Since the UL BLER
`value usually would be kept within a small value, this procedure saves most of signaling overhead
`for feedback.
`Proposal 2-5: A feedback time T can be explicitly configured for the UE to wait for
`feedback. A UL transmission is considered successful if no feedback is received within
`feedback time T. The specific design is up to RAN2.
`
`
`
`3. HARQ process ID
`
`In LTE SPS and fast UL framework with multiple HARQ processes, the HARQ PID is not
`indicated. Formulas have been specified (TS 36.321) to derive the HARQ PID from the absolute
`system frame number (SFN) and subframe number (which is known in both eNB and UE). In other
`
`
`
`5
`
`

`

`
`
`words, the HARQ PID is synchronized, and eNB and UE are in-sync on which process ID to use on
`each TTI.
`
`
`
`For NR UL transmission without UL grant, it has been proposed to specify HARQ process
`ID based on the resources that are used for the transmission. In the following we illustrate the
`implications of this design based on two different cases. In one case the HARQ process ID is shared
`with the dynamic grant, and in another case, there are different pools for HARQ process IDs for
`dynamic grant and UL transmission without UL grant.
`
`Furthermore, HARQ ID based on a physical resource is not possible for dynamic TDD
`where the next occasion for UL transmission is not guaranteed to be a UL subframe, unless HARQ
`PID is defined based on transmission occasions rather than absolute subframe number, etc. Another
`issue that need to be addressed is how HARQ process ID based on physical resources can work
`when repetition is used. In that case we need to guarantee that the same HARQ process ID is used
`for different repetition, although they are transmitted on different physical resources. Figure below
`shows this problem with 4 repetition that may start at any time, and there is ambiguity how the
`HARQ process ID should be identified.
`
`4 repetitions starting at t
`
`4 repetitions starting at t+T
`
`HARQ PID=?
`
`HARQ PID=?
`
`Figure 2 Ambiguity for HARQ process ID when repetition with flexible starting time
`
`
`
`This ambiguity can be avoided by using different resources for different HARQ PIDs as
`well as different resources for repetitions. In summary, in order to support functionalities introduced
`in NR, such as dynamic TDD, repetition, periodicity shorter than one subframe, etc. We propose
`that
`
`Proposal 2-6: In UL transmission without UL grant, HARQ PID can be implicitly
`indicated based on the transmission occasions, frequency resources and DMRS resources
`
`
`
`If HARQ PID of UL transmission without UL grant and the HARQ PID of dynamic grant is
`taken from the same pool, then it is required to have some mapping between the HARQ PIDs for
`dynamic grant and for transmission without UL grant when both are scheduled. This mapping can
`be quite complicated, and result in ambiguity on the UE whether the gNB is requesting for a
`retransmission of a failed dynamically scheduled transmission or a failed transmission without UL
`grant.
`
`With the agreement that a different RNTI can be used for SPS re-retransmission, there is no
`confusion that a certain RNTI scrambled UL-grant refers to retransmissions of a SPS HARQ
`process or a dynamic scheduling HARQ process. In principle, HARQ process IDs can be shared
`between SPS and dynamic scheduling. But a clear boundary between the two within one pool can
`facilitate dynamic scheduling in gNB.
`
`Proposal 2-7: HARQ Process IDs for dynamic grant and UL transmission without UL
`grant should be separated, but can be from the same pool.
`
`
`
`6
`
`

`

`
`
`C. UL Waveform type Indication
`
`1. Waveform type indication for UL transmission with grant
`
`NR PUSCH supports both OFDM and DFT-S-OFDM waveforms. The following options
`can be considered for waveform type indication
`
`Option 1: Waveform type indicated as part of system information.
`
` For this option, waveform type for all PUSCH transmissions is indicated via 1 bit in RMSI,
`i.e., the signaling that has already been agreed for msg3 PUSCH is made applicable for all
`PUSCH transmissions.
` Since DFT-S-OFDM based waveform should be limited to a single stream transmissions,
`the UE should use CP-OFDM when performing multi-stream transmissions irrespective of
`waveform indicated by RMSI.
`Option 2: Waveform type indicated via UE specific RRC signaling
`
` For this option, waveform type for PUSCH transmissions other than msg3 transmission is
`indicated to the UE via UE specific RRC signaling.
` Depending on the RRC configured waveform type, the UL resource allocation type, and
`possibly the DCI format that the UE uses for monitoring UL grants can be different.
` With this approach, the waveform used by UE will be uncertain during RRC reconfiguration
`of waveform type. This can be addressed by making the UE use a default waveform type for
`UL grants received in common search space. The waveform type indicated for msg3 in
`RMSI (as per current agreement) can be used as the default waveform type.
`Option 3: Waveform type indicated dynamically to the UE.
`
` For this option, the waveform type is indicated dynamically by one of the following
`alternatives
`o a) Explicit indication in DCI (e.g. using 1 bit)
`o b) Implicit indication via DCI
`o c) Make the UE simultaneously monitor two DCI formats, one corresponding to
`OFDM and another corresponding to DFTS-OFDM.
` Among the above alternatives, simultaneous monitoring of two UL DCI formats would
`increase BDs/blocking. Even if 1 bit is used for waveform type indication, the MCS to use
`for different waveform types still needs to be resolved. Considering this, the implicit
`indication approach described in [2] is preferable over the other alternatives.
`Based on the above analysis, it is recommended to support fast switching between OFDM and DFT-
`S-OFDM waveforms. One approach is to adopt an MCS table that can address waveform options in
`addition to modulation orders and code rates. One such example is shown in Error! Reference
`source not found. in the Annex.
`Proposal 3-1 Support fast switching between OFDM and DFT-S-OFDM waveforms for NR
`PUSCH via DCI signalling.
`
`
`2. Waveform type indication for UL transmission without UL grant
`
`It is preferable that a common mechanism is defined for indication of the waveform type, mainly
`due to that there is fundamentally no difference in switching between waveforms between
`transmission with grant and transmission without UL grant. We propose that the switching between
`waveforms is done via DCI signaling, i.e. using entries in the MCS table. This is applicable both in
`type 1 and type 2 transmission without UL grant, sa in both cases MCS needs to be signaled by
`either RRC signaling in type 1 or L1 signaling in type 2
`
`
`
`7
`
`

`

`
`
`Proposal 3-2 Support switching between OFDM and DFT-S-OFDM waveforms for both type
`1 and type 2 UL transmission without UL grant using MCS indication.
`D. Frequency hopping
`
`In LTE frequency hopping is configured by higher layer configuration and is enabled by
`means of layer 1 signalling. Two types of frequency hopping are supported in LTE that is either
`based on pre-defined cell-specific patterns (type 2) or explicit hopping information in the
`scheduling grant (type 1).
`
`It has been agreed in RAN1#89 that for DFT-s-OFDM based NR-PUSCH transmission,
`least intra-slot frequency hopping is supported for 14 symbol slot case. It is further proposed here
`that type 1 PUSCH frequency hopping is supported for both UL transmission with grant and UL
`transmission without UL grant.
`
`Proposal 4-1 Type 1 intra-slot and inter-slot frequency hopping is supported for both
`UL transmission with grant and UL transmission without UL grant
`
`
`
`
`
`III.
`
`Conclusion
`
`Based on the discussion in section II we propose the following:
`
`Regarding SR Configuration
` Proposal 1‐1:
`o Confirm the working assumption to support configuration allowing 1 OFDM symbol 
`periodicity for SR.  
`
` 
` Proposal 1‐2
`o A UE can be configured with multiple SR configurations (already agreed in RAN1#90)
`o For each SR configuration, the following should be indicated via RRC 
` A SR configuration index (that corresponds to a SR periodicity and slot offset) which 
`identifies the slots to be used for SR transmission.
` For long‐PUCCH based SR ‐ up to 2 long‐PUCCH resource indices that identify the 
`long‐PUCCH resource(s) to use for SR transmission within the slots identified by SR 
`configuration index.
` For short‐PUCCH based SR ‐ up to 14 short‐PUCCH resource indices (i.e., up to one 
`resource every OFDM symbol) that identify the short‐PUCCH resource(s) to use for 
`SR transmission within the slots identified by SR configuration index. 
`o For SR periodicity, in addition to the periodicities supported for LTE, additional more 
`frequent periodicities should be supported for higher SCS cases as shown in below Table.
` Note: For higher SCS, only a subset of SR offsets with coarser granularity than slot 
`duration may be supported especially for SR periodicities spanning multiple 
`milliseconds. 
`
`
`
`
`
`Table - Supported periodicity for configuring per-slot SR resources
`
`Supported periodicity of per-slot SR
`resources (ms)
`
`Subcarrier
`spacing
`(kHz)
`
`8
`
`

`

`
`
`15
`30
`60
`120
`240
`
`1,2,5,10,20,40,80
`0.5,1,2,5,10,20,40,80
`0.25,0.5,1,2,5,10,20,40,80
`0.125,0.25,0.5,1,2,5,10,20,40,80
`0.0625,0.125,0.25,0.5,1,2,5,10,20,40,80
`
`
`Regarding UL Transmission without grant
` Proposal 2-1: Repetition number K for Type 2 UL transmission without grant is configured
`only by RRC.
` Proposal 2-2: Option (b) should be considered for configuration of repetition in UL
`transmission without UL grant
` Proposal 2-3: RV cycling for repetition is supported. RVs that will be specified is pending
`agreement on the exact RV design in the channel coding
` Proposal 2-4: For UL transmission without UL grant a UL-TWG configuration index (that
`corresponds to a periodicity and slot offset) should be configured by RRC. For type 1 UL
`transmission without UL grant, resource allocation down to UL symbol must be configured
`by RRC signalling
` Proposal 2-5: A feedback time T can be explicitly configured for the UE to wait for
`feedback. A UL transmission is considered successful if no feedback is received within
`feedback time T. The specific design is up to RAN2.
`
` Proposal 2-6: In UL transmission without UL grant, HARQ PID can be implicitly indicated
`based on the transmission occasions, frequency resources and DMRS resources
`
` Proposal 2-7: HARQ Process IDs for dynamic grant and UL transmission without UL grant
`should be separated, but can be from the same pool.
`
`Regarding waveform indication
` Proposal 3‐1 Support fast switching between OFDM and DFT‐S‐OFDM waveforms for NR PUSCH via 
`DCI signalling. 
` Proposal 3‐2 Support switching between OFDM and DFT‐S‐OFDM waveforms for both type 1 and 
`type 2 UL transmission without UL grant using MCS indication  
`
`
`Regarding Frequency hopping
` Proposal 4-1 Type 1 intra-slot and inter-slot frequency hopping is supported for both UL
`transmission with grant and UL transmission without UL grant
`
`
`References
`
`IV.
`
`[1] Chairman’s note, RAN1 NR AH #2
`[2] R1-1718435 – “Discussion on CQI and MCS”, Ericsson, RAN1#90bis, Prague, October 2017.
`
`
`
`9
`
`