DETAILED ACTION
The amendments and remarks filed 6/5/2025 were received. Claims 7-9 are pending.
PRIOR ART
The following references are prior art:
1. (11/15/2024 PTO-892) Appl. No. 17/802,808 (“Matsumura”) is prior art under 35 U.S.C. 102(a)(2) since it was published as US 2023/0086798 A1, names another inventor (Yuki Matsumura), and was effectively filed on Feb. 28, 2020 before the effective filing date of the present invention (Mar. 27, 2020).
CLAIM REJECTIONS — 35 U.S.C. 112
The following is a quotation of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention
Claims 7-9 are rejected under 35 U.S.C. 112(a) as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claim 7 as amended recites “transmitting, to the base station apparatus, the codebook-based PUSCH, wherein: in the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH.” Applicant claims the use of two SRS resource set configurations in codebook-based PUSCH. Claims 8 and 9 recite similar limitations. Applicant states, on page 1 of their Remarks, “Support for the new amendments may be found in the originally filed application, for example, in paragraphs [0117] and [0121] of the originally filed specification.” However, the Examiner cannot find written description support for these limitations in the portions cited by Applicant or anywhere in the disclosure. The most relevant portions of the disclosure that the Examiner can find are:
[0116] A PUSCH transmission scheme may include codebook-based transmission configuration and non-codebook based transmission configuration.
(cited by Applicant) [0117] An SRI field in the DCI format 0_l or 0_2 may be used to indicate the spatial domain transmission filter. Information on two spatial domain transmission filters may be indicated for PUSCH resources 801 and 802. The SRI field may indicate the SRS resource index, and the spatial domain transmission filter for the SRS corresponding to the indicated SRS resource index in the DCI. The UE 102 may apply the same spatial domain transmission filter as the SRI-indicated SRS.
[0119] A first case (Case 1) includes a single SRS resource and SRS spatial relation in- formation with multiple RS indices.
[0120] A second case (Case 2) includes a single SRS resource and multiple spatial relation
information with a single RS index.
(cited by Applicant) [0121] A third case (Case 3) includes a single SRS resource, single spatial relation information, and multiple SRS resource set. The SRI field may indicate combinations of an SRS resource index and an SRS resource set index. For example, the SRI field may indicate combination #1 (an SRS index #1 and an SRS resource set #1) and combination #2 (an SRS index #1 and an SRS resource set #2). AUE 102 may apply a spatial domain transmission filter based on the SRS index #1 in the SRS resource set #1 to the PUSCH 801 and a spatial domain transmission filter based on the SRS index #1 in the SRS resource set #2.
[0123] A fourth case (Case 4) includes multiple SRS resources, and single spatial relation information for each SRS resource.
[0124] Additionally or alternately, the multi-beam based PUSCH transmission using the SRI field in the DCI may be applied for codebook-based transmission or non-codebook based transmission. Additionally or alternately, the different schemes may be applied to codebook-based transmission and non-codebook based transmission. For example, for codebook-based transmission, scheme of case 1 and case 2 may be applied, and for non-codebook based transmission, schemes of case 3 and case 4 may be applied. (emphasis added).
As such, the Specification generally disclosed the use of codebook or non-codebook based transmissions across cases 1, 2, 3, and 4 but only specifically described the use of codebook-based transmission for case 1 and 2 and specifically described the use of non-codebook based tranmissions for case 3 and 4. Case 3 is described in the paragraph cited by Applicant. The Application specifically disclosed case 3 as using multiple SRS resource sets and as being non-codebook based. The limitation “transmitting, to the base station apparatus, the codebook-based PUSCH, wherein: in the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH” claims the use of two SRS resource set configurations in codebook-based PUSCH, rather than the non-codebook based transmission as described in the specification.
Referring to MPEP 2163, to satisfy the written description requirement, a patent specification must describe the claimed invention in sufficient detail that one skilled in the art can reasonably conclude that the inventor had possession of the claimed invention. See, e.g., Moba, B.V. v. Diamond Automation, Inc., 325 F.3d 1306, 1319, 66 USPQ2d 1429, 1438 (Fed. Cir. 2003). An applicant shows that the inventor was in possession of the claimed invention by describing the claimed invention with all of its limitations using such descriptive means as words, structures, figures, diagrams, and formulas that fully set forth the claimed invention. Lockwood v. Amer. Airlines, Inc., 107 F.3d 1565, 1572, 41 USPQ2d 1961, 1966 (Fed. Cir. 1997). Here, the Examiner cannot find description in sufficient detail that one skilled in the art can reasonably conclude that the inventor had possession of the claimed invention.
CLAIM REJECTIONS — 35 U.S.C. 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:
35 U.S.C. 103 Conditions for patentability; non-obvious subject matter.
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.
CLAIMS 7-9
Claims 7-9 are rejected under 35 U.S.C. 103 as being unpatentable over Matsumura (US 2023/0086798 A1).
Claim 7
With respect to claim 7, Matsumura taught:
A user equipment (UE) comprising: receiving circuitry (Matsumura [0215] taught that FIG. 14 is a diagram illustrating an example of a configuration of a user terminal according to one embodiment. The user terminal 20 includes… a transmitting/receiving section 220. Matsumura [0219] taught that the transmitting/receiving section 220 can include… a transmitting/receiving circuit. Matsumura [0285] taught that in the present disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" can be used interchangeably)
configured to: receive, from a base station apparatus, a radio resource control (RRC) message including two sounding reference signal (SRS) resource set configurations, one of the two SRS resource set configurations being a configuration for applying a first spatial domain transmission filter, the other one of the two SRS resource set configurations being a configuration for applying a second spatial domain transmission filter (Matsumura taught [0063] In Rel. 15 NR, the UE may receive information (SRS configuration information, for example, a parameter in the RRC control element "SRS-Config") used for transmission of a measurement reference signal (for example, a sounding reference signal (SRS)). [0064] Specifically, the UE may receive at least one of information related to one or a plurality of SRS resource sets (SRS resource set information, for example, "SRS-ResourceSet" of the RRC control element) and information related to one or a plurality of SRS resources (SRS resource information, for example, "SRS-Resource" of the RRC control element). [0071] The spatial relation information (for example, "spatialRelation Info" of the RRC information element) of the SRS may indicate spatial relation information between a given reference signal and the SRS. [0077] The UE may determine the spatial relation of the PUSCH scheduled by the DCI based on a value of a given field (for example, SRS resource identifier (SRI) field) in the DCI (for example, DCI format 0_1). Specifically, the UE may use the spatial relation information (for example, "spatialRelationinfo" of the RRC information element) of the SRS resource determined based on the value (for example, SRI) of the given field for the PUSCH transmission. [0092] In the first embodiment, the UE may be configured with a given number (for example, M) of SRS resource lists in association with one SRS resource set by RRC signaling. Here, the given number M may be, for example, 8, 64, or the like, or may be larger than 64. One or a plurality of SRS resource lists may be configured in an SRS resource set for a specific use (for example, a codebook or non-codebook). [0093] A maximum of R SRS resources may be associated with one SRS resource list. Here, R may correspond to the maximum number of TRPs for the PUSCH. [0094] FIG. 5A illustrates an example in which a plurality of SRS resource lists (SRS resource list #0, #1, ... ) are configured in association with the SRS resource set. The SRS resource list #0 is associated with the SRS resource #0. The SRS resource list #1 is associated with {SRS resources #0, #1}. [0098] In the first embodiment, one or a plurality of SRS resource lists in the activated SRS resource lists may be indicated to the UE by using a field of the DCI. Note that the field may be an existing DCI field (for example, the SRI field), may be a new DCI field (for example, the SRS resource list field for repetition transmission), or may be expressed by a combination of a plurality of fields. [0099] A UE configured with codebook-based PUSCH transmission or configured with single-layer non-codebook based PUSCH transmission may assume that one SRS resource list is indicated for PUSCH transmission across multiple TRPs. [0100] a DCI field for specifying one SRS resource list according to the first embodiment. In this example, a value ("Bit field mapped to index") of a given field included in the DCI and a corresponding activated SRS resource list are illustrated. [0105] it is possible to dynamically change the SRS resource list specified by the DCI by using the MAC CE to perform the PUSCH repetition transmission. For example, control using different SRS resources can be performed for each PUSCH resource and for each PUSCH repetition. [0164] In each of the above embodiments, the UE in which one SRS resource (or an SRS resource list including one SRS resource) is specified for the PUSCH repetition transmission may transmit the repetition transmission based on the SRS resource. Note that the repetition transmission based on the SRS resource may mean repetition transmission based on a spatial relation determined based on the SRS resource (for example, a spatial domain transmission filter based on the spatial relation is used). [0212] the transmitting section and the receiving section of the base station 10... [0213] the transmitting/receiving section 120 may transmit, to the user terminal 20, at least one of radio resource control (RRC) signaling. [Claim 5] A base station comprising: a transmitting section that transmits, to a terminal, at least one of radio resource control (RRC) signaling… and downlink control information (DCI) used for determination of spatial relation information for a physical uplink shared channel (PUSCH) for a plurality of transmission/reception points. The Examiner finds that Matsumura taught to: receive a radio resource control (RRC) message (i.e., RRC signaling) including two sounding reference signal (SRS) resource set configurations (i.e., information related to one or a plurality of SRS resource sets, including the plurality of SRS resource lists indicated to the UE, by RRC signaling, by using a field of the DCI, where a maximum of R SRS resources are associated with one SRS resource list. There are a plurality of SRS resource lists and each is a configuration of an SRS resource set), one of the two SRS resource set configurations being a configuration for applying a first spatial domain transmission filter, the other one of the two SRS resource set configurations being a configuration for applying a second spatial domain transmission filter (i.e., the RRC information includes control/configuration for a plurality of SRS resources, each (i.e., first, second, one, the other. etc.) of which has spatialRelationInfo that indicates the spatial domain transmission filter based on the spatial relation). Matsumura suggests that the RRC message controlling SRS is received from a base station apparatus with the description in [0212]-[0213] since the UE is being controlled),
and receive, from the base station apparatus, downlink control information (DCI) for determining the first spatial domain transmission filter and the second spatial domain transmission filter in accordance with a scheme, the first spatial domain transmission filter and the second spatial domain transmission filter being, respectively, applied to a first repetition of a codebook-based physical uplink shared channel (PUSCH) and a second repetition of the codebook-based PUSCH (Matsumura taught [0032]-[0037] The UE controls… PUSCH transmission processing (for example, at least one of transmission, mapping, modulation, and code) in K consecutive slots based on at least one of the following field valued ( or information indicated by the field value) in the DCI: … PUSCH spatial relation info, or the state of transmission configuration indication (TCI) or transmission configuration indicator (TCI-state). [0069] For example, in the case of the codebook-based transmission, the UE may determine the precoder for the PUSCH transmission on the basis of the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI). [0072] In the present disclosure… the SRS index, the SRS resource ID, and the SRI may be replaced with each other. [0077] The UE may determine the spatial relation of the PUSCH scheduled by the DCI based on a value of a given field (for example, SRS resource identifier (SRI) field) in the DCI (for example, DCI format 0_1). Specifically, the UE may use the spatial relation information (for example, "spatialRelationinfo" of the RRC information element) of the SRS resource determined based on the value (for example, SRI) of the given field for the PUSCH transmission. [0078] When the codebook-based transmission is used for the PUSCH, in the UE, two SRS resources per SRS resource set may be configured by RRC, and one of the two SRS resources may be indicated by DCI (1-bit SRI field). [0082] the present inventors have conceived a control method of PUSCH repetition transmission. According to an aspect of the present disclosure, for example, a UE may perform PUSCH repetition transmission for multiTRPs using different beams for each repetition unit (for example, segment, subslot). [0083] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The radio communication method according to each of the embodiments may be applied independently, or may be applied in combination with others. [0088] In the following embodiments, the PUSCH across the plurality of TRPs may be replaced with a repetition PUSCH across the plurality of TRPs, simply a repeated PUSCH, a repetition transmission, or the like. [0089] In addition, the SRS resource set in the following embodiments may be read as an SRS resource set whose usage is a codebook or a non-codebook. [0099] A UE configured with codebook-based PUSCH transmission. [0105] it is possible to dynamically change the SRS resource list specified by the DCI by using the MAC CE to perform the PUSCH repetition transmission. For example, control using different SRS resources can be performed for each PUSCH resource and for each PUSCH repetition. [0016] FIGS. 5A to 5D are diagrams illustrating examples of notification of spatial relation information according to a first embodiment. [0017] FIGS. 6A to 6C are diagrams illustrating examples of notification of spatial relation information according to a second embodiment. [0018] FIGS. 7A to 7C are diagrams illustrating examples of notification of spatial relation information according to a third embodiment. [0019] FIGS. 8A to 8C are diagrams illustrating examples of notification of spatial relation information according to a fourth embodiment. [0020] FIGS. 9A to 9C are diagrams illustrating examples of notification of spatial relation information according to a fifth embodiment. [0021] FIGS. l0A to l0C are diagrams illustrating examples of notification of spatial relation information according to a sixth embodiment. [0022] FIGS. 11A to 11C are diagrams illustrating examples of notification of spatial relation information according to a seventh embodiment. [0168] The UE may switch and use a plurality of embodiments among the first to seventh embodiments described above. For example, the first, third, fourth or fifth embodiment using a MAC CE may be applied when a UE receives a MAC CE configured by RRC (for example, MAC CE based control configured to be used for PUSCH repetition transmission) or a new MAC CE (for example, the MAC CE as described in the first embodiment), otherwise a non-MAC CE based control (second or sixth embodiment) may be applied. The Examiner finds that Matsumura taught to receive, from the base station apparatus, downlink control information (DCI) for determining the first spatial domain transmission filter and the second spatial domain transmission filter (i.e., determination of spatial relation information) in accordance with a scheme (e.g., DCI according to one of Matsumura’s embodiments described in [0090]-[0162] with respect to FIGs. 5-11.), the first spatial domain transmission filter and the second spatial domain transmission filter being, respectively, applied (i.e., different SRS resources/spatial domain transmission filters can be performed for each PUSCH resource and for each PUSCH repetition) to a first repetition of a codebook-based physical uplink shared channel (PUSCH) and a second repetition of the codebook-based PUSCH (i.e., repetition PUSCH across the plurality of TRPs that using codebook or non-codebook based PUSCH transmission));
processing circuitry (Matsumura taught [0217] The control section 210 controls the entire user terminal 20. The control section 210 can include a controller, a control circuit.)
configured to use the DCI to determine, in accordance with the scheme, a first reference signal resource index and a second reference signal resource index, which are, respectively, associated with the first spatial domain transmission filter and the second spatial domain transmission filter (Matsumura, Abstract, taught a terminal according to one aspect of the present disclosure includes a control section that determines spatial relation information for a physical uplink shared channel (PUSCH) for a plurality of transmission/reception points by using at least one of radio resource control (RRC) signaling, medium access control (MAC) signaling, and downlink control information (DCI), and a transmitting section that repeatedly transmits the PUSCH by using a spatial domain transmission filter based on the spatial relation information. Matsumura [0032]- [0037] taught field value (or information indicated by the field value) in the DCI: . . . PUSCH spatial relation info. [0072] The spatial relation information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the given reference signal. [0073] Note that, in the present disclosure… the SRS index, the SRS resource ID, and the SRI may be replaced with each other. Matsumura [0075] taught that when spatial relation information regarding the SSB or CSI-RS and the SRS is configured for a given SRS resource, the UE may transmit the SRS resource by using the same spatial domain filter (spatial domain transmission filter) as a spatial domain filter (spatial domain reception filter) for receiving the SSB or CSI-RS. Matsumura [0077] taught the UE may determine the spatial relation of the PUSCH scheduled by the DCI based on a value of a given field (for example, SRS resource identifier (SRI) field) in the DCI (for example, DCI format 0_1). Specifically, the UE may use the spatial relation information (for example, "spatialRelationinfo" of the RRC information element) of the SRS resource determined based on the value (for example, SRI) of the given field for the PUSCH transmission. [0091] FIGS. 5A to 5D are diagrams illustrating examples of notification of spatial relation information according to the first embodiment. [0092] In the first embodiment, the UE may be configured with a given number (for example, M) of SRS resource lists in association with one SRS resource set by RRC signaling. Here, the given number M may be, for example, 8, 64, or the like, or may be larger than 64. One or a plurality of SRS resource lists may be configured in an SRS resource set for a specific use (for example, a codebook or non-codebook). [0093] A maximum of R SRS resources may be associated with one SRS resource list. Here, R may correspond to the maximum number of TRPs for the PUSCH. [0094] FIG. SA illustrates an example in which a plurality of SRS resource lists (SRS resource list #0, #1, ... ) are configured in association with the SRS resource set. The SRS resource list #0 is associated with the SRS resource #0. The SRS resource list #1 is associated with {SRS resources #0, #1}. [0098] In the first embodiment, one or a plurality of SRS resource lists in the activated SRS resource lists may be indicated to the UE by using a field of the DCI. Note that the field may be an existing DCI field (for example, the SRI field), may be a new DCI field (for example, the SRS resource list field for repetition transmission), or may be expressed by a combination of a plurality of fields. [0099] A UE configured with codebook-based PUSCH transmission or configured with single-layer non-codebook based PUSCH transmission may assume that one SRS resource list is indicated for PUSCH transmission across multiple TRPs. [0100] a DCI field for specifying one SRS resource list according to the first embodiment. In this example, a value ("Bit field mapped to index") of a given field included in the DCI and a corresponding activated SRS resource list are illustrated. [0164] In each of the above embodiments, the UE in which one SRS resource (or an SRS resource list including one SRS resource) is specified for the PUSCH repetition transmission may transmit the repetition transmission based on the SRS resource. Note that the repetition transmission based on the SRS resource may mean repetition transmission based on a spatial relation determined based on the SRS resource (for example, a spatial domain transmission filter based on the spatial relation is used). The Examiner finds that Matsumura taught processing circuitry (i.e., controller of the UE) configured to use the DCI to determine, in accordance with the scheme (i.e., use the DCI in accordance with a first embodiment of the seven embodiments), a first reference signal resource index and a second reference signal resource index (i.e., SRS resource lists indicated by the SRI field of the DCI), which are, respectively, associated with the first spatial domain transmission filter and the second spatial domain transmission filter (i.e., the SRS resource lists are associated with SRS resources that corresponding to spatial relation info/spatial domain transmission filters)),
and transmitting circuitry (Matsumura [0215] taught that the user terminal 20 includes… a transmitting/receiving section 220. Matsumura [0219] taught that the transmitting/receiving section 220 can include… a transmitting/receiving circuit),
configured to transmit, to the base station apparatus, the codebook-based PUSCH, wherein the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH, the first repetition of the codebook-based PUSCH is transmitted based on the first reference signal resource index such that the first spatial domain transmission filter is applied to the first repetition of the codebook-based PUSCH, and the second repetition of the codebook-based PUSCH is transmitted based on the second reference signal resource index such that the second spatial domain transmission filter is applied to the second repetition of the PUSCH (Matsumura [Abstract] taught a terminal according to one aspect of the present disclosure includes a control section that determines spatial relation information for a physical uplink shared channel (PUSCH) for a plurality of transmission/reception points by using at least one of radio resource control (RRC) signaling, medium access control (MAC) signaling, and downlink control information (DCI), and a transmitting section that repeatedly transmits the PUSCH by using a spatial domain transmission filter based on the spatial relation information. [0072] The spatial relation information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the given reference signal. [0073] Note that, in the present disclosure… the SRS index, the SRS resource ID, and the SRI may be replaced with each other. Matsumura [0075] taught that when spatial relation information regarding the SSB or CSI-RS and the SRS is configured for a given SRS resource, the UE may transmit the SRS resource by using the same spatial domain filter (spatial domain transmission filter) as a spatial domain filter (spatial domain reception filter) for receiving the SSB or CSI-RS. Matsumura [0077] taught the UE may determine the spatial relation of the PUSCH scheduled by the DCI based on a value of a given field (for example, SRS resource identifier (SRI) field) in the DCI (for example, DCI format 0_1). Specifically, the UE may use the spatial relation information (for example, "spatialRelationinfo" of the RRC information element) of the SRS resource determined based on the value (for example, SRI) of the given field for the PUSCH transmission. [0078] When the codebook-based transmission is used for the PUSCH, in the UE, two SRS resources per SRS resource set may be configured by RRC, and one of the two SRS resources may be indicated by DCI (1-bit SRI field). [0082] the present inventors have conceived a control method of PUSCH repetition transmission. According to an aspect of the present disclosure, for example, a UE may perform PUSCH repetition transmission for multiTRPs using different beams for each repetition unit (for example, segment, subslot). [0088] In the following embodiments, the PUSCH across the plurality of TRPs may be replaced with a repetition PUSCH across the plurality of TRPs, simply a repeated PUSCH, a repetition transmission, or the like. [0089] In addition, the SRS resource set in the following embodiments may be read as an SRS resource set whose usage is a codebook or a non-codebook, or may be read as an SRS resource set for other usages. [0091] FIGS. 5A to 5D are diagrams illustrating examples of notification of spatial relation information according to the first embodiment. [0092] In the first embodiment, the UE may be configured with a given number (for example, M) of SRS resource lists in association with one SRS resource set by RRC signaling. Here, the given number M may be, for example, 8, 64, or the like, or may be larger than 64. One or a plurality of SRS resource lists may be configured in an SRS resource set for a specific use (for example, a codebook or non-codebook). [0093] A maximum of R SRS resources may be associated with one SRS resource list. Here, R may correspond to the maximum number of TRPs for the PUSCH. [0094] FIG. SA illustrates an example in which a plurality of SRS resource lists (SRS resource list #0, #1, ... ) are configured in association with the SRS resource set. The SRS resource list #0 is associated with the SRS resource #0. The SRS resource list #1 is associated with {SRS resources #0, #1}. [0098] In the first embodiment, one or a plurality of SRS resource lists in the activated SRS resource lists may be indicated to the UE by using a field of the DCI. Note that the field may be an existing DCI field (for example, the SRI field), may be a new DCI field (for example, the SRS resource list field for repetition transmission), or may be expressed by a combination of a plurality of fields. [0099] A UE configured with codebook-based PUSCH transmission or configured with single-layer non-codebook based PUSCH transmission may assume that one SRS resource list is indicated for PUSCH transmission across multiple TRPs. [0100] a DCI field for specifying one SRS resource list according to the first embodiment. In this example, a value ("Bit field mapped to index") of a given field included in the DCI and a corresponding activated SRS resource list are illustrated. [0104] FIG. 5D is a diagram illustrating an example of a DCI field for specifying a plurality of SRS resource lists according to the first embodiment. [0105] According to the first embodiment described above, it is possible to dynamically change the SRS resource list specified by the DCI by using the MAC CE to perform the PUSCH repetition transmission. For example, control using different SRS resources can be performed for each PUSCH resource and for each PUSCH repetition. [0165] In each of the above embodiments, the UE in which the plurality of SRS resources ( or the SRS resource list including the plurality of SRS resources) are specified for the PUSCH repetition transmission may transmit a part of the repetition transmission based on a part of the SRS resources and transmit the remaining repetition transmission based on the remaining. [0167] The UE may apply the same one of the foregoing first to seventh embodiments to codebook-based transmission and non-codebook-based transmission. The UE may apply the different embodiments in the foregoing first to seventh embodiments to codebook-based transmission and non-codebook-based transmission. The Examiner finds that Matsumura taught to transmit, to the base station apparatus, the codebook-based PUSCH (i.e., PUSCH repetition transmissions based on SRS resources), wherein in the scheme based on DCI (i.e., the first embodiment in Matsumura), the two SRS resource set configurations (i.e., two SRS resources per SRS resource set, indicated by DCI, where the DCI indicates an SRS resource list) are used for the first repetition of the codebook-based PUSCH and the second repetition of the ccodebook-based PUSCH, the first repetition of the codebook-based PUSCH is transmitted based on the first reference signal resource index such that the first spatial domain transmission filter is applied to the first repetition of the codebook-based PUSCH, and the second repetition of the codebook-based PUSCH is transmitted based on the second reference signal resource index such that the second spatial domain transmission filter is applied to the second repetition of the PUSCH (i.e., in Matsumura the SRS resource ID is used as an index of the given reference signal and the different SRS resource lists are associated with SRS resources that correspond to spatial relation info/spatial domain transmission filters used when transmitting the PUSCH repetitions, which can be codebook-based)).
The Examiner recognizes that Matsumura does not identically disclose as set forth in section 102 the claimed “codebook-based PUSCH.” However, Matsumura suggested this limitation because Matsumura taught to combine its techniques across embodiments:
[0088] In the following embodiments, the PUSCH across the plurality of TRPs may be replaced with a repetition PUSCH across the plurality of TRPs, simply a repeated PUSCH, a repetition transmission, or the like.
[0089] In addition, the SRS resource set in the following embodiments may be read as an SRS resource set whose usage is a codebook or a non-codebook, or may be read as an SRS resource set for other usages.
[0105] For example, control using different SRS resources can be performed for each PUSCH resource and for each PUSCH repetition.
[0165] In each of the above embodiments, the UE in which the plurality of SRS resources ( or the SRS resource list including the plurality of SRS resources) are specified for the PUSCH repetition transmission may transmit a part of the repetition transmission based on a part of the SRS resources and transmit the remaining repetition transmission based on the remaining.
The Examiner finds that 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. Specifically, it would be obvious to implement Matsumura’s first embodiment using codebook-based PUSCH because Matsumura [0167] states “The UE may apply the same one of the foregoing first to seventh embodiments to codebook-based transmission and non-codebook-based transmission.”
Claim 8
Claim 8 recites limitations similar to claim 7 except that it additionally recites that the base station apparatus comprises “transmitting circuitry” and “receiving circuitry.” Matsumura [0196] taught that the base station 10 includes… a transmitting/receiving section 120. Matsumura [0200] taught that the transmitting/receiving section 120 may include… a transmitting/receiving circuit. Claim 8 is rejected for these reasons along with the reasons given for claim 7 above.
Claim 9
Claim 9 recites limitations similar to claim 7 and is rejected by the same reasoning.
RESPONSE TO ARGUMENTS
Applicant’s arguments, see Remarks, filed 9/25/2025, with respect to Rejections under 35 U.S.C. 112(a) have been fully considered and are persuasive in view of the amendments. Those rejections have been withdrawn.
Applicant’s arguments, see Remarks, filed 9/25/2025, with respect to Claim Objections have been fully considered and are persuasive in view of the amendments. Those objections have been withdrawn.
Applicant’s arguments filed 9/25/22025 with respect to the rejections under 35 U.S.C. 103 have been fully considered but they are not persuasive.
To start, the Examiner believes that Applicant is arguing limitations that are not claimed. Claim 7 recites “a radio resource control (RRC) message including two sounding reference signal (SRS) resource set configurations.” That is the SRS resource configuration is included in an RRC message. Claim 7 goes on to state “one of the two SRS resource set configurations being a configuration for applying a first spatial domain transmission filter, the other one of the two SRS resource set configurations being a configuration for applying a second spatial domain transmission filter.” At best, the claim is limited to two configurations of an SRS resource set that in an RRC message, where these configurations are for applying a first/second spatial domain transmission filter. Matsumura’s SRS resource lists read on the above limitations because they are configurations of a SRS resource set, are included in RRC, and are configurations for applying spatial relations info/spatial domain transmission filter. If something more specific is intended then it should be claimed.
In response to Applicants arguments, on page 2 and 3 Applicant quoted the previous Office Action in which the Examiner responded to Applicant’s argument about “two SRS resource set configurations” by asserting that Matsumura’s multiple SRS resource lists are used for codebook-based PUSCH transmission. Applicant then provided their understanding of such lists in paragraphs 92, 94, 95, 98, 99, and 103. However, Applicant did not address paragraph [0105] cited in the previous office action and relied on again in the present rejection. Matsumura [0105] states: “it is possible to dynamically change the SRS resource list specified by the DCI by using the MAC CE to perform the PUSCH repetition transmission. For example, control using different SRS resources can be performed for each PUSCH resource and for each PUSCH repetition.”
Matsumura’s plurality of SRS resource lists read on the claimed two sounding reference signal (SRS) resource set configurations. As explained in the rejection above, the Examiner finds that Matsumura taught to receive a radio resource control (RRC) message (i.e., RRC signaling) including two sounding reference signal (SRS) resource set configurations (i.e., information related to one or a plurality of SRS resource sets, including the plurality of SRS resource lists indicated to the UE, by RRC signaling, by using a field of the DCI, where a maximum of R SRS resources are associated with one SRS resource list. There are a plurality of SRS resource lists and each is a configuration of an SRS resource set), one of the two SRS resource set configurations being a configuration for applying a first spatial domain transmission filter, the other one of the two SRS resource set configurations being a configuration for applying a second spatial domain transmission filter (i.e., the RRC information includes control/configuration for a plurality of SRS resources, each (i.e., first, second, one, the other. etc.) of which has spatialRelationInfo that indicates the spatial domain transmission filter based on the spatial relation). Matsumura suggests that the RRC message controlling SRS is received from a base station apparatus with the description in [0212]-[0213] since the UE is being controlled.
CONCLUSION
Applicant's amendment necessitated the new grounds 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 extension fee 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 date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Christopher Davis whose telephone number is 703-756-1832. The examiner can normally be reached Mon-Fri from 11AM to 7PM ET. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ayaz Sheikh, can be reached at telephone number 571-272-3795. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center to authorized users only. Should you have questions about access to the USPTO patent electronic filing system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). Examiner interviews are available via a variety of formats see MPEP § 713.01. To schedule an interview, use the Request Form at https://www.uspto.gov/InterviewPractice
/C.R.D./
Examiner, Art Unit 2476
/AYAZ R SHEIKH/Supervisory Patent Examiner, Art Unit 2476