3GPP TSG RAN WG1 Meeting 91 R1-1719932
`Reno, USA, November 27th – December 1st, 2017
`Agenda Item:
`7.3.3.4
`Source:
`LG Electronics
`Title:
`Remaining issues on UL data transmission procedure
`Document for: Discussion and decision
`
`1. Introduction
`In this contribution, we provide our views on the design of UL data transmission with and without grant.
`Especially, we focus on transmission procedure of UL data transmission without grant, including resource
`configuration for repetition and TB identification. We also propose our view on relationship between semi-
`persistent CSI and UL data transmission without grant.
`2. Uplink data transmission with grant
`In RAN1#90bis meeting [1] and RAN2#99bis meeting [2], followings are agreed relevant to SR resource
`configuration:
`
`Agreements:
`•
`For each “SR configuration”, the following is indicated via RRC
`– A periodicity and offset which identify the slots/symbols to be used for SR
`•
`FFS the offset for the SR periodicity shorter than one slot for a given SCS
`• Non-periodic SR solutions to meet URLLC latency requirements are not precluded
`• At least support following as the periodicity of resources for SR
`– FFS other values with taking into account the alignment with 14 symbols
`
`
`Agreements:
`•
`1. An SR configuration consists of a collection of sets of PUCCH resources across different BWPs and cells
`with the following constraints:
`– Per cell, at any given time there is at most one usable PUCCH resource per LCH
`– This corresponds to the case of one single LTE-like set of SR PUCCH resources being configured
`per LCH per BWP, and only one BWP being active at a time
`2. Each LCH is mapped to none or one SR configuration.
`3. Each SR configuration has its own SR counter and prohibit timer.
`– This counter and timer control the SR configuration i.e. SR procedures on the group of LCHs
`mapped to the SR configuration in question.
`– When max SR transmission counter is reached on a SR configuration, SR failure is declared and
`the UE triggers a RACH and releases all PUCCH resources.
`– SR counters and timers are independent across different configurations.
`4 BWP switching and cell activation / deactivation do not interfere with the operation of the counter and
`timer.
`5 The selection of which valid PUCCH resource for SR to signal SR on when the MAC entity has more than
`one valid PUCCH resource for SR in one ‘TTI’ is left to UE implementation.
`FFS Maximum number of SR configurations/PUCCH resource per MAC entity
`
`•
`•
`
`•
`
`•
`
`•
`
`
`
`APPLE 1006
`
`1
`
`

`

`2.1. SR periodicity and offset with Slot format
`Since SR configuration is semi-static configuration, it is necessary to define how to handle the case where SR
`occasion occurs in non-UL symbols indicated by slot format indicated in dynamic SFI/semi-static DL/UL
`assignment. Given dynamic TDD operation, particularly based on dynamic SFI, where a UE can transmit SR
`need to be clarified. In applying periodicity and offset of a SR configuration, following option can be
`considered to count periodicity and/or offset:
`
` Option 1: Count only semi-statically configured fixed UL resource
`
` Option 2: Count only semi-statically configured fixed and flexible UL
`
` Option 3: Periodicity and offset are applied in number of slots/OFDM symbols regardless of
`actual resource type
`
`Option 1 has no ambiguity but it has less flexibility since SR occasion can occur only on semi-static UL
`resource. In Option 3, periodicity and offset in configuration means absolute time. It may help achieving target
`latency by adjusting periodicity. However, if UE configured with larger periodicity, it is hard for gNB to
`allocate UL slot/mini-slot/symbol at a proper time. Option 2 is more flexible way than other options. In this
`case, SR occasion can occur on semi-static UL and flexible resource. However, if Option 2 is used, some
`further clarification on less than slot level periodicity is needed. As each slot can have different number of
`UL/flexible symbols, this becomes a bit challenging to apply in less than slot periodicity. Considering this, our
`proposal is
`
`Proposal 1: Select between two options.
`
` Alt 1: Regardless of slot or mini-slot level periodicity, consider Option 3
`
` Alt 2: For slot-level periodicity/offset, Option 2 is adopted, and for less than slot-level periodicity,
`Option 3 is adopted. When Option 2 is considered, UL/flexible slot where the configured PUCCH
`for SR can be transmitted is considered as valid UL slot.
`
`When Option 3 is considered, there are some cases where SR cannot be transmitted. First, the slot or
`resource can be DL resource or there is no sufficient UL/flexible resource to transmit the configured PUCCH
`for SR transmission. In such cases, SR needs to be postponed to the next available SR occasion or next
`available PUCCH/PUSCH transmission where SR can be piggybacked.
`
`Proposal 2: At a SR occasion, if the resources are either DL or reserved, SR is not transmitted. It can be
`transmitted either at next available SR occasion or next available PUCCH/PUSCH transmission. The
`dropped SR needs to be informed to the higher layer.
`
`Proposal 3: At a SR occasion, if there is no sufficient UL/flexible resources to transmit the configured
`PUCCH for SR, SR is not transmitted. It can be transmitted either at next available SR occasion or next
`available PUCCH/PUSCH transmission. The dropped SR needs to be informed to the higher layer.
`
`2
`
`

`

