Shared document processing method, device, electronic device and storage medium

Abstract

The present application discloses a shared document processing method, device, electronic device and storage medium, which belongs to the field of Internet technology. The method includes: receiving a user's access request for the shared document; in response to the access request, determining whether the access request contains user login information; in the case where the access request contains user login information, obtaining information corresponding to the user from a data file based on the user's login identifier; wherein the data file stores the information filled in by the user in the shared document; writing the information corresponding to the user into a private document corresponding to the user; sending the private document corresponding to the user to the user's client for display; wherein the private document contains the public information in the shared document and the information filled in by the user.

Description

Technical Field

[0001] The present application belongs to the field of Internet technology, and specifically relates to a shared document processing method, device, electronic device and storage medium. Background Art

[0002] At present, in many cases, it is necessary to collect some personal information of multiple team members, and it often involves some sensitive information, such as home address, personal contact number, personal ID information and other private data. Usually, the initiator sends a shared document link in a multi-person chat group, and the other users open the shared document and fill in the relevant information. After the user opens the shared document, he can browse the data filled in by other users, which is easy to cause information leakage. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a shared document processing method, device, electronic device and storage medium, which can solve the problem of information leakage in shared documents.

[0004] In a first aspect, an embodiment of the present application provides a shared document processing method, the method comprising:

[0005] Receiving a request from a client for accessing the shared document;

[0006] In response to the access request, determining whether the access request includes user login information;

[0007] When the access request does not contain user login information, sending a non-logged-in signal to the client of the user to make the client jump to the login interface;

[0008] In the case where the access request includes user login information, obtaining information corresponding to the user from a data file based on the user's login identifier; wherein the data file stores information filled in by the user in the shared document;

[0009] Writing information corresponding to the user into a private document corresponding to the user;

[0010] The private document corresponding to the user is sent to the user's client for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

[0011] In a second aspect, an embodiment of the present application provides a shared document processing device, including:

[0012] A first receiving module, configured to receive an access request from a client for the shared document;

[0013] A first determination module, configured to determine, in response to the access request, whether the access request contains user login information;

[0014] A first sending module, configured to send a non-logged-in signal to a client of the user when the access request does not contain user login information, so that the client jumps to a login interface;

[0015] A first processing module, configured to obtain information corresponding to the user from a data file based on the user's login identifier when the access request includes user login information; wherein the data file stores information filled in by the user in the shared document;

[0016] A first writing module, used to write information corresponding to the user into a private document corresponding to the user;

[0017] The second sending module is used to send the private document corresponding to the user to the client of the user for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

[0018] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0019] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0020] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.

[0021] In a sixth aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the first aspect or the second aspect.

[0022] In the embodiment of the present application, when a user requests to access a shared document, it is determined whether the user's access request contains user login information. If the access request does not contain user login information, it means that the user does not have a login account, and the client is controlled to jump to the login interface to allow the user to log in, so as to prevent people who are not related to the shared document from obtaining the information filled in by the user and prevent information leakage. If the access request contains user login information, that is, the user has logged in, the information corresponding to the user is obtained according to the user's login identifier, and the information corresponding to other users will not be obtained. After obtaining the information corresponding to the user, the information corresponding to the user is written into a private document and the private document is sent to the user's client for display. The private document contains the public information of the shared document and the information filled in by the user himself, so that the user can view and modify the information filled in by himself. Since the user's client will not obtain or display the information filled in by other users, it can be guaranteed that the information filled in by other users will not be leaked. Through the embodiment of the present application, in the scenario of shared documents, each user can only see the public information of the shared document and the information filled in by the user himself, but will not see the information filled in by other users, thereby ensuring the user's personal privacy. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a flow chart of the shared document processing method in an embodiment of the present application.

[0024] Figure 2 It is a schematic diagram of a table document in an embodiment of the present application.

[0025] Figure 3 It is a schematic diagram of a private document in an embodiment of the present application.

[0026] Figure 4 This is a schematic diagram of a private document in another embodiment of the present application.

[0027] Figure 5 It is a schematic diagram of a shared document in an embodiment of the present application.

[0028] Figure 6 It is a schematic diagram of a shared document processing device in an embodiment of the present application.

[0029] Figure 7 It is a schematic diagram of an electronic device in an embodiment of the present application.

