CN117749401A

CN117749401A - System and method for collaborative protocol signing

Info

Publication number: CN117749401A
Application number: CN202310829036.XA
Authority: CN
Inventors: N·A·斯特拉顿; J·芒西; T·H·阮; P·A·埃珀特
Original assignee: Adobe Systems Inc
Current assignee: Adobe Inc
Priority date: 2022-09-22
Filing date: 2023-07-07
Publication date: 2024-03-22

Abstract

Systems and methods for collaborative document signing are described. According to one aspect, a method for collaborative document signing includes initiating a real-time communication session including a user, identifying a source document for a protocol using a protocol signing interface of the real-time communication session, assigning the user as a signer of the protocol using the protocol signing interface, and generating the protocol. In some cases, the protocol includes a source document. The method also includes obtaining a signature for the protocol from the user and generating a signed protocol including the signature.

Description

System and method for collaborative protocol signing

Cross Reference to Related Applications

The present application claims priority from U.S. patent and trademark office filed U.S. provisional application No. 63/376,613 at month 22 of 2022, 35u.s.c. ≡119, the disclosure of which is incorporated herein by reference in its entirety.

Background

The following relates generally to document generation and, more particularly, to generation of signed documents. The document may be generated using document generation software. For example, document generation software may be used to create a tabular document that includes digital content (such as paragraphs of text). In some cases, the content of the document is provided by the user, and in other cases, the content is derived from a database and corresponds to the type of document generated.

In some cases, the document generation software may collect a signature (such as an electronic signature) from the user that indicates that the user has signed the contents of the form document. In some cases, the document generation software creates a signed document that includes the contents of the form document and the signature of the user. The signed document may be shared with the signing user and other users using digital communication channels (such as email, websites, file sharing services, etc.).

Disclosure of Invention

Aspects of the present disclosure provide collaborative protocol signing via a protocol signing interface displayed in a user interface of a real-time communication session. In some cases, the document generation interface allows a user to identify another user as a signer of the protocol and to identify a source document for the protocol. Based on the identity of the user and the source document, aspects of the present disclosure initiate a signing session during which a protocol is generated based on information collected via a protocol signing interface and a signed protocol is generated that includes the signatures of other users. Thus, aspects of the present disclosure simplify creation of signed protocols within a single real-time communication session by utilizing a protocol signing interface to gather information about the protocol to be signed and the signer of the protocol.

A method, apparatus, non-transitory computer readable medium, and system for non-limiting are described. One or more aspects of the methods, apparatus, non-transitory computer-readable media, and systems include initiating a real-time communication session including a user; identifying a source document for the protocol using a protocol signature interface of the real-time communication session; using a protocol signing interface to assign a user as a signer of a protocol; generating a protocol, wherein the protocol includes a source document; obtaining a signature for a protocol from a user; and generating a signed protocol comprising the signature.

Drawings

Fig. 1 illustrates an example of a protocol signature system in accordance with aspects of the present disclosure.

Fig. 2 illustrates an example of a method for signing a protocol in a real-time communication session in accordance with aspects of the present disclosure.

Fig. 3 illustrates an example of a protocol signing device in accordance with aspects of the present disclosure.

Fig. 4 illustrates an example of a method for generating a signed protocol in accordance with aspects of the present disclosure.

FIG. 5 illustrates an example of a document template list in accordance with aspects of the present disclosure.

Fig. 6 illustrates an example of a protocol signature interface in accordance with aspects of the present disclosure.

Fig. 7 illustrates an example of a signature session summary in accordance with aspects of the present disclosure.

Fig. 8 illustrates an example of a computing device for protocol signing in accordance with aspects of the present disclosure.

Detailed Description

The following relates generally to document generation and, more particularly, to generation of signed documents. Document generation software may be used to generate documents (such as contracts, agreements, insurance policies, etc.) that require signing and share them with signers of the documents via digital communication channels (such as emails, websites, cloud storage, etc.).

In some cases, a signer of a document may participate in a meeting regarding the document to be signed. For example, in a meeting such as a video conference, it is not unusual for a document to need to be signed by the participants of the meeting before any additional discussion can continue. For example, non-public agreements may need to be signed before new product releases are discussed, or I-9 documents may need to be filled out and signed before hired offers can be expanded.

In some cases, a document drafter may create a document in a document drafter application and may share links to the created document in a meeting. However, conventional document generation techniques do not provide the ability to select information for generating a document to be signed in a user interface of a meeting. Without the ability to create a document within a meeting, a conference moderator must change the point of interest from the user interface of the meeting to other software, create the document, and then return to the user interface of the meeting to initiate the online signing process.

Accordingly, one aspect of the present disclosure provides a system for identifying attendees of a real-time conference (such as a video conference, an audio conference, a text-based conference, etc.) as signers of a document, and preparing a data object for the attendees, the data object including the document and to accept the signature of the attendees.

For example, the system provides a user interface that directs a moderator of the meeting by selecting a document template that provides the contents of the data object, and selecting attendees as the intended signer of the document. The system confirms the identity of the attendees by checking the credentials that the attendees provide to log into the real-time meeting. The system then generates a data object to include the content of the document template selected by the moderator and accept a set of form fields that include the attendee's name and the value of the corresponding signature.

After the system generates the data object, the user interface allows the moderator to begin the signing process during which the moderator and attendees can review and discuss documents in the user interface of the meeting and the system gathers the attendees' signatures. The system adds the signature as a value for a corresponding table field in the data object and then generates a signed data object that includes the document and the signature. The system thus provides information that verifies that the attendees have signed the document. The system may generate a representation of the signed document based on the signed data object that visually connects the signed representation of the attendee with a representation of the content of the document.

