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 .
Response to Amendment
Applicant’s amendment filed on March 13, 2026, has been entered. Claims 5-9 are presently pending with claims 5, 6, 8, and 9 being independent. Claims 1-4 are canceled. Claims 5-9 are currently amended.
Response to Arguments
Applicant's arguments, pages 6-12, filed March 13, 2026, have been fully considered but they are not persuasive.
In response to applicant's argument that the examiner's conclusion of obviousness is based upon improper hindsight reasoning, it must be recognized that any judgment on obviousness is in a sense necessarily a reconstruction based upon hindsight reasoning. But so long as it takes into account only knowledge which was within the level of ordinary skill at the time the claimed invention was made, and does not include knowledge gleaned only from the applicant's disclosure, such a reconstruction is proper. See In re McLaughlin, 443 F.2d 1392, 170 USPQ 209 (CCPA 1971).
Applicant argues, concerning Eklof et al. (US 2022/0201582 A1; hereinafter Eklof), that “at most, the cited text indicates that an RRCReconfiguration and an associated condition may be provided, without explaining the internal configuration or data structure of that message. Indeed, Eklof does not teach a list that includes plural pieces of information corresponding to candidate cells together with associated transition conditions. However, the claims do not require an explanation of the internal configuration or data structure of the message. Eklof teaches that there may be many cells or beams reported as possible CHO candidates, that the network may issue conditional handover commands for several such candidates, and that the RRCConnectionReconfiguration for each candidate may differ in handover execution condition and random access information. Eklof further teaches that conditional handover related configurations may be for a list of cell(s) and may comprise both an RRCReconfiguration message and triggering condition configuration. Thus, Eklof teaches providing multiple candidate cell configurations with their associated CHO execution conditions. Moreover, Deenoo et al. (US 2020/0154326 A1; hereinafter Deenoo) teaches a reconfiguration message with one or more conditional mobility IEs per candidate target cell, a conditional reconfiguration containing information associated with a plurality of targets, and a plurality of trigger conditions where each trigger is associated with a conditional reconfiguration, e.g., a pair of reconfiguration and trigger condition associated with a target cell. Accordingly, even if Eklof alone did not describe the internal data structure of the message, the combined teachings of Eklof and Deenoo render obvious configuring the CHO message as an information element containing a list of plural candidate cell information together with associated transition conditions. Applicant’s argument addresses Eklof in isolation and does not rebut the teachings of the combination. See Eklof ¶¶ [0123], [0145]-[0148], and [0159]-[0161].
Next, applicant argues that Eklof is “completely silent as to how the plurality of candidate-cell information and the transition conditions are configured within the RRCReconfiguration.” That the “limitation specifically requires that the plural pieces of information on candidate cells and transition conditions are configured in one information element.” However, Eklof teaches that there may be many cells or beams reported as possible CHO candidates, that the network may issue conditional handover commands for several such candidates, and that the RRCConnectionReconfiguration for each candidate may differ in handover execution condition and random access information. The conditional handover related configurations may be for a cell or a list of cells and may comprise both an RRCReconfiguration message and triggering condition configuration. The rejection is based on the combination of Eklof and Deenoo, not Eklof alone. Deenoo teaches RRC connection reconfiguration including one or more conditional mobility information elements per candidate target cell, a conditional reconfiguration containing information associated with a plurality of targets, and pairs of reconfiguration and trigger condition associated with target cells. Thus, even assuming Eklof does not describe the exact internal arrangement of the RRCReconfiguration, Deenoo teaches configuring plural candidate cell information and corresponding transition conditions together in information elements. It would have been obvious to implement Eklof’s multiple candidate CHO configurations using Deenoo’s per candidate conditional mobility IE structure to maintain the association between each candidate cell and its corresponding execution condition and to efficiently signal multiple CHO candidates in one message. See Eklof ¶¶ [0123], [0145]-[0148], and [0159]-[0161]; Deenoo ¶¶ [0078], [0103], [0120], and [0142].
Applicant argues that Deenoo “does not disclose or suggest a specific information element containing a list, or plural candidate cell information together with associated transition conditions in that list.” Applicant further states that “Deenoo is silent as to how any candidate cell information and transition conditions are actually configured within the message. It does not describe a list structure and does not explain that the candidate cell information and corresponding transition conditions are configured together in one information element. In fact, the paragraph [0103] expressly contemplates that the reconfiguration and triggering condition configuration may be provided in different messages, which is contrary to the claimed arrangement.” However, applicant addresses paragraph [0103] of Deenoo in isolation. Deenoo further teaches that an RRC connection reconfiguration may include one or more conditional mobility IEs per candidate target cell, that one conditional reconfiguration may contain information associated with a plurality of targets, and that a WTRU may be configured with a plurality of trigger conditions where each trigger is associated with a conditional reconfiguration, e.g., a pair of reconfiguration and trigger condition associated with a target cell. Deenoo’s statement in paragraph [0103] that the reconfiguration and triggering condition configuration may be provided in different messages is merely an alternative embodiment and does not negate Deenoo’s teaching that they may be provided in the same message or as multiple instances within the same message. The rejection is based on the combined teachings of Eklof and Deenoo. It would have been obvious to configure Eklof’s multiple CHO candidate cell configurations using Deenoo’s per candidate conditional mobility IE structure so that each candidate cell is associated with its corresponding transition condition in the CHO message.
Applicant argues that 3GPP TS 36.331 version 15.6.0 Release 15 (Radio Resource Control (RRC); hereinafter 3GPP RRC) and Chang et al. (US 2022/0322173 A1; hereinafter Chang) do not teach a list including “plural pieces of information on candidate cells and transition conditions associated with the candidate cells.” The rejection does not rely on 3GPP RRC or Chang for teaching the claimed information element of plural candidate cell information and associated transition conditions.
Applicant does not make specific arguments related to dependent claim 7. The rejection of claim 7 is maintained along with the rejection of the independent claims for the reasons stated above.
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.
Claims 5-9 are rejected under 35 U.S.C. 103 as being unpatentable over Eklof et al. (US 2022/0201582 A1; hereinafter Eklof) in view of Deenoo et al. (US 2020/0154326 A1; hereinafter Deenoo) further in view of 3GPP TS 36.331 version 15.6.0 Release 15 (Radio Resource Control (RRC); hereinafter 3GPP RRC) and Chang et al. (US 2022/0322173 A1; hereinafter Chang).
Regarding claim 5, Eklof teaches a terminal comprising (read as a wireless device or user equipment (UE) (FIG. 11, element 1100 UE; ¶ [0036] User Equipment.):
a receiver that receives, from a source radio base station (read as network node or source node), a message which has an information element in which a list is configured, the list including plural pieces of information on candidate cells (read as target information) and transition conditions (read as triggering condition) associated with the candidate cells (FIG. 6, element 600 Network Node; Fig. 8, step 4 Conditional HO Command; FIG. 11, element 1135 receiver; ¶ [0090] The wireless device includes communication circuitry. The communication circuitry is configured to receive information from nodes.; ¶ [0123] There may often be many cells or beams that the UE reported as possible candidates. The network should issue conditional handover commands for several of those candidates. The RRCConnectionReconfiguration for each of those candidates may differ, e.g. in terms of the HO execution condition.; ¶ [0125] A conditional HO command is sent to the UE by the serving gNB.; ¶ [0145] A UE configured with a set of conditional RRCReconfiguration(s) shall execute a conditional handover when the condition for the handover is fulfilled. Conditional handover configuration(s) may be for a cell or list of cells.; ¶ [0150] RRCReconfiguration with a reconfigurationWithSync (field containing configuration necessary to execute handover, like target information).; ¶ [0158] The network configures the UE with triggering conditions.; ¶ [0159] The source node may send a conditional handover (CHO) configuration to the UE, including the prepared RRCReconfiguration as well as a condition associated with the RRCReconfiguration.; [0161] A HO command type of message contains HO triggering condition(s) and dedicated RRC configuration(s).; ¶ [0361] A receiver.);
a transmitter that transmits a complete message (read as RRCReconfigurationComplete), in which the transaction ID (read as rrc-TransactionIdentifier) included in the one piece of information on the one candidate cell is included, to the target radio base station (read as suitable cell or towards that cell or target node) when the processor performs the transition (read as performs CHO execution) to the target radio base station, wherein the processor includes, in the complete message (read as RRCReconfiguration-Complete message), information for notifying of the radio link failure (read as a failure report is available) (FIG. 5, element 520 Communication Circuitry; element 510 Processing Circuitry; FIG. 11, element 1133 transmitter, element 1101 processor; ¶ [0090] The wireless device includes communication circuitry. The communication circuitry is configured to transmit information to nodes. The processing circuitry is configured to perform processing, such as by executing instructions stored in memory. The processing circuitry in this regard may implement certain function units.; ¶ [0159] The UE executes the CHO. The UE performs random access and synchronization towards the potential target node and transmits an RRCReconfigurationComplete to the target node.; ¶ [0200] The UE performs CHO execution towards that cell and sends an RRCReconfigurationComplete. Include in the RRCReconfiguration-Complete message an indication that a failure report is available, for the network may request it.; ¶ [0222] The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration.; page 14 code, RRCReconfigurationComplete message, RRCReconfigurationComplete ::= SEQUENCE {rrc-TransactionIdentifier…}),
Eklof does not explicitly teach a transaction ID being included in a piece of information on each candidate cell; a processor that performs, based on one transition condition included in the list in the message, a synchronization with one candidate cell associated with the one transition condition and performs a transition to a target radio base station which configures one piece of information on the one candidate cell, without transmitting a re-establishment request message, when a radio link failure is detected during a random access procedure.
In analogous art, Deenoo teaches a transaction ID (read as identity) being included in a piece of information on each candidate cell (read as target) (¶ [0078] One or more conditional mobility information elements (IEs) per candidate target cell.; ¶ [0103] A reconfiguration element may be associated with a specific target. Either the reconfiguration message may carry an identity associated with the configuration of the triggering condition or the triggering condition may carry an identity associated with the reconfiguration message.; ¶ [0186] A list of conditional reconfiguration identities (condReconfigID) may also be linked in reconfigID. A condReconfigID may include events that need to be satisfied to apply a corresponding reconfiguration associated with that or a given measurement object.);
a processor that performs, based on one transition condition included in the list in the message, a synchronization with one candidate cell associated with the one transition condition (read as trigger condition) and performs a transition (read as random access operation) to a target radio base station which configures one piece of information on one candidate cell (read as selected cell), without transmitting a re-establishment request message (read as instead of re-establishment request), when a radio link failure is detected during a random access procedure (FIG. 1B, element 118 processor; FIG. 2, illustrates trigger condition; ¶ [0030] A processor.; ¶ [0079] When a trigger condition is satisfied or met, a contention free RACH resource may be selected and random access operation performed.; ¶ [0086] The PRACH resource configuration may also be associated with a RS that may correspond to a new radio synchronization sequence (NR-SS).; ¶ [0087] A PRACH resource configuration may be received in relation to a handover.; ¶ [0171] When a trigger condition is satisfied, the WTRU may apply the conditional reconfiguration. The WTRU may access the target cell associated with the trigger condition using selected random access resources.; ¶ [0186] A list of conditional reconfiguration identities (condReconfigID). A condReconfigID may include events that need to be satisfied to apply a corresponding reconfiguration.; ¶ [0191] A conditional reconfiguration message that includes a trigger condition and configuration information for handover to a target cell.; ¶ [0208] WTRU may perform cell selection upon a radio link failure. If a WTRU determines that the conditional reconfiguration for the selected cells exists, then the WTRU may perform actions as if trigger conditions are satisfied towards that selected cell. The WTRU may transmit an RRC reconfiguration complete indicating successful conditional reconfiguration to the target cell instead of a re-establishment request.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine transitioning to a target cell without a re-establishment request taught by Deenoo with conditional handover taught by Eklof. One would have been motivated to do so in order to minimize handover delays and improve reliability, which would result in increased user satisfaction, by using the conditional handover mechanism while avoiding the delay associated with re-establishment (Deenoo: ¶¶ [0002-0003]).
Eklof and Deenoo do not explicitly teach wherein the processor resumes a radio bearer suspended due to the radio link failure in a case of performing the synchronization with the one candidate cell.
In analogous art, 3GPP RRC teaches wherein the processor resumes a radio bearer (read as SRB1) suspended due to the radio link failure in a case of performing the synchronization with the one candidate cell (read as target PCell) (§5.3.5.4 start synchronizing to the DL of the target PCell; §5.3.7.2 upon detecting radio link failure; §5.3.7.5 re-establish RLC for SRB1, resume SRB1).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the resumption of a radio bearer taught by 3GPP RRC with transitioning to a target cell without a re-establishment request taught by Deenoo and conditional handover taught by Eklof. One would have been motivated to do so in order to recover from radio link failures faster reducing service interruption and latency, which would result in increased user satisfaction, by resuming a radio bearer to reactivate suspended communication with minimal overhead.
Eklof, Deenoo, and 3GPP RRC do not explicitly teach wherein the synchronization is executed as part of a conditional handover (CHO) procedure.
In analogous art, Chang teaches wherein the synchronization is executed as part of a conditional handover (CHO) procedure (¶ [0070] The operation of executing a conditional handover includes one or a plurality of the following: synchronization to the target cell is performed.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine synchronization during handover as taught by Chang with the resumption of a radio bearer taught by 3GPP RRC, transitioning to a target cell without a re-establishment request taught by Deenoo and conditional handover taught by Eklof. One would have been motivated to do so in order to reduce handover latency and improve service continuity by executing synchronization during conditional handover, avoiding delays of a re-establishment request and promptly restoring suspended radio bearers (Chang: ¶¶ [0002-0004]).
Regarding claims 6, 8, and 9, Eklof teaches a terminal comprising (read as a wireless device or user equipment (UE) (FIG. 11, element 1100 UE; ¶ [0036] User Equipment.):
a receiver that receives, from a source radio base station (read as network node or source node), a first message which has an information element in which a list is configured, the list including plural pieces of information on candidate cells (read as target information) and transition conditions (read as triggering condition) associated with the candidate cells (FIG. 6, element 600 Network Node; Fig. 8, step 4 Conditional HO Command; FIG. 11, element 1135 receiver; ¶ [0090] The wireless device includes communication circuitry. The communication circuitry is configured to receive information from nodes.; ¶ [0123] There may often be many cells or beams that the UE reported as possible candidates. The network should issue conditional handover commands for several of those candidates. The RRCConnectionReconfiguration for each of those candidates may differ, e.g. in terms of the HO execution condition.; ¶ [0125] A conditional HO command is sent to the UE by the serving gNB.; ¶ [0145] A UE configured with a set of conditional RRCReconfiguration(s) shall execute a conditional handover when the condition for the handover is fulfilled. Conditional handover configuration(s) may be for a cell or list of cells.; ¶ [0150] RRCReconfiguration with a reconfigurationWithSync (field containing configuration necessary to execute handover, like target information).; ¶ [0158] The network configures the UE with triggering conditions.; ¶ [0159] The source node may send a conditional handover (CHO) configuration to the UE, including the prepared RRCReconfiguration as well as a condition associated with the RRCReconfiguration.; [0161] A HO command type of message contains HO triggering condition(s) and dedicated RRC configuration(s).; ¶ [0361] A receiver.);
a transmitter that transmits a complete message (read as RRCReconfigurationComplete), in which the transaction ID (read as rrc-TransactionIdentifier) included in the one piece of information on the one candidate cell is included, to the target radio base station (read as suitable cell or towards that cell or target node) when the processor performs the transition (read as performs CHO execution) to the target radio base station, (FIG. 5, element 520 Communication Circuitry; element 510 Processing Circuitry; FIG. 11, element 1133 transmitter, element 1101 processor; ¶ [0090] The wireless device includes communication circuitry. The communication circuitry is configured to transmit information to nodes. The processing circuitry is configured to perform processing, such as by executing instructions stored in memory. The processing circuitry in this regard may implement certain function units.; ¶ [0159] The UE executes the CHO. The UE performs random access and synchronization towards the potential target node and transmits an RRCReconfigurationComplete to the target node.; ¶ [0200] The UE performs CHO execution towards that cell and sends an RRCReconfigurationComplete. Include in the RRCReconfiguration-Complete message an indication that a failure report is available, for the network may request it.; ¶ [0222] The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration.; page 14 code, RRCReconfigurationComplete message, RRCReconfigurationComplete ::= SEQUENCE {rrc-TransactionIdentifier…}),
wherein the processor includes, in a second message different from the complete message (read as RLF report), at least one of information on a cell in which the radio link failure is detected and information on a location of the terminal where the radio link failure is detected during the random access procedure (read as to connect to a target cell), wherein the transmitter transmits, to the target radio base station (read as target), the second message including the at least one of the information on the cell and the information on the location of the terminal therein ((FIG. 5, element 520 Communication Circuitry; element 510 Processing Circuitry; ¶ [0009] The failure is caused by failure of the wireless device to connect to target cell. The failure is caused by radio link failure. The failure is caused by a random access problem.; ¶ [0090] The wireless device includes communication circuitry 520. The communication circuitry is configured to transmit information to nodes.; ¶ [0090] The processing circuitry is configured to perform processing, such as by executing instructions stored in memory. The processing circuitry in this regard may implement certain function units.; ¶ [0134] The RLF report contains various types of information to the failure, e.g., which cell the UE failed in, measurements for that cell and other types of information that the network might need.; ¶ [0135] RLF report logs information associated to the time and location where the failure has occurred. The UE transmits the report to the target.).
Eklof does not explicitly teach a transaction ID being included in a piece of information on each candidate cell; a processor that performs, based on one transition condition included in the list in the message, a synchronization with one candidate cell associated with the one transition condition and performs a transition to a target radio base station which configures one piece of information on the one candidate cell, without transmitting a re-establishment request message, when a radio link failure is detected during a random access procedure.
In analogous art, Deenoo teaches a transaction ID (read as identity) being included in a piece of information on each candidate cell (read as target) (¶ [0078] One or more conditional mobility information elements (IEs) per candidate target cell.; ¶ [0103] A reconfiguration element may be associated with a specific target. Either the reconfiguration message may carry an identity associated with the configuration of the triggering condition or the triggering condition may carry an identity associated with the reconfiguration message.; ¶ [0186] A list of conditional reconfiguration identities (condReconfigID) may also be linked in reconfigID. A condReconfigID may include events that need to be satisfied to apply a corresponding reconfiguration associated with that or a given measurement object.);
a processor that performs, based on one transition condition included in the list in the message, a synchronization with one candidate cell associated with the one transition condition (read as trigger condition) and performs a transition (read as random access operation) to a target radio base station which configures one piece of information on one candidate cell (read as selected cell), without transmitting a re-establishment request message (read as instead of re-establishment request), when a radio link failure is detected during a random access procedure (FIG. 1B, element 118 processor; FIG. 2, illustrates trigger condition; ¶ [0030] A processor.; ¶ [0079] When a trigger condition is satisfied or met, a contention free RACH resource may be selected and random access operation performed.; ¶ [0086] The PRACH resource configuration may also be associated with a RS that may correspond to a new radio synchronization sequence (NR-SS).; ¶ [0087] A PRACH resource configuration may be received in relation to a handover.; ¶ [0171] When a trigger condition is satisfied, the WTRU may apply the conditional reconfiguration. The WTRU may access the target cell associated with the trigger condition using selected random access resources.; ¶ [0186] A list of conditional reconfiguration identities (condReconfigID). A condReconfigID may include events that need to be satisfied to apply a corresponding reconfiguration.; ¶ [0191] A conditional reconfiguration message that includes a trigger condition and configuration information for handover to a target cell.; ¶ [0208] WTRU may perform cell selection upon a radio link failure. If a WTRU determines that the conditional reconfiguration for the selected cells exists, then the WTRU may perform actions as if trigger conditions are satisfied towards that selected cell. The WTRU may transmit an RRC reconfiguration complete indicating successful conditional reconfiguration to the target cell instead of a re-establishment request.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine transitioning to a target cell without a re-establishment request taught by Deenoo with conditional handover taught by Eklof. One would have been motivated to do so in order to minimize handover delays and improve reliability, which would result in increased user satisfaction, by using the conditional handover mechanism while avoiding the delay associated with re-establishment (Deenoo: ¶¶ [0002-0003]).
Eklof and Deenoo do not explicitly teach wherein the processor resumes a radio bearer suspended due to the radio link failure in a case of performing the synchronization with the one candidate cell.
In analogous art, 3GPP RRC teaches wherein the processor resumes a radio bearer (read as SRB1) suspended due to the radio link failure in a case of performing the synchronization with the one candidate cell (read as target PCell) (§5.3.5.4 start synchronizing to the DL of the target PCell; §5.3.7.2 upon detecting radio link failure; §5.3.7.5 re-establish RLC for SRB1, resume SRB1).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the resumption of a radio bearer taught by 3GPP RRC with transitioning to a target cell without a re-establishment request taught by Deenoo and conditional handover taught by Eklof. One would have been motivated to do so in order to recover from radio link failures faster reducing service interruption and latency, which would result in increased user satisfaction, by resuming a radio bearer to reactivate suspended communication with minimal overhead.
Eklof, Deenoo, and 3GPP RRC do not explicitly teach wherein the synchronization is executed as part of a conditional handover (CHO) procedure.
In analogous art, Chang teaches wherein the synchronization is executed as part of a conditional handover (CHO) procedure (¶ [0070] The operation of executing a conditional handover includes one or a plurality of the following: synchronization to the target cell is performed.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine synchronization during handover as taught by Chang with the resumption of a radio bearer taught by 3GPP RRC, transitioning to a target cell without a re-establishment request taught by Deenoo and conditional handover taught by Eklof. One would have been motivated to do so in order to reduce handover latency and improve service continuity by executing synchronization during conditional handover, avoiding delays of a re-establishment request and promptly restoring suspended radio bearers (Chang: ¶¶ [0002-0004]).
Regarding claim 7, Eklof teaches wherein the processor includes, in a message different from the complete message (read as RLF report), the at least one of the information on the cell and the information on the location of the terminal (read as UE), based on an instruction (read as request) from a network (FIG. 5, element 510 Processing Circuitry; ¶ [0090] The processing circuitry is configured to perform processing, such as by executing instructions stored in memory. The processing circuitry in this regard may implement certain function units.; ¶ [0127] The network can request information from the UE.; ¶ [0134] The RLF report contains various types of information to the failure, e.g., which cell the UE failed in, measurements for that cell and other types of information that the network might need.; ¶ [0135] The target node may request the UE to report the stored RLF report. RLF report logs information associated to the time and location where the failure has occurred. The UE transmits the report to the target.).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Johansson et al. (US 2014/0133465 A1) discloses “Radio Link Failure Report Extensions in Mobile Communication Networks”
Latheef et al. (US 2020/0351744 A1) discloses “Method and Apparatus for Executing Conditional Handover in Wireless Communication Network”
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 DAVID M KAYAL whose telephone number is (703)756-4576. The examiner can normally be reached M-F 8-5 ET.
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, Ricky Ngo can be reached at 571-272-3139. 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.
/D.M.K./Examiner, Art Unit 2464
/RICKY Q NGO/Supervisory Patent Examiner, Art Unit 2464
Prosecution Insights