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 . Claims 1-18 are pending.
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-18 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception without significantly more.
Step 1 (The Statutory Categories): Is the claim to a process, machine, manufacture, or composition of matter? MPEP 2106.03.
Per Step 1, claim 1 is to a system (i.e., a machine), claim 10 to a method (i.e., a process). Thus, the claims are directed to statutory categories of invention. However, the claims are rejected under 35 U.S.C. 101 because they are directed to an abstract idea, a judicial exception, without reciting additional elements that integrate the judicial exception into a practical application.
The analysis proceeds to Step 2A Prong One.
Step 2A Prong One: Does the claim recite an abstract idea, law of nature, or natural phenomenon? MPEP 2106.04.
The abstract idea of claim 1 is:
capture user ratings and comments following a communication between at least the first user and the end user within the active chat session;
validate and process feedback collected from the end user, perform natural language processing to assess sentiment of the captured feedback and to flag inappropriate content;
create a sharable link, wherein the sharable link comprises a unique URL directing to an HTML page that embeds the validated feedback;
generate a public access link with branded feedback representation and structured metadata, wherein the structured metadata comprises at least a title, a description, and an image link prepared to enhance display of the feedback across social platforms;
enable sharing of the generated feedback;
provide authorized personnel access to review and manage stored feedback.
The abstract idea of claim 10 is:
capturing user ratings and comments through a chat assessment form, the chat assessment form being captured following the communication between at least the first user and the end user;
validating the captured feedback collected via the chat assessment form, wherein the validating comprises performing natural language processing to assess sentiment of the captured feedback and to flag inappropriate content;
storing the validated feedback and the active chat session;
enabling authorized personnel to review and manage stored feedback;
displaying assessment details, and creating a sharable link to the first user via a sharable link module, wherein the sharable link comprises a unique URL directing to an HTML page that embeds the validated feedback;
generating a public access link with branded feedback representation and structured metadata , wherein the structured metadata comprises at least a title, a description, and an image link prepared to enhance display of the feedback across social platforms;
sharing of the feedback;
provide authorized personnel access to review and manage stored feedback.
The abstract idea steps italicized above describe the rules or instructions that pertain to managing customer feedback, which constitutes a process that, under its broadest reasonable interpretation, covers managing personal behavior relationships, interactions between people. This is further supported by [0001]-[0005] of applicant’s specification as filed. If a claim limitation, under its broadest reasonable interpretation, covers managing personal behavior relationships, interactions between people, including social activities, teaching, and/or following rules or instructions, then it falls within the Certain Methods of Organizing Human Activity – Managing Personal Behavior Relationships, Interactions Between People grouping of abstract ideas. Accordingly, the claim recites an abstract idea.
Step 2A Prong Two: Does the claim recite additional elements that integrate the judicial exception into a practical application? MPEP 2106.04.
This judicial exception is not integrated into a practical application because the additional elements are merely instructions to apply the abstract idea to a computer, as described in MPEP 2106.05(f).
Claim 1 recites the following additional elements: a server; at least one processor; a non-transitory computer-readable storage medium storing instructions that, when executed by the at least one processor, cause the system to implement; a user interaction module implemented by the at least one processor and configured to facilitate real-time communication between at least a first user and an end user within an active chat session; a chat assessment form generated by the at least one processor and embedded within a live chat application; a feedback validation and processing unit comprising instructions executable by the at least one processor; wherein the feedback validation and processing unit is further configured to; a live chat handler implemented by the at least one processor and configured to communicate with a database storage system to store active chat session history; the database storage system comprising a non-transitory computer-readable storage medium configured to store validated feedback and active chat session history; an assessment manager implemented by the at least one processor, the assessment manager comprising a display module for assessment details and further comprising a sharable link module comprising instructions executable by the at least one processor; an HTML rendering engine implemented by the at least one processor; wherein the HTML rendering engine is further configured to pre-generate rendered versions of the feedback for instant display so as to reduce server load during subsequent requests; an external sharing module implemented by the at least one processor, the external sharing module being configured on the assessment manager; across external digital platforms; wherein the assessment manager is configured to; wherein the external sharing module is configured to communicate with a browser; wherein the external sharing module is configured to communicate with the HTML rendering engine to render a website with the use of HTML.
Claim 10 recites the following additional elements: within a digital communication platform; being performed by a server system comprising at least one processor executing instructions stored on a non-transitory computer-readable storage medium; facilitating, by the at least one processor via a user interaction module, real-time communication within an active chat session between at least a first user and an end-user; generated by the at least one processor and embedded within the active chat session; with the use of a feedback validation and processing unit executed by the at least one processor; in a database storage system comprising a non-transitory computer-readable storage medium; using an assessment manager executed by the at least one processor; by the at least one processor; via a display module; using an HTML rendering engine executed by the at least one processor; wherein generating the public access link comprises pre-generating, by the HTML rendering engine, rendered versions of the feedback for instant display so as to reduce server load during subsequent requests; across external platforms via an external sharing module executed by the at least one processor and configured on the assessment manager; wherein the assessment manager is configured to; wherein the external sharing module is configured to communicate with a browser; wherein the external sharing module is configured to communicate with the HTML rendering engine to render a website with the use of HTML.
These elements are merely instructions to apply the abstract idea to a computer, per MPEP 2106.05(f). Applicant has only described generic computing elements in their specification, as seen in [0019]-[0025] of applicant’s specification as filed, for example.
Further, the combination of these elements is nothing more than a generic computing system applied to the tasks of the abstract idea. Because the additional elements are merely instructions to apply the abstract idea to a generic computing system, they do not integrate the abstract idea into a practical application, when viewed in combination. See MPEP 2106.05(f).
Therefore, per Step 2A Prong Two, the additional elements, alone and in combination, do not integrate the judicial exception into a practical application. The claim is directed to an abstract idea.
Step 2B (The Inventive Concept): Does the claim recite additional elements that amount to significantly more than the judicial exception? MPEP 2106.05.
Step 2B involves evaluating the additional elements to determine whether they amount to significantly more than the judicial exception itself.
The examination process involves carrying over identification of the additional element(s) in the claim from Step 2A Prong Two and carrying over conclusions from Step 2A Prong Two pertaining to MPEP 2106.05(f).
The additional elements and their analysis are therefore carried over: applicant has merely recited elements that facilitate the tasks of the abstract idea, as described in MPEP 2106.05(f).
Further, the combination of these elements is nothing more than a generic computing system applied to the tasks of the abstract idea. When the claim elements above are considered, alone and in combination, they do not amount to significantly more.
Therefore, per Step 2B, the additional elements, alone and in combination, are not significantly more. The claims are not patent eligible.
The analysis takes into consideration all dependent claims as well:
Dependent claims 2-9 and 11-18 further narrow the abstract idea with additional steps and/or information and would fall into the same abstract idea grouping above. Some of the dependent claims recite further additional elements, beyond those highlighted above. These include:
Claim 2: wherein the chat assessment form is embedded within a live chat application; the chat assessment form can adapt its prompts based on user responses.
Claim 4: wherein the database storage system is structured to support high concurrency and real-time data synchronization, ensuring minimal latency in feedback access; data storage encryption; a backup mechanism.
Claim 6: a customization feature; wherein the engine can generate a preview of the rendered feedback for review before public sharing; wherein the engine supports multiple formats, including PDF.
Claim 7: enable integration with social media APIs for direct posting of feedback links with formatted previews; wherein the module supports manual sharing options through shareable QR codes or customized link shorteners.
Claim 8: wherein feedback rendered by the HTML rendering engine is accessible on both desktop and mobile devices.
Claim 9: a notification service.
Claim 11: through the chat assessment form interface embedded within a live chat window; wherein the interface provides real-time suggestions.
Claim 13: periodic data archiving.
Claim 14: exporting feedback data for use in third-party reporting tools.
Claim 15: generating a public access link configured to embedding metadata tags that optimize search engine visibility and social media display; generating versions optimized for different devices by the HTML rendering engine; wherein the engine is configured to perform a customization step where users can adjust visual elements before finalizing the feedback presentation.
Claim 16: sharing the feedback through the external sharing module configured to format the content to match the standards of a target platform; scheduling processing by the sharing module to automate the timing of feedback posts.
Claim 17: wherein the feedback rendered by the HTML rendering engine is responsive and adapts to the screen size and resolution of the viewing device.
Similar to above, these further additional elements are generic computing elements and processes that are claimed in a results-oriented manner and being used in their ordinary capacity to facilitate the tasks of the narrowed abstract idea. This is equivalent to “apply it,” per MPEP 2106.05(f). Whether viewed alone or in combination, this does not integrate the abstract idea into practical application or add significantly more.
Accordingly, claims 1-18 are rejected under 35 USC § 101 as being directed to non-statutory subject matter.
Response to Arguments
Applicant’s arguments filed 8/10/26 have been carefully considered. Examiner’s response follows.
Claim Interpretation under 35 U.S.C. § 112(f)
In view of applicant’s amendments and remarks, examiner has withdrawn the interpretation under 35 U.S.C. § 112(f). The claims are given their broadest reasonable interpretation in light of the specification.
Claim Rejection – 35 USC § 101
Regarding the rejection under 35 USC § 101 and Step 2A Prong One, applicant offers:
The Examiner categorizes the claims as falling within the "certain methods of organizing human activity - managing personal behavior relationships, interactions between people" grouping, citing the steps of capturing user ratings and comments, validating feedback, storing chat history, creating a sharable link, generating a public access link, enabling sharing, and providing authorized personnel with access to stored feedback. Applicant respectfully submits that this characterization mischaracterizes the claims.
The "managing personal behavior relationships" grouping, as set forth in the 2019 Revised Patent Subject Matter Eligibility Guidance and MPEP §2106.04(a)(2)(II)(C), is directed to social activities, teaching, and following rules or instructions among persons. The example fact patterns in this category include performance of contractual obligations, advertising and marketing activities, and rules-based human conduct (e.g., voting, arbitration, dispute resolution). The recited steps of the present claims, by contrast, are not concerned with managing the conduct of persons toward one another. The claimed system does not regulate, instruct, or direct human behavior. Rather, the claims are directed to the automated, technical processing of user-generated digital data, namely, the validation, structured storage, rendering, and machine-readable propagation of feedback artifacts across distributed digital platforms by means of a specific server architecture.
Properly viewed, the claims are directed to a technical mechanism for managing and distributing digital content across heterogeneous web platforms, with each step rooted in computer-implemented data manipulation. The natural-language processing of feedback content for sentiment assessment and inappropriate-content flagging (claim 1); the generation of structured metadata comprising at least a title, a description, and an image link to enhance display across social platforms (claim 1); the pre-generation of rendered HTML versions of the feedback for instant display so as to reduce server load (claim 1); and the rendering, by an HTML rendering engine, of a branded feedback representation accessible via a unique URL embedded in an HTML page (claim 1), none of these can plausibly be characterized as "managing personal behavior relationships." These steps cannot be performed mentally or by a person acting alone in any pen-and-paper analog of human social activity. They are inherently computer-implemented, platform-specific, and concerned with the technical interoperability of distributed digital systems.
To the extent that the Office Action relies on the recitation of "capture user ratings and comments" as evidence of human activity, Applicant notes that the capture step in the claims is performed by a chat assessment form generated by the at least one processor and embedded within the active chat session, that is, by a computer-implemented user interface element, not by human-to-human dialogue. The mere fact that the resulting data ultimately represents end- user input no more renders the claims directed to managing human behavior than would a claim to a packet-level network protocol be characterized as managing the conduct of the persons whose messages it carries.
Accordingly, Applicant respectfully submits that the claims do not recite an abstract idea within the asserted grouping. The analysis should end at Step 2A Prong One, and the rejection should be withdrawn on that basis alone. Should the Examiner nonetheless maintain that the claims recite an abstract idea, Applicant respectfully traverses for the further reasons set forth below.
While well taken, examiner remains unpersuaded. Applicant appears to conflate the abstract idea with the additional elements, as seen in applicant’s remarks (e.g., ‘The natural-language processing of feedback content for sentiment assessment and inappropriate-content flagging (claim 1); the generation of structured metadata comprising at least a title, a description, and an image link to enhance display across social platforms (claim 1); the pre-generation of rendered HTML versions of the feedback for instant display so as to reduce server load (claim 1); and the rendering, by an HTML rendering engine, of a branded feedback representation accessible via a unique URL embedded in an HTML page (claim 1), none of these can plausibly be characterized as “managing personal behavior relationships… They are inherently computer-implemented, platform-specific, and concerned with the technical interoperability of distributed digital systems.’).
Here, examiner identified an abstract idea that includes (claim 1 being representative):
capture user ratings and comments following a communication between at least the first user and the end user within the active chat session;
validate and process feedback collected from the end user, perform natural language processing to assess sentiment of the captured feedback and to flag inappropriate content;
create a sharable link, wherein the sharable link comprises a unique URL directing to an HTML page that embeds the validated feedback;
generate a public access link with branded feedback representation and structured metadata, wherein the structured metadata comprises at least a title, a description, and an image link prepared to enhance display of the feedback across social platforms;
enable sharing of the generated feedback;
provide authorized personnel access to review and manage stored feedback.
These steps are not necessarily technical and could be accomplished via an interpersonal interaction or an interaction between an individual and a computer. (Creating, sharing, and generating links is something that can also be performed manually.)
The additional elements of the claim (e.g., a server; at least one processor; a non-transitory computer-readable storage medium storing instructions that, when executed by the at least one processor, cause the system to implement; a user interaction module; etc.), at least based on applicant’s specification, are generic computing elements used in their ordinary capacity to facilitate the tasks of the abstract idea. Per MPEP 2106.05(f), this does not integrate the abstract idea into practical application. The same interpretation holds regardless of whether the additional elements are viewed alone or in combination, given that the ordered combination is itself a generic computing system.
Applicant continues:
Even assuming that the claims recite an abstract idea, the claims as amended plainly integrate any such idea into a practical application. Under MPEP §2106.04(d) and §2106.05(a), additional claim elements that reflect an improvement in the functioning of a computer or an improvement to another technology or technical field render the claims patent-eligible. The amended claims clearly demonstrate such improvements.
First, and most prominently, the recited HTML rendering engine is configured to pre-generate rendered versions of the feedback for instant display so as to reduce server load during subsequent requests. This is not generic computing activity, it is a specific computer-architectural feature directed to mitigating a known technical problem in high-traffic web- content distribution, namely server contention and latency during repeated rendering of the same content for multiple requesting devices. Support for this feature is found verbatim at paragraph [0025] of the specification, which describes that, to optimize performance during large events, the assessment preview renderer pre-generates rendered versions of the feedback for instant display, thereby reducing server load during subsequent requests. This is precisely the type of computer-functional improvement that the Federal Circuit has recognized as patent- eligible. See, e.g., Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1336 (Fed. Cir. 2016). The pre-generation step of the present claims is a concrete computer-capability improvement that goes well beyond invoking a computer merely as a tool to carry out an otherwise abstract process.
Second, the recited structured metadata, comprising at least a title, a description, and an image link prepared to enhance display of the feedback across social platforms, is directed to a specific technical solution that enables interoperability of the rendered feedback artifact with heterogeneous third-party platforms. As described at paragraph [0020] of the specification, this structured metadata ensures that the feedback, when re-rendered by external platforms, appears with a consistent, branded, and machine-parseable presentation. This is not a generic data- display step; it is a concrete technical mechanism that addresses the cross-platform interoperability problem inherent in modern distributed web content.
Third, the recited natural language processing applied to assess sentiment of captured feedback and to flag inappropriate content represents a specific computer-implemented function that operates on captured digital input. This is not a step that can be performed in the human mind, in pen-and-paper form, or by way of analog social management; it is an automated text- processing operation performed by the at least one processor on data already captured by computer-generated UT elements.
Fourth, the recited unique URL directing to an HTML page that embeds the validated feedback (as further coupled to the assessment manager and the HTML rendering engine) constitutes a specific computer-architectural construct, not a mere abstract pointer. The URL is generated as a runtime artifact of the feedback-rendering process and serves as a persistent, machine-resolvable address for the rendered HTML representation of the feedback. The composition of such a URL, and its persistence in association with the rendered HTML page, is a non-trivial technical operation with no analog in the asserted grouping of organizing human activity.
These features, individually and in combination, supply a particular machine and a particular technological environment in which the claimed feedback processing occurs. They are not generic instructions to "apply" an abstract idea using a generic computer; they are constraints that materially alter how feedback is processed, stored, rendered, and propagated, and they are tightly coupled to the recited server, processor, and non-transitory computer-readable storage medium of the amended claims. Accordingly, even if any abstract idea were present, the additional elements integrate it into a practical application, and the rejection should be withdrawn under Step 2A Prong Two.
At Step 2A Prong Two, the question being asked is “does the claim recite additional elements that integrate the judicial exception into a practical application?”
Examiner’s position is that the additional elements do not integrate the abstract idea into practical application. Instead, applicant has applied generic computing technology to the tasks of the abstract idea, in an effort to automate a previously manual process. This is explicitly described in applicant’s specification, as seen in [0004]:
Given these limitations, there is a clear need for an improved system and method that automates the end-to-end process of capturing, validating, storing, and sharing user feedback which is provided by the claimed invention disclosed therein. Claimed subject matter provides real-time integration capabilities, ensures feedback authenticity, and facilitates the effortless distribution of content in a visually appealing and structured format. This would enable organizations to manage user feedback more efficiently, reduce the manual workload, and maximize the impact of positive user experiences by sharing them seamlessly across digital channels.
MPEP 2106.05(a), is clear, however, that facilitating automation via additional elements doesn’t necessarily equate to an improvement to technology:
In computer-related technologies, the examiner should determine whether the claim purports to improve computer capabilities or, instead, invokes computers merely as a tool. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1336, 118 USPQ2d 1684, 1689 (Fed. Cir. 2016). In Enfish, the court evaluated the patent eligibility of claims related to a self-referential database. Id. The court concluded the claims were not directed to an abstract idea, but rather an improvement to computer functionality. Id. It was the specification’s discussion of the prior art and how the invention improved the way the computer stores and retrieves data in memory in combination with the specific data structure recited in the claims that demonstrated eligibility. 822 F.3d at 1339, 118 USPQ2d at 1691. The claim was not simply the addition of general purpose computers added post-hoc to an abstract idea, but a specific implementation of a solution to a problem in the software arts. 822 F.3d at 1339, 118 USPQ2d at 1691. […]
Examples that the courts have indicated may not be sufficient to show an improvement in computer-functionality:
Generating restaurant menus with functionally claimed features, Ameranth, 842 F.3d at 1245, 120 USPQ2d at 1857;
Accelerating a process of analyzing audit log data when the increased speed comes solely from the capabilities of a general-purpose computer, FairWarning IP, LLC v. Iatric Sys., 839 F.3d 1089, 1095, 120 USPQ2d 1293, 1296 (Fed. Cir. 2016);
Mere automation of manual processes, such as using a generic computer to process an application for financing a purchase, Credit Acceptance Corp. v. Westlake Services, 859 F.3d 1044, 1055, 123 USPQ2d 1100, 1108-09 (Fed. Cir. 2017) or speeding up a loan-application process by enabling borrowers to avoid physically going to or calling each lender and filling out a loan application, LendingTree, LLC v. Zillow, Inc., 656 Fed. App'x 991, 996-97 (Fed. Cir. 2016) (non-precedential) (Examiner’s highlight)
As seen in the bolded portion above, merely automating a formerly manual process isn’t necessarily sufficient to demonstrate an improvement to technology. Therefore, examiner maintains, in direct contradiction to applicant’s four points above and any cited court decisions, that the additional elements do not “supply a particular machine and a particular technological environment in which the claimed feedback processing occurs.”
Applicant continues:
Even were the analysis to proceed to Step 2B, the claims clearly recite, individually and in combination, significantly more than any alleged abstract idea. The Federal Circuit has held that an inventive concept may be found in the non-conventional and non-generic arrangement of known, conventional pieces. See BASCOM Global Internet Servs., Inc. v. AT&T Mobility LLC, 827 F.3d 1341, 1350 (Fed. Cir. 2016).
The amended claim 1 recites a particular ordered combination of computer-architectural features whose composite operation is not routine, well-understood, or conventional. The chat- triggered capture of user feedback via an embedded chat assessment form is coupled to NLP- based sentiment and inappropriate-content evaluation by the feedback validation and processing unit; the validated feedback is then persistently stored together with the active chat session in a database storage system comprising a non-transitory computer-readable storage medium; the assessment manager exposes that stored feedback for authorized review and originates a sharable link comprising a unique URL directing to an HTML page that embeds the validated feedback; an HTML rendering engine then generates the public access representation, equipped with structured metadata (title, description, and image link) configured for display across social platforms, and pre-generates the rendered versions to mitigate server load during subsequent requests; and an external sharing module communicates with both the rendering engine and a browser to disseminate the rendered artifact across heterogeneous external platforms. This particular ordered combination is not merely the addition of generic computer components to an abstract idea; it is a specific computer architecture that addresses a specific problem in the technical field of automated, cross- platform, real-time feedback management.
Importantly, none of the cited references, alone or in combination, discloses this particular ordered combination. As discussed further in connection with the § 103 rejection below, the cited art teaches isolated fragments of conventional feedback handling, social customer care portals, message aggregation, and survey workflows, but the cited art does not disclose the specific synthesis recited in the present claims. The fact that the asserted prior art combinations consist of four to six separate references that the Examiner has stitched together is itself probative of non-routineness.
Accordingly, even were the claims found to recite an abstract idea and even were the practical- application analysis of Step 2A Prong Two found insufficient, the claims would nonetheless recite an inventive concept that amounts to significantly more than the alleged abstract idea. The rejection under 35 U.S.C. § 101 should therefore be withdrawn.
With respect to dependent claims 2-9 and 11-18, Applicant submits that each of these claims further narrows the subject matter of the independent claim from which it depends with additional technical features (including, for example, scoring-algorithm-based feedback prioritization and administrator alerting (claim 3), high-concurrency database synchronization with encryption and backup (claim 4), customization features and multi-format rendering (claim 6), API-based social media integration with QR-coded sharing (claim 7), responsive cross-device rendering (claims 8 and 17), notification services (claims 9 and 18), and categorical organization with periodic archiving and cross-referencing (claim 13)). Each of these limitations further reinforces the technical character of the claimed invention and provides an additional independent basis for patent-eligibility under §101. Reconsideration and withdrawal of the § 101 rejection as to all of claims 1-18 is respectfully requested.
Examiner notes that the determination made at Step 2B was informed by MPEP 2106.05 (II), which recites:
Although the conclusion of whether a claim is eligible at Step 2B requires that all relevant considerations be evaluated, most of these considerations were already evaluated in Step 2A Prong Two. Thus, in Step 2B, examiners should:
Carry over their identification of the additional element(s) in the claim from Step 2A Prong Two;
Carry over their conclusions from Step 2A Prong Two on the considerations discussed in MPEP §§ 2106.05(a) - (c), (e) (f) and (h);
Re-evaluate any additional element or combination of elements that was considered to be insignificant extra-solution activity per MPEP § 2106.05(g), because if such re-evaluation finds that the element is unconventional or otherwise more than what is well-understood, routine, conventional activity in the field, this finding may indicate that the additional element is no longer considered to be insignificant; and
Evaluate whether any additional element or combination of elements are other than what is well-understood, routine, conventional activity in the field, or simply append well-understood, routine, conventional activities previously known to the industry, specified at a high level of generality, to the judicial exception, per MPEP § 2106.05(d). (Examiner’s highlight)
As seen in the second bullet point above, examiner “carried” over the analysis from Step 2A Prong Two, where it was determined that the additional elements, alone and in combination, are merely being used to facilitate the tasks of the abstract idea, per MPEP 2106.05(f).
Lastly, examiner notes that novelty isn’t equivalent to eligibility. MPEP 2106.04 (I) is informative:
The Supreme Court’s decisions make it clear that judicial exceptions need not be old or long-prevalent, and that even newly discovered or novel judicial exceptions are still exceptions. For example, the mathematical formula in Flook, the laws of nature in Mayo, and the isolated DNA in Myriad were all novel or newly discovered, but nonetheless were considered by the Supreme Court to be judicial exceptions because they were “‘basic tools of scientific and technological work’ that lie beyond the domain of patent protection.” Myriad, 569 U.S. 576, 589, 106 USPQ2d at 1976, 1978 (noting that Myriad discovered the BRCA1 and BRCA1 genes and quoting Mayo, 566 U.S. 71, 101 USPQ2d at 1965); Flook, 437 U.S. at 591-92, 198 USPQ2d at 198 (“the novelty of the mathematical algorithm is not a determining factor at all”).
In other words, while applicant may very well arrive at a novel claim, this doesn’t automatically result in the claim being eligible.
In summary, examiner maintains the rejections under 35 USC § 101.
Claim Rejection – 35 USC § 103
Regarding the prior art rejections, applicant’s claim amendments and clarifying remarks are persuasive. The rejections under 35 USC § 103 are withdrawn.
In particular, Vijayaraghavan is directed to a system for monitoring social media threads triggered from a chat exit survey, in which a real-time text-mining engine identifies positive outcomes and forwards them through an auto-post engine to social media platforms via the standard API. As Vijayaraghavan teaches at [0087], the auto-post engine is a software engine that interfaces with the transcript database and the social media platforms, extracts the key posts and segments from the transcript databases, and posts them into the social media platforms through the standard API. Vijayaraghavan thus addresses the problem of moving identified positive feedback into social media channels, but it does so by direct API-level posting of transcript fragments.
It does not teach, suggest, or contemplate (i) an HTML rendering engine that generates a branded feedback representation embedded within an HTML page accessible via a unique URL; (ii) structured metadata comprising a title, description, and image link configured for display of the feedback across social platforms; or (iii) the pre-generation of rendered HTML versions of feedback for instant display to reduce server load. Vijayaraghavan's auto-post engine deposits text into social platforms; it does not generate a publicly accessible, branded, structured- metadata-equipped feedback artifact addressable by a unique URL, as the claimed invention does.
Gaedcke, the second primary reference, does not teach, and does not suggest, integration with a chat-assessment-form-driven workflow in which post-chat feedback is captured by an embedded form, validated by a feedback validation and processing unit using natural language processing for sentiment assessment and inappropriate-content flagging, and then rendered and disseminated with structured metadata configured for display across social platforms. The sharable link in Gaedcke is intended as a callback to a customer-service response page within a particular support exchange; it is not the artifact-distribution sharable URL of the present claims, which directs to an HTML page that embeds the validated feedback for cross-platform syndication.
Bowden, the third primary reference, is directed to a feedback module that asks the user whether they wish to rate the system, and, upon receiving an unfavorable rating, presents a free-form text field, with the submitted data being posted to an Admin Contacts Controller and notification being sent to admin users by email (Bowden [0060]). Bowden's feedback module performs rudimentary input collection and email- based admin notification; it does not perform natural language processing to assess sentiment, and it does not flag inappropriate content. Bowden's structured metadata refers to message-organization fields used internally for message display ordering; it does not refer to a title, description, and image link configured for display of feedback across social platforms, as recited in the present claims.
Additional references considered by examiner include:
US 20120072358, which teaches customer care replies on social media: [0059] Social network services take many forms, each allowing users to create social media postings. One form is a profile based social network service. In a profile based social network service, users create a profile as representations of themselves. The profiles often include photographs, likes and dislikes, and other user generated content. Many profiles also include a contact list used to connect to other users' profiles and access the other users' content. Profile based social network services focus on the relationships among people, which includes groups of people who share interests or are friends for any reason. Most profile based social network services are accessed via the Internet using a URL. The profile based social network establishes connections among users. Examples of profile based social networks include Facebook, MySpace, LinkedIn, and Bebo. Most profile based social networks include an area for comment by the user and by other users. In addition, many profile based social networks include a status message feature, which is an example of a microblog.
US 20130014258, which teaches sharing social media posts: [0022] The user computing device 110 can be, for example, a personal computer, a laptop computer, a tablet computer, a smart phone, a mobile computing device, an Internet appliance, or the like. A user can employ the computing device 110 to interact with social media services and other resources available on the network 199. In one embodiment, the user logs on to Twitter to post content to be read by their followers, and to review content postings made by other Twitter users. In another embodiment, a post made by the user include a command intended to instruct a remote network-based application to perform a corresponding action. One possible action is to automatically publish results on a social media service. Thus, the user computing device 110 can also be used to view the results of application processing initiated by the user, which can be read by their social media followers.
US 20130305218, which teaches HTML rendering: [0204] In certain embodiments, such as where the application development environment includes a representation of the app on a mobile device, device representation 116 may include a representation of the display of the HTML module within the display of the mobile device. As shown in FIG. 22, the HTML module displayed through device representation 116 may updated and display the current HTML page based on the input and selections made by the developer in HTML manager window 680. In certain embodiments, when an end user has downloaded and launched an app containing the HTML module, the HTML module may be responsible for rendering and displaying the HTML content on the end user's mobile device.
US 20130318156, which teaches sharing across a feed: [0003] Social networking platforms such as Facebook, Google+, FourSquare, LinkedIn, and Twitter have become deeply embedded into the social fabric of modern day life. These platforms support a variety of functions, ranging from sharing daily activities and photos to use as corporate advertising and marketing channels. Many individuals use these sites as sources of news and information about topics of interest such as current events, travel, sports, food, geographic areas, local news, etc. Moreover, companies use these channels to advertise promotions, sales, new products and services, as well as general information. In many instances the messaging and news feeds supplied by these platforms have become the de facto method of communication among and for large groups of individuals. This collection of data sent to and viewed by an individual is typically referred to as a "feed." Recently, sites such as Klout, HootSuite, and Sprout Social have begun aggregating data fees from the individual social network platforms onto a single platform. This process provides a "global" view of content and its creators and illustrates how it proliferates across the web. Moreover, it allows multiple users who otherwise might not be connected to view and possibly comment on content submitted by others.
These references, while generally describing sharing feedback and/or HTML rendering, stop well short of the specificity of the claims. Accordingly, the previous rejections under 35 USC § 103 are withdrawn.
In summary, examiner has responded to all of applicant’s remarks.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
US 20120072358, which teaches customer care replies on social media: [0059] Social network services take many forms, each allowing users to create social media postings. One form is a profile based social network service. In a profile based social network service, users create a profile as representations of themselves. The profiles often include photographs, likes and dislikes, and other user generated content. Many profiles also include a contact list used to connect to other users' profiles and access the other users' content. Profile based social network services focus on the relationships among people, which includes groups of people who share interests or are friends for any reason. Most profile based social network services are accessed via the Internet using a URL. The profile based social network establishes connections among users. Examples of profile based social networks include Facebook, MySpace, LinkedIn, and Bebo. Most profile based social networks include an area for comment by the user and by other users. In addition, many profile based social networks include a status message feature, which is an example of a microblog.
US 20130014258, which teaches sharing social media posts: [0022] The user computing device 110 can be, for example, a personal computer, a laptop computer, a tablet computer, a smart phone, a mobile computing device, an Internet appliance, or the like. A user can employ the computing device 110 to interact with social media services and other resources available on the network 199. In one embodiment, the user logs on to Twitter to post content to be read by their followers, and to review content postings made by other Twitter users. In another embodiment, a post made by the user include a command intended to instruct a remote network-based application to perform a corresponding action. One possible action is to automatically publish results on a social media service. Thus, the user computing device 110 can also be used to view the results of application processing initiated by the user, which can be read by their social media followers.
US 20130305218, which teaches HTML rendering: [0204] In certain embodiments, such as where the application development environment includes a representation of the app on a mobile device, device representation 116 may include a representation of the display of the HTML module within the display of the mobile device. As shown in FIG. 22, the HTML module displayed through device representation 116 may updated and display the current HTML page based on the input and selections made by the developer in HTML manager window 680. In certain embodiments, when an end user has downloaded and launched an app containing the HTML module, the HTML module may be responsible for rendering and displaying the HTML content on the end user's mobile device.
US 20130318156, which teaches sharing across a feed: [0003] Social networking platforms such as Facebook, Google+, FourSquare, LinkedIn, and Twitter have become deeply embedded into the social fabric of modern day life. These platforms support a variety of functions, ranging from sharing daily activities and photos to use as corporate advertising and marketing channels. Many individuals use these sites as sources of news and information about topics of interest such as current events, travel, sports, food, geographic areas, local news, etc. Moreover, companies use these channels to advertise promotions, sales, new products and services, as well as general information. In many instances the messaging and news feeds supplied by these platforms have become the de facto method of communication among and for large groups of individuals. This collection of data sent to and viewed by an individual is typically referred to as a "feed." Recently, sites such as Klout, HootSuite, and Sprout Social have begun aggregating data fees from the individual social network platforms onto a single platform. This process provides a "global" view of content and its creators and illustrates how it proliferates across the web. Moreover, it allows multiple users who otherwise might not be connected to view and possibly comment on content submitted by others.
THIS ACTION IS MADE FINAL. 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 SAMUEL WASAFF whose telephone number is (571)270-5091. The examiner can normally be reached Monday through Friday 8:00 am to 6:00 pm.
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, SARAH MONFELDT can be reached at (571) 270-1833. 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 SAMUEL WASAFF
Primary Examiner
Art Unit 3629
/JOHN S. WASAFF/Primary Examiner, Art Unit 3629