In the collaboration protocol signature context, an example use of the present disclosure is to generate data objects including documents during a video conference and accept signatures for the documents. For example, the moderator and attendees are participating in a video conference initiated using the system, and the moderator determines that the attendees must sign a non-public agreement (NDA) before the discussion can continue. The system provides a user interface that allows the moderator to select an NDA template from a list of document templates and identify attendees as the intended signer for the NDA. The system assigns attendees as signers for the NDA based on retrieving email addresses that the attendees use to log into the video conference.

After the system confirms that the attendees are the intended signers of the document, the system generates a data object comprising the content of the NDA and a form field accepting a value equal to the attendee's name and the attendee's electronic signature. In response to input from the moderator, the system initiates a signing process during which the user interface of the conference displays the content of the NDA so that the moderator and attendees can discuss the content, and during which the data object accepts the signature of the attendee for the NDA. The system generates a signed data object by populating the relevant form field with the received signature, thereby verifying that the attendees have signed the NDA and allowing the moderator and attendees to continue discussion. The system may use the signed data object to generate a representation of the signed NDA, the representation of the signed NDA including text of the NDA, the name of the attendee, and a representation of the attendee's signature.

According to some aspects, a protocol signing system is provided that includes a communication component, a signing component, an integration component, and a protocol generation component. In some cases, the communication component initiates a real-time communication session that includes the user. In some cases, the signing component displays a protocol signing interface for the document in a user interface of the real-time communication session and identifies the user as a signer of the document. In some cases, the integration component obtains a signature for the document from the user via a protocol signature interface. In some cases, the protocol generation component generates a signed document that includes the signature.

According to some aspects, the real-time communication session is a segment of real-time or near real-time communication provided via a software application associated with the GUI. According to some aspects, the software application is a communication component. Thus, examples of real-time communication sessions include video conferences, audio conferences, text-based chat sessions, and the like associated with a GUI of a computing device.

By utilizing the user interface of the conference to obtain information about the protocol to be signed and the intended signer of the protocol, the system simplifies creation of the signed protocol within a single real-time conference, thus avoiding the cumbersome process of switching from the user interface of the real-time conference to another user interface of external software to generate the protocol for signing.

Further example applications of the present disclosure are provided with reference to fig. 1 and 2 in the context of collaborative protocol signing. Details regarding the architecture of the system are provided with reference to fig. 1, 3 and 8. Examples of processes for collaborative protocol signing are provided with reference to fig. 2 and 4-7.

Document signing system

Fig. 1 illustrates an example of a protocol signature system 100 in accordance with aspects of the present disclosure. The illustrated example includes a first user 105, a first user device 110, a second user 115, a second user device 120, a protocol signing device 125, a cloud 130, and a database 135. The protocol signing device 125 is an example of, or includes aspects of, the corresponding elements described with reference to fig. 3.

Referring to fig. 1, according to some aspects, a protocol signing device 125 initiates a real-time communication session comprising a first user 105 and a second user 115 and displays a protocol signing interface to the second user 115 in a user interface of the real-time communication session.

As used herein, a "protocol" is a data structure that includes a document (or template document), a set of fields, values corresponding to fields, a list of signers, a set of signatures, or any combination thereof. In some examples, the protocol may be generated during a real-time communication session.

As used herein, a "real-time communication session" is a segment of real-time or near real-time communication. According to some aspects, real-time or near real-time communication includes the exchange of data between one or more computing devices via a communication component of the computing device (including hardware, firmware, software, or a combination thereof) and according to a communication protocol. Examples of real-time or near real-time communications include the exchange of video, audio, and text data, or a combination thereof.

In some cases, the second user 115 is a moderator of the signing session during which the signed protocol was generated. According to some aspects, the protocol signing device 125 identifies the protocol to be signed via input provided by the second user 115 to the protocol signing interface and identifies the first user 105 as the signer of the protocol. According to some aspects, in response to the identification, the protocol signing device 125 initiates a signing session, generates a protocol to be signed, and prompts the user 105 to confirm their identity and sign the protocol. According to some aspects, after receiving the signature from the first user 105, the protocol signing device 125 generates a signed protocol, including the protocol, the name of the signer of the protocol, and the signature of the signer of the protocol, and ends the signing session.

According to some aspects, each of the first user device 110 and the second user device 120 is a personal computer, a laptop computer, a mainframe computer, a palmtop computer, a personal assistant, a mobile device, or any other suitable processing device. In some examples, as described with reference to fig. 5, each of the first user device 110 and the second user device 120 includes software that allows the first user 105 and the second user 115 to provide input to view a user interface of a real-time communication session and to provide input to the user interface, respectively.

According to some aspects, the user interface enables the first user 105 and the second user 115 to interact with the first user device 110 and the second user device 120, respectively. In some aspects, each of the user interfaces may include an audio device such as an external speaker system, an external display device such as a display screen, or an input device (e.g., a remote control device that interfaces with the user interface directly or through an I/O controller module). In some cases, the user interface may be a user graphical interface (GUI). According to some aspects, a user interface is included in the protocol signature apparatus 125, and the first user 105 and/or the second user 115 interact directly with the protocol signature apparatus 125 via the user interface. According to some aspects, the user interface is provided by the protocol signing device 125 via the first user equipment 110 and the second user equipment 120, and the first user 105 and the second user 115 interact with the protocol signing device 125 via the user interface.

According to some aspects, the protocol signing device 125 comprises a computer implemented network. In some aspects, the protocol signing device 125 further includes one or more processors, a memory subsystem, a communication interface, an I/O interface, one or more user interface components, and a bus. In some aspects, the protocol signature apparatus 125 communicates with the first user device 110, the second user device 120, the database 135, or a combination thereof via the cloud 130.

