WIPO

L N WORLD
Digital Access Service INTELLECTUAL PROPERTY
(DAS) ORGANIZATION

CERTIFICATE OF AVAILABILITY OF A CERTIFIED PATENT DOCUMENT IN A

DIGITAL LIBRARY

The International Bureau certifies that a copy of the patent application indicated
below has been available to the WIPO Digital Access Service since the date of
availability indicated, and that the patent application has been available to the
indicated Office(s) as of the date specified following the relevant Office code:

Document details: ~ Country/Office: US

Filing date: 16 Aug 2019 (16.08.2019)
Application number: 62888051

Date of availability of document: 27 Aug 2019 (27.08.2019)

The following Offices can retrieve this document by using the access code:
AR, AU, BR, CA, CL, CN, DK, EA, EE, EP, ES, FI, GB, GE, IB, IL, IN,
JP, KR, MA, NL, NO, NZ, SE, US

Date of issue of this certificate: 04 Sep 2020 (04.09.2020)

34, chemin des Colombettes

1211 Geneva 20, Switzerland
 TED STATES DEPARTMENT OF COMMERCE
United States Patent and Trademark Office

September 04, 2020

THIS IS TO CERTIFY THAT ANNEXED HERETO IS A TRUE COPY FROM

THE RECORDS OF THE UNITED STATES PATENT AND TRADEMARK
OFFICE OF THOSE PAPERS OF THE BELOW IDENTIFIED PATENT
APPLICATION THAT MET THE REQUIREMENTS TO BE GRANTED A
FILING DATE UNDER 35 USC 111.

APPLICATION NUMBER: 62/888,051

FILING DATE: August 16, 2019

St
THE COUNTRY CODE AND NUMBER OF YOUR PRIORITY
APPLICATION, TO BE USED FOR FILING ABROAD UNDER THE PARIS
CONVENTION, IS US62/888,051

i
Certified by

Poiclion v
Unider Secrctary of Commérce
for Intellectual Property
and Dircetor of the United States
Patent and Trademark Office
 Electronic Acknowledgement Receipt

EFS ID: 36901380

Application Number: 62888051

International Application Number:

Confirmation Number: 3279

Title of Invention: Mechanism for HARQ Feedback of Sidelink Resource Allocation Mode 1

First Named Inventor/Applicant Name: YU-HSIN CHENG

Customer Number: 54000

Filer: Alvin Sean Koan

Filer Authorized By:

Attorney Docket Number: us78171

Receipt Date: 16-AUG-2019

g Date:

Time Stamp: 16:01:43

Application Type: Provisional

Payment information:
Submitted with Payment yes

Payment Type DA

Payment was successfully received in RAM $280

RAM confirmation Number E20198FG02141363
Deposit Account

Authorized User

The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
File Listing:
Document i e " File Size(Bytes)/ Pages
Number Document Description File Name Message Digest (if appl.)

2032286
1 Provisional Cover Sheet (SB16) US78171-SB16.pdf no 4
errsnaasnossen a1
s

Warnings:
Information:

129380
Auth or Resc of Auth to Access Appl by
2 US78171-5839.pdf no 2
DAS/PDX Office eSS SN0 TSRS
et

Warnings:
Information:

498933
3 Specification US78171-SPEC.pdf no 28
cetisasdiaccracsnsasescrscos10ase
o

Warnings:

