RESOURCE CONFIGURATION METHOD, DEVICE, AND STORAGE MEDIUM

§102 §103 §DOUBLEPATENT

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 . DETAILED ACTION In the amendment filed September 8, 2026, claims 1, 7, 12, and 17 are amended, claims 4, 10 and 19 are cancelled, new claims 21-23 are added and claims 1-3, 5-9, 11-18, and 20-23 are currently pending for examination. Response to Arguments Regarding Double Patenting applicant’s arguments, see section III, page 10 and 11, filed September 08, 2026, have been fully considered and are not persuasive. The applicant argued that, see section III, page 10 and 11, “It is evident that claim 10 of the instant application relates to the mapping order from PRACH resources to PUSCH resources, while claim 11 of US Patent No. 12,127,268 relates to the mapping order from PUSCH resources to PRACH resources. Therefore, claim 10 of the instant application is fundamentally different from claim 11 of US Patent No. 12,127,268. Moreover, as acknowledged in section 13 (on page 17) of the Office Action, the cited reference documents fail to disclose the features of claim 10 of the instant application. At present, independent claims 1, 7, 12 and 17 have been amended to incorporate the limitations of claim 10 (as discussed below in the response to 35 U.S.C. § 102 & § 103). Therefore, the current set of amended claims is patentably distinct from the claims of US Patent No. 12,127,268. Accordingly, Applicant respectfully requests withdrawal of the rejections of claims”. In response to applicant's argument, the examiner respectfully disagrees with the argument above. Per instant published specification, see paragraphs, “[0083] In some implementations, for the PRACH resource corresponding to the preamble, the mapping rule between the PUSCH resource and the PRACH resource includes that a dimension of the mapping between the PUSCH resource and the PRACH resource includes at least one of the following: preamble indices within a RACH occasion, PRACH resource numbers of frequency division multiplexed RACH occasions, time resource indices of time division multiplexed RACH occasions within a PRACH slot, and indices of PRACH slots. The RACH occasion refers to time domain resources and frequency domain resources for transmitting the preamble.”, “[0089] The mapping rule between the PRACH resources and the PUSCH resources includes that the PRACH resources are mapped to the PUSCH resources based on the following priority order: a. an order of PUSCH port indices in a PUSCH resource; b. an order of PUSCH resource numbers of frequency division multiplexed PUSCH resource blocks; and c. an order of time resource indices of time division multiplexed PUSCH resource blocks.” and “0092] For example, when the PRACH resources are mapped to the PUSCH resources based on the following priority order, the PUSCH resources are mapped to the PRACH resources first based on the order of the PUSCH port indices in one PUSCH resource, after the PUSCH port indices in one PUSCH resource have been used, the PUSCH resources are mapped to the PRACH resources based on the order of the PUSCH resource numbers of the frequency division multiplexed PUSCH resource blocks, and after the PUSCH resource numbers have been used, the PUSCH resources are mapped to the PRACH resources based on the order of the time resource indices of the time division multiplexed PUSCH resource blocks.”, “[0134] Correspondingly, the mapping rule between the PRACH resources and the PUSCH resources includes that the PRACH resources are mapped to the PUSCH resources based on the following priority order: an order of the PUSCH port indices in one PUSCH resource; an order of the PUSCH resource numbers of the frequency division multiplexed PUSCH resource blocks; and an order of the time resource indices of the time division multiplexed PUSCH resource blocks.”, see also para. 0094 and 0096, none of these paragraphs disclose the amended limitation. Application seems to be arguing new matter. Clarification is required. Regarding claim objections applicant’s arguments, see page 12 Section V, filed September 8, 2026, with respect to claims 1, 7, 12 and 17 have been fully considered and are persuasive. The claim objections of claims 1-3, 5-9, 11-18, and 20 have been withdrawn. Regarding 35 U.S.C. 102 and 103 applicant’s arguments, see page 12 Section VI, filed September 8, 2026,, with respect to claims 1, 7, 12 and 17 have been fully considered and are not persuasive. See Section 3 above and below rejections. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the claims at issue are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a nonstatutory double patenting ground provided the reference application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The USPTO internet Web site contains terminal disclaimer forms which may be used. Please visit http://www.uspto.gov/forms/. The filing date of the application will determine what form should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp. Claims 1-3, 5-9, 11-18 and 20 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1-11, 13-20, and 22 of US Patent 12,127,268. Note that the applicant filing of the continuing application is voluntary and not the direct, unmodified result of restriction requirement under 35 U.S.C. 121 (i.e. without a restriction requirement by the examiner) and the claims of the second application are drawn to the “same invention” as the first application or patent. Moreover, although the conflicting claims are not identical, they are not patentably distinct from each other because claims 1-3, 5-9, 11-18 and 20 of the instant application merely broadens the scope of claims 1-11, 13-20, and 22 of US Patent 12,127,268 by eliminating the elements and their functions of the claims, and claims 1-3, 5-9, 11-18 and 20 of this instant application is therefore and obvious variant thereof. Instant Application 18888125 US Patent No.:12,127,268 1. A method for communication, comprising: sending, by a terminal device, a preamble of a Message A (MsgA); and sending, by the terminal device according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port. wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c). 1. A method for communication, comprising: sending, by a terminal device, a preamble of a Message A (MsgA); and sending, by the terminal device according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: first in an increasing order of preamble indices within each PRACH occasion; secondly in an increasing order of PRACH resource numbers for frequency division multiplexed PRACH occasions; and then in an increasing order of time resource indices for time division multiplexed PRACH occasions within a PRACH slot. 2. The method according to claim 1, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port. 2. The method according to claim 1, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 3. The method according to claim 1, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 3. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 4. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 5. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks. 5. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks. 6. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources is a preset rule. 6. The method according to claim 1, wherein the mapping rule between the PRACH resources and the PUSCH resources is a preset rule. 7. A method for communication, comprising: receiving, by a network device, a preamble of a Message A (MsgA); and receiving, by the network device, a physical uplink shared channel (PUSCH) of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein correspondence between the preamble of the MsgA and the PUSCH resource follows a mapping rule between physical random access channel (PRACH) resources and PUSCH resources, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH and one PUSCH Demodulation Reference Signal (DMRSI port wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c) 7. A method for communication, comprising: receiving, by a network device, a preamble of a Message A (MsgA); and receiving, by the network device, a physical uplink shared channel (PUSCH) of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein correspondence between the preamble of the MsgA and the PUSCH resource follows a mapping rule between physical random access channel (PRACH) resources and PUSCH resources, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: first in an increasing order of preamble indices within each PRACH occasion; secondly in an increasing order of PRACH resource numbers for frequency division multiplexed PRACH occasions; and then in an increasing order of time resource indices for time division multiplexed PRACH occasions within a PRACH slot. 8. The method according to claim 7, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port. 8. The method according to claim 7, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 9. The method according to claim 7, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 9. The method according to claim 7, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 10. The method according to claim 7, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 11. The method according to claim 7, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: (d) in an increasing order of PUSCH resource numbers for multiple PUSCH resource blocks on a same time resource; (e) in an increasing order of PUSCH DMRS port indices; and (f) in an increasing order of time resource indices for multiple time resources on a slot, wherein a priority of the order in (d) is higher than a priority of the order in (e), and the priority of the order in (e) is higher than a priority of the order in (f). 11. The method according to claim 7, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: (d) in an increasing order of PUSCH resource numbers for multiple PUSCH resource blocks on a same time resource; (e) in an increasing order of PUSCH DMRS port indices; and (f) in an increasing order of time resource indices for multiple time resources on a slot, wherein a priority of the order in (d) is higher than a priority of the order in (e), and the priority of the order in (e) is higher than a priority of the order in (f). 12. A terminal device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program to cause the terminal device to perform steps of: sending a preamble of a Message A (MsgA); and sending, according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH Demodulation Reference Signal (DMRS) port wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order:(a) in an increasing order of preamble indices within a same PRACH occasion;(b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and(c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b),and the priority of the order in (b) is higher than a priority of the order in (c). 13. A terminal device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program to cause the terminal device to perform steps of: sending a preamble of a Message A (MsgA); and sending, according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: first in an increasing order of preamble indices within each PRACH occasion; secondly in an increasing order of PRACH resource numbers for frequency division multiplexed PRACH occasions; and then in an increasing order of time resource indices for time division multiplexed PRACH occasions within a PRACH slot. 14. The terminal device according to claim 13, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port. 13. The terminal device according to claim 12, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 15. The terminal device according to claim 13, wherein one PRACH resource comprises: one preamble on one PRACH occasion. 14. The terminal device according to claim 12, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 16. The terminal device according to claim 13, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 15. The terminal device according to claim 12, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises: for preambles in different time resources, mapping of the preamble in a time resource with a small time resource index is prioritized; for preambles in different PRACH occasions and in a same time resource, mapping of the preamble in a PRACH occasion with a small PRACH occasion index is prioritized; and for preambles in a same PRACH occasion and in a same time resource, mapping of the preamble with a small preamble index is prioritized. 17. The terminal device according to claim 13, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises: for preambles in different time resources, mapping of the preamble in a time resource with a small time resource index is prioritized; for preambles in different PRACH occasions and in a same time resource, mapping of the preamble in a PRACH occasion with a small PRACH occasion index is prioritized; and for preambles in a same PRACH occasion and in a same time resource, mapping of the preamble with a small preamble index is prioritized. 16. The terminal device according to claim 12, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises: for PUSCH resources in different time resources, mapping of the PUSCH resource in a time resource with a small time resource index is prioritized; for PUSCH resources with different PUSCH DMRS ports in a same time resource, mapping of the PUSCH resource with a small PUSCH DMRS port index is prioritized; and for PUSCH resources with a same PUSCH DMRS port index and different PUSCH resource numbers of PUSCH time resource blocks in a same time resource, mapping of the PUSCH resource with a small PUSCH resource number is prioritized. 18. The terminal device according to claim 13, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises: for PUSCH resources in different time resources, mapping of the PUSCH resource in a time resource with a small time resource index is prioritized; for PUSCH resources with different PUSCH DMRS ports in a same time resource, mapping of the PUSCH resource with a small PUSCH DMRS port index is prioritized; and for PUSCH resources with a same PUSCH DMRS port index and different PUSCH resource numbers of PUSCH time resource blocks in a same time resource, mapping of the PUSCH resource with a small PUSCH resource number is prioritized. 17. A network device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program to cause the network device to perform steps of: receiving a preamble of a Message A (MsgA); and receiving a physical uplink shared channel (PUSCH) of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein correspondence between the preamble of the MsgA and PUSCH resource follows a mapping rule between physical random access channel (PRACH) resources and PUSCH resources, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH Demodulation Reference Signal (DMRS1 port, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order:(a) in an increasing order of preamble indices within a same PRACH occasion;(b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and(c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b),and the priority of the order in (b) is higher than a priority of the order in (c). 19. A network device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program to cause the network device to perform steps of: receiving a preamble of a Message A (MsgA); and receiving a physical uplink shared channel (PUSCH) of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA, wherein correspondence between the preamble of the MsgA and PUSCH resource follows a mapping rule between physical random access channel (PRACH) resources and PUSCH resources, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: first in an increasing order of preamble indices within each PRACH occasion; secondly in an increasing order of PRACH resource numbers for frequency division multiplexed PRACH occasions; and then in an increasing order of time resource indices for time division multiplexed PRACH occasions within a PRACH slot. 20. The network device according to claim 19, wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port. 18. The network device according to claim 17, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 22. The network device according to claim 19, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource. 20. The network device according to claim 17, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks. 23. The network device according to claim 19, wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks. Although the conflicting claims are not identical, they are not patentable distinct from each other. Thus, in view of the above, it is clear that the conflicting claims are not patentably distinct from each other because claims 1-3, 5-9, 11-18 and 20 of the instant application are of the same scope of the claims 1-11, 13-20, and 22 US Patent 12, 127,268. Notice re prior art available under both pre-AIA and AIA 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 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. 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)(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. Claim(s) 1-3, 5-9 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by OPPO (On Channel Structure for 2-step RACH, R-1902747, 03-2019). As per claim 1, OPPO disclose A method for communication (see Fig.1-Fig.3), comprising: sending, by a terminal device (see sections 1-3, UE/ a terminal device), a preamble of a Message A (MsgA) (see sections 1-3, In 2-step RACH procedure, the UE sends MsgA, and when the gNB detects MsgA, it responds with MsgB); and sending, by the terminal device according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA (see sections 1-3, a channel structure for 2-step RACH. In the 2-step RACH procedure, the UE transmits MsgA, whose channel structure is preamble and PUSCH carrying payload, different PUSCH resources (with different time-frequency resources) is configured for different preambles within the same PRACH occasion), wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block and one PUSCH Demodulation Reference Signal (DMRS) port (see section 1, 2, 3, based on Rel-15 PUSCH and DMRS design, up to 12 PUSCHs are multiplexed on the same PUSCH time and frequency resources with 12 different DMRS ports, mapping of PUSCH time-frequency resources of one PUSCH resource block and one PUSCH DMRS port, Proposal 6, page 5, Fig.4); wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c) (see Section 3, pages 6-7, the PRACH resources are mapped / the mapping rule, to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c), see also pages 7-8)). As per claim 2, OPPO disclose the method according to claim 1. OPPO further disclose wherein one PUSCH resource comprises: one preamble on one PRACH occasion (see section 1, 2, 3, one of the PRACH resources is one preamble of one PRACH opportunity, and there are multiple preambles in one or more PRRCH occasions associated with each PUSCH resource). As per claim 3, OPPO disclose the method according to claim 1. OPPO further disclose wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource (see section 1, 2, 3, one of the PRACH resources is one preamble of one PRACH opportunity, and multiple preambles in one or more PRRCH occasions associated with each PUSCH resource). As per claim 5, OPPO disclose the method according to claim 1. OPPO further disclose wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks (see Section 3, pages 6-7, the PUSCH resources are mapped / the mapping rule, to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks, see also pages 7-8). As per claim 6, OPPO disclose the method according to claim 1. OPPO further disclose wherein the mapping rule between the PRACH resources and the PUSCH resources is a preset rule (see section 3, define the mapping relationship between the PRACH preamble and the PUSCH in MsgA" In 2"·step RACH, a preamble in one PRACH occasion would be selected by one UE for the preamble in MsgA" Then one corresponding PUSCH resource would be determined" Based on Rel-15 PUSCH and its DMRS design, at most 12 PUSCH can be 11multiplexed on the same PUSCH time and frequency resource with12 different DMRS ports. Therefore. PUSCH resource in MsgA would be defined by a specific PUSCH time and frequency resources and a DMRS port in corresponding to a preamble. Proposal 4: PUSCH resource in ,MsgA shall be defined by a specific PUSCH time and frequency resource and a DMRS port in corresponding to a preamble/ a preset rule). As per claim 7, claim 7 (a network device, page 6. a gNB) is rejected the same way as claim 1. As per claim 8, claim 8 is rejected the same way as claim 2. As per claim 9, claim 9 is rejected the same way as claim 3. As per claim 23, claim 23 is rejected the same way as claim 6. 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 of this title, 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. Claims 12-14 and 17-20 are rejected under 35 U.S.C. 103 as being unpatentable over OPPO (On Channel Structure for 2-step RACH, R-1902747, 03-2019), and further in view of Tian et al. (US Pub. No.: 2021/0360485). As per claim 12, claim 12 is rejected the same way as claim 1. OPPO however does not explicitly disclose the terminal device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program. Tian however disclose A terminal device (see Fig.1, UE, Fig.11, a communication node (e.g., UE)), comprising: a processor (see Fig.11, processor 1110); and a memory (see Fig.11, a memory 1105) configured to store a computer program (see para. 0063, a memory 1105 having instructions stored thereupon) executable by the processor, wherein the processor is configured to execute the computer program (see para. 0063, the instructions upon execution by the processor 1110 configure the hardware platform 1100 to perform the operations described in FIGS. 1 to 10). Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide the functionality of the terminal device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program, as taught by Tian, in the system of OPPO, so as to enable a mapping rule between RACH occasion for preamble and PUSCH resource for payload to be pre-defined, see Tian, paragraphs 21-22. As per claim 13, the combination of OPPO and Tian disclose the terminal device according to claim 12. OPPO further disclose wherein one PUSCH resource comprises: one preamble on one PRACH occasion (see section 2.2, One of the PRACH resources is one preamble of one PRACH opportunity. There will be multiple preambles in one or more PRRCH occasions associated with each PUSCH resource). As per claim 14, the combination of OPPO and Tian disclose the terminal device according to claim 12. OPPO further disclose wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that multiple PRACH resources are mapped to one PUSCH resource (see section 2.2, One of the PRACH resources is one preamble of one PRACH opportunity. There will be multiple preambles in one or more PRRCH occasions associated with each PUSCH resource). As per claim 17, claim 17 is rejected the same way as claim 1. OPPO however does not explicitly disclose the network device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program. Tian however disclose A network device (see Fig.1, BS, Fig.11, network node (e.g., BS)), comprising: a processor (see Fig.11, processor 1110); and a memory (see Fig.11, a memory 1105) configured to store a computer program (see para. 0063, a memory 1105 having instructions stored thereupon) executable by the processor, wherein the processor is configured to execute the computer program (see para. 0063, the instructions upon execution by the processor 1110 configure the hardware platform 1100 to perform the operations described in FIGS. 1 to 10) and wherein correspondence between a preamble of MsgA and PUSCH resource follows a mapping rule between physical random access channel (PRACH) resources and PUSCH resources (see para. 0034-0038, the physical resources for preamble (PRACH) and payload (PUSCH) are reserved, and a mapping rule between RACH occasion for preamble and PUSCH resource for payload is pre-defined, also per para. 0048, The preamble and PUSCH resource for payload in msgA can be individually configured by the network (e.g., the BS). UE determines the payload transmission resources based on the preamble and the association rule or mapping rule between the preamble and associated payload). Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide the functionality of the network device, comprising: a processor; and a memory configured to store a computer program executable by the processor, wherein the processor is configured to execute the computer program, as taught by Tian, in the system of OPPO, so as to enable a mapping rule between RACH occasion for preamble and PUSCH resource for payload to be pre-defined, see Tian, paragraphs 21-22. As per claim 18, claim 18 is rejected the same way as claim 14. As per claim 20, the combination of OPPO and Tian disclose the network device according to claim 17. OPPO further disclose wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PUSCH resources are mapped to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks (see Section 3, pages 6-7, the PUSCH resources are mapped / the mapping rule, to the PRACH resources in the following order: first in an increasing order of PUSCH resource numbers for frequency division multiplexed PUSCH resource blocks; secondly in an increasing order of PUSCH DMRS port indices; and then in an increasing order of time resource indices of time division multiplexed PUSCH resource blocks, see also pages 7-8) XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Second Rejection Claim(s) 1, 7,12 and 17 are rejected under 35 U.S.C. 103 as being unpatentable over ZTE (Summary of 7.2.1.1 Channel Structure for Two-step RACH, R-1903435, March 1, 2019 (03-2019)) and further in view of OPPO (On Channel Structure for 2-step RACH, R-1902747, 03-2019). As per claim 1, ZTE disclose A method for communication, comprising: sending, by a terminal device, a preamble of a Message A (MsgA) (see sections 2 and 2.2, msgA transmission is simultaneously associated with the PUSCH occasion by the UE and transmitted/sent/sending to a network devise); and sending, by the terminal device according to a mapping rule between physical random access channel (PRACH) resources and physical uplink shared channel (PUSCH) resources, a PUSCH of the MsgA on a PUSCH resource corresponding to the preamble of the MsgA (sections 2.1 and 2.2, and appendix B) that: the configuration of PUSCH resources is separate from that of PRACH resources, and the period, offset, and resource size in each occasion can all be flexibly configured by means of broadcasting (equivalent to a terminal device acquiring configuration information of a physical uplink shared channel (PUSCH) resource, and a network device sending the configuration information of the PUSCH resource). An association rule should be defined. For example, a PUSCH occasion is associated with a RACH occasion (equivalent to a mapping rule between the PUSCH resources and PRACH resources), and msgA transmission is simultaneously associated with the PUSCH occasion and RACH occasion (equivalent to the network device receiving msgA, wherein there is a mapping rule between PUSCH resources and PRACH resources in the msgA)), wherein one PUSCH resource comprises: PUSCH time-frequency resources of one PUSCH resource block; and one PUSCH DMRS port (see section 2.1, appendix A, the mapping between the PRACH preamble and the time-frequency resource of PUSCH in msgA and DMRS port). ZTE however does not explicitly disclose wherein the mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c). OPPO however disclose wherein a mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c) (see Section 3, pages 6-7, the PRACH resources are mapped / the mapping rule, to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c), see also pages 7-8)). Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide the functionality of wherein a mapping rule between the PRACH resources and the PUSCH resources comprises that the PRACH resources are mapped to the PUSCH resources in the following order: (a) in an increasing order of preamble indices within a same PRACH occasion; (b) in an increasing order of PRACH resource numbers for multiple PRACH occasions on a same time resource; and (c) in an increasing order of time resource indices for multiple PRACH occasions on a PRACH slot, wherein a priority of the order in (a) is higher than a priority of the order in (b), and the priority of the order in (b) is higher than a priority of the order in (c), as taught by OPPO, in the system of ZTE, so as to enable different mapping rule between RACH occasion for preamble and PUSCH resource, see OPPO, Figure 2, page 3. As per claim 7, claim 7 is rejected the same way as claim 1. As per claim 12, claim 12 is rejected the same way as claim 1. As per claim 17, claim 17 is rejected the same as claim 1. ZTE also disclose the terminal device acquires the mapping rule between the PUSCH resources and the PRACH resources (ZTE diagram in appendix B) discloses that msgA transmission is simultaneously associated with the PUSCH occasion and RACH occasion, it is a conventional means in the art to enable a terminal to first obtain an associated mapping rule, and then send msgA on the basis of the mapping rule). Allowable Subject Matter Claims 11, 15-16 and 21-22 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Rastegardoost (US Pub. No.:2020/0314913) – see para. 0393, “Channel structure of MsgA may comprise preamble and PUSCH carrying payload. For example, existing PRACH preamble design may be used for 2-step RACH. For example, PUSCH including DMRS for transmission of payload of MsgA may be used for 2-step RACH. The PRACH preamble and the PUSCH in a MsgA may be TDMed. It may be important for the wireless device operating in unlicensed bands, that the gap between the preamble and PUSCH short enough such that the MsgA can be transmitted using one LBT. The PRACH preamble and/or RO and the time-frequency resource of PUSCH in MsgA plus DMRS may be mapped”. Agiwal (US Pub. No.:2020/0260500) – see para. see para. 0049, “Referring to FIGS. 5A and 5B, in a case of two step CF RACH, a gNB 503 signals contention free random access resources (i.e., dedicated preambles/RACH occasions and PUSCH resources) to a UE 501 in steps 510 and 550, respectively. The UE 501 transmits a PRACH preamble in a PRACH occasion and an msgA payload (or an msgA MAC PDU) in a PUSCH resource/occasion using the assigned contention free random access resources in steps 520, 530, 560, and 570, respectively”. THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to LAKERAM JANGBAHADUR whose telephone number is (571)272-1335. The examiner can normally be reached on M-F 7 am - 4 pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ian Moore can be reached on 571-272-3085. 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 the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /LAKERAM JANGBAHADUR/ Primary Examiner, Art Unit 2469