DETAILED ACTION
1. Claims 1-20 are presented for examination. Claims 1-5, 7-12, and 14-20 are amended.
Notice of Pre-AIA or AIA Status
2. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
3. Applicant’s arguments with respect to claim(s) 1 have been considered but are moot based on the new grounds of rejection necessitated by applicant’s amendments.
Claim Rejections - 35 USC § 103
4. 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.
5. 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.
6. 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 non-obviousness.
7. Claim(s) 1-4, 7-12 and 14-20 is/are rejected under 35 U.S.C. 103 as being unpatentable over US 2020/0351784 A1 by Tsai et al. (hereafter referred to as Tsai), in view of US 2020/0092814 A1 by Zhou et al. (hereafter referred to as Zhou).
Regarding claim 1, Tsai teaches a monitoring method, comprising:
obtaining, by a terminal, wake-up signal configuration information (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”) from a network-side device (see at least ¶ [0036]);
performing, by the terminal, detection for a wake-up signal within a first duration according to the wake-up signal configuration information, wherein the first duration belongs to a physical downlink control channel (PDCCH) monitoring period configured by the network-side device (see at least ¶ [0057]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”), and …; and
determining, by the terminal, a monitoring behavior for a target channel based on the detection of the wake-up signal (see at least ¶ [0057]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”), wherein the target channel comprises at least one of the following:
physical downlink control channel (PDCCH); physical downlink shared channel (PDSCH); or physical uplink shared channel (PUSCH) (see at least ¶ [0057]; PDCCH).
However, Tsai does not appear to specifically disclose the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion.
In the same field of endeavor, Zhou teaches the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion (see at least ¶ [0041]; “ In response to detecting the first WUS and determining the MAC entity is in the first DRX active time, the wireless device may monitor a first PDCCH of the second cell at least during the first DRX active time.”).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify the monitoring taught by Tsai with the monitoring taught by Zhou in order to enable wake-up procedure and power saving operations (Zhou ¶ [0058]).
Regarding claim 2, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein during the detecting for the wake-up signal, the terminal does not perform monitoring for a first channel, the first channel comprising at least one of PDCCH, PDSCH, or PUSCH (see at least ¶ [0057]; “For another example, if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission). If the drx-InactivityTimer is running on a second WUS occasion, the UE may not monitor the WUS on the second WUS occasion (since the UE is in DRX active time). In addition, the UE may go to sleep when the drx-InactivityTimer expires.”).
Regarding claim 3, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the determining, by the terminal, a monitoring behavior for a target channel based on the detection of the wake-up signal comprises one of the following:
in a case that the terminal detects the wake-up signal or in a case that the detected wake-up signal indicates monitoring the target channel, performing, by the terminal, monitoring for the target channel; or,
in a case that the terminal does not detect the wake-up signal or in a case that the terminal detects the wake-up signal and the wake-up signal indicates not monitoring the target channel, skipping, by the terminal, the monitoring for the target channel (see at least ¶ [0058]; “In other words, the purpose of the WUS may be to wake up the UE (e.g., when the UE receives the WUS), so that the UE may wake up to stay in DRX active time for monitoring the PDCCH (on next on duration time). However, if the UE is already in the DRX active time, it is unnecessary to monitor the WUS. Thus, the UE may not need to monitor the WUS when the UE is in DRX active time, so as to reduce the power consumption.” And at least ¶ [0060]; “In one implementation, the UE may not monitor the WUS on the WUS occasion (or ignore monitoring the WUS on the WUS occasion) when the UE is in DRX active time (e.g., duration of drx-InactivityTimer). On the contrary, the UE may monitor the WUS on the WUS occasion when the UE is not in DRX active time.” ).
Regarding claim 4, Tsai in view of Zhou teaches the method according to claim 1. In addition, Tsai teaches wherein the determining, by the terminal, a monitoring behavior for a target channel based on the detection of the wake-up signal further comprises: in a case that the terminal detects the wake-up signal or in a case that the detected wake-up signal indicates monitoring the target channel, performing, by the terminal, monitoring for the target channel (see at least ¶ [0056]; “Therefore, the network node could send a WUS (beforehand) to wake up the UE to monitor the normal PDCCH if needed.”): and wherein the terminal does not perform detection for the wake-up signal during the monitoring for the target channel (see at least ¶ [0057]; “If the drx-InactivityTimer is running on a second WUS occasion, the UE may not monitor the WUS on the second WUS occasion (since the UE is in DRX active time).”).
Regarding claim 7, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the method further comprises: in a case that the terminal receives a second-channel skipping indication, performing, by the terminal, detection for the wake-up signal within the second-channel skipping duration indicated by the second-channel skipping indication (see at least ¶ [0057]; “If the drx-InactivityTimer is running on a second WUS occasion, the UE may not monitor the WUS on the second WUS occasion (since the UE is in DRX active time). In addition, the UE may go to sleep when the drx-InactivityTimer expires.”).
Regarding claim 8, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the method further comprises:
in a case that the terminal detects the wake-up signal or in a case that the detected wake-up signal indicates monitoring the target channel, starting or restarting, by the terminal, a DRX inactivity timer; or adjusting, by the terminal, the starting time of a DRX on duration timer to be the ending time of a time unit in which the wake-up signal is detected (see at least ¶ [0050]-[0052]; “In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time). Alternatively, the UE may skip triggering drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or inactive time).”).
Regarding claim 9, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the method further comprises:
in a case that the terminal detects the wake-up signal and the wake-up signal indicates a second time interval, starting or restarting, by the terminal, a DRX inactivity timer when or after the second time interval is ended; or
adjusting, by the terminal, the starting time of a DRX on duration timer to be the ending time of the second time interval;
wherein the terminal performs monitoring for the target channel when or after the second time interval is ended, and/or the terminal skips the monitoring for the target channel within the second time interval (see at least ¶ [0050]-[0052]; In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time). Alternatively, the UE may skip triggering drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or inactive time). ).
Regarding claim 10, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the wake-up signal configuration information comprises at least one of the following:
a wake-up signal monitoring occasion; the first duration; a first timer, wherein a length of the first timer is equal to a length of the first duration, and the terminal performs a behavior of monitoring for the wake-up signal and the monitoring behavior for the target channel during the running of the first timer; a wake-up signal monitoring period; a period of the first duration; a time-frequency domain resource occupied by the wake-up signal; a frequency hopping format of the wake-up signal; or sequence information of the wake-up signal (see at least ¶ [0057]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”).
Regarding claim 11, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the wake-up signal configuration information comprises a wake-up signal monitoring occasion (see at least ¶ [0056]; “Therefore, the network node could send a WUS (beforehand) to wake up the UE to monitor the normal PDCCH if needed.”), and the performing, by the terminal, detection for the wake-up signal within the first duration according to the wake-up signal configuration information comprises: performing, by the terminal, detection for the wake-up signal on the wake-up signal monitoring occasion within the first duration, according to the wake-up signal configuration information (see at least Fig. 6 and ¶ [0057]; “For another example, if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission). If the drx-InactivityTimer is running on a second WUS occasion, the UE may not monitor the WUS on the second WUS occasion (since the UE is in DRX active time). In addition, the UE may go to sleep when the drx-InactivityTimer expires.”).
Regarding claim 12, Tsai in view of Zhou teaches the method according to claim 1.
In addition, Tsai teaches wherein the first duration is a DRX onduration or part of the DRX onduration; wherein the first duration being part of the DRX onduration comprises: a start time of the first duration is a start time of the DRX onduration and an end time of the first duration is earlier than an end time of the DRX onduration; or the end time of the first duration is the end time of the DRX onduration and the start time of the first duration is later than the start time of the DRX onduration (see at least ¶ [0050]; “In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time).”).
Regarding claim 14, Tsai teaches a wake-up signal transmission method, comprising:
sending, by a network-side device, wake-up signal configuration information to a terminal (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”); and
transmitting, by the network-side device, a wake-up signal within a first duration according to the wake-up signal configuration information, wherein the first duration belongs to a physical downlink control channel (PDCCH) monitoring time period configured by the network-side device (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”).
However, Tsai does not appear to specifically disclose the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion.
In the same field of endeavor, Zhou teaches the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion (see at least ¶ [0041]; “ In response to detecting the first WUS and determining the MAC entity is in the first DRX active time, the wireless device may monitor a first PDCCH of the second cell at least during the first DRX active time.”).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify the monitoring taught by Tsai with the monitoring taught by Zhou in order to enable wake-up procedure and power saving operations (Zhou ¶ [0058]).
Regarding claim 15, Tsai in view of Zhou teaches the method according to claim 14.
In addition, Tsai teaches wherein the wake-up signal configuration information comprises at least one of the following:
a wake-up signal monitoring occasion; the first duration; a first timer, wherein a length of the first timer is equal to a length of the first duration, and the terminal performs a behavior of monitoring for the wake-up signal and monitoring on a target channel during running of the first timer; a wake-up signal monitoring period; a period of the first duration; a time-frequency domain resource occupied by the wake-up signal; a frequency hopping format of the wake-up signal; or sequence information of the wake-up signal (see at least ¶ [0057]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”).
Regarding claim 16, Tsai in view of Zhou teaches the method according to claim 14.
In addition, Tsai teaches wherein the method further comprises one of the following:
in a case that the network-side device transmits the wake-up signal, or in a case that the transmitted wake-up signal indicates monitoring on a target channel, starting or restarting, by the network-side device, a DRX inactivity timer, or adjusting, by the network-side device, the starting time of a DRX onduration timer to be the ending time of a time unit in which the wake-up signal is transmitted (see at least ¶ [0050]-[0052]; “In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time). Alternatively, the UE may skip triggering drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or inactive time).”).
Regarding claim 17, Tsai in view of Zhou teaches the method according to claim 14.
In addition, Tsai teaches wherein the method further comprises:
in a case that the network-side device transmits the wake-up signal and the wake-up signal indicates a third time interval, starting or restarting, by the network-side device, a DRX inactivity timer when or after the third time interval is ended;
or adjusting, by the network-side device, the starting time of a DRX onduration timer to be the ending time of the third time interval transmitted;
wherein the terminal performs monitoring on a target channel when or after the third time interval is ended, and/or the terminal skips the monitoring for the target channel within the third time interval (see at least ¶ [0050]-[0052]; In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time). Alternatively, the UE may skip triggering drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or inactive time). ).
Regarding claim 18, Tsai in view of Zhou teaches the method according to claim 14.
In addition, Tsai teaches wherein the first duration is a DRX onduration or part of the DRX onduration;
wherein the first duration being part of the DRX onduration comprises:
a start time of the first duration is a start time of the DRX onduration and an end time of the first duration is earlier than an end time of the DRX onduration, or the end time of the first duration is the end time of the DRX onduration and the start time of the first duration is later than the start time of the DRX onduration (see at least ¶ [0050]-[0052]; In one implementation, the UE may stop the drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or in active time). The UE may stop the drx-onDurationTimer when the UE does not receive the WUS on the WUS occasion (in DRX active time or DRX inactive time). Alternatively, the UE may skip triggering drx-onDurationTimer when the UE receives the WUS on the WUS occasion (in DRX active time or inactive time). ).
Regarding claim 19, Tsai teaches a communication device (see at least Fig. 8), comprising a processor implemented in hardware (see at least Fig. 8 (826)), a memory (see at least Fig. 8 (828)), and a program or instructions stored in the memory and executable by the processor (see at least ¶ [0104]-[0150]), wherein the program or the instructions, when executed by the processor, causes the communication device to perform:
obtaining wake-up signal configuration information from a network-side device (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”);
performing detection for a wake-up signal within a first duration according to the wake-up signal configuration information, wherein the first duration belongs to a physical downlink control channel (PDCCH) monitoring period configured by the network-side device (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”), and …; and
determining a monitoring behavior for a target channel based on the detection of the wake-up signal (see at least ¶ [0057] – [0058]; “if the UE receives the WUS on a first WUS occasion, the UE may wake up to monitor the PDCCH and start/restart a drx-InactivityTimer when the UE receives a PDCCH for scheduling (e.g., PDCCH for UL/DL data transmission).”), wherein the target channel comprises at least one of the following:
physical downlink control channel (PDCCH); physical downlink shared channel (PDSCH); or physical uplink shared channel (PUSCH) (see at least ¶ [0057]; PDCCH).
However, Tsai does not appear to specifically disclose the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion.
In the same field of endeavor, Zhou teaches the PDCCH monitoring period comprises at least one of discontinuous reception (DRX) active time or a monitoring period corresponding to a PDCCH monitoring occasion (see at least ¶ [0041]; “ In response to detecting the first WUS and determining the MAC entity is in the first DRX active time, the wireless device may monitor a first PDCCH of the second cell at least during the first DRX active time.”).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify the monitoring taught by Tsai with the monitoring taught by Zhou in order to enable wake-up procedure and power saving operations (Zhou ¶ [0058]).
Regarding claim 20, Tsai teaches a communication device (see at least Fig. 8), comprising a processor implemented in hardware (see at least Fig. 8 (826)), a memory (see at least Fig. 8 (828)) and a program or instructions stored in the memory and executable by on the processor (see at least ¶ [0104]-[0105] ), wherein the program or the instructions, when executed by the processor, causes the communication device to perform the steps of the monitoring method according to claim 14 (see rejection above).
8. Claim(s) 5 and 6 is/are rejected under 35 U.S.C. 103 as being unpatentable over Tsai in view of Zhou as applied to claim 1 above, further in view of US 2004/0229659 A1 by Boos et al. (hereafter referred to as Boos).
Regarding claim 5, Tsai in view of Zhou teaches the method according to claim 1.
Tsai in view of Zhou does not appear to specifically disclose wherein the determining, by the terminal, a monitoring behavior for a target channel based on the detection of wake-up signal comprises: in a case that the terminal detects a wake-up signal and the wake-up signal indicates a first time interval, performing, by the terminal, monitoring for the target channel when or after the ending of the first time interval, and/or skipping, by the terminal, the monitoring for the target channel within the first time interval.
In the same field of endeavor, Boos teaches wherein the determining, by the terminal, a monitoring behavior for a target channel based on the detection of wake-up signal comprises: in a case that the terminal detects a wake-up signal and the wake-up signal indicates a first time interval, performing, by the terminal, monitoring for the target channel when or after the ending of the first time interval, and/or skipping, by the terminal, the monitoring for the target channel within the first time interval (see at least ¶ [0022]-[0025]; “Along these lines, the control circuit is operable to determine whether the skipping of monitoring for a subsequent wakeup period would exceed the wakeup period interval required to retain at least five signal strength measurements in memory. In this case, the control circuit would not direct the receiver to skip (Rx enabled) the monitoring of the received signal strength of the at least one neighboring channel for at least one subsequent wakeup period.”).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify Tsai in view of Zhou with Boos in order to reduce current drain in a communication device (Boos ¶ [0001]).
Regarding claim 6, Tsai in view of Zhou and Boos teaches the method according to claim 5.
In the obvious combination, Boos teaches wherein the method further comprises: performing, by the terminal, detection for the wake-up signal within the first time interval (see at least ¶ [0022]; “Along these lines, the control circuit is operable to determine whether the skipping of monitoring for a subsequent wakeup period would exceed the wakeup period interval required to retain at least five signal strength measurements in memory.”).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify Tsai in view of Zhou with Boos in order to reduce current drain in a communication device (Boos ¶ [0001]).
9. Claim(s) 13 is/are rejected under 35 U.S.C. 103 as being unpatentable over Tsai in view of Zhou as applied to claim 1 above, further in view of US 9,460,321 B1 by Brocato.
Regarding claim 13, Tsai teaches the method according to claim 1.
Tsai in view of Zhou does not appear to specifically disclose wherein the performing, by the terminal, detection for a wake-up signal within a first duration according to the wake-up signal configuration information comprises: performing, by the terminal, detection for the wake-up signal within the first duration according to the wake-up signal configuration information by using a near-zero power receiver.
In the same field of endeavor, Brocato teaches wherein the performing, by the terminal, detection for a wake-up signal within a first duration according to the wake-up signal configuration information comprises: performing, by the terminal, detection for the wake-up signal within the first duration according to the wake-up signal configuration information by using a near-zero power receiver (see at least col. 13 lines 18-26; For the purpose of a zero-power receiver to perform a wake-up task).
It would have been obvious to one having ordinary skill in the art before the effective filing date to modify Tsai in view of Zhou with Brocato in order to extend battery life in wireless mobile applications.
Conclusion
10. 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.
13. Any inquiry concerning this communication or earlier communications from the examiner should be directed to NATASHA W COSME whose telephone number is (571)270-7225. The examiner can normally be reached M-F 7:30-4. 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, Ayman Abaza can be reached at 571-270-0422. 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.
/NATASHA W COSME/Primary Examiner, Art Unit 2465
Prosecution Insights