Cloud-based document license management
By generating unique links and permissions associated with cloud-based documents, the problem of document owners struggling to manage user access permissions is solved, enabling flexible permission management and intuitive user interaction.
Patent Information
- Application Number
- CN202410041020.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-06-29
- Filing Date
- 2018-06-29
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2038-06-29
AI Technical Summary
In cloud-based document collaboration, document owners find it difficult to intuitively manage and isolate access permissions for different users, resulting in unintuitive user interactions.
By generating and maintaining unique links associated with cloud-based documents, each link linked to a unique identifier and license, different client devices are allowed to access and interact with the documents based on their permissions, including editing or viewing rights, and different interactive elements are displayed through a graphical user interface.
It enables flexible permission management for different users, allowing different client devices to edit or view as needed, and can update and revoke permissions in real time, improving the intuitiveness and security of user interaction.
Smart Images

Figure CN117874375B_ABST
Abstract
Description
[0001] Case information
[0002] This application is a divisional application of the invention patent application filed on June 29, 2018, with application number 201810696031.3 and invention title "Cloud-based Document License Management".
[0003] Cross-referencing related applications
[0004] This application relates to a co-pending U.S. patent application filed June 29, 2017, application number 15 / 637,729, entitled "Presentation Collaboration with Various Electronic Devices" (Attorney No. 3462.0660000); a co-pending U.S. patent application filed June 29, 2017, application number 15 / 637,096, entitled "Color Theme Maintenance For Presentations" (Attorney No. 3462.0630000); and a co-pending U.S. patent application filed June 29, 2017, application number 15 / 637,717, entitled "Automatic Layout". The co-pending U.S. patent application “Engine (Automatic Layout Engine)” (Attorney No. 3462.0620000) and the co-pending U.S. patent application filed on June 29, 2017, application No. 15 / 637,077, entitled “Smart Defaults Based on Previous Settings For PresentationSlides” (Attorney No. 3462.0650000), are all incorporated herein by reference in their entirety. Background Technology
[0005] As document creation has evolved, authors, editors, and programmers sometimes collaborate with other contributors. To facilitate collaborative document creation among many writers, cloud-based document generation has become a common architecture, allowing numerous users to access and / or edit documents. In some cases, cloud-based documents may reside in a repository, allowing a single user to access and / or edit the document at a time. For example, cloud-based documents may implement a "checkout" feature, allowing only one editor to make changes at a time. In other cases, some cloud-based documents may allow real-time document editing.
[0006] However, as collaboration develops, document owners may want to isolate users and grant different types of access to different individuals. The challenge with this isolation is that the different licenses must be intuitive for the document owner so that users can use them intuitively. Attached Figure Description
[0007] The accompanying drawings are incorporated herein and form part of the specification.
[0008] Figure 1 This is a block diagram of a document license management system according to some embodiments.
[0009] Figure 2 This is a block diagram of a document license management system that highlights different licenses according to some embodiments.
[0010] Figure 3A It is a screen display of a document interaction graphical user interface according to some embodiments.
[0011] Figure 3B This is a screen display of a chat panel according to some embodiments.
[0012] Figure 4A It is a screen display of a graphical user interface enabled by an editor according to some embodiments.
[0013] Figure 4B It is a screen display of a graphical user interface enabled by a viewer according to some embodiments.
[0014] Figure 5 These are exemplary computer systems for implementing various embodiments.
[0015] In the accompanying drawings, the same reference numerals usually denote the same or similar elements. Furthermore, the leftmost numeral of the reference numerals typically indicates the drawing in which the reference numeral first appears. Detailed Implementation
[0016] This document provides embodiments of systems, apparatuses, devices, methods, and / or computer program products for managing licenses associated with cloud-based documents, and / or combinations and sub-combinations thereof.
[0017] The systems and methods described herein can manage, assign, and / or send licensed links associated with cloud-based documents. In one embodiment, the document generation system can generate and / or maintain documents. The document can be a computer-readable document that can be displayed on a computer screen and / or monitor. For example, the document may include text, images, spreadsheets and / or tables, presentations, slides, computer program code, and / or internet browser code. In embodiments, the document may include temporary information, such as audio and / or video files. The document generation system can generate documents upon request from users and / or client devices. The document generation system can also store documents in a repository within the document generation system.
[0018] In this embodiment, the document generation system may maintain licenses associated with the generated documents. The document generation system may maintain licenses based on different links associated with the documents. Links may be, for example, Uniform Resource Locators (URLs), Uniform Resource Identifiers (URIs), and / or embedded web page objects that authorize client devices to access servers and / or databases maintaining the documents. The document generation system may generate unique links to the documents and may send these unique links to client devices. Each link may be associated with one or more unique identifiers and unique licenses. If a client device uses the link to access the associated document, the client device may receive the license associated with the link used. This link structure may allow the document generation system to grant different document licenses to different client devices.
[0019] In one embodiment, the link may include a unique identifier. The document generation system can format the link to include the unique identifier, for example, by generating a unique text URL. The document generation system can then send the link to a client device. In another embodiment, the document generation system may maintain an index of unique identifiers and permissions associated with the unique link identifier. Permissions may include permissions associated with the cloud-based document. For example, permissions may include allowing client devices accessing the link to edit the associated cloud-based document. In another embodiment, the link may not allow editing the document but may instead allow client devices to view the document. In yet another embodiment, the link may allow commenting and / or interaction with chat features associated with the document. In yet another embodiment, commenting and / or chat interaction may be coupled with editor and / or viewer permissions.
[0020] In this embodiment, client devices can share links. Because the document generation system can associate permissions with links, links can be shared among different client devices, thereby granting other client devices the same associated permissions. For example, the link can be embedded in a webpage or sent via electronic messaging, allowing multiple client devices to access the link. In this embodiment, sharing links can still maintain a unique identifier associated with the link. If multiple client devices use the same link to access the document, the document generation system can still distinguish each client device using a unique identifier (e.g., an Internet Protocol (IP) address associated with the client device). In this embodiment, although the document generation system can distinguish each client device, it can still grant the same permissions to client devices accessing the document using the same link.
[0021] In this embodiment, the document generation system can modify the licenses associated with the links. The document generation system can revoke licenses and / or grant other licenses to enable further interaction with the document. This embodiment may allow the revocation of licenses for links that may be broken and / or become insecure. This embodiment may also allow enabling features for client devices that have already received the links.
[0022] In this embodiment, the graphical user interface (GUI) display may be a license associated with a link. For example, when a client device accesses a link, the document generation system may generate a GUI that allows the client device to interact with the document associated with the link. The client device may display the GUI and / or use the GUI to send commands to the document generation system. In this embodiment, the GUI may display a link for accessing the document, a document interface for interacting with the document, and / or a chat panel with chat features enabled.
[0023] In some embodiments, the GUI may display different elements depending on the license associated with the link. For example, a client device accessing the link with an editor license may view a different GUI than a client device accessing the link with a viewer license. In some embodiments, the GUI associated with an editor license may include a document editing interface, an editor chat panel, and / or a viewer chat panel. In some embodiments, the GUI associated with a viewer license may include a document viewing interface and / or a viewer chat panel.
[0024] The chat panel can be one or more parts of the GUI and / or can share the association between the GUI and the document. The document generation system can instantiate the chat panel, receive comments and / or chat messages from client devices via the chat panel, and / or maintain the comments and / or chat messages in a repository. The client device can use the GUI to send comments and / or chat messages to the document generation system. In an embodiment, the document generation system can associate a link for accessing a document with the comments and / or chat messages received in the chat panel.
[0025] In this embodiment, the document generation system can generate a document reference associated with comments and / or chat messages. The document generation system can identify parameters related to the document and associate these parameters with the comments and / or chat messages. For example, the document generation system can generate a presentation including several slides and links associated with the presentation. The document generation system can send the links to a client device, allowing the client device to access a GUI and interact with the slides of the presentation. If the document generation system receives comments from the client device while the slides are displayed on the GUI, the document generation system can associate the slide number of the displayed slide with the received comment. In embodiments where the document is a text document comprising one or more pages, the document generation system can associate the page number of the displayed page with the received comment.
[0026] In one embodiment, the document generation system can receive comments associated with a document from a first client device. The first client device can interact with the document via a first GUI displayed on the first client device. The document generation system can store the received comments and / or associate document references with the comments. The document generation system can then receive a request to access the document from a second client device. The second client device can access the document using the same links as the first client device, or it can use different links generated by the document generation system. The document generation system can send a second GUI to the second client device. The second GUI may or may not display the same GUI components as the first GUI. Using the second GUI, the second client device can interact with the document and view the comments received from the first client device.
[0027] In an embodiment, if the document is a presentation, the comments may include slide number references. When a second client device accesses the presentation via a link, the second client device can interact with the slides of the presentation via a second GUI. When the second client device views the slide associated with the comment, the document generation system can send the comment to the second client device. When the second client device accesses the slide associated with the comment, the second GUI can display the comment. In an embodiment, the second GUI can display the comment in a chat panel. In an embodiment, the second GUI may not display the comment if the slide associated with the comment is not displayed on the second GUI.
[0028] In an embodiment, the chat panel associated with the second GUI may utilize notification features to alert the user to new comments and / or chat messages. For example, after the second client device accesses a document with comments and / or chat messages, the document generation system may send a notification to the second GUI indicating that the comments and / or chat messages are associated with a document not yet displayed on the second client device. This notification may include comments, chat messages, a first client device identifier, and / or a document reference indicating a portion of the document to which the comments and / or chat messages apply.
[0029] These features will now be discussed with respect to the corresponding figures.
[0030] Figure 1 This is a block diagram of a document license management system 100 according to some embodiments. In these embodiments, the document license management system 100 can generate cloud-based documents and / or manage links and licenses associated with those cloud-based documents. The document license management system 100 may include a document generation system 110, a network 120, and one or more client devices 130A, 130B, ..., 130n.
[0031] In this embodiment, document generation system 110 can generate, store, and / or maintain cloud-based documents. Document generation system 110 can also generate links associated with the cloud-based documents. Document generation system 110 can also assign licenses to links and / or maintain records of links and associated licenses. Document generation system 110 may include server 111 and document database 112.
[0032] In this embodiment, server 111 may include one or more processors, memory, routers, modems, antennas, and / or circuitry, configured to interface with document database 112, network 120, and / or client device 130. Server 111 may communicate with client device 130 using network 120 and / or network protocols. Network 120 may include a network capable of transmitting information wired or wirelessly, and may be, for example, the Internet, a local area network (LAN), and / or a wide area network (WAN). Network protocols may be, for example, Hypertext Transfer Protocol (HTTP), TCP / IP, Ethernet, or asynchronous transfer mode (ATM). Server 111 may send and / or receive information to client device 130. Server 111 may process information sent and / or received from client device 130. Server 111 may retrieve information (e.g., document attributes) from document database 112 and / or send that information to client device 130. Server 111 may receive document interactions and / or commands from client device 130.
[0033] In this embodiment, server 111 may be configured to generate cloud-based documents. Cloud-based documents may include text, images, spreadsheets and / or tables, presentations, slides, computer program code, and / or internet browser code. In this embodiment, cloud-based documents may include temporary information, such as audio and / or video files. Server 111 may use a database management system to interact with document database 112 and / or store the generated cloud-based documents in document database 112. Document database 112 may include tables, records, indexes, and / or other storage configured to store cloud-based documents and / or records of licenses associated with the cloud-based documents.
[0034] In one embodiment, server 111 may instantiate a cloud-based document based on a command received from client device 130. Client device 130 may be a computing platform, such as, but not limited to, a smartphone, tablet, laptop, desktop computer, web browser, and / or other computing devices configured to connect to network 120 to communicate with document generation system 110. In one embodiment, server 111 may receive and / or store documents generated by client device 130. Server 111 may associate client device ownership of the document based on attributes of the client device 130 that requested document generation. For example, client device 130A may request document generation. Client device 130A may provide account information and / or login information to document generation system 110. In response to receiving account information and / or login information, document generation system 110 may allow client device 130A to generate the document. In one embodiment, server 111 may associate document ownership with client device 130A and / or the account associated with client device 130A. In this embodiment, a user can access the document generation system 110 using different client devices 130, and can still access the documents they own by providing the same account information using another client device 130. In this embodiment, the server 111 can store the generated documents in the document database 112 and / or maintain ownership records for the generated documents.
[0035] In an embodiment, a client device 130 and / or account considered the document owner can specify permissions associated with the document. The owner can use client device 130 to interact with document generation system 110 to manage permissions associated with the documents they own. In an embodiment, document generation system 110 can receive commands to generate one or more links to the document and / or send links to client device 130. Links can be, for example, Uniform Resource Locators (URLs), Uniform Resource Identifiers (URIs), and / or embedded web page objects that authorize client device 130 to access documents stored in document generation system 110.
[0036] The document generation system 110 can generate unique links to documents and send these unique links to one or more client devices 130A, 130B, ..., 130n. Each link can be associated with one or more unique identifiers and / or unique licenses. If a client device 130 uses the link to access the associated document, the client device 130 can receive the license associated with the used link from the document generation system 110. This link structure allows the document generation system 110 to grant different document licenses to different client devices 130.
[0037] In one embodiment, the link may include a unique identifier. The document generation system 110 may format the link to include the unique identifier, for example, by generating a unique text URL. The document generation system 110 may then send the link to the client device 130. In another embodiment, the client device 130A may send a command to the document generation system 110, causing the document generation system 110 to send the link to the client device 130B.
[0038] In this embodiment, the document generation system 110 may maintain an index of unique link identifiers and / or permissions associated with unique identifiers. The document generation system 110 may store this index in the document database 112 and / or in a separate memory storage device.
[0039] The associated permissions may include permissions associated with the cloud-based document. For example, a permission may include allowing client device 130 to access the link to edit the associated cloud-based document. In an embodiment, the link may not allow editing the document, but may instead allow client device 130 to view the document. In an embodiment, the link may allow commenting and / or interaction with chat features associated with the document. In an embodiment, commenting and / or chat interaction may be coupled with editor and / or viewer permissions. Document permissions and chat features will be referenced... Figures 3A to 3B and Figures 4A to 4B Further discussion.
[0040] In one embodiment, client devices 130 accessing a link can share the link. Because the document generation system 110 can associate a license with a link, the link can be shared among different client devices 130, granting the same associated license to other client devices 130. In another embodiment, client device 130A can receive a link from the document generation system 110. Client device 130A can then send the link to one or more other client devices 130. For example, the link can be embedded in a webpage or sent via electronic messaging, allowing multiple client devices 130 to access the link.
[0041] In this embodiment, the shared link can still maintain a unique identifier associated with it. If multiple client devices 130 use the same link to access a document, the document generation system 110 can still use a unique identifier (e.g., an Internet Protocol (IP) address, telephone number, Global Positioning System (GPS) information, account information, and / or other information that can distinguish client devices 130) to differentiate each client device 130. In this embodiment, although the document generation system 110 can distinguish each client device 130, it can still grant the same permission to client devices 130 that access the document using the same link.
[0042] In this embodiment, the document generation system 110 can modify the licenses associated with the links. The document generation system 110 can revoke licenses and / or grant other licenses to enable further interaction with the document. This embodiment may allow the revocation of licenses for links that may be broken and / or become insecure. This embodiment may also allow enabling features for client devices 130 that have already received the links.
[0043] In this embodiment, the graphical user interface (GUI) display may be a license associated with a link. For example, when client device 130 accesses a link, document generation system 110 may generate a GUI allowing the client device to interact with the document associated with the link. Client device 130 may display the GUI and / or use the GUI to send commands to the document generation system. In this embodiment, the GUI may display a link for accessing the document, a document interface for interacting with the document, and / or a chat panel with chat features enabled. The GUI display features will refer to... Figures 3A to 3B and Figures 4A to 4B Further detailed discussion.
[0044] Figure 2 This is a block diagram highlighting different licenses of a document license management system 200 according to some embodiments. In the embodiments, the document license management system 200 may include a document generation system 210, a network 220, and client devices. The client devices are divided into two categories: editor client devices 232A, 232B, ..., 232n and viewer client devices 234A, 234B, ..., 234n. The document generation system 210 may include, as referenced... Figure 1 The document generation system 110 described herein contains similar components. These components may include a server 211 and a document database 212, which can be configured to work in conjunction with the referenced... Figure 1 The described server 111 and document database 112 operate in a similar manner. Network 220 may include, and also refers to... Figure 1 The components described are similar to those in Network 120.
[0045] Editor client devices 232A, 232B, ..., 232n and / or viewer client devices 234A, 234B, ..., 234n can be computing platforms, such as, but not limited to, smartphones, tablets, laptops, desktop computers, web browsers, and / or other computing devices configured to connect to network 220 to communicate with document generation system 210. In some embodiments, editor client device 232A may include hardware different from editor client device 232B. In some embodiments, editor client device 232A may include the same hardware as editor client device 232B. In some embodiments, viewer client device 234A may include hardware different from viewer client device 234B. In some embodiments, viewer client device 234A may include the same hardware as viewer client device 234B. In some embodiments, editor client device 232A may include hardware different from viewer client device 234A. In some embodiments, editor client device 232A may include the same hardware as viewer client device 234A.
[0046] In one embodiment, editor client device 232A may differ from editor client device 232B based on a link received from document generation system 210. Document generation system 210 may send a first link to editor client device 232A and a second link to editor client device 232B. Document generation system 210 may associate different licenses with the first and second links. Document generation system 210 may assign licenses received from the document's owner. In one embodiment, the first and second links may be associated with editor licenses, allowing editor client device 232 interacting with the first or second link to edit the associated document. In another embodiment, the licenses associated with the first and second links may be the same.
[0047] In this embodiment, the permission associated with the first link may differ from the permission associated with the second link. For example, when editor client device 232A interacts with the document using the first link, document generation system 210 may allow editor client device 232A to edit parts and / or subsets of the document. Conversely, when editor client device 232B interacts with the document using the second link, document generation system 210 may allow editor client device 232B to edit the entire document. Editor client device 232B has the right to edit the entire document, while editor client device 232A has the right to edit parts of the document. For example, document generation system 210 may restrict editor client device 232A to certain pages of a text document, certain slides of a presentation, certain sections of software code, certain parts of an audio file, and / or certain parts of a video file.
[0048] In this embodiment, the editor client device 232A may be able to view the viewer chat panel on the GUI display (as shown in reference). Figure 4A (as described above), while editor client device 232B cannot view the viewer chat panel. In an embodiment, editor client device 232A can view the editor chat panel on the GUI display, while editor client device 232B cannot. Because document generation system 210 manages permissions associated with links sent to editor client devices 232, document generation system 210 can customize the permissions associated with each link. This customization can allow shared editing permissions between editor client devices 232, but specific editing restrictions can be applied to certain editor client devices 232. Customizable link permissions can allow for greater flexibility in managing cloud-based document access.
[0049] The link sent to viewer client device 234 may also include a customizable license. In an embodiment, document generation system 210 may send a first link to viewer client device 234A and a second link to viewer client device 234B. The first and second links may be associated with a viewer license, allowing viewer client device 234 to interact with either the first or second link to view the associated document. In an embodiment, the license associated with the first and second links may be the same.
[0050] In this embodiment, the permission associated with the first link may differ from the permission associated with the second link. For example, when viewer client device 234A interacts with the document using the first link, document generation system 210 may allow viewer client device 234A to view portions and / or subsets of the document. Conversely, when viewer client device 234B interacts with the document using the second link, document generation system 210 may allow viewer client device 234B to view the entire document. Viewer client device 234B may have viewer permission to view the entire document, while viewer client device 234A may have viewer permission to view portions of the document. For example, document generation system 210 may restrict viewer client device 234A to certain pages of a text document, certain slides of a presentation, certain segments of software code, certain portions of an audio file, and / or certain portions of a video file.
[0051] In this embodiment, the viewer client device 234A may be able to view the viewer chat panel on a GUI display (as shown in reference). Figure 4B(as described above), while viewer client device 234B cannot view the viewer chat panel. Because document generation system 210 manages permissions associated with links sent to viewer client devices 234, document generation system 210 can customize the permissions associated with each link. This customization can allow shared viewing permissions among viewer client devices 234, but specific viewing restrictions can be applied to certain viewer client devices 234.
[0052] In an embodiment, the document generation system 210 may restrict the time during which the viewer client device 234 can view the document. For example, the document generation system 210 may specify time windows during which access to the document is allowed and / or not allowed. For example, a link sent to the viewer client device 234A may allow the viewer client device 234A to access the document between 3:00 PM and 4:00 PM. In an embodiment, this time window may correspond to a presentation of the document, such as a PowerPoint presentation. In an embodiment, the document generation system 210 may impose a time limit on access to the document via the link. For example, the viewer client device 234A may be allowed to view the document for one hour from the moment the viewer client device 234A first uses the link.
[0053] In one embodiment, the document generation system 210 may set location restrictions on links sent to the viewer client device 234. For example, although the viewer client device 234A can access the link, the document generation system 210 may require the viewer client device 234A to be located at a specific geographic location before granting access to the document. In one embodiment, the document generation system 210 may require the viewer client device 234A to provide Global Positioning System (GPS) coordinates before authorizing access to the document. In another embodiment, the document generation system 210 may determine the location of the viewer client device 234A based on its IP address.
[0054] The license described in the reference viewer client device 234 can also be applied to the editor client device 232.
[0055] In an embodiment, editor client device 232 may differ from viewer client device 234 based on the link received from document generation system 210. For example, editor client device 232A may receive a first link from document generation system 210 with an editor license associated with the first link. Viewer client device 234A may receive a second link from document generation system 210 with a viewer license associated with the second link. The first and second links may be associated with the same document. In an embodiment, document generation system 210 may convert the license associated with the first link from an editor license to a viewer license or vice versa. Although editor client device 232 may have already retained ownership of the link based on the revocation of its editor license, editor client device 232 may be converted to viewer client device 234. Document generation system 210 may change the license associated with the link due to potential security breaches. In one embodiment, the document generation system 210 can convert the license associated with the second link from a viewer license to an editor license so as to easily and quickly grant editor access to the viewer client device 234 and convert the viewer client device 234 into an editor client device 232.
[0056] In this embodiment, even after the editor client device 232 receives the editor link, the document generation system 210 can still change the license, grant, and / or revoke the license associated with the link. The document generation system 210 can also perform this customization using a viewer link already received by the viewer client device 234.
[0057] In one embodiment, the document generation system 210 may send a first link to the editor client device 232A and a second link to the viewer client device 234A. The first and second links may correspond to the same cloud-based document stored in the document generation system 210. While the viewer client device 234A can view the document, the editor client device 232A can continue editing it. In one embodiment, the document generation system 210 may receive edits from the editor client device 232A, update the stored cloud-based document, and / or send edits to the viewer client device 234A. In one embodiment, these edits may be sent to the viewer client device 234A in real-time or near real-time. In one embodiment, the viewer client device 234A does not need to refresh the document or re-request the document to view the updates. Similarly, another editor client device 232B may also access the document and view the edits in real-time. In another embodiment, the document generation system 210 may request updates from the viewer client device 234A and / or the editor client device 232B before sending the updates.
[0058] In this embodiment, the document may be a presentation. Using editor links, editor client device 232A can edit the presentation into different completion stages. In this embodiment, editor client device 232A may also possess the presentation, allowing editor client device 232A to dictate licenses associated with the presentation. Editor client device 232A may send a command to document generation system 210 to generate another editor link for editor client device 232B. Document generation system 210 may generate the link and send it to editor client device 232B. In this embodiment, document generation system 210 may generate the link for editor client device 232A. Editor client device 232A may then send the link to editor client device 232B. After receiving the editor link, editor client device 232B can edit the presentation. In this embodiment, editor client device 232B can access the presentation, while editor client device 232A is also accessing the presentation. This embodiment allows editor client devices 232A and 232B to edit the presentation simultaneously and in real time.
[0059] In one embodiment, editor client device 232A can send a command to document generation system 210 to generate a viewer link for viewer client device 234A. Document generation system 210 can generate the link and send it to viewer client device 234A. In another embodiment, document generation system 210 can generate the link for editor client device 232A. Editor client device 232A can then send the link to viewer client device 234A. After receiving the viewer link, viewer client device 234A can view the presentation even while editor client devices 232A and / or 232B are still editing the presentation. In the context of the presentation, if changes are needed during presentation delivery, editor client devices 232A and / or 232B can quickly edit the presentation without interrupting the flow of the given presentation and / or without needing to re-deliver an updated presentation file. In another embodiment, the owner of editor client device 232A and / or the presentation can specify the portion of the presentation seen by viewer client device 234A. The ability to control portions of a document viewed by the viewer client device 234 can also be applied to other document types and can be changed in real time by the document owner.
[0060] In this embodiment, the configuration allows editor client device 232A and / or document owner to quickly generate viewer links for presentations. The document owner can send the link to effectively deliver presentation slides to one or more viewer client devices 234. In this embodiment, because the document owner and / or editor client device 232A can also manipulate portions of the presentation seen by the viewer client device 234, the document owner and / or editor client device 232A can use the presentation slides as a customizable visualization tool. This configuration can allow for cross-platform presentations using viewer links. In this embodiment, the configuration can eliminate the need for the document owner to output and / or send presentation files. In this embodiment, the configuration can also eliminate the need for the document owner to share their computer screen, which may display private information other than the presentation. The document link configuration can allow for faster deployment of documents, such as presentations. These permissions and controls for viewer document interaction can also be applied to other document types described above.
[0061] Figure 3A This is a screen display of a document interactive graphical user interface (GUI) 300 according to some embodiments. The document generation system can instantiate the document interactive GUI 300 and / or provide access to the document interactive GUI 300 to client devices. The document interactive GUI 300 can be developed using an application programming interface (API). In an embodiment, the document generation system can send a licensed link 310 to the client device, allowing the client device to access the document. The document interactive GUI 300 can be displayed on the client device, allowing the client device to interact with the document.
[0062] In an embodiment, the document interaction GUI 300 may include a license association link 310, a document interface 320, and / or a chat panel 330. A client device utilizing the license association link 310 can access the document using, for example, a web browser. In an embodiment, after obtaining the license association link 310, the client device can use a link request in its web browser to access the page and / or document associated with the license association link 310. In an embodiment, the license association link 310 may include a page address and / or may be an HTTP request. Utilizing the license association link 310 allows it to be displayed in the document interaction GUI 300.
[0063] If the document generation system receives an access request, it may return one or more files to the requesting client device, such as HTML files, images, flash files, JavaScript files, CSS files, audio files, video files, and / or other files used to generate the document interactive GUI 300.
[0064] Based on a file instantiated by the document generation system, the document interaction GUI 300 may include a document interface 320 and / or a chat panel 330. In an embodiment, the document interface 320 may display a document stored in the document generation system. The document interface 320 may allow a client device displaying the document interaction GUI 300 to interact with the document. The available document interaction may depend on a license association link 310 used to access the document. For example, if the license association link 310 is associated with an editor license, the client device is allowed to edit the document, and the client device can edit the document using the document interface 320. For example, the client device may utilize computer peripherals (e.g., a mouse, keyboard, and / or touchscreen display) to manipulate the document displayed in the document interface 320. In an embodiment, the client device may send these edits to the document generation system that instantiated the document.
[0065] In one embodiment, if license association link 310 is associated with a viewer license that allows the client device to view the document, the client device can use document interface 320 to view the document. In another embodiment, document interface 320 may display portions of the document depending on the viewer license associated with license association link 310. In yet another embodiment, the viewer license may allow the client device to navigate the entire document using document interface 320. Also in another embodiment, the viewer license may restrict the portions of the document that the client device can navigate. Using document interface 320, the client device can interact with the document.
[0066] Chat panel 330 will refer to Figure 3B Describe it. Figure 3B This is a screen display of a chat panel 330 according to some embodiments. The chat panel 330 may be part of a document interaction GUI 300. In embodiments, permission-associated links 310 may allow commenting and / or interaction with chat features associated with the document. In embodiments, commenting and / or chat interaction may be coupled with editor and / or viewer permissions.
[0067] Chat panel 330 may be one or more parts of document interaction GUI 300 and / or may be associated with a document displayed in document interface 320. The document generation system may instantiate chat panel 330, receive comments and / or chat messages from client devices via chat panel 330, and / or maintain comments and / or chat messages in a repository. Client devices may utilize chat panel 330 to send comments and / or chat messages to the document generation system. In an embodiment, the document generation system may associate licensed association links 310 with comments and / or chat messages received in chat panel 330.
[0068] In this embodiment, the client device can submit input message 333 to the chat panel 330. In this embodiment, input message 333 may include text messages, image messages, audio messages, and / or video messages. In this embodiment, if the client device is equipped with a text input peripheral, such as a keyboard and / or a touchscreen display, the client device can receive text input message 333. In this embodiment, if the client device is equipped with a camera, the client device can capture images and / or video as input message 333. In this embodiment, if the client device is equipped with a microphone, the client device can capture audio messages as input message 333. In this embodiment, the chat panel 330 can display predefined input message 333, allowing the client device to send selection commands as input message 333.
[0069] In this embodiment, when input message 333 is received on the chat panel 330, the client device displaying the document interaction GUI 300 can send input message 333 to the document generation system. In this embodiment, the document generation system can store input message 333 and / or generate user message 331, associating input message 333 with user identifier 332 and / or document reference 334. In this embodiment, the client device can generate user message 331 including input message 333, user identifier 332, and / or document reference 334. If the client device generates user message 331, it can send the message to the document generation system.
[0070] In an embodiment, to construct user message 331, the client device and / or document generation system receiving input message 333 may associate user identifier 332 and / or document reference 334 with input message 333. User identifier 332 may be an identifier of the user submitting input message 333. For example, user identifier 332 may be a license association link 310, a portion of license association link 310, and / or an identifier defined by the client device, such as a selected display name submitted with input message 333. In an embodiment, user identifier 332 may include a location-based identifier and / or a time-based identifier, such as a timestamp associated with the submission of input message 333.
[0071] Document reference 334 may be a parameter relating to a document associated with license association link 310. Document reference 334 may refer to a portion of a document relating to input message 333. For example, a document generation system may generate a presentation including several presentation slides and a license association link 310 associated with the presentation. The document generation system may send the link to a client device, allowing the client device to access the document interactive GUI 300 and interact with the presentation slides. When slides are displayed on the document interactive GUI 300, if the document generation system receives input message 333 from the client device, the document generation system may associate the slide number of the displayed slide with input message 333. Document reference 334 may include the displayed slide number. In embodiments where the document is a text document comprising one or more pages, when pages are displayed on the document interactive GUI 300, if the document generation system receives input message 333 from the client device, the document generation system may associate the page number of the displayed page with input message 333. Document reference 334 may include the displayed page number.
[0072] In this embodiment, the document generation system can associate user message 331 with a document associated with the permission association link 310. When another client device accesses the document, the client device can display a separate instance of chat panel 330, which can display the stored user message 331. For example, a first client device can be associated with user message 331A. A second client device can view user message 331A and / or can submit input message 333B to generate user message 331B.
[0073] In an embodiment, the chat panel 330 may include notification features to alert the user to new user messages 331. For example, after a client device accesses a document with an associated user message 331, the document generation system may send a notification to the client device indicating that a new user message 331 has been associated with a document that the client device has not previously displayed. This notification may be the user message 331 and may include an input message 333, a user identifier 332, and / or a document reference 334. In an embodiment, the notification may include different colors, audio tones, and / or the presence of separate display elements displayed on the document interaction GUI 300 between different user messages 331.
[0074] Figure 4A This is a screen display of an editor-enabled graphical user interface (GUI) 400 according to some embodiments. In embodiments, the editor-enabled GUI 400 may display an editor license association link 410, a document editing interface 420, an editor chat panel 430, and a viewer chat panel 435. Figure 4B This is a screen display of a viewer-enabled graphical user interface (GUI) 405 according to some embodiments. In embodiments, the viewer-enabled GUI 405 may display a viewer license association link 415, a document viewing interface 425, and a viewer chat panel 435. An editor-enabled GUI 400 and a viewer-enabled GUI 405 will be discussed together to illustrate comparative embodiments.
[0075] The document generation system can instantiate an editor-enabled GUI 400 and / or provide access to the editor-enabled GUI 400 to client devices. The document generation system can also instantiate a viewer-enabled GUI 405 and / or provide access to the viewer-enabled GUI 405 to client devices. Application Programming Interfaces (APIs) can be used to develop the editor-enabled GUI 400 and / or the viewer-enabled GUI 405.
[0076] In this embodiment, the document generation system can send an editor license association link 410 to a first client device, allowing the first client device to access and / or edit the document. The document generation system can associate the editor license association link 410 with an editor's license. When the first client device accesses the editor license association link 410, an editor-enabled GUI 400 can be displayed on the first client device, allowing the first client device to view and / or edit the document.
[0077] In this embodiment, the document generation system can send a viewer license association link 415 to a second client device, allowing the second client device to view the document or a portion thereof. The document generation system can associate the viewer license association link 415 with a viewer license. When the second client device accesses the viewer license association link 415, a viewer-enabled GUI 405 can be displayed on the second client device, allowing the second client device to view the document.
[0078] The document editing interface 420 may be part of the editor-enabled GUI 400. In an embodiment, the document editing interface 420 may display a document and / or allow editing of the document. This interaction may be similar to that described in the reference. Figure 3A The editing features described in document interface 320 occur in a manner that is consistent with the document interface.
[0079] The document viewing interface 425 may be part of the viewer-enabled GUI 405. In an embodiment, the document viewing interface 425 may display the document and / or portions of the document. Viewing the document can be similar to... Figure 3A The document interface 320 describes how to view license features.
[0080] In this embodiment, if a client device has already accessed the editor permission association link 410 to view the editor-enabled GUI 400, the client device can also display the editor chat panel 430 and the viewer chat panel 435. In this embodiment, the editor chat panel 430 can receive and / or display user messages sent from other client devices that have already accessed the editor permission association link 410. For example, if a first client device has accessed the first editor permission association link 410 and has generated input messages related to the underlying document, a second client device that has accessed the second editor permission association link 410 can view the input messages generated by the first client device. In this embodiment, client devices accessing the editor permission association link 410 can communicate and add comments and annotations about the document in the editor chat panel 430.
[0081] Conversely, in this embodiment, the viewer chat panel 435 may differ from the editor chat panel 430. The viewer chat panel 435 may display user messages and / or input messages related to documents from client devices that have accessed the viewer license association link 415, such as... Figure 4BAs shown. In an embodiment, the viewer-enabled GUI 405 can display the viewer chat panel 435, but not the editor chat panel 430. In an embodiment, client devices using the viewer license association link 415 cannot view the editor chat panel 430. In an embodiment, this configuration allows client devices accessing the editor license association link 410 to view user messages and / or input messages from client devices that have already accessed the viewer license association link 415. In an embodiment, the document editor can view viewer comments about the document, while the viewer cannot view editor comments. In an embodiment, this configuration allows the editor to use the editor chat panel 430 for private communication without revealing the communication to the viewer using the viewer license. This configuration can allow the editor to use the viewer chat panel 435 to view viewer comments. In an embodiment, the editor license association link 410 can allow the editor and / or client devices to submit input messages and / or user messages to the editor chat panel 430 and the viewer chat panel 435. In this configuration, a client device using the editor license association link 410 can use the viewer license association link 415 to send communications to the client device.
[0082] In the embodiments, although Figure 4A Editor chat panel 430 and viewer chat panel 435 are displayed, but the editor-enabled GUI 400 can display more than one copy of editor chat panel 430 and viewer chat panel 435. For example, a document generation system can instantiate multiple editor chat panels and / or group users of editor license association link 410 into different chat panel categories. In an embodiment, a user subscribed to a chat panel can communicate with other users who have also subscribed to the same chat panel. In an embodiment, viewer chat panel 435 can also be split into multiple viewer chat panels 435. A user accessing viewer license association link 415 can be grouped with other users of viewer license association link 415. In an embodiment, a user accessing editor license association link 410 can also view one or more viewer chat panels 435.
[0083] Figure 5 This is an exemplary computer system 500 for implementing various embodiments. For example, one or more computer systems (such as...) can be used. Figure 5 Various embodiments of this disclosure can be implemented using the computer system 500 shown. For example, one or more computer systems 500 (or portions thereof) may be used to implement it. Figure 1 and Figure 2 The document generation system 110 and / or 210.
[0084] Computer system 500 can be any well-known computer capable of performing the functions described herein.
[0085] Computer system 500 includes one or more processors (also called central processing units or CPUs), such as processor 504. Processor 504 is connected to communication infrastructure or bus 506.
[0086] One or more processors 504 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor designed to process dedicated electronic circuitry for mathematically intensive applications. The GPU may have a parallel architecture, which is efficient for parallel processing of large blocks of data, such as mathematically intensive data commonly used in computer graphics applications, images, and videos.
[0087] The computer system 500 also includes user input / output devices 503, such as monitors, keyboards, and indicator devices, that communicate with the communication infrastructure 506 through a user input / output interface 502.
[0088] Computer system 500 also includes main or primary memory 508, such as random access memory (RAM). Main memory 508 may include one or more levels of cache. Control logic (i.e., computer software) and / or data are already stored in main memory 508.
[0089] The computer system 500 may also include one or more auxiliary storage devices or memories 510. Auxiliary memory 510 may include, for example, a hard disk drive 512 and / or a removable storage device or drive 514. The removable storage drive 514 may be a floppy disk drive, magnetic tape drive, optical disc drive, optical storage device, magnetic tape backup device, and / or any other storage device / drive.
[0090] The removable storage driver 514 can interact with the removable storage unit 518. The removable storage unit 518 includes a computer-usable or readable storage device on which computer software (control logic) and / or data are stored. The removable storage unit 518 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disc, and / or any other computer data storage device. The removable storage driver 514 reads from and / or writes to the removable storage unit 518 in a well-known manner.
[0091] According to an exemplary embodiment, auxiliary storage 510 may include other means, methods, or approaches for allowing computer system 500 to access computer programs and / or other instructions and / or data. Such means, methods, or approaches may include, for example, removable storage unit 522 and interface 520. Examples of removable storage unit 522 and interface 520 may include a program box and box interface (such as an interface found in video game devices), a removable storage chip (such as EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.
[0092] Computer system 500 may further include a communication or network interface 524. Communication interface 524 enables computer system 500 to communicate with and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and commonly referred to by reference numeral 528). For example, communication interface 524 may allow computer system 500 to communicate with remote device 528 via communication path 526, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic and / or data may be sent to and from computer system 500 via communication path 526.
[0093] In embodiments, tangible devices or articles of manufacture including tangible computer-usable or readable media on which control logic (software) is stored are also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 500, main memory 508, auxiliary memory 510, and removable storage units 518 and 522, as well as tangible articles embodying any combination thereof. When executed by one or more data processing devices (such as computer system 500), this control logic causes such data processing devices to operate as described herein.
[0094] Based on the teachings contained in this disclosure, how to use different Figure 5 The data processing apparatus, computer system, and / or computer architecture illustrated in the embodiments will be readily apparent to those skilled in the art. Specifically, the embodiments may be implemented using software, hardware, and / or operating system methods other than those described herein.
[0095] It should be recognized that the detailed description section, rather than the abstract section, is intended to be used to interpret the claims. The abstract section may set forth one or more, but not all, exemplary embodiments conceived by the inventors, and is therefore not intended to limit this disclosure or the appended claims in any way.
[0096] While this disclosure has been described herein with reference to exemplary embodiments for illustrative fields and applications, it should be understood that the scope of this disclosure is not limited thereto. Other embodiments and modifications thereof are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and / or entities illustrated in the drawings and / or described herein. Furthermore, embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond those described herein.
[0097] The embodiments are described herein using functional building blocks that illustrate the implementation of specific functions and their relationships. For ease of description, the boundaries of these functional building blocks are arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are properly performed. Moreover, alternative embodiments may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.
[0098] References to "an embodiment," "embodiment," "exemplary embodiment," or similar phrases herein indicate that the described embodiment may include specific features, structures, or characteristics, but each embodiment may not necessarily include those specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. In addition, when a specific feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art may incorporate such feature, structure, or characteristic into other embodiments, whether or not it is expressly mentioned or described herein.
[0099] The breadth and scope of the disclosed invention should not be limited by any of the exemplary embodiments described above, but should be defined solely by the appended claims and their equivalents.
Claims
1. A system comprising: Memory; and One or more processors, coupled to the memory, are configured to perform operations including: Receive a request from the client device to access the document associated with the link, where: The link contains an embedded license that allows the client device to access the document; The license includes a first access license and a second access license that is different from the first access license; The first access permission includes displaying a first chat panel and a second chat panel, the first chat panel including a first comment on the document, and the second chat panel including a second comment on the document; and The second access permission includes hiding the first chat panel and showing the second chat panel; and In response to receiving the request to access the document associated with the link: In response to the link having the first access permission, the document is displayed on the client device, along with a first chat panel and a second chat panel associated with the document, wherein the first chat panel includes at least one of user messages associated with the document or edits made to the document; and In response to the link having the second access permission, the document is displayed on the client device while the first chat panel is hidden and the second chat panel is displayed.
2. The system according to claim 1, wherein the operation further includes: In response to the link having a third access permission different from the first and second access permissions, the document and a plurality of chat panels associated with the document are simultaneously displayed on the client device, wherein the plurality of chat panels include the first chat panel.
3. The system according to claim 1, wherein the operation further includes: Comments on the document are received from a user with the first access permission via the first chat panel; and The comments are stored in the database.
4. The system according to claim 3, wherein the operation further includes: A notification is generated in response to receiving the comment.
5. The system according to claim 1, wherein the operation further comprises: In response to the link having the first access permission, permission to edit the document is granted.
6. The system of claim 5, wherein the operation further comprises: Receive editing of the document from a user with the first access permission; and The edits are stored in the database.
7. A non-transitory computer-readable device storing instructions that, when executed by at least one computing device, cause the at least one computing device to perform an operation, the operation comprising: Receive a request from the client device to access the document associated with the link, where: The link contains an embedded license that allows the client device to access the document; The license includes a first access license and a second access license that is different from the first access license; The first access permission includes displaying a first chat panel and a second chat panel, the first chat panel including a first comment on the document, and the second chat panel including a second comment on the document; and The second access permission includes hiding the first chat panel and showing the second chat panel; and In response to receiving the request to access the document associated with the link: In response to the link having the first access permission, the document is displayed on the client device, along with a first chat panel and a second chat panel associated with the document, wherein the first chat panel includes at least one of user messages associated with the document or edits made to the document; and In response to the link having the second access permission, the document is displayed on the client device while the first chat panel is hidden and the second chat panel is displayed.
8. The non-transitory computer-readable device of claim 7, wherein the operation further comprises: In response to the link having a third access permission different from the first and second access permissions, the document and a plurality of chat panels associated with the document are simultaneously displayed on the client device, wherein the plurality of chat panels include the first chat panel.
9. The non-transitory computer-readable device of claim 7, further comprising: Comments on the document are received from a client device with the first access permission via the first chat panel; and The comments are stored in the database.
10. The non-transitory computer-readable device of claim 9, wherein the operation further comprises: A notification is generated in response to receiving the comment.
11. The non-transitory computer-readable device of claim 7, wherein the operation further comprises: In response to the link having the first access permission, permission to edit the document is granted.
12. The non-transitory computer-readable device of claim 11, further comprising: Receive editing of the document from a client device that has the first access permission; and The edits are stored in the database.
13. The non-transitory computer-readable device of claim 7, wherein the operation further comprises: Receive a request to convert the license of the link from the first access license to the second access license or from the second access license to the first access license.
14. A computer-implemented method, comprising: Receive a request from the client device to access the document associated with the link, where: The link contains an embedded license that allows the client device to access the document; The license includes a first access license and a second access license that is different from the first access license; The first access permission includes displaying a first chat panel and a second chat panel, the first chat panel including a first comment on the document, and the second chat panel including a second comment on the document; and The second access permission includes hiding the first chat panel and showing the second chat panel; and In response to receiving the request to access the document associated with the link: In response to the link having the first access permission, the document is displayed on the client device, along with a first chat panel and a second chat panel associated with the document, wherein the first chat panel includes at least one of user messages associated with the document or edits made to the document; and In response to the link having the second access permission, the document is displayed on the client device while the first chat panel is hidden and the second chat panel is displayed.
15. The computer-implemented method of claim 14, wherein the method further comprises: In response to the link having a third access permission different from the first and second access permissions, the document and a plurality of chat panels associated with the document are simultaneously displayed on the client device, wherein the plurality of chat panels include the first chat panel.
16. The computer-implemented method according to claim 14, further comprising: Comments on the document are received from a client device with the first access permission via the first chat panel; and The comments are stored in the database.
17. The computer-implemented method according to claim 16, further comprising: A notification is generated in response to receiving the comment.
18. The computer-implemented method according to claim 14, further comprising: In response to the link having the first access permission, permission to edit the document is granted.
19. The computer-implemented method according to claim 18, further comprising: Receive editing of the document from a client device that has the first access permission; And store the edits in the database.
20. The computer-implemented method according to claim 14, further comprising: Receive a request to convert the license of the link from the first access license to the second access license or from the second access license to the first access license.
Citation Information
Patent Citations
Automatic layout engine
US11036914B2
Smart Defaults Based on Previous Settings for Presentation Slides
US20190005010A1
Color Theme Maintenance for Presentations
US20190005016A1
Presentation Collaboration with Various Electronic Devices
US20190005694A1
Global link providing modification rights to a shared folder
US20140067865A1