In some cases, the protocol signing device 125 is implemented on a server. The server provides one or more functions to users linked by way of one or more of the various networks (e.g., cloud 130). In some cases, the server comprises a single microprocessor board that includes a microprocessor responsible for controlling all aspects of the server. In some cases, the server uses microprocessors and protocols to exchange data with other devices/users via hypertext transfer protocol (HTTP) and Simple Mail Transfer Protocol (SMTP) over one or more of the networks, but other protocols such as File Transfer Protocol (FTP) and Simple Network Management Protocol (SNMP) may also be used. In some cases, the server is configured to send and receive hypertext token language (HTML) formatted files (e.g., for displaying web pages). In various embodiments, the server comprises a general purpose computing device, a personal computer, a laptop computer, a mainframe computer, a supercomputer, or any other suitable processing apparatus. The protocol signing device 125 is an example of, or includes aspects of, the corresponding elements described with reference to fig. 2 and/or 3.

Further details regarding the architecture of the protocol signing device 125 are provided with reference to fig. 3 and 8. Further details regarding the process for collaborative protocol signing are provided with reference to fig. 2 and 4-7.

According to some aspects, cloud 130 is a computer network, such as data storage and computing capabilities, configured to provide on-demand availability of computer system resources. In some examples, cloud 130 provides resources without active management from the user. The term "cloud" is sometimes used to describe a data center that is available to many users over the internet. Some large cloud networks have functionality that is distributed across multiple locations from a central server. If a server has a direct or close connection to a user, the server is designated as an edge server. In some cases, the cloud 130 is limited to a single organization. In other examples, the cloud 130 is available to many organizations. In one example, cloud 130 includes a multi-layer communication network that includes a plurality of edge routers and core routers. In another example, cloud 130 is based on a local set of switches in a single physical location. According to some aspects, the cloud 130 provides communication between the first user device 110, the second user device 120, the protocol signing device 125, the database 135, and combinations thereof.

According to some aspects, database 135 is an organized collection of data. For example, database 135 stores data in a particular format called schema (schema). Database 135 may be constructed as a single database, a distributed database, a multi-distributed database, or an emergency backup database. In some cases, the database controller may manage the data stored and processed in the database 135. In some cases, the first user 105 and/or the second user 115 interact with a database controller. In other cases, the database controller operates automatically without user interaction. According to some aspects, as described with reference to fig. 5, database 135 stores a list of document templates, source documents to which the list of document templates corresponds, signature session summaries, user display names, user identifiers, signature session contexts, context tokens, protocols, signature inputs, signatures associated with signature inputs, signed protocols, or combinations thereof. In some aspects, the database 135 is external to the protocol signature apparatus 125 and communicates with the protocol signature apparatus 125 via the cloud 130. In some aspects, the database 135 is included in the protocol signing device 125.

Fig. 2 illustrates an example of a method 200 for signing a protocol in a real-time communication session in accordance with aspects of the present disclosure. In some examples, these operations are performed by a system comprising a processor executing a set of codes to control functional elements of a device. Additionally or alternatively, certain processes are performed using special purpose hardware. Generally, these operations are performed according to methods and processes described in accordance with aspects of the present disclosure. In some cases, the operations described herein consist of various sub-steps, or are performed in conjunction with other operations.

Referring to fig. 2, the system initiates a real-time communication session and displays a protocol signature interface to a second user of the real-time communication session, such as a moderator of the signature session. In some cases, a protocol signing interface facilitates identification of a protocol and allocation of a first user signer of the protocol and is used to initiate a signing session during which the signed protocol is generated.

In some examples, a "protocol" is a data structure that includes a document (or template document), a set of fields, values corresponding to fields, a list of signers, a set of signatures, or any combination thereof. In some examples, the protocol may be generated during a real-time communication session based on teleconferencing software. The document signing service may be integrated into teleconferencing software and may be used to generate protocols and sign protocols during real-time communication sessions. For example, a signing process or ceremony initiated by the signing service may be performed within a real-time communication session of the teleconferencing software. Once all of the signatures are collected for the list of signers, the protocol may be considered signed or closed. In some cases, a signed or closed protocol (i.e., signed document) is generated during a real-time communication session by identifying a document, setting a value (optional) for a field, identifying or selecting a list of signers, and by obtaining a signature from a signer.

At operation 205, the system displays a protocol signature interface for the protocol in the real-time communication session. In some cases, the operations of this step refer to or may be performed by a protocol signing device as described with reference to fig. 1 and 3. In some cases, as described with reference to fig. 4, the protocol signing device displays a protocol signing interface for the protocol in a real-time communication session.

At operation 210, the second user identifies a source document and a signer for the protocol based on the protocol signing interface. In some cases, the operations of this step refer to or may be performed by a second user as described with reference to fig. 1. In some cases, as described with reference to fig. 4, a second user (e.g., a moderator of a signature session) identifies a source document for a protocol and assigns a first user as a signer of the protocol based on a protocol signature interface.

At operation 215, the first user provides a signature for the protocol. In some cases, the operations of this step refer to or may be performed by a first user as described with reference to fig. 1. In some cases, the first user provides a signature for the protocol as described with reference to fig. 4.

At operation 220, the system generates a signed protocol that includes the signature. In some cases, the operations of this step refer to or may be performed by a protocol signing device as described with reference to fig. 1 and 3. In some cases, the system generates a signed protocol that includes the signature based on the protocol, as described with reference to fig. 4.

Fig. 3 illustrates an example of a protocol signing device in accordance with aspects of the present disclosure. The protocol signature apparatus 300 is an example of, or includes aspects of, the corresponding elements described with reference to fig. 1.

In one aspect, the protocol signing device 300 includes a processor unit 305, a memory unit 310, a communication component 315, a signing component 320, an integration component 325, and a protocol generation component 330. According to some aspects, the protocol signature apparatus is, or includes aspects of, an example of a computing device as described with reference to fig. 8. For example, in some cases, the communication component 315, the integration component 325, and the protocol generation component 330 are implemented as hardware circuitry that interacts with components similar to those illustrated in fig. 8 via channels. For example, in some cases, the communication component 315, the signature component 320, the integration component 325, and the protocol generation component 330 are implemented as software stored in a memory device.