Information:
29973
4 Fee Worksheet (SB06) fee-info.pdf no 2
Rt S 0047 202D
[

Warnings:
Information:
Total Files Size (in byces){ 2690572
This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
Post Card, as described in MPEP 503.

New Applications Under35 U.5.C. 111

If a new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
1.53(b)-(d)
and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
Acknowledgement Receipt will establish the filing date of the application.
National Stage of an International Application under 35 U.S.C. 371
If a timely submission to enter the national stage of an international application is compliant with the conditions of 35
U.5.C. 371 and other applicable requirements a Form PCT/DO/EO/903 indic: g acceptance of the application as a
national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
New International Application Filed with the USPTO as a Receiving Office
If a new international application is being filed and the international application includes the necessary components for
an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number
and of the International Filing Date (Form PCT/RO/105) will be issued in due course, subject to pres: ions concerning
national security, and the date shown on this Acknowledgement Receipt establish the international g date of
the application.
Doc Code: TR.PROV
Document Description: Provisional Cover Sheet (SB16)
PTO/SBI16 (02-18)
Approved for use through 11/30/2020. OMB 0651-0032
U.S. Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
Under the Paperwork Reduction Act of 1995, no persons are required to responid to a callection of information unless it displays a valid OMB control number
Provisional Application for Patent Cover Sheet
This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 CFR 1.53(c)
Inventor(s)

Inventor 1 Remove

Given Name Middle Name Family Name City State Country i

tU-HSIN I EHENG I hsinchu I w

Inventor 2 Remove

Given Name Middle Name Family Name City State Country j

tUNG-LAN I I SENG I tsinchu I Tw

Inventor 3

Given Name Middle Name Family Name City State Country j

MEI-JU EHiH Hsinchu rw

Inventor 4

Given Name Middle Name Family Name City State Country

[HunG-cHEN [cHEN |sinchu rw

All Inventors Must Be Listed — Additional Inventor Information blocks may be Add
generated within this form by selecting the Add button.

Title of Invention |Vlechanism for HARQ Feedback of Sidelink Resource Allocation Mode 1

Attorney Docket Number (if applicable) us78171

Correspondence Address

Direct all correspondence to (select one):

(® The address corresponding to Customer Number (O Firm or Individual Name

Customer Number kdOOO

The invention was made by an agency of the United States Government or under a contract with an agency of the United
States Government.

® No.
Yes, the invention was made by an agency of the United States Government. The U.S. Government agency name is:
Yes, the invention was under a contract with an agency of the United States Government. The name of the U.S.
Government agency and Government contract number are:
EFS - Web 102
Doc Code: TR.PROV
Document Description: Provisional Cover Sheet (SB16)
PTO/SBI16 (02-18)
Approved for use through 11/30/2020. OMB 0651-0032
U.S. Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
Under the Paperwork Reduction Act of 1995, no persons are required to responid to a callection of information unless it displays a valid OMB control number

EFS - Web 102

Doc Code: TR.PROV
Document Description: Provisional Cover Sheet (SB16)
PTO/SBI16 (02-18)
Approved for use through 11/30/2020, OME 0651-0032
U.S. Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it cisplays a valid OMB control number

Entity Status
Applicant asserts small entity status under 37 CFR 1.27 or applicant certifies micro entity status under 37 CFR 1.29

) Applicant asserts small entity status under 37 CFR 127

(O Applicant certifies micro entity status under 37 CFR 1.29. Applicant must attach form PTO/SB/15A or B or equivalent.
@® No

Warning
Petitioner/applicant is cautioned to avoid submitting personal information in documents filed in a patent application that may
contribute to identity theft. Personal information such as social security numbers, bank account numbers, or credit card
numbers (other than a check or credit card authorization form PTO-2038 submitted for payment purposes) is never required
by the USPTO to support a petition or an application. If this type of personal information is included in documents submitted
to the USPTO, petitioners/applicants should consider redacting such personal information from the documents before
submitting them to USPTO. Petitioner/applicant is advised that the record of a patent application is available to the public
after publication of the application (unless a non-publication request in compliance with 37 CFR 1.213(a) is made in the
application) or issuance of a patent. Furthermare, the record from an abandoned application may also be available to the
public if the application is referenced in a published application or an issued patent (see 37 CFR1.14). Checks and credit
card authorization forms PTO-2038 submitted for payment purposes are not retained in the application file and therefore are
not publicly available.

Signature

Please see 37 CFR 1.4(d) for the form of the signature.

Signature IAlvin Koan/ Date (YYYY-MM-DD) P019-08-16

First Name Ivin Last Name 0an Regisiraiio_n Number Lsass

(If appropriate)

This collection of information is required by 37 CFR 1.51. The information is required to obtain or retain a benefit by the public which is to
file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection
is estimated to take 8 hours to complete, including gathering, preparing, and submitting the completed application form to the USPTO.
Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or
suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department
of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. This
form can only be used when in conjunction with EFS-Web. If this form is mailed to the USPTO, it may cause delays in handling
the provisional application.

EFS - Web 102

 Privacy Act Statement

The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of
the attached form related to a patent application or paten. Accordingly, pursuant to the requirements of the Act, please be
advised that : (1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the
information solicited is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and
Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not
furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your
submission, which may result in termination of proceedings or abandonment of the application or expiration of the patent.

The information provided by you in this form will be subject to the following routine uses:

1. The information on this form will be treated confidentially to the extent allowed under the Freedom of Information
Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C 552a). Records from this system of records may be disclosed to the
Department of Justice to determine whether disclosure of these records is required by the Freedom of Information
Act.
A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to
a court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement
negotiations.
A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a
request involving an individual, to whom the record pertains, when the individual has requested assistance from the
Member with respect to the subject matter of the record.
A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need
for the information in order to perform a contract. Recipients of information shall be required to comply with the
requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).
A record related to an International Application filed under the Patent Cooperation Treaty in this system of
records may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property
Organization, pursuant to the Patent Cooperation Treaty.
A record in this system of records may be disclosed, as a routine use, t o a n other federal agency for purposes
of National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services,
or his/her designee, during an inspection of records conducted by GSA as part of that agency’s responsibility to
recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and
29086. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this
purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make
determinations about individuals.
A record from this system of records may be disclosed, as a routine use, to the public after either publication of
the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record
may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an
application which became abandoned or in which the proceedings were terminated and which application is
referenced by either a published application, an application open to public inspection or an
issued patent.
A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law
enforcement agency, if the USPTO becomes aware of a violation or potential viclation of law or regulation.
 Mechanism for HARQ Feedback of Sidelink Resource
Allocation Mode 1

1. Background
For sidelink resource allocation mode 1:

* Sidelink HARQ ACK/NACK report from transmitter UE to gNB is supported with

details for further study.

2. Problem
In resource allocation mode 1 (note: mode 1 is that BS schedules SL resource(s)

to be used by UE for SL transmission(s)) for unicast and groupcast, it is supported for

the transmitter UE via Uu link to report HARQ feedback to gNB to indicate the need

for retransmission of a TB transmitted by the transmitter UE. Since the HARQ feedback

is transmitted via Uu link, UE may use PUCCH and/or PUSCH to transmit HARQ bits.

However, how to generate HARQ bits for SL is still unclear. For example, in current

HARQ codebook generation procedure (note: described in 3GPP TS 38.213 ch.9.1.2 for

semi-static HARQ codebook and 3GPP TS 38.213 ch.9.1.3 for dynamic HARQ

codebook), HARQ codebook is associated to KO (ie., PDSCH-

TimeDomainResourceAllocationList) and K1 (i.e., dl-DataToUL-ACK) as shown in Figure

0(a).

Figure 0(a), relationship between K0, K1, PDCCH and PDSCH

1
 However, the DCI (e.g., DCI_SL) in SL resource allocation mode 1 may contain the

resource allocation information about PSCCH and PSSCH which is a different

mechanism from Uu design as shown in Figure 0(b) and Figure 0(c), so we may need

new designs to generate HARQ codebook for SL resource allocation mode 1 according

to new parameters KO_1, KO_2 and K1_SL. Furthermore, PUCCH resource for SL may

overlap with PUCCH resource for Uu, so we have to define the behavior when PUCCH

resources overlap.

K1 St PUCCH

Figure O(b), possible relationship between K0_1, KO_2, K1_SL, PDCCH, PSCCH,
PUCCH and PSSCH

PSCCH K1 SL
PUCCH

Figure 0(c), possible relationship between KO_SL, K1_SL, PDCCH, PSCCH, PUCCH

and PSSCH

3. Solution summary
Definition:
1. PSSCH candidate: possible PSSCH resource allocation scheduled by DCI_SL/SCI.
There may be a PSSCH-TimeDomainResourceAllocationList-SCI (note: denoted
as KO_2, and it contains a list of possible values (note: Range of KO_2 may be
reported as UE capability or be (pre-)defined in the specification directly), and
SCI will indicate one of them. The Xth entry in the list is denoted as KO_2_x)
and/or PSSCH-TimeDomainResourceAllocationList-DCI_SL (note: contain a list
of possible KO_SL values, and DCI_SL will indicate one of them. The Xth entry
in the list is denoted as KO_SL_x) in RRC configuration, and they contain a list
of time domain resource allocation information. When generating HARQ
codebook, UE will consider resource indicated by each entry of the list as a
PSSCH candidate.
PSCCH candidate: possible PSCCH resource allocation scheduled by DCI_SL.
There may be a PSCCH-TimeDomainResourceAllocationList-DCI_SL (note:
denoted as KO_1, and it contains a list of possible values, and SCI will indicate
one of them. The Xth entry in the list is denoted as KO_1_x) in RRC
configuration, and it contains a list of time domain resource allocation
information. When generating HARQ codebook, UE will consider resource
indicated by each entry of the list as a PSCCH candidate.
K1_SL: SL_DClcontrolToUL-ACK. It contains a list of timing (or timing gap/offset)
from a given SL HARQ feedback (on PUCCH resource) to the corresponding
PDCCH. The Xth entry In the list s denoted as K1_SL_x
K1_PSCCH: SL_SClcontrolToUL-ACK. It contains a list of timing (or timing
gap/offset) from a given SL HARQ feedback (on PUCCH resource) to the
corresponding PSCCH. The Xth entry in the list is denoted as K1_PSCCH_x
K1_PSSCH: SL_DataToUL-ACK. It contains a list of timing (or timing gap/offset)
from a given SL HARQ feedback (on PUCCH resource) to the corresponding
PSSCH. The Xth entry in the list is denoted as K1_PSSCH_x
The numerology of KO_1, KO_2, KO_SL, K1_SL, K1_PSCCH, and/or K1_PSSCH
may be based on numerology of SL or UL or DL BWP
The granularity of KO_1, KO_2, KO_SL, K1_SL, K1_PSCCH, and/or K1_PSSCH
may be symbol or slot or subframe or sub-slot
If the numerology of KO_1 is based on numerology of SL BWP and the
numerology of SL BWP is larger than numerology of DL BWP, KO_1 =0
corresponds to the first slot/symbol/subframe/sub-slot for the larger SCS
which overlaps with the corresponding PDCCH (note : containing KO_1 which
indicates PSCCH).
In another approach, If the numerology of KO_1 is based on numerology of SL
BWP and the numerology of SL BWP is larger than numerology of DL BWP,
 KO_1 =0 corresponds to the slot/symbol/subframe/sub-slot for the larger
SCS with end boundary aligned to the slot/symbol/subframe/sub-slot for the
corresponding PDCCH (note : containing KO_1 which indicates PSCCH).
If the numerology of KO_1 is based on numerology of SL BWP and the
numerology of SL BWP is smaller than numerology of DL BWP, KO_1 =0
corresponds to the slot/symbol/subframe/sub-slot for the smaller SCS which
overlaps with the corresponding PDCCH (note : containing KO_1 which
indicates PSCCH).
9. If the numerology of K1_PSCCH/K1_PSSCH is based on numerology of SL BWP
and the numerology of SL BWP is smaller than numerology of UL BWP,
K1_PSCCH/K1_PSSCH =0 corresponds to the first slot/symbol/subframe/sub-
slot for the larger SCS which overlaps with the corresponding PSCCH/PSSCH
(note : K1_PSCCH/K1_PSSCH indicates time gap from PSCCH/PSSCH to PUCCH).
In another approach, If the numerology of K1_PSCCH/K1_PSSCH is based on
numerology of SL BWP and the numerology of SL BWP is smaller than
numerology of UL BWP, K1_PSCCH/K1_PSSCH =0 corresponds to the
slot/symbol/subframe/sub-slot for the larger SCS with end boundary aligned
to the slot/symbol/subframe/sub-slot for the corresponding PSCCH/PSSCH
(note : K1_PSCCH/K1_PSSCH indicates time gap from PSCCH/PSSCH to PUCCH)
If the numerology of K1_PSCCH/K1_PSSCH is based on numerology of SL BWP
and the numerology of SL BWP is larger than numerology of UL BWP,
K1_PSCCH/K1_PSSCH =0 corresponds to the slot/symbol/subframe/sub-slot
for the smaller SCS which overlaps with the corresponding PSCCH/PSSCH
(note : K1_PSCCH/K1_PSSCH indicates time gap from PSCCH/PSSCH to PUCCH)
10. The UE may store UE capability in the RAN as part of UE context, UE inactive
context. In addition, the information may be forwarded to (at least) one target
cell by the source cell through backhaul connection for:1) handover procedure,
or 2) for RRC Resume procedure, or 3) for SCG configuration.
11.1f PSSCH and PSCCH is transmitted on the same slot by default, UE may
consider that KO_2 is “0” or there is no parameter “K0_2" in all embodiments
of this PV
12.KO_1, KO_2, KO_SL, K1_PSCCH, K1_PSSCH, and K1_SL may be dynamically
indicated with a minimum applicable value by DCI_SL/DCI/SCI/MAC-CE/MAC-
CE-SL (note: MAC-CE-SL is MAC control element, and MAC-CE-SL is transmitted
on PC5 interface or on SL channel).
Entries in the active table/list with KO_1, KO_2, KO_SL, K1_PSCCH, K1_PSSCH,
and/or K1_SL values smaller than the indicated minimum applicable values are
 not expected by or not valid for the UE.
13. If the slot of PUCCH resource locates on the same time as or aftera slot for an
active DL BWP change on a serving cell or an active UL BWP change on a
serving cell and the slot of a PSSCH/PSCCH candidate is before the slot for the
active DL BWP change on the serving cell or the active UL BWP change on the
serving cell, UE may exclude the PSSCH/PSCCH candidates from generating
HARQ codebook bit.
14. If the slot of PUCCH resource locates on the same time as or after a slot for an
active SL BWP change on a serving cell and the slot of a PSSCH/PSCCH
candidate is before the slot for the active SL BWP change on the serving cell,
UE may exclude the PSSCH/PSCCH candidates from generating HARQ
codebook bit.

31 generate HARQ codebook for SL resource allocation 1

311 excluding PSSCH/PSCCH candidate

1. if at least one symbol of the PSSCH candidate time resource indicated by a
SCl is configured as DL/flexible (i.e., FL), the PSSCH candidate is excluded
from PSSCH candidate lists. Remaining PSSCH candidates are denoted as
valid PSSCH candidates.
if at least one symbol of the PSSCH candidate time resource indicated by a
DCI_SL is configured as DL/FL, the PSSCH candidate is excluded from PSSCH
candidate lists. Remaining PSSCH candidates are denoted as valid PSSCH
candidates.
if at least one symbol of the PSCCH candidate time resource indicated by a
DCI_SL is configured as DL/FL, the PSCCH candidate is excluded from PCCCH
candidate lists. Remaining PCCCH candidates are denoted as valid PSCCH
candidates.
[Mei-Ju] When KO_1 and KO_2 are used, are valid PSSCH/PSCCH candidates
considered? Are original PSSCH/PSCCH candidates considered? After reading
the PV, it seems the original PSSCH/PSCCH candidates are considered when
calculating the KO_1 and KO_2. Is it possible that KO_1 and KO_2 calculate the
valid PSSCH/PSCCH candidates rather than the original PSSCH/PSCCH
candidates?
3.1.2 generating HARQ codebook according to sl-DataToUL-ACK and/or PSSCH time

domain resource allocation

1. If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH

resource or PUSCH resource) and UE is configured to monitor a SCl on PSCCH
in slot n-K1_PSCCH_x, UE may consider the PSSCHs scheduled by the SCI as
PSSCHs candidates according to all entries of KO_2 (i.e., PSSCH-
TimeDomainResourceAllocationList-SCl). In another approach, UE may
consider the PSSCHs scheduled by the DCI_SL as PSSCHs candidates
according to all entries of Ko_SL (i.e., PSSCH-
TimeDomainResourceAllocationList-DCI_SL).
2. If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH
resource or PUSCH resource) and UE is configured to monitor PSSCH in slot
n-K1_PSSCH_x, UE may consider
the PSSCHs scheduled by the SCl as PSSCHs
candidates according to all entries of KO_2 (i.e., PSSCH-
TimeDomainResourceAllocationList-SCl). In another approach, UE may
consider the PSSCHs scheduled by the DCI_SL as PSSCHs candidates
according to all entries of KO_SL (i.e., PSSCH-
TimeDomainResourceAllocationList-DCI_SL).
3. If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH
resource or PUSCH resource), UE is configured to monitor DCI_SL on PDCCH
in slot n-K1_SL_x, and the DCI_SL indicates a PSCCH which contains a SCI
(note: in this solution, DCI_SL only indicate one specific PSCCH resource
location), then UE may consider the PSSCHs scheduled by the SCl as PSSCHs
candidates according to all entries of KO_2 (i.e., PSSCH-
TimeDomainResourceAllocationList-SCI). In another approach, UE may
consider the PSSCHs scheduled by the DCI_SL as PSSCHs candidates
according to all entries of KO_SL (i.e., PSSCH-
TimeDomainResourceAllocationList-DCI_SL).
4. If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH
resource or PUSCH resource), UE is configured to monitor DCI_SL on PDCCH
in slot n-K1_SL_x, and the DCI_SL may indicate more than one PSCCH
candidate which contains a SCI in slot n-K1_SL_x+KO_1_x (note: in this
solution, each entry in Ko_1 (i.e., PSCCH-
TimeDomainResourceAllocationList-DCI_SL) can indicate one PSCCH

6
 candidate), then UE may consider the PSSCHs scheduled by the SCI as
