Response to an amendment
This office action is a response to a communication made on 06/23/2026.
Claims 2-3, 11-12 and 24 are canceled.
Claims 25 is new.
Claims 1, 4-6, 9-10, 13-17 and 21 are currently amended.
Claims 1, 4-10, 13-23 and 25 are pending for this application.
Response to Arguments
Applicant’s arguments with respect to claim(s) 1, 10 and 15 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Applicant’s arguments, see remarks on page 10-11, filed 06/23/2026, with respect to the rejection(s) of claim(s) 1, 10 and 15 under 102(a)(1) have been considered and regarding the amended feature of “joining a live collaborative session, the live collaborative session enabling a subset of the one or more client devices using the application to simultaneously and collaboratively edit a document” are persuasive. Therefore, the rejection has been withdrawn. However, upon further consideration, a new ground(s) of rejection is made in view of Rose et al. (US 2020/0279070 A1) in view of Lo et al. (US 9,667,676 A1).
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.
Claim 17 is 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 17 recites the limitation "a URL" in line 1. There is insufficient antecedent basis for this limitation in the claim.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim(s) 1, 4-10 and 13-24 is/are rejected under 35 U.S.C. 103 as being unpatentable over Rose et al. (US 2020/0279070 A1), hereinafter “Rose” in view of Lo et al. (US 9,667,676 A1), hereinafter “Lo”. Rose cited in applicant IDS filed 07/18/2025.
With respect to claim 1, Rose discloses a method, comprising:
joining, by a first client device executing a video conference client application, a video conference hosted by a video conference provider, the video conference comprising a plurality of client devices (¶0052, teaches the users referred to herein access a group-based communication or messaging system using client devices, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video, audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text as well as an image and a video within the group-based message as group-based message contents, ¶0061-¶0062, teaches each organization group may have one or more group-based communication channels (explained below) to which users may be assigned or which the users may join… Group-based communication system users may join group-based communication channels);
receiving, from a second client device of the plurality of client devices, a network address corresponding to an application installed on one or more client devices of the plurality of client devices, the application including a collaborative mode (¶0025, ¶0063, ¶0128, ¶0130, ¶0134 and ¶0141, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item… the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page)… the group-based messages are uniformly presented to each of the users viewing the group-based messages in the selected channel. For the purposes described herein, the user inputs a group-based message utilizing input field 305 and input/output circuitry 250. For example, the user (Matt) inputs or enters “Here's the link to the shared document: https://doc.ACME.com/12345” into input field 305… group-based message 304C comprises a resource request in the form of URL (i.e. network address) https://doc.ACME.com/12345. wherein Anna (see Fig. 3A-3C) uses the first client device and Matt uses the second client device… FIG. 3C shows an example of the group-based message in the channel if an APP was previously installed in the interface instance. For example, the ACME Docs APP is already installed in the interface instance on the defined preview server 102, thus defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered as defined preview 312, without needing to install (or reinstall) the APP… resource addresses are associated with a defined preview application (APP));
receiving, from the video conference provider, information about the network address based on the network address (¶0130, ¶0134 and ¶0147, teaches group-based message 304C comprises a resource request in the form of URL (i.e. network address) https://doc.ACME.com/12345... defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered as defined preview 312… receive defined preview data from the resource provider);
generating a rendering of the information about the network address (See Fig. 3C, item 304E, ¶0134-¶0135 and ¶0148 teaches defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered as defined preview 312… Defined preview 312 includes image 314 (e.g., a logo of a document hosting service or another image as defined at the resource provider), description text 316 and 318 (e.g., a title and authors of the document). Defined preview 312 also includes summary text 320, which summarizes or depicts the information in the resource… render the defined preview (e.g. defined preview 312) of the resource based on the defined preview data to the group-based communication interface associated with the group-based message), wherein the rendering includes one or more controls, each control associated with an action to take in response to selecting the control (¶0135 and ¶0149, teaches the defined preview 312 also includes the interactive graphical element 322, which allows for a user to select the element for further user interface functions… the defined preview comprises interactive graphical elements (e.g. interactive graphical element 322), wherein each interactive graphical element comprises a user selectable item), a first control of the one or more controls being configured to join a collaborative session using the application in the collaborative mode with the one or more client devices (¶0054, teaches access may further be facilitated by a validated request to join or an invitation to join (i.e. collaborative session) transmitted by one group member user to another non-member user, ¶0135, ¶0141 and ¶0149, teaches the defined preview 312 also includes the interactive graphical element 322, which allows for a user to select the element (i.e. a first control of the one or more controls) for further user interface functions… resource addresses are associated with a defined preview application (APP)…the defined preview comprises interactive graphical elements (e.g. interactive graphical element 322), wherein each interactive graphical element comprises a user selectable item);
displaying the rendering on a display of the first client device (See Fig. 3C, ¶0148 teaches the defined preview 312 is provided to a client device 110A, such that it may be displayed on a group-based communication interface of the client device 110A by interface module 246);
receiving an indication of a selection of the first control of the one or more controls (¶0135 and ¶0149, teaches a user to select the element for further user interface functions… the defined preview comprises interactive graphical elements (e.g. interactive graphical element 322), wherein each interactive graphical element comprises a user selectable item. For example, a computer bug tracking resource provider may return defined preview data including a button (user selectable item) which, when selected by a user begins a user interaction with the resource provider and handled by the bug tracking resource provider); and
outputting a command to execute the action associated with the first control (¶0135 and ¶0149, teaches selecting element 322 shows more or less summary text 320…the defined preview comprises interactive graphical elements (e.g. interactive graphical element 322), wherein each interactive graphical element comprises a user selectable item), wherein the action includes:
executing, at the first client device, the application corresponding to the network address in the collaborative mode (¶0052, teaches the users referred to herein access a group-based communication or messaging system using client devices, ¶0054, teaches access may further be facilitated by a validated request to join or an invitation to join (i.e. collaborative session) transmitted by one group member user to another non-member user, ¶0141, teaches resource addresses are associated with a defined preview application (APP)).
However, Rose remain silent on joining a live collaborative session, the live collaborative session enabling a subset of the one or more client devices using the application to simultaneously and collaboratively edit a document.
Lo discloses joining a live collaborative session (Col-2, II. 32-37, teaches a data stream, such as a series of real-time images or Video, of the native application window containing the content item on the host device is transmitted to each participant of the collaborative editing session (i.e. live collaborative session) over the peer-to-peer connection to the web browser of each client device), the live collaborative session enabling a subset of the one or more client devices using the application to simultaneously and collaboratively edit a document (Col-6, II. 5-19, teaches a user provides a request to open a content item via a native client application 255 for the content item on client device A. Native application 255 sends a request to launch the content item from a file folder and the content item is displayed 302 on client device A. Subsequently, client device B and client device C send 304 collaboration requests identifying the content item to client device A to initiate a collaborative editing session (i.e. live collaborative session) with client device A as the host device. In this example, client device B and client device C have sent the collaboration request via a web browser from a webpage. Accordingly, client application 200 of client device A receives the collaboration requests and connection module 210 establishes a peer-to-peer connection (P2P) with each web browser of client device B and client device C, Col-8, II. 52-57, teaches changes provided to content item 402 via a screen sharing interface (i.e., screen sharing window 404) are made to the file of content item 402 via communications between screen sharing window 404 simultaneously provided on each of client devices B and C and client application 200 of host device A over the peer to peer connection, Col-9, II. 25-29, teaches real-time content item collaboration is the simultaneous editing or viewing of a content item remotely hosted by a host client device where other devices are able to make edits or other changes to the content item on the host machine via their own client device).
Therefore, it would be obvious to one of ordinary skill in the art before the effective filing date of the invention to modify Rose’s group based communication with joining a live collaborative session, the live collaborative session enabling a subset of the one or more client devices using the application to simultaneously and collaboratively edit a document of Lo, in order to reduce document version inconsistencies and synchronization delays while allowing multiple users to contribute to the document concurrently (Lo).
For claim 10, it is a non-transitory computer readable medium claim corresponding to the method of claim 1. Therefore claim 10 is rejected under the same ground as claim 1.
For claim 15, it is a system claim corresponding to the method of claim 1. Therefore claim 15 is rejected under the same ground as claim 1.
With respect to claim 4, Rose in view of Lo discloses the method of claim 1, wherein:
the network address corresponds to the application (Rose, ¶0141, resource addresses are associated with a defined preview application (APP));
the application is not installed on the first client device (Rose, ¶0131, teaches the resource request (e.g., “https://doc.ACME.com/12345”) is a subscribed resource according to the operations described in FIGS. 4-8 and that a defined preview application (APP) such as the ACME Docs APP is not installed on the interface instance (e.g. the defined preview server 102)); and
the one or more controls include a second control to cause the application to be installed on the first client device (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element ((i.e. second control) comprises a user selectable item, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D).
with respect to claim 5, Rose in view of Lo discloses the method of claim 1, wherein:
the network address corresponds to the application (Rose, ¶0141, resource addresses are associated with a defined preview application (APP));
the application is installed on the first client device (Rose, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D); and
the one or more controls include:
a second control to cause the application to open in the collaborative mode on each client device of the plurality of client devices (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A, ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D, ¶0134, teaches the ACME Docs APP is already installed in the interface instance on the defined preview server 102, thus defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered);
a third second control to cause the application to open execute on only the first client device (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0063 teaches the term "resource request" refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), 12121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A).
with respect to claims 6 and 16, Rose in view of Lo discloses the method of claim 1, wherein:
the network address corresponds to the application (Rose, ¶0141, resource addresses are associated with a defined preview application (APP));
the information about the network address includes second information about the application based on the network address (Rose, ¶0063, teaches a resource request comprises a uniform resource locator (URL) identifying a requested resource and a resource address, ¶0135, teaches defined preview 312 includes image 314 (e.g., a logo of a document hosting service or another image as defined at the resource provider), description text 316 and 318 (e.g., a title and authors of the document), wherein title or description of text are second information).
with respect to claim 7, Rose in view of Lo discloses the method of claim 6, wherein the information about the network address further includes instructions for rendering the information about the network address, including a preview of the application based on the network address (Rose, ¶0077, teaches the defined preview server 102 may determine and transmit commands and instructions for rendering one or more group-based communication channels, including defined previews of resources, to client devices 110A-110N, ¶0130, teaches a metadata preview of the resource is displayed based on metadata and other information collected by the defined preview server 102. For example, a logo (i.e image) of the document service, a title, and a description (i.e. text) of the document are shown in metadata preview 308).
with respect to claim 8, Rose in view of Lo discloses the method of claim 7, wherein the preview of the application is further based on information about the first client device (Rose, ¶0130, teaches a metadata preview of the resource is displayed based on metadata and other information collected by the defined preview server 102. For example, a logo (i.e image) of the document service, a title, and a description (i.e. text) of the document are shown in metadata preview 308).
With respect to claim 9, Rose in view of Lo discloses the method of claim 1, wherein:
the network address corresponds to the application (Rose, ¶0141, resource addresses are associated with a defined preview application (APP)); and
the information about the network address includes default information about the application (Rose, ¶0063, teaches a resource request in the form of a URL “http://logo.ACME.com” is a resource request for the “logo” of “ACME.” The resource address is the address of the URL, ¶0130, teaches group-based message 304C comprises a resource request in the form of URL (i.e. network address) https://doc.ACME.com/12345.).
With respect to claim 13, Rose in view of Lo discloses the non-transitory computer-readable medium of claim 10, wherein:
the network address is a uniform resource locator (URL) corresponding to the application (Rose, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page)… a resource request comprises a uniform resource locator (URL) identifying a requested resource and a resource address, ¶0141, teaches resource addresses are associated with a defined preview application (APP)), a portion of the URL being registered with an operating system of the first client device in response to an installation of the application on the first client device (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element ((i.e. second control) comprises a user selectable item, ¶0065, teaches the subscribed resource addresses (i.e URL)s are stored as a list or registry in a subscription database, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D); and
the one or more controls include:
a second control to cause the application to open in the collaborative mode on each client device of the plurality of client devices (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D, ¶0134, teaches the ACME Docs APP is already installed in the interface instance on the defined preview server 102, thus defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered, ¶0141, resource addresses are associated with a defined preview application (APP) );
a third second control to cause the application to open execute on the first client device (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0063 teaches the term "resource request" refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), 121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A).
with respect to claim 14, Rose in view of Lo discloses the non-transitory computer-readable medium of claim 10, wherein:
the network address corresponds to the application (Rose, ¶0141, resource addresses are associated with a defined preview application (APP));
the application is installed in the video conference client software of the first client device (Rose, ¶0055, one or more group-based communication channel identifiers associated with group-based communication channels (i.e. video conference) that the user has been granted access to, one or more group identifiers for groups with which the user is associated, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D); and
the one or more controls include:
a second control to cause the application to open in the collaborative mode on each client device of the plurality of client devices (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0055, one or more group-based communication channel identifiers associated with group-based communication channels (i.e. video conference) that the user has been granted access to, one or more group identifiers for groups with which the user is associated, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video, audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text (i.e. chat message) as well as an image and a video within the group-based message as group-based message contents, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A, ¶0131, teaches provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D, ¶0134, teaches the ACME Docs APP is already installed in the interface instance on the defined preview server 102, thus defined preview module 208 and communication circuitry 212 sends a defined preview request to the resource provider and the defined preview data is received and rendered); and
a third second control to cause the application to open on the first client device, the opened application included in a video conference interface corresponding to the video conference (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0055, one or more group-based communication channel identifiers associated with group-based communication channels (i.e. video conference) that the user has been granted access to, one or more group identifiers for groups with which the user is associated, ¶0063 teaches the term "resource request" refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A).
with respect to claim 17, Rose in view of Lo discloses the system of claim 16, wherein:
the network address is a URL (Rose, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page)… a resource request comprises a uniform resource locator (URL) identifying a requested resource and a resource address);
the URL includes a portion corresponding to the application (Rose, ¶0141, teaches resource addresses are associated with a defined preview application (APP));
the information about the network address further includes instructions for rendering the information about the network address, including a preview of the application based on the network address (Rose, ¶0077, teaches the defined preview server 102 may determine and transmit commands and instructions for rendering one or more group-based communication channels, including defined previews of resources, to client devices 110A-110N, ¶0130, teaches a metadata preview of the resource is displayed based on metadata and other information collected by the defined preview server 102. For example, a logo (i.e image) of the document service, a title, and a description (i.e. text) of the document are shown in metadata preview 308); and
the preview of the application is further based on information about the first client device (Rose, ¶0130, teaches a metadata preview of the resource is displayed based on metadata and other information collected by the defined preview server 102. For example, a logo (i.e image) of the document service, a title, and a description (i.e. text) of the document are shown in metadata preview 308).
With respect to claim 18, Rose in view of Lo discloses the system of claim 15, wherein the first client device includes a chat interface of the video conference client application and receiving, from the second client device of the plurality of client devices, the network address comprises receiving a chat message including the network address using the chat interface (Rose, ¶0051, teaches the data may be received directly from the another computing device or may be received indirectly via one or more intermediary computing devices, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video, audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text (i.e. chat message) as well as an image and a video within the group-based message as group-based message contents).
With respect to claim 19, Rose in view of Lo discloses the system of claim 15, wherein receiving, from the video conference provider (¶0055, one or more group-based communication channel identifiers associated with group-based communication channels (i.e. video conference) that the user has been granted access to, one or more group identifiers for groups with which the user is associated), the information about the network address based on the network address comprises:
outputting the network address to the video conference provider (Rose, ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A are discussed in connection with FIGS. 3-8);
receiving, from the video conference provider, a scope associated with the network address, wherein the scope is associated with an authentication information request (Rose, ¶0130, teaches group-based message 304C comprises a resource request in the form of URL “https://doc.ACME.com/12345.” In the depicted embodiment, the resource location requires authentication before a resource preview can be fully shown);
outputting, to the video conference provider, authentication information about the first client device (Rose, ¶0121, teaches visual outputs (e.g. a defined preview of a requested resource) that may be provided to a user by circuitry of client device 110A are discussed in connection with FIGS. 3-8, ¶0130, teaches group-based message 304C comprises a resource request in the form of URL “https://doc.ACME.com/12345.” In the depicted embodiment, the resource location requires authentication before a resource preview can be fully shown); and
receiving, from the video conference provider, the information about the network address based on the authentication information about the first client device (Rose, ¶0130, teaches group-based message 304C comprises a resource request in the form of URL “https://doc.ACME.com/12345.” In the depicted embodiment, the resource location requires authentication before a resource preview can be fully shown).
With respect to claim 20, Rose in view of Lo discloses the system of claim 15, wherein receiving, from the video conference provider (¶0055, one or more group-based communication channel identifiers associated with group-based communication channels (i.e. video conference) that the user has been granted access to, one or more group identifiers for groups with which the user is associated), the information about the network address based on the network address comprises:
outputting the network address and authentication information about the first client device to a webhook endpoint (Rose, ¶0067, teaches the resource provider may provide only an image file of the of ACME logo for the resource request: “http://logo.ACME.com.” Alternatively, the resource provider may also provide textual information such as a description of the logo, legal information such as copyright and trademark information, etc. Defined preview data may be in the form of a JSON object (i.e. webhook endpoint), a URL, or other data, ¶0072, teaches “user authentication information” may comprise information positively identifying a user, client device, or user profile and may include login credentials including user name, password, and other identifying information. An “authenticated user” refers to a user requesting a resource that has also been authenticated by the resource provider. For example, the resource provider may compare an event token to user authentication information in order to authenticate a user); and
receiving, from the webhook endpoint, the information about the network address based on the authentication information about the first client device (Rose, ¶0064, teaches the resource provider is also configured to receive authentication information to authenticate a defined preview request, as part of the defined preview request, ¶0067, teaches the resource provider may provide only an image file of the of ACME logo for the resource request: “http://logo.ACME.com.” Alternatively, the resource provider may also provide textual information such as a description of the logo, legal information such as copyright and trademark information, etc. Defined preview data may be in the form of a JSON object (i.e. webhook endpoint), a URL, or other data, ¶0072, teaches “user authentication information” may comprise information positively identifying a user, client device, or user profile and may include login credentials including user name, password, and other identifying information. An “authenticated user” refers to a user requesting a resource that has also been authenticated by the resource provider. For example, the resource provider may compare an event token to user authentication information in order to authenticate a user).
With respect to claims 21 and 23, Rose in view of Lo discloses the method of claim 1 wherein the application is a native desktop application different from the video conference client application (Rose, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video, audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text as well as an image and a video within the group-based message as group-based message contents, Lo, Col-9, II. 17-20, teaches client application 200 provides the instructions to native application 255 of content item 402 to execute the instructions).
With respect to claim 22, Rose in view of Lo discloses the method of claim 1 wherein:
the application is installed in the video conference client application of the first client device (Rose, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video, audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text as well as an image and a video within the group-based message as group-based message contents, ¶0131-¶0132, teaches the server then provides the opportunity to install the APP in the interface instance (e.g., installing the APP on the defined preview server 102) as shown in group-based message 304D), and the one or more controls include a second control to cause the application to execute on the first client device (Rose, ¶0025, teaches the defined preview comprises interactive graphical elements, wherein each interactive graphical element comprises a user selectable item, ¶0063 teaches the term “resource request” refers any electronically generated digital content object, such as text, which refers to an identification of a resource, such as document, image, video, web site (i.e. web page), ¶0141, teaches resource addresses are associated with a defined preview application (APP)), the application included in a video conference interface of the video conference client application corresponding to the video conference (Rose, ¶0059, teaches Group-based message communications may include any text (including a resource request), image, video (i.e. video conference), audio or combination thereof provided by a user (using a client device). For instance, a user may provide a group-based message that includes text as well as an image and a video within the group-based message as group-based message contents, ¶0074, teaches the selected group-based communication interface may be used as part of a standalone service, application, or device or it may be applied as a layer atop an existing service application or device).
With respect to claim 25, Rose in view of Lo discloses the method of claim 1, wherein joining a live collaborative session comprising the one or more client devices using the application to collaboratively edit a document comprises joining a live collaboration session comprising the one or more client devices using the application integrated into the video conference client application to collaboratively edit a document (Lo, Col-2, II. 32-37, teaches a data stream, such as a series of real-time images or Video, of the native application window containing the content item on the host device is transmitted to each participant of the collaborative editing session (i.e. live collaborative session) over the peer-to-peer connection to the web browser of each client device, Col-5, II. 15-26, teaches as an alternative, client application 200 may integrate access to content management system 110 with the local file management system provided by operating system 245. When access to content management system 110 is integrated in the local file management system, a file organization scheme maintained at content management system 110 is represented as a local file structure by operating system 245 in conjunction with client application 200. Client application 200 may take various forms, such as a stand-alone application, an application plug-in, a browser extension, and so forth, Col-6, II. 5-19, teaches a user provides a request to open a content item via a native client application 255 for the content item on client device A. Native application 255 sends a request to launch the content item from a file folder and the content item is displayed 302 on client device A. Subsequently, client device B and client device C send 304 collaboration requests identifying the content item to client device A to initiate a collaborative editing session (i.e. live collaborative session) with client device A as the host device. In this example, client device B and client device C have sent the collaboration request via a web browser from a webpage. Accordingly, client application 200 of client device A receives the collaboration requests and connection module 210 establishes a peer-to-peer connection (P2P) with each web browser of client device B and client device C, Col-8, II. 52-57, teaches changes provided to content item 402 via a screen sharing interface (i.e., screen sharing window 404) are made to the file of content item 402 via communications between screen sharing window 404 simultaneously provided on each of client devices B and C and client application 200 of host device A over the peer to peer connection, Col-9, II. 25-29, teaches real-time content item collaboration is the simultaneous editing or viewing of a content item remotely hosted by a host client device where other devices are able to make edits or other changes to the content item on the host machine via their own client device).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US9218102B1 teaches Collaborative editing of electronic documents in realtime is provided. A host serves a client code over a network to a plurality of clients that each employ a browser to run the client code. The client code revises the text document locally in response to user input, frequently sends those edits to the host, receives updates from the other clients via the host, and revises the local text document accordingly. Each client, in some embodiments, stores three variables, one for edits not yet reported to the host, one for edits reported by not yet acknowledged, and one for the text document as modified by the acknowledged edits. Updates from the other clients are applied to the three variables according to certain rules. A composition of the three variables yields a version of the text document. The host keeps records of which edits were introduced by which client.
US20030225832A1 teaches A multimedia collaboration system that integrates separate real-time and asynchronous networks—the former for real-time audio and video, and the latter for control signals and textual, graphical and other data—in a manner that is interoperable across different computer and network operating system platforms and which closely approximates the experience of face-to-face collaboration, while liberating the participants from the limitations of time and distance. These capabilities are achieved by exploiting a variety of hardware, software and networking technologies in a manner that preserves the quality and integrity of audio/video/data and other multimedia information, even after wide area transmission, and at a significantly reduced networking cost as compared to what would be required by presently known approaches. The system architecture is readily scalable to the largest enterprise network environments. It accommodates differing levels of collaborative capabilities available to individual users and permits high-quality audio and video capabilities to be readily superimposed onto existing personal computers and workstations and their interconnecting LANs and WANs. In a particular preferred embodiment, a plurality of geographically dispersed multimedia LANs are interconnected by a WAN. The demands made on the WAN are significantly reduced by employing multi-hopping techniques, including dynamically avoiding the unnecessary decompression of data at intermediate hops, and exploiting video mosaicing, cut-and-paste and-audio mixing technologies so that significantly fewer wide area transmission paths are required while maintaining the high quality of the transmitted audio/video.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to GOLAM MAHMUD whose telephone number is (571)270-0385. The examiner can normally be reached Mon-Fri 8.00-5.00pm.
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, Umar Cheema can be reached at 5712703037. 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.
/G.M/Examiner, Art Unit 2458
/UMAR CHEEMA/Supervisory Patent Examiner, Art Unit 2458
Prosecution Insights