DETAILED ACTION
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 Amendment
Amendments filed on 10/22/2025 are entered. The amendments change the scopes of the previously presented claims. New grounds of rejections are applied to the amended claims and the current Office Action is made FINAL as necessitated by the claim amendments.
Response to Arguments
Applicant’s arguments with respect to claim(s) 1, 4-11 and 14-20 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
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.
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) 1, 4-8, 10-11, 14-18 and 20-24 is/are rejected under 35 U.S.C. 103 as being unpatentable over Guo ‘512 (US 2025/0024512 A1) in view of Go (US 2025/0151063) and Fan (US 2024/0205855).
Guo ‘512 discloses the following features.
Regarding claim 1, a method comprising:
transmitting, by the wireless device (see “UE” recited in paragraph [0123]), a RA preamble of an RA procedure of the serving cell (see step 910 in Fig. 9 and paragraph [0123], wherein the UE transmits a random access preamble in a cell associated with multiple TAGs);
receiving an RAR, corresponding to the RA preamble, wherein the RAR comprises: a TAC (see step 920 in Fig. 9, wherein the UE receives a RAR including a TAC in response to the preamble transmitted in step 910); and a bitfield indicating a binary value, wherein a first value of the binary value indicates the first TAG and a second value of the binary value indicates the second TAG; wherein the RAR does not comprise a TAG ID (see “the TAG indication field may be included in the RAR. In such aspects, the corresponding TAG may be indicated using a reserved bit in the RAR PDSCH. For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106], wherein a single bit field is used for indicating the TAG, therefore, there is no need for the use of a TAG identity field);
applying the TAC to the TAG, wherein the TAG is: the first TAG based on the binary value being set to the first value; and the second TAG based on the binary value being set to the second value (see step 940 in Fig. 9, wherein timing advance parameter being adjusted with the corresponding TAG based on the TAC; and see paragraph [0106], which describe the TAG indicator bit).
Regarding claim 4, wherein the applying is further based on the one or more configuration parameters indicating the TAG (see “the TAG indication field may be included in the RAR. In such aspects, the corresponding TAG may be indicated using a reserved bit in the RAR PDSCH. For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106], wherein a single bit field is used for indicating the TAG, therefore, there is no need for the use of a TAG identity field).
Regrading claim 5, wherein: the first TAG is identified by a first TAG identity (see “each serving cell may be linked to a specific TAG by including a TAG identifier (sometimes referred to as a tag-Id) within the configured serving cell parameters (sometimes referred to as ServingCellConfig)” recited in paragraph [0090]).
Regarding claim 6, wherein the RAR comprises a 12-bit field indicating the TAC (see “For example, an initial TAC (sometimes referred to as TA) may be associated with a number of bits in the RAR (e.g., 12 bits, indicating a value within the range from 0 to 3846)” as recited in paragraph [0100]).
Regarding claim 10, wherein the first value is zero; the second value is one (see “For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106]); and a first TAG ID of the first TAG is lower than a second TAG ID of the second TAG see “the second cell 715 may be configured with two TAG identifiers, as shown by reference number 740 (e.g., Tag-Id1 and Tag-Id2)” recited in paragraph [0102], wherein Tag-Id1 is lower than Tag-Id2).
Regarding claim 11, a wireless device (see “UE” recited in paragraph [0123]) comprising:
one or more processors; and
memory (see Fig. 22 including memory 292 and processor 290) storing instructions that, when executed by the one or more processors, cause the wireless device to:
transmit a RA preamble of an RA procedure of the serving cell (see step 910 in Fig. 9 and paragraph [0123], wherein the UE transmits a random access preamble in a cell associated with multiple TAGs);
receive an RAR, corresponding to the RA preamble, wherein the RAR comprises: a TAC (see step 920 in Fig. 9, wherein the UE receives a RAR including a TAC in response to the preamble transmitted in step 910); and a bitfield indicating a binary value, wherein a first value of the binary value indicates the first TAG and a second value of the binary value indicates the second TAG; wherein the RAR does not comprise a TAG ID (see “the TAG indication field may be included in the RAR. In such aspects, the corresponding TAG may be indicated using a reserved bit in the RAR PDSCH. For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106], wherein a single bit field is used for indicating the TAG, therefore, there is no need for the use of a TAG identity field);
apply the TAC to the TAG, wherein the TAG is: the first TAG based on the binary value being set to the first value; and the second TAG based on the binary value being set to the second value (see step 940 in Fig. 9, wherein timing advance parameter being adjusted with the corresponding TAG based on the TAC; and see paragraph [0106], which describe the TAG indicator bit).
Regarding claim 14, wherein the applying is further based on the one or more configuration parameters indicating the TAG (see “the TAG indication field may be included in the RAR. In such aspects, the corresponding TAG may be indicated using a reserved bit in the RAR PDSCH. For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106], wherein a single bit field is used for indicating the TAG, therefore, there is no need for the use of a TAG identity field).
Regrading claim 15, wherein: the first TAG is identified by a first TAG identity; (see “each serving cell may be linked to a specific TAG by including a TAG identifier (sometimes referred to as a tag-Id) within the configured serving cell parameters (sometimes referred to as ServingCellConfig)” recited in paragraph [0090]).
Regarding claim 16, wherein the RAR comprises a 12-bit field indicating the TAC (see “For example, an initial TAC (sometimes referred to as TA) may be associated with a number of bits in the RAR (e.g., 12 bits, indicating a value within the range from 0 to 3846)” as recited in paragraph [0100]).
Regarding claim 20, wherein the first value is zero; the second value is one (see “For example, if the reserved bit is set to 0, then the corresponding TAG may be a first TAG of the multiple TAGs associated with the serving cell. And if the reserved bit is set to 1, then the corresponding TAG may be a second TAG of the multiple TAGs associated with the serving cell” recited in paragraph [0106]); and a first TAG ID of the first TAG is lower than a second TAG ID of the second TAG see “the second cell 715 may be configured with two TAG identifiers, as shown by reference number 740 (e.g., Tag-Id1 and Tag-Id2)” recited in paragraph [0102], wherein Tag-Id1 is lower than Tag-Id2).
Regarding claim 21, wherein the second TAG is identified by a second TAG identity (see “each serving cell may be linked to a specific TAG by including a TAG identifier (sometimes referred to as a tag-Id) within the configured serving cell parameters (sometimes referred to as ServingCellConfig)” recited in paragraph [0090]).
Regarding claim 23, wherein the second TAG is identified by a second TAG identity (see “each serving cell may be linked to a specific TAG by including a TAG identifier (sometimes referred to as a tag-Id) within the configured serving cell parameters (sometimes referred to as ServingCellConfig)” recited in paragraph [0090]).
Guo’512 does not disclose the following features: regarding claims 1 and 11, receiving, by a wireless device, RRC configuration parameters comprising: a first TAG index of a first TAG for a serving cell, wherein the first TAG is associated with a first uplink TCI state for uplink transmissions via an uplink BWP of the serving cell; a second TAG index of a first TAG for a serving cell, wherein the second TAG is associated with a second uplink TCI state for uplink transmissions via an uplink BWP of the serving cell; a TAG parameter used to determine a TAG of the first TAG and the second TAG, for applying a TAC comprised in the RAR; applying the TAC to the TAG wherein the TAG is the first TAG based on the TAG parameter; and the second TAG based on the TAG parameter; transmitting, via the serving cell, an uplink signal based on a TA value of the TAG; regarding claims 7 and 17, wherein transmitting the uplink signal is further based on an uplink TCI state associated with the TAG; regarding claims 8 and 18, wherein the uplink TCI state is: the first uplink TCI state in response to the TAG being the first TAG; regarding claims 22 and 24, wherein the uplink TCI state is the second uplink TCI state in response to the TAG being the second TAG.
Go discloses the following features.
Regarding claims 1 and 11, a method comprising:
receiving, by a wireless device (see “The UE may receive configuration information related to the serving cell (via/using TRP1 and/or TRP2) from the network side” recited in paragraph [0302]), RRC configuration parameters (see “The configuration information may be transmitted through a higher layer (e.g., RRC, MAC CE)” recited in paragraph [0309]) comprising:
a first TAG index of a first TAG for a serving cell (see “The configuration information may include information related to multiple TRP settings, multiple TAG settings for serving cells” recited in paragraph [0303] and “TAG index’ recited in paragraph [0305]), wherein the first TAG is associated with a first uplink TCI state (see “TCI state” recited in paragraph [0305]) for uplink transmissions via an uplink BWP of the serving cell (see “BWP” recited in paragraph [0305]; and see “multiple TAG settings for serving cells, and uplink transmission and reception” recited in paragraph [0303]; Fig. 15 also shows that the configuration information received by the UE in step S1201 being used for the uplink transmission in step S1203);
a second TAG index of a first TAG for a serving cell (see “The configuration information may include information related to multiple TRP settings, multiple TAG settings for serving cells” recited in paragraph [0303] and “TAG index’ recited in paragraph [0305]), wherein the second TAG is associated with a second uplink TCI state (see “TCI state” recited in paragraph [0305]) for uplink transmissions via an uplink BWP of the serving cell (see “BWP” recited in paragraph [0305]; and see “multiple TAG settings for serving cells, and uplink transmission and reception” recited in paragraph [0303]; Fig. 15 also shows that the configuration information received by the UE in step S1201 being used for the uplink transmission in step S1203); and
transmitting, via the serving cell, an uplink signal based on a TA value of the TAG (see step S1030 in Fig. 10 and paragraphs [0208]-[0209], wherein the UE performs uplink transmission based on the first indication information or the second indication information each having a TA value associated with a TAG).
Regarding claims 7 and 17, wherein transmitting the uplink signal is further based on an uplink TCI state associated with the TAG (see step S1030 in Fig. 10 and paragraphs [0208]-[0209], wherein the UE performs uplink transmission based on the first indication information or the second indication information each having a UL TCI state and TA value associated with a TAG).
Regarding claims 8 and 18, wherein the uplink TCI state is: the first uplink TCI state in response to the TAG being the first TAG (see “first UL TCI state…first TAG…second UL TCI state…second TAG” recited in paragraph [0209]).
Regarding claims 22 and 24, wherein the uplink TCI state is the second uplink TCI state in response to the TAG being the second TAG (see “first UL TCI state…first TAG…second UL TCI state…second TAG” recited in paragraph [0209]).
Fan discloses the following features.
Regarding claims 1 and 11, a TAG parameter used to determine a TAG (see “the SSB group is sent to the terminal by using an RRC configuration message… the association relationship between the SSB group and the TAG is sent to the terminal by using the RRC configuration message” recited in paragraph [0195]), of the first TAG and the second TAG, for applying a TAC comprised in the RAR (see “The terminal determines, based on the SSB corresponding to the RAR message, the TAG corresponding to the initial TA value indicated in the RAR message” recited in paragraph [0195]; and paragraph [0193] shows that the RAR includes a timing advance command);
applying the TAC to the TAG wherein the TAG is the first TAG based on the TAG parameter; and the second TAG based on the TAG parameter (see “a TAG corresponding to an initial TA value indicated by the timing advance command field in the RAR message is determined by using an SSB corresponding to the RAR message” recited in paragraph [0194] and see “The terminal determines, based on the SSB corresponding to the RAR message, the TAG corresponding to the initial TA value indicated in the RAR message” recited in paragraph [0195]).
It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Guo ‘512 using features, as taught by Go and Fan, in order to configure uplink transmission operation of a terminal for a serving cell serving multiple timing advance groups (see paragraphs [0201]-[0203] of Go) and in order to reduce the transmission overhead in a RAR message (see paragraph [0194] of Fan).
Claim(s) 9 and 19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Guo ‘512, Go and Fan as applied to claims 1-2 and 11-12 above, and further in view of Comsa (US 2024/0188015 A1).
Guo ‘512, Go and Fan disclose the features as shown above.
Guo ‘512 does not disclose the following features: regarding claims 9 and 19, wherein transmitting the uplink signal with a transmit power that is determined based on the uplink TCI state.
Comsa discloses the following features.
Regarding claims 9 and 19, wherein transmitting the uplink signal with a transmit power that is determined based on the uplink TCI state (see “The WTRU may further set the power of this PUCCH based on the first or second set of power control parameters for PUCCH configured for the identified enhanced TCI state” recited in paragraph [0190]).
It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Guo ‘512, Go and Fan using features, as taught by Comsa, in order to allow a WTRU to communicate with multiple TRPs simultaneously (see paragraph [0090] of Comsa).
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 JUTAI KAO whose telephone number is (571)272-9719. The examiner can normally be reached Monday-Friday 8:00-17:00 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, Kwang Yao can be reached at (571)272-3182. 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.
/JUTAI KAO/Primary Examiner, Art Unit 2473