`2.2. SR configuration of periodicity shorter than a slot
`From above agreement of last meeting, a scheduling request can be configured with symbol-level periodicity.
`Even though symbol-level periodicity is configured, it is not desirable that SR PUCCH is mapped across slot
`boundary. To keep slot boundary with symbol-level periodicity, one way is to drop SR PUCCH crossing slot
`boundary. This approach has benefit for dynamic TDD case, however we have to discuss about how to assign
`PUCCH resource in symbol level without considering the slot. Alternative way is SR occasion pattern for a
`slot. The SR occasion pattern would have symbol-level periodicity in a slot. By repeating this slot for every
`slot, we can get symbol-level periodicity without violation slot boundary. In this option, we can re-use agreed
`PUCCH allocation method for other UCI such as HARQ-ACK.
`
`Proposal 4: For SR configuration with periodicity shorter than a slot,
`
` SR configuration has SR occasion pattern for a slot.
`
` Every slot has same SR occasion pattern.
`
`
`
`In order to define SR occasion pattern, following options can be considered where we prefer Option
`1.
`
` Option 1: only one PUCCH resource is indicated in SR configuration for first SR occasion in
`a slot. Other SR occasion in a slot is implicitly indicated by repetition of the PUCCH resource
`with given periodicity.
`
` Option 2: PUCCH resources for all of SR occasion in a slot is explicitly indicated in SR
`configuration.
`
`
`3. Uplink data transmission without grant
`In RAN1#90bis meeting [1] and email discussion on UL transmission without grant [3], followings are agreed
`relevant to UL transmission without grant:
`
`Agreements:
`• At least support following periodicities of resources for UL transmission without UL grant
`– FFS other values with taking into account the alignment with 14 symbols
`Agreements:
`• For UL transmission without UL grant, for each configuration
`– The number of configured HARQ processes is explicitly configured by RRC
`– Each configuration can have multiple HARQ processes
`• The value range is {1, 2, …, M}, where M value is FFS
`
`Agreements:
`• For Type 1 and Type 2 UL transmission without grant, RNTI(s) is/are configured by UE-specific RRC
`signaling.
`– Whether the same or different RNTI(s) for Type 1 and Type 2 can be decided by RAN2.
`• Within each type, an RNTI is configured by UE-specific RRC signaling at least for one resource configuration
`in a serving cell
`
`
`
`Agreements:
`• For UL transmission without UL grant,
`
`3
`
`

`

