DETAILED ACTION
This is in response to Applicant’s reply dated 6/26/26. Claims 29, 31, 34-36, 38-42, 44, 46, and 48 have been examined. Claims 1-28, 30, 32-33, 37, 43, 45, and 47 have been cancelled.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 29-48 are rejected under 35 U.S.C. 102(a)(1) as being unpatentable by Ganesan et al. (WO 2021/140494; included in IDS; hereafter Ganesan).
Regarding Claim 29 (Currently Amended),
A method, performed by a first user equipment (UE), of handling communication over a sidelink (SL) in a wireless communication network, the method comprising:
receiving a request message, from a second UE, carrying a respective identifier for multiple SL carriers for which channel state information (CSI) are requested [Ganesan: respective identifier for multiple SL carriers == unicast link ID(s); 0068; the TX UE 201 sends a SL-CSI request 215 to the RX UE 205; 0097; RAN node 210 may indicate in the DCI to request SL- CSI report(s) from TX UE 201; in one embodiment, the SL-CSI request in the DCI may also include unicast link ID(s) or destination ID(s) and - in that case - the TX UE 201 is only allowed to transmit/multiplex SL-CSI values for the specified unicast link ID(s) or destination ID(s); 0099; when TX UE 201 receives SL CSI-RS request from RAN node 210, it may start transmitting SL CSI-RS corresponding to one or more unicast links or destination IDs for SL LCHs with Mode- 1 configurations and request SL-CSI values accordingly];
obtaining quality information of multiple SL carriers [Ganesan: 0068; the RX UE 205 responds by sending a SL-CSI value 220 to the TX UE 201; here, the SL- CSI value 220 is based on the physical layer measurements from RX UE 205 to TX UE 201; 0092; the TX UE 201 may reduce the overhead of CSI reporting to the RAN node 210 including identifying and combining/merging CSI reports from multiple unicast links belonging to the same TX-RX UE pairs; 0087; figure 4B depicts one embodiment of the first field 405; the first field 405 may begin with a SL link ID presence/absence flag 420 (e.g., 1-bit flag) where, for example, the value ‘G indicates the presence of SL link ID; the presence bit/flag 420 is followed by first SL link ID (or destination ID) sub-field 425 and then followed by first SL BWP ID or SL carrier ID sub-field 430, and then followed by first SL CQI 435 and first SL RI 440 values; 0088; figure 4C depicts one embodiment of the second field 410; as depicted, the second field 410 may begin with a SL link ID presence/absence flag 445 (e.g., 1-bit flag) and is followed by second SL link ID (or destination ID) sub-field 450 and then followed by second SL BWP ID or SL carrier ID sub-field 455, and then followed by second SL CQI 460 and second SL RI 465 values];
selecting a SL carrier to transmit a CSI reporting medium access control (MAC) control element (CE) on [Ganesan: 0162; the identifier comprises a link ID that uniquely denotes a source-destination pair between the TX UE and the RX UE; in some embodiments, generating the SL-CSI report comprises multiplexing a plurality of SL-CSI values from multiple carriers and/or bandwidth parts and from multiple panels and/or beams for the same source-destination pair; in some embodiments, the MAC CE further includes an additional field to report one or more of: a SL-CSI measurement configuration, a SL BWP ID, a SL carrier ID, a SL logical panel ID, and a SL Slot number];
Note:
A SL carrier ID means a selected SL carrier.
transmitting, to a second UE, the CSI reporting MAC CE comprising: a quality indication of a respective SL carrier of two or more configured SL carriers of the multiple SL carriers [Ganesan: 0092; the TX UE 201 may reduce the overhead of CSI reporting to the RAN node 210 including identifying and combining/merging CSI reports from multiple unicast links belonging to the same TX-RX UE pairs; 0161; in some embodiments, generating the SL-CSI report comprises multiplexing a plurality of SL-CSI values from the plurality of unicast links, each SL-CSI value being tagged with a different identifier; 0068; the RX UE 205 responds by sending a SL-CSI value 220 to the TX UE 201; here, the SL- CSI value 220 is based on the physical layer measurements from RX UE 205 to TX UE 201; 0069; regarding the SL CSI reporting 230, a MAC CE may be used to carry a SL-CSI report; 0086; figure 4A depicts the MAC CE 400 containing a plurality of SL fields, including a first field 405, a second field 410, and a third field 415; here, the first field 405 provides information for a first SL Link and the second field 410 provides information for a second SL Link]; and
a respective identifier of the two or more configured SL carriers of which the respective quality indication is included in the CSI reporting MAC CE [Ganesan: 0092; the TX UE 201 may reduce the overhead of CSI reporting to the RAN node 210 including identifying and combining/merging CSI reports from multiple unicast links belonging to the same TX-RX UE pairs; in one example, along with the merged CSI values the TX UE may transmit individual unicast link ID that contains the same CSI values in the MAC CE 400; 0162; In some embodiments, generating the SL-CSI report comprises multiplexing a plurality of SL-CSI values from multiple carriers and/or bandwidth parts and from multiple panels and/or beams for the same source-destination pair; 0087; figure 4B depicts one embodiment of the first field 405; the first field 405 may begin with a SL link ID presence/absence flag 420 (e.g., 1-bit flag) where, for example, the value ‘G indicates the presence of SL link ID; the presence bit/flag 420 is followed by first SL link ID (or destination ID) sub-field 425 and then followed by first SL BWP ID or SL carrier ID sub-field 430, and then followed by first SL CQI 435 and first SL RI 440 values; 0088; figure 4C depicts one embodiment of the second field 410; as depicted, the second field 410 may begin with a SL link ID presence/absence flag 445 (e.g., 1-bit flag) and is followed by second SL link ID (or destination ID) sub-field 450 and then followed by second SL BWP ID or SL carrier ID sub-field 455, and then followed by second SL CQI 460 and second SL RI 465 values].
Regarding Claim 31 (Currently Amended),
further comprising obtaining a latency bound of the requested one or more indications [Ganesan: 0085; in various embodiments, priority of SL LCH(s) and/or minimum latency bound for the SL-CSI reporting from RX UE(s) may also be used as a selection criterion if there are limited resources].
Regarding Claim 34 (Previously Presented),
wherein the respective identifier is: carried via one or more existing reserved bits; and/or carried in a new field for indicating the identifier of the SL carrier; and/or indicated using one or more fields in a medium access control (MAC) subheader for a MAC control element (CE) [Ganesan: 0087; figure 4B depicts one embodiment of the first field 405; the first field 405 may begin with a SL link ID presence/absence flag 420 (e.g., 1-bit flag) where, for example, the value ‘G indicates the presence of SL link ID; the presence bit/flag 420 is followed by first SL link ID (or destination ID) sub-field 425 and then followed by first SL BWP ID or SL carrier ID sub-field 430, and then followed by first SL CQI 435 and first SL RI 440 values; 0088; figure 4C depicts one embodiment of the second field 410; as depicted, the second field 410 may begin with a SL link ID presence/absence flag 445 (e.g., 1-bit flag) and is followed by second SL link ID (or destination ID) sub-field 450 and then followed by second SL BWP ID or SL carrier ID sub-field 455, and then followed by second SL CQI 460 and second SL RI 465 values].
Regarding Claim 35 (Previously Presented),
wherein: the message comprises a bitmap field containing multiple bits in a MAC CE; and a bit in the bitmap represents a specific SL carrier [Ganesan: 0087; figure 4B depicts one embodiment of the first field 405; the first field 405 may begin with a SL link ID presence/absence flag 420 (e.g., 1-bit flag) where, for example, the value ‘G indicates the presence of SL link ID; the presence bit/flag 420 is followed by first SL link ID (or destination ID) sub-field 425 and then followed by first SL BWP ID or SL carrier ID sub-field 430, and then followed by first SL CQI 435 and first SL RI 440 values; 0088; figure 4C depicts one embodiment of the second field 410; as depicted, the second field 410 may begin with a SL link ID presence/absence flag 445 (e.g., 1-bit flag) and is followed by second SL link ID (or destination ID) sub-field 450 and then followed by second SL BWP ID or SL carrier ID sub-field 455, and then followed by second SL CQI 460 and second SL RI 465 values].
Regarding Claims 36, 38-41, which recite the same claim limitations as those in claims 29, 31, and 34-35; the same rationale of rejection as presented in claims 29, 31, and 34-35 is applicable.
Regarding Claims 42 and 44, which recite the same claim limitations as those in claims 29 and 31, the same rationale of rejection as presented in claims 29 and 31 is applicable.
Regarding Claims 46 and 48, which recite the same claim limitations as those in claims 29 and 31, the same rationale of rejection as presented in claims 29 and 31 is applicable.
Response to Arguments
Applicant's arguments filed 6/26/26 have been fully considered but they are not persuasive.
Applicant argues regarding claims 29 and 42 on pages 7-8 of the Remarks section that Ganesan does not teach that the request message received by the RX UE carries a respective identifier for multiple SL carriers, rather only a single SL-CSI value. There is no selection of a SL carrier on which to transmit the SL-CSI value.
Examiner’s Response:
For purposes of brevity, please see the rejection above. See Ganesan [para. 92; 161-162].
Applicant argues regarding claims 29 and 42 on page 8 of the Remarks section that Ganesan fails to teach “the RX UE transmitting … a CSI reporting MAC CE including a quality indication of … two or more configured SL carriers of the multiple carriers … a respective identifier of the two or more configured SL carriers of which the respective quality indication is included in the CSI reporting MAC CE.”
Examiner’s Response:
For purposes of brevity, please see the rejection above. See Ganesan [para. 92; 161-162].
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SAAD A WAQAS whose telephone number is (571)270-5642. The examiner can normally be reached 8:30 - 5:00 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Marcus Smith can be reached at (571) 270-1096. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
SAAD A. WAQAS
Primary Examiner
Art Unit 2468
/Saad A. Waqas/Primary Examiner, Art Unit 2468
Prosecution Insights