[0030] Figure 8 It is a schematic diagram of the hardware structure of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0031] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0032] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0033] It should be noted that all actions to obtain signals, information or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where they are located, and with the authorization given by the corresponding device / account owner.

[0034] The following describes in detail the shared document processing method provided by the embodiment of the present application through specific embodiments and application scenarios in conjunction with the accompanying drawings.

[0035] like Figure 1 As shown, this embodiment introduces a shared document processing method, which is applied to a server, and the method includes steps S1100 to S1600. Each step of the shared document processing method in this embodiment is executed by the server.

[0036] S1100: Receive a user's access request for the shared document.

[0037] Shared documents can be used to collect information from multiple users. After the initiator creates a shared document, the link to the shared document is shared with multiple users. After other users click the link to the shared document, the user's client sends an access request to the server for the shared document.

[0038] For example, in a multi-person chat group, a user creates a shared document and shares the link of the shared document in the multi-person chat group. Other users can send access requests to the server by clicking the link of the shared document.

[0039] like Figure 2As shown, the shared document can be a spreadsheet document. The spreadsheet document contains header information, which is filled in by the initiator. The header information indicates the information that other users need to fill in. For example, the header information may include name, ID number, home address, personal contact number, emergency contact, etc. The shared document can also be a document in other forms.

[0040] S1200: In response to the access request, determine whether the access request includes user login information.

[0041] A user can click a link to a shared document when logged in. A user can also click a link to a shared document when not logged in. If a user clicks a link to a shared document when logged in, the access request may include user login information, such as a user ID (Identity document). Whether the user is logged in can be determined based on the access request.

[0042] S1300: When the access request does not include user login information, a non-logged-in signal is sent to the client of the user, so that the client jumps to a login interface.

[0043] If the access request does not contain the user login information, there is a risk of information leakage when the server returns private documents to the client. To avoid information leakage, the server will not return private documents when the user is not logged in. The server will return a login signal to the client, allowing the client to jump to the login interface and prompt the user to log in.

[0044] For example, user B clicks a link to a shared document when not logged in. The access request does not contain user B's login information. After receiving the access request, the server returns a non-logged in signal to user B's client and displays a login interface on user B's client.

[0045] S1400: When the access request includes user login information, obtain information corresponding to the user from a data file based on the user's login identifier; wherein the data file stores information filled in by the user in the shared document.

[0046] When the access request includes the user login information, the user login identifier can be obtained from the user login information. For example, the user ID is obtained from the user login information. The server obtains the information corresponding to the user from the data file based on the user login identifier. The information corresponding to the user is the information that the user has filled in for the shared document. The information that the user has filled in is saved in the data file.

[0047] For example, if the user has filled in the name and ID number for the shared document, the name and ID number filled in by the user will be saved in the data file. When the access request contains the user login information, the name and ID number filled in by the user are obtained from the data file.

[0048] S1500: Writing information corresponding to the user into a private document corresponding to the user.

[0049] Private documents are created by the server, and each user has a private document. For example, if three users access a shared document, the server will create three private documents. Private documents contain public information. Private documents can also contain information filled in by the user. For example, the name and ID number filled in by the user are obtained from the data file, and the name and ID number filled in by the user are written into the private document corresponding to the user.

[0050] Private documents will not contain information filled in by other users. For example, after user A, user B, and user C have filled in their information, user A's private document will only contain public information and the information filled in by user A, and user A's private document will not contain the information filled in by user B and user C.

[0051] S1600: Sending a private document corresponding to the user to the user's client for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

[0052] The public information in a shared document is the information filled in by the initiator when creating the shared document. The public information can be viewed by all users. For example, if the shared document is a spreadsheet document, the public information is the header information filled in by the initiator.

[0053] If the user's private document is displayed for the first time on the client, it means that the user has not yet filled in the information, so the private document displayed this time only contains public information. If the user has filled in the information before the private document is displayed this time, the private document displayed this time contains both public information and the information previously filled in by the user.

[0054] like Figure 3As shown, the private document is a table document, and the header information includes name, ID number, home address, personal contact number and emergency contact. The user has filled in the name and ID number. The name filled in by the user is "Wang Mazi" and the ID number filled in by the user is "66668888". After the user clicks the link of the shared document, the server sends a private document to the client of the user. The private document contains the header information and the name "Wang Mazi" filled in by the user and the ID number "66668888" filled in by the user. The private document containing the name "Wang Mazi" and the ID number "66668888" is displayed on the client.