PSSCHs candidates according to all entries of KO_2 (i.e., PSSCH-
TimeDomainResourceAllocationList-SC).
It is noted that these solutions may be applied for both semi-static HARQ
codebook and dynamic HARQ codebook
It is noted that these solutions may be applied for both dynamic SL resource
allocation mode 1 and semi-persistent resource allocation mode 1 (e.g., type
2 configured grant in SL mode 1 (note: type 2 configured grant is configured
by RRC and is activated by DCI-SL) or type 1 configured grant in SL mode 1
(note: type 1 configured grant is activated by RRC configuration))
UE reports SL HARQ-ACK information in a PUCCH only for one (or “X”) PSSCH
for all PSSCH candidates. Note: UE only expects to receive one PSSCH
successfully before UE reports the SL HARQ feedback. In one approach, X
may be reported by UE capability.
HARQ codebook is generated per source ID/UE identity. For example, if
DCI_SL indicates UE to report HARQ feedback on a PUCCH resource, UE will
generates HARQ codebook by excluding PSSCH candidates and/or PSCCH
candidates which are not transmitted from the same source ID/UE identity
as source ID/UE identity contained in the DCI_SL (or specifically SCI
contained in the DCI_SL).

3.2 Configuration of SL HARQ codebook type

Definition:
SL-RRC: RRC signaling transmitted on SL channel
SIB-SL: System Information Block transmitted on SL channel
MIB-SL: Master Information Block transmitted on SL channel

There is a new IE “SL-HARQ-ACK-Codebook” contained in RRC/SL-

