Detailed Action
This action is in response to application filed on 10/25/2023 which claims foreign priority to Korean application no. KR10-2022-0179929 filed on 12/20/2022.
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1-18 are pending.
Claims 7-12 are objected.
Claims 1-6, and 13-18 are rejected.
Information Disclosure Statement
The information disclosure Statement (IDS) submitted on 10/25/2023 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the IDS statements are being considered by the examiner.
Drawings
The drawings submitted on 10/25/2023 are accepted.
Claim Objections
Claims 7 and 13 recites “API”. All abbreviations should be written out at least once in the claim.
Claim 7 recites the limitation "the rule table" in line 3. There is insufficient antecedent basis for this limitation in the claim.
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.
Claim 1 is rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Claim 1:
In summary, claim 1 recites “gateway apparatus comprising: a sub-processing unit… a setting unit… main processing unit…”. The specification of present application fails to provide deliberate/clear and limiting definition for the above noted components. Under broadest reasonable interpretation, “a sub-processing unit and “main processing unit” can fairly construed as software per se (e.g., virtualized processors and/or software functions). Furthermore, “a setting unit” can fairly be construed as carrier waves and/or signal per se.
Thus, the recited “gateway apparatus” is not a "process", a "machine", a "manufacture", or "composition of matter", as defined in 35 U.S.C. 101.
At least due to dependency, dependent claims 2-6 are rejected under the same rational as noted above for claim 1.
Claim 13 is rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Claim 13:
In summary, claim 13 recites “API setting system comprising: one gateway apparatus… API manager device… gateway apparatus comprises: a sub-processing unit… a setting unit… main processing unit…”. The specification of present application fails to provide deliberate/clear and limiting definition for the above noted components. Under broadest reasonable interpretation, “gateway apparatus comprises: a sub-processing unit and main processing unit” and “API manager device” can fairly construed as software per se (e.g., virtualized processors and/or software functions). Furthermore, “a setting unit” can fairly be construed as carrier waves and/or signal per se.
Thus, the recited “API setting system” is not a "process", a "machine", a "manufacture", or "composition of matter", as defined in 35 U.S.C. 101.
At least due to dependency, dependent claims 14-18 are rejected under the same rational as noted above for claim 13.
Examiner Note: Claims1-18 are interpreted in view of specification paragraphs 0004-0006, 0025, 0060 as providing technical solution (e.g. using two rule tables) to a technical problem (e.g. lock which causes performance degradation), thereby improving computing device/environment performance by minimizing lock in a multi thread environment.
Allowable Subject Matter
Claims 1-18 are allowable if above noted rejections and objections are overcome via amendments and/or arguments. Reasons for allowance will be held in abeyance until all matters in the prosecution are closed.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant’s disclosure.
Cycle-efficient TDM Timeslot Remapping For Network Processing Engines
DOCUMENT ID
US 20050111475 A1
DATE PUBLISHED
2005-05-26
Abstract
A method and apparatus for remapping channel data are presented. Multiple successive frames carrying data in timeslots are received. The timeslots are assigned to channels so that data for the channels includes interleaved data. The data from the multiple successive frames for each of a predetermined number of the timeslots are aggregated. The aggregated data is mapped, by timeslot, to produce a timeslot-based map. The aggregated data of the timeslot-based map is remapped to produce a channel-based map in which the data for the channels are grouped together by channel in the order that the data were received.
… [0018] As shown in FIG. 2, the timeslot-remap information 50 can further include a second, "shadow" copy of the timeslot-remap table, indicated by reference numeral 51b. The timeslot-remap table 51a is the active table that is used by the NPE remap software. The shadow table 51b is used to store a new configuration as it is being programmed--an action that could take an extended period of time. When a complete new configuration is stable and ready to be used, the NPE software sets the change-table request indicator 58 (which may be implemented as a single bit) to signal to the NPE remap process 46 that a timeslot-remap table update has occurred…
APPLICATION PROGRAMMING INTERFACE (API) ENABLER FOR UPDATED APIs
DOCUMENT ID
US 20240078140 A1
DATE PUBLISHED
2024-03-07 US 20240078140 A1
Abstract
According to some embodiments, systems and methods are provided, including a repository storing at least an Application Programming Interface (API) mapping table; a memory storing processor-executable program code; and a processing unit to execute the processor-executable program code to: receive an input of one or more legacy API identification elements for a legacy API; determine whether the received legacy API identification elements correspond to a standard legacy API; in a case the received legacy API identification elements do correspond to a standard legacy API, determine whether a corresponding updated API is available; in a case the corresponding updated API is available, determine whether the legacy API includes at least one extension; and in a case the legacy API does include at least one extension, generate an updated corresponding API extension, and transmit the corresponding updated API and the updated corresponding API extension to the user. Numerous other aspects are provided.
ON-SITE ARTIFICIAL INTELLIGENCE APPLICATION PROGRAMMING INTERFACES FOR ROUTING AND ADAPTING TRAFFIC
DOCUMENT ID
US 20230388226 A1
DATE PUBLISHED
2023-11-30
Abstract
In some implementations, an application programming interfaces (API) manager may receive, at a set of artificial intelligence (AI) APIs, a set of inputs from a set of on-site devices. Accordingly, the API manager may route the set of inputs to a corresponding set of remote servers and may receive, from at least one server of the corresponding set of remote servers, at least one response based on at least one input, from the set of inputs, routed to the at least one server. The API manager may transmit the at least one response to a corresponding device from the set of on-site devices. Further, the API manager may modify at least one API, of the set of AI APIs, based on a traffic pattern associated with the set of inputs and the at least one response
Dynamic Management Of Network Policies Between Microservices Within A Service Mesh
DOCUMENT ID
US 11563636 B1
DATE PUBLISHED
2023-01-24
Abstract
Systems, methods and/or computer program products optimizing network policies between microservices of a service mesh. The service mesh tracks incoming API calls of applications and based on the historical transactions, the context of API calls, and the microservices in the microservice chain being invoked, network controls and policy configurations are set to optimize the transactions performed by the service mesh. Dimensions of the communications between microservices of the service mesh are dynamically optimized via the service mesh control plane using a policy optimizer. Optimized dimensions of service mesh transactions includes automated policy adjustments to retries between microservices, circuit breaking between microservices, automated timeout adjustments between microservices and intelligent rate limiting between microservices and/or rate limiting applied to user profiles.
See form 892.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MUSTAFA A AMIN whose telephone number is (571)270-3181. The examiner can normally be reached on Monday-Friday from 8:00 AM to 5:00 PM.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kevin Young, can be reached on 571-270-3180. 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 Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center for authorized users only. Should you have questions about access to Patent Center, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
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) Form at https://www.uspto.gov/patents/uspto-automated- interview-request-air-form.
/MUSTAFA A AMIN/ Primary Examiner, Art Unit 2194