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 .
Preliminary Amendment
The present Office Action is based upon the original patent application as modified by the preliminary amendment filed on February 16, 2024. Claims 1-18 are now pending in the present application.
Priority
Acknowledgment is made of applicant's claim for foreign priority under 35 U.S.C. 119(a)-(d). Receipt is acknowledged of papers, which have been placed of record in the file.
Applicant’s claim for the benefit of a prior-filed application under 35 U.S.C. 119(e) or under 35 U.S.C. 120, 121, 365(c), or 386(c) is acknowledged.
Information Disclosure Statement
The information disclosure statement submitted on February 26, 2024 has been considered by the Examiner and made of record in the application.
Claim Rejections - 35 USC § 103
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.
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.
The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claims 1-7, 9-14, 16, and 17 are rejected under 35 U.S.C. 103 as being unpatentable over Zandi et al. (hereinafter Zandi) (U.S. Patent Application Publication # 2018/0262592 A1) in view of Jin et al. (hereinafter Jin) (U.S. Patent Application Publication # 2022/0271990 A1).
Regarding claim 1, Zandi teaches and discloses a method comprising:
receiving an indication to create a notification publish space (publish-subscribe messaging system topic/telemetry; figure 1) to monitor failure, from a central entity (monitoring system; figure 1); creating the notification publish space, and sending an acknowledgement of the indication to create the notification publish space to the central entity ([0026]; “…Publish-subscribe messaging system 102 may allow streams 122 of messages to be generated and identified by a number of topics 120, thereby enabling producers of the messages to publish information to the topics and consumers of the information to subscribe to the topics…create topics, subscribe to the topics, and publish messages to the topics…”; [0028]; “…the monitoring server may subscribe to one or more topics 120 associated with network telemetry data in the publish-subscribe messaging system, and the nodes may publish streams 122 of messages containing the network telemetry data to the topics…”; [0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures…”; teaches an indication to create a publish-subscribe topic, including monitoring failure, from the central entity, such as the monitoring server and creating the publish-subscribe topic/telemetry and communicating the creation of the publish-subscribe topic/telemetry);
receiving a subscription to the notification publish space from at least one logical entity of the access network node or of another access network node (node, 114-118, figure 1) ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the nodes subscribing to the publish-subscribe topic/telemetry);
receiving a failure notification of a failure of the at least one logical entity being monitored for failure; and notifying the subscribers of the notification publish space concerning the failure of the at least one logical entity ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches receiving and identifying a notification of a failure and notifying subscribers of the identified failure).
However, Zandi may not explicitly disclose a central entity of an access network node, the notification publish space comprising an identifier of the central entity of the access network node being monitored for failure.
Nonetheless, in the same field of endeavor, Jin teaches and suggests a central entity (gNB-CU; figure 1) of an access network node (data center/gNB; figure 1), the notification publish space (table, figure 2) comprising an identifier (gNB-CU_ID; figure 2) of the central entity of the access network node being monitored for failure ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches a central entity, such as gNB-CU of an access network node (gNB/datacenter) and an identifier of the central entity being monitored for failure).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate a central entity, such as gNB-CU of an access network node and an identifier of the central entity being monitored for failure as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 2, Zandi discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose wherein the failure notification of the failure comprises an identifier of the failed at least one logical entity.
Nonetheless, in the same field of endeavor, Jin further teaches and suggests wherein the failure notification of the failure comprises an identifier (gNB-CU_ID; figure 2) of the failed at least one logical entity ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches identifying the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate identifying the failed gNB-CU with associated identifier as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin, for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 3, Zandi discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose transmitting an identifier of the failed at least one logical entity to the subscribers of the notification publish space.
Nonetheless, in the same field of endeavor, Jin further teaches and suggests transmitting an identifier (gNB-CU_ID; figure 2) of the failed at least one logical entity to the subscribers of the notification publish space ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches communicating the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate identifying the failed gNB-CU with associated identifier as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin, for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 4, Zandi, as modified by Jin, further teaches and suggests filtering the at least one logical entity prior to notifying the notification publish space concerning the failure of the at least one logical entity, such that a first subset of the at least one logical entity receives the notification of the failure, and a second subset of the at least one logical entity does not receive the notification of the failure due to not being affected with the failure ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0038]; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the notification are transmitted to the nodes which subscribe to the notifications and not those who are not affected and have not subscribed).
Regarding claim 5, Zandi teaches and discloses a method comprising: transmitting an indication to create a notification publish space to a data storage function (publish-subscribe messaging system topic/telemetry; figure 1); receiving an acknowledgement of the indication to create the notification publish space from the data storage function ([0026]; “…Publish-subscribe messaging system 102 may allow streams 122 of messages to be generated and identified by a number of topics 120, thereby enabling producers of the messages to publish information to the topics and consumers of the information to subscribe to the topics…create topics, subscribe to the topics, and publish messages to the topics…”; [0028]; “…the monitoring server may subscribe to one or more topics 120 associated with network telemetry data in the publish-subscribe messaging system, and the nodes may publish streams 122 of messages containing the network telemetry data to the topics…”; [0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures…”; teaches an indication to create a publish-subscribe topic, including monitoring failure, from the central entity, such as the monitoring server and creating the publish-subscribe topic/telemetry and communicating the creation of the publish-subscribe topic/telemetry); and
transmitting the associated publish space information to at least one logical entity (node, 114-118, figure 1) of the access network node or of another access network node being monitored for failure ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches transmitting and identifying a notification of a failure and notifying subscribers of the identified failure); subscribe to the notification publish space to receive information concerning a failure of the at least one logical entity of the access network node or of the another access network node ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the nodes subscribing to the publish-subscribe topic/telemetry).
However, Zandi may not explicitly disclose the notification publish space comprising an identifier of a central entity of an access network node being monitored for failure; and transmitting the identifier of the central entity; and wherein the identifier of the central entity is configured to be used with the at least one logical entity to subscribe to the notification publish space.
Nonetheless, in the same field of endeavor, Jin teaches and suggests the notification publish space (table, figure 2) comprising an identifier (gNB-CU_ID; figure 2) of a central entity (gNB-CU; figure 1) of an access network node being monitored for failure ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches a central entity, such as gNB-CU of an access network node (gNB/datacenter) and an identifier of the central entity being monitored for failure); and transmitting the identifier of the central entity, wherein the identifier of the central entity is configured to be used with the at least one logical entity to subscribe to the notification publish space ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches communicating the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate a central entity, such as gNB-CU of an access network node and an identifier of the central entity being monitored for failure as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 6, Zandi discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose wherein the central entity comprises either a central unit control plane entity or a near real time radio intelligent controller.
Nonetheless, in the same field of endeavor, Jin further teaches and suggests wherein the central entity (gNB-CU, figure 1) comprises either a central unit control plane entity or a near real time radio intelligent controller ([0017]; [0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; [0045]; teaches the gNB-CU comprises a control plane).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate the gNB-CU comprises a control plane as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin, for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 7, Zandi discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose detecting the failure of the at least one logical entity of the access network node or of the another access network node; and notifying a data storage function of the failure, the notifying comprising including an identifier of the failed at least one logical entity.
Nonetheless, in the same field of endeavor, Jin further teaches and suggests detecting the failure of the at least one logical entity of the access network node or of the another access network node; and notifying a data storage function of the failure, the notifying comprising including an identifier (gNB-CU_ID; figure 2) of the failed at least one logical entity ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches identifying the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate identifying the failed gNB-CU with associated identifier as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin, for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 9, Zandi, as modified by Jin, further teaches and suggests filtering the at least one logical entity prior to notifying the data storage function of the failure of the at least one logical entity, such that a first subset of the at least one logical entity receives a failure notification, and a second subset of the at least one logical entity does not receive the failure notification ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0038]; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the notification are transmitted to the nodes which subscribe to the notifications and not those who are not affected and have not subscribed).
Regarding claim 10, Zandi, as modified by Jin, further teaches and suggests subscribing to the notification publish space ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the nodes subscribing to the publish-subscribe topic/telemetry).
Regarding claim 11, Zandi, as modified by Jin, further teaches and suggests detecting falsely identified failures ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches identifying a failure and notifying subscribers of the identified failure).
Regarding claim 12, Zandi, as modified by Jin, further teaches and suggests wherein detecting falsely identified failures comprises at least one of: integrating reports from multiple of the at least one logical entity; or an artificial intelligence or machine learning model ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches identifying a failure and notifying subscribers of the identified failure).
Regarding claim 13, Zandi teaches and discloses a method comprising: subscribing to the notification publish space of the radio access network data storage function (publish-subscribe messaging system topic/telemetry; figure 1) ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the nodes subscribing to the publish-subscribe topic/telemetry), the notification publish space (publish-subscribe messaging system topic/telemetry; figure 1) used to provide or receive information concerning a failure of at least one logical entity (node, 114-118, figure 1) of the access network node or of another access network node being monitored for failure; and receiving a notification of failure of the at least one logical entity with the notification publish space of the radio access network data storage function ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches receiving and identifying a notification of a failure and notifying subscribers of the identified failure).
However, Zandi may not explicitly disclose receiving an identifier from a central entity of an access network node, the identifier used to identify a notification publish space of a radio access network data storage function; using the identifier of the central entity being monitored for failure; and the notification of failure comprising an identifier of the failed at least one logical entity.
Nonetheless, in the same field of endeavor, Jin teaches and suggests receiving an identifier (gNB-CU_ID; figure 2) from a central entity (gNB-CU; figure 1) of an access network node, the identifier used to identify a notification publish space (table, figure 2) of a radio access network data storage function; using the identifier of the central entity being monitored for failure; and the notification of failure comprising an identifier of the failed at least one logical entity ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches a central entity, such as gNB-CU of an access network node (gNB/datacenter) and an identifier of the central entity being monitored for failure and communicating the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate a central entity, such as gNB-CU of an access network node and an identifier of the central entity being monitored for failure and communicating the failed gNB-CU with associated identifier as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 14, Zandi discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose detecting the failure of the at least one logical entity; and notifying a data storage function of the failure, the notifying comprising including an identifier of the failed at least one logical entity.
Nonetheless, in the same field of endeavor, Jin further teaches and suggests detecting the failure of the at least one logical entity; and notifying a data storage function of the failure, the notifying comprising including an identifier (gNB-CU_ID; figure 2) of the failed at least one logical entity ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches identifying the failed gNB-CU with associated identifier).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate identifying the failed gNB-CU with associated identifier as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin, for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 16, Zandi teaches and discloses a method comprising: detecting a failure of at least one logical entity of an access network node (node, 114-118, figure 1) being monitored for failure; and transmitting a notification to a radio access network data storage function (204, figure 2) of the failure of the at least one logical entity; wherein the notification is configured to be used with the radio access network data storage function to notify subscribers of a notification publish space (publish-subscribe messaging system topic/telemetry; figure 1) concerning the failure of the at least one logical entity ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches receiving and identifying a notification of a failure and notifying subscribers of the identified failure);
wherein the notification publish space is accessible to the subscribers of the notification publish space to be notified of the failure ([0026]; [0030]; [0032]; “…one or more nodes 114-118…may execute brokers for receiving messages published to the publish-subscribe messaging system, storing the messages, and allowing agents of the publish-subscribe messaging system executing on other components of the system to retrieve the stored messages…”; [0043]; “…publish messages 310 to publish-subscribe messaging system 102, and nodes 322-324 may use subscriptions 326-328 to topics 312 to receive the messages…”; teaches the nodes subscribing to the publish-subscribe topic/telemetry).
However, Zandi may not explicitly disclose the notification comprising an identifier of the failed at least one logical entity.
Nonetheless, in the same field of endeavor, Jin teaches and suggests the notification comprising an identifier (gNB-CU_ID; figure 2) of the failed at least one logical entity (gNB-CU; figure 1) ([0019]; “…detecting in advance failure or disaster events through a separate device (ex. high availability (HA) controller, HAC) that monitors the states of gNB-CUs and data centers in real time…”; [0041]; “…a device that rapidly detects a failure or disaster event through a separate device that monitors the states of gNB-CUs and data centers in real time…”; [0043]; teaches a central entity, such as gNB-CU of an access network node (gNB/datacenter) and an identifier of the central entity being monitored for failure).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate a central entity, such as gNB-CU of an access network node and an identifier of the central entity being monitored for failure as taught by Jin with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi for the purpose of improving restoration and recovery of service and managing resources in event of a failure, as suggested by Jin.
Regarding claim 17, Zandi, as modified by Jin, further teaches and suggests wherein detecting the failure comprises utilizing previously collected failure statistics and other information stored within a radio access network data storage function ([0038]; “…the monitoring server may apply a statistical model to the telemetry data and/or correlate events in the telemetry data to identify faults, failures, anomalies, trends, and/or other states in the node. The monitoring server may also generate alerts and/or notifications based on statistical model output, the correlated events, and/or other results or conclusions drawn from the analysis…”; teaches identifying a failure and notifying subscribers of the identified failure).
Claims 8, 15, and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Zandi et al. (hereinafter Zandi) (U.S. Patent Application Publication # 2018/0262592 A1) in view of Jin et al. (hereinafter Jin) (U.S. Patent Application Publication # 2022/0271990 A1), and further in view of Cheng (U.S. Patent Application Publication # 2020/0077310 A1).
Regarding claims 8, 15, and 18, Zandi, as modified by Jin, discloses subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure, but may not explicitly disclose wherein detecting the failure is performed with at least one of: at least one service response timer expiry; at least one transport network failure detection timer expiry; or an artificial intelligence or machine learning method indicating a probability of failure at a given time or time period.
Nonetheless, in the same field of endeavor, Cheng teaches and suggests wherein detecting the failure is performed with at least one of: at least one service response timer expiry; at least one transport network failure detection timer expiry; or an artificial intelligence or machine learning method indicating a probability of failure at a given time or time period ([0028]; [0055]; [0056]; teaches detecting a failure including a validity timer).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to detecting a failure including a validity timer as taught by Cheng with the method for subscribing to the publish-subscribe topic/telemetry and receiving and identifying a notification of a failure and notifying subscribers of the identified failure as disclosed by Zandi, as modified by Jin for the purpose of reducing the impact of failure in the network, as suggested by Cheng.
Conclusion
The prior art made of record and not relied upon is considered pertinent to Applicant’s disclosure.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SUK JIN KANG whose telephone number is (571) 270-1771. The examiner can normally be reached on Monday-Friday 8am-5pm.
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, Chirag Shah can be reached on (571) 272-3144. 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.
Any inquiry of a general nature or relating to the status of this application or proceeding should be directed to the receptionist/customer service whose telephone number is (571) 272-2600.
/Suk Jin Kang/
Examiner, Art Unit 2477
March 19, 2026