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 . Claims 1, 13, 34, 38, 41, 44, and 47-55 are currently pending.
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.
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.
Claim(s) 1, 13, 34, 38, 41, 44, and 47-55 is/are rejected under 35 U.S.C. 103 as being unpatentable over Shi (US 20220279599 A1) in view of Zheng (US 12414057 B2) and Liu et al. (US 20210298029 A1).
Regarding claim 1, Shi discloses an information transmission method, applied to a network device and comprising: sending indication information to a terminal, the indication information indicating at least one Bandwidth Part (BWP), wherein the at least one BWP comprises at least one time domain resource, or at least one frequency domain resource, or at least one time domain resource and at least one frequency domain resource, and the at least one BWP is used for the terminal to determine a BWP for the terminal to perform at least one of following: receiving information or sending information; wherein the sending the indication information to the terminal comprises: sending the indication information to the terminal through a System Information Block 1 (SIB 1), wherein the at least one BWP comprises at least one of N initial uplink (UL) Bandwidth Parts (BWPs) or N initial downlink (DL) BWPs (paragraph [0059]; network device sends relevant configuration information of BWP via SIB1 for the initial access of the terminal device. The initial BWP may include an initial uplink BWP (initial UL BWP) and an initial downlink BWP (initial DL BWP)) (paragraph [0086]; SIB1 may indicates a plurality of initial UL BWPs); wherein the indication information further indicates at least one of: generic parameters related to the N initial UL BWPs, Random Access Channel (RACH) configuration information, common configuration information of Physical Uplink Shared Channel (PUSCH) and common configuration information of Physical Uplink Control Channel (PUCCH), or generic parameters related to the N initial DL BWPs, common configuration information of Physical Downlink Control Channel (PDCCH), and common configuration information of Physical Downlink Shared Channel (PDSCH),wherein N is an integer greater than 1 (paragraph [0087]; SIB1 includes RACH common configuration) (paragraph [0078]; BWP is configured with generic parameters) (paragraphs [0080-0082]; BWP is also configured with PUSCH common configuration information and PUCCH common configuration information) (paragraph [0086]; SIB1 indicates a plurality of initial UL BWPs, where each of the plurality of initial UL BWPs may include at least one random access resource configuration); wherein the indication information comprises BWPs used for RedCap terminals and BWPs used for all terminals (paragraphs [0103] [0106]; SIB1 indicates 4 resource configurations. A resource configuration may be used by all terminal devices and other resource configuration may be used only by a part of NR-light terminal devices (RedCap terminals)); wherein, an indication manner of the indication information comprises an index of the at least one BWP (paragraph [0058]; the network device may configure four UL BWPs and four DL BWPs for one terminal device in the connected state. The indexes of the four UL BWPs are 0, 1, 2 and 3 respectively, and the indexes of the four DL BWPs are 0, 1, 2, and 3 respectively). However, Shi et al. may not explicitly suggest the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals. Zheng et al. from the same or similar field of endeavor suggest BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals (fig. 9-10, 13-15 and claim 1; first-type terminal device determines a frequency resource of an initial BWP corresponding to the first-type terminal device, where the frequency resource of the first initial BWP does not overlap a frequency resource of a second initial BWP, and the first-type terminal device and a second-type terminal device have different capabilities. The first initial BWP may include an initial uplink BWP and an initial downlink BWP). Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi’s method/system where BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals as suggested by Zheng. The motivation would have been to configure initial bandwidth parts of terminals devices of different types differently to improve initial access performance (col. 1 lines 60-64). However, Shi et al. and Zheng may not explicitly suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource. Liu et al. from the same or similar field of endeavor suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource (paragraph [0185]; resource block assignment information includes bit mapping of Resource Block Groups (RBGs) allocated to the terminal apparatus. A frequency domain resource assignment field included in the DCI format represents the resource block assignment information. Base station apparatus allocates resources to the terminal apparatus in the DL BWP to which the resource block assignment is applied, for generating the bit mapping. The terminal apparatus determines the DL BWP to which the resource block assignment is applied, and determines the resource allocation based on the bit mapping in the determined DL BWP) (paragraph [0253]; size of the initial DL BWP is the number of resource blocks of a BWP indicated by SIB1, the frequency domain resource assignment includes an RIV, the RIV is given according to the size of a DL BWP). Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi and Zheng’s method/system where the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource as suggested by Liu et al. The motivation would have been to configure initial bandwidth parts of terminals devices to efficiently perform communication (paragraph [0005]).
Regarding claim 13, Shi discloses an information transmission method, applied to a terminal and comprising: receiving indication information, the indication information indicating at least one Bandwidth Part (BWP), wherein the at least one BWP comprises at least one time domain resource, or at least one frequency domain resource, or at least one time domain resource and at least one frequency domain resource, and the at least one BWP is used for the terminal to determine a BWP for the terminal to perform at least one of following: receiving or sending information; wherein the receiving the indication information comprises: receiving the indication information through a System Information Block 1 (SIB 1), wherein the at least one BWP comprises at least one of N initial uplink (UL) Bandwidth Parts (BWPs) or N initial downlink (DL) BWPs (paragraph [0059]; network device sends relevant configuration information of BWP via SIB1 for the initial access of the terminal device. The initial BWP may include an initial uplink BWP (initial UL BWP) and an initial downlink BWP (initial DL BWP)) (paragraph [0086]; SIB1 may indicates a plurality of initial UL BWPs); wherein the indication information further indicates at least one of: generic parameters related to the N initial UL BWPs, Random Access Channel (RACH) configuration information, common configuration information of Physical Uplink Shared Channel (PUSCH) and common configuration information of Physical Uplink Control Channel (PUCCH), or generic parameters related to the N initial DL BWPs, common configuration information of Physical Downlink Control Channel (PDCCH), and common configuration information of Physical Downlink Shared Channel (PDSCH),wherein N is an integer greater than 1 (paragraph [0087]; SIB1 includes RACH common configuration) (paragraph [0078]; BWP is configured with generic parameters) (paragraphs [0080-0082]; BWP is also configured with PUSCH common configuration information and PUCCH common configuration information) (paragraph [0086]; SIB1 indicates a plurality of initial UL BWPs, where each of the plurality of initial UL BWPs may include at least one random access resource configuration); wherein the indication information comprises BWPs used for RedCap terminals and BWPs used for all terminals (paragraphs [0103] [0106]; SIB1 indicates 4 resource configurations. A resource configuration may be used by all terminal devices and other resource configuration may be used only by a part of NR-light terminal devices (RedCap terminals)); wherein, an indication manner of the indication information comprises an index of the at least one BWP (paragraph [0058]; the network device may configure four UL BWPs and four DL BWPs for one terminal device in the connected state. The indexes of the four UL BWPs are 0, 1, 2 and 3 respectively, and the indexes of the four DL BWPs are 0, 1, 2, and 3 respectively). However, Shi et al. may not explicitly suggest the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals. Zheng et al. from the same or similar field of endeavor suggest BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals (fig. 9-10, 13-15 and claim 1; first-type terminal device determines a frequency resource of an initial BWP corresponding to the first-type terminal device, where the frequency resource of the first initial BWP does not overlap a frequency resource of a second initial BWP, and the first-type terminal device and a second-type terminal device have different capabilities. The first initial BWP may include an initial uplink BWP and an initial downlink BWP). Therefore it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi’s method/system where BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals as suggested by Zheng. The motivation would have been to configure initial bandwidth parts of terminals devices of different types differently to improve initial access performance (col. 1 lines 60-64). However, Shi et al. and Zheng may not explicitly suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource. Liu et al. from the same or similar field of endeavor suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource (paragraph [0185]; resource block assignment information includes bit mapping of Resource Block Groups (RBGs) allocated to the terminal apparatus. A frequency domain resource assignment field included in the DCI format represents the resource block assignment information. Base station apparatus allocates resources to the terminal apparatus in the DL BWP to which the resource block assignment is applied, for generating the bit mapping. The terminal apparatus determines the DL BWP to which the resource block assignment is applied, and determines the resource allocation based on the bit mapping in the determined DL BWP) (paragraph [0253]; size of the initial DL BWP is the number of resource blocks of a BWP indicated by SIB1, the frequency domain resource assignment includes an RIV, the RIV is given according to the size of a DL BWP). Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi and Zheng’s method/system where the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource as suggested by Liu et al. The motivation would have been to configure initial bandwidth parts of terminals devices to efficiently perform communication (paragraph [0005]).
Regarding claim 34, Shi discloses a terminal, comprising: a processor and a memory configured to store instructions executable by the processor, wherein when the instructions are executed by the processor, the processor is configured to perform: receiving indication information, the indication information indicating at least one Bandwidth Part (BWP), wherein the at least one BWP comprises at least one time domain resource, or at least one frequency domain resource, or at least one time domain resource and at least one frequency domain resource, and the at least one BWP is used for the terminal to determine a BWP for the terminal to perform at least one of following: receiving information or sending information; wherein the receiving the indication information comprises: receiving the indication information through a System Information Block 1 (SIB 1), wherein the at least one BWP comprises at least one of N initial uplink (UL) Bandwidth Parts (BWPs) or N initial downlink (DL) BWPs (paragraph [0059]; network device sends relevant configuration information of BWP via SIB1 for the initial access of the terminal device. The initial BWP may include an initial uplink BWP (initial UL BWP) and an initial downlink BWP (initial DL BWP)) (paragraph [0086]; SIB1 may indicates a plurality of initial UL BWPs); wherein the indication information further indicates at least one of: generic parameters related to the N initial UL BWPs, Random Access Channel (RACH) configuration information, common configuration information of Physical Uplink Shared Channel (PUSCH) and common configuration information of Physical Uplink Control Channel (PUCCH), or generic parameters related to the N initial DL BWPs, common configuration information of Physical Downlink Control Channel (PDCCH), and common configuration information of Physical Downlink Shared Channel (PDSCH),wherein N is an integer greater than 1 (paragraph [0087]; SIB1 includes RACH common configuration) (paragraph [0078]; BWP is configured with generic parameters) (paragraphs [0080-0082]; BWP is also configured with PUSCH common configuration information and PUCCH common configuration information) (paragraph [0086]; SIB1 indicates a plurality of initial UL BWPs, where each of the plurality of initial UL BWPs may include at least one random access resource configuration); wherein the indication information comprises BWPs used for RedCap terminals and BWPs used for all terminals (paragraphs [0103] [0106]; SIB1 indicates 4 resource configurations. A resource configuration may be used by all terminal devices and other resource configuration may be used only by a part of NR-light terminal devices (RedCap terminals)); wherein, an indication manner of the indication information comprises an index of the at least one BWP (paragraph [0058]; the network device may configure four UL BWPs and four DL BWPs for one terminal device in the connected state. The indexes of the four UL BWPs are 0, 1, 2 and 3 respectively, and the indexes of the four DL BWPs are 0, 1, 2, and 3 respectively). However, Shi et al. may not explicitly suggest the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals. Zheng et al. from the same or similar field of endeavor suggest BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals (fig. 9-10, 13-15 and claim 1; first-type terminal device determines a frequency resource of an initial BWP corresponding to the first-type terminal device, where the frequency resource of the first initial BWP does not overlap a frequency resource of a second initial BWP, and the first-type terminal device and a second-type terminal device have different capabilities. The first initial BWP may include an initial uplink BWP and an initial downlink BWP). Therefore it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi’s method/system where BWPs used for Reduced Capability (RedCap) terminals and BWPs used for non-Reduced Capability (RedCap) terminals, and the BWPs used for the RedCap terminals are different from the BWPs used for the non-RedCap terminals as suggested by Zheng. The motivation would have been to configure initial bandwidth parts of terminals devices of different types differently to improve initial access performance (col. 1 lines 60-64). However, Shi et al. and Zheng may not explicitly suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource. Liu et al. from the same or similar field of endeavor suggest wherein the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource (paragraph [0185]; resource block assignment information includes bit mapping of Resource Block Groups (RBGs) allocated to the terminal apparatus. A frequency domain resource assignment field included in the DCI format represents the resource block assignment information. Base station apparatus allocates resources to the terminal apparatus in the DL BWP to which the resource block assignment is applied, for generating the bit mapping. The terminal apparatus determines the DL BWP to which the resource block assignment is applied, and determines the resource allocation based on the bit mapping in the determined DL BWP) (paragraph [0253]; size of the initial DL BWP is the number of resource blocks of a BWP indicated by SIB1, the frequency domain resource assignment includes an RIV, the RIV is given according to the size of a DL BWP). Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Shi and Zheng’s method/system where the indication manner of the indication information comprises at least one of the following: a bitmap corresponding to the at least one BWP; or a Resource Indication Value (RIV) of the at least one frequency domain resource as suggested by Liu et al. The motivation would have been to configure initial bandwidth parts of terminals devices to efficiently perform communication (paragraph [0005]).
Regarding claim 38, Shi further suggests wherein the indication information comprises BWP locations that are used for RedCap terminals, and parameter configuration information corresponding to the BWPs that are used for RedCap terminals (paragraphs [0065-0066]; each initial UL BWP of the plurality of BWPs for the terminal device may include at least one random access resource configuration and at least one parameter of the random access resource corresponding to each random access resource configuration. The parameter may be a frequency domain position, a time domain position, a period, a quantity, etc.) (paragraph [0067]; the terminal device may be an NR-light terminal device).
Regarding claim 41, Shi further suggests wherein the indication information comprises time and/or frequency domain resource locations that are used for RedCap terminals, and parameter configuration information corresponding to time and/or frequency domain resources that are used for RedCap terminals (paragraphs [0065-0066]; each initial UL BWP of the plurality of BWPs for the terminal device may include at least one random access resource configuration and at least one parameter of the random access resource corresponding to each random access resource configuration. The parameter may be a frequency domain position, a time domain position, a period, a quantity, etc.) (paragraph [0067]; the terminal device may be an NR-light terminal device).
Regarding claim 44, Shi further suggests wherein the indication information further comprises BWP locations that are used for RedCap terminals, and parameter configuration information corresponding to the BWPs that are used for RedCap terminals (paragraphs [0065-0066]; each initial UL BWP of the plurality of BWPs for the terminal device may include at least one random access resource configuration and at least one parameter of the random access resource corresponding to each random access resource configuration. The parameter may be a frequency domain position, a time domain position, a period, a quantity, etc.) (paragraph [0067]; the terminal device may be an NR-light terminal device).
Regarding claim 47, Shi further suggests wherein the indication information further indicates at least one of the following: terminal types that are allowed to access the at least one BWP; at least one terminal processing capability supported by the at least one BWP; priorities of the terminal types that are allowed to access the at least one BWP; or BWP that each terminal type in at least one terminal type is as a high priority (paragraph [0114]; the SIB1 may include corresponding relationship between resource configuration and the type of terminal device and/or service type of the terminal device).
Regarding claim 48, Shi further suggests wherein the RedCap terminals use fewer antennas than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has less receiving antenna than eMBB).
Regarding claim 49, Shi further suggests wherein the RedCap terminals support smaller bandwidth than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has reduced bandwidth compared to eMBB).
Regarding claim 50, Shi further suggests wherein the indication information further indicates at least one of the following: terminal types that are allowed to access the at least one BWP; at least one terminal processing capability supported by the at least one BWP; priorities of the terminal types that are allowed to access the at least one BWP; or BWP that each terminal type in at least one terminal type is as a high priority (paragraph [0114]; the SIB1 may include corresponding relationship between resource configuration and the type of terminal device and/or service type of the terminal device).
Regarding claim 51, Shi further suggests wherein the RedCap terminals use fewer antennas than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has less receiving antenna than eMBB).
Regarding claim 52, Shi further suggests wherein the RedCap terminals support smaller bandwidth than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has reduced bandwidth compared to eMBB).
Regarding claim 53, Shi further suggests wherein the indication information further indicates at least one of the following: terminal types that are allowed to access the at least one BWP; at least one terminal processing capability supported by the at least one BWP; priorities of the terminal types that are allowed to access the at least one BWP; or BWP that each terminal type in at least one terminal type is as a high priority (paragraph [0114]; the SIB1 may include corresponding relationship between resource configuration and the type of terminal device and/or service type of the terminal device).
Regarding claim 54, Shi further suggests wherein the RedCap terminals use fewer antennas than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has less receiving antenna than eMBB).
Regarding claim 55, Shi further suggests wherein the RedCap terminals support smaller bandwidth than enhanced Mobile Broadband (eMBB) terminal/Ultra-Reliable Low-Latency Communications (URLLC) terminals (paragraph [0047]; NR-light terminal device has reduced bandwidth compared to eMBB).
Response to Remarks/Arguments
Applicant’s remarks/arguments filed on 08/20/2026 with respect to claim(s) 1, 13, and 34 have been considered but are moot in view of new ground of rejection.
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 HOANG-CHUONG Q VU whose telephone number is (571)270-3945. The examiner can normally be reached Monday-Friday (9:30-5:30 PM 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, AYAZ SHEIKH can be reached at 571-272-3795. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of 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.
HOANG-CHUONG Q. VU
Primary Examiner
Art Unit 2476
/HOANG-CHUONG Q VU/Primary Examiner, Art Unit 2476
Prosecution Insights