[0055] In the embodiment of the present application, when a user requests to access a shared document, it is determined whether the user's access request contains user login information. If the access request does not contain user login information, it means that the user does not have a login account, and the client is controlled to jump to the login interface to allow the user to log in, so as to prevent people who are not related to the shared document from obtaining the information filled in by the user and prevent information leakage. If the access request contains user login information, that is, the user has logged in, the information corresponding to the user is obtained according to the user's login identifier, and the information corresponding to other users will not be obtained. After obtaining the information corresponding to the user, the information corresponding to the user is written into a private document and the private document is sent to the user's client for display. The private document contains the public information of the shared document and the information filled in by the user himself, so that the user can view and modify the information filled in by himself. Since the user's client will not obtain or display the information filled in by other users, it can be guaranteed that the information filled in by other users will not be leaked. Through the embodiment of the present application, in the scenario of shared documents, each user can only see the public information of the shared document and the information filled in by the user himself, but will not see the information filled in by other users, thereby ensuring the user's personal privacy.

[0056] In this embodiment, before obtaining the information corresponding to the user from the data file based on the user's login identification, it also includes: determining whether a private document corresponding to the user has been saved; if not, creating a private document corresponding to the user based on the public information in the shared document.

[0057] The server will create a private document corresponding to each user and save the created private document on the server. Usually, after the client sends a request to access a shared document to the server for the first time, the server will create a private document for the client user and save the private document on the server. When the server creates a private document, it will create it based on the public information in the shared document. The private document created by the server will contain public information.

[0058] After receiving the client's access request for a shared document, the server will determine whether the private document corresponding to the client user has been saved. If the private document corresponding to the user has been saved in the server, the server will directly return the private document to the client. If the private document corresponding to the user has not been saved in the server, the server will create a private document and then return the created private document to the client.

[0059] In one example, user A clicks on a shared document link for the first time, and the client of user A sends an access request for the shared document to the server. After receiving the access request, the server determines that there is no private document corresponding to user A saved, and the server creates a private document corresponding to user A.

[0060] In this embodiment, when the private document corresponding to the user is not saved in the server, the server will create a private document corresponding to the user to ensure that each user corresponds to a private document to avoid information leakage.

[0061] In this embodiment, creating a private document corresponding to the user according to the public information in the shared document includes steps S3100-S3300.

[0062] S3100: Obtain a request serial number corresponding to the access request.

[0063] The server can receive access requests from multiple different users, and the server generates corresponding request numbers according to the order of the access requests. For example, the server receives access requests from user A, user B, and user C in sequence. The server receives the access request from user A first, so the request number corresponding to user A's access request is before the request number corresponding to user B's access request. For example, the request number corresponding to the access request from user A is 2, the request number corresponding to the access request from user B is 3, and the request number corresponding to the access request from user C is 4.

[0064] S3200: Acquire public information in the shared document.

[0065] The shared document is saved on the server, and the server can directly obtain public information from the shared document. For example, if the shared document is a table document, then the header information in the table document can be obtained.

[0066] S3300: Generate a private document corresponding to the user according to the public information and the request serial number.

[0067] The private document generated by the server contains public information, and the private document is associated with the user according to the request sequence number. For example, the request sequence number can be added to the file name of the private document.

[0068] This embodiment obtains a request serial number, and different users correspond to different request serial numbers. A private document is generated according to the request serial number, and the private document corresponds to the user, so as to avoid the situation where the private document sent by the server to the client does not correspond to the user of the client, and to avoid information leakage. At the same time, the private document contains the public information of the shared document. When the private document is displayed on the user's client, the user can view the public information of the shared document, so that the user can fill in the public information of the shared document.

[0069] In this embodiment, when the shared document is a table document, after the private document corresponding to the user is sent to the client of the user for display, steps S4100-S4500 are also included.

[0070] S4100: Receive a private document containing information filled in by a user.

[0071] After the server sends the private document corresponding to the user back to the client, the private document corresponding to the user is displayed on the client. The user can fill in the private document. After the user has completed filling in, the client sends the private document filled in by the user to the server, and the server receives the private document containing the content filled in by the user.

[0072] like Figure 4 As shown, the user fills in "Wang Mazi" in the "Name" column, the user fills in "888888" in the "ID Number" column, and the user fills in "Shanghai xxxx" in the "Home Address" column.