The processor unit 305 includes one or more processors. The processing unit 305 is a smart hardware device (e.g., a general purpose processing component, a Digital Signal Processor (DSP), a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor unit 305 is configured to operate the memory array using a memory controller. In other cases, the memory controller is integrated in the processor unit 305. In some cases, the processor unit 305 is configured to execute computer-readable instructions stored in the memory unit 310 to perform various functions. In some aspects, the processor unit 305 includes special purpose components for modem processing, baseband processing, digital signal processing, or transmission processing.

Memory unit 310 includes one or more memory devices. Examples of memory unit 310 include Random Access Memory (RAM), read Only Memory (ROM), or a hard disk. Examples of memory unit 310 include solid state memory and hard drives. In some examples, memory unit 310 is used to store computer readable, computer executable software comprising instructions that, when executed, cause a processor of processor unit 305 to perform the various functions described herein. In some cases, memory unit 310 includes a basic input/output system (BIOS) that controls basic hardware or software operations, such as interactions with peripheral components or devices. In some cases, memory unit 310 includes a memory controller that operates the memory cells of memory unit 310. For example, the memory controller may include a row decoder, a column decoder, or both. In some cases, memory cells within memory cell 310 store information in the form of logical states.

According to some aspects, the communication component 315 initiates a real-time communication session that includes a user. According to some aspects, the communication component 315 is implemented as software, firmware, one or more hardware circuits, or a combination thereof, stored in the memory unit 310 and executable by the processor unit 305.

According to some aspects, the signature component 320 uses a protocol signature interface of a real-time communication session to identify a source document for a protocol. In some examples, the signing component 320 assigns users as signers of the protocol using a protocol signing interface.

In some examples, the signature component 320 displays a list of document templates in a protocol signature interface of the real-time communication session, wherein the source document is identified based on the list of document templates. In some aspects, the document template list includes a representation of the source document. In some examples, the signing component 320 selects a protocol for signing based on the representation of the source document.

In some examples, the signature component 320 authenticates the user based on the user identifier. In some examples, in response to authentication, the signature component 320 includes the user identifier in a user identifier field of the protocol signature interface. In some examples, the signature component 320 determines that the user is not authenticated. In some examples, the signing component 320 displays a request to provide a user identifier for the user in a protocol signing interface.

In some examples, the signing component 320 displays a summary of the signing session within the protocol signing interface, wherein the summary includes the user identifier and a representation of the source document. In some examples, the signature component 320 initiates a signature session during which a signature is obtained. In some examples, the signature component 320 displays an indication that the signed protocol includes a signature in a user interface of the real-time communication session.

According to some aspects, signature component 320 is implemented as software, firmware, one or more hardware circuits, or a combination thereof, stored in memory unit 310 and executable by processor unit 305.

According to some aspects, the integration component 325 generates a protocol, wherein the protocol includes a source document. In some examples, the integration component 325 obtains a signature for the protocol from the user. In some examples, the integration component 325 generates a signing session context for the signing session, wherein the signed protocol is based on the signing session context.

According to some aspects, the integration component 325 is implemented as software, firmware, one or more hardware circuits, or a combination thereof, stored in the memory unit 310 and executable by the processor unit 305.

According to some aspects, the protocol generation component 330 generates a signed protocol that includes a signature. According to some aspects, the protocol generation component 330 is implemented as software, firmware, one or more hardware circuits, or a combination thereof, stored in the memory unit 310 and executable by the processor unit 305.

According to some aspects, the protocol signing apparatus 300 is implemented as a computing device, such as the computing device described with reference to fig. 8, and the communication component 315, the signing component 320, the integration component 325, the protocol generation component 330, or a combination thereof is implemented as one or more software applications stored in the memory unit 310 and executable by the processor unit 305. For example, in some cases, the communication component 315, the signature component 320, the integration component 325, the protocol generation component 330, or a combination thereof is implemented as a protocol signature application stored in the memory unit 310 and executable by the processor unit 305.

According to some aspects, the protocol signing apparatus 300 is implemented as one or more servers, such as the servers described with reference to fig. 1, and the communication component 315, the signing component 320, the integration component 325, the protocol generation component 330, or a combination thereof is implemented as one or more servers configured to communicate with each other, such as through a cloud as described with reference to fig. 1, and through one or more communication protocols. In some cases, the communication component 315, the signature component 320, the integration component 325, the protocol generation component 330, or a combination thereof communicates with each other via API calls. According to some aspects, the integration component 325 is implemented as an integration server. According to some aspects, the integration server is external to the protocol signature apparatus 300.

Collaborative protocol signature

A method for collaborative protocol signing is described with reference to fig. 4-7. One or more aspects of the method include initiating a real-time communication session including a user; identifying a source document for the protocol using a protocol signature interface of the real-time communication session; using a protocol signing interface to assign a user as a signer of a protocol; generating a protocol, wherein the protocol includes a source document; obtaining a signature for a protocol from a user; and generating a signed protocol comprising the signature.

Some examples of the method further include displaying a list of document templates in a protocol signature interface of the real-time communication session, wherein the source document is identified based on the list of document templates. In some aspects, the document template list includes a representation of the source document. Some examples of the method further include selecting a protocol for signing based on the representation of the source document.

Some examples of the method further include authenticating the user based on the user identifier. Some examples also include including a user identifier in a user identifier field of the protocol signature interface in response to the authentication. Some examples of the method further include determining that the user is not authenticated. Some examples also include displaying, in the protocol signature interface, a request to provide a user identifier for the user.

Some examples of the method further include displaying a summary of the signature session within the protocol signature interface, wherein the summary includes a representation of the source document and the user identifier. Some examples of the method further include initiating a signature session, wherein the signature is acquired during the signature session. Some examples of the method further include generating a signing session context for the signing session, wherein the signed protocol is based on the signing session context. Some examples of the method further include displaying, in a user interface of the real-time communication session, an indication that the signed protocol includes the signature.

Fig. 4 illustrates an example of a method 400 for generating a signed protocol in accordance with aspects of the present disclosure. In some examples, these operations are performed by a system comprising a processor executing a set of codes to control functional elements of a device. Additionally or alternatively, certain processes are performed using special purpose hardware. Generally, these operations are performed according to methods and processes described in accordance with aspects of the present disclosure. In some cases, the operations described herein consist of various sub-steps, or are performed in conjunction with other operations.

Referring to fig. 4, according to some aspects, a system initiates a real-time communication session and uses a prompt displayed via a protocol signing interface of a user interface of the real-time communication session to obtain information for the signing session and initiate the signing session. According to some aspects, during a signing session, a selected source document is prepared as a protocol for signing by a moderator of the signing session. For example, in some cases, a moderator of the signature session selects a source document for the protocol and assigns users of the real-time communication session as signers of the protocol. As used herein, the term "source document" refers to any data organized as a computer file. Examples of source documents include text files, PDFs, word processing documents, video files, audio files, or any other type of file. As used herein, the term "protocol" refers to an object that is capable of including content (such as content included in a source document) and electronic signatures as data or embedded metadata. In some cases, the protocol includes the content of the source document. In some cases, the protocol includes a table field and a value for the table field.

According to some aspects, when each user assigned as a signer of a protocol signs the protocol, the signing session ends and the signed protocol is generated. According to some aspects, by providing a protocol signing interface for obtaining information for a protocol and initiating a signing session in a user interface of a real-time communication session, the system enables a user to easily prepare a protocol for signing without switching from the user interface of the real-time communication session to a separate user interface of a protocol preparation application or the like.

At operation 405, the system initiates a real-time communication session including the user. In some cases, the operations of this step refer to or may be performed by a communication component as described with reference to fig. 3. According to some aspects, the real-time communication session is a segment of real-time or near real-time communication. According to some aspects, real-time or near real-time communication includes the exchange of data between one or more computing devices via a communication component of the computing device (including hardware, firmware, software, or a combination thereof) and according to a communication protocol. Examples of real-time or near real-time communications include the exchange of video, audio, and text data, or a combination thereof.

According to some aspects, the real-time communication session includes a "moderator". According to some aspects, the moderator is a user prompting the communication component to initiate a real-time communication session, or a user determined to be a moderator during the real-time communication session. According to some aspects, users included in a real-time communication session are identified according to a user identifier. According to some aspects, the user identifier is an identifier, such as an email address, used by the user to log into software associated with a real-time communication session (e.g., a communication component).

According to some aspects, a temporary user identifier is provided by a communication component for a user that is not logged into software associated with a real-time communication session based on, for example, characteristics of a user device associated with the user. According to some aspects, the communication component associates the moderator identifier with a user that is a moderator of the real-time communication session. According to some aspects, as described with reference to fig. 1, the communication component stores the user identifier, the moderator identifier, an association of the user identifier and/or the moderator identifier, or a combination thereof, in a database.

At operation 410, the system identifies a source document for the protocol using a protocol signature interface of the real-time communication session. In some cases, the operations of this step refer to or may be performed by a signature component as described with reference to fig. 3. For example, according to some aspects, a signing component receives a protocol signature initiation input and displays a protocol signature interface in response to the protocol signature initiation input.

According to some aspects, a user of a real-time communication session provides a protocol signature initiation input to a user interface of the real-time communication session (e.g., a GUI provided by a software application associated with the real-time communication session, such as a communication component), and the GUI provides the protocol signature initiation input to the user in response to the protocol signature initiation input. According to some aspects, in response to receiving the protocol signature initiation input, the signature component displays a protocol signature interface in a user interface of the real-time communication session. As an example, in some cases, a protocol signing interface may be triggered from a user interface of a real-time communication session to initiate a process of displaying the protocol signing interface to a moderator of the signing session. According to some aspects, the signing component identifies a user providing protocol signature initiation input as a moderator of the signing session.

According to some aspects, information displayed in a protocol signing interface (e.g., dialog) directs a moderator of a signing session through the configuration of the signing session.

According to some aspects, the signing component displays a list of document templates in a protocol signing interface of the real-time communication session. According to some aspects, the document template list includes a representation of the source document. According to some aspects, the representation of the source document is a thumbnail representation of the source document. According to some aspects, the signing component obtains a list of document templates (e.g., from the database described with reference to fig. 1) using a user identifier or other credential of a moderator of the signing session.

According to some aspects, the signing component selects a protocol for signing based on the representation of the source document. For example, a moderator of the signing session may select a source document for a protocol by providing a selection input to the protocol signing interface to select a representation of the source document from the document template list, and the signing component selects a protocol corresponding to the selected source document. According to some aspects, as described with reference to FIG. 1, a list of document templates, source documents associated with the list of document templates, and representations of the source documents are stored in a database. An example of a protocol signature interface including a list of document templates is illustrated in FIG. 5.

At operation 415, the system uses the protocol signing interface to assign the user as a signer of the protocol. In some cases, the operations of this step refer to or may be performed by a signature component as described with reference to fig. 3. For example, in response to selecting the representation of the source document, the signing component provides a request in the protocol signing interface for a moderator of the signing session for the user to be assigned as a signer of the protocol, in accordance with some aspects. According to some aspects, the signing component displays a user name associated with a user of the real-time communication session in a protocol signing interface, a moderator of the signing session can select the user as a signer of the protocol, and in response to the selection, the signing component assigns the user as a signer of the protocol.

According to some aspects, the signing component authenticates the user based on the user identifier and, in response to the authentication, includes the user identifier in a user identifier field of the protocol signing interface. According to some aspects, the signing component determines that the user is not authenticated and displays a request to provide a user identifier for the user in a protocol signing interface.

For example, according to some aspects, if a user has been authenticated into a real-time communication session via a login with a user identifier (such as an email address, etc.), the signing component authenticates the user and automatically populates the user identifier field of the protocol signing interface with the user identifier of the user. According to some aspects, if the user has not been authenticated into the real-time communication session by the communication component, the signature component prompts the moderator via the protocol signature interface to enter a valid user identification for the user. An example of a protocol signature interface including a user name and a user identifier is illustrated in fig. 6.

According to some aspects, a message displayed in a protocol signing interface (such as a conversation) includes a request to select a user to sign a protocol. For example, in some cases, the message includes a drop-down control that includes a list of users of the real-time communication session. In some cases, the signature component uses an API associated with the real-time communication session to obtain a list of users and returns a user display name, a unique identifier for the user, and a user identifier for the user, such as an email address (if the user is authenticated into the real-time communication session). According to some aspects, upon selection of a user by a moderator of a signing session, if a user identifier for the user is available to the signing component, the signing component automatically populates the user identifier field of the message. According to some aspects, if the user is not authenticated into the real-time communication session, the moderator of the signature session may manually enter the user identifier of the user into the message.

At operation 420, the system generates a protocol, wherein the protocol includes the source document. In some cases, the operations of this step refer to or may be performed by an integrated component as described with reference to fig. 3.

According to some aspects, a signing component displays a summary of a signing session within a protocol signing interface, wherein the summary comprises a representation of a source document and a user identifier. According to some aspects, a signing session (e.g., signing ceremony) is a series of processes involving the generation of signed protocols. According to some aspects, the signing component displays a representation of the source document, a name of the source document, a display name of the user, and a user identifier as a summary in a protocol signing interface. An example of a protocol signing interface comprising a summary of a signing session comprising a user name, a user identifier, and a representation of a source document is illustrated in fig. 7.

According to some aspects, a signing component initiates a signing session, wherein a protocol is generated in response to initiating the signing session. For example, according to some aspects, a moderator of a signature session provides a validation input to a portion of a protocol signature interface, and a signature component initiates the signature session in response to the validation input. For example, in some aspects, a moderator of the signing session clicks the confirm button to accept the configuration of the signing session and the signing component initiates the signing session using data associated with the signing session summary (such as the document corresponding to the representation of the source document, the name of the document, the user name, and/or the user identifier).

According to some aspects, the signing component transmits data associated with the signing session summary to the integration component, thereby initiating a signing session. An example of a protocol signature interface including a confirm button is illustrated in fig. 7.

According to some aspects, the signing component closes the protocol signing interface and sends a message (e.g., a chat interface via a user interface of a real-time communication session) to the integration component in response to the confirmation input. According to some aspects, the message includes data associated with a signed session summary, and the integration component uses the data associated with the signed session summary to set the user as a signer of the protocol based on the user identifier. According to some aspects, a message command integration component generates a protocol that includes a source document and one or more form fields corresponding to a message included in a signed session summary.

For example, in some cases, the integration component extracts data associated with the signed session summary from the message and, using the source document and a user identifier of the user selected to sign the document, the integration component generates a protocol such that the protocol includes the content of the source document. In some cases, the protocol includes a table field corresponding to the name of the user associated with the user identifier. In some cases, the protocol includes a table field corresponding to the user identifier. In some cases, the protocol includes a form field corresponding to the signature of the user.

According to some aspects, the integration component generates a signing session context for the signing session, wherein the signed protocol is based on the signing session context. According to some aspects, the signature session context includes state data for coordinating the signature session. According to some aspects, the integration component provides the signature session context to the database as described with reference to fig. 1.

According to some aspects, the state data includes a context token based on an index value retrieved from a database. In some cases, the context token is salted (salt) and encrypted so that it can be passed as an opaque token (e.g., via various API calls associated with the signed session). Encryption is the process of converting data into something that appears random. Decryption is the process of converting encrypted data back to its original form. Symmetric encryption may be used to encrypt large amounts of data. For example, a symmetric key may be used during both the encryption and decryption processes. In some examples, encryption algorithms may be used to make decrypting data as difficult as possible without using a key. In some cases, there may be no significantly better technique than trying each possible key. For such algorithms, the use of longer keys makes decryption of data without keys more difficult. Examples of encryption algorithms include Data Encryption Standard (DES), triple DES, advanced Encryption Standard (AES), asymmetric encryption algorithm (RSA), or Elliptic Curve Cryptography (ECC).

In some cases, at each step of the signature session, an opaque context token is passed through the API to synchronize the signature session with the state of the document. In some cases, the integration component registers a callback with the signing component for events related to a change in state of the document being signed, thereby adding the context token as part of the callback data. In some cases, the context token is decrypted to obtain data from the context token and re-encrypted in each step of the signature session.

At operation 425, the system obtains a signature for the protocol from the user. In some cases, the operations of this step refer to or may be performed by an integrated component as described with reference to fig. 3.

According to some aspects, during a signing session, the integration component provides a message (such as a card in a chat interface) via a user interface of the real-time communication session that invites the identified user to provide censoring input to the user interface to censor and sign the agreement. In some cases, the integration component provides the message via one or more APIs.

In some cases, a portion of the user interface (such as a "command" button) includes a command identifier that indicates that the portion of the user interface is to be used to provide censoring input. In some cases, a context token is included in the message to associate an input to a portion of the user interface (such as a click of a command button) and a command identifier with the signature session. In some cases, each user of the real-time communication session may see the invitation to sign the invitation, but only the identified user may continue the signed session by providing an audit input.

According to some aspects, in response to receiving the censoring input, the integration component displays a message (such as a conversation) to the identified user via the user interface of the real-time communication session prompting the identified user to confirm their identity by providing an accepting input to the user interface. In some cases, in response to another user of the real-time communication session attempting to provide an acceptance input to the user interface, the integrated component displays a message indicating that the other user is not the user identified as the signer.

For example, when the user provides an acceptance input, the integration component checks the identity of the user by comparing the user identifier with the user identifier extracted from the signed session context (e.g., using a context token acquisition). In some cases, if the user matches a user identifier of a user identified as a signer, the integration component displays a request to the user to provide an identity confirmation input to a user interface of the real-time communication session. In some cases, if the user identifier does not match the user identified as the signer of the document, the integration component displays a message to the user informing the user that it is not the selected signer.

According to some aspects, after the integration component receives identity confirmation input via a user interface of the real-time communication session, the integration component instructs the signing component to display the source document to the identified user.

According to some aspects, the signature component displays the source document in a user interface of the real-time communication session. According to some aspects, a signing component displays a source document to an identified user in a web browser (such as a web browser implemented on a user device associated with the identified user). For example, in some cases, after the integration component receives identity confirmation input via a user interface of the real-time communication session, the integration component provides a web link to the identified user, wherein the web link is a link to a signed page that displays the URL correspondence. In some cases, the URL includes a context token for the signing session, where the context token includes a new salt value and indicates the signing step for which the context token is to be used.

According to some aspects, a user provides a link input to a web link, and an integration component receives a request for a signed page in response to the link input. In some cases, when the integration component receives a request for a signed page, the integration component obtains a signed session context using the context token and evaluates the state of the context token with reference to the signed session context. In some cases, the integration component returns an error page to the web browser if the state of the context token is different from the state of the signature session. In some cases, if the signing session context and the context token include compatible states, the integration component uses data from the signing session context to obtain the signing access token and URL, and the URL is returned to the web browser as a redirect response to take the user to the signing page to review and sign the protocol.

According to some aspects, in response to the signature page opening in the web browser, the signature component prompts a user in a user interface of the real-time communication session to share the web browser so that the source document can be discussed.

At operation 430, the system generates a signed protocol that includes the signature. In some cases, the operations of this step refer to or may be performed by a protocol generation component as described with reference to fig. 3.

According to some aspects, in response to the identified user providing signature input in a user interface or web browser of the real-time communication session, the integration component receives signature input for the document from the identified user.

According to some aspects, the integration component receives a callback message in response to the signature input indicating that the user has completed a step in the signature session, and the integration component extracts a context token from the callback message, obtains the signature session context from the database, and obtains the current state of the protocol. If the state of the protocol matches the callback message and the state of the signature session context matches the expected previous step of the signature session, the signature session context is updated to a new state (such as a state indicating that the signature session is complete) and the integration component issues the corresponding message to the user interface of the real-time communication session.

According to some aspects, in response to receiving the signature input, the integration component updates the state of the context token. In some cases, the protocol generation component generates a signed protocol comprising a signature associated with the signature input based on the signature session data and/or the state of the context token received from the integration component. For example, in some cases, the signed protocol includes a protocol, a value equal to the user's name in a form field corresponding to the user's name, a value equal to the user's identifier in a form field corresponding to the user's identifier, a value equal to the signature in a form field corresponding to the user's signature, or a combination thereof.

According to some aspects, the integration component checks the context token and signs the session context to indicate that all users identified as signers have signed the protocol. When each of the identified users has signed the protocol, the integration component issues a corresponding message to the user interface of the real-time communication session and ends the signing session.

According to some aspects, in response to the end of the signing session, the signing component displays a representation of the protocol in a user interface of the real-time communication session. In some cases, the representation of the protocol includes a representation of the content of the source document and any values included in the signed document. For example, in some cases, the representation of the protocol includes a textual representation of the user name, user identifier, signature, or a combination thereof.

FIG. 5 illustrates an example of a document template list in accordance with aspects of the present disclosure. Referring to fig. 5, as described with reference to fig. 4, in some cases, a protocol signature interface 500 is included in a user interface of a real-time communication session and includes a document template list 505.

Fig. 6 illustrates an example of a protocol signature interface in accordance with aspects of the present disclosure. Referring to fig. 6, as described with reference to fig. 4, in some cases, the protocol signature interface 600 includes a menu including a user display name and a user identifier.

Fig. 7 illustrates an example of a signature session summary in accordance with aspects of the present disclosure. Referring to fig. 7, as described with reference to fig. 4, the protocol signing interface 700 includes a signing session summary 705 (including a representation of a source document, a source document name, a user display name, and a user identifier) and a "confirm" button 710 by which a user may provide a confirmation input.

Fig. 8 illustrates an example of a computing device 800 for protocol signing in accordance with aspects of the present disclosure. In one aspect, computing device 800 includes processor(s) 805, memory subsystem 810, communication interface 815, I/O interface 820, user interface component(s) 825, and channel 830.

In some aspects, computing device 800 is an example of, or includes aspects of, protocol signature apparatus 125 of fig. 1. In some cases, computing device 800 includes one or more processors 805, the one or more processors 805 may execute instructions stored in memory subsystem 810 to initiate a real-time communication session including a user; identifying a source document for the protocol using a protocol signature interface of the real-time communication session; using a protocol signing interface to assign a user as a signer of a protocol; generating a protocol, wherein the protocol includes a source document (directly or by reference); obtaining a signature for a protocol from a user; and generating a signed protocol comprising the signature.

According to some aspects, computing device 800 includes one or more processors 805. In some cases, the processor is a smart hardware device (e.g., a general purpose processing component, a Digital Signal Processor (DSP), a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor is configured to operate the memory array using the memory controller. In other cases, the memory controller is integrated in the processor. In some cases, the processor is configured to execute computer-readable instructions stored in the memory to perform various functions. In some aspects, the processor includes special purpose components for modem processing, baseband processing, digital signal processing, or transmission processing.

According to some aspects, memory subsystem 810 includes one or more memory devices. Examples of memory devices include Random Access Memory (RAM), read Only Memory (ROM), or hard disks. Examples of memory devices include solid state memory and hard drives. In some examples, the memory is used to store computer-readable, computer-executable software comprising instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory includes, among other things, a basic input/output system (BIOS) that controls basic hardware or software operations, such as interactions with peripheral components or devices. In some cases, the memory controller operates the memory cells. For example, the memory controller may include a row decoder, a column decoder, or both. In some cases, memory cells within a memory store information in the form of logical states.

In some examples, the communication interface 815 operates at the boundary between a communication entity (e.g., computing device 800, one or more user devices, a cloud, and one or more databases) and channel 830 and may also record and process communications. In some cases, a communication interface is provided to enable a processing system coupled to a transceiver (e.g., a transmitter and/or a receiver). In some examples, the transceiver is configured to transmit (or send) and receive signals for the communication device via the antenna.

According to some aspects, the I/O interface 820 is controlled by an I/O controller to manage input and output signals for the device. In some cases, I/O interface 820 manages peripheral devices that are not integrated into computing device 800. In some cases, I/O interface 820 represents a physical connection to an external peripheral deviceAn interface or port. In some cases, the I/O controller uses an operating system (e.g. Or other known operating systems). In some cases, the I/O controller represents or interacts with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I/O controller is implemented as a component of a processor. In some cases, the user interacts with the device via the I/O interface 820 or via hardware components controlled by the I/O controller.

According to some aspects, user interface component(s) 825 enable a user to interact with computing device 800. In some cases, the user interface component(s) 825 include an audio device such as an external speaker system, an external display device such as a display screen, an input device (e.g., a remote control device that interfaces with the user interface directly or through an I/O controller), or a combination thereof. In some cases, the user interface component(s) 825 include a GUI.

The description and drawings described herein represent example configurations and do not represent all implementations that are within the scope of the claims. For example, operations and steps may be rearranged, combined, or otherwise modified. Furthermore, structures and devices may be shown in block diagram form in order to represent relationships between components and to avoid obscuring the described concepts. Similar components or features may have the same name but may have different reference numbers corresponding to different figures.

Some modifications of the present disclosure will be apparent to those skilled in the art, and the principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The described methods may be implemented or performed by a device that includes a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Thus, the functions described herein may be implemented in hardware or software and may be performed by a processor, firmware, or any combination thereof. If implemented in software for execution by a processor, the functions may be stored on a computer-readable medium in the form of instructions or code.

Computer-readable media include non-transitory computer storage media and communication media including any medium that facilitates transfer of code or data. Non-transitory storage media may be any available media that can be accessed by a computer. For example, a non-transitory computer readable medium may include Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), compact Disk (CD) or other optical disk storage, magnetic disk storage, or any other non-transitory medium for carrying or storing data or code.

Further, the connection components may be properly termed a computer-readable medium. For example, if the code or data is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, or microwave signals, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies are included in the definition of medium. Combinations of media are also included within the scope of computer-readable media.

In this disclosure and the following claims, the word "or" indicates an inclusive list such that, for example, a list of X, Y or Z represents X or Y or Z or XY or XZ or YZ or XYZ. The phrase "based on" is also not used to denote a closed set of conditions. For example, a step described as "based on condition a" may be based on both condition a and condition B. In other words, the phrase "based on" should be construed to mean "based, at least in part, on". Furthermore, the words "a" or "an" mean "at least one".

Claims

1. A method for collaborative document signing, comprising:

initiating a real-time communication session including a user;

identifying a source document for a protocol using a protocol signature interface of the real-time communication session;

generating the protocol during the real-time communication session, wherein the protocol includes the source document;

using the protocol signing interface to assign the user as a signer of the protocol;

obtaining a signature for the protocol from the user; and

a signed protocol is generated that includes the signature.

2. The method of claim 1, further comprising:

a list of document templates is displayed in the protocol signature interface of the real-time communication session, wherein the source document is identified based on the list of document templates.

3. The method according to claim 2, wherein:

the document template list includes a representation of the source document.

4. A method according to claim 3, further comprising:

the protocol for signing is selected based on the representation of the source document.

5. The method of claim 1, further comprising:

authenticating the user based on a user identifier; and

in response to the authentication, the user identifier is included in a user identifier field of the protocol signature interface.

6. The method of claim 1, further comprising:

determining that the user is not authenticated; and

a request to provide a user identifier for the user is displayed in the protocol signature interface.

7. The method of claim 1, further comprising:

a summary of a signature session is displayed within the protocol signature interface, wherein the summary includes a user identifier and a representation of the source document.

8. The method of claim 1, further comprising:

a signature session is initiated, wherein the signature is acquired during the signature session.

9. The method of claim 1, further comprising:

a signing session context is generated for the signing session, wherein the signed protocol is based on the signing session context.

10. The method of claim 1, further comprising:

displaying in the user interface of the real-time communication session an indication that the signed protocol includes the signature.

11. A system, comprising:

one or more processors; and

one or more memory components coupled with the one or more processors, the one or more processors configured to:

initiating a real-time communication session including a user;

generating the protocol, wherein the protocol includes the source document;

obtaining a signature for the protocol from the user; and

a signed protocol is generated that includes the signature.

12. The system of claim 11, the one or more processors further configured to:

13. The system of claim 11, the one or more processors further configured to:

authenticating the user based on a user identifier; and

14. The system of claim 11, the one or more processors further configured to:

determining that the user is not authenticated; and

15. The system of claim 11, the one or more processors further configured to:

16. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to:

initiating a real-time communication session including a user;

obtaining a signature for the protocol from the user; and

a signed protocol is generated that includes the signature.

17. The non-transitory computer-readable medium of claim 16, wherein the instructions further cause the processor to:

18. The non-transitory computer readable medium of claim 17, wherein:

The document template list includes representations of source documents.

19. The non-transitory computer-readable medium of claim 18, wherein the instructions further cause the processor to:

20. The non-transitory computer-readable medium of claim 16, wherein the instructions further cause the processor to: