DETAILED ACTION
Acknowledgments
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This action is in reply to the application and preliminary amendment simultaneously filed on 07/25/2025.
Claims 27-45 have been added.
Claims 1-26 have been canceled.
Claims 27-45 are currently pending and have been examined.
Information Disclosure Statement
The Information Disclosure Statements filed 07/29/2025 and 09/25/2025 have been considered. Initialed copies of the Form 1449 are enclosed herewith.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 27-45 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-patent eligible subject matter because the claim(s) as a whole, considering all claim elements both individually and in combination, do not amount to significantly more than an abstract idea.
Step 1:
The claims recite a process, system, apparatus, article of manufacture, and/or a nontransitory storage medium with instructions, each of which are proper statutory categories.
Step 2A (prong 1):
Claim 1 (representative of claims 36 and 45):
The claim limitations are grouped as shown immediately following:
A method for detecting a denial-of-service, DoS, attack, on an upstream device, the method being performed in a radio network node, the method comprising: (Certain Methods Of Organizing Human Activity - managing personal behavior or interactions between people including following rules or instructions)
obtaining a metric based on radio access network, RAN, signalling for communication between a user equipment, UE, and the radio network node, the metric being based on one or both of buffer status reports, BSRs, from the UE, and a volume of used physical resource blocks, PRBs; (Certain Methods Of Organizing Human Activity - managing personal behavior or interactions between people including following rules or instructions)
determining that a DoS attack is in progress on the upstream device based on the metric, the upstream device being provided upstream from the radio network node, when the metric is based on the BSRs, the determining that a DoS attack is in progress comprises determining that a statistic of frequency of BSRs indicate a frequency that is greater than a threshold frequency. (Certain Methods Of Organizing Human Activity - managing personal behavior or interactions between people including following rules or instructions)
Additional dependent claims 28-35 and 37-44 do not appear remedy the deficiency.
Step 2A (prong 2):
Claim 1 (representative of claims 36 and 45):
… an upstream device
… a radio network node
… radio access network
… a processor
…a memory
… a non-transitory computer storage medium
These remaining claim limitations are delineated as shown immediately preceding. The abstract idea is not integrated into a practical application. There are no improvements to the functioning of a computer, other technology or technical field, a particular machine is not cited, nothing is transformed to a different state or thing, the abstract idea is not more than a drafting effort designed to monopolize the abstract idea. The claim merely uses a computer as a tool to perform the abstract idea, which is generally linked to a particular field of use, in this case, marketing and advertising. Thus, these limitations are recited at a high-level of generality (i.e., as a generic processor and memory performing a generic computer function of processing and storing data) such that it amounts no more than mere instructions to apply the exception using a generic computer component – MPEP 2106.05(f). Further, receiving data, evaluating data and distributing data are data gathering and data outputting, which has no effect on technology and does no more than generally link the use of the judicial exception to a particular technological environment or field of use – see MPEP 2106.05(h).
Step 2B:
The claim limitations do not provide an Inventive Concept. The claim limitations do not recite additional elements that amount to significantly more that the abstract idea because the additional elements of the system comprising a computer processor, computer readable storage medium with instructions, and a memory configured to store information, each recited at a high level of generality in a computer network which only perform the universal computer functions of accessing, receiving, storing, and processing data, transmitting and presenting information. Taking the elements both individually and as an ordered combination, the function performed by the computer at each step of the process is purely orthodox. Using a computer to obtain and display data are some of the most basic functions of a computer. As shown, the individual limitations claimed are some of the most rudimentary functions of a computer. The technical solution described in this invention does not alter hardware structure or its routine, does not transform the character of the information being processed, does not identify a novel source or type of data, does not advance the functionality of a computer as a tool, and does not incorporate specific rules enabling the computer to accomplish innovative utilities. In summary, the individual step and/or component does no more than require a general computer to perform standard computer functions. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of a computer devices amounts to no more than mere instructions to apply the exception using a generic computer component - requiring the use of software to tailor information and provide it to the user on a generic computer, Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1370-71, 115 USPQ2d 1636, 1642 (Fed. Cir. 2015).
Claim 45, as recited, are directed toward a non-transitory computer storage medium storing a computer program. Such logic can be interpreted as computer code, per se, which is not a statutory category and is therefore unpatentable. However, a computer program can be eligible for patent protection if it is tangibly embodied on a computer readable medium and, when executed by a computer, performs the steps of the invention. Appropriate correction is required.
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 27-45 are rejected under U.S.C. 103 as being unpatentable over Kolekar (USPGP 2023/0422038 A1), hereinafter KOLEKAR, in view of Kuirapati et al. (USPGP 2007/0121596 A1), hereinafter KURAPATI.
Claim 27:
KOLEKAR as shown below discloses the following limitations:
A method for detecting a denial-of-service, DoS, attack, on an upstream device, the method being performed in a radio network node, the method comprising: (see at least paragraph 0013)
obtaining a metric based on radio access network, RAN, signalling for communication between a user equipment, UE, and the radio network node, the metric being based on one or both of buffer status reports, BSRs, from the UE, and a volume of used physical resource blocks, PRBs; (see at least paragraphs 0013, 0039, 0143 (TABLE))
determining that a DoS attack is in progress on the upstream device based on the metric, the upstream device being provided upstream from the radio network node, when the metric is based on the BSRs, the determining that a DoS attack is in progress comprises determining that a statistic of frequency of BSRs indicate a frequency that is greater than a threshold frequency. (see at least paragraphs 0018, 0019)
KOLEKAR does not specifically disclose an upstream device per se. KURAPATI, however, in at least Figure 10 as well as associated and related text does. In this case, each of the elements claimed are all shown by the prior art of record but not combined as claimed. However, the technical ability exists to combine and modify the elements as claimed and the results of the combination are predictable. Therefore, when combined, the elements perform the same function as they did separately. (KSR v. Teleflex, 127 S. Ct. 1727 (2007)). Consequently, it would have been obvious to one of ordinary skill in the art at the effective filing date to combine/modify the method of KOLEKAR with the technique of KURAPATI because, “Dealing with both internal and external threats to secure data networks from DoS, Distributed DoS ("DDoS"), and SPAM is well known to the data world. In voice networks, however, these same threats have significantly amplified impacts because the telephone and its related services are personal, real-time, and interactive. Imagine a phone ringing regularly in the middle of the night because of a spammer, or all phones in an enterprise ringing constantly due to a DoS attack, or entire voice mail systems being completely filled overnight with SPAM (and then each individual having to clear out their voice mailbox manually in the morning).” (KURAPATI: paragraph 0004). Additionally, there is a recognized problem or need in the art including market pressure, design need, etc., and there are a finite number of identified predictable solutions. Accordingly, those in the art could have pursued known solutions with reasonable expectation of success. (KSR v. Teleflex, 127 S. Ct. 1727 (2007)). Fundamentally, in the competitive business climate, there is a profit-driven motive to maximize the profitability of goods and services that are provided or marketed to customers. Enterprises typically use business planning to make decisions in order to maximize profits.
Claim 28:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the metric is based on a volume of scheduling requests transmitted from the UE.
See at least paragraphs 0071, 0100, and 0143 (TABLE).
Claim 29:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the determining that a DoS attack is in progress comprises determining that the volume of scheduling requests is less than a threshold volume of scheduling requests.
See at least paragraphs 0018 and 0019.
Claim 30:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the determining that a DoS attack is in progress comprises determining that the BSRs indicate a high buffer level over time.
See at least paragraphs 0013, 0039, 0143 (TABLE).
Claim 31:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the determining that a DoS attack is in progress comprises determining that the volume of PRBs is greater than a threshold volume of PRBs.
See at least paragraphs 0013, 0039, 0143 (TABLE).
Claim 32:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
signalling an alert indicating that the DoS attack is in progress.
See at least paragraph 0012.
Claim 33:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the determining that a DoS attack is in progress is configured to detect a flood of user datagram protocol, UDP, packets.
See at least paragraph 0064.
Claim 34:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KOLEKAR further discloses the following limitations:
wherein the determining that a DoS attack is in progress is configured to detect a flood of transport control protocol, TCP, synchronise, SYN, messages.
See at least paragraph 0064.
Claim 35:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections above. KURAPATI further discloses the following limitations:
wherein the DoS attack involves a user plane attack.
See at least paragraphs 0113 and 0228. In this case, each of the elements claimed are all shown by the prior art of record but not combined as claimed. However, the technical ability exists to combine and modify the elements as claimed and the results of the combination are predictable. Therefore, when combined, the elements perform the same function as they did separately. (KSR v. Teleflex, 127 S. Ct. 1727 (2007)). Consequently, it would have been obvious to one of ordinary skill in the art at the effective filing date to combine/modify the method of KOLEKAR with the technique of KURAPATI because, “Dealing with both internal and external threats to secure data networks from DoS, Distributed DoS ("DDoS"), and SPAM is well known to the data world. In voice networks, however, these same threats have significantly amplified impacts because the telephone and its related services are personal, real-time, and interactive. Imagine a phone ringing regularly in the middle of the night because of a spammer, or all phones in an enterprise ringing constantly due to a DoS attack, or entire voice mail systems being completely filled overnight with SPAM (and then each individual having to clear out their voice mailbox manually in the morning).” (KURAPATI: paragraph 0004). Additionally, there is a recognized problem or need in the art including market pressure, design need, etc., and there are a finite number of identified predictable solutions. Accordingly, those in the art could have pursued known solutions with reasonable expectation of success. (KSR v. Teleflex, 127 S. Ct. 1727 (2007)). Fundamentally, in the competitive business climate, there is a profit-driven motive to maximize the profitability of goods and services that are provided or marketed to customers. Enterprises typically use business planning to make decisions in order to maximize profits.
Claims 36-45:
The combination of KOLEKAR/KURAPATI discloses the limitations as shown in the rejections of the claims above. The Examiner finds that remaining claims 36-45 are not patentably distinct from claims 27-35, because the inventions in the claims are directed to related, indistinct products. The related inventions would be distinct if: (1) the inventions as claimed were either not capable of use together or could have a materially different design, mode of operation, function, or effect; (2) the inventions did not overlap in scope, i.e., are mutually exclusive; and (3) the inventions as claimed were not obvious variants. See MPEP § 806.05(j). Furthermore, the inventions as claimed encompass overlapping subject matter and are obvious variants that do not produce any new, meaningful, synergetic result that would render the claims novel. Therefore, for the sake of clarity, the Examiner has grouped the rejections of claims 27-45 accordingly using the same references and citations as above.
CONCLUSION
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Non-Patent Literature:
James Joshi. “Network Security.” (Nov. 16, 2018). Retrieved online 10/15/2026. Security Attack - an overview | ScienceDirect Topics
Relevancy: “Information assurance (IA) deals with security and dependability of systems and networks. In this chapter, we provide an overview of issues, terminology, and techniques related to the security of the network. Network security comprises of ongoing activities that (a) assess the network for its current state of security, (b) have in place protection and prevention mechanisms against security threats, (c) implement detection mechanisms to rapidly identify security attacks that may have been successful, and (d) have policies, procedures, and techniques in place to respond to attacks. We discuss these aspects in a succinct manner in this chapter. In Section 2.2, we describe the network communications and how they are vulnerable to security attacks and provide a brief overview of security services. Section 2.3 is devoted to mechanisms that are used to protect networks from security threats or prevent successful attacks and here we discuss firewalls and cryptographic protocols. Intrusion detection is examined in Section 2.4 and response mechanisms are considered in Section 2.5.” (Abstract/Introduction)
Eric Chou et al. “Distributed Denial of Service (DDoS) Practical Detection and Defense.” (2018). Retrieved online 10/15/2026. Distributed Denial of Service (DDoS)
Relevancy: “Humans need to be connected to one another for society to flourish. The internet is an essential connector in today’s world. By 2020, it is projected that there will be 50 billion internet-connected devices in use. With the rise of new technologies in our lives, new cyber threats and attacks regularly occur. We’re seeing politically motivated DDoS attacks, and a new twist on cyberattacks—the 2017 attempt to cash in on the soaring price of Bitcoin. We need cyber-warriors to continually out-think and out-smart those who are using IoT devices, cloud infrastructures, and other technologies against us.” (Abstract/Introduction)
Madhusanka Liyanage et al. “Open RANSecurity: Challenges and Opportunities.” (3 Dec 2022). Retrieved online 10/15/2026. Open RAN Security: Challenges and Opportunities
Relevancy: “Open RAN (ORAN, O-RAN) represents a novel industry-level standard for RAN (Radio Access Network), which defines interfaces that support inter-operation between vendors’ equipment and offer network flexibility at a lower cost. Open RAN integrates the benefits and advancements of network softwarization and Artificial Intelligence to enhance the operation of RAN devices and operations. Open RAN offers new possibilities so that different stakeholders can develop the RAN solution in this open ecosystem. However, the benefits of Open RAN bring new security and privacy challenges. As Open RAN offers an entirely different RAN configuration than what exists today, it could lead to severe security and privacy issues if mismanaged, and stakeholders are understandably taking a cautious approach towards the security of Open RAN deployment. In particular, this paper provides a deep analysis of the security and privacy risks and challenges associated with Open RAN architecture. Then, it discusses possible security and privacy solutions to secure Open RAN architecture and presents relevant security standardization efforts relevant to Open RAN security. Finally, we discuss how Open RAN can be used to deploy more advanced security and privacy solutions in 5G and beyond RAN.” (Abstract/Introduction)
Foreign Art:
GOMEZ-HIDALGO P V. et al. “Method For Handling Denial Of Service (DoS) Attack, Involves Initiating Sending, Directly Or Indirectly, Second Message To One Of One Or More Third Nodes Operating In Communications System.” (WO 2023/020747 A1)
Relevancy: “The method involves receiving (401) a first message indicating an identifier identifying the second node, a first indication indicating target nodes operating outside of the communication system, under DoS attack, and source nodes of the DoS attack, and second indication indicating an action to be taken in the communication system to mitigate the DoS attack, from a second node operating outside of the communication system. The second message is initiated (403) for sending, directly or indirectly to third nodes operating in the communication system. The second message is sent based on the received first message. The second message initiates an application of the indicated action in the communication system.” (Abstract/Introduction)
XIE M et al. “Method For Resisting Denial-of-service Attack In Terminal Device, Involves Determining Management Policy According To Model, Where Model Is Obtained By Training Access Behavior Data Set, And Behavior Log Of Service/interface Is Accessed.” (WO 2019/095911 A1)
Relevancy: “The method involves receiving an access request initiated by a client application (CA) to a service/interface (10). The service/interface is accessed by the CA. Service or resource is requested. The access request is transmitted to a defense module deployed in a trusted execution environment (TEE). Determination is made to check whether to authorize the access request or not by the defense module according to a management policy. The management policy is determined according to an access behavior model, where the access behavior model is obtained by training an access behavior data set (138), and an access behavior log of the service/interface is accessed by the TEE.” (Abstract/Introduction)
HALDAR D. et al. “Suppressing Method Of Short Message Service (SMS) Induced Denial Of Service (DoS) Attack On Telecommunications Network, By Communicating Trigger To SMS Router, If Quantity Of SMS Message Requests Exceed Predefined SMS Request Threshold.” (WO 2010/021886 A1)
Relevancy: “The suppressing method involves receiving target device identifier and originating source identifier associated with SMS message (410) at the register (406). Location of target device associated with target device identifier is requested from register, and received at the register. The register is updated to include location of target device. The SMS message requests quantity are determined at predefined time frame. A trigger (434) is communicated to SMS router, when it is determined that quantity of SMS message requests exceed predefined SMS request threshold.” (Abstract/Introduction)
Any inquiry of a general nature or relating to the status of this application or concerning this communication or earlier communications from the Examiner should be directed to James A. Reagan (james.reagan@uspto.gov) whose telephone number is 571.272.6710. The Examiner can normally be reached Monday through Friday from 9 AM to 5 PM. If attempts to reach the examiner by telephone are unsuccessful, the Examiner’s supervisor, John Hayes, can be reached at 571.272.6708.
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://portal.uspto.gov/external/portal/pair . Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866.217.9197 (toll-free).
Any response to this action should be mailed to:
Commissioner for Patents
PO Box 1450
Alexandria, Virginia 22313-1450
or faxed to 571-273-8300.
Hand delivered responses should be brought to the United States Patent and Trademark Office Customer Service Window:
Randolph Building
401 Dulany Street
Alexandria, VA 22314.
/JAMES A REAGAN/Primary Examiner, Art Unit 3697
james.reagan@uspto.gov
571.272.6710 (Office)
571.273.6710 (Desktop Fax)