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 .
This action is in response to the amendment file on 6/15/2026.
Claims 1-9, 12, 14-15 are amended.
Claims 13, 16-20 are canceled.
The 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph for claims 1 and 14 are withdrawn based on claim amendments.
Claims 1-12, 14-15 are examined and rejected.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-3, 7, 9, 12, 14-15 rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention. These claims recite the limitations: “... inter-UE DRX configuration”, “inter-UE control information”; “inter-UE physical shared channel”, “inter-UE physical control channel”. The specification lacks written description for these limitation. This is a new matter situation.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim(s) 1-3, 9, 12, 14-15 are rejected under 35 U.S.C. 103 as being unpatentable over Lin (US 11,877241 B1, hereinafter “Lin”).
Regarding Claim 1, Lin teaches a method comprising:
obtaining, by a first user equipment (UE) at least one inter-UE discontinuous reception (DRX) configuration (Examiners Note: the limitation “inter-UE” is interpreted as sidelink (SL). Based on this interpretation, see FIG. 9., a flow chart illustrating the method for DRX support in SL communication; step S910, the UE determines an SL DRX configuration set based on one of the following: one or more types of one or more SL services which the UE is participating with one or more peer UEs, one or more SL DRX configurations received from the peer UEs, and control information received from a BS);
determining to use a first inter-UE DRX configuration for a reception of a message for establishing a unicast connection, among the at least one inter-UE DRX configuration, based on a first service (see step S920, the UE applies the SL DRX configuration set to enable a DRX operation for SL communications with the peer UEs; also see step S910, UE determines SL DRX configuration set based on one or more SL services which the UE is participating with one or more peer UEs; and at col 10, lines 33-35, for either one of unicast/groupcast/broadcast/i.e., representing SL services, the SL DRX configuration could be associated with the destination ID; also cee Claim 1, the UE maintains separate SL active times for different SL DRX configurations when multiple SL DRX configurations corresponding to the multiple peer UEs for unicast, groupcast, or broadcast communication are applied);
receiving, from a second UE, first inter-UE control information for scheduling of an inter-UE physical shared channel through an inter-UE physical control channel based on an active time of the first inter-UE DRX configuration (see col 15, lines 19-24, if the UE has received the SCI/i.e., a first SCI, from its peer UE recently, which is used for SL communication with other UEs or this UE, then the UE may be able to determine whether the peer UE is still in the SL DRX active time based on the SL DRX inactivity timer of the peer UE. That is, the peer UE may stay in SL DRX active time before its SL DRX inactivity timer (which may be started when the peer UE sends SCI) expires, and the value of the SL DRX inactivity timer of the peer UE may be derived via a previous signaling for SL DRX configuration exchange); and
receiving, from the second UE, the message for establishing the unicast connection and second inter-UE control information through the inter-UE physical shared channel, based on the active time (see col 18, lines 10-14, a group member may send a wake-up signal/i.e., representing a message for unicast communication, on a UE-specific resource when he wants to perform a one-on-one unicast communication with a specific UE; also see col 10, lines 6-19, a UE may maintain a respective SL DRX active time for each SL link to a peer UE (i.e. Sidelink active time per link)/i.e., representing the capability of the UE to receive a second SCI… That is, the SL DRX active time of the UE (i.e., Sidelink active time per UE) may be determined to be the joint set of the SL DRX active times of all SL links to the peer UEs),
wherein the at least one nter-UE DRX configuration is configured for each unicast service (see col 10, lines 33-41, for a unicast link, the SL DRX timer could be configured per peer UE, per unicast link, or per PC5 RRC connection/i.e., representing each information of the unicast service link such as peer UE, per unicast link, per PC5 connection. For example, the SL DRX configuration may be identified by the source ID and the destination ID of an SL link. For example, the SL DRX configuration may be configured for each combination of source ID, destination ID, and cast type. It means that even for the same pair of source ID and destination ID, different cast types may apply different SL DRX configurations).
Lin does not specify “receiving a first inter-UE control information/first SCI” and “receiving a second inter-UE control information/second SCI”.
However, it would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin to specify the reception of distinct SCIs (first SCI and second SCI), since Lin already discloses that a UE may maintain an activity timer for each SL to a peer UE, and that the SL DRX active time is the sidelink active time per UE, to be used as a joint set of SL DRX configurations and active times for all SL links to the peer UEs (see Lin, col 10, lines 6-19).
Regarding Claim 2, Lin teaches the method of claim 1, wherein the second inter-UE control information includes a cast type indicator, and wherein the cast type indicator represents broadcast (see col 10, lines 42-65, A UE may simultaneously have several SL DRX configurations to apply, e.g., different peer UEs apply different SL DRX configurations, and different broadcast/groupcast service apply different SL DRX configurations as well. In this case, the UE should monitor the joint set or superposition of all SL DRX active time requested by the peer UEs and the interested groupcast/broadcast services indicated in their SL DRX configurations. For example, a UE may receive an SL DRX configuration indicating when its peer UEs or when its interested groupcast/broadcast services may perform SL transmission. This UE then needs to keep awake during the transmission pattern indicated by any of its peer UEs and any of its interested groupcast/broadcast services).
Regarding Claim 3, Lin teaches the method of claim 1, wherein the second nter-UE control information includes a cast type indicator, and wherein the cast type indicator represents unicast (see col 18, lines 10-14, a group member may send a wake-up signal/i.e., representing a message for unicast communication, on a UE-specific resource when he wants to perform a one-on-one unicast communication with a specific UE).
Regarding Claim 9, Lin teaches the method of claim 1, wherein the first inter-UE DRX configuration is configured for a destination L2 ID related to the first service (see col 10, lines 33-41, for a unicast link, the SL DRX timer could be configured per peer UE, per unicast link, or per PC5 RRC connection. For example, the SL DRX configuration may be identified by the source ID and the destination ID of an SL link. For example, the SL DRX configuration may be configured for each combination of source ID, destination ID, and cast type/i.e., related to the service type (unicast, broadcast etc.). It means that even for the same pair of source ID and destination ID, different cast types may apply different SL DRX configurations).
Regarding Claim 12, Lin teaches the method of claim 1, wherein a second inter-UEDRX configuration included in the at least one inter-UEDRX configuration is related to a plurality of services (see col.13-14, or a mode-1 and/or mode-2 UE, the SL DRX configuration may be configured per V2X application/service or per UE ID. In other words, a UE may have separate UE ID for transmission/reception of different V2X applications/services, and thus, the UE may apply different SL DRX configurations for different V2X applications/services).
Regarding Claim 14, Lin teaches a first user equipment (UE) (see FIG. 4 for UE) comprising: one or more processors; one or more transceivers; and one or more memories connected to the one or more processors and storing instructions, wherein the instructions, based on being executed by the one or more processors, cause the first UE to:
obtain at least one inter-UE discontinuous reception (DRX) configuration (Examiners Note: the limitation “inter-UE” is interpreted as sidelink (SL). Based on this interpretation, see FIG. 9., a flow chart illustrating the method for DRX support in SL communication; step S910, the UE determines an SL DRX configuration set based on one of the following: one or more types of one or more SL services which the UE is participating with one or more peer UEs, one or more SL DRX configurations received from the peer UEs, and control information received from a BS);
determine to use a first inter-UE DRX configuration for a reception of a message for establishing a unicast connection, among the at least one inter-UE DRX configuration, based on a first service (see step S920, the UE applies the SL DRX configuration set to enable a DRX operation for SL communications with the peer UEs; also see step S910, UE determines SL DRX configuration set based on one or more SL services which the UE is participating with one or more peer UEs; and at col 10, lines 33-35, for either one of unicast/groupcast/broadcast/i.e., representing SL services, the SL DRX configuration could be associated with the destination ID; also cee Claim 1, the UE maintains separate SL active times for different SL DRX configurations when multiple SL DRX configurations corresponding to the multiple peer UEs for unicast, groupcast, or broadcast communication are applied);
receive, from a second UE, first inter-UE control information for scheduling of an inter-UE physical shared channel through an inter-UE physical control channel, based on an active time of the first inter-UE DRX configuration (see col 15, lines 19-24, if the UE has received the SCI/i.e., a first SCI, from its peer UE recently, which is used for SL communication with other UEs or this UE, then the UE may be able to determine whether the peer UE is still in the SL DRX active time based on the SL DRX inactivity timer of the peer UE. That is, the peer UE may stay in SL DRX active time before its SL DRX inactivity timer (which may be started when the peer UE sends SCI) expires, and the value of the SL DRX inactivity timer of the peer UE may be derived via a previous signaling for SL DRX configuration exchange); and
receive, from the second UE, the message for establishing the unicast connection and second inter-UE control information through the inter-UE physical shared channel based on the active time (see col 18, lines 10-14, a group member may send a wake-up signal/i.e., representing a message for unicast communication, on a UE-specific resource when he wants to perform a one-on-one unicast communication with a specific UE; also see col 10, lines 6-19, a UE may maintain a respective SL DRX active time for each SL link to a peer UE (i.e. Sidelink active time per link)/i.e., representing the capability of the UE to receive a second SCI… That is, the SL DRX active time of the UE (i.e., Sidelink active time per UE) may be determined to be the joint set of the SL DRX active times of all SL links to the peer UEs),
wherein the at least one inter-UE DRX configuration is configured for each unicast service (see col 10, lines 33-41, for a unicast link, the SL DRX timer could be configured per peer UE, per unicast link, or per PC5 RRC connection/i.e., representing each information of the unicast service link such as peer UE, per unicast link, per PC5 connection. For example, the SL DRX configuration may be identified by the source ID and the destination ID of an SL link. For example, the SL DRX configuration may be configured for each combination of source ID, destination ID, and cast type. It means that even for the same pair of source ID and destination ID, different cast types may apply different SL DRX configurations).
Lin does not specify “receiving a first inter-UE control information/first SCI” and “receiving a second inter-UE control information/second SCI”.
However, it would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin to specify the reception of distinct SCIs (first SCI and second SCI), since Lin already discloses that a UE may maintain an activity timer for each SL to a peer UE, and that the SL DRX active time is the sidelink active time per UE, to be used as a joint set of SL DRX configurations and active times for all SL links to the peer UEs (see Lin, col 10, lines 6-19).
Regarding Claim 15, Lin teaches a processing device adapted to control a first user equipment (UE) (see FIG. 4 for UE), the processing device comprising: one or more processors; and one or more memories connected to the one or more processors and storing instructions, wherein the instructions, based on being executed by the one or more processors cause the first UE to:
obtain at least one inter-UE discontinuous reception (DRX) configuration (Examiners Note: the limitation “inter-UE” is interpreted as sidelink (SL). Based on this interpretation, see FIG. 9., a flow chart illustrating the method for DRX support in SL communication; step S910, the UE determines an SL DRX configuration set based on one of the following: one or more types of one or more SL services which the UE is participating with one or more peer UEs, one or more SL DRX configurations received from the peer UEs, and control information received from a BS);
determine to use a first inter-UE DRX configuration for a reception of a message for establishing a unicast connection, among the at least one inter-UE DRX configuration, based on a first service (see step S920, the UE applies the SL DRX configuration set to enable a DRX operation for SL communications with the peer UEs; also see step S910, UE determines SL DRX configuration set based on one or more SL services which the UE is participating with one or more peer UEs; and at col 10, lines 33-35, for either one of unicast/groupcast/broadcast/i.e., representing SL services, the SL DRX configuration could be associated with the destination ID; also cee Claim 1, the UE maintains separate SL active times for different SL DRX configurations when multiple SL DRX configurations corresponding to the multiple peer UEs for unicast, groupcast, or broadcast communication are applied);
receive, from a second UE, first inter-UE control information for scheduling of an inter-UE physical shared channel through an inter-UE physical control channel, based on an active time of the first inter-UE DRX configuration (see col 15, lines 19-24, if the UE has received the SCI/i.e., a first SCI, from its peer UE recently, which is used for SL communication with other UEs or this UE, then the UE may be able to determine whether the peer UE is still in the SL DRX active time based on the SL DRX inactivity timer of the peer UE. That is, the peer UE may stay in SL DRX active time before its SL DRX inactivity timer (which may be started when the peer UE sends SCI) expires, and the value of the SL DRX inactivity timer of the peer UE may be derived via a previous signaling for SL DRX configuration exchange); and
receive, from the second UE, the message for establishing the unicast connection and second inter-UE control information through the inter-UE physical shared channel based on the active time (see col 18, lines 10-14, a group member may send a wake-up signal/i.e., representing a message for unicast communication, on a UE-specific resource when he wants to perform a one-on-one unicast communication with a specific UE; also see col 10, lines 6-19, a UE may maintain a respective SL DRX active time for each SL link to a peer UE (i.e. Sidelink active time per link)/i.e., representing the capability of the UE to receive a second SCI… That is, the SL DRX active time of the UE (i.e., Sidelink active time per UE) may be determined to be the joint set of the SL DRX active times of all SL links to the peer UEs),
wherein the at least one inter-UE DRX configuration is configured for each unicast service (see col 10, lines 33-41, for a unicast link, the SL DRX timer could be configured per peer UE, per unicast link, or per PC5 RRC connection/i.e., representing each information of the unicast service link such as peer UE, per unicast link, per PC5 connection. For example, the SL DRX configuration may be identified by the source ID and the destination ID of an SL link. For example, the SL DRX configuration may be configured for each combination of source ID, destination ID, and cast type. It means that even for the same pair of source ID and destination ID, different cast types may apply different SL DRX configurations).
Lin does not specify “receiving a first inter-UE control information/first SCI” and “receiving a second inter-UE control information/second SCI”.
However, it would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin to specify the reception of distinct SCIs (first SCI and second SCI), since Lin already discloses that a UE may maintain an activity timer for each SL to a peer UE, and that the SL DRX active time is the sidelink active time per UE, to be used as a joint set of SL DRX configurations and active times for all SL links to the peer UEs (see Lin, col 10, lines 6-19).
Claim(s) 4, 6-7, are rejected under 35 U.S.C. 103 as being unpatentable over Lin in view of Fu (US 20230077297 A1, hereinafter “Fu”).
Regarding Claim 4, Lin teaches the method of claim 1, but does not disclose details regarding: transmitting, by the first UE, to the second UE, a direct communication accept (DCA) message, as a response for the message for establishing the unicast connection; and establishing, by the first UE, the unicast connection with the second UE, based on the transmission of the DCA message.
In the same field of endeavor, Fu teaches this limitation: see para 202, when the second terminal device is interested in using at least one announced service over a unicast link with the first terminal device, the second terminal device may send the Direct Communication Accept message to the first terminal device.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin, to specify using a direct communication accept (DCA) message as a response for the message for establishing the unicast connection, the motivation being the Direct Communication Accept message includes information regarding a corresponding privacy policy of the second terminal device (see Fu, para 202), and also so that the privacy policy between the two terminals match (see FU, para 15).
Regarding Claim 6, Lin discloses the method of claim 1, but does not disclose detials regarding: the message for establishing the unicast connection includes a direct communication request (DCR) message.
In the same field of endeavor, Fu teaches this limitation: see para 202, the request message may be the Direct Communication Request message which may be transmitted via broadcast, when the second terminal device is interested in using at least one announced service over a unicast link with the first terminal device, the second terminal device may send the Direct Communication Accept message to the first terminal device. In addition, the Direct Communication Accept message may further include information regarding at least one corresponding privacy policy of the second terminal device.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin, to send with a direct communication request (DCR) message as for establishing the unicast connection as taught by Fu, the motivation being that the privacy policy between the two terminals match as a result of the DCA and DCR (see FU, para 15).
Regarding Claim 7, Lin discloses the method of claim 1, wherein the first inter-UEDRX configuration is configured for a direction of a pair of a source layer (L) 2 ID and a destination L2 ID (see col 10, lines 32-41, for a unicast link, the SL DRX timer could be configured per peer UE, per unicast link, or per PC5 RRC connection. For example, the SL DRX configuration may be identified by the source ID and the destination ID of an SL link. For example, the SL DRX configuration may be configured for each combination of source ID, destination ID, and cast type. It means that even for the same pair of source ID and destination ID, different cast types may apply different SL DRX configurations).
Claim(s) 5 is rejected under 35 U.S.C. 103 as being unpatentable over Lin in view of Fu, in view of Pan (WO 2021119474 A1, hereinafter “Pan”, from IDS).
Regarding Claim 5, Lin in view of Fu do not disclose details regarding: receiving by the first UE, from the second UE, a medium access control (MAC) protocol data unit (PDU), based on the unicast connection.
In the same field of endeavor, Pan teaches this limitation: see paras 317 and para 318, The determination of whether a SL transmission is destined for a UE may be made at a UE by checking if information carried in the SL transmission matches information known to the UE … unicast transmission… of the decoded MAC PDU.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the combined teachings of Lin and Fu, to specify communication over unicast connection using MAC PUD by determining the destination and source address of the MAC PDU as taught by Pan, to ensure that the sidelink transmission destined for the UE matches the information known to the UE (see Pan, para 317).
Claim(s) 8 is rejected under 35 U.S.C. 103 as being unpatentable over Lin in view of Fu, in view of Pan.
Regarding Claim 8, Lin in view of Fu, do not disclose details regarding: the source L2 ID is related to the second UE, and wherein the destination L2 ID is related to the first UE.
In the same field of endeavor, Pan teaches this limitation: see para 317, The determination of whether a SL transmission is destined for a UE may be made at a UE by checking if information carried in the SL transmission matches information known to the UE … para 319, if unicast transmission, the DST (destination) field of the decoded MAC PDU sub header is equal to the 8 MSB of any of the Source Layer-2 ID(s) of the UE/i.e., L2 destination address of the first device, for which the 16 LSB are equal to the Destination ID in the corresponding SCI, and the SRC (source) field of the decoded MAC PDU sub header is equal to the 16 MSB of any of the Destination Layer-2 ID(s) of the UE/i.e., L2 source address of the second device for which the 8 LSB are equal to the Source ID in the corresponding SCI.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the combined teachings of Lin and Fu, to specify details regarding communication direction of a pair of a source layer L2 ID and a destination L2 ID as taught by Pan, so as to ascertain that a SL transmission is destined for this UE based on its destination address (see Pan, para 317).
Claim(s) 10-11 rejected under 35 U.S.C. 103 as being unpatentable over Lin in view of Park (US 20230363048 A1, hereinafter “Park”).
Regarding Claim 10, Lin discloses the method of claim 1, but does not disclose details regarding: the first service is a service related to voice over internet protocol (VoIP).
In the same field of endeavor, Park teaches this limitation: see para 112, After the DRX inactivity timer and the RRC inactivity timer are started, if no DL grant or UL grant has occurred in the UE until the timer expires, a short DRX cycle may be started, if a short DRX cycle is configured for the UE. Further, for example, the short DRX cycle may be started if the UE receives a DRX command and a short DRX cycle is set for the UE. Here, the DRX command may be received via a DRX Command MAC CE, wherein the DRX command MAC CE may be identified via an LCID in the MAC PDU sub header. For example, the short DRX cycle may be motivated mainly by the Voice over Internet Protocol (VoIP) service.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin, to establish a VoIP service using short DRX cycle as taught by Park, the motivation being, if a short DRX cycle is started, the UE may not monitor the PDCCH during the DRX sleep period, but may perform the PDCCH monitoring only during the on-duration interval, thereby reducing the power consumption (see Park, para 113).
Regarding Claim 11, Lin discloses the method of claim 1, but does not disclose details regarding: the first service is a service related to autonomous driving.
In the same field of endeavor, Park teaches this limitation: see para 271, The UE device includes various forms of the communication devices in which interactive services using SLs are supported for services such as Internet access, service performance, navigation, real-time information, autonomous driving, safety, and risk diagnosis.
It would have been obvious to one having ordinary skill in the art, before the effective filing date of the claimed invention, to modify the teaching of Lin, to include service related to autonomous driving as taught by Park, the motivation being, the motivation being for performing the DRX operations in a new radio (NR) vehicle to everything (V2X) (see Park, Background).
Response to Arguments
Applicant's arguments filed 6/15/2026 have been fully considered but they are not persuasive as detailed below:
The 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph for claims 1 and 14 are withdrawn based on claim amendments.
On page 7, regarding claim 1, the Applicant argues that: “… Lin does not disclose a DCR message, which is a message for establishing a unicast connection, nor does Lin disclose a feature in which a DRX operation is performed for receiving such a message. The wake-up signal of Lin relied upon by the Examiner is exchanged only between UEs that are already associated and merely wakes a known UE, and it does not relate to a unicast connection.”
The Examiner respectfully disagrees.
Amended claim 1 recites: “… A method comprising: obtaining, by a first user equipment (UE), at least one inter-UE discontinuous reception (DRX) configuration; determining to use a first inter-UE DRX configuration for a reception of a message for establishing a unicast connection, among the at least one inter-UE DRX configuration, based on a first service; receiving, from a second UE, first inter-UE control information for scheduling of an inter-UE physical shared channel through an inter-UE physical control channel, based on an active time of the first inter-UE DRX configuration; and receiving, from the second UE, the message for establishing the unicast connection and second inter-UE control information through the inter-UE physical shared channel, based on the active time, wherein the at least one inter-UE DRX configuration is configured for each unicast service”.
Amended Claim 1 does not recite the limitation “…DCR message, which is a message for establishing a unicast connection…”. This limitation is in claim 6, and is taught by a combination of Lin and Fu and detailed above in the claim 6 rejection.
The same argument applies to the other independent claims 14-15.
Conclusion
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 DEEPA BELUR whose telephone number is (571)270-3722. The examiner can normally be reached M-F 8 am - 4:30 pm.
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, Kevin Bates can be reached at 571-272-3980. 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.
/DEEPA BELUR/Primary Examiner, Art Unit 2472
Prosecution Insights