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 .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 06/07/2024 was filed with the instant application for consideration. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1, 3-9, 11, 13, 15-16, 18-24, 26, 28-30 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Ly et al. (US 2018/0109976 A1), hereinafter, “Ly”.
Regarding claim 1, Ly discloses: An apparatus for wireless communication at a user equipment (UE) (Ly: fig 13, wireless device 1305, para [0065], where, an apparatus for wireless communication is described, and para [0168]), comprising: a memory; and one or more processors, coupled to the memory (Ly: fig 13, wireless device 1305, para [0066], where, “The apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory” and para [0168])), configured to: transmit, to a network entity, multiple physical random access channel (PRACH) transmissions based at least in part on a PRACH slot frequency hopping (Ly: fig 9, First PRACH transmission 935the UE and 11, par [0161]-[0162], where, “a resource structure 1100 for RACH procedures using multiple PRACH transmissions in accordance with one or more aspects of the present disclosure. For example, the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”), and
receive, from the network entity, a response based at least in part on the multiple PRACH transmissions associated with the PRACH slot frequency hopping (Ly: fig 11, para [0148], where, the UE115-b, receive the RACH response message 945, further fig 11 and par [0161]-[0162]).
Regarding claim 13, the claim includes features identical to the subject matter mentioned in the rejection to claim 1 above. The claims are mere reformulation of claim 1 in order to define the wireless communication apparatus at a network entity, and the rejection to claim 1 is applied hereto.
Regarding claim 16, the claim includes features identical to the subject matter mentioned in the rejection to claim 1 above. The claims are mere reformulation of claim 1 in order to define the wireless communication method for user equipment, and the rejection to claim 1 is applied hereto.
Regarding claim 28, the claim includes features identical to the subject matter mentioned in the rejection to claim 1 above. The claims are mere reformulation of claim 1 in order to define the corresponding the wireless communication method for a network entity, and the rejection to claim 1 is applied hereto.
Regarding claims 3 and 18, Ly discloses: 3. The apparatus of claim 1, wherein the one or more processors are further configured to: transmit, to the network entity, capability signaling indicating that the UE is capable of performing the multiple PRACH transmissions with the PRACH slot frequency hopping (Ly: fig 15-16, para [0194], where, “Software 1530 may include code to implement aspects of the present disclosure, including code to support RACH procedures using multiple PRACH transmissions….[0196], the wireless device may include a single antenna 1540. However, in some cases the device may have more than one antenna 1540, which may be capable of concurrently transmitting or receiving multiple wireless transmissions”); and transmit the multiple PRACH transmissions based at least in part on the capability signaling (Ly: fig 15-16, para [0196], the wireless device may include a single antenna 1540. However, in some cases the device may have more than one antenna 1540, which may be capable of concurrently transmitting or receiving multiple wireless transmissions”).
Regarding claims 4 and 19, Ly discloses: wherein the one or more processors are configured to transmit the multiple PRACH transmissions based at least in part on using same spatial domain filters or same transmit beams (Ly: fig 11, para [0161], where, “the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”).
Regarding claims 5 and 20, Ly discloses: wherein the one or more processors are configured to transmit the multiple PRACH transmissions based at least in part on using different spatial domain filters or different transmit beams (Ly: fig 11, para [0161], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot, but the frequency resources used may be different”).
Regarding claims 6 and 21, Ly discloses: wherein the multiple PRACH transmissions are associated with a common PRACH slot frequency hopping flag indicating that PRACH slot frequency hopping is enabled (Ly: fig 11, para [0161], where, “the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”).
Regarding claims 7 and 22, Ly discloses: wherein the multiple PRACH transmissions are each associated with a separate PRACH slot frequency hopping flag that indicates whether PRACH slot frequency hopping is enabled of (Ly: fig 9, para [0143], where, “multiple time-separate slots may be used to transmit the multiple PRACH transmissions or multiple frequency sub-bands may be used to transmit the multiple PRACH transmissions).
Regarding claims 8 and 23, Ly discloses: wherein the one or more processors are further configured to: receive, from the network entity, a PRACH slot frequency hopping configuration of (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”); and transmit the multiple PRACH transmissions based at least in part on the PRACH slot frequency hopping configuration of (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”).
Regarding claims 9 and 24, Ly discloses: The apparatus of claim 8, wherein the PRACH slot frequency hopping configuration indicates one or more of (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”): a frequency hop offset in terms of a quantity of resource blocks in a PRACH occasion or a quantity of PRACH occasions in a PRACH slot (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”). [[; and a quantity of hops based at least in part on a quantity of synchronization signal blocks associated with the PRACH occasion and a quantity of frequency division multiplexed PRACH occasions. ]]
Regarding claims 11, 26 and 29, Ly discloses: wherein the PRACH slot frequency hopping is an inter-PRACH slot frequency hopping (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”).
Regarding claims 15 and 30, Ly discloses: wherein the one or more processors are further configured to: receive, from the UE, one or more of capability signaling or a PRACH slot frequency hopping configuration (Ly: fig 11, para [0161]-[0162], where, “the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”); and receive the multiple PRACH transmissions based at least in part on the one or more of the capability signaling or the PRACH slot frequency hopping configuration (Ly: fig 15, para [0196], where, “antenna 1540, which may be capable of concurrently transmitting or receiving multiple wireless transmissions”).
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 text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action.
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.
Claims 2, 10,12, 14, 17, 25 and 27 are rejected under 35 U.S.C. 103 as being unpatentable over Ly et al. (US 2018/0109976 A1), hereinafter, “Ly” in view of Rune et al (US 2023/0292371 A1), hereinafter, “Rune”.
Regarding claims 2, 14, and 17, Ly discloses: wherein the PRACH slot frequency hopping (Ly: fig 11, para [0161], where, “the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”),
However, Ly does not explicitly teach: the PRACH slot frequency hopping is an intra-PRACH slot frequency hopping.
Rune teach: the PRACH slot frequency hopping is an intra-PRACH slot frequency hopping (Rune: TABLE-US-0025: where, “See Table 8.3-1 in 38.213 [13]. msgA-IntraSlotFrequencyHopping Intra-slot frequency hopping per PUSCH occasion”).
Therefore, it would have been obvious to one of ordinary skilled in the art before the effective filing date of the invention to use “the PRACH slot frequency hopping is an intra-PRACH slot frequency hopping” as taught by Rune into Ly in order to be able to detect and demodulate the PUSCH transmission (Rune: para [0022]).
Regarding claims 10 and 25, Ly modified by Rune disclose: wherein the PRACH slot frequency hopping configuration is: common for multiple PRACH transmissions using same spatial domain filters (Ly: fig 11, para [0162], where, “multiple PRACH transmissions may be sent in the first slot using certain frequency resources and the same multiple PRACH transmissions may also be sent in the second slot”); separate for multiple PRACH transmissions using same spatial domain filters (Rune: para [0164], where, “the common TA, which refers to the common component of propagation delay shared by all UEs within the coverage of same satellite beam/cell, is broadcasted by the network per satellite beam/cell”); common for multiple PRACH transmissions using different spatial domain filters; or separate for multiple PRACH transmissions using different spatial domain filters.
Regarding claims 12 and 27, Ly modified by Rune disclose: wherein the PRACH slot frequency hopping is based at least in part on one or more of (Ly: fig 11, para [0161]-[0162], where, “the resource structure 1100 may be configured to send PRACH transmissions using frequency hopping in the same slot”): a system frame number (Rune: par a[0027], where, “The values in the column “subframe number” indicate which subframes are configured with PRACH occasion”), a slot number, or an association period associated with the multiple PRACH transmissions.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NIZAM U AHMED whose telephone number is (571)272-9561. The examiner can normally be reached Mon-Fry, 7:00 AM-6:00 PM PST.
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, Huy Vu can be reached at 571-272-3155. 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.
/NIZAM U AHMED/Primary Examiner, Art Unit 2461
Prosecution Insights