RRC/SIB/SIB-SL/MIB-SL, which indicates SL HARQ-ACK codebook is either
semi-static or dynamic. It is noted that this IE may be configured per
resource pool(note: resource pool for scheduled PSCCH and/or PSSCH)/per
BWP(note: can be DL BWP and/or SL BWP and/or UL BWP)/ per anchor
carrier/ per cell/ per cell group (e.g., master cell group and secondary cell
group)/ per UE. In one approach, the IE can be valid in an area composed by
systemInformationArealD, (physical) cell identities list, zones, or ranges, etc.
SL HARQ codebook type may be the same as the HARQ codebook type of the
cell which contains scheduling information (i.e., DCI_SL).
 3. SL HARQ codebook type may be a UE capability, and UE may inform BS
whether it supports dynamic/semi-static/both HARQ codebook type in
sidelink operation

33 Multiplexing UCI and SL HARQ feedback

Definition:
UCI: Uplink control information, which comprises SR, HARQ, and CSI
feedback on PUCCH resource
How to differentiate eMBB and URLLC service on Uu interface: UE may treat
a data in PDSCH as URLLC service if there is an indicator contained in the
scheduling DCI. In another approach, UE may treat a data in PDSCH as URLLC
service according to DCI format. In another approach, UE may treat a data in
PDSCH as URLLC service according to sub-slot numerology for HARQ
feedback. In another approach, UE may treat a data in PDSCH as URLLC
service according to RNTIL. In another approach, UE may treat a data in
PDSCH as URLLC service according to MCS table for the PDSCH.

There is a new |E SL-PUCCHresource contained in RRC/SL-RRC/SIB/SIB-SL,

which indicates PUCCH resource dedicated forSL HARQ feedback. It is noted
that SL-PUCCH resource may not overlap with PUCCH resource for UCl in
time/frequency domain. In one approach, if there is no such IE in RRC/SIB,
UE will consider SL HARQ feedback can multiplex with UCI on PUCCH
resource.
There is a new IE SL-UCI-MUX (note: T/F indicator) contained in RRC/SIB/SIB-
SL/SL-RRC, which indicates whether UE can perform UCI and SL HARQ
multiplexing or not. In one approach, if there is no such IE in RRC/SIB, UE will
consider SL HARQ feedback can multiplex with UCI on PUCCH resource. In
another approach, if there is no such IE in RRC/SIB/SL-RRC/SIB-SL, UE will
consider SL HARQ feedback cannot multiplex with UCI on PUCCH resource.
There is a new IE SL-onPUSCH (note: T/F indicator) contained in RRC/SIB/SIB-
SL/SL-RRC, which indicates whether UE can perform transmit SL HARQ on
PUSCH or not (note: when PUCCH resource contains SL HARQ overlaps with
PUSCH). In one approach, if there is no such IE in RRC/SIB, UE will consider
SL HARQ feedback can transmit on PUSCH. In another approach, if there is
no such IE in RRC/SIB/SIB-SL/SL-RRC, UE will consider SL HARQ feedback

8
cannot transmit on PUSCH.
Itis noted that if UE does not support SL HARQ on PUSCH, UE may transmit
PUSCH and drop SL HARQ when the PUCCH resource of SL HARQ overlaps
with PUSCH.
It is noted that if UE supports SL HARQ on PUSCH, UE may transmit SL
HARQ and drop PUSCH when the PUCCH resource of SL HARQ overlaps with
PUSCH.
Multiplexing UCI and SL HARQ feedback may be a UE capability, and UE may
inform BS whether it supports multiplexing UCI and SL HARQ feedback
There is a new IE for-SL-HARQ, (note: T/F indicator) contained in PUCCH
resource/PUCCH resource set configuration in RRC/SIB. The PUCCH
resource/PUCCH resources contained in PUCCH resource set may contain SL
HARQ feedback if the for-SL-HARQ indicates “T”.
(for SL HARQ and UCI multiplexing case) if the payload size of PUCCH
resource cannot contain all SL HARQ and UCI bits, there may be a priority
rule to decide which information can be transmitted on the PUCCH resource.
For example, URLLC HARQ> eMBB HARQ > SL HARQ > SR > CSl part | > CSI
part Il (note: URLLC HARQ> eMBB HARQ means URLLC HARQ has higher
priority than eMBB HARQ ).
In one approach, the priority of SLHARQ depends on the priority information
indicator (e.g., PPPP) in the scheduling SCI.
In one approach, there is a threshold configured in RRC signaling for UCI of
eMBB (eMBB HARQ or eMBB SR or eMBB CSI feedback). If the priority
information indicator in the scheduling SCl is less than the threshold for UCI
of eMBB (note: smaller value of priority indicator means more important),
UE may drop UCI for eMBB. Otherwise, UE may drop SL HARQ.
In one approach, there is a threshold configured in RRC signaling for UCI of
URLLC (URLLC HARQ or URLLC SR or URLLC CSI feedback). If the priority
information indicator in the scheduling SCl is less than the threshold for UCI
of URLLC (note: smaller value of priority indicator means more important),
UE may drop UCI for URLLC. Otherwise, UE may drop SL HARQ.
It is noted that eMBB and URLLC here refer to eMBB and URLLC service via
Uuinterface.
(for case that SL HARQ and UCI are independently reported) if the
time/frequency domain of SL HARQ PUCCH resource overlaps with UCI
HARQ PUCCH resource, there may be a priority rule to decide which
information can be transmitted on the resource. For example, PUCCH
 resource containing URLLC HARQ> PUCCH resource containing eMBB HARQ
> PUCCH resource containing SL HARQ > PUCCH resource containing SR >
PUCCH resource containing CSI part | > PUCCH resource containing CSI part
Il. In one approach, the priority of SL HARQ depends on the priority
information indicator (e.g., PPPP) in the scheduling SCI. It is noted that the
priority of PUCCH resource depends on the highest priority of UCI contained
in the PUCCH resource
In one approach, there is a threshold configured in RRC signaling for UCI of
eMBB (eMBB HARQ or eMBB SR or eMBB CSl). If the priority information
indicator in the scheduling SCI is less than the threshold (note: more
important), UE may drop UCI for eMBB.
In one approach, there is a threshold configured in RRC signaling for UCI of
URLLC (URLLC HARQ or URLLC SR or URLLC CSlI). If the priority information
indicator in the scheduling SCI is less than the threshold (note: more
important), UE may drop UCI for URLLC.

4 Solution elaboration
4.1 generate HARQ codebook for SL resource allocation 1

4.1.1 excluding PSSCH/PSCCH candidate

1 if at least one symbol of the PSSCH candidate time resource indicated by a SCl is
configured as DL/FL, the PSSCH candidate is excluded from PSSCH candidate lists.
For example, if RRC configures KO_2={0,1,2,3} and UE receives one SCl in slot n,
the PSSCH candidate are located on slot n+0, slot n+1, slot n+2, or slot n+3 (note:
n+KO_2_x). If one DL/FL symbol overlapped with the PSSCH candidates scheduled
by the SCI, UE may exclude those PSSCH candidates. The remaining PSSCH
candidates are denoted as valid PSSCH candidates.
if at least one symbol of the PSSCH candidate time resource indicated by a DCI_SL
is configured as DL/FL, the PSSCH candidate is excluded from PSSCH candidate
lists. For example, if RRC configures KO_SL={0,1,2,3} and UE receives one DCI_SL
in slot n, the PSSCH candidate are located on slot n+0, slot n+1, slot n+2, or slot

10
 n+3 (note: n+KO_SL_x). If one DL/FL symbol overlapped with the PSSCH
candidates scheduled by the DCI_SL, UE may exclude those PSSCH candidates.
The remaining PSSCH candidates are denoted as valid PSSCH candidates.
3 ifatleast one symbol of the PSCCH candidate time resource indicated by a DCI_SL
is configured as DL/FL, the PSCCH candidate is excluded from PSCCH candidate
lists. For example, if RRC configures KO_1={0,1,2,3}
and UE receives one DCI_SL in
slot n, the PSCCH candidate are located on slot n+0, slot n+1, slot n+2, or slot n+3
(note: n+K0_1_x). If one DL/FL symbol overlapped with the PSCCH candidates
scheduled by the DCI_SL, UE may exclude those PSCCH candidates. The remaining
PSSCH candidates are denoted as valid PSCCH candidates.

