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
Preliminary Amendment filed 03/07/2025 has been entered. The Specification contains no new matter. Claims 1-14 are cancelled; claims 15-32 are new. Claims 15-32 are pending.
Information Disclosure Statement
The information disclosure statements (IDS) submitted on 03/07/2025 and 07/22/2026 were in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statements are being considered by the Examiner.
Claim Objections
Claims 15, 21, 25, and 31 are objected to because of the following informalities:
Claim 15 recites “a second business scenario” in line 4, where claim 15 previously recites “a second business scenario” in line 3. Examiner suggests the amendment “a second business scenario…[[a]] the second business scenario” for clarity.
Claim 25 recites “a second business scenario” in line 6, where claim 25 previously recites “a second business scenario” in line 5. Examiner suggests the amendment “a second business scenario…[[a]] the second business scenario” for clarity.
Claim 15 recites “at least part of content” in line 4, which lacks an article.
Claim 21 recites “at least part of content” in line 11, which lacks an article.
Claim 25 recites “at least part of content” in line 6, which lacks an article.
Claim 31 recites “at least part of content” in line 11, which lacks an article.
Appropriate correction is required.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 15-32 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 15 recites the limitation "a second business scenario" in line 3. There is insufficient antecedent basis for this limitation in the claim, as the claims do not previously recite “a first business scenario”, which would be required in order to recite “a second business scenario”. The use of an ordinal numeral without its preceding ordinal numerals would simultaneously 1) require a distinctly ordered item of a set (i.e., “a second business scenario”), and 2) leave such a set undefined, and therefore the scope of the claims would be indefinite. Claims 23 and 25 similarly recited “a second business scenario” and are rejected under the same rationale. Claims 16-22, 24, and 26-32 are rejected as depending from claims 15, 23, and 25, respectively, and under the same rationale.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 15, 16, 19-23, 25, 26, and 29-32 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Cohen (U.S. Pat. App. Pub. 2025/0080480).
Regarding claim 15, Cohen disclosed a method for information processing, comprising: obtaining a first link corresponding to at least one message in a first session (inserting/generating, i.e., obtaining, reference object/digital connection link, i.e., first link, referencing a first message, i.e., at least one message, ¶[0050], [0055], [0070], [0077]; message received in a chat session, i.e., first session, ¶[0061]); in response to an operation of sending the first link to a second business scenario (transmitting, i.e., sending, second message with reference object, i.e., first link, ¶[0055], [0072], [0080]; receiving second message at a client device, i.e., second business scenario, ¶[0061]), displaying first content in a second business scenario (displaying second message on client device, ¶[0081]), wherein the first content comprises at least part of content of the at least one message (displaying part of the first message, ¶[0053], [0072], [0082]); and updating the first content in the second business scenario accordingly based on change information of the at least one message (updating displayed first message, i.e., first content, to match edited first message, i.e., change information, ¶[0058], [0138]).
Regarding claim 16, Cohen disclosed the method wherein the change information of the at least one message comprises information representing one or more of the following events: in the first session, an expression reply is received for a message of the at least one message (claimed in the alternative); in the first session, a topic message reply is received for a message of the at least one message receives (claimed in the alternative); in the first session, an editing operation is performed on a message of the at least one message (editing a first message, ¶[0056], [0137], [0138]); in the first session, a message of the at least one message is withdrawn (claimed in the alternative); or in the first session, a state of a message of the at least one message is changed (editing a first message, ¶[0056], [0137], [0138]).
Regarding claim 19, Cohen disclosed the method wherein the second business scenario comprises one or more of the following: a second session being a further session other than the first session (claimed in the alternative); a document (claimed in the alternative); a schedule (schedule, ¶[0249]); an audio-video conference (claimed in the alternative); a task (claimed in the alternative); an e-mail (email interface, ¶[0176]); a project management system (claimed in the alternative); or a customer relationship management system (claimed in the alternative).
Regarding claim 20, Cohen disclosed the method wherein after updating the first content in the second business scenario, the method further comprises: labeling a first message of the at least one message with a first predetermined identification in the second business scenario, or labeling a changed message of the at least one message with a second predetermined identification in the second business scenario (adding a tag/flag/metadata, i.e., label, to database record associated with first message, ¶[0073]).
Regarding claim 21, Cohen disclosed the method wherein updating the first content in the second business scenario accordingly comprising: updating the first content in the second business scenario accordingly based on a trigger of a member in the second business scenario on the first content, wherein the trigger comprises at least one of the following: an open operation on the second business scenario (displaying updated/edited messages when user, i.e., member, scrolls back/places into focus, i.e., opens, edited messages, ¶[0353]); a refresh operation on the second business scenario (claimed in the alternative); a click operation on the first link in the first content (claimed in the alternative); a click operation on a text link in the first content, the text link corresponding to the first link (claimed in the alternative); or a click operation on a message card in the first content, at least part of content of the at least one message being presented in the message card (claimed in the alternative).
Regarding claim 22, Cohen disclosed the method wherein the method further comprises at least one of the following: setting a message type in the first session based on a first configuration operation of a first type user in the first session, to enable change information satisfying the message type to be used to update the first content in the second business scenario (storing, i.e., setting, “D”/”Default” type of a message, ¶[0140]); setting a message change type in the first session based on a second configuration operation of the first type user in the first session, to enable the change information satisfying the message change type to be used to update the first content in the second business scenario (associating, i.e., setting, “Edited” message type, i.e., message change type, ¶[0137]); or based on a third configuration operation of the first type user in the first session, allowing change information of a user in the first session to be used to update the first content in the second business scenario (updating displayed first message, i.e., first content, to match edited first message, i.e., change information, ¶[0058], [0138]).
Regarding claim 23, Cohen disclosed a method for information processing, comprising: obtaining a first link corresponding to at least one message in a first session (inserting/generating, i.e., obtaining, reference object/digital connection link, i.e., first link, referencing a first message, i.e., at least one message, ¶[0050], [0055], [0070], [0077]; message received in a chat session, i.e., first session, ¶[0061]); in response to an operation of sending the first link to a second business scenario (transmitting, i.e., sending, second message with reference object, i.e., first link, ¶[0055], [0072], [0080]; receiving second message at a client device, i.e., second business scenario, ¶[0061]), displaying a first content in the second business scenario (displaying second message on client device, ¶[0081]); wherein a content presented in the first content comprises the at least one message (displaying the first message, ¶[0053], [0072], [0082]); and wherein the content presented in the first content further comprises: an expression replied to the at least one message; and/or
in response to the at least one message comprising a topic message, a reply message to the topic message presented in the first content (first message including reply, i.e., reply message, ¶[0176]).
Regarding claim 25, An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor (processing device, memory, instructions, ¶[0395]-[0396]), the program, when executed by the processor, performing acts comprising: obtaining a first link corresponding to at least one message in a first session (inserting/generating, i.e., obtaining, reference object/digital connection link, i.e., first link, referencing a first message, i.e., at least one message, ¶[0050], [0055], [0070], [0077]; message received in a chat session, i.e., first session, ¶[0061]);
in response to an operation of sending the first link to a second business scenario (transmitting, i.e., sending, second message with reference object, i.e., first link, ¶[0055], [0072], [0080]; receiving second message at a client device, i.e., second business scenario, ¶[0061]), displaying first content in a second business scenario (displaying second message on client device, ¶[0081]), wherein the first content comprises at least part of content of the at least one message (displaying part of the first message, ¶[0053], [0072], [0082]); and updating the first content in the second business scenario accordingly based on change information of the at least one message (updating displayed first message, i.e., first content, to match edited first message, i.e., change information, ¶[0058], [0138]).
Regarding claim 26, Cohen disclosed the electronic device wherein the change information of the at least one message comprises information representing one or more of the following events: in the first session, an expression reply is received for a message of the at least one message (claimed in the alternative); in the first session, a topic message reply is received for a message of the at least one message receives (claimed in the alternative); in the first session, an editing operation is performed on a message of the at least one message (editing a first message, ¶[0056], [0137], [0138]); in the first session, a message of the at least one message is withdrawn (claimed in the alternative); or in the first session, a state of a message of the at least one message is changed (editing a first message, ¶[0056], [0137], [0138]).
Regarding claim 29, Cohen disclosed the electronic device wherein the second business scenario comprises one or more of the following: a second session being a further session other than the first session (claimed in the alternative); a document (claimed in the alternative); a schedule (schedule, ¶[0249]); an audio-video conference (claimed in the alternative); a task (claimed in the alternative); an e-mail (email interface, ¶[0176]); a project management system (claimed in the alternative); or a customer relationship management system (claimed in the alternative).
Regarding claim 30, Cohen disclosed the electronic device wherein after updating the first content in the second business scenario, the acts further comprise: labeling a first message of the at least one message with a first predetermined identification in the second business scenario, or labeling a changed message of the at least one message with a second predetermined identification in the second business scenario (adding a tag/flag/metadata, i.e., label, to database record associated with first message, ¶[0073]).
Regarding claim 31, Cohen disclosed the electronic device wherein updating the first content in the second business scenario accordingly comprising: updating the first content in the second business scenario accordingly based on a trigger of a member in the second business scenario on the first content, wherein the trigger comprises at least one of the following: an open operation on the second business scenario (displaying updated/edited messages when user, i.e., member, scrolls back/places into focus, i.e., opens, edited messages, ¶[0353]); a refresh operation on the second business scenario (claimed in the alternative); a click operation on the first link in the first content (claimed in the alternative); a click operation on a text link in the first content, the text link corresponding to the first link (claimed in the alternative); or a click operation on a message card in the first content, at least part of content of the at least one message being presented in the message card (claimed in the alternative).
Regarding claim 32, Cohen disclosed the electronic device wherein the acts further comprise at least one of the following: setting a message type in the first session based on a first configuration operation of a first type user in the first session, to enable change information satisfying the message type to be used to update the first content in the second business scenario (storing, i.e., setting, “D”/”Default” type of a message, ¶[0140]); setting a message change type in the first session based on a second configuration operation of the first type user in the first session, to enable the change information satisfying the message change type to be used to update the first content in the second business scenario (associating, i.e., setting, “Edited” message type, i.e., message change type, ¶[0137]); or based on a third configuration operation of the first type user in the first session, allowing change information of a user in the first session to be used to update the first content in the second business scenario (updating displayed first message, i.e., first content, to match edited first message, i.e., change information, ¶[0058], [0138]).
Allowable Subject Matter
Claims 17, 18, 24, 27, and 28 would be allowable if rewritten to overcome the rejection(s) under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), 2nd paragraph, set forth in this Office action and to include all of the limitations of the base claim and any intervening claims.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOSEPH R MANIWANG whose telephone number is (571)270-7257. The examiner can normally be reached 8:30AM - 4:30PM.
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, Wing F Chan can be reached at (571) 272-7493. 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.
/JOSEPH R MANIWANG/Primary Examiner, Art Unit 2453
Prosecution Insights