Prosecution Insights
Last updated: November 20, 2026
Application No. 18/528,282

Automatic Image Composition with Item Promotion

Final Rejection §101§112
Filed
Dec 04, 2023
Examiner
VAN BRAMER, JOHN W
Art Unit
3622
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
eBay Inc.
OA Round
4 (Final)
33%
Grant Probability
At Risk
5-6
OA Rounds
1y 7m
Est. Remaining
67%
With Interview

Examiner Intelligence

Grants only 33% of cases
33%
Career Allowance Rate
193 granted / 581 resolved
-18.8% vs TC avg
Strong +34% interview lift
Without
With
+33.5%
Interview Lift
resolved cases with interview
Typical timeline
4y 7m
Avg Prosecution
29 currently pending
Career history
616
Total Applications
across all art units

Statute-Specific Performance

§101
28.8%
-11.2% vs TC avg
§103
30.3%
-9.7% vs TC avg
§102
17.5%
-22.5% vs TC avg
§112
15.8%
-24.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 581 resolved cases

Office Action

§101 §112
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 . Response to Amendment The amendment filed on July 16, 2026, cancelled no claims. Claims 1, 12, 18, and 20 were amended and no new claims were added. Thus, the currently pending claims addressed below are claims 1-2, 4-7, 9-13, 15-21, and 24-25. Claim Interpretation The following terms have been interpreted in light of the specification: Promotion data: Describes text-based parameters of the item such as promotion start date, promotion end date, and/or item discount amount (Based on at least paragraph 3, 20, 26, 28-32 and 85-92 of the applicant’s specification and the applicant’s arguments dated September 5, 2025). Claim Rejections - 35 USC § 112 The amendment filed on July 16, 2026, has overcome the 35 U.S.C. 112(b) rejections of claims 1-2, 4-7, 9-13, 15-21, and 24-25 detailed in the Office Action dated April 16, 2026. Thus, the rejections are hereby withdrawn. The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112: The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention. Claims 1-2, 4-7, 9-13, 15-21, and 24-25 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s), as amended and based on the applicant’s arguments, contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention. Claims 1, 12, and 18 include limitations for which the specification does not describe in sufficient detail to enable one of ordinary skill in the art to recognize that the inventor invented what is claimed. The test for sufficiency is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date. Claim 1, 12, and 18 recite: “generating, by the computing device, a promotion emblem image including one or more graphical promotion data fields and one or more embedded encoding elements configured to target promotion data and, when processed, populate the one or more graphical promotion data fields with information from the promotion data”. The applicant’s disclosure does not have support for generating a promotion emblem image including one or more embedded encoding elements configured to target promotion data, and when processed, populate the one or more graphical promotion data fields with information from the promotion data. First, the phrase “embedded encoding elements” is not used in the applicant’s specification. As such, the applicant’s specification does not support generating a promotion emblem image including one or more embedded encoding elements. The term “elements” is extremely broad and could possibly refer to a number of different terms used in the applicant’s specification, such as text elements, html tags, emblem composition attributes, graphical promotion data fields, encodings, etc. Of the numerous possible types of “embedded encoding elements” within the specification which the applicant may be referring to, only encodings are disclosed as being able to be executed because they are software instructions (see at least paragraph 30). According to the applicant’s specification these software encodings when executed These software encodings, when executed, can perform different task with regards to the generating of a promotion emblem image. Some encodings, such as discount remote retrieval encodings and date remote retrieval encodings are JavaScript code including a JSON object which identifies the parameter within the promotion data (i.e., discount amount, and date) to retrieve and populate in the one or more graphical promotion data fields (i.e., discount amount data field and date data field) as disclosed in the applicant’s specification in at least paragraphs 23 and 85-91). However, other software encodings such as encodings that define properties of the emblem such as its shape, color of various portions of the emblem, text displayed within graphical data fields of the emblem, the relative arrangement of feature, and other properties as disclosed in paragraphs 93-98. Since, these encodings are disclosed as software code in the applicant’s specification, they are cannot be properly construed as “elements”, because the elements of the emblem image would be the text and images that make up the emblem itself or possibly the fields of the emblem in which the text and images are place. Instead, these would be properly construed as software instead of an element. Additionally, the applicant’s claims require that the software encodings be executed to populates the graphical promotion data fields with information from the promotion data. However, according to the applicant’s specification only the remote encodings are able to be executed to populates the graphical promotion data fields with information from the promotion data. As such, the applicant’s specification does not have support for the more generic software “encodings” being executable to populate the graphical promotion data fields with information from the promotion data. In fact, according to the applicants specification the other software “encodings” such as encodings that define properties of the emblem such as its shape, color of various portions of the emblem, the relative arrangement of feature, and other properties, are executable to perform a different function altogether, and do not access the promotion data to perform such functions. Finally, this limitation in the claims is a genus limitation described using functional claim language and encompasses any and all software implementations capable of accessing the data in the promotion data. In order to have support for this genus, there must be sufficient species of this being performed in the applicant’s specification to prove possession of the claimed genus of any and all possible software implementations. The examiner has only been able to identify 2 species of software encoded in a promotion emblem image that are capable of being executed to populates the graphical promotion data fields with information from the promotion data. The first species is a discount remote retrieval encoding comprising JavaScript code including a JSON object which identifies the parameter within the promotion data (i.e., discount amount parameter) to retrieve and populate in the one or more graphical promotion data fields (i.e., discount amount data field). The second is a date remote retrieval encoding comprising JavaScript code including a JSON object which identifies the parameter within the promotion data (i.e., date parameter) to retrieve and populate in the one or more graphical promotion data fields (i.e., date data field). These two species are insufficient to prove the applicant invented the claimed genus. In fact, these two species are insufficient to prove the applicant invented an invention in which can perform any and all possible types of remote retrieval encodings. Instead, the applicant’s specification is only able to be said to support remote retrieval encoding comprising JavaScript code which includes a JSON object that identifies the parameter within the promotion data to be retrieved and populated. As per the “Supplementary Examination Guidelines for Determining Compliance with 35 U.S.C. and for Treatment of Related Issues in Patent Applications” issued on January 21, 2011 and MPEP 2161.01, the first paragraph of § 112 contains a written description requirement that is separate and distinct from the enablement requirement. To satisfy the written description requirement, the specification must describe the claimed invention in sufficient detail that one skilled in the art can reasonably conclude that the inventor had possession of the claimed invention. Specifically, the specification must describe the claimed invention in a manner understandable to a person of ordinary skill in the art and show that the inventor actually invented the claimed invention. The written description requirement of § 112, ¶ 1 applies to all claims including original claims that are part of the disclosure as filed. Claims may fail to satisfy the written description requirement when the invention is claimed and described in functional language, but the specification does not sufficiently identify how the invention achieves the claimed function. The problem is especially acute with genus claims that use functional language to define the boundaries of a claimed genus. In such a case, the functional claim may simply claim a desired result and may do so without describing species that achieve that result. But the specification must demonstrate that the applicant has made a generic invention that achieves the claimed result and do so by showing that the applicant has invented species sufficient to support a claim to the functionally-defined genus. The level of detail required to satisfy the written description requirement varies depending on the nature and scope of the claims and on the complexity and predictability of the relevant technology. Computer-implemented inventions are often disclosed and claimed in terms of their functionality. This is because writing computer programming code for software to perform specific functions is normally within the skill of the art once those functions have been adequately disclosed. Nevertheless, for computer-implemented inventions, the determination of the sufficiency of disclosure will require an inquiry into both the sufficiency of the disclosed hardware as well as the disclosed software due to the interrelationship and interdependence of computer hardware and software. When examining computer-implemented functional claims, examiners should determine whether the specification discloses the computer and the algorithm (e.g., the necessary steps and/or flowcharts) that perform the claimed function in sufficient detail such that one of ordinary skill in the art can reasonably conclude that the inventor invented the claimed subject matter. Specifically, if one skilled in the art would know how to program the disclosed computer to perform the necessary steps described in the specification to achieve the claimed function and the inventor was in possession of that knowledge, the written description requirement would be satisfied. If the specification does not provide a disclosure of the computer and algorithm in sufficient detail to demonstrate to one of ordinary skill in the art that the inventor possessed the invention including how to program the disclosed computer to perform the claimed function, a rejection under § 112, ¶ 1 for lack of written description must be made. In the instant case, the claimed invention fails to satisfy the written description requirement because the invention is a genus claim and described in functional language but the specification does not sufficiently identify how the invention achieves the claimed function because genus claims that use functional language to define the boundaries of a claimed genus. The claims simply claim a desired result, and does so without describing species that achieve that result. As detail above, the specification provides no showing that the applicant has invented species sufficient to support the claim to the functionally-defined genus. There are only two species of said genus disclosed in the applicant’s disclosure and both species require that the remote encoding comprise JavaScript code including a JSON object which identifies the parameter within the promotion data (i.e., date parameter) to be retrieved and populated. One of ordinary skill in the art would not be able to conclude that the applicant possessed an invention in which the remote encoding could be performed in another manner. This is especially true given the limitation which requires that this remote encoding allows for the promotion data populating the data fields be updatable in the combined image. Many of the standard mechanisms for programming such remote encoding would not be updateable in the manner claimed. Likewise of the standard mechanisms which would be updatable, they would not necessarily allow the updating to occur when the promotion emblem image is in the combined image without modifying pixel data of the digital image. Furthermore, there are no algorithms or flow charts that describe the specific details necessary for implementation of the claimed invention using either of these two species of the claimed genus, much less a disclosure of an algorithm or flow chart for the claimed genus itself. Hence, it is clear that the specification fails to satisfy the written description because it does not sufficiently identify how the invention achieves the claimed functionally defined genus. An adequate written description of a claimed genus requires more than the generic statement of the inventions boundaries as presented in the applicant’s disclosure. Dependent claims 2, 6-7, 9-11, 13, 15-17 and 19-21 fail to correct the deficiencies of the claims from which they depend and, as such, are rejected by virtue of dependency. 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 1-2, 4-7, 9-11, and 21 are directed to a method which would be classified under one of the listed statutory classifications (i.e., 2019 Revised Patent Subject Matter Eligibility Guidance (hereinafter “PEG”) “PEG” Step 1=Yes). However, claims 1-2, 4-7, 9-11, and 21 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Claim(s) 1-2, 4-5, and 11 recite(s) the following abstract idea: generating a promotional emblem image including one or more graphical promotion data fields and one or more embedded JavaScript Notation (JSON) objects comprising parameters identifying target promotion data in a promotion dataset to be populated in the one or more graphical promotion data fields, wherein the promotion emblem image is a scalable vector graphic (SVG) image defined by an image encoding structure, wherein the one or more JavaScript Object Notation (JSON) objects are embedded within the image encoding structure, wherein the one or more JSON objects includes a promotion date parameter (i.e., object) and a promotion discount parameter (i.e., object); (Examiner’s note: a JSON object is a collection of key-value pairs included in curly braces. As such, it is merely a set of key value pairs) receiving a digital image of an item; receiving a user selection of the promotional emblem image; and responsive to receiving the user selection of the promotional emblem image: identifying an instance of the target promotion data of the item in the promotion dataset, the instance of the promotion data associated with the item; populating the one or more graphical promotion data fields with information from the instance of the target promotion data of the item through processing the one or more JSON objects, wherein the populating replaces the one or more JSON objects with the information from the promotion data; forming a combined image by combining the promotional emblem image including the one or more graphical promotion data fields populated with the information from the instance of the target promotion data with the digital image in an overlapping arrangement non-destructive to the digital image such that the information of the instance of the target promotion data populating the one or more graphical promotion data fields of the promotion emblem image in the combined image is updatable in the combined image without modifying pixel data of the image; and outputting the combined image for display in association with a listing for the item, wherein outputting the combined image for display includes replacing the digital image in a listing of the item displayed with the combined image. The limitations as detailed above, as drafted, falls within the “Certain Method of Organizing Human Activity” grouping of abstract ideas namely commercial or legal interactions because they recite advertising, marketing and sales activities or behaviors. Accordingly, the claim recites an abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes). This judicial exception is not integrated into a practical application because the claim only recites the additional elements of: a computing device executing software (e.g., embedded encoding elements) which is merely a general-purpose computer executing software; a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision); and generating a dynamic SVG with an embedded encoding element (i.e., software encoding) within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object (e.g., a generic computer component as it is a traditional way in which dynamic SVGs tags are intended to operate). When analyzing these additional elements, both individually and as a whole, the main question that needs to be answered is whether the dynamic SVG being claimed is a technical element of the claim which results in an improvement to a traditional SVG capable of transforming the abstract idea into a practical application under Step 2a, Prong 2. The applicant’s disclosure in figures 4-5 and paragraphs 85-98 describe how the invention dynamically updates the SVG using a JavaScript function including the JSON object. However, these sections of the applicant’s disclosure do not describe any problems encountered when including a JavaScript function with a JSON object within an SVG, nor any technical solutions for overcoming such problems. Furthermore, the applicant’s disclosure provides no specific information regarding how one of ordinary skill in the art would need to implement such an SVG. The closest thing to a specific technical implementation is found in figure 5. In figure 5, short snippets of barely legible code for implementing such an SVG are disclosed. Item 500 includes standard SVG shape encoding. Item 502 is SVG text encoding including the standard tspan tag. Within the first standard tspan tag in figure 5 the applicant has included item 406 and within the second standard tspan tag the applicant has included item 400. Based on paragraphs 86 and 89, item 400 and 406 are respective JavaScript functions that include respective JSON objects. There is no disclosure in the applicant’s disclosure of the specific JavaScript function itself nor the creation or structure of the JSON object. There is no disclosure regarding whether the JavaScript function is within the SVG file using the standard <script>…</script> tags or located external to the SVG file. Instead, the applicant merely assumes that one of ordinary skill in the art would already know how incorporate remote retrieval encoding with the SVG using JavaScript functions that includes JSON object. This weighs heavily against the generating of the dynamic SVG being a new type of SVG that the applicant has invented. Next, the examiner considered the significance of a JavaScript function that includes a JSON object. As disclosed in W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6, which discloses on page 1 that JSON is merely a format for storing and transporting data. JSON is text, and can be transported anywhere, and read by any programming language. JavaScript Objects can be converted to JSON, and JSON can be converted back to JavaScript Object. Thus, it would not appear that a JavaScript function with a JSON object would be a technical improvement of any kind. Next, the examiner considered whether it is unusual to including JavaScript within an SVG file. Based on W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165, which discloses on at least pages 56-57 and 71-77 that including JavaScript in an SVG was standard by at least 2010 by using the standard <script> tag. Next, the examiner considered whether it was unusual for JavaScript in an SVG to access a JSON object. Based on Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which discloses on pages 22-24 that SVG is designed to work with CSS, JavaScript, HTML, and other XML languages. The following SVG elements are used to integrate code from those languages in your SVG markup: <script> element can be used to include JSON data in the markup without parsing it, so that another script can access it by reading this element’s text content using type="text/json". Thus, based on these three references, generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object appears to be a normal way in which SVG markup language is intended to operate. SVG is an XML-based vector graphic format that utilizes standardized tags, much like tags in an HTML document, to generate a graphic. These tags appear to already include the functionality for generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object. Thus, every factor considered from the applicant’s disclosure, as well as, the traditional functionalities of SVG tags weighs against this being a technical improvement and instead provides a clear indication that standard SVG functionality is merely being used as a tool to implement the abstract idea. As such, the additional element of a computing device with a computer-readable storage media executing software code (e.g., a general-purpose computer with a generic computer component), a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision), and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object, whether considered individually or as a whole, amount to using a general-purpose computer with generic computer components as tools to merely implement the abstract idea. The following limitations, if removed from the abstract idea and considered additional elements, merely perform generic computer function of processing, storing, communicating (e.g., transmitting and receiving), and displaying data and, as such, are insignificant extra-solution activities (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving, by the computing device, a digital image of an item (receiving data); receiving, by the computing device via a graphical user interface (GUI) implemented by the computing device, a user selection of the promotional emblem including a graphical promotion data field (receiving data); and outputting, by the computing device, the combined image for display in the GUI, the combined image displayed in the GUI in association with a listing for the item implemented by the computing device, wherein outputting the combined image for display includes replacing the digital image in the listing of the item displayed with the combined image (transmitting data). The additional technical elements above are recited at a high-level of generality (i.e., as a generic processor and generic computer components performing a generic computers function of processing, communicating and displaying) such that it amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and generic computer components. The claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the additional technical elements above do not integrate the abstract idea/judicial exception into a practical application because it does not impose any meaningful limits on practicing the abstract idea. More specifically, the additional elements fail to include (1) improvements to the functioning of a computer or to any other technology or technical field (see MPEP 2106.05(a)), (2) applying or using a judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition (see Vanda memo), (3) applying the judicial exception with, or by use of, a particular machine (see MPEP 2106.05(b)), (4) effecting a transformation or reduction of a particular article to a different state or thing (see MPEP 2106.05(c)), or (5) applying or using the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception (see MPEP 2106.05(e) and Vanda memo). Rather, the limitations merely add the words “apply it” (or an equivalent) with the judicial exception, or mere instructions to implement an abstract idea on one or more computers, or merely uses computers as a tool to perform an abstract idea (see MPEP 2106.05(f)), or generally link the use of the judicial exception to a particular technological environment or field of use (see MPEP 2106.05(h)). Thus, the claim is “directed to” an abstract idea (i.e. “PEG” Revised Step 2A Prong Two=Yes) When considering Step 2B of the Alice/Mayo test, the claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims do not amount to significantly more than the abstract idea. More specifically, as discussed above with respect to integration of the abstract idea into a practical application, the additional elements of using a computing device, a graphical user interface, and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object (e.g. a general-purpose computer with generic computer components) to perform the claimed functions amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and one or more generic computer component as a tool. “Generic computer implementation” is insufficient to transform a patent-ineligible abstract idea into a patent-eligible invention (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2352, 2357) and more generally, “simply appending conventional steps specified at a high level of generality” to an abstract idea does not make that idea patentable (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Mayo, 132 S. Ct. at 1300). Moreover, “the use of generic computer elements like a microprocessor or user interface do not alone transform an otherwise abstract idea into patent-eligible subject matter (See FairWarning, 120 U.S.P.Q.2d. 1293, citing DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1256 (Fed. Cir. 2014)). As such, the additional elements of the claim do not add a meaningful limitation to the abstract idea because they would be generic computer functions in any computer implementation. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea). Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of the computer or improves any other technology. Their collective functions merely provide generic computer implementation. The Examiner notes simply implementing an abstract concept on one or more computers, without meaningful limitations to that concept, does not transform a patent-ineligible claim into a patent-eligible one (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bancorp, 687 F.3d at 1280), limiting the application of an abstract idea to one field of use does not necessarily guard against preempting all uses of the abstract idea (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bilski, 130 S. Ct. at 3231), and further the prohibition against patenting an abstract principle “cannot be circumvented by attempting to limit the use of the [principle] to a particular technological environment” (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Flook, 437 U.S. at 584), and finally merely limiting the field of use of the abstract idea to a particular existing technological environment does not render the claims any less abstract (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2358; Mayo, 132 S. Ct. at 1294; Bilski v. Kappos, 561 U.S. 593, 612 (2010); Content Extraction & Transmission LLC v. Wells Fargo Bank, Nat’l Ass’n, 776 F.3d 1343, 1348 (Fed. Cir. 2014); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014). Applicant herein only requires one or more general-purpose computer and generic computer components (as evidenced from figures 1 and 10, as well as, paragraphs 35 and 127-134 of the applicant’s specification which discloses that the computing device is a general-purpose computer with generic computer components; the Intellectual Ventures I v. Capital One decision which found that a generic interactive interface that provides information to and accepts user input is a generic computer element; the prior arts of Zorzi et al. (PGPUB: 2023/0146018 – paragraph 37 and claim 5) and Uzgin et al. (PGPUB: 2019/0043231 – paragraphs 43 and 87), which both disclose that, prior to the effective filing date of the instant invention standard vector formats for vector files include one or more of SVG and JSON formats; and W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6; W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165; and Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which are all used to disclose that SVG tags that include JavaScript for accessing JSON objects were well-known prior to the effective filing data of the applicant’s invention); therefore, there does not appear to be any alteration or modification to the generic activities indicated, and they are also therefore recognized as insignificant activity with respect to eligibility. Finally, the following limitations, if removed from the abstract idea and considered additional elements, would be considered insignificant extra solution activity as they are directed to merely receiving, displaying, storing, and/or transmitting data (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving, by the computing device, a digital image of an item (receiving data); receiving, by the computing device via a graphical user interface (GUI) implemented by the computing device, a user selection of the promotional emblem including a graphical promotion data field (receiving data); and outputting, by the computing device, the combined image for display in the GUI, the combined image displayed in the GUI in association with a listing for the item implemented by the computing device, wherein outputting the combined image for display includes replacing the digital image in the listing of the item displayed with the combined image (transmitting data). Thus, taken individually and in combination, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea) (i.e., “PEG” Step 2B=No). The dependent claims 6-7, 9-10, and 21 appear to merely further limit the abstract idea by further limiting the generating of the combined image which is considered part of the abstract idea (Claims 6); adding an additional step of layering the promotion emblem in the overlapping arrangement which is considered part of the abstract idea (Claim 7); further limiting the information from the promotion data to include a promotion start date, a promotion end date, and a promotion discount which is considered part of the abstract idea (Claim 9); adding an additional step of flattening the combined image which is considered part of the abstract idea (Claim 10); and adding an additional step of updating the appearance of the promotion emblem image which is considered part of the abstract idea (Claim 21), and therefore only further limit the abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes), does/do not include any new additional elements that are sufficient to amount to significantly more than the judicial exception, and as such are “directed to” said abstract idea (i.e. “PEG” Step 2A Prong Two=Yes); and do not add significantly more than the idea (i.e. “PEG” Step 2B=No). Thus, based on the detailed analysis above, claims 1-2, 4-7, 9-11, and 21 are not patent eligible. Claims 18-20, and 25 are directed to methods and a system which would be classified under one of the listed statutory classifications (i.e., 2019 Revised Patent Subject Matter Eligibility Guidance (hereinafter “PEG”) “PEG” Step 1=Yes). However, claims 18-20, and 25 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Claim(s) 18 and 25 recite(s) the following abstract idea: generating a promotional emblem image including one or more graphical promotion data fields and one or more embedded JavaScript Notation (JSON) objects comprising parameters identifying target promotion data in a promotion dataset to be populated in the one or more graphical promotion data fields, wherein the promotion emblem image is as a scalable vector graphic (SVG) image defined by an image encoding structure, and the one or more embedded encoding elements include one or more JavaScript Object Notation (JSON) objects embedded within the image encoding structure, wherein the one or more JavaScript Object Notation (JSON) objects are embedded within the image encoding structure (Examiner’s note: a JSON object is a collection of key-value pairs included in curly braces. As such, it is merely a set of key value pairs); receiving a digital image of an item; receiving a user selection of the promotional emblem image; and responsive to receiving the user selection of the promotional emblem image: identifying an instance of the target promotion data of the item from the promotion dataset, the instance of the target promotion data associated with the item; populating the one or more graphical promotion data fields with information from the instance of the target promotion data of the item through processing the one or more JavaScript Object Notation (JSON) objects, wherein processing the one or more JavaScript Object Notation (JSON) objects replaces information in the one or more graphical promotion data fields with the information from the promotion data; forming a combined image by combining the promotional emblem image including the one or more graphical promotion data fields populated with the information from the instance of the target promotion data of the item with the digital image in an overlapping arrangement non-destructive to the digital image such that the information from the instance of the target promotion data populating the one or more graphical promotion data fields of the promotion emblem image in the combined image is updatable in the combined image without modifying the pixel data of the digital image; and outputting the combined image for display, the combined image displayed in association with a listing for the item. The limitations as detailed above, as drafted, falls within the “Certain Method of Organizing Human Activity” grouping of abstract ideas namely commercial or legal interactions because they recite advertising, marketing and sales activities or behaviors. Accordingly, the claim recites an abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes). This judicial exception is not integrated into a practical application because the claim only recites the additional elements of: a computing device with a computer-readable storage media executing software (e.g. one or more embedded encoding elements) which is merely a a general-purpose computer with a generic computer component executing software; a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision); and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object (e.g., a generic computer component as it is a traditional way in which dynamic SVGs tags are intended to operate). When analyzing these additional elements, both individually and as a whole, the main question that needs to be answered is whether the dynamic SVG being claimed is a technical element of the claim which results in an improvement to a traditional SVG capable of transforming the abstract idea into a practical application under Step 2a, Prong 2. The applicant’s disclosure in figures 4-5 and paragraphs 85-98 describe how the invention dynamically updates the SVG using a JavaScript function including the JSON object. However, these sections of the applicant’s disclosure do not describe any problems encountered when including a JavaScript function with a JSON object within an SVG, nor any technical solutions for overcoming such problems. Furthermore, the applicant’s disclosure provides no specific information regarding how one of ordinary skill in the art would need to implement such an SVG. The closest thing to a specific technical implementation is found in figure 5. In figure 5, short snippets of barely legible code for implementing such an SVG are disclosed. Item 500 includes standard SVG shape encoding. Item 502 is SVG text encoding including the standard tspan tag. Within the first standard tspan tag in figure 5 the applicant has included item 406 and within the second standard tspan tag the applicant has included item 400. Based on paragraphs 86 and 89, item 400 and 406 are respective JavaScript functions that include respective JSON objects. There is no disclosure in the applicant’s disclosure of the specific JavaScript function itself nor the creation or structure of the JSON object. There is no disclosure regarding whether the JavaScript function is within the SVG file using the standard <script>…</script> tags or located external to the SVG file. Instead, the applicant merely assumes that one of ordinary skill in the art would already know how incorporate remote retrieval encoding with the SVG using JavaScript functions that includes JSON object. This weighs heavily against the generating of the dynamic SVG being a new type of SVG that the applicant has invented. Next, the examiner considered the significance of a JavaScript function that includes a JSON object. As disclosed in W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6, which discloses on page 1 that JSON is merely a format for storing and transporting data. JSON is text, and can be transported anywhere, and read by any programming language. JavaScript Objects can be converted to JSON, and JSON can be converted back to JavaScript Object. Thus, it would not appear that a JavaScript function with a JSON object would be a technical improvement of any kind. Next, the examiner considered whether it is unusual to including JavaScript within an SVG file. Based on W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165, which discloses on at least pages 56-57 and 71-77 that including JavaScript in an SVG was standard by at least 2010 by using the standard <script> tag. Next, the examiner considered whether it was unusual for JavaScript in an SVG to access a JSON object. Based on Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which discloses on pages 22-24 that SVG is designed to work with CSS, JavaScript, HTML, and other XML languages. The following SVG elements are used to integrate code from those languages in your SVG markup: <script> element can be used to include JSON data in the markup without parsing it, so that another script can access it by reading this element’s text content using type="text/json". Thus, based on these three references, generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object appears to be a normal way in which SVG markup language is intended to operate. SVG is an XML-based vector graphic format that utilizes standardized tags, much like tags in an HTML document, to generate a graphic. These tags appear to already include the functionality for generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object. Thus, every factor considered from the applicant’s disclosure, as well as the traditional functionalities of SVG tags weighs against this being a technical improvement and instead provides a clear indication that standard SVG functionality is merely being used as a tool to implement the abstract idea. As such, the additional element of a computing device with a computer-readable storage media (e.g., a general-purpose computer with a generic computer component), a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision), and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object, whether considered individually or as a whole, amount to using a general-purpose computer with generic computer components as tools to merely implement the abstract idea. The following limitations, if removed from the abstract idea and considered additional elements, merely perform generic computer function of processing, storing, communicating (e.g., transmitting and receiving), and displaying data and, as such, are insignificant extra-solution activities (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving a digital image of an item (receiving data); receiving, via a graphical user interface (GUI), a user selection of the promotional emblem image (receiving data); and outputting the combined image for display in the GUI, the combined image displayed in the GUI in association with a listing for the item implemented by the one or more computing devices (transmitting data). The additional technical elements above are recited at a high-level of generality (i.e., as a generic processor and generic computer components performing a generic computers function of processing, communicating and displaying) such that it amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and generic computer components. The claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the additional technical elements above do not integrate the abstract idea/judicial exception into a practical application because it does not impose any meaningful limits on practicing the abstract idea. More specifically, the additional elements fail to include (1) improvements to the functioning of a computer or to any other technology or technical field (see MPEP 2106.05(a)), (2) applying or using a judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition (see Vanda memo), (3) applying the judicial exception with, or by use of, a particular machine (see MPEP 2106.05(b)), (4) effecting a transformation or reduction of a particular article to a different state or thing (see MPEP 2106.05(c)), or (5) applying or using the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception (see MPEP 2106.05(e) and Vanda memo). Rather, the limitations merely add the words “apply it” (or an equivalent) with the judicial exception, or mere instructions to implement an abstract idea on one or more computers or merely uses computers as a tool to perform an abstract idea (see MPEP 2106.05(f)), or generally link the use of the judicial exception to a particular technological environment or field of use (see MPEP 2106.05(h)). Thus, the claim is “directed to” an abstract idea (i.e. “PEG” Revised Step 2A Prong Two=Yes) When considering Step 2B of the Alice/Mayo test, the claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims do not amount to significantly more than the abstract idea. More specifically, as discussed above with respect to integration of the abstract idea into a practical application, the additional elements of using a computing device with a memory executing software, a graphical user interface, and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object (e.g. a general-purpose computer with generic computer components) to perform the claimed functions amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and one or more generic computer component. “Generic computer implementation” is insufficient to transform a patent-ineligible abstract idea into a patent-eligible invention (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2352, 2357) and more generally, “simply appending conventional steps specified at a high level of generality” to an abstract idea does not make that idea patentable (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Mayo, 132 S. Ct. at 1300). Moreover, “the use of generic computer elements like a microprocessor or user interface do not alone transform an otherwise abstract idea into patent-eligible subject matter (See FairWarning, 120 U.S.P.Q.2d. 1293, citing DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1256 (Fed. Cir. 2014)). As such, the additional elements of the claim do not add a meaningful limitation to the abstract idea because they would be generic computer functions in any computer implementation. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea). Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of the computer or improves any other technology. Their collective functions merely provide generic computer implementation. The Examiner notes simply implementing an abstract concept on one or more computers, without meaningful limitations to that concept, does not transform a patent-ineligible claim into a patent-eligible one (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bancorp, 687 F.3d at 1280), limiting the application of an abstract idea to one field of use does not necessarily guard against preempting all uses of the abstract idea (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bilski, 130 S. Ct. at 3231), and further the prohibition against patenting an abstract principle “cannot be circumvented by attempting to limit the use of the [principle] to a particular technological environment” (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Flook, 437 U.S. at 584), and finally merely limiting the field of use of the abstract idea to a particular existing technological environment does not render the claims any less abstract (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2358; Mayo, 132 S. Ct. at 1294; Bilski v. Kappos, 561 U.S. 593, 612 (2010); Content Extraction & Transmission LLC v. Wells Fargo Bank, Nat’l Ass’n, 776 F.3d 1343, 1348 (Fed. Cir. 2014); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014). Applicant herein only requires one or more general-purpose computer and generic computer components (as evidenced from figures 1 and 10, as well as, paragraphs 35 and 127-134 of the applicant’s specification which discloses that the computing device is a general-purpose computer with generic computer components; the Intellectual Ventures I v. Capital One decision which found that a generic interactive interface that provides information to and accepts user input is a generic computer element; the prior arts of Zorzi et al. (PGPUB: 2023/0146018 – paragraph 37 and claim 5) and Uzgin et al. (PGPUB: 2019/0043231 – paragraphs 43 and 87), which both disclose that, prior to the effective filing date of the instant invention standard vector formats for vector files include one or more of SVG and JSON formats; and W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6; W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165; and Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which are all used to disclose that SVG tags that include JavaScript for accessing JSON objects were well-known prior to the effective filing data of the applicant’s invention); therefore, there does not appear to be any alteration or modification to the generic activities indicated, and they are also therefore recognized as insignificant activity with respect to eligibility. Finally, the following limitations, if removed from the abstract idea and considered additional elements, would be considered insignificant extra solution activity as they are directed to merely receiving, displaying, storing, and/or transmitting data (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving a digital image of an item (receiving data); receiving, via a graphical user interface (GUI), a user selection of the promotional emblem image (receiving data); and outputting the combined image for display in the GUI, the combined image displayed in the GUI in association with a listing for the item implemented by the one or more computing devices (transmitting data). Thus, taken individually and in combination, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea) (i.e., “PEG” Step 2B=No). The dependent claims 19-20 appear to merely further limit the abstract idea by adding an additional step of controlling deployment of the combined image which is considered part of the abstract idea (Claim 19); and adding an additional step of converting (i.e., flattening) the combined image to a single raster image responsive to a condition being satisfied, and doing nothing to the combined image if the condition is not satisfied which is considered part of the abstract idea (Claim 20), and therefore only further limit the abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes), does/do not include any new additional elements that are sufficient to amount to significantly more than the judicial exception, and as such are “directed to” said abstract idea (i.e. “PEG” Step 2A Prong Two=Yes); and do not add significantly more than the idea (i.e. “PEG” Step 2B=No).. Thus, based on the detailed analysis above, claims 18-20, and 25 are not patent eligible. Claims 12-13, 15-17 and 24 are directed to a method which would be classified under one of the listed statutory classifications (i.e., 2019 Revised Patent Subject Matter Eligibility Guidance (hereinafter “PEG”) “PEG” Step 1=Yes). However, claims 12-13, 15-17 and 24 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Claim(s) 12 and 24 recite(s) the following abstract idea: generating a promotional emblem image including one or more graphical promotion data fields and one or more embedded key value pairs comprising parameters identifying target promotion data in a promotion dataset to be populated in the one or more graphical promotion data fields, wherein the promotion emblem image is a scalable vector graphic (SVG) image defined by an image encoding structure, wherein the one or more embedded key value pairs is embedded within the image encoding structure; receiving a listing of an item on an electronic commerce platform, the listing including: promotion data describing promotion parameters of the item and a digital image of an item; receiving a user selection of the promotion emblem image; and responsive to receiving the user selection of the promotion emblem image: processing the one or more key value pairs to populate the one or more graphical promotion data fields with information from the promotion data; generating a combined image formed from the digital image of the item and the promotion emblem image, the promotion emblem image layered with the digital image of the item with a HyperText Markup Language (HTML) tag (i.e., element) in an overlapping arrangement non-destructive to the digital image without modifying pixel data of the digital image; and controlling deployment of the combined image within the listing for display based on the promotion parameters, wherein controlling deployment of the combined image within the listing includes replacing the digital image in the within with the combined image. The limitations as detailed above, as drafted, falls within the “Certain Method of Organizing Human Activity” grouping of abstract ideas namely commercial or legal interactions because they recite advertising, marketing and sales activities or behaviors. Accordingly, the claim recites an abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes). This judicial exception is not integrated into a practical application because the claim only recites the additional elements of: a computing device executing software (e.g., one or more embedded encoding elements and JavaScript potions) which is merely a general-purpose computer executing software; a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision); and generating a dynamic SVG with an embedded software (e.g., one or more embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript potion containing the key value pairs (e.g., a generic computer component as it is a traditional way in which dynamic SVGs tags are intended to operate). When analyzing these additional elements, both individually and as a whole, the main question that needs to be answered is whether the dynamic SVG being claimed is a technical element of the claim which results in an improvement to a traditional SVG capable of transforming the abstract idea into a practical application under Step 2a, Prong 2. The applicant’s disclosure in figures 4-5 and paragraphs 85-98 describe how the invention dynamically updates the SVG using a JavaScript function including the JSON object. However, these sections of the applicant’s disclosure do not describe any problems encountered when including a JavaScript function with a JSON object (i.e., key value pairs) within an SVG, nor any technical solutions for overcoming such problems. Furthermore, the applicant’s disclosure provides no specific information regarding how one of ordinary skill in the art would need to implement such an SVG. The closest thing to a specific technical implementation is found in figure 5. In figure 5, short snippets of barely legible code for implementing such an SVG are disclosed. Item 500 includes standard SVG shape encoding. Item 502 is SVG text encoding including the standard tspan tag. Within the first standard tspan tag in figure 5 the applicant has included item 406 and within the second standard tspan tag the applicant has included item 400. Based on paragraphs 86 and 89, item 400 and 406 are respective JavaScript functions that include respective JSON objects. There is no disclosure in the applicant’s disclosure of the specific JavaScript function itself nor the creation or structure of the JSON object. There is no disclosure regarding whether the JavaScript function is within the SVG file using the standard <script>…</script> tags or located external to the SVG file. Instead, the applicant merely assumes that one of ordinary skill in the art would already know how incorporate remote retrieval encoding with the SVG using JavaScript functions that includes JSON object. This weighs heavily against the generating of the dynamic SVG being a new type of SVG that the applicant has invented. Next, the examiner considered the significance of a JavaScript function that includes a JSON object. As disclosed in W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6, which discloses on page 1 that JSON is merely a format for storing and transporting data. JSON is text, and can be transported anywhere, and read by any programming language. JavaScript Objects can be converted to JSON, and JSON can be converted back to JavaScript Object. Thus, it would not appear that a JavaScript function with a JSON object would be a technical improvement of any kind. Next, the examiner considered whether it is unusual to including JavaScript within an SVG file. Based on W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165, which discloses on at least pages 56-57 and 71-77 that including JavaScript in an SVG was standard by at least 2010 by using the standard <script> tag. Next, the examiner considered whether it was unusual for JavaScript in an SVG to access a JSON object. Based on Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which discloses on pages 22-24 that SVG is designed to work with CSS, JavaScript, HTML, and other XML languages. The following SVG elements are used to integrate code from those languages in your SVG markup: <script> element can be used to include JSON data in the markup without parsing it, so that another script can access it by reading this element’s text content using type="text/json". Thus, based on these three references, generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object appears to be a normal way in which SVG markup language is intended to operate. SVG is an XML-based vector graphic format that utilizes standardized tags, much like tags in an HTML document, to generate a graphic. These tags appear to already include the functionality for generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object. Thus, every factor considered from the applicant’s disclosure, as well as the traditional functionalities of SVG tags weighs against this being a technical improvement and instead provides a clear indication that standard SVG functionality is merely being used as a tool to implement the abstract idea. As such, the additional element of a computing device with a computer-readable storage media (e.g., a general-purpose computer with a generic computer component), a graphical user interface for providing information to an accepting user input (e.g., a generic computer element as per the Intellectual Ventures I v. Capital One decision), and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript Object Notation (JSON) object, whether considered individually or as a whole, amount to using a general-purpose computer with generic computer components as tools to merely implement the abstract idea. The following limitations, if removed from the abstract idea and considered additional elements, merely perform generic computer function of processing, storing, communicating (e.g., transmitting and receiving), and displaying data and, as such, are insignificant extra-solution activities (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving, by the computing device, a listing of an item on an electronic commerce platform implemented by the computing device, the listing including: promotion data describing promotion parameters of the item and a digital image of an item (receiving data); receiving, by the computing device via a graphical user interface (GUI) implemented by the computing device, a user selection of the promotion emblem image (receiving data); and controlling, by the computing device, deployment of the combined image within the listing for display in the GUI based on the promotion parameters, wherein controlling deployment of the combined image within the listing includes replacing the digital image in the withing with the combined image (transmitting data). The additional technical elements above are recited at a high-level of generality (i.e., as a generic processor and generic computer components performing a generic computers function of processing, communicating and displaying) such that it amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and generic computer components. The claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the additional technical elements above do not integrate the abstract idea/judicial exception into a practical application because it does not impose any meaningful limits on practicing the abstract idea. More specifically, the additional elements fail to include (1) improvements to the functioning of a computer or to any other technology or technical field (see MPEP 2106.05(a)), (2) applying or using a judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition (see Vanda memo), (3) applying the judicial exception with, or by use of, a particular machine (see MPEP 2106.05(b)), (4) effecting a transformation or reduction of a particular article to a different state or thing (see MPEP 2106.05(c)), or (5) applying or using the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception (see MPEP 2106.05(e) and Vanda memo). Rather, the limitations merely add the words “apply it” (or an equivalent) with the judicial exception, or mere instructions to implement an abstract idea on one or more computers, or merely uses computers as a tool to perform an abstract idea (see MPEP 2106.05(f)), or generally link the use of the judicial exception to a particular technological environment or field of use (see MPEP 2106.05(h)). Thus, the claim is “directed to” an abstract idea (i.e. “PEG” Revised Step 2A Prong Two=Yes) When considering Step 2B of the Alice/Mayo test, the claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims do not amount to significantly more than the abstract idea. More specifically, as discussed above with respect to integration of the abstract idea into a practical application, the additional elements of using a computing device executing software, a graphical user interface, and generating a dynamic SVG with an embedded encoding element within a data field, wherein the embedded encoding element includes a JavaScript portion comprising key value pairs (e.g., JavaScript Object Notation (JSON) object) (e.g. a general-purpose computer with generic computer components) to perform the claimed functions amounts to no more than mere instructions to apply the exception using one or more general-purpose computers and one or more generic computer component. “Generic computer implementation” is insufficient to transform a patent-ineligible abstract idea into a patent-eligible invention (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2352, 2357) and more generally, “simply appending conventional steps specified at a high level of generality” to an abstract idea does not make that idea patentable (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Mayo, 132 S. Ct. at 1300). Moreover, “the use of generic computer elements like a microprocessor or user interface do not alone transform an otherwise abstract idea into patent-eligible subject matter (See FairWarning, 120 U.S.P.Q.2d. 1293, citing DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1256 (Fed. Cir. 2014)). As such, the additional elements of the claim do not add a meaningful limitation to the abstract idea because they would be generic computer functions in any computer implementation. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea). Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of the computer or improves any other technology. Their collective functions merely provide generic computer implementation. The Examiner notes simply implementing an abstract concept on one or more computers, without meaningful limitations to that concept, does not transform a patent-ineligible claim into a patent-eligible one (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bancorp, 687 F.3d at 1280), limiting the application of an abstract idea to one field of use does not necessarily guard against preempting all uses of the abstract idea (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Bilski, 130 S. Ct. at 3231), and further the prohibition against patenting an abstract principle “cannot be circumvented by attempting to limit the use of the [principle] to a particular technological environment” (See Accenture, 728 F.3d 1336, 108 U.S.P.Q.2d 1173 (Fed. Cir. 2013), citing Flook, 437 U.S. at 584), and finally merely limiting the field of use of the abstract idea to a particular existing technological environment does not render the claims any less abstract (See Affinity Labs, _F.3d_, 120 U.S.P.Q.2d 1201 (Fed. Cir. 2016), citing Alice, 134 S. Ct. at 2358; Mayo, 132 S. Ct. at 1294; Bilski v. Kappos, 561 U.S. 593, 612 (2010); Content Extraction & Transmission LLC v. Wells Fargo Bank, Nat’l Ass’n, 776 F.3d 1343, 1348 (Fed. Cir. 2014); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014). Applicant herein only requires one or more general-purpose computer and generic computer components (as evidenced from figures 1 and 10, as well as, paragraphs 35 and 127-134 of the applicant’s specification which discloses that the computing device is a general-purpose computer with generic computer components; the Intellectual Ventures I v. Capital One decision which found that a generic interactive interface that provides information to and accepts user input is a generic computer element; the prior arts of Zorzi et al. (PGPUB: 2023/0146018 – paragraph 37 and claim 5) and Uzgin et al. (PGPUB: 2019/0043231 – paragraphs 43 and 87), which both disclose that, prior to the effective filing date of the instant invention standard vector formats for vector files include one or more of SVG and JSON formats; and W3schools, JavaScript JSON Reference, January 19, 2023, https://web. archive.org/ web/20230119215806/https://www.w3schools.com/jsref/jsref_obj_json.asp, pages 1-6; W3C, An SVG Primer for Today’s Browser’s, September 2010, https:// www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SMIL_animations, pages 1-165; and Oreillymedia, Using SVG with CSS3 and HTML5 – Supplementary Material, July 6, 2022, https://web.archive.org/web/20220706014901/ https://oreillymedia.github.io/Using_SVG/guide/markup.html#integration, pages 1-56, which are all used to disclose that SVG tags that include JavaScript for accessing JSON objects were well-known prior to the effective filing data of the applicant’s invention); therefore, there does not appear to be any alteration or modification to the generic activities indicated, and they are also therefore recognized as insignificant activity with respect to eligibility. Finally, the following limitations, if removed from the abstract idea and considered additional elements, would be considered insignificant extra solution activity as they are directed to merely receiving, displaying, storing, and/or transmitting data (see MPEP 2016.05(d)(II) and MPEP 2106.05(g)): receiving, by the computing device, a listing of an item on an electronic commerce platform implemented by the computing device, the listing including: promotion data describing promotion parameters of the item and a digital image of an item (receiving data); receiving, by the computing device via a graphical user interface (GUI) implemented by the computing device, a user selection of the promotion emblem image (receiving data); and controlling, by the computing device, deployment of the combined image within the listing for display in the GUI based on the promotion parameters, wherein controlling deployment of the combined image within the listing includes replacing the digital image in the withing with the combined image (transmitting data). Thus, taken individually and in combination, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea) (i.e., “PEG” Step 2B=No). The dependent claims 13 and 15-17 appear to merely further limit the abstract idea by further limiting the promotional emblem image and further limiting the processing of the one or more embedder encoding element which are both considered part of the abstract idea (Claim 13); further limiting the controlling the deployment which is considered part of the abstract idea (Claims 15-16); further limiting the generating the combined image which is considered part of the abstract idea (Claim 17), and therefore only further limit the abstract idea (i.e. “PEG” Revised Step 2A Prong One=Yes), does/do not include any new additional elements that are sufficient to amount to significantly more than the judicial exception, and as such are “directed to” said abstract idea (i.e. “PEG” Step 2A Prong Two=Yes); and do not add significantly more than the idea (i.e. “PEG” Step 2B=No).. Thus, based on the detailed analysis above, claims 12-13, 15-17 and 24 are not patent eligible. Possible Allowable Subject Matter Claims 1-2, 4-7, 9-13, 15-21, and 24-25 are contain subject matter that would be allowable over the prior art if the applicant were to be able to overcome the 35 USC 112(a) rejections, and the 35 USC 101 rejections above. The following is a statement of reasons for the indication of allowable subject matter: The examiner has found prior art (see Gao et al. - CN104050568A; Uzgin et al. - 2019/0043231; and Shorthand.com (What’s the difference between SVG, PNG, and JPEG?, February 3, 2023, https://web.archive.org/web/20230203032116/ https://shorthand.com/the-craft/what-is-an-svg-file/index.html, pages 1-10) that discloses methods and a system comprising: one or more computing devices; and one or more computer-readable storage media storing instructions which, when executed by the one or more computing devices, cause the one or more computing devices to perform operations comprising: receiving a listing of an item on an electronic commerce platform, the listing including a graphical promotion dataset of the item; receiving, via a graphical user interface (GUI), a user selection of an promotion emblem including a graphical promotion data field; and responsive to receiving the user selection of the promotion emblem: identifying graphical promotion data of the item from the graphical promotion dataset; identifying a graphical promotion data field of the promotion emblem; processing a promotion data retrieval encoding within an image encoding structure of the promotion emblem by executing computer-readable instructions stored within the promotional data retrieval encoding that define graphical objects targeting the promotion data to retrieve the graphical promotion data of the item from the promotion dataset and populate the graphical promotion data field with the graphical promotion data of the item, thereby replacing the graphical promotion data field with the graphical promotion data; forming/generating a combined image by combining the promotion emblem including the graphical promotion data field populated with the promotion data of the item with the digital image in an overlapping arrangement non-destructive to the digital image; and controlling deployment of the combined image by outputting the combined image within the listing based on the promotion parameters for display in the GUI. While Gao, Uzgin, and Shorthand.com disclose a computer performing these steps with regards to graphical based items of the graphical promotion dataset, any text-based items in the promotion dataset would need to be input in the same namespace as the SVG file or updated manually. Based on the applicant’s specification, in at least paragraph 92-95 and 42, as well as, the applicant’s arguments filed on September 5, 2025, the promotional dataset includes text and the one or more embedded encodings (i.e., JavaScript functions comprising JSON objects) which are software instructions within the promotional emblem that is are executed by utilizing the key value pairs of the JSON objects to identify text associated textual categories in the promotional dataset and populate said text in the promotional data fields of the promotional emblem image. As such, the prior art of Gao, Uzgin, and Shorthand.com cannot be said to teach, as required by the limitations described in claims 1, 12, and 18, the claimed one or more embedded encodings (i.e., JavaScript functions comprising JSON objects) which are software instructions within the promotional emblem that is are executed by utilizing the key value pairs of the JSON objects to identify text associated textual categories in the promotional dataset and populate said text in the promotional data fields of the promotional emblem image. The examiner has also found prior art (see stackoverflow.com, Scripting <path> data in SVG (reading and modifying), November 21, 2021, https://web.archive.org/web/ 20211129035935/https://stackoverflow.com/questions/8053487/scripting-path-data-in-svg-reading-and-modifying, pages 1-6) that discloses including JavaScript in a <script> encoding of the SVG file, that when executed allows for the dynamic updating of text from a remote location. Thus, the examiner has found prior art which discloses each and every limitation of the claims. However, it would not have been obvious to one of ordinary skill in the art to combine these four different references without the use of impermissible hindsight by using the applicant’s claims as a roadmap. Thus, claims contain subject matter that would be allowable over the prior art of Gao, Uzgin, and Shorthand.com if the applicant were to be able to overcome the 35 USC 112(a) rejections and the 35 USC 101 rejections above. Response to Arguments Applicant's arguments filed July 16, 2025, have been fully considered but they are not persuasive. The applicant argues, with respect to the 112(a) rejections, that the claims as originally filed demonstrate possession of the claims genus. The examiner strongly disagrees. First, the originally filed claims recited executing instructions stored within an encoding of the emblem. Thus, according to the originally filed claims, the emblem included software encodings which were executed. This is not what is being recited in the claims as currently amended. The claims, as currently amended, recite one or more embedded encoding elements when processed populate the data filed with information from the promotion data. Thus, the current claims do not indicate that the claimed “embedded encoding elements” are software instructions which are executed. Likewise, the originally filed claims did not limit the instructions within the encoding of the emblem to performing the function of populating the data fields with information form the promotion data. As such, the claims as originally filed cannot be said to support the claims as currently amended and the applicant’s arguments are not convincing. Second, even if the applicant were to amend the claims to recite such software instructions and did not limit them to populating the data fields with information in the promotion data, the original filed claims cannot be said to provide proof that the applicant possessed the functionally claimed genus. While MPEP 2163 does state that the originally filed claims are part of the disclosure, it does not address whether a functionally claimed genus in such claims proves to one or ordinary skill in the art that the applicant possessed the claimed genus. The applicant’s specification actually states the functionally claimed genus in paragraph 23 of the specification. So whether such a genus was also stated in the originally filed claims is immaterial to the 112(a) rejection. As clearly outlined in the “Supplementary Examination Guidelines for Determining Compliance with 35 U.S.C. and for Treatment of Related Issues in Patent Applications” issued on January 21, 2011, the the written description requirement of § 112, ¶ 1 applies to all claims including original claims that are part of the disclosure as filed. Claims may fail to satisfy the written description requirement when the invention is claimed and described in functional language, but the specification does not sufficiently identify how the invention achieves the claimed function. The question is not whether the claims, as originally filed or not, simply recite a claimed functional genus. Instead, it is a matter of whether the specification describes the functional genus with enough detail to prove that the applicant possessed the functionally claimed genus. As outlined in said Supplementary Examination Guidelines, the specification needs to describe enough species of the functionally claimed genus to prove that applicant invented the functionally claimed genus. In the instant case there are only two species of code embedded within the emblem which populates information from the promotion dataset into fields of the emblem. Both of these species require that the code be programmed in the same manner using remote retrieval encoding comprising JavaScript functions that includes one or more JSON objects. The applicant’s specification provides no indication that the applicant was in possession of any other type of software instructions within the emblem that might have been capable of performing this populating. As such, it is clear that the rejections are proper. Therefore, the applicant’s arguments are not convincing, and the rejections have been maintained. The applicant’s arguments with respect to the 112(b) rejections are moot as the amendment has overcome the rejections. In regards to the 35 USC 101 rejection, the applicant argues that the claims as amended integrate the alleged abstract idea into a practical application under Step 2a, Prong 2 because they recite a specific technical improvement in the field of item listing promotion management that provides technical advantages over conventional system. The examiner disagrees. In order to overcome a 35 USC 101 rejection under Step 2a, Prong 2, any purported technical improvement that is capable of transforming an abstract idea into a practical application must be rooted in the “additional elements” of the claim. “Additional elements” are defined as those elements that are not part of the identified abstract idea itself. In fact MPEP 2106.05, specifically states that improvements rooted in the abstract idea which is merely applied using the “additional elements” as a tool cannot be considered an improvement in technology (see MPEP 2106.05(a) - “It is important to note, the judicial exception alone cannot provide the improvement”; and MPEP 2106.05(a)(II) - “However, it is important to keep in mind that an improvement in the abstract idea itself (e.g. a recited fundamental economic concept) is not an improvement in technology.”). As such, the argued technical solution to a technical solution cannot be considered an improvement in technology capable of transforming an abstract idea into a practical application under Step 2a, Prong 2 because the purported technical solution to a technical problem is rooted solely in the abstract idea itself which is merely applied using the “additional elements” as a tool. Improvements of this nature are improvements to an abstract idea which are improvements in ineligible subject matter (see the SAP v Investpic decision - Page 2, line 22 through Page 3, line 13 - Even assuming that the algorithms claimed are groundbreaking, innovative or even brilliant, the claims are ineligible because their innovation is an innovation in ineligible subject matter because they are nothing but a series of mathematical algorithms based on selected information and the presentation of the results of those algorithms. Thus, the advance lies entirely in the realm of abstract ideas, with no plausible alleged innovation in the non-abstract application realm. An advance of this nature is ineligible for patenting; and Page 10, lines 18-24 - Even if a process of collecting and analyzing information is limited to particular content, or a particular source, that limitations does not make the collection and analysis other than abstract.). As clearly articulated in the rejections above, the claimed “additional elements”, whether considered individually or in combination amount to no more than using a general-purpose computer with generic computer component and generating an SVG image in a traditional manner as tools for merely applying the abstract idea which is insufficient to transform an abstract idea into a practical application under Step 2a, Prong 2. Likewise, the examiner’s analysis does not indicate that the generating of the SVG was well-understood, routine, and conventional. Instead, it indicates that it was a known manner of generating SVG images. As such, the examiner has not made a reference to how well-known it was before the filing date of the applicant’s invention when performing the Step 2a, Prong 2 analysis as the applicant alleges. Finally, based on the applicant’s specification generating a composite image by generating an overlay of the emblem and placing it over the image is all that is required for the claimed “non-destructive manner” to be true. As such, there is no inherent technology involved in the claimed “non-destructive manner” which is why these limitations are considered part of the abstract idea itself and not “additional elements” of the claims. Therefore, the applicant’s arguments are not convincing, and the rejections have been maintained. The applicant argues that the claims overcome the 101 rejections under Step 2b because the ordered combination is not well-understood, routine, or conventional. The examiner disagrees. It appears that the applicant is misconstruing the requirements under Step 2b. Under Step 2b, it is the order combination of “additional elements” of the claims which overcome the 101 rejections if said combination of “additional elements” were not well-understood, routine, and conventional. There is no requirement under Step 2B to analyze the ordered steps of the abstract idea with respect to whether they were well-understood, routine, and conventional. In fact, MPEP 2106, makes it clear that merely applying the abstract idea using the “additional elements” as a tool are incapable of being considered significantly more than the abstract idea. The examiner has clearly considered the “additional elements” of the claims, both individually and as an order combination, and provided proof that these “additional elements” were indeed well-understood, routine, and conventional before the effective filing date of the invention. Since, the claims merely require using these well-understood, routine, and conventional “additional elements” as a tool to apply the abstract idea, the claims cannot be considered significantly more under Step 2b. Thus, the applicant’s arguments are not convincing, and the rejections have been maintained. The examiner notes, that it would hypothetically be possible to amend the claim so that they would be reciting an improvement in technology. Given the proof supplied by the examiner, when using an SVG programmed in the known way, and having the listing and the combined image comprising code embedded in the emblem the digital image are presented on a web page implemented by a single computer that also contains the promotion dataset, the claimed updating would not be an improvement to a technology. However, if the listing and the combined image are presented on a web page operated by a second computer, and the promotion data set remains on the currently claimed computer this would not be the case. If the code embedded in the emblem executes remote retrieval code on said second computer to access the promotional data set on the currently claimed computer, then this remote accessing of such data to update the emblem would be an improvement in technology given the state of the art before the effective filing date of the invention. This is because, before the effective filing date of the invention, the well understood, routine, and conventionally method of dynamically updating this information was when code of the SVG file is being executed by the same computer as the promotion data set. The examiner has been unable to find proof that such dynamic updating was well known when the combined image is displayed in a webpage implemented by a second computer and the promotion data set resides on a different computer remote for the second computer. However, for such an amendment to overcome the 101 rejections, the invention must comprise both the currently claimed computer and this new hypothetical second computer and must positively recite the steps of the abstract idea being performed by each said computer. This is the only way in which both computers could be considered “additional elements” of the claimed invention. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Li (PGPUB: 2022/0070514) which discloses obtaining an image of a product and promotion information for the product; determining a discount price for the product; and generating an overlay indicating the discount which is displayed on the product image. Pasala et al. (PGPUB: 2019/0346981) which discloses generating advertisements by obtaining an input file including image components, scalable vector graphic (SVG) components, text components, tween components, animation components, physics components, and augmented reality (AR) components; converting the components into JSON elements; and using a template generating a layered advertisement for consumption on a computing device. Stansell et al. (PGPUB: 2019/0244436) which discloses receiving an image and a promotional offer; analyzing the promotional offer; determining whether to display the promotional offer to a user; and overlaying the promotion on an image. Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN W VAN BRAMER whose telephone number is (571)272-8198. The examiner can normally be reached Monday-Thursday 5:30 am - 4 pm EST. 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, Spar Ilana can be reached at 571-270-7537. 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. /John Van Bramer/Primary Examiner, Art Unit 3622
Read full office action

Prosecution Timeline

Show 5 earlier events
Nov 13, 2025
Final Rejection mailed — §101, §112
Jan 12, 2026
Examiner Interview Summary
Jan 12, 2026
Applicant Interview (Telephonic)
Feb 05, 2026
Request for Continued Examination
Feb 26, 2026
Response after Non-Final Action
Apr 16, 2026
Non-Final Rejection mailed — §101, §112
Jul 16, 2026
Response Filed
Nov 09, 2026
Final Rejection mailed — §101, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12718265
PUSHING CONTENT TO SECONDARY CONNECTED DEVICES
2y 4m to grant Granted Aug 25, 2026
Patent 12694746
ELECTRICAL COMPUTERS AND DIGITAL PROCESSING SYSTEMS INVOLVING INTERPROGRAM OR INTERPROCESS COMMUNICATION REGARDING AMUSEMENT DEVICES AND GAMES
3y 1m to grant Granted Jul 28, 2026
Patent 12657602
ADVERTISING DEVICE MONITORING METHOD AND DEVICE
3y 11m to grant Granted Jun 16, 2026
Patent 12602708
SYSTEM AND METHOD FOR CAPABILITY PACKAGES OFFERING BASED ON ANALYSIS OF EDITED WEBSITES AND THEIR USE
3y 5m to grant Granted Apr 14, 2026
Patent 12586097
SYSTEM AND METHOD FOR PROVIDING VIRTUAL ITEMS TO USERS OF A VIRTUAL SPACE
2y 3m to grant Granted Mar 24, 2026
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

5-6
Expected OA Rounds
33%
Grant Probability
67%
With Interview (+33.5%)
4y 7m (~1y 7m remaining)
Median Time to Grant
High
PTA Risk
Based on 581 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