4.1.2 embodiment of generating HARQ codebook according to sl-DataToUL-ACK

and/or PSSCH time domain resource allocation

1 If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH resource or

PUSCH resource) and UE is configured to monitor a SCI on PSCCH 102 in slot n-
K1_PSCCH_x, UE may consider the PSSCHs scheduled by the SCI as PSSCHs
candidates according to all entries of PSSCH-TimeDomainResourceAllocationList-
SCl as shown in Figure 1. For example, in figure 1, if K1_PSCCH = {1, 2, 3, 4 slot(s)}
and KO_2 = {0,1,2 slot(s)} are configured in RRC signaling and UE is indicated to
transmit SLHARQ feedback on PUCCH resource 106 in slot #n according to DCI_SL
contained in the PDCCH 100, UE may check whether there are valid PSCCH
candidates on slot n-1, slot n-2, slot n-3, slot n-4 (note: n - K1_PSCCH_x). Then,
after excluding invalid PSCCH candidates, UE may further check valid PSSCH
candidates by assuming there are PSSCH transmitted on slot n-1+0, n-1+1,n-
1+2,..,n-4+2 (note: n- K1_PSCCH_x+KO_2_x). Afterwards, UE may generate SL
HARQ information for each PSSCH candidate.

slot #n
PSCOH 102 PUCCH 106

I
Ki_PACEH

Figure 1. example of embodiment 1 of 4.1.2

11
 In another approach, UE may consider the PSSCHs scheduled by the DCI_SL
as PSSCHs candidates according to all entries of PSSCH-
TimeDomainResourceAllocationList-DCI_SL as shown in Figure 2. For example, in
figure 2, if K1I_PSCCH ={1, 2, 3, 4 slot(s)} and KO_SL = {0,1,2 slot(s)} are configured
in RRC signaling and UE is indicated to transmit SL HARQ feedback on PUCCH
resource 206 in slot #n according to DCI_SL contained in the PDCCH 200 in slot
#n-6 and SCI contained in the PSCCH 202 in slot #n-2 (note: we assume UE only
receives SCI successfully on the PSCCH 202 in slot #n-2 and SCI indicates that UE
selects “4” from K1_PSCCH lists). UE may check valid PSSCH candidates by
assuming there are PSCCH transmitted on slot n-6+0, n-6+1, and n-6+2 (note: n-
6+K0_SL_x). Then, after excluding invalid PSSCH candidates, UE may generate SL
HARQ information for each PSSCH candidate.
siot #ta
slot#n-6 PSCCH 20T PUCCH 206

o PSSCHZ2OS
KO_SL K1_PSCCH

Figure 2. another approach of embodiment 1 of4.1.2

If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH resource or
PUSCH resource) and UE is configured to monitor PSSCH in slot n-K1_PSSCH_x,
UE may consider the PSSCHs scheduled by the SCI as PSSCHs candidates
according to all entries of PSSCH-TimeDomainResourceAllocationList-SCI as
shown in Figure 3. For example, in figure 3, if K1_PSSCH = {1, 2, 3, 4 slot(s)} and
KO_2 = {0,1,2 slot(s)} are configured in RRC signaling and UE is indicated to
transmit SL HARQ feedback on PUCCH resource 306 in slot #n according to SCI
contained in the PSCCH 302 and DCI_SL contained in the PDCCH 300, UE may
check whether there are valid PSSCH candidates on slot n-1, slot n-2, slot n-3, slot
n-4 (note: n - K1_PSSCH_x). Afterwards, UE may generate SL HARQ information
for each PSSCH candidate.

slot#n
PSCCH 302 PUCCH 306

PSSCH 304
5 e PO
Ko_1 KO 2 Ki_PSSTH

12
 Figure 3. example of embodiment 2 of 4.1.2
In another approach, UE may consider the PSSCHs scheduled by the DCI_SL
as PSSCHs candidates according to all entries of PSSCH-
TimeDomainResourceAllocationList-DCI_SL as shown in Figure 4. For example, in
figure 4, if K1I_PSSCH={1, 2, 3, 4 slot(s)}and KO_SL = {0,1,2 slot(s)} are configured
in RRC signaling and UE is indicated to transmit SL HARQ feedback on PUCCH
resource 406 in slot #n according to DCI_SL contained on the PDCCH 400 in slot
#n-6 and SCI contained on PSCCH 402 in slot#n-2 (note: we assume UE only
receives SCI successfully on the PSCCH 402 is in the same slot #n-2 as PSSCH and
SClindicates that UE selects “4” from K1_PSSCH lists). Then, UE may further check
valid PSSCH candidates by assuming there are PSSCH transmitted on slot n-6+0,
n-6+1, and n-6+2 (note: n-6+KO_SL_x). Afterwards, UE may generate SL HARQ
information for each PSSCH candidate.

siot #n1
slot#n-6 PSCCH 402 PUCCH 406

Ko_st T xalesscn
Figure 4. another approach of embodiment 2 of 4.1.2

If the UE is indicated to transmit HARQ feedback on slot n (by PUCCH resource or

PUSCH resource), UE is configured to monitor DCI_SL on PDCCH in slot n-K1_SL,
and the DCI_SL indicates a PSCCH which contains a SCI (note: in this solution,
DCI_SL only indicates one specific PSCCH resource location), then UE may
consider the PSSCHs scheduled by the SCI as PSSCHs candidates according to all
entries of PSSCH-TimeDomainResourceAllocationList-SCl as shown in Figure 5.
For example, in figure 5, if K1_SL={5, 6, 7, 8 slot(s)} and KO_2 ={0,1,2 slot(s)} are
configured in RRC signaling and UE is indicated to transmit SL HARQ feedback on
PUCCH resource 506 in slot #n according to DCI_SL contained in the PDCCH 500
in slot n-5, slot n-6, slot n-7 or slot n-8 (note: slot n-K1_SL_x), UE may also be
indicated to a SCI contained in PSCCH 502 in slot n-5+3, n-6+3, n-7+3, or n-8+3
(note: DCI_SL may contain an offset “3” which indicate the location of PSCCH in
slot n-K1_SL_x+3). Then, UE may check whether there are valid PSSCH candidates
on slot n-5+3+0, slot n-5+3+1, slot n-5+3+2,., n-8+3+2 (note: n-
K1_SL_x+3+K0_2_x). Afterwards, UE may generate SL HARQ information for each

13
PSSCH candidate.
slot #n
PUECH 506

Figure 5. example of embodiment 3 of 4.1.2

In another approach, UE may consider the PSSCHs scheduled by the DCI_SL

as PSSCHs candidates according to all entries of PSSCH-
TimeDomainResourceAllocationList-DCI_SL as shown in Figure 6. For example, in
figure 6, if K1_SL= {5, 6, 7, 8 slot(s)} and KO_SL = {0,1,2 slot(s)} are configured in
RRC signaling and UE is indicated to transmit SL HARQ feedback on PUCCH
resource 606 in slot #n according to DCI_SL contained in the PDCCH 600 in slot n-
5, slot n-6, slot n-7 or slot n-8 (note: slot n-K1_SL_x). Then, UE may further check
valid PSSCH candidates by assuming there are PSSCH transmitted on slot n-5+0,
n-5+1, ..., or n-8+2 (note: n-K1_SL_x+KO_SL_x). Afterwards, UE may generate SL
HARQ information for each PSSCH candidate.

K1_st slot #n
PSCCH 502 CCH 806

FOCCH 800
KoL

Figure 6. another approach of embodiment 3 of 4.1.2