[0073] S4200: Obtain the first position according to the request sequence number.

[0074] The first line in a shared document is the header information, which is filled in by the initiator. Other users fill in the corresponding content based on the header information. In a shared document, the content filled in by each user is saved in one line in the shared document.

[0075] The first position indicates a row in the shared document. For example, if the request number of the first user is 2, the content filled in by the first user is saved in the second row of the table document. If the request number of the second user is 3, the content filled in by the second user is saved in the third row of the table document.

[0076] S4300: Acquire the second position of the information filled in by the user in the private document.

[0077] The first row in the private document is the header information obtained from the shared document. The content filled in by the user is in the second row in the private document. The second position indicates the column in the private document. Different contents filled in by the user are in different columns in the private document.

[0078] like Figure 4 In the private document shown, the first line is the header information, and the second line is the content filled in by the user. Different letters are used to represent different columns in the private document. The user filled in "Wang Mazi" in the "Name" column, which is located in column A. The user filled in "888888" in the "ID Number" column, which is located in column B.

[0079] S4400: Determine a third position according to the first position and the second position.

[0080] The third position is the position of the information filled in by the user in the shared document. The first position represents a row in the shared document, and the second position represents a column in the shared document. The third position can be determined in the shared document based on the first position and the second position.

[0081] S4500: Save the information filled in by the user and the corresponding third position in the data file.

[0082] Each item filled in by the user has a different position in the shared document. The information filled in by the user and the corresponding third position are saved in the data file.

[0083] After receiving the second access request from the creator of the shared document, the information filled in by all users and the corresponding third location are obtained from the data file. The information filled in by all users is written into the shared document according to the corresponding third location. The shared document is sent to the creator's client for display.

[0084] like Figure 5 As shown, the request number of the first user is 2, and the request number of the second user is 3. The content filled in by the first user is saved in the second row, and the content filled in by the second user is saved in the third row. The name "Wang Mazi" filled in by the first user is in the A column of the private document, so "Wang Mazi" is in the first row, column A of the shared document. The ID number "66667777" filled in by the second user is in the B column of the private document, so "66667777" is in the third row, column B of the shared document.

[0085] This embodiment obtains the first position according to the request serial number, and jointly determines the third position of the information filled in by the user in the shared document according to the first position and the second position of the information filled in by the user in the private document. Since different users have different request serial numbers, the content filled in by different users corresponds to different positions in the shared document, thereby avoiding overlapping of information filled in by different users.

[0086] In this embodiment, before receiving the user's access request for the shared document, steps S6100-S6300 are also included.

[0087] S6100: Receive a creation request for the shared document.

[0088] The shared document is created by the initiator. After the initiator creates the shared document on the client, the initiator's client sends a request to create the shared document to the server. The server receives the creation request.

[0089] S6200: Acquire public information according to the creation request.

[0090] When the initiator creates a shared document on the client, the initiator can write public information into the shared document. Public information can be viewed by all users. After receiving the creation request of the shared document, the server obtains the public information according to the creation request. For example, the creation request can include the public information filled in by the initiator, and the server can obtain the public information from the creation request.

[0091] In one example, the shared document is a spreadsheet document. When creating a spreadsheet document, the initiator fills in the header information, the creation request includes the header information, and the server obtains the header information from the creation request.

[0092] S6300: Generate the shared document and a data file corresponding to the shared document according to the public information.

[0093] The shared document is created by the server, and the shared document created by the server will contain public information. For example, if the public information is the header information, then the server will generate a table document, and the table document generated by the server will contain the header information.

[0094] When a shared document is created on the server, the server will also create a data file corresponding to the shared document. The data file is used to save the information filled in by the user for the shared document. When the data file is created, the data file is a blank file. When a user fills in information for the shared document, the information filled in by the user is saved in the data file.

[0095] Shared documents and corresponding data files are stored on the server. You can create a folder on the server, and store shared documents and corresponding data files in the folder. You can also store private documents in the folder.

[0096] This embodiment introduces a shared document processing method, which includes steps S101-S110.

[0097] S101: A first client receives a second input, and in response to the first input, the first client sends a save request to a server.

[0098] The first client is the client of the initiator. The initiator creates a form document through the first client. The initiator fills in the header information and sends a save request to the server after completing the filling. For example, the header information includes "name", "ID number", "home address", "personal contact number", and "emergency contact".

