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
Applicant's amendment filed on 11/20/2025 has been entered. Claims 1, 3-4, 6, 10-13 and 21-22 have been amended. No claims have been added or cancelled. Claims 1, 3-18 and 21-22 are still pending in this application, with claims 1, 10 and 21, being independent.
Response to Arguments
Applicant’s arguments with respect to claim(s) 1, 3-18 and 21-22 have been considered but are moot based on new grounds of rejections.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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.
Claim(s) 1, 3, 5, 7, 9-12, 14, 16, 18 and 21-22 are rejected under 35 U.S.C. 103 as being unpatentable over Lu et al. (US 2023/0180273; hereinafter Lu) in view of Lei et al. (US 2021/0051727; hereinafter Lei).
Regarding claim 1, Lu shows a method (Figure 3A shows a method performed in part by a network device of Figure 13.) for configuring a random access parameter, performed by a network device, the method comprising:
determining a physical uplink control channel (PUCCH) configuration parameter, wherein the PUCCH configuration parameter comprises a first PUCCH configuration parameter of performing hybrid automatic repeat request feedback of a fourth message (Msg.4 HARQ feedback) in a random access process for a first-type terminal (Figure 3A; Par. 0152-0154; the network device transmits PUCCH configuration information to perform HARQ feedback on msg4 or MsgB, and the terminals perform HARQ feedback on msg4 or MsgB by using the PUCCH configuration. PUCCH configuration information includes first physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the unconventional terminal transmitted via a random access response (RAR).) and a second PUCCH configuration parameter of performing Msg.4 HARQ feedback in a random access process for a second-type terminal (Figure 3A; Par. 0152-0154; noted the second random access configuration information includes second physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the conventional terminal transmitted via a random access response (RAR).), and a capability of the first-type terminal is different from a capability of the second-type terminal (Par. 0009; the terminal equipment supported by Rel-15 and Rel-16 communication systems are also referred to as conventional terminals, and the above terminal equipment with medium and low capabilities are also referred to as unconventional terminals.);
wherein the first PUCCH configuration parameter is partially different from the second PUCCH configuration parameter (Par. 0091, 0110; RACH configurations for unconventional and conventional terminals have some common configurations and also, different configurations.).
Lu shows all of the elements including the first PUCCH configuration parameter and the second PUCCH configuration parameter, as discussed above. Lu does not specifically show at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Lei. Specifically, Lei shows at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different (Par. 0110; UE may receive different PUCCH resource indications via system information wherein each of the PUCCH resource indications may be partially or wholly different from the others.).
In view of the above, having the system of Lu, then given the well-established teaching of Lei, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Lei, in order to provide motivation to handle random access procedures in a manner that is efficient and reduces signaling overhead, as well as accommodates different connection states and flexible channel structure (Par. 0005 of Lei).
Regarding claim 3, modified Lu shows wherein at least one of the following parameters in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different (Examiner elects this claim limitation for prosecution. Lu: Figure 3A; Par. 0091, 0152-0154; noted PUCCH configuration information includes first physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the unconventional terminal transmitted via a random access response (RAR) and the second random access configuration information includes second physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the conventional terminal transmitted via a random access response (RAR).):
the PUCCH supporting intra-slot frequency hopping (FH) or the PUCCH not supporting intra-slot FH;
a PRB position where the PUCCH supports intra-slot FH; or
an FH width when the PUCCH supporting intra-slot FH.
Regarding claim 5, modified Lu shows wherein the PUCCH configuration parameter comprises a common PUCCH configuration parameter for the first-type terminal and the second-type terminal (Lu: Par. 0110; RACH configurations for unconventional and conventional terminals have some common configurations.).
Regarding claim 7, modified Lu shows sending the PUCCH configuration parameter (Lu: Par. 0152-0154; transmitting the PUCCH configuration information.).
Regarding claim 9, modified Lu shows receiving a terminal capability reported by a terminal, wherein the terminal capability represents that the terminal is the first-type terminal or the second-type terminal (Lu: Figure 7-7A; Par. 0170; the network device receives the unconventional capability indication information, which is used to indicate that the terminal is an unconventional terminal. Therefore, the network device is able to identify the unconventional terminal according to the unconventional capability indication information.); and
determining a resource for the terminal to perform the Msg.4 HARQ feedback according to the terminal capability (Lu: Figures 7-7Al Par. 0166, 0170; the network device is able to identify the unconventional terminal according to the unconventional capability indication information, so that it may perform data transmission with the unconventional terminal in a manner matching the performance of the unconventional terminal.).
Regarding claim 10, Lu shows a method (Figure 3A shows a method performed in part by a terminal of Figure 14.) for configuring a random access parameter, performed by a terminal, the method comprising:
determining a PUCCH configuration parameter, wherein the PUCCH configuration parameter comprises a first PUCCH configuration parameter of performing hybrid automatic repeat request feedback of a fourth message (Msg.4 HARQ feedback) in a random access process for a first-type terminal (Figure 3A; Par. 0152-0154; the network device transmits PUCCH configuration information to perform HARQ feedback on msg4 or MsgB, and the terminals perform HARQ feedback on msg4 or MsgB by using the PUCCH configuration. PUCCH configuration information includes first physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the unconventional terminal transmitted via a random access response (RAR).) and a second PUCCH configuration parameter of performing Msg.4 HARQ feedback in a random access process for a second-type terminal (Figure 3A; Par. 0152-0154; noted the second random access configuration information includes second physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the conventional terminal transmitted via a random access response (RAR).) and a capability of the first-type terminal is different from a capability of the second-type terminal (Par. 0009; the terminal equipment supported by Rel-15 and Rel-16 communication systems are also referred to as conventional terminals, and the above terminal equipment with medium and low capabilities are also referred to as unconventional terminals.); and
determining a resource of performing the Msg.4 HARQ feedback in the random access process according to the PUCCH configuration parameter (Figure 3A; Par. 0154-0156; a PUCCH resource indicator for performing HARQ feedback on msg4 by the unconventional terminal is added to the RAR or fallbackRAR of msg2. After the random access is successful (for example, the contention resolution is successful), the unconventional terminal instructs the physical layer (MAC) to generate HARQ feedback, and the physical layer uses a PUCCH resource for the unconventional terminal to perform HARQ feedback on msg4.);
wherein the first PUCCH configuration parameter is partially different from the second PUCCH configuration parameter (Par. 0091, 0110; RACH configurations for unconventional and conventional terminals have some common configurations and also, different configurations.).
Lu shows all of the elements including the first PUCCH configuration parameter and the second PUCCH configuration parameter, as discussed above. Lu does not specifically show at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Lei. Specifically, Lei shows at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different (Par. 0110; UE may receive different PUCCH resource indications via system information wherein each of the PUCCH resource indications may be partially or wholly different from the others.).
In view of the above, having the system of Lu, then given the well-established teaching of Lei, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Lei, in order to provide motivation to handle random access procedures in a manner that is efficient and reduces signaling overhead, as well as accommodates different connection states and flexible channel structure (Par. 0005 of Lei).
Regarding claim 11, modified Lu shows determining a terminal type, wherein the terminal is the first-type terminal or the second-type terminal (Par. 0088; A resource location under the first random access configuration used by the unconventional terminal may be different from a location of a second random access resource used by the conventional terminal.); and
determining the PUCCH configuration parameter according to the terminal type (Par. 0088; 0199-200; a message is transmitted to the network device according to the first random access configuration information; and data transmission is performed with the network device by using an unconventional transmission mode.);
Regarding claims 12, 14, 16 and 18, these claims are rejected based on the same reasoning as presented in the rejection of claims 3, 5, 7 and 9, respectively.
Regarding claims 21, Lu shows a device (Figure 3A shows a method performed in part by a network device of Figure 13.) for configuring a random access parameter, comprising:
a processor; and a memory for storing instructions executable by the processor (Figure 13 shows the network device includes a program stored in memory and executed by a processor to perform the disclosed method.); wherein the processor is configured to:
determine a physical uplink control channel (PUCCH) configuration parameter, wherein the PUCCH configuration parameter comprises a first PUCCH configuration parameter of performing hybrid automatic repeat request feedback of a fourth message (Msg.4 HARQ feedback) in a random access process (Figure 3A; Par. 0152-0154; the network device transmits PUCCH configuration information to perform HARQ feedback on msg4 or MsgB, and the terminals perform HARQ feedback on msg4 or MsgB by using the PUCCH configuration.) for a first-type terminal (Figure 3A; Par. 0152-0154; the network device transmits PUCCH configuration information to perform HARQ feedback on msg4 or MsgB, and the terminals perform HARQ feedback on msg4 or MsgB by using the PUCCH configuration. PUCCH configuration information includes first physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the unconventional terminal transmitted via a random access response (RAR).) and a second PUCCH configuration parameter of performing Msg.4 HARQ feedback in a random access process for a second-type terminal (Figure 3A; Par. 0152-0154; noted the second random access configuration information includes second physical uplink control channel (PUCCH) configuration information for performing HARQ feedback on the fourth message (msg4) by the conventional terminal transmitted via a random access response (RAR).), and a capability of the first-type terminal is different from a capability of the second-type terminal (Par. 0009; the terminal equipments supported by Rel-15 and Rel-16 communication systems are also referred to as conventional terminals, and the above terminal equipments with medium and low capabilities are also referred to as unconventional terminals.); and
send the PUCCH configuration parameter (Figure 2A; Par. 0156; sending the PUCCH configuration parameter is transmitted.);
wherein the first PUCCH configuration parameter is partially different from the second PUCCH configuration parameter (Par. 0091, 0110; RACH configurations for unconventional and conventional terminals have some common configurations and also, different configurations.).
Lu shows all of the elements including the first PUCCH configuration parameter and the second PUCCH configuration parameter, as discussed above. Lu does not specifically show at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Lei. Specifically, Lei shows at least one of a PUCCH or a PUCCH format in the first PUCCH configuration parameter and the second PUCCH configuration parameter is different (Par. 0110; UE may receive different PUCCH resource indications via system information wherein each of the PUCCH resource indications may be partially or wholly different from the others.).
In view of the above, having the system of Lu, then given the well-established teaching of Lei, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Lei, in order to provide motivation to handle random access procedures in a manner that is efficient and reduces signaling overhead, as well as accommodates different connection states and flexible channel structure (Par. 0005 of Lei).
Regarding claim 22, Lu shows a device (Figure 3A shows a method performing in part by a terminal of Figure 14.) for configuring a random access parameter, comprising:
a processor; and a memory for storing instructions executable by the processor ; wherein the processor is configured to perform the method of claim 10 (Figure 14 shows the terminal includes a program stored in memory and executed by a processor to perform the disclosed method.).
Claim(s) 4, 6, 13 and 15 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lu in view of Lei and Awad et al. (US Pat. 11,363,605; hereinafter Awad).
Regarding claim 4, modified Lu shows all of the elements including wherein the capability of the first-type terminal is stronger than the capability of the second-type terminal (Par. 0009; the terminal equipments supported by Rel-15 and Rel-16 communication systems are also referred to as conventional terminals, and the above terminal equipments with medium and low capabilities are also referred to as unconventional terminals.).
Modified Lu does not specifically show the method further comprising at least one of: the first PUCCH configuration parameter comprising a configuration parameter supporting intra-slot FH, and the second PUCCH configuration parameter comprising a configuration parameter not supporting intra-slot FH; or an intra-slot FH width configured in the first PUCCH configuration parameter being greater than an intra-slot FH width configured in the second PUCCH configuration parameter.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Awad. Specifically, Awad shows the method further comprising at least one of:
the first PUCCH configuration parameter comprising a configuration parameter supporting intra-slot FH, and the second PUCCH configuration parameter comprising a configuration parameter not supporting intra-slot FH (Figure 8; col. 12, lines 18-40; t will be appreciated that whilst in the legacy PUCCH area slot hopping may be supported (for frequency diversity), the MTC specific PUCCH is provided without slot hopping enabled in order to ensure compatibility with Rel-13 reduced bandwidth MTC devices (and/or similar). Therefore, regardless whether or not PUCCH slot hopping is enabled in the cell for legacy devices, the PUCCH resources allocated to MTC devices remain within the same resource block (and/or alternate only within the same 1.4 MHz bandwidth) in both slots.); or
an intra-slot FH width configured in the first PUCCH configuration parameter being greater than an intra-slot FH width configured in the second PUCCH configuration parameter
In view of the above, having the system of Lu, then given the well-established teaching of Awad, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Awad, in order to provide motivation to improve the MTC device's overall power consumption (col. 13, lines 15-18 of Awad).
Regarding claim 6, modified Lu shows all of the elements including wherein the capability of the first-type terminal is stronger than the capability of the second-type terminal (Par. 0009; the terminal equipment supported by Rel-15 and Rel-16 communication systems are also referred to as conventional terminals, and the above terminal equipment with medium and low capabilities are also referred to as unconventional terminals.).
Lu does not specifically show the PUCCH configuration parameter comprises one or a combination of: the PUCCH not supporting intra-slot FH; and the PUCCH supporting intra-slot FH and an intra-slot FH width being within a bandwidth range supported by the second-type terminal.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Awad. Specifically, Awad shows the PUCCH configuration parameter comprises one or a combination of: the PUCCH not supporting intra-slot FH; and PUCCH supporting intra-slot FH (Figure 8; col. 12, lines 18-40; t will be appreciated that whilst in the legacy PUCCH area slot hopping may be supported (for frequency diversity), the MTC specific PUCCH is provided without slot hopping enabled in order to ensure compatibility with Rel-13 reduced bandwidth MTC devices (and/or similar). Therefore, regardless whether or not PUCCH slot hopping is enabled in the cell for legacy devices, the PUCCH resources allocated to MTC devices remain within the same resource block (and/or alternate only within the same 1.4 MHz bandwidth) in both slots.); and
an intra-slot FH width being within a bandwidth range supported by the second-type terminal.
In view of the above, having the system of Lu, then given the well-established teaching of Awad, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Awad, in order to provide motivation to improve the MTC device's overall power consumption (col. 13, lines 15-18 of Awad).
Regarding claims 13 and 15, these claims are rejected based on the same reasoning as presented in the rejection of claims 4 and 6, respectively.
Claim(s) 8 and 17 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lu in view of Lei and Yang et al. (US 2019/0297618; hereinafter Yang).
Regarding claim 8, modified Lu shows all of the elements except wherein the PUCCH configuration parameter is carried in remaining minimum system information (RMSI).
However, the above-mentioned claim limitations are well-established in the art as evidenced by Yang. Specifically, Yang shows wherein the PUCCH configuration parameter is carried in remaining minimum system information (RMSI) (Par. 0140; when the PUCCH resource set is indicated by an RMSI bit (as system information), the UE may interpret the unused bit(s) (in the DCI) as indicating an additional offset for a state indicated by the RMSI bit. That is, the base station may change the PUCCH resource set through the unused bit(s).).
In view of the above, having the system of Lu, then given the well-established teaching of Yang, it would have been obvious before the effective filing date of the claimed invention to modify the system of Lu as taught by Yang, in order to provide motivation to improve the MTC device's overall power consumption (col. 13, lines 15-18 of Yang).
Regarding claim 17, this claim is rejected based on the same reasoning as presented in the rejection of claim 8.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 20210037605 A1 - Systems and methods for interlace PUCCH transmission in 5G networks are described. The gNB sends an RRC message to a UE. The RRC message provides one or more PUCCH interlace allocations within a BW. Each PUCCH interlace allocation has a PUCCH format for each PUCCH interlace. Each PUCCH format contains a different PUCCH interlace index. The UE sends a PUCCH interlace in the BWP based on the PUCCH interlace allocation. A PUCCH in the allocated PUCCH interlace has a cyclic shift that is dependent on a resource block number in the allocated PUCCH interlace within the BWP.
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 REDENTOR M PASIA whose telephone number is (571)272-9745. The examiner can normally be reached Mondays-Thursdays - 5am-245pm and Fridays 5am-330pm.
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.
/REDENTOR PASIA/Primary Examiner, Art Unit 2413