If the UE is indicated to transmit HARQ feedback in slot n (by PUCCH resource or

PUSCH resource), UE is configured to monitor DCI_SL on PDCCH in slot n-K1_SL,
and the DCI_SL may indicate more than one PSCCH candidate which contains a
SCI in slot n-K1_SL+KO_1_x (note: in this solution, each entry in PSCCH-
TimeDomainResourceAllocationList-DCI_SL can indicate one PSCCH candidate),
then UE may consider the PSSCHs scheduled by the SCI as PSSCHs candidates
according to all entries of PSSCH-TimeDomainResourceAllocationList-SCI as
shown in Figure 7. For example, in figure 7, if K1_SL = {5, 6, 7, 8 slot(s)}, KO_1
={0,1,2 slot(s)} and KO_2 = {0, 1,2 slot(s)} are configured in RRC signaling and UE is

14
 indicated to transmit SL HARQ feedback on PUCCH resource 706 in slot #n
according to DCI_SL contained on the PDCCH 700 in slot n-5, slot n-6, slot n-7 or
slot n-8 (note: slot n-K1_SL_x), UE may also check whether there are valid PSCCH
candidates on slot n-5+3+0, slot n-5+3+1, slot n-5+3+2,..., n-8+3+2 (note: n-
K1_SL_x+3+K0_1_x) on PSCCH 702 in slot n-5+0, n-5+1, n-5+2,..., or n-8+2 (note:
slot n-K1_SL_x+KO_1_x). Then, after excluding invalid PSCCH candidates, UE may
check whether there are valid PSSCH candidates on slot n-5+0+0, slot n-5+0+1,
slot n-5+0+2,..., n-8+2+2 (note: n-K1_SL_x+KO_1_x+K0_2_x). Afterwards, UE may
generate SL HARQ information for each PSSCH candidate.

KI_SiL slot #n
PRCEHFO; UECH 708

PDCCH 700 psscH 704

K0_1 ko2
Figure 7. example of embodiment 4 of 4.1.2

embodiment of Configuration of SL HARQ codebook type

There is a new IE “SL-HARQ-ACK-Codebook” contained in RRC/SL-RRC/SIB/SIB-
SL/MIB-SL, which indicates SL HARQ-ACK codebook is either semi-static or
dynamic. It is noted that this IE may be configured per resource pool/per BWP/
per anchor carrier/ per cell/ per cell group/ per UE.
SLUHRRO ACK Cadehook :i=
Semiiatatic, dynamic, all, sparel
¥
| SL-HARQ-ACK-Codebook
Indicate SL HARQ codebook type.
: If not configured, the default value is “semi-static” or “dynamic”

SL HARQ codebook type may be the same as the HARQ codebook type of the
cell which containing scheduling information (i.e., DCI_SL).
For example, UE is configured to perform SL transmission on cell#0 and “pdsch-
HARQ-ACK-Codebook” of cell#0 indicates that HARQ codebook type on cell#0 is
“dynamic codebook”. Therefore, UE expects to generate dynamic HARQ
codebook, which means UE may expect that SCl or DCI_SL contains SL_DAI (i.e.,

15
 downlink assignment index for SL) for dynamic SL HARQ codebook.

4.3 embodiment of Multiplexing UCI and SL HARQ feedback

There is a new IE SL-PUCCHresource contained in RRC/SIB, which indicates PUCCH
resource dedicated for SL HARQ feedback. It is noted that SL-PUCCH resource may
not overlap with PUCCH resource for UCI in time/frequency domain. In one
approach, if there is no such IE in RRC/SIB, UE will consider SL HARQ feedback can
multiplex with UCI on PUCCH resource.
SHoPUCOHEcmotren oo o 1
SLipucthidesnnrceTd S1LPUCCH Resourcald,
StArninepRE PRE-Td,
AntrdslatFreqiencyBoppine ENOMERATED | anabied 1
SecandHopPRR PRECTA
format cHOTCE |
formarp BUCCH format,
formati PHCCH formati,
formats PUCCH format?,
fornat3 PUCOH- Eormat 3,
foxmard PUCCR-Foxmatd
3
iritdalevelicahice INTEGER(D..11),
nrofSymbols INTESER (1.0},
srartingsymbolTndex TNTEGER(D...13}

] SL-PUCCHresource
Indicate PUCCH resource dedicated for SL
UE is not expected that time/frequency domain resource of any SL-PUCCHresource overlap with
PUCCH-resource for UCI
i i not configured, UE will multiplex SL HARQ with UCI on PUCCH resource for UCI

There is a new IE SL-UCI-MUX (note: T/F indicator) contained in RRC/SIB, which

indicates whether UE can perform UCI and SL HARQ multiplexing or not. In one
approach, if there is no such IE in RRC/SIB, UE will considerSL HARQ feedback can
multiplex with UCI on PUCCH resource. In another approach, if there is no such
IE in RRC/SIB, UE will consider SL HARQ feedback cannot multiplex with UCI on
PUCCH resource.

16
BLIUCT MUK oo
Trie
3
or
OET MUK i Boolean
SL-UCI-MUX
Indicate whether UE can perform UCI and SL HARQ multiplexing or not
fig d, the UE multipl SL HARQ with UCIby defaul

3 Thereis a new IE SL-onPUSCH (note: T/F indicator) contained in RRC/SIB, which

indicates whether UE can perform transmit SL HARQ on PUSCH or not (note:
when PUCCH resource contains SL HARQ overlaps with PUSCH). In one approach,
if there is no such IE in RRC/SIB, UE will consider SL HARQ feedback can transmit
on PUSCH. In another approach, if there is no such IE in RRC/SIB, UE will consider
SL HARQ feedback cannot transmit on PUSCH.
S lonPUSEH fom i
Tilie
’
or
Bianpuscs s Boalean