[0099] S102: In response to the save request, the server creates an original table file and an original json file.

[0100] After receiving the save request, the server creates the original table file and the original json file. The original table file contains the header information, and the original file can be named "Original File-Personal Information Collection.xls". The original json file can be named "Original File-Personal Information Collection.json", and the json content format design is as follows:

[0101] [{“Cell location”: “xx”, “Cell content”: “yy”, “User ID”: “dd”}]

[0102] S103: The second client receives the third input, and in response to the third input, the second client sends an access request to the server.

[0103] The second client is a client of another user, and the third input is a link of the form document clicked by the user.

[0104] S104: The server determines whether the user has logged in according to the access request; if the user has not logged in, the server returns a not logged in signal to the second client, and the second client jumps to the login interface.

[0105] S105: When the user has logged in, the server obtains the user ID, and searches for the private file corresponding to the user ID on the server according to the user ID. After the server searches for the private file corresponding to the user ID, the server sends the private file back to the second client, and the second client displays the private file.

[0106] S106: After the server fails to find a private file corresponding to the user ID, the server creates a private file corresponding to the user ID according to the header information in the original table file. The private file is named after the user ID and saved in the server.

[0107] When creating a private file on the server, the server first creates a blank table file and stores it in the file directory corresponding to the server according to the user ID. The file directory structure is as follows:

[0108] / root directory / year month date-personal ID card and family information collection / {user ID} / {user ID}-{request serial number}.xls

[0109] After the server creates a blank table file, the server reads the header information in the original table file, and writes the read header information into the header of the user's private file to inform the user what information should be filled in.

[0110] When multiple second clients send access requests to the server, the server generates corresponding request serial numbers according to the order of the access requests, and writes the request serial numbers into the file name of the private file.

[0111] S107: The server obtains the content in the original json file, obtains the information corresponding to the user according to the user ID, writes the obtained information corresponding to the user into the private file corresponding to the user, and sends the private file back to the second client for display.

[0112] The following is the JSON content submitted by all users, including cell content, cell location and user ID.

[0113] [{"Cell location":"A6","Cell content":"Wang Mazi","User ID":"aaa"},

[0114] {"Cell location":"B6","Cell content":"66668888","User ID":"aaa"},

[0115] {"Cell location":"A3","Cell content":"88888888","User ID":"bbb"},

[0116] {"Cell location":"A4","Cell content":"Shanghai xxx","User ID":"ccc"}]

[0117] For example, if the current user ID is "aaa", the information corresponding to the user ID obtained by the server is:

[0118] [{"Cell location":"A6","Cell content":"Wang Mazi","User ID":"aaa"},

[0119] {"Cell Location":"B6","Cell Content":"66668888","User ID":"aaa"}]

[0120] S108: The second client receives the fourth input, and in response to the fourth input, the second client sends a save request to the server.

[0121] After the second client displays the private file corresponding to the user, the user can fill in information in the private file. After the user finishes filling in, the second client sends a save request to the server.

[0122] S109: After the server receives the save request sent by the second client, the server saves the received private file, reads the information filled in by the user in the private file, and merges the information filled in by the user and the user ID into the original json file.

[0123] For example, the information read by the server from the private file is shown in the following json format:

[0124] [{"cell position": "A2", "cell content": "Wang Mazi"},

[0125] {"cell position": "B2", "cell content": "88888888"},

[0126] {"cell position": "C2", "cell content": "xxx, Shanghai"},

[0127] {"cell position": "D2", "cell content": "138***8888"}]

[0128] The server obtains the request sequence number of this user. For example, the request sequence number of this user is 6. The server modifies the cell position according to the request sequence number. The information filled in by this user is in the following json format:

[0129] [{"cell position": "A6", "cell content": "Wang Mazi", "user id", "aaa"},

[0130] {"cell position": "B6", "cell content": "88888888", "user id", "aaa"},

[0131] {"cell position": "C6", "cell content": "xxx, Shanghai", "user id", "aaa"},

[0132] {"cell position": "D6", "cell content": "138***8888", "user id", "aaa"}

[0133] The server merges the user-filled information in the above json format into the original json file to obtain all the user-filled information as follows:

[0134] [{"cell position": "A6", "cell content": "Wang Mazi", "user id", "aaa"},

[0135] {"Cell location":"B6","Cell content":"88888888","User id","aaa"},

[0136] {"Cell location":"C6","Cell content":"Shanghai xxx","User id","aaa"},

[0137] {"Cell location":"D6","Cell content":"138***8888","User id","aaa"},

[0138] "Cell location": "A9", "Cell content": "Wang Er", "User id", "bbb"},

[0139] {"Cell location":"B9","Cell content":"56785555","User id","bbb"},

[0140] {"Cell location":"C9","Cell content":"Shanghai xxx","User id","bbb"},

[0141] {"Cell location":"D9","Cell content":"138***7777","User id","bbb"}]

