Prosecution Insights
Last updated: July 17, 2026
Application No. 18/779,313

Virtual RAN Cell Site Resiliency and Energy Efficiency

Non-Final OA §102
Filed
Jul 22, 2024
Priority
Jul 29, 2023 — IN 202321051130
Examiner
NIKMANESH, SEAHVOSH J
Art Unit
Tech Center
Assignee
Mavenir Systems Inc.
OA Round
1 (Non-Final)
86%
Grant Probability
Favorable
1-2
OA Rounds
2m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 86% — above average
86%
Career Allowance Rate
570 granted / 661 resolved
+26.2% vs TC avg
Moderate +13% lift
Without
With
+12.7%
Interview Lift
resolved cases with interview
Typical timeline
2y 2m
Avg Prosecution
5 currently pending
Career history
661
Total Applications
across all art units

Statute-Specific Performance

§101
3.1%
-36.9% vs TC avg
§103
45.1%
+5.1% vs TC avg
§102
29.9%
-10.1% vs TC avg
§112
4.8%
-35.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 661 resolved cases

Office Action

§102
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 is in response to the IDS filed 2/14/2025. Priority Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55. Information Disclosure Statement The IDS filed 2/14/2025 has been considered. The International Search Report 11/29/2024 has been reviewed and is noted. Claim Objections Claims 1 and 11 are objected to because of the following informalities: Claim 1, line 2 is missing the colon at the end of the word comprising. It will be treated as though a colon will be added through future amendment in order to clarify the preamble of the claim. Appropriate correction is required. b. Claim 11, line 2 is missing the colon at the end of the word comprising. It will be treated as though a colon will be added through future amendment in order to clarify the preamble of the claim. Appropriate correction is required. Claim Rejections - 35 USC § 102 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. 6. Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Anderson et al., USPGPub 2022/0272594 A1. a. Regarding claim 1, Anderson et al. shows a method for providing enhanced resiliency of a radio access network (RAN) cell site having multiple sectors associated with multiple cells, comprising(:) providing a first radio unit (RU) simultaneously serving a first set of sectors with a first set of antenna streams; and providing a second RU simultaneously serving at least a second set of sectors with a second set of antenna streams; and reconfiguring, by a network management unit, at least the first set of sectors with a reduced antenna configuration in the case of one of a failure or shutdown of the first RU, whereby all sectors of the cell site remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned. The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. The Backhaul, Midhaul, and fronthaul and IP connectivity are examples of the DU Ru connectivity and various transports [0025], elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034], and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). It is very clear that the systems and methods are in place to account for such considerations. PNG media_image1.png 484 634 media_image1.png Greyscale b. Regarding claim 2, Anderson et al. shows the method of claim 1, further comprising: providing a third RU simultaneously serving at least a third set of sectors with a third set of antenna streams; wherein, in the case of one of a failure or shutdown of the first RU, all sectors of the cell site are served by the second RU and the third RU to remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). c. Regarding claim 3, Anderson et al. shows the method of claim 1, further comprising: providing a third RU simultaneously serving at least a third set of sectors with a third set of antenna streams; wherein, in the case of one of a failure or shutdown of the first and second RUs, all sectors of the cell site are served by the third RU to remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). d. Regarding claim 4, Anderson et al. shows the method of claim 2, further comprising: providing at least one distributed unit (DU) simultaneously serving at least one of the first RU, the second RU and the third RU (Fig. 1A and C; [0036], [0052], and [0055]; i.e. the DU, CU, and RU are arranged for overlap and to facilitate failover techniques). e. Regarding claim 5, Anderson et al. shows the method of claim 3, further comprising: providing a first DU to serve the first RU, the second RU and the third RU for at least a first portion of at least one of the first, second and third set of antenna streams; and providing a second DU to serve the first RU, the second RU and the third RU for at least a second portion of at least one of the first, second and third set of antenna streams; wherein, in the case of one of a failure or shutdown of one of the first DU or the second DU, the remaining operational DU serves at least one operational RU to provide service to all sectors of the cell site (Fig. 1A and C; [0036], [0052], and [0055]; i.e. the DU, CU, and RU are arranged for overlap and to facilitate failover techniques. The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. The Backhaul, Midhaul, and fronthaul and IP connectivity are examples of the DU Ru connectivity and various transports [0025], elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034], and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). It is very clear that the systems and methods are in place to account for such considerations. f. Regarding claim 6, Anderson et al. shows the method of claim 4, wherein: a first DU is provided to serve the first RU, the second RU and the third RU for at least a first portion of at least one of the first, second and third set of antenna streams; and a second DU is provided to serve the first RU, the second RU and the third RU for at least a second portion of at least one of the first, second and third set of antenna streams; wherein, in the case of one of a failure or shutdown of one of the first DU or the second DU, the remaining operational DU serves at least one operational RU to provide service to all sectors of the cell site. (The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. The Backhaul, Midhaul, and fronthaul and IP connectivity are examples of the DU Ru connectivity and various transports [0025] and elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034] and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). g. Regarding claim 7, Anderson et al., shows the method of claim 1, wherein: at least one of the first set of sectors and the second set of sectors is configured as one of two-transmitters-and-two-receivers antenna configuration, or four-transmitters-and-four-receivers antenna configuration; and in the case of one of a failure or shutdown of the first RU, the at least one of the first sector, the second sector and the third sector is reconfigured as follows: one of i) from two-transmitters-and-two-receivers antenna configuration to one-transmitter-and-one-receiver antenna configuration, or ii) from four-transmitters-and-four-receivers antenna configuration to one of two-transmitters-and-two-receivers antenna configuration or one-transmitter-and-one-receiver antenna configuration. The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. It would have been obvious to a person having ordinary skill in the art at the time of the invention to have considered elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034] and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). It is very clear that the systems and methods are in place to account for such considerations and further clarify that this is at least obvious and why the consideration can be made and understood to be a reasonable expectation for success in understanding. h. Regarding claim 8, Anderson et al. shows the method of claim 2, wherein: at least one of the first sector, the second sector and the third sector is configured as one of two-transmitters-and-two-receivers antenna configuration, or four-transmitters-and-four-receivers antenna configuration; and in the case of one of a failure or shutdown of the first RU, the at least one of the first sector, the second sector and the third sector is reconfigured as follows: one of i) from two-transmitters-and-two-receivers antenna configuration to one-transmitter-and-one-receiver antenna configuration, or ii) from four-transmitters-and-four-receivers antenna configuration to one of two-transmitters-and-two-receivers antenna configuration or one-transmitter-and-one-receiver antenna configuration. The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. It would have been obvious to a person having ordinary skill in the art at the time of the invention to have considered elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034] and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). i. Regarding claim 9, Anderson et al. shows the method of claim 1, further comprising: providing, in connection with the reconfiguring, changes to system information blocks indicating antenna capabilities, based on available active antenna processing chains (Fig. 1B; [0032]-[0034] and [0128]; i.e. the nodes and cells are given the identifiers and respective configurations and resources of the RU coverages which can be with regards to latency or load and managed/reassigned upon failure). j. Regarding claim 10, Anderson et al. shows the method of claim 2, further comprising: providing, in connection with the reconfiguring, changes to system information blocks indicating antenna capabilities, based on available active antenna processing chains (Fig. 1B; [0032]-[0034] and [0128]; i.e. the nodes and cells are given the identifiers and respective configurations and resources of the RU coverages which can be with regards to latency or load and managed/reassigned upon failure). k. Regarding claim 11, Anderson et al. shows a system for providing enhanced resiliency of a radio access network (RAN) cell site having multiple sectors associated with multiple cells, comprising(:) a first radio unit (RU) simultaneously serving a first set of sectors with a first set of antenna streams; and a second RU simultaneously serving at least a second set of sectors with a second set of antenna streams; and a network management unit selectively reconfiguring at least the first set of sectors with a reduced antenna configuration in the case of one of a failure or shutdown of the first RU, whereby all sectors of the cell site remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned. The DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. The Backhaul, Midhaul, and fronthaul and IP connectivity are examples of the DU Ru connectivity and various transports [0025]. and elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034] and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). It is very clear that the systems and methods are in place to account for such considerations). PNG media_image1.png 484 634 media_image1.png Greyscale l. Regarding claim 12, Anderson et al. shows t1he system of claim 11, further comprising: a third RU simultaneously serving at least a third set of sectors with a third set of antenna streams; wherein, in the case of one of a failure or shutdown of the first RU, all sectors of the cell site are served by the second RU and the third RU to remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). m. Regarding claim 13, Anderson et al. shows the system of claim 11, further comprising: a third RU simultaneously serving at least a third set of sectors with a third set of antenna streams; wherein, in the case of one of a failure or shutdown of the first and second RUs, all sectors of the cell site are served by the third RU to remain in service (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). n. Regarding claim 14, Anderson et al. shows the system of claim 12, further comprising: at least one distributed unit (DU) simultaneously serving at least one of the first RU, the second RU and the third RU (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). o. Regarding claim 15, Anderson et al. shows the system of claim 13, further comprising: a first DU to serve the first RU, the second RU and the third RU for at least a first portion of at least one of the first, second and third set of antenna streams; and a second DU to serve the first RU, the second RU and the third RU for at least a second portion of at least one of the first, second and third set of antenna streams; wherein, in the case of one of a failure or shutdown of one of the first DU or the second DU, the remaining operational DU serves at least one operational RU to provide service to all sectors of the cell site (Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). p. Regarding claim 16, Anderson et al. shows the system of claim 14, wherein: a first DU is provided to serve the first RU, the second RU and the third RU for at least a first portion of at least one of the first, second and third set of antenna streams; and a second DU is provided to serve the first RU, the second RU and the third RU for at least a second portion of at least one of the first, second and third set of antenna streams; wherein, in the case of one of a failure or shutdown of one of the first DU or the second DU, the remaining operational DU serves at least one operational RU to provide service to all sectors of the cell site(Fig. 1C and 1A; [0016]-[0038] and [0055]-[0072]; i.e. upon failure of one DU the remaining RU are reassigned). q. Regarding claim 17, Anderson et al. shows the system of claim 11, wherein: at least one of the first set of sectors and the second set of sectors is configured as one of two-transmitters-and-two-receivers antenna configuration, or four-transmitters-and-four-receivers antenna configuration; and the network management unit reconfigures the at least one of the first sector, the second sector and the third sector in the case of one of a failure or shutdown of the first RU, as follows: one of i) from two-transmitters-and-two-receivers antenna configuration to one-transmitter-and-one-receiver antenna configuration, or ii) from four-transmitters-and-four-receivers antenna configuration to one of two-transmitters-and-two-receivers antenna configuration or one-transmitter-and-one-receiver antenna configuration ([0020] shows that the RU’s may be configured in any combination of transmitters and receivers). r. regarding claim 18, Anderson et al. shows the system of claim 12, wherein: at least one of the first sector, the second sector and the third sector is configured as one of two-transmitters-and-two-receivers antenna configuration, or four-transmitters-and-four-receivers antenna configuration; and the network management unit reconfigures the at least one of the first sector, the second sector and the third sector in the case of one of a failure or shutdown of the first RU, as follows: one of i) from two-transmitters-and-two-receivers antenna configuration to one-transmitter-and-one-receiver antenna configuration, or ii) from four-transmitters-and-four-receivers antenna configuration to one of two-transmitters-and-two-receivers antenna configuration or one-transmitter-and-one-receiver antenna configuration ([0020] shows that the RU’s may be configured in any combination of transmitters and receivers) ([0033] shows that the DUs/RUs can be configured to manage the performance). For sake of establishing the understanding of the material in Anderson et al is at least obvious to one of ordinary skill in the art at the time the invention was made to have further (fix here when you get back!) Anderson et al. does not explicitly show the limitations as stated regarding the antenna streams. Anderson et al. teaches that the DU and corresponding RU may provide services for one or more slice types and additionally the management node facilitates the RU/DU pairing and can be based on latency, expected load,…failure of a given DU…, facilitate reassignment [0034]. The Backhaul, Midhaul, and fronthaul and IP connectivity are examples of the DU Ru connectivity and various transports [0025]. It would have been obvious to a peron having ordinary skill in the art at the time of the invention to have considered elements pertaining to the latency, load, or failure among the reasons to adjust or continue the service with other sources having overlap to further maintain the coverage areas and nodes [0034] and that the management node uses information, such as constraint parameters, to follow failover actions or rules assignment upon failure ([0044]-[0045]). It is very clear that the systems and methods are in place to account for such considerations and further clarify that this is at least obvious and why the consideration can be made and understood to be a reasonable expectation for success in understanding. s. regarding claim 19, Anderson et al. shows the system of claim 11, wherein: the network management unit is configured to provide, in connection with the reconfiguring, changes to system information blocks indicating antenna capabilities, based on available active antenna processing chains (Fig. 1B; [0032]-[0034] and [0128]; i.e. the nodes and cells are given the identifiers and respective configurations and resources of the RU coverages which can be with regards to latency or load and managed/reassigned upon failure). t. regarding claim 20, Anderson et al. shows the system of claim 12, wherein: the network management unit is configured to provide, in connection with the reconfiguring, changes to system information blocks indicating antenna capabilities, based on available active antenna processing chains (Fig. 1B; [0032]-[0034] and [0128]; i.e. the nodes and cells are given the identifiers and respective configurations and resources of the RU coverages which can be with regards to latency or load and managed/reassigned upon failure). Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Suthar et al., US PGPub 2020/0162348 A1, shows a method of automated provisioning of VRAN and further details of Virtualization of Radio Access Networks. Any inquiry concerning this communication or earlier communications from the examiner should be directed to SEAHVOSH J NIKMANESH whose telephone number is (571)270-5549. The examiner can normally be reached M-F 9-5. 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, Yuwen Pan can be reached at (571)272-7855. 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. /Seahvosh Nikmanesh/Examiner, Art Unit 2649 /YUWEN PAN/Supervisory Patent Examiner, Art Unit 2649
Read full office action

Prosecution Timeline

Jul 22, 2024
Application Filed
Jul 07, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 11430788
INTEGRATED CIRCUIT WITH LATCH-UP IMMUNITY
2y 6m to grant Granted Aug 30, 2022
Patent 11355626
HIGH ELECTRON MOBILITY TRANSISTOR
2y 8m to grant Granted Jun 07, 2022
Patent 11355402
ADHESION DEVICE, MICRO DEVICE OPTICAL INSPECTION AND REPAIRING EQUIPMENT AND OPTICAL INSPECTION AND REPAIRING METHOD
2y 5m to grant Granted Jun 07, 2022
Patent 11340530
IMPLANTING METHOD AND APPARATUS
2y 6m to grant Granted May 24, 2022
Patent 11315814
CARRYING APPARATUS AND CARRYING METHOD
3y 5m to grant Granted Apr 26, 2022
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
86%
Grant Probability
99%
With Interview (+12.7%)
2y 2m (~2m remaining)
Median Time to Grant
Low
PTA Risk
Based on 661 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month