SL-onPUSCH
Indicate whether UE can transmit SL HARQ on PUSCH or not
{ If not configured, the UE cannot transmit SL HARQ on PUSCH

It is noted that if UE does not support SL HARQ on PUSCH, UE may transmit

PUSCH and drop SL HARQ when the PUCCH resource of SL HARQ overlaps with
PUSCH. For example, if UE is indicated to transmit SL HARQon slot n+8 by DCI_SL
on slot n and UE is indicated to transmit PUSCH on slot n+8 by DCI 0_1 on slot
n+4, UE may drop SL HARQ but only transmit PUSCH on slot n+8 when SL-
onPUSCH is “False”.
4 There is a new IE for-SL-HARQ (note: T/F indicator) contained in PUCCH
resource/PUCCH resource set configuration in RRC/SIB. The PUCCH
resource/PUCCH resources contained in PUCCH resource set may contain SL
HARQ feedback if the for-SL-HARQ indicates “T".
PUBCH resouice fxe i
putch-Resourcerd PUCCH-Resourcard,
UiarllngrRa BRE-Td,

17
intraSlotFraaicncyiopplng ENOMERATED { enabled |}
BecondHopPRE PRE 1d
format CHOTCE {
farmato PUCCH: formatD,
Farmatl BUCOH format1,
Formar PUCOH: formet2,
Eoxmard BUCCH- Format 3,
formatd BUCCH- formatd
1
BUCGEH format-x iis SEOURNCT/
ShiEaICudlicBnitE INTEGER (% 0. x ),
prafsvnbels TNTEGER (v 0 v,
Btartingsinbol Todex TNTESER(L G. o2 ny
3
For-BromeRD

For BL HARD | Boplesn

¥

for-SL-HARQ
Indicate this PUCCH can transmit SL HARQ on PUSCH or not
It not configured, the UE cannot transmit SL HARQ on the PUCCH

5 (for SL HARQ and UCI multiplexing case) if the payload size of PUCCH resource
cannot contain all SL HARQ and UCI bits, there may be a priority rule to decide
which information can be transmitted on the PUCCH resource. For example,
URLLC HARQ> eMBB HARQ > SL HARQ > SR > CSl part | > CSl part Il
For example, UE is indicated to transmit SL HARQ feedback on PUCCH resource
#3 and UE is also indicated to transmit Uu HARQ feedback and CSI feedback on
PUCCH resource #3. If O_SL_ACK (i.e., number of SL HARQ bits) + O_ACK (i.e.,
number of Uu HARQ feedback bits)+ O_CSI (i.e., number of CS| feedback) + O_CRC
(i.e., total bits of CRC for SL HARQ, Uu HARQ and CSI feedback) is larger than
payload size of PUCCH resource #3 (note: payload size of PUCCH resource may be
related to number of PRB, number of symbols, modulation and/or code rate), the
UE may drop CSI feedback first and then SL HARQ until O_SL_ACK + O_ACK +
O_CSI + O_CRC is smaller than payload size of PUCCH resource #3
In one approach, the priority of SLHARQ depends on the priority information

18
 indicator (e.g., PPPP) in the scheduling SCI. For example, UE is configured with a
threshold (e.g., “3”) for dropping eMBB UCI, and if PPPP in a SCl or a DCI_SL is “2”,
UE may drop eMBB UCI if the PUCCH resource of the eMBB UCI overlapped with
SL HARQ feedback of the PSSCH scheduled by the SCI or the DCI_SL.
6 (forcase that SLHARQ and UCl are independently reported) if the time/frequency
domain of SL HARQ PUCCH resource overlaps with UCI HARQ PUCCH resource,
there may be a priority rule to decide which information can be transmitted on
the resource. For example, PUCCH resource containing URLLC HARQ> PUCCH
resource containing eMBB HARQ, > PUCCH resource containing SL HARQ > PUCCH
resource containing SR > PUCCH resource containing CSI part | > PUCCH resource
containing CSI partIl.
For example, UE is indicated to transmit SL HARQ feedback on SL-PUCCH resource
#3in 10" and 11*" symbols of slot n and UE is also indicated to transmit Uu HARQ,
feedback and CSI feedback on PUCCH resource #2 in 9™ and 10 symbols of slot
n. Since SL-PUCCH resource #3 and PUCCH resource #2 are (partially) overlapped,
UE may drop SL HARQ and SL-PUCCH resource #3 but only transmit PUCCH
resource #2 for Uu HARQ feedback on slot n.
In one approach, the priority of SL HARQ depends on the priority information
indicator (e.g., PPPP) in the scheduling SCI. It is noted that the priority of PUCCH
resource is depended on the highest priority of UCI contained in the PUCCH
resource. For example, UE is configured with a threshold (e.g., “1”) for dropping
URLLC UCI, and if PPPP in a SCl or a DCI_SL is “2”, UE may drop URLLC UCI if the
PUCCH resource of the URLLC UCI overlapped with SL HARQ feedback of the
PSSCH scheduled by the SCI or the DCI_SL.

5. Tentative Claims

In this material, we propose methods for dealing with SL HARQ feedback for

resource allocation mode 1. The methods may be featured with:

- generating SL HARQ codebook according to new parameter KO_1, KO_2,

KO_SL, K1_SL, K1_PSCCH, and/or K1_PSSCH

Defining a priority rule when PUCCH resource of SL HARQ and UCI overlap.

determining HARQ codebook type for SL HARQ

19
 Appendices
The description in this application contains specific information pertaining to

exemplary implementations in the present disclosure. The drawings in the present

disclosure and their accompanying detailed description are directed to merely

exemplary implementations. However, the present disclosure is not limited to merely

these exemplary implementations. Other variations and implementations of the

present disclosure will occur to those skilled in the art. Unless noted otherwise, like

or corresponding elements among the figures may be indicated by like or corresponding

reference numerals. Moreover, the drawings and illustrations in the present disclosure

are generally not to scale and are not intended to correspond to actual relative

dimensions.

EA - Appendix: Description on selected terms

close-loop power control: UE adjusts TX power according to the dynamic

indication received from BS.

Z, ~ Appendix: Instructions to read this

application
For the purpose of consistency and ease of understanding, like features are

identified (although, in some examples, not shown) by numerals in the example figures.

However, the features in different implementations may be differed in other respects,

and thus shall not be narrowly confined to what is shown in the figures.

References to “one implementation,” “an implementation,” “example

implementation,” “various implementations,” “some implementations,”

“implementations of the present application,” etc., may indicate that the

implementation(s) of the present application so described may include a particular

feature, structure, or characteristic, but not every possible implementation of the

present application necessarily includes the particular feature, structure, or

characteristic. Further, repeated use of the phrase “in one implementation,” or “in an

example implementation,” “an implementation,” do not necessarily refer to the same

implementation, although they may. Moreover, any use of phrases like

“implementations” in connection with “the present application” are never meant to

characterize that all implementations of the present application must include the

particular feature, structure, or characteristic, and should instead be understood to

mean “at least some implementations of the present application” includes the stated

particular feature, structure, or characteristic. The term “coupled” is defined as

connected, whether directly or indirectly through intervening components, and is not

necessarily limited to physical connections. The term “comprising,” when utilized,

means “including, but not necessarily limited to”; it specifically indicates open-ended

inclusion or membership In the so-described combination, group, series and the

equivalent.

Additionally, for the purposes of explanation and non-limitation, specific details,

such as functional entities, techniques, protocols, standard, and the like are set forth

for providing an understanding of the described technology. In other examples,

detailed description of well-known methods, technologies, system, architectures, and

the like are omitted so as not to obscure the description with unnecessary details.

Persons skilled in the art will immediately recognize that any network function(s)

or algorithm(s) described in the present disclosure may be implemented by hardware,

software or a combination of software and hardware. Described functions may

correspond to modules may be software, hardware, firmware, or any combination

thereof. The software implementation may comprise computer executable

instructions stored on computer readable medium such as memory or other type of

storage devices. For example, one or more microprocessors or general purpose

21
computers with communication processing capability may be programmed with

corresponding executable instructions and carry out the described network function(s)

or algorithm(s). The microprocessors or general purpose computers may be formed of

Applications Specific Integrated Circuitry (ASIC), programmable logic arrays, and/or

using one or more Digital Signal Processor (DSPs). Although some of the example

implementations described in this specification are oriented to software installed and

executing on computer hardware, nevertheless, alternative example implementations

implemented as firmware or as hardware or combination of hardware and software

are well within the scope of the present disclosure.

The computer readable medium includes but is not limited to Random Access

Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read-Only

Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM),

flash memory, Compact Disc Read Only Memory (CD ROM), magnetic cassettes,

magnetic tape, magnetic disk storage, or any other equivalent medium capable of

storing computer-readable instructions.

A radio communication network architecture (e.g., a Long Term Evolution (LTE)

system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system) typically

includes at least one base station, at least one User Equipment (UE), and one or more

optional network elements that provide connection towards a network. The UE

communicates with the network (e.g., a Core Network (CN), an Evolved Packet Core

(EPC) network, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a

Next-Generation Core (NGC), or an internet) through a Radio Access Network (RAN)

established by the base station.

It should be noted that, in the present application, a UE may include, but is not

limited to, a mobile station, a mobile terminal or device, a user communication radio

terminal, etc. For example, a UE may be a portable radio equipment, which includes,

but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, or a

Personal Digital Assistant (PDA) with wireless communication capability. The UE is

22
configured to receive/transmit signals over an air interface from/to one or more cells

in a radio access network.

A base station may include, but is not limited to, a Node B (NB) as in the UMTS, an

evolved Node B (eNB) as in the LTE-A, a Radio Network Controller (RNC) as in the UMTS,

a Base Station Controller (BSC) as in the GSM/GERAN, an NG-eNB as in an E-UTRA base

station in connection with the 5GC, a next generation Node B (gNB) as in the 5G-AN,

and any other apparatus capable of controlling radio communication and managing

radio resources within a cell. The base station may connect to serve the one or more

UEs through a radio interface to the network.

A base station may be configured to provide communication services according to

at least one of the following Radio Access Technologies (RATs): Worldwide

Interoperability for Microwave Access (WiMAX), Global System for Mobile

communications (GSM, often referred to as 2G), GSM EDGE radio access Network

(GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication

System (UMTS, often referred to as 3G) based on basic Wideband-Code Division

Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, elTE

(evolved LTE), New Radio (NR, often referred to as 5G), and/or LTE-A Pro. However, the

scope of the present application should not be limited to the above mentioned

protocols.

The base station is operable to provide radio coverage to a specific geographical

area using a plurality of cells forming the radio access network. The base station

supports the operations of the cells. Each cell is operable to provide services to at least

one UE within its radio coverage. More specifically, each cell (often referred to as a

serving cell) provides services to serve one or more UEs within its radio coverage, (e.g.,

each cell schedules the downlink and optionally uplink resources to at least one UE

within its radio coverage for downlink and optionally uplink packet transmissions). The

base station can communicate with one or more UEs in the radio communication
system through the plurality of cells. A cell may allocate Sidelink (SL) resources for

23
supporting Proximity Service (ProSe). Each cell may have overlapped coverage areas

with other cells.

As discussed above, the frame structure for NRis to supportflexible configurations

for accommodating various next generation (e.g., 5G) communication requirements,

such as enhanced Mobile BroadBand (eMBB), massive Machine Type Communication

(mMTC), Ultra-Reliable communication and Low Latency Communication (URLLC),

while fulfilling high reliability, high data rate and low latency requirements. The

Orthogonal Frequency-Division Multiplexing (OFDM) technology as agreed in 3GPP

may serve as a baseline for NR waveform. The scalable OFDM numerology, such as the

adaptive sub-carrier spacing, the channel bandwidth, and the Cyclic Prefix (CP), may

also be used. Additionally, two coding schemes are considered for NR: (1) Low-Density

Parity-Check (LDPC) code and (2) polar code. The coding scheme adaption may be

configured based on the channel conditions and/or the service applications.

Moreover, it should be noted that in a transmission time interval TX of a single NR

frame, at least DownLink (DL) transmission data, a guard period, and UpLink (UL)

transmission data should be included. Additionally, the respective portions of the DL

transmission data, the guard period, and the UL transmission data should also be

configurable, for example, based on the network dynamics of NR. In addition, SL

resource may also be provided in an NR frame to support ProSe services.

In addition, the terms “system” and “network” herein may be used

interchangeably. The term “and/or” herein is only an association relationship for

describing associated objects, and represents that three relationships may exist. For

example, A and/or B may indicate that: A exists alone, A and B exist at the same time,

and B exists alone. In addition, the character “/” herein generally represents that the

former and latter associated objects are in an “or” relationship.

 A - Appendix: hardware example applicable in

this application
Fig. KKK illustrates a block diagram of a node for wireless communication, in

accordance with various aspects of the present application. As shown in Fig. KKK, a

node KKKOO may include a transceiver KKK20, a processor KKK28, a memory KKK34,

one or more presentation components KKK38, and at least one antenna KKK36. The

node KKKOO may also include an RF spectrum band module, a base station

communications module, a network communications module, and a system

communications management module, Input/Output (I/O) ports, 1/O components,

and power supply (not explicitly shown in FIG. KKK). Each of these components may

be in communication with each other, directly or indirectly, over one or more buses

KKK40. In one implementation, the node KKKOO may be a UE or a base station that

performs various functions described herein, for example, with reference to Figs. 1

through KKK-1.

The transceiver KKK20 having a transmitter KKK22 (e.g., transmitting/transmission

circuitry) and a receiver KKK24 (e.g., receiving/reception circuitry) may be configured

to transmit and/or receive time and/or frequency resource partitioning information.

In some implementations, the transceiver KKK20 may be configured to transmit in

different types of subframes and slots including, but not limited to, usable, non-usable

and flexibly usable subframes and slot formats. The transceiver KKK20 may be

configured to receive data and control channels.

The node KKKOO may include a variety of computer-readable media. Computer-

readable media can be any available media that can be accessed by the node KKKOO

and include both volatile and non-volatile media, removable and non-removable

media. By way of example, and not limitation, computer-readable media may comprise

computer storage media and communication media. Computer storage media

includes both volatile and non-volatile, removable and non-removable media

25
implemented in any method or technology for storage of information such as

computer-readable.

Computer storage media includes RAM, ROM, EEPROM, flash memory or other

memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk

storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic

storage devices. Computer storage media does not comprise a propagated data signal.

Communication media typically embodies computer-readable instructions, data

structures, program modules or other data in a modulated data signal such as a carrier

wave or other transport mechanism and includes any information delivery media. The

term “modulated data signal” means a signal that has one or more of its characteristics

set or changed in such a manner as to encode information in the signal. By way of

example, and not limitation, communication media includes wired media such as a

wired network or direct-wired connection, and wireless media such as acoustic, RF,

infrared and other wireless media. Combinations of any of the above should also be

included within the scope of computer-readable media.

The memory KKK34 may include computer-storage media in the form of volatile

and/or non-volatile memory. The memory KKK34 may be removable, non-removable,

or a combination thereof. Exemplary memory includes solid-state memory, hard drives,

optical-disc drives, and etc. As illustrated in Fig. KKK, The memory KKK34 may store

computer-readable, computer-executable instructions KKK32 (e.g., software codes)

that are configured to, when executed, cause the processor KKK28 to perform various

functions described herein, for example, with reference to Figs. 1 through KKK-1.

Alternatively, the instructions KKK32 may not be directly executable by the processor

KKK28 but be configured to cause the node KKKOO (e.g., when compiled and executed)

to perform various functions described herein.

The processor KKK28 (e.g., having processing circuitry) may include an intelligent

hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, and

etc. The processor KKK28 may include memory. The processor KKK28 may process

26
the data KKK30 and the instructions KKK32 received from the memory KKK34, and

information through the transceiver KKK20, the base band communications module,

and/or the network communications module. The processor KKK28 may also process

information to be sent to the transceiver KKK20 for transmission through the antenna

KKK36, to the network communications module for transmission to a core network.

One or more presentation components KKK38 presents data indications to a

person or other device. Exemplary presentation components KKK38 include a display

device, speaker, printing component, vibrating component, and etc.

From the above description, it is manifested that various techniques may be used

for implementing the concepts described in the present application without departing

from the scope of those concepts. Moreover, while the concepts have been

described with specific reference to certain implementations, a person of ordinary skill

in the art would recognize that changes may be made in form and detail without

departing from the scope of those concepts. As such, the described implementations

are to be considered In all respects as illustrative and not restrictive. It should also

be understood that the present application is not limited to the particular

implementations described above, but many rearrangements, modifications, and

substitutions are possible without departing from the scope of the present disclosure.
 KKKO00 KKK36

Memory KKK40

KKK34
Transceiver
Data KKK20
KKK30 Transmitter
KKK22
Instructions Receiver
KKK32 KKK24

Processor

Presentation
Components -
KKK38 T nstructions |
- =
KKK32

Fig. KKK
 =

=
WORLD
INTELLEGTUAL PROPERTY
ORGANIZATION

DOCUMENT MADE AVAILABLE UNDER THE

PATENT COOPERATION TREATY (PCT)
International application number: PCT/CN2020/109132

International filing date: 14 August 2020 (14.08.2020)

Document type: Certified copy of priority document

Document details: Country/Office: us

Number. 62/888,051
Filing date: 16 August 2019 (16.08.2019)

Date of receipt at the International Bureau: 04 September 2020 (04.09.2020)

Remark: Priority document submitted or transmitted to the International Bureau in compliance with Rule
17.1(a),(b) or (b-bis)

24, chemin des Colombettes

1211 Geneva 20, Switzerl and
www.wipo.int