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 .
Claim Rejections - 35 USC § 102
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 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, 4 - 7, 9, 12 - 15, 19, and 21 - 29 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Babael, U.S. Patent Publication No. 2023/0019993.
Babael teaches:
1. (Currently Amended) A method for configuring a resource, performed by an access network device, comprising:
sending common configuration information of a downlink control channel for an initial bandwidth part (BWP) configuration (initial BWP configured by SearchSpaceZero, [210]);
wherein the common configuration information of the downlink control channel indicates a predetermined resource for a first-type terminal to perform a predetermined operation; and
the predetermined resource comprises at least one of:
an additional common control resource set (CORESET);
an additional common search space;
a common CORESET0 (DCI sets CORESET0 for initial BWP, [0210]); or
a common search space 0.
4. (Currently Amended) The method of claim 1, wherein if an initial BWP does not contain entire CORESET0, the additional common CORESET does not have to be contained in a bandwidth of the CORESET0 (under a broadest reasonable interpretation, no terms following a conditional “if” need to actually execute, Examiner suggests utilizing “when” or “responsive to”).
5. (Currently Amended) The method of claim 1, further comprising at least one of:
the additional common CORESET being configured as a CORESET associated with a common search space for the first-type terminal to perform the predetermined operation (parameter may indicate that a search space is a common search space (CSS), [0208]);
the additional common search space being configured as a common search space for the first-type terminal to perform the predetermined operation;
the CORESET0 being configured as a CORESET associated with a common search space for the first-type terminal to perform the predetermined operation; or
the common search space 0 being configured as a common search space for the first-type terminal to perform the predetermined operation.
6. (Currently Amended) The method of claim 5, wherein the predetermined resource further comprises a resource configured for a second-type terminal in a predetermined message;
the predetermined message comprises at least one of:
a master information block (MIB) or a system information block 1 (SIB1) (broadcast channel can provide a MIB, [0070]);
the resource configured for the second-type terminal comprises at least one of a resource for paging monitoring, a resource for system message monitoring or a resource for random access response (RAR) monitoring; and
the resource configured for the second-type terminal is configured as the common search space for the first-type terminal to perform the predetermined operation.
7. (Currently Amended) The method of claim 6, further comprising at least one of:
a CORESET associated with a search space for paging monitoring configured for the second-type terminal being configured as a CORESET associated with a search space for paging monitoring for the first-type terminal;
a CORESET associated with a search space for system message monitoring configured for the second-type terminal being configured as a CORESET associated with a search space for system message monitoring for the first-type terminal;
a search space for paging monitoring configured for the second-type terminal being configured as a search space for paging monitoring for the first-type terminal (PCCH utilized for carrying paging messages for wireless devices with unknown locations, [0069]); or
a search space for system message monitoring configured for the second-type terminal being configured as a search space for system message monitoring for the first-type terminal.
9. (Currently Amended) A method for configuring a resource, performed by a first- type terminal, comprising:
receiving common configuration information of a downlink control channel configured for an initial bandwidth part (BWP) (initial BWP configured by SearchSpaceZero, [210]);
wherein the common configuration information of the downlink control channel indicates a predetermined resource for the first-type terminal to perform a predetermined operation; and
the predetermined resource comprises at least one of:
an additional common control resource set (CORESET);
an additional common search space; a common CORESET0 (DCI sets CORESET0 for initial BWP, [0210]); or
a common search space 0.
12. (Currently Amended) The method of claim 9, wherein if an initial BWP does not contain entire CORESET0, the additional common CORESET does not have to be contained in a bandwidth of the CORESET0 (under a broadest reasonable interpretation, no terms following a conditional “if” need to actually execute, Examiner suggests utilizing “when” or “responsive to”).
13. (Currently Amended) The method of claim 9, further comprising at least one of:
the additional common CORESET being configured as a CORESET associated with a common search space for the first-type terminal to perform the predetermined operation (parameter may indicate that a search space is a common search space (CSS), [0208]);
the additional common search space being configured as a common search space for the first-type terminal to perform the predetermined operation;
the CORESET0 being configured as a CORESET associated with a common search space for the first-type terminal to perform the predetermined operation; or the common search space 0 being configured as a common search space for the first-type terminal to perform the predetermined operation.
14. (Currently Amended) The method of claim 13, wherein the predetermined resource further comprises a resource configured for a second-type terminal in a predetermined message;
the predetermined message comprises at least one of:
a master information block (MIB) or a system information block 1 (SIB1) (broadcast channel can provide a MIB, [0070]);
the resource configured for the second-type terminal comprises at least one of a resource for paging monitoring, a resource for system message monitoring or a resource for random access response (RAR) monitoring; and
the resource configured for the second-type terminal is configured as the common search space for the first-type terminal to perform the predetermined operation.
15. (Currently Amended) The method of claim 14, further comprising at least one of:
a CORESET associated with a search space for paging monitoring configured for the second-type terminal being configured as a CORESET associated with a search space for paging monitoring for the first-type terminal;
a CORESET associated with a search space for system message monitoring configured for the second-type terminal being configured as a CORESET associated with a search space for system message monitoring for the first-type terminal;
a search space for paging monitoring configured for the second-type terminal being configured as a search space for paging monitoring for the first-type terminal (PCCH utilized for carrying paging messages for wireless devices with unknown locations, [0069]); or
a search space for system message monitoring configured for the second-type terminal being configured as a search space for system message monitoring for the first-type terminal.
19. (Currently Amended) A communication device, comprising:
a memory; and
a processor coupled to the memory, and configured to:
send common configuration information of a downlink control channel for an initial bandwidth part (BWP) configuration (initial BWP configured by SearchSpaceZero, [210]);
wherein the common configuration information of the downlink control channel indicates a predetermined resource for a first-type terminal to perform a predetermined operation; and
the predetermined resource comprises at least one of: an additional common control resource set (CORESET);
an additional common search space;
a common CORESET0 (DCI sets CORESET0 for initial BWP, [0210]); or
a common search space 0.
21. (New) A communication device, comprising:
a memory; and
a processor coupled to the memory, and configured to perform the method of claim 9 (rejected for the same reasons as stated in claim 9).
22. (New) The method of claim 1, wherein an identifier of the additional common CORESET is not 0;
an identifier of the additional common search space is not 0 (CSS may indicate DCI formats to monitor, [0208], it is not stated that the value is 0); or
an identifier of the additional common CORESET is not 0 and an identifier of the additional common search space is not 0.
23. (New) The method of claim 1, wherein if an initial BWP configured for a second-type terminal contains the CORESET0, the CORESET0 contains an additional common CORESET configured for the second-type terminal (Coreset#0 configures initial BWP, [0210]).
24. (New) The method of claim 1, wherein an initial BWP configured for a second- type terminal contains the CORESET0, and a bandwidth overlap exists between the initial BWP of the second-type terminal and an initial BWP of the first-type terminal (Coreset#0 configures initial BWP, [0210]).
25. (New) The method of claim 1, wherein if an initial BWP does not include entire CORESET0, at least one of a common search space 0 or entire CORESET configured for a second-type terminal is configured to perform at least one of (under a broadest reasonable interpretation, no terms following a conditional “if” need to actually execute, Examiner suggests utilizing “when” or “responsive to”):
receiving a system information block 1 (SIB1);
receiving other system message; or
paging monitoring.
26. (New) The method of claim 9, wherein an identifier of the additional common CORESET is not 0;
an identifier of the additional common search space is not 0 (CSS may indicate DCI formats to monitor, [0208], it is not stated that the value is 0); or
an identifier of the additional common CORESET is not 0 and an identifier of the additional common search space is not 0.
27. (New) The method of claim 9, wherein if an initial BWP configured for a second-type terminal contains the CORESET0, the CORESET0 contains an additional common CORESET configured for the second-type terminal (Coreset#0 configures initial BWP, [0210]).
28. (New) The method of claim 9, wherein an initial BWP configured for a second- type terminal contains the CORESET0, and a bandwidth overlap exists between the initial BWP of the second-type terminal and an initial BWP of the first-type terminal (Coreset#0 configures initial BWP, [0210]).
29. (New) The method of claim 9, wherein if an initial BWP does not include entire CORESET0, at least one of a common search space 0 or entire CORESET configured for a second-type terminal is configured to perform at least one of (under a broadest reasonable interpretation, no terms following a conditional “if” need to actually execute, Examiner suggests utilizing “when” or “responsive to”):
receiving a system information block 1 (SIB1);
receiving other system message; or
paging monitoring.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PETER G SOLINSKY whose telephone number is (571)270-7216. The examiner can normally be reached M - Th, 6:30 A - 5:00 P.
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, Asad Nawaz can be reached at 571-272-3988. 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.
PETER G. SOLINSKY
Examiner
Art Unit 2463
/Peter G Solinsky/Primary Examiner, Art Unit 2463
Prosecution Insights