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 .
DETAILED ACTION
In the amendment filed August 7, 2026, claims 1, 2, 5 and 6 have been amended, claims 1-3 and 5-7 are currently pending for examination.
Response to Arguments
Regarding claim objections applicant’s arguments, see page 5 paragraphs 3, filed August 7, 2026, with respect to claims 2 and 6 have been fully considered and are persuasive. The claim objections of claims 2 and 6 have been withdrawn.
Regarding 35 U.S.C. 103 applicant’s arguments, see page 5 paragraphs 4 - page 9 paragraphs 1-3, filed August 7, 2026, with respect to claims 1-3 and 5-7 have been fully considered and are not persuasive.
Regarding claims 1 and 5, the applicant first argued that, see page 6, “…Applicant respectfully submits that the cited references do not teach or suggest such subject matter. For example, claim 1 of Kuppuswamy recites "us[ing] a first portion of the RU port identifier to identify an endpoint group." Kuppuswamy at claim 1. However, in Kuppuswamy, the "first portion of the RU port identifier corresponds to a group index and the second portion of the RU port identifier corresponds to a per-group layer/stream index." Id. At claim 4. The different portions of the RU port identifier are to send a single eAxC message to the RU endpoint. See id. at claims 1 and 4. However, this cannot be relied upon to allegedly teach or suggest the claimed features of "receiving a control plane message from an O-RAN distributed unit (O-DU)," and "extending a control plane message of a representative eAxC_ID to a control plane message of at least one member eAxC_ID corresponding to the representative eAxC_ID based on the configuration information for the eAxC_ID group." Also, the group index in Kuppuswamy cannot be used to allegedly teach or suggest the eAxCID group supporting Section Extension 10.
In response to applicant's argument, the examiner respectfully disagrees with the argument above.
Regarding amended claims 1 and 5, Kuppuswamy disclose a method performed by a middle node (see Fig.1, para. 30, an open fronthaul (FH) interface / a middleware/node between the DU 180A and the RU 180B, combination of RU and FH) in a communication system, the method comprising:
receiving a request message for capability information from a controller (see Fig.1, Fig.8, para. 121, the DU requesting capability information from RU 802 and open fronthaul (FH) interface);
transmitting capability information of the middle node in response to the request message (see para. 122, the RU 802 transmits capability information 810 of the open fronthaul (FH) interface that is received by the DU 804); and receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group supporting Section Extension 10 based on the capability information of the middle node from the controller (see Fig.8, steps, 820, 830, 834, 850, para. 124, 129-136, the DU 804 transmits an eAxC allocation configuration 830 that is received by the RU 802 / receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group, the eAxC allocation configuration 830 indicate whether the DU 804 is applying the first encoding technique or the second encoding technique to the RU port identifiers of an eAxC message. The eAxC allocation configuration 830 additionally or alternatively indicate a mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration 830 may indicate that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group and At 840, the RU 802 configure endpoint groups based on the eAxC allocation configuration 830. The RU 802 use the group index to determine where (e.g., to which hardware component) to route the eAxC message for processing, see also Figs.9-Figs.13, para.146, At 908, the RU uses a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group, as described in connection with 864 of FIG. 8. For example, 908 is performed by a second portion component 1346 of the apparatus 1302 of FIG. 13. See also para. 0149-0153); receiving a control plane message from an O-RAN distributed unit (0-DU) (see Fig.1, para. 30, 71-72, the O-RAN includes an open fronthaul (FH) interface between the DU and the RU, see also Fig.8, para. 75, 76, 136, the DU 804 an O-RAN transmits an eAxC allocation configuration 830 that the RU 802 use to configure the endpoints groups (e.g., at 840) / receiving a control plane message, the RU 802 determines that a first eAxC message of the eAxC messages 834 corresponds to a PRACH control plane message based on properties of the first eAxC message, see also para. 121, Fig.16, para. 203-231, the DU facilitates communication in an O-RAN. At 1602, the DU receives capability information indicating support of endpoint groups from an RU, as described in connection with the capability information 810 of FIG. 8, see also Fig.5, para. 81; and extending a control plane message (see para. 79, Fig.5, para. 85, 86, for uplink eAxC allocations 518 and downlink eAxC allocations 516, when the RU receives a message, such as a control plane message, the RU determines the hardware component to route the message to for processing) of a representative eAxC_ID to a control plane message of at least one member eAxC_ID corresponding to the representative eAxC_ID based on the configuration information for the eAxCID group (see Claim1, para. 89, 168, the RU receives an eAxC message from the DU, as described in connection with the eAxC message 850 of FIG. 8. For example, 1104 may be performed by a message component 1342 of the apparatus 1302 of FIG. 13. The eAxC message may include an M-plane message, a C-plane message, see also para. 248, The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include a DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC identifier 400 of FIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier 610 of FIG. 6 and/or the RU port identifier 710 of FIG. 7. The group index and the per-group layer/stream index may be based on the capability information, see also para. 135, Fig.8, para. 136, 180, the DU 804 transmits an eAxC allocation configuration 830 that the RU 802 uses to configure the endpoints groups (e.g., at 840)).
Regarding claims 1 and 5, the applicant second argued that, see page 7 paragraphs 1-3, “…Moreover, Bachu cannot be relied upon to cure the deficiencies of Kuppuswamy of not teaching the claimed "middle node." The Examiner appears to allege that the fronthaul multiplexing (FHM) 220 in Buchu can serve as an interface between the RU 225 and DU 215. However, the Examiner failed to demonstrate how the FHM can send the transmitting capability information and receiving configuration information for the eAxCID group supporting Section Extension 10. Therefore, Bachu cannot be combined with Kuppuswamy to allegedly teach or suggest claim 1.Therefore, Applicant respectfully submits that the cited references, either individually or in combination, do not teach or suggest claim 1. Based on at least the above reasons, Applicant respectfully submits that independent claim 1 is patentable over the cited references.
In response to applicant's argument, the examiner respectfully disagrees with the argument above.
In response to applicant's arguments against the references individually, one cannot show nonobviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986).
Regarding amended claims 1 and 5, Buchu clearly disclose a fronthaul multiplexer (FHM) as “a middle node” (see Fig.2, an FHM 220, see para. 0084-0085, FHM 220 / a middle node serve as an interface between the RU 225 and DU 215 and multiplex information received from RUs 225 before providing the information to DU 215 and/or demultiplex information received from DU 215 before providing the information to the RUs 225, see also para. 0085-0087).
Under the broadest reasonable interpretation, the combination of the systems as disclosed by Kuppuswamy and Buchu reads upon “receiving a request message for capability information from a controller; transmitting capability information of the middle node in response to the request message; receiving configuration information for an extended antenna carrier (eAxC)_ identifier (ID) group supporting Section Extension 10 based on the capability information of the middle node from the controller; receiving a control plane message from an O-RAN distributed unit (O-DU); and extending a control plane message of a representative eAxCID to a control plane message of at least one member eAxCID corresponding to the representative eAxCID based on the configuration information for the eAxCID group” as recites in the claim.
The applicant further argues, see page 7 paragraphs 4-5 , that “Dependent claims 2-3 and 6-7 each depend from one of independent claims 1 and 5 described above. Accordingly, Applicant respectfully submits that claims 2-3 and 6-7 are patentable at least due to their respective dependencies and the additional features recited therein. Withdrawal of the pending rejections of these claims is, therefore, respectfully requested.”
The examiner respectfully disagrees with the argument above, per above cites reasons the above listed claims are not allowable.
Regarding claims 1 and 5, the applicant third argued that, see page 7 paragraphs 6 – page 9 paragraphs 1-3, “…Additionally, as noted above, Bachu cannot be relied upon to cure the deficiencies of Hu that does not teach the claimed "middle node" to perform the claimed features. The Examiner appears to allege that the fronthaul multiplexing (FHM) 220 in Buchu can serve as an interface between the RU 225 and DU 215. However, the Examiner failed to demonstrate how the FHM can send the transmitting capability information and receiving configuration information for the eAxCID group supporting Section Extension 10. Therefore, Bachu cannot be combined with Hu to allegedly teach or suggest claim 1. Therefore, Applicant respectfully submits that the cited references, either individually or in combination, do not teach or suggest claim 1. Based on at least the above reasons, Applicant respectfully submits that independent claim 1 is patentable over the cited references.
In response to applicant's argument, the examiner respectfully disagrees with the argument above. See below rejections in view of the claim amendments.
Regarding amended claims 1 and 5, Hu clearly teaches, A method performed by fronthaul interface (see Fig.1, O-RAN Open Fronthaul interface (OFH I/F) 103) in a communication system, the method comprising: receiving a request message for capability information from a controller (see Fig.1, Fig.6, before the operation 601, the method further includes receiving a request message and reporting information related to second endpoints to an O-DU, the information related to second endpoints being used by the O-DU to determine the first endpoint); transmitting capability information of the fronthaul interface the middle node in response to the request message (see para. 0118, the information transmitted related to second endpoints includes a first capability and a second capability possessed by the second endpoints, wherein the first capability indicates that the second endpoints support a first information section extension, and the second capability indicates a maximum value of a number of pieces of the first information supported by the second endpoints); and receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group supporting Section Extension 10 based on the capability information of the fronthaul interface from the controller (see Fig.6, para. 0110, 0209, when the first control-plane message includes a section extension whose extension type is 10, it indicates that the first information will be applied to a group of endpoints. That is, one eAxCid is used to indicate the section description of a group of eAxCids, and then the first information will be applied to the endpoints corresponding to all eAxCids in the group, see also para. 0209, ,see also 0127-0132, if the first control-plane message further includes a section extension for indicating a group of extended antenna-carrier identifiers, operation 602 includes performing the operation related to the first information in endpoints corresponding to the group of extended antenna-carrier identifiers, according to the first control-plane message, see also para. 0286-0293); receiving a control plane message from an O-RAN distributed unit (O-DU) (see para. 0078, receiving a control plane message from an O-DU, see also Fig.6. para. 0113-0116, Operation 601: receiving a first control-plane message from an O-DU, the first control-plane message being used for indicating a first endpoint in the O-RU to perform an operation related to first information); and extending a control plane message of a representative eAxCID to a control plane message of at least one member eAxCID corresponding to the representative eAxCID based on the configuration information for the eAxCID group (see para. 0110, 0209, extending a control plane message of an eAxCID to a control plane message of at least one member eAxCID corresponding to the eAxCID based on the configuration information for the eAxCID group, 0210-0223, 0292-0297, 0301), the Examiner further states that Buchu teaches a fronthaul multiplexer (FHM) as “a middle node” (see Fig.2, an FHM 220, see para. 0084-0085, FHM 220 / a middle node serve as an interface between the RU 225 and DU 215 and multiplex information received from RUs 225 before providing the information to DU 215 and/or demultiplex information received from DU 215 before providing the information to the RUs 225).
In response to applicant's arguments against the references individually, one cannot show nonobviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986).
Under the broadest reasonable interpretation, the combination of the systems as disclosed by Hu and Buchu reads upon “receiving a request message for capability information from a controller; transmitting capability information of the middle node in response to the request message; receiving configuration information for an extended antenna carrier (eAxC)_ identifier (ID) group supporting Section Extension 10 based on the capability information of the middle node from the controller; receiving a control plane message from an O-RAN distributed unit (O-DU); and extending a control plane message of a representative eAxCID to a control plane message of at least one member eAxCID corresponding to the representative eAxCID based on the configuration information for the eAxCID group” as recites in the claim.
Notice re prior art available under both pre-AIA and AIA
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 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.
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 of this title, 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 1-3 and 5-7 are rejected under 35 U.S.C. 103 as being unpatentable over Kuppuswamy et al. (US Patent No.: 11,516,721), and further in view of Bachu et al. (US Pub. No.: 2024/0067997).
As per claim 1, Kuppuswamy disclose A method performed by a middle node (see Fig.1, para. 30, an open fronthaul (FH) interface / a middleware/node between the DU 180A and the RU 180B, combination of RU and FH) in a communication system, the method comprising:
receiving a request message for capability information from a controller (see Fig.1, Fig.8, para. 121, the DU requesting capability information from RU 802 and open fronthaul (FH) interface);
transmitting capability information of the middle node in response to the request message (see para. 122, the RU 802 transmits capability information 810 of the open fronthaul (FH) interface that is received by the DU 804); and
receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group supporting Section Extension 10 based on the capability information of the middle node from the controller (see Fig.8, steps, 820, 830, 834, 850, para. 124, 129-136, the DU 804 transmits an eAxC allocation configuration 830 that is received by the RU 802 / receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group, the eAxC allocation configuration 830 indicate whether the DU 804 is applying the first encoding technique or the second encoding technique to the RU port identifiers of an eAxC message. The eAxC allocation configuration 830 additionally or alternatively indicate a mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration 830 may indicate that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group and At 840, the RU 802 configure endpoint groups based on the eAxC allocation configuration 830. The RU 802 use the group index to determine where (e.g., to which hardware component) to route the eAxC message for processing, see also Figs.9-Figs.13, para.146, At 908, the RU uses a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group, as described in connection with 864 of FIG. 8. For example, 908 is performed by a second portion component 1346 of the apparatus 1302 of FIG. 13. See also para. 0149-0153);
receiving a control plane message from an O-RAN distributed unit (0-DU) (see Fig.1, para. 30, 71-72, the O-RAN includes an open fronthaul (FH) interface between the DU and the RU, see also Fig.8, para. 75, 76, 136, the DU 804 an O-RAN transmits an eAxC allocation configuration 830 that the RU 802 use to configure the endpoints groups (e.g., at 840) / receiving a control plane message, the RU 802 determines that a first eAxC message of the eAxC messages 834 corresponds to a PRACH control plane message based on properties of the first eAxC message, see also para. 121, Fig.16, para. 203-231, the DU facilitates communication in an O-RAN. At 1602, the DU receives capability information indicating support of endpoint groups from an RU, as described in connection with the capability information 810 of FIG. 8, see also Fig.5, para. 81; and
extending a control plane message (see para. 79, Fig.5, para. 85, 86, for uplink eAxC allocations 518 and downlink eAxC allocations 516, when the RU receives a message, such as a control plane message, the RU determines the hardware component to route the message to for processing) of a representative eAxC_ID to a control plane message of at least one member eAxC_ID corresponding to the representative eAxC_ID based on the configuration information for the eAxCID group (see Claim1, para. 89, 168, the RU receives an eAxC message from the DU, as described in connection with the eAxC message 850 of FIG. 8. For example, 1104 may be performed by a message component 1342 of the apparatus 1302 of FIG. 13. The eAxC message may include an M-plane message, a C-plane message, see also para. 248, The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include a DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC identifier 400 of FIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier 610 of FIG. 6 and/or the RU port identifier 710 of FIG. 7. The group index and the per-group layer/stream index may be based on the capability information, see also para. 135, Fig.8, para. 136, 180, the DU 804 transmits an eAxC allocation configuration 830 that the RU 802 uses to configure the endpoints groups (e.g., at 840)).
Although Kuppuswamy disclose A method performed by a middle node (see Fig.1, para. 30, an open fronthaul (FH) interface / a middleware/node between the DU 180A and the RU 180B, combination of RU and FH) in a communication system).
Kuppuswamy however disclose “a middle node”;
Buchu however disclose a fronthaul multiplexer (FHM) as “a middle node” (see Fig.2, an FHM 220, see para. 0084-0085, FHM 220 / a middle node serve as an interface between the RU 225 and DU 215 and multiplex information received from RUs 225 before providing the information to DU 215 and/or demultiplex information received from DU 215 before providing the information to the RUs 225, see also para. 0085-0087).
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide the functionality of “a middle node”, as taught by Bachu, in the system of Kuppuswamy, so as to improve wireless communications within a CU/DU split configuration within a base station in an open radio access network (O-RAN) architecture, see Bachu, paragraphs 38-39.
As per claim 2, the combination of Kuppuswamy and Bachu disclose the method of claim 1.
Kuppuswamy further disclose wherein the capability information of the middle node comprises: information about a maximum number of eAxC_ID groups by the middle node being able to process and information about a maximum number of eAxC_IDs that can be included in one eAx D group (see Fig.11, para. 99, 164-165, the DU allocates eAxCIDs to each of the endpoints received in the capability information. For example, the DU allocates the 85 endpoints to 85 group layers/streams within the first three blocks 620, 622, 624. In some examples, the DU may determine to allocate a subset of the endpoints. For example, the DU may determine to allocate eAxCIDs to half of the endpoints of the first group 602. In such an example, the DU may allocate five bits to represent half of the endpoints (e.g., 25 endpoints) of the first group 602, may allocate five bits to represent the 25 endpoints of the second group 604, and may allocate four bits to represent the 10 endpoints of the third group 606, see also Fig.6, para. 95).
As per claim 3, the combination of Kuppuswamy and Bachu disclose the method of claim 1.
Kuppuswamy further disclose wherein the configuration information for the eAxD group comprises: information about a representative eAxC_ID of the eAxCID group and information about at least one member eAxC_ID included in the eAxC_ID group (see para. 99, 165, the DU determines to allocate eAxCIDs to half of the endpoints of the first group 602. In such an example, the DU may allocate five bits to represent half of the endpoints (e.g., 25 endpoints) of the first group 602, may allocate five bits to represent the 25 endpoints of the second group 604, and may allocate four bits to represent the 10 endpoints of the third group 606).
As per claim 5, claim 5 is rejected the same way as claim 1. Bachu further disclose A middle node (see Fig.2, Fig.6, FHM 220, a device 605) in a communication system, the middle node comprising: a transceiver (see Fig.6, a receiver 610 and a transmitter 615); a memory (see Fig.6, communications manager 620 with a CPU for storing / a memory); and at least one processor (see Fig.6, communications manager 620).
As per claim 6, claim 6 is rejected the same way as claim 2.
As per claim 7, claim 7 is rejected the same way as claim 3.
As per claim 8, claim 8 is rejected the same way as claim 4.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Claims 1 and 5 are rejected under 35 U.S.C. 103 as being unpatentable over Hu et al. (US Pub. No.: 2023/0112049), and further in view of Bachu et al. (US Pub. No.: 2024/0067997).
As per claim 1, Hu disclose A method performed by fronthaul interface (see Fig.1, O-RAN Open Fronthaul interface (OFH I/F) 103) in a communication system, the method comprising:
receiving a request message for capability information from a controller (see Fig.1, Fig.6, before the operation 601, the method further includes receiving a request message and reporting information related to second endpoints to an O-DU, the information related to second endpoints being used by the O-DU to determine the first endpoint);
transmitting capability information of the fronthaul interface the middle node in response to the request message (see para. 0118, the information transmitted related to second endpoints includes a first capability and a second capability possessed by the second endpoints, wherein the first capability indicates that the second endpoints support a first information section extension, and the second capability indicates a maximum value of a number of pieces of the first information supported by the second endpoints); and
receiving configuration information for an extended antenna carrier (eAxC)_identifier (ID) group supporting Section Extension 10 based on the capability information of the fronthaul interface from the controller (see Fig.6, para. 0110, 0209, when the first control-plane message includes a section extension whose extension type is 10, it indicates that the first information will be applied to a group of endpoints. That is, one eAxCid is used to indicate the section description of a group of eAxCids, and then the first information will be applied to the endpoints corresponding to all eAxCids in the group, see also para. 0209, ,see also 0127-0132, if the first control-plane message further includes a section extension for indicating a group of extended antenna-carrier identifiers, operation 602 includes performing the operation related to the first information in endpoints corresponding to the group of extended antenna-carrier identifiers, according to the first control-plane message, see also para. 0286-0293);
receiving a control plane message from an O-RAN distributed unit (O-DU) (see para. 0078, receiving a control plane message from an O-DU, see also Fig.6. para. 0113-0116, Operation 601: receiving a first control-plane message from an O-DU, the first control-plane message being used for indicating a first endpoint in the O-RU to perform an operation related to first information); and
extending a control plane message of a representative eAxCID to a control plane message of at least one member eAxCID corresponding to the representative eAxCID based on the configuration information for the eAxCID group (see para. 0110, 0209, extending a control plane message of an eAxCID to a control plane message of at least one member eAxCID corresponding to the eAxCID based on the configuration information for the eAxCID group, 0210-0223, 0292-0297, 0301).
Hu however disclose “a middle node”;
Buchu however disclose a fronthaul multiplexer (FHM) as “a middle node” (see Fig.2, an FHM 220, see para. 0084-0085, FHM 220 / a middle node serve as an interface between the RU 225 and DU 215 and multiplex information received from RUs 225 before providing the information to DU 215 and/or demultiplex information received from DU 215 before providing the information to the RUs 225).
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide the functionality of “a middle node”, as taught by Bachu, in the system of Hu, so as to improve wireless communications within a CU/DU split configuration within a base station in an open radio access network (O-RAN) architecture, see Bachu, paragraphs 38-39.
As per claim 5, claim 5 is rejected the same way as claim 1.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Jeon (US Pub. No.:2023/0231686) – see para. 0137-0138, “The RU of various embodiments may transmit capability information of the RU to the DU. The capability information may be transmitted through fronthaul. The DU may receive the capability information of the RU. The capability information of the RU may include information indicating an SRS transmission scheme supported by the RU. According to an embodiment, the capability information of the RU may include information indicating whether the RU supports the antenna number based SRS transmission scheme. Also, according to an embodiment, the capability information of the RU may include information indicating whether the RU is possible to support the uplink IQ data buffer based SRS transmission scheme when the TDD system is configured”.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LAKERAM JANGBAHADUR whose telephone number is (571)272-1335. The examiner can normally be reached on M-F 7 am - 4 pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ian Moore can be reached on 571-272-3085. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/LAKERAM JANGBAHADUR/
Primary Examiner, Art Unit 2469
Prosecution Insights