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 .
Response to Arguments
Applicant's arguments filed May 19, 2026 have been fully considered but they are not persuasive.
Applicant asserts that the claims are patentable because the combination of Yoshioka, Pelletier, and Panteleev allegedly does not teach “feedback information to the network device on a third resource based on either a comparison of a priority of the sidelink HARQ with the a first threshold when it is determined to multiplex the sidelink HARQ and the downlink HARQ, or on a comparison of the priority of the sidelink HARQ with the second threshold when it is determined to drop either the sidelink HARQ or downlink HARQ, wherein the feedback information comprises the multiplexed sidelink HARQ and downlink HARQ if the first threshold is used, or the sidelink HARQ or the downlink HARQ if the second threshold is used,” as recited in independent claim 21. However, the examiner respectfully disagrees with applicant’s assertion. Yoshioka discloses feedback information to the network device on a third resource based on either a comparison of a priority of the sidelink HARQ with the a first threshold when it is determined to multiplex the sidelink HARQ and the downlink HARQ, or on a comparison of the priority of the sidelink HARQ with the second threshold when it is determined to drop either the sidelink HARQ or downlink HARQ, wherein the feedback information comprises the multiplexed sidelink HARQ and downlink HARQ if the first threshold is used, or the sidelink HARQ or the downlink HARQ if the second threshold is used (Yoshioka, paragraph [0036], same slot is indicated for feeding back an SL HARQ-ACK and a Uu HARQ-ACK; collision between PUCCH including SL HARQ-ACK and PUCCH including another type of UCI; paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities).
Applicant argues that Yoshioka does not teach “a comparison of a priority of the sidelink HARQ with the a first threshold when it is determined to multiplex the sidelink HARQ and the downlink HARQ,” as recited in claim 21, because “Yoshioka teaches that, when there is a conflict inasmuch as two competing HARQs are scheduled to the same time slot, the conflict may be resolved by dropping or postponing the SL HARQ-ACK. Alternatively, rather than employ a priority level, the SL-HARQ-ACK and Uu- HARQ-ACK may be multiplexed.” Applicant appears to be arguing that Yoshioka’s multiplexing of SL-HARQ-ACK and Uu-HARQ-ACK are not based on a priority level. However, the examiner respectfully disagrees with applicant’s arguments. Yoshioka discloses, for example in paragraph [0077], that SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities. Accordingly, Yoshioka discloses that all of multiplexing, dropping, and postponing [which is, itself, time multiplexing] are all based on priorities.
Applicant further argues that Yoshioka is wholly silent on determining whether to drop a HARQ or multiplex conflicting HARQs, let alone using different thresholds for comparison of sidelink HARQ priority based on whether it is determined to multiplex conflicting HARQs or to drop one of them, and therefore, Yoshioka fails to disclose ”sending feedback information to a network device based on either a comparison of a priority of the sidelink HARQ with a first threshold when it is determined to multiplex the sidelink HARQ and a downlink HARQ, or on a comparison of the priority of the sidelink HARQ with the second threshold when it is determined to drop either the sidelink HARQ or downlink HARQ, where the feedback information is either the multiplexed HARQs if the first threshold is used, or either the sidelink or downlink HARQ [while dropping the other] if the second threshold is used,” as recited in claim 21. However, the examiner respectfully disagrees with applicant’s arguments. Yoshioka discloses, for example in paragraph [0077], that SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities. Accordingly, Yoshioka discloses that multiplexing and dropping are both based on priorities. Further, Yoshioka discloses, in paragraph [0073], that dropping or postponing may be based on being unicast or groupcast, and that unicast has higher priority and groupcast has lower priority. Pelletier further discloses, in paragraph [0045], that Uu traffic may have different priorities based on being unicast vs. groupcast vs. broadcast. Accordingly, in the combination including Yoshioka and Pelletier, priority decisions when dropping or postponing [time multiplexing] downlink data may be based on two different [unicast or groupcast] thresholds.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claim(s) 21-22, 25-27, 30-32, 35-37 and 40-48 under 35 U.S.C. 103 as being unpatentable over Yoshioka et al. (US 2022/0321278) in view of Pelletier et al. (US 2017/0031565), and further in view of Panteleev et al. (US 2021/0243796).
Regarding claim 21, Yoshioka discloses a method, comprising:
obtaining, by a first terminal device, a first resource used to transmit a sidelink hybrid automatic repeat request (HARQ) and a second resource used to transmit a downlink HARQ device (Yoshioka, Fig. 3; paragraph [0007], in sidelink transmission mode 1, user apparatus 20A transmits HARQ-ACK to base station apparatus 10 on a PUCCH; paragraph [0009], HARQ-ACKs in direct communication between terminals scheduled by a base station; paragraph [0032], based on SL scheduling determined by the base station, HARQ-ACK is fed back from the user apparatus 20A to the base station apparatus 10; paragraph [0034]; paragraph [0036], SL HARQ-ACK on the sidelink between the user apparatus 20A and the user apparatus 20B and Uu HARQ-ACK between the user apparatus 20A and the base station apparatus; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot), and a determination of whether to multiplex the sidelink HARQ and downlink HARQ or to drop either the sidelink HARQ or downlink HARQ (Yoshioka, paragraph [0036], same slot is indicated for feeding back an SL HARQ-ACK and a Uu HARQ-ACK; collision between PUCCH including SL HARQ-ACK and PUCCH including another type of UCI; paragraph [0071], how to multiplex an SL HARQ-ACK and a Uu HARQ-ACK; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot; drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0074], it is also possible to consider multiplexing an SL HARQ-ACK and a Uu HARQ-ACK; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities),
wherein the sidelink HARQ corresponds to sidelink data sent by the first terminal device, and the downlink HARQ corresponds to downlink data that is received by the first terminal device from a network device (Yoshioka, Fig. 3; paragraph [0007], in sidelink transmission mode 1, user apparatus 20A transmits HARQ-ACK to base station apparatus 10 on a PUCCH; paragraph [0009], HARQ-ACKs in direct communication between terminals scheduled by a base station; paragraph [0032], based on SL scheduling determined by the base station, HARQ-ACK is fed back from the user apparatus 20A to the base station apparatus 10; paragraph [0034]; paragraph [0036], SL HARQ-ACK on the sidelink between the user apparatus 20A and the user apparatus 20B and Uu HARQ-ACK between the user apparatus 20A and the base station apparatus; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot);
determining, by the first terminal device, at least one threshold set from a plurality of thresholds based on a service type of the downlink data, wherein the at least one threshold set from the plurality of thresholds correspond to one service type of the data, different thresholds correspond to different service types of the downlink data, the at least one threshold set may be preconfigured or predefined, wherein the at least one threshold set includes a first threshold and a second threshold, and the at least one threshold set is used to represent a priority of downlink data of one service type (Yoshioka, paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on [priorities] corresponding to scheduling earlier than the latest; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities; paragraph [0078], Uu eMBB-HARQ-ACK, Uu URLLC-HARQ-ACK); and
sending, by the first terminal device when the first resource and the second resource overlap in time domain, feedback information to the network device on a third resource based on either a comparison of a priority of the sidelink HARQ with the a first threshold when it is determined to multiplex the sidelink HARQ and the downlink HARQ, or on a comparison of the priority of the sidelink HARQ with the second threshold when it is determined to drop either the sidelink HARQ or downlink HARQ, wherein the feedback information comprises the multiplexed sidelink HARQ and downlink HARQ if the first threshold is used, or the sidelink HARQ or the downlink HARQ if the second threshold is used, the third resource is determined based on the first resource and the second resource, and wherein the third resource is the first resource, the second resource, or a different resource (Yoshioka, paragraph [0036], same slot is indicated for feeding back an SL HARQ-ACK and a Uu HARQ-ACK; collision between PUCCH including SL HARQ-ACK and PUCCH including another type of UCI; paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities),
wherein when the sidelink HARQ includes HARQs corresponding to a plurality of different pieces of data sent by the first terminal device to one or more terminal devices, such that there are a plurality of pieces of sidelink data corresponding to the sidelink HARQ, the priority of the sidelink HARQ is a largest value in values of priority fields in a plurality of pieces of sidelink control information (SCI) for scheduling the plurality of pieces of data (Yoshioka, paragraph [0041], eMBB is associated with a low priority; paragraph [0042], URLLC is associated with a high priority; paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0077], eMBB or URLLC HARQ-ACK may be dropped or postponed based on the priority), and
wherein when the Priority of the sidelink HARQ is indicated in the priority fields of the SCI, when a field used by the SCI to indicate the priority of the sidelink HARQ, the priority of the sidelink HARQ is less than the first threshold (Yoshioka, paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on priorities corresponding to scheduling earlier than the latest; priorities may set in an order of SL-unicast HARQ-ACK>Uu HARQ-ACK>SL-groupcast HARQ-ACK, so SL-groupcast HARQ-ACK is the lowest priority).
Yoshioka does not explicitly disclose wherein the at least one threshold set from the plurality of thresholds correspond to one service type of the downlink data, and does not disclose that the priority of the HARQ is in a default priority state.
Pelletier discloses the priority of the HARQ is in a default priority state (Pelletier, paragraph [0568], control information sets a specific priority for a given HARQ process, WTRU receives further control signaling that deactivates the non-default priority).
It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to add the features taught by Pelletier into the system of Yoshioka in order to improve coordination of transmissions when interacting with different schedulers (Pelletier; [0006], [0984]).
The combination of Yoshioka and Pelletier does not explicitly disclose wherein the at least one threshold set from the plurality of thresholds correspond to one service type of the downlink data.
Panteleev discloses wherein the at least one threshold set from the plurality of thresholds correspond to one service type of the downlink data (Panteleev, paragraph [0043], conditional priorities for the cellular packets in the Uu link; paragraph [0045], different set of thresholds Pu-b, Pu-g, Pg-b may be configured for unicast and broadcast, unicast and groupcast, groupcast and broadcast). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to add the features taught by Panteleev into the system of the combination of Yoshioka and Pelletier in order to enhance groupcast and unicast transmission between devices (Panteleev; [0050]).
Regarding claim 22, the combination of Yoshioka, Pelletier, and Panteleev, particularly Yoshioka discloses wherein the priority of the sidelink HARQ is further based on: a priority of a transmission resource of the sidelink HARQ (Yoshioka, paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK).
Regarding claim 25, the combination of Yoshioka, Pelletier, and Panteleev, particularly Yoshioka discloses wherein sending, by the first terminal device, feedback information to the network device on the third resource based on the priority of the sidelink HARQ and the first threshold comprises: when a value of the priority of the sidelink HARQ is greater than or equal to the second threshold, sending, by the first terminal device, the downlink HARQ to the network device on the third resource and not sending the sidelink HARQ; or when a value of the priority of the sidelink HARQ is smaller than the second threshold, sending, by the first terminal device, the sidelink HARQ to the network device on the third resource and not sending the downlink HARQ (Yoshioka, paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK).
Regarding claim 26, Yoshioka discloses a method, comprising:
determining a first resource used to transmit a sidelink hybrid automatic repeat request (HARQ) and a second resource used to transmit a downlink HARQ (Yoshioka, Fig. 3; paragraph [0007], in sidelink transmission mode 1, user apparatus 20A transmits HARQ-ACK to base station apparatus 10 on a PUCCH; paragraph [0009], HARQ-ACKs in direct communication between terminals scheduled by a base station; paragraph [0032], based on SL scheduling determined by the base station, HARQ-ACK is fed back from the user apparatus 20A to the base station apparatus 10; paragraph [0034]; paragraph [0036], SL HARQ-ACK on the sidelink between the user apparatus 20A and the user apparatus 20B and Uu HARQ-ACK between the user apparatus 20A and the base station apparatus; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot), and whether to multiplex the sidelink HARQ and downlink HARQ, or to drop either the sidelink HARQ or downlink HARQ (Yoshioka, paragraph [0036], same slot is indicated for feeding back an SL HARQ-ACK and a Uu HARQ-ACK; collision between PUCCH including SL HARQ-ACK and PUCCH including another type of UCI; paragraph [0071], how to multiplex an SL HARQ-ACK and a Uu HARQ-ACK; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot; drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0074], it is also possible to consider multiplexing an SL HARQ-ACK and a Uu HARQ-ACK; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities),
wherein the sidelink HARQ corresponds to sidelink data sent by a first terminal device, and the downlink HARQ corresponds to downlink data sent by a network device to the first terminal device (Yoshioka, Fig. 3; paragraph [0007], in sidelink transmission mode 1, user apparatus 20A transmits HARQ-ACK to base station apparatus 10 on a PUCCH; paragraph [0009], HARQ-ACKs in direct communication between terminals scheduled by a base station; paragraph [0032], based on SL scheduling determined by the base station, HARQ-ACK is fed back from the user apparatus 20A to the base station apparatus 10; paragraph [0034]; paragraph [0036], SL HARQ-ACK on the sidelink between the user apparatus 20A and the user apparatus 20B and Uu HARQ-ACK between the user apparatus 20A and the base station apparatus; paragraph [0073], receiving DCI designating allocation of feedback Uu-HARQ-ACK and another DCI designating SL-HARQ-ACK in the same slot); and
receiving, when the first resource and the second resource overlap in time domain, feedback information from the first terminal device on a third resource, wherein the feedback information comprises the sidelink HARQ multiplexed with the downlink HARQ, the sidelink HARQ, or the downlink HARQ, wherein the feedback information is determined based either on a priority of the sidelink HARQ and a first threshold when it is determined to multiplex the sidelink HARQ and the downlink HARQ, or on the priority of the sidelink HARQ and a second threshold when it is determined to drop either the sidelink HARQ or downlink HARQ, the third resource is determined based on the first resource and the second resource, and wherein the third resource is the first resource, the second resource, or a different resource (Yoshioka, paragraph [0036], same slot is indicated for feeding back an SL HARQ-ACK and a Uu HARQ-ACK; collision between PUCCH including SL HARQ-ACK and PUCCH including another type of UCI; paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on [priorities] corresponding to scheduling earlier than the latest; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities;),
wherein when the sidelink HARQ includes HARQs corresponding to a plurality of different pieces of data sent by the first terminal device to one or more terminal devices, such that there are a plurality of pieces of sidelink data corresponding to the sidelink HARQ, the priority of the sidelink HARQ is a largest value in values of priority fields in a plurality of pieces of sidelink control information (SCI) for scheduling the plurality of pieces of data (Yoshioka, paragraph [0041], eMBB is associated with a low priority; paragraph [0042], URLLC is associated with a high priority; paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0077], eMBB or URLLC HARQ-ACK may be dropped or postponed based on the priority),
wherein when the priority of the sidelink HARQ is indicated in the priority fields of the SCI, when a field used by the SCI to indicate the priority of the sidelink HARQ, the priority of the sidelink HARQ is less than the first threshold (Yoshioka, paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on priorities corresponding to scheduling earlier than the latest; priorities may set in an order of SL-unicast HARQ-ACK>Uu HARQ-ACK>SL-groupcast HARQ-ACK, so SL-groupcast HARQ-ACK is the lowest priority), and
wherein the first threshold and the second threshold comprise a threshold set that is determined from a plurality of thresholds based on a service type of the downlink data, wherein at least one threshold of the plurality of thresholds corresponds to one service type of the downlink data, different thresholds correspond to different service types of the downlink data, the plurality of thresholds includes the threshold set, and the threshold set may be preconfigured or predefined, threshold set is used to represent a priority of data of one service type (Yoshioka, paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on [priorities] corresponding to scheduling earlier than the latest; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities; paragraph [0078], Uu eMBB-HARQ-ACK, Uu URLLC-HARQ-ACK).
Yoshioka does not explicitly disclose wherein the threshold set is used to represent a priority of downlink data of one service type, and does not disclose that the priority of the HARQ is in a default priority state.
Pelletier discloses the priority of the HARQ is in a default priority state (Pelletier, paragraph [0568], control information sets a specific priority for a given HARQ process, WTRU receives further control signaling that deactivates the non-default priority).
It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to add the features taught by Pelletier into the system of Yoshioka in order to improve coordination of transmissions when interacting with different schedulers (Pelletier; [0006], [0984]).
The combination of Yoshioka and Pelletier does not explicitly disclose wherein the threshold set is used to represent a priority of downlink data of one service type.
Panteleev discloses wherein the threshold set is used to represent a priority of downlink data of one service type (Panteleev, paragraph [0043], conditional priorities for the cellular packets in the Uu link; paragraph [0045], different set of thresholds Pu-b, Pu-g, Pg-b may be configured for unicast and broadcast, unicast and groupcast, groupcast and broadcast). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to add the features taught by Panteleev into the system of the combination of Yoshioka and Pelletier in order to enhance groupcast and unicast transmission between devices (Panteleev; [0050]).
Claim 27 is rejected under substantially the same rationale as claim 22.
Claim 30 is rejected under substantially the same rationale as claim 25.
Claim 31 is rejected under substantially the same rationale as claim 21. Yoshioka additionally discloses a communication apparatus, comprising at least one processor and a memory, wherein the memory stores program instructions, and when executing the program instructions, the at least one processor executes operations (Yoshioka, paragraph [0114], program on the processor and memory device cause the processor to execute operations).
Claim 32 is rejected under substantially the same rationale as claim 22.
Claim 35 is rejected under substantially the same rationale as claim 25.
Claim 36 is rejected under substantially the same rationale as claim 26. Yoshioka additionally discloses a communication apparatus, comprising at least one processor and a memory, wherein the memory stores program instructions, and when executing the program instructions, the at least one processor executes operations (Yoshioka, paragraph [0114], program on the processor and memory device cause the processor to execute operations).
Claim 37 is rejected under substantially the same rationale as claim 22.
Claim 40 is rejected under substantially the same rationale as claim 25.
Regarding claim 41, the combination of Yoshioka, Pelletier, and Panteleev, particularly Yoshioka discloses wherein sending, by the first terminal device, feedback information to the network device on the third resource based on the priority of the sidelink HARQ and the first threshold comprises: when a value of the priority of the sidelink HARQ is greater than the first threshold, sending, by the first terminal device, the sidelink HARQ multiplexed with the downlink HARQ to the network device on the third resource; and when a value of the priority of the sidelink HARQ is less than or equal to the first threshold, sending, by the first terminal device, the downlink HARQ to the network device on the third resource and not sending the sidelink HARQ (Yoshioka, paragraphs [0047]-[0049], different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK; paragraph [0077], SL URLLC HARQ-ACK may always be dropped or postponed or Uu URLLC HARQ-ACK may be always be dropped or postponed, or both HARQ-ACKs may be multiplexed and transmitted, depending on priorities).
Claims 42-44 are rejected under substantially the same rationale as claim 41.
Regarding claim 45, the combination of Yoshioka, Pelletier, and Panteleev, particularly Yoshioka discloses wherein the priority of the sidelink HARQ is further based on a priority of sidelink data corresponding to the sidelink HARQ (Yoshioka, paragraphs [0041]-[0042] and [0047]-[0049], assign different priority levels for different service types including eMBB and URLLC; paragraph [0073], drop or postpone either one of the Uu-HARQ-ACK or the SL-HARQ-ACK based on priorities set for SL-unicast-HARQ-ACK, Uu-HARQ-ACK, SL-groupcast-HARQ-ACK, or based on priorities corresponding to scheduling earlier than the latest; paragraph [0078], Uu eMBB-HARQ-ACK, Uu URLLC-HARQ-ACK).
Claims 46-48 are rejected under substantially the same rationale as claim 45.
Conclusion
THIS ACTION IS MADE FINAL. 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.
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Guo et al. (US 20220286255) discloses the priority level for SL CSI reporting may be determined as follows. If the TX UE configures the PQI indicating a priority level for the pair of SL CSI-RS and SL CSI reporting explicitly, this priority level may be used as the priority level for the SL CSI reporting; otherwise, if the SL CSI-RS is transmitted together with data, the priority level for the data may be used as the priority level for the CSI reporting corresponding to the CSI-RS; otherwise, if the CSI reporting is transmitted together with data directed to the destination UE of the SL CSI reporting, i.e. the TX UE, the priority level for the data may be used as the priority level for the SL CSI reporting.
Yi et al. (US 20160205632) discloses when dropping is configured, the priority of channels may be order or PRACH-PUCCH-PUSCH with UCI-PUSCH without UCI-SRS. That is, the dropping priority may be similar to scaling priority. When the same channels are colliding with each other between two eNBs, priority eNB may be configured. Alternatively, order of PRACH-HARQ-ACK/SR-CSI-data may be considered. By default, the UE assume that higher priority is given to the eNB which maintains C-Plane connection (e.g., PCell).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ALAN LOUIS LINDENBAUM whose telephone number is (571)270-3858. The examiner can normally be reached Monday through Friday 11:00 AM to 7:00 PM EST.
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, Un Cho can be reached at (571) 272-7919. 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.
/A.L.L/ Examiner, Art Unit 2413
/UN C CHO/ Supervisory Patent Examiner, Art Unit 2413
Prosecution Insights