[0142] S110: The first client receives the fifth input, and in response to the fifth input, the first client sends an access request to the server. After the server receives the access request sent by the first client, the server reads the original json file, and writes the corresponding cell content into the original table file according to the cell position. After writing, the server sends the original table file to the first client, and the first client displays the original table file.

[0143] When the initiator needs to view the information filled in by the user, the initiator clicks the link of the table document displayed by the first client, and the first client sends an access request to the server. After receiving the access request, the server writes the content of the original json file into the original table file, and then sends the original table file back to the first client for display.

[0144] In the embodiment of the present application, when a user requests to access a shared document, it is determined whether the user's access request contains user login information. If the access request does not contain user login information, it means that the user does not have a login account, and the client is controlled to jump to the login interface to allow the user to log in, so as to prevent people who are not related to the shared document from obtaining the information filled in by the user and prevent information leakage. If the access request contains user login information, that is, the user has logged in, the information corresponding to the user is obtained according to the user's login identifier, and the information corresponding to other users will not be obtained. After obtaining the information corresponding to the user, the information corresponding to the user is written into a private document and the private document is sent to the user's client for display. The private document contains the public information of the shared document and the information filled in by the user himself, so that the user can view and modify the information filled in by himself. Since the user's client will not obtain or display the information filled in by other users, it can be guaranteed that the information filled in by other users will not be leaked. Through the embodiment of the present application, in the scenario of shared documents, each user can only see the public information of the shared document and the information filled in by the user himself, but will not see the information filled in by other users, thereby ensuring the user's personal privacy.

[0145] The shared document processing method provided in the embodiment of the present application can be executed by a shared document processing device. In the embodiment of the present application, the shared document processing device provided in the embodiment of the present application is described by taking the shared document processing device executing the shared document processing method as an example.

[0146] like Figure 6 As shown, this embodiment introduces a shared document processing device 600, including:

[0147] The first receiving module 601 is used to receive a user's access request for the shared document.

[0148] The first determination module 602 is used to respond to the access request and determine whether the access request contains user login information.

[0149] The first sending module 603 is used to send a non-logged-in signal to the client of the user when the access request does not include the user login information, so that the client jumps to the login interface.

[0150] The first processing module 604 is used to obtain information corresponding to the user from a data file based on the user's login identifier when the access request includes user login information; wherein the data file stores information filled in by the user in the shared document.

[0151] The first writing module 605 is used to write the information corresponding to the user into the private document corresponding to the user.

[0152] The second sending module 606 is used to send the private document corresponding to the user to the client of the user for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

[0153] In the embodiment of the present application, when a user requests to access a shared document, it is determined whether the user's access request contains user login information. If the access request does not contain user login information, it means that the user does not have a login account, and the client is controlled to jump to the login interface to allow the user to log in, so as to prevent people who are not related to the shared document from obtaining the information filled in by the user and prevent information leakage. If the access request contains user login information, that is, the user has logged in, the information corresponding to the user is obtained according to the user's login identifier, and the information corresponding to other users will not be obtained. After obtaining the information corresponding to the user, the information corresponding to the user is written into a private document and the private document is sent to the user's client for display. The private document contains the public information of the shared document and the information filled in by the user himself, so that the user can view and modify the information filled in by himself. Since the user's client will not obtain or display the information filled in by other users, it can be guaranteed that the information filled in by other users will not be leaked. Through the embodiment of the present application, in the scenario of shared documents, each user can only see the public information of the shared document and the information filled in by the user himself, but will not see the information filled in by other users, thereby ensuring the user's personal privacy.

[0154] In one embodiment, the device further comprises:

[0155] The second judgment module is used to judge whether the private document corresponding to the user has been saved.

[0156] The first creation module is used to create a private document corresponding to the user according to the public information in the shared document when the private document corresponding to the user is not saved.

[0157] In one embodiment, the device further comprises:

[0158] The first acquisition module is used to acquire a request sequence number corresponding to the access request.

[0159] The second acquisition module is used to acquire the public information in the shared document.

[0160] The first creation module is further used to generate a private document corresponding to the user according to the public information and the request sequence number.

[0161] In one implementation, when the shared document is a table document, the device further includes:

[0162] The second receiving module is used to receive a private document containing information filled in by a user.

[0163] The third acquisition module is used to acquire the first position according to the request sequence number.

[0164] The fourth acquisition module is used to obtain the second position of the information filled in by the user in the private document.

[0165] The first determining module is used to determine a third position according to the first position and the second position.

[0166] The first saving module is used to save the information filled in by the user and the corresponding third position in the data file.

[0167] In one embodiment, the device further comprises:

[0168] The third receiving module is used to receive a creation request for the shared document.

[0169] The fifth acquisition module is used to acquire public information according to the creation request.

[0170] The second creation module is used to generate the shared document and a data file corresponding to the shared document according to the public information.

[0171] The shared document processing device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0172] The shared document processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0173] The shared document processing device provided in the embodiment of the present application can achieve Figures 1 to 5 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0174] Alternatively, if Figure 7 As shown, an embodiment of the present application also provides an electronic device 700, including a processor 701 and a memory 702, and the memory 702 stores a program or instruction that can be executed on the processor 701. When the program or instruction is executed by the processor 701, the various steps of the above-mentioned shared document processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0175] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0176] Figure 8 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0177] The electronic device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010 and other components.

[0178] Those skilled in the art will appreciate that the electronic device 1000 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0179] The user input unit 1007 is used to receive a user's access request for the shared document.

[0180] The processor 1010 is used to respond to the access request and determine whether the access request contains user login information.

[0181] The processor 1010 is further configured to send a non-logged-in signal to the client of the user when the access request does not include the user login information, so that the client jumps to the login interface.

[0182] Processor 1010 is further configured to obtain information corresponding to the user from a data file based on the user's login identifier when the access request includes user login information; wherein the data file stores information filled in by the user in the shared document.

[0183] The processor 1010 is further configured to write the information corresponding to the user into a private document corresponding to the user.

[0184] The processor 1010 is further configured to send a private document corresponding to the user to a client of the user for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

[0185] In the embodiment of the present application, when a user requests to access a shared document, it is determined whether the user's access request contains user login information. If the access request does not contain user login information, it means that the user does not have a login account, and the client is controlled to jump to the login interface to allow the user to log in, so as to prevent people who are not related to the shared document from obtaining the information filled in by the user and prevent information leakage. If the access request contains user login information, that is, the user has logged in, the information corresponding to the user is obtained according to the user's login identifier, and the information corresponding to other users will not be obtained. After obtaining the information corresponding to the user, the information corresponding to the user is written into a private document and the private document is sent to the user's client for display. The private document contains the public information of the shared document and the information filled in by the user himself, so that the user can view and modify the information filled in by himself. Since the user's client will not obtain or display the information filled in by other users, it can be guaranteed that the information filled in by other users will not be leaked. Through the embodiment of the present application, in the scenario of shared documents, each user can only see the public information of the shared document and the information filled in by the user himself, but will not see the information filled in by other users, thereby ensuring the user's personal privacy.

[0186] Optionally, the processor 1010 is further configured to determine whether a private document corresponding to the user has been saved.

[0187] The processor 1010 is further configured to create a private document corresponding to the user according to the public information in the shared document when the private document corresponding to the user is not saved.

[0188] Optionally, the processor 1010 is further configured to obtain a request sequence number corresponding to the access request.

[0189] The processor 1010 is further configured to obtain the public information in the shared document.

[0190] The processor 1010 is further configured to generate a private document corresponding to the user according to the public information and the request sequence number.

[0191] Optionally, when the shared document is a spreadsheet document, the processor 1010 is further configured to receive a private document containing information filled in by a user.

[0192] The processor 1010 is further configured to obtain the first position according to the request sequence number.

[0193] The processor 1010 is further configured to obtain a second position of the information filled in by the user in the private document.

[0194] The processor 1010 is further configured to determine a third position according to the first position and the second position.

[0195] The processor 1010 is further configured to save the information filled in by the user and the corresponding third position in the data file.

[0196] Optionally, the processor 1010 is further configured to receive a creation request for the shared document.

[0197] The processor 1010 is further configured to obtain public information according to the creation request.

[0198] The processor 1010 is further configured to generate the shared document and a data file corresponding to the shared document according to the public information.

[0199] It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0200] The memory 1009 can be used to store software programs and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0201] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.

[0202] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned shared document processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0203] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0204] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned shared document processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0205] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0206] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned shared document processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0207] It should be noted that, in this article, the term "comprises", "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0208] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0209] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A shared document processing method, characterized in that: The method comprises: receiving a user's access request for the shared document; In response to the access request, determining whether the access request includes user login information; When the access request does not contain user login information, sending a non-logged-in signal to the client of the user to make the client jump to the login interface; In the case where the access request includes user login information, obtaining information corresponding to the user from a data file based on the user's login identifier; wherein the data file stores information filled in by the user in the shared document, and the information corresponding to the user is information already filled in by the user for the shared document; Writing information corresponding to the user into a private document corresponding to the user; The private document corresponding to the user is sent to the client of the user for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

2. The method according to claim 1, characterized in that Before acquiring information corresponding to the user from a data file based on the login identifier of the user, the method further includes: Determining whether a private document corresponding to the user has been saved; If not, a private document corresponding to the user is created according to the public information in the shared document.

3. The method according to claim 2, characterized in that The step of creating a private document corresponding to the user according to the public information in the shared document comprises: Obtaining a request sequence number corresponding to the access request; Acquire public information in the shared document; A private document corresponding to the user is generated according to the public information and the request sequence number.

4. The method according to claim 3, characterized in that In the case where the shared document is a table document, after sending the private document corresponding to the user to the client of the user for display, the method further includes: receiving a private document containing information filled in by the user; Get the first position according to the request sequence number; Obtaining the second position of the information filled in by the user in the private document; determining a third position based on the first position and the second position; The information filled in by the user and the corresponding third position are saved in the data file.

5. The method according to claim 1, characterized in that: Before receiving the user's access request for the shared document, the method further includes: receiving a creation request for the shared document; Obtaining public information according to the creation request; The shared document and a data file corresponding to the shared document are generated according to the public information.

6. A shared document processing device, characterized in that: include: A first receiving module, configured to receive an access request from a client for the shared document; A first determination module, configured to determine, in response to the access request, whether the access request contains user login information; A first sending module, configured to send a non-logged-in signal to a client of the user when the access request does not contain user login information, so that the client jumps to a login interface; A first processing module is configured to obtain information corresponding to the user from a data file based on the user's login identifier when the access request includes user login information; wherein the data file stores information filled in by the user in the shared document, and the information corresponding to the user is information already filled in by the user for the shared document; A first writing module, used to write information corresponding to the user into a private document corresponding to the user; The second sending module is used to send the private document corresponding to the user to the client of the user for display; wherein the private document includes the public information in the shared document and the information filled in by the user.

7. The device according to claim 6, characterized in that Also includes: A second determination module is used to determine whether a private document corresponding to the user has been saved; The first creation module is used to create a private document corresponding to the user according to the public information in the shared document when the private document corresponding to the user is not saved.

8. The device according to claim 7, characterized in that Also includes: A first acquisition module, used to acquire a request sequence number corresponding to the access request; A second acquisition module, used to acquire public information in the shared document; The first creation module is further used to generate a private document corresponding to the user according to the public information and the request sequence number.

9. The device according to claim 8, characterized in that In the case where the shared document is a table document, the method further includes: A second receiving module, used to receive a private document containing information filled in by the user; A third acquisition module, used to acquire the first position according to the request sequence number; A fourth acquisition module, used to acquire the second position of the information filled in by the user in the private document; A first determining module, configured to determine a third position according to the first position and the second position; The first saving module is used to save the information filled in by the user and the corresponding third position in the data file.

10. The device according to claim 6, characterized in that Also includes: A third receiving module, configured to receive a creation request for the shared document; A fifth acquisition module, used to acquire public information according to the creation request; The second creation module is used to generate the shared document and a data file corresponding to the shared document according to the public information.

11. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the shared document processing method according to any one of claims 1 to 5 are implemented.

12. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the shared document processing method according to any one of claims 1 to 5 are implemented.

Images