`– The HARQ ID for a TB should be the same during the repetitions and retransmissions if any.
`– The HARQ ID is at least determined by
`• the number of HARQ processes in the configuration
`• the time-domain resource for the UL data transmission
`• FFS: other factors such as frequency-domain resource, DMRS, repetition K dependency on
`initial transmission.
`
`
`
`Working assumption:
`• For UL transmission without UL grant, for a TB transmission with K repetitions
`– The repetitions follow an RV sequence and it is configured by UE-specific RRC signalling to be
`one of the following:
`• Sequence 1: {0, 2, 3, 1}
`• Sequence 2: {0, 3, 0, 3}
`• Sequence 3: {0, 0, 0, 0}
`
`
`3.1. Aspects of Resource configuration
`In agreement from RAN1 NR#2 meeting, we have “a resource” in each configuration for UL data transmission
`without grant. For “a resource”, a configuration has “a resource” with periodicity and offset and one TB is
`mapped to “a resource”. Considering K repetitions including initial transmission, the gNB has to configure
`resources to UE for following repetitions as well as initial transmission. However, meaning of “a resource” is
`a bit ambiguous. To clarify this, we can consider two different interpretation of “a resource” for one TB in
`note:
`
` Option 1: “one TB” is mapped across K repetition including initial transmission. In this case, “a
`resource” can be interpreted as K transmission occasion for all of the K repetition including first
`repetition transmission.
`
` Option 2: “one TB” is mapped onto each transmission of K repetition. In this case, “a resource” can
`be interpreted only one transmission occasion for either first repetition transmission or other
`successive repetition
`
`For Option 1, each configuration has K transmission occasion in one periodicity for K repetition.
`Resources for K transmission occasion can be configured implicitly (consecutive or periodic) or explicitly
`(periodic or patterned). For Option 2, each configuration has only one transmission occasion in one periodicity.
`In this case, K transmission occasion across multiple periodicity is used for K repetitions.
`
`Considering that the number of repetition K is UE-specific, it would not be beneficial to restrict UE
`sharing the same resource to UE having same K. In Option 2, the number of transmission occasion in a
`periodicity is tied with the number of repetitions K. It means it is hard to share same resource among multiple
`UE having different K. In this sense, it can be preferred to allocate a single periodic resource to UE without
`consideration of K and each UE uses K transmission occasions within K times periodicity for repetition.
`
`In those point of view, we propose that Option 2 is understood as the agreement, and focus on a single resource
`per resource configuration in Rel-15 at least before December.
`
`4
`
`

`

`
`
`Figure 1 possible options of resource configuration
`
`
`
`Proposal 5: For resource configuration of UL data transmission without grant,
`
` Clarify that previous agreement for “a resource” means a transmission occasion in a periodicity.
`
` Single periodic “a resource” per resource configuration is prioritized.
`
` Definition of “a resource” can be following:
`
` “a resource” means one transmission occasion for either initial transmission or repetition.
`
` Repetition occurs sequentially utilizing the configured resource.
`
`Regardless of those options, it can be considered to restrict timing of initial transmission in order to use
`this timing as an anchor point of repetitions. Especially, this anchor point can be used for differentiation of
`resource used for first repetition from resources used for other successive repetitions. This is mainly useful for
`HARQ PID determination based on the resource of first repetition. If latency is not concerned, this approach
`can be considered to simplify HARQ PID determination and procedure for UL transmission without grant.
`However, we generally prefer no restriction of initial transmission (i.e., first repetition) as the main motivation
`of UL transmission without grant is to reduce the latency.
`
`Proposal 6: Initial transmission without grant can start at any configured resource for UL data transmission
`without grant.
`
`
`3.2. Simultaneous configuration of Type 1 and Type 2 UL TX w/o grant
`The main difference between two types is modification capability by L1 signalling. Furthermore, each type
`can be used for different purpose/applications. To be specific, Type 2 UL transmission without grant can be
`
`5
`
`

`

`used for VoIP like LTE SPS. Since there is only one Type 2 configuration in a serving cell, UE cannot use
`simultaneously multiple URLLC service but also URLLC service and VoIP or eMBB service. In this sense, it
`is necessary to support Type 1 and Type 2 simultaneously. When they are configured simultaneously, it is
`necessary to have a mechanism to differentiate UL grant for which configuration. One simple approach is to
`assign different RNTI per each type configuration.
`
`Proposal 7: UE can be configured with both of types UL data transmission without grant simultaneously.
`3.3. RV sequences
`The selected three RV sequences are under working assumption. In our view, two configurations are
`sufficient given that there is no clear benefits of {0, 3, 0, 3}. It can at least save RRC overhead, and also
`possibly DCI overhead if type 2 can use RV sequence to be dynamically indicated as alternative way.
`Furthermore, the selected RV sequences would be also used for grant-based multi-slot transmission, where
`scheduling may also indicate the RV sequence.
`
`Remaining issues are the followings:
`
`(1) Default RV sequence: considering RRC signalling overhead (e.g., RMSI overhead in case repetition
`is used for Msg 3), we consider it is beneficial to have a default RV sequence. For that at least for
`type1/2 configuration, {0, 0, 0, 0} would be more appropriate.
`
`(2) Applying RV sequence per each repetition or over multiple repetitions. For example, if large number
`of repetitions is configured, it could be more desirable to apply RV sequences in a unit of multiple
`slots/repetitions instead of single slot/repetition to enable chase combining. So, applying RV
`sequences differently (i.e., a unit of M repetitions where M can be ceil (K/4)) considering different
`number of repetitions can be considered.
`
`
`
`Proposal 8: Default RV sequence can be defined or configured for any repetition as well as UL data
`transmission without grant
`
`Proposal 9: For applying RV sequence of length M to K repetition, a method for applying RV sequence can
`be changed according to K.
`3.4. HARQ PID determination
`The gNB would need to identify transport block to schedule possible retransmission for the failed transport
`block of UL transmission without grant and to support potential HARQ combining among the repetitions
`associated with the same transport block. In case of UL transmission with grant, UL grant could indicate
`transport block to be transmitted in terms of HARQ PID. However, in case of UL data transmission without
`grant, it is necessary to define how to identify the TB transmitted without grant. In previous e-mail discussion
`on UL data transmission without grant, it has been agreed that HARQ PID is determined at least by time-
`
`6
`
`

`

`domain resource and the number of HARQ process in a configuration. Considering the agreement, followings
`are possible options for identification of the TB transmitted without grant:
`
` Option 1: HARQ PID is determined by a function of resource index of the initial transmission without
`grant among K repetition.
`
` Option 2: HARQ PID is determined by a function of resource index of the each transmission without grant
`among K repetition.
`
`For both of options, at least time-domain resource index is used for deriving HARQ PID. When using
`time-domain resource index, these approach can be similar to HARQ ID determination used in LTE SPS. The
`main difference of those options is how to derive HARQ PID of repetitions.
`
`In Option 1, it is necessary for UE to indicate which transmission is initially transmitted. For this, UE
`may use different time/frequency resource or RS parameter for initial transmission. This indication can be
`useful anchor point for repetition and RV cycling, however, it also reduce the number of UE to be distinguished
`in the same time and frequency resources.
`
`For Option 1, it is possible that the network may have not detected the first transmission correctly in
`such case different HARQ ID is derived in case of repetition. To avoid such a case, another approach is to map
`the same HARQ ID over the multiple for example time resources such that the transmissions including
`initial/repetition within the window can be mapped to the same HARQ ID. In Option 2, HARQ PID is
`determined by time-domain resource index for each UL transmission without grant including repetitions. In
`the case of identifying HARQ PID, this options does not depend on first transmission, rather HARQ PID is
`determined by a set of resources (e.g., every M resources share the same HARQ PID). Therefore, there is no
`need to indicate transmission order at least for HARQ PID determination.
`
`Figure 2 shows difference between Option 1 and Option 2 with above approach. As in figure 2(b), In
`case initial transmission (i.e., first repetition) starts in the middle of M resources where the remaining resources
`are less than the number of repetitions, either we drop the remaining repetitions with different HARQ PID
`from the initial transmission or the UE may continue repetition with different HARQ PID. If the latter is used,
`the network may not be able to combine repetitions with different HARQ PIDs. However, this can increase
`the reception probability when collision probability is high.
`
`7
`
`

`

`
`
`Figure 2 difference between Option 1 and Option 2
`
`The proper option may also depend on how resource configuration is done to support repetition. For example,
`if the resource configuration identifies potential candidates where initial transmission would occur, Option 1
`can be preferred. Or, if the resource is shared between initial and retransmission, Option 2 would work better.
`
`Proposal 10: To determine HARQ PID for UL data transmission without grant,
`
` Joint decision of HARQ ID determination with resource configuration for initial/retransmission
`is necessary.
`
` FFS between
`
` Option 1: HARQ PID is determined by resource index of initial transmission
`
` HARQ PID of repetition is following determined HARQ PID of initial transmission
`
` Option 2: HARQ PID is determined by resource index of each transmission
`
` Resource index in time-domain can be SFN, slot index, mini-slot and/or symbol index
`
` FFS whether resource index also include RS parameter and/or frequency index
`
`
`3.5. HARQ-ACK feedback
`To determine HARQ-ACK state of UL data transmission without grant, it is necessary to define UE behavior
`related HARQ procedure at least after K repetitions. If UE doesn’t get any feedback until the end of K
`repetitions, it can be considered UE can assume HARQ-ACK state. After finishing K repetition, a UE can wait
`for retransmission grant or may start a new transmission (with the same TB) via UL transmission without grant.
`From the network perspective, when a UE starts the new transmission, HARQ-ACK combining with previous
`
`8
`
`

`

`transmission is not assumed as the network does not know whether it is for the same TB or not. Or, the UE
`does not assume neither NACK nor ACK until the timer expires to flush the buffer.
`
`Proposal 11: No specific handling or assumption is made when a UE has not received any UL grant after
`finishing transmission of K repetition. A UE may restart initial transmission based on UL transmission
`without grant, or wait until HARQ-ACK timer expires for HARQ-ACK buffer flushing.
`
`If UL data transmission without grant supports some features such as ACK-based termination of repetition or
`retransmission without grant, gNB may need additional HARQ-ACK feedback. We can consider following
`options from previous agreement:
`
` Option 1: Based on UL grant to indicate “ACK”
`
` Option 2: Group-common DCI to indicate “ACK” or “ACK or NACK”
`
`For Option 1, we can easily adopt Option 1 by defining a special set of parameter as no resource
`allocation. In this case, option 1 is beneficial in term of specification effort.
`
`For Option 2, considering asynchronous HARQ and multiple HARQ process, it may need to indicate
`multiple HARQ-ACK at the same time for the same UE. Considering that, it is not easy to design group-
`common DCI. To support multiple HARQ-ACK feedback in one DCI for a UE, required bits size may be large.
`However, not to increase blind decoding, a size of group-common DCI should be same as a size of UE-specific
`DCI.
`
`In those points of views, option 1 is preferred to support additional HARQ-ACK feedback if ACK feedback is
`supported.
`
`Proposal 12: If ACK feedback is necessary, UL grant with special state (e.g., no resource allocation) can be
`used as an ACK.
`4. Relationship with semi-persistent CSI
`For another new feature in NR compared with LTE is the support of semi-persistent CSI (SP-CSI)
`reporting on PUSCH. In RAN1 NR#3, the support of semi-persistent CSI reporting on PUSCH was agreed.
`As Type 2 UL data transmission without grant, SP-CSI on PUSCH will be activated/deactivated by DCI. In
`this sense, it is possible to introduce same/similar procedure to UL data transmission without grant for SP-CSI.
`In design of SP-CSI, we need to consider how to configure ‘resources’ where SP-CSI is transmitted (i.e., semi-
`persistent PUSCH resource configurations) and how to activate such resource/SP-CSI.
`
`Before discussing details of configuration and activation, it needs to be clarified whether the configured
`PUSCH resource for SP-CSI can also carry UL-SCH. If it is assumed that PUSCH for SP-CSI transmits only
`SP-CSI without UL-SCH, it is considered as UCI piggyback on PUSCH without UL-SCH. In this sense, there
`should be a mechanism to separate SP-CSI PUSCH configurations from other type 1/2 configurations. If it is
`assumed that PUSCH for SP-CSI can also carry UL-SCH, it is generally very similar to type 2 configurations.
`As type 2 resource for UL-SCH can be periodic and there is possibility that SP-CSI periodicity for UL-SCH
`
`9
`
`

`

`and type 2 periodicity are aligned, possibility to configure PUSCH resource for SP-CSI both with and without
`UL-SCH could be necessary.
`
`Proposal 13: In configuration of PUSCH for SP-CSI, it can be configured whether the resource can carry
`UL-SCH or not.
`
`
`
`Given the similarity in terms of functionality, type 2 framework could be reused for SP-CSI with some
`clarification.
`
`(1) At least two type 2 configurations are supported in a given cell
`
`A. When two configurations are given, one is configured for SP-CSI without UL-SCH, and the other
`is configured for type 2 with UL-SCH.
`
`B. When single configuration is given, one type 2 configuration can be used for UL-SCH only or
`UL-SCH with SP-CSI if SP-CSI is activated.
`
`(2) In activation DCI for type 2, if two configurations are given,
`
`A. Different RNTI is used between PUSCH for SP-CSI without UL-SCH and PUSCH for type 2
`with UL-SCH
`
`(3) In activation DCI for type 2, if one configuration is given
`
`A. In activation DCI, if aperiodic CSI is triggered, it is considered that SP-CSI is validated.
`Otherwise, it is considered that aperiodic CSI is not activated.
`
`
`
`If dedicated configurations are assumed for SP-CSI PUSCH different from type 2 configuration where SP-CSI
`PUSCH can only carry CSI without UL-SCH, separate RNTI may be used between different configurations.
`A similar mechanism of L1 based activation can be used similar as two type 2 configuration cases in the above.
`
`It needs to be also clarified that whether there is one SP-CSI reporting configuration per a given cell or there
`can be multiple SP-CSI reporting configurations where one or more can be dynamically selected by L1
`activation signalling. This can be further discussed in MIMO session. In general, if L1 singling needs to also
`select one or more SP-CSI reporting configurations, we can consider to reuse aperiodic CSI trigger field in UL
`grant. In other words, aperiodic CSI trigger field is reused to activate one or more of SP-CSI configurations.
`It is assumed that a UE is configured semi-statically the mapping between value of aperiodic CSI trigger with
`a set of SP-CSI configurations.
`
`Proposal 14: To achieve higher reliability of SP-CSI on PUSCH,
`
` Use different RNTI from RNTI used for grant-based transmission.
`
`10
`
`

`

` Following two options including down-selection should be further considered
`
` Option 1: using one of RNTI(s) for Type 1 UL data transmission without grant
`
` Option 2: using one of RNTI(s) for Type 2 UL data transmission without grant
`5. Handling dynamic changing of BWP
`Semi-static resource configurations, including SR, SPS/grant-free and SP-CSI configuration, may be
`affected by changing BWP. Especially PUSCH configuration like SPS/grant-free, Activated/changed BWP
`can have different number of RB from previously activated BWP. In this case, PUSCH allocated on previous
`BWP should be deactivated or changed. In other word, when BWP is deactivated, related configured resource
`can be also deactivated or unavailable autonomously.
`
`For seamless working of these configuration, UE can be configured with a set of multiple UL resource
`across multiple BWP and/or BWP candidates. In this approach, when a BWP is activated (or deactivated),
`related UL resource can be also available (or unavailable), respectively. In addition to this, a subset of UL
`resources in a set can be configured and/or indicated as usable or unusable by higher layer signalling and/or
`L1 signalling. In this case, only usable UL resources can change into available resource.
`
`To be more specific, our proposal is as follows.
`
`Proposal 15: For type 1 resource configurations, separate resource configurations per configured UL BWP
`is assumed. The configuration in the currently active UL BWP is assumed to be valid for type 1 resource.
`
`Proposal 16: For type 2 resource configurations, we can consider two approaches.
`
` Approach 1: Validation is for the current active UL BWP only. When active UL BWP is changed,
`it is considered that previously activated type 2 resource is automatically invalidated. New
`validation on the new active UL BWP is necessary for type 2 resource in this case. Similar approach
`is applied to SP-CSI PUSCH if it’s based on L1 signaling based activation.
`
` Approach 2: Upon validating type 2 resource, activation on multiple resources (one resource per
`each BWP) can be considered. Further details should be discussed if this approach is adopted. For
`example, at least PUSCH resources are semi-statically configured per BWP, L1 signaling can
`indicate which resources are activated across multiple BWPs.
`
`As each approach has pros and cons (e.g., Approach 1 requires transmitting activation DCI whenever UL BWP
`switches, and Approach 2 requires some more specification works), one possible approach is to allow sending
`validation/invalidation DCI with BWP index which activate/deactivate resources in the indicated BWP. This
`validation/invalidation DCI would not switch BWP. In summary, it can be as the follows.
`
`- Validation/Invalidation of a type 2 resource or SP-CSI PUSCH is validated/invalidated only by L1
`signaling. No assumptions across BWP switching.
`
`11
`
`

`

`- Validation/invalidation signaling can include BWP index which activate/deactivate resources of non-
`active BWP.
`
`- When BWP switching occurs, a UE can assume a type 2 resource or SP-CSI PUSCH is valid if it has
`been already activated.
`
`Proposal 17: For UL data transmission without grant and/or SP-CSI,
`
` Validation/Invalidation of a type 2 resource and/or SP-CSI PUSCH is validated/invalidated only
`by L1 signaling. No assumptions across BWP switching.
`
` Validation/invalidation signaling can include BWP index which activate/deactivate resources of
`non-active BWP.
`
` When BWP switching occurs, a UE can assume a type 2 resource and/or SP-CSI PUSCH is valid
`if it has been already activated.
`
`
`6. Conclusion
`In this contribution, we discuss on UL transmission with/without grant. Our proposals are as follows:
`
`Proposal 1: Select between two options.
`
` Alt 1: Regardless of slot or mini-slot level periodicity, consider Option 3
`
` Alt 2: For slot-level periodicity/offset, Option 2 is adopted, and for less than slot-level periodicity,
`Option 3 is adopted. When Option 2 is considered, UL/flexible slot where the configured PUCCH
`for SR can be transmitted is considered as valid UL slot.
`
`Proposal 2: At a SR occasion, if the resources are either DL or reserved, SR is not transmitted. It can be
`transmitted either at next available SR occasion or next available PUCCH/PUSCH transmission. The
`dropped SR needs to be informed to the higher layer.
`
`Proposal 3: At a SR occasion, if there is no sufficient UL/flexible resources to transmit the configured
`PUCCH for SR, SR is not transmitted. It can be transmitted either at next available SR occasion or next
`available PUCCH/PUSCH transmission. The dropped SR needs to be informed to the higher layer.
`
`Proposal 4: For SR configuration with periodicity shorter than a slot,
`
` SR configuration has SR occasion pattern for a slot.
`
` Every slot has same SR occasion pattern.
`
`
`
`In order to define SR occasion pattern, following options can be considered where we prefer Option
`1.
`
`12
`
`

`

` Option 1: only one PUCCH resource is indicated in SR configuration for first SR occasion in
`a slot. Other SR occasion in a slot is implicitly indicated by repetition of the PUCCH resource
`with given periodicity.
`
` Option 2: PUCCH resources for all of SR occasion in a slot is explicitly indicated in SR
`configuration.
`
`Proposal 5: For resource configuration of UL data transmission without grant,
`
` Clarify that previous agreement for “a resource” means a transmission occasion in a periodicity.
`
` Single periodic “a resource” per resource configuration is prioritized.
`
` Definition of “a resource” can be following:
`
` “a resource” means one transmission occasion for either initial transmission or repetition.
`
` Repetition occurs sequentially utilizing the configured resource.
`
`Proposal 6: Initial transmission without grant can start at any configured resource for UL data transmission
`without grant.
`
`Proposal 7: UE can be configured with both of types UL data transmission without grant simultaneously.
`
`Proposal 8: Default RV sequence can be defined or configured for any repetition as well as UL data
`transmission without grant
`
`Proposal 9: For applying RV sequence of length M to K repetition, a method for applying RV sequence can
`be changed according to K.
`
`Proposal 10: To determine HARQ PID for UL data transmission without grant,
`
` Joint decision of HARQ ID determination with resource configuration for initial/retransmission
`is necessary.
`
` FFS between
`
` Option 1: HARQ PID is determined by resource index of initial transmission
`
` HARQ PID of repetition is following determined HARQ PID of initial transmission
`
` Option 2: HARQ PID is determined by resource index of each transmission
`
` Resource index in time-domain can be SFN, slot index, mini-slot and/or symbol index
`
` FFS whether resource index also include RS parameter and/or frequency index
`
`13
`
`

`

`Proposal 11: No specific handling or assumption is made when a UE has not received any UL grant after
`finishing transmission of K repetition. A UE may restart initial transmission based on UL transmission
`without grant, or wait until HARQ-ACK timer expires for HARQ-ACK buffer flushing.
`
`Proposal 12: If ACK feedback is necessary, UL grant with special state (e.g., no resource allocation) can be
`used as an ACK.
`
`Proposal 13: In configuration of PUSCH for SP-CSI, it can be configured whether the resource can carry
`UL-SCH or not.
`
`Proposal 14: To achieve higher reliability of SP-CSI on PUSCH,
`
` Use different RNTI from RNTI used for grant-based transmission.
`
` Following two options including down-selection should be further considered
`
` Option 1: using one of RNTI(s) for Type 1 UL data transmission without grant
`
` Option 2: using one of RNTI(s) for Type 2 UL data transmission without grant
`
`Proposal 15: For type 1 resource configur