CN115168071A

CN115168071A - Method and device for realizing cross-system data penetration

Info

Publication number: CN115168071A
Application number: CN202210783522.8A
Authority: CN
Inventors: 唐诗斯
Original assignee: Dingtalk China Information Technology Co Ltd
Current assignee: Dingtalk China Information Technology Co Ltd
Priority date: 2022-06-27
Filing date: 2022-06-27
Publication date: 2022-10-11

Abstract

One or more embodiments of the present specification provide a method and an apparatus for implementing cross-system data penetration, which are applied to a client of an application program, where a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated in the client; the method comprises the following steps: responding to the trigger operation of a local user for the current document, and generating a corresponding to-be-processed event related to a target user by the document editing module; and the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed to a target function module in a client corresponding to the target user for processing.

Description

Method and device for realizing cross-system data penetration

Technical Field

One or more embodiments of the present disclosure relate to the field of data transmission, and in particular, to a method and an apparatus for implementing cross-system data penetration.

Background

In daily life, applications like schedules, backlogs and the like are used more and more frequently, and most users perform daily time management through the backlogs. When an application such as backlog is used, documents associated with backlog often need to be processed. In the existing stage, because the document system and other functional systems such as backlog are mutually independent, when a user opens a document, the user needs to jump back and forth between different systems, which greatly increases the complexity of operation and affects the use experience of the user.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a method and an apparatus for implementing cross-system data penetration, which can implement data penetration between a document system and other functional systems, simplify user operation complexity, and improve user operation efficiency.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, a method for implementing cross-system data penetration is provided, which is applied to a client of an application program, and a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated in the client; the method comprises the following steps:

responding to the trigger operation of a local user for the current document, and generating a corresponding to-be-processed event related to a target user by the document editing module;

and the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed to a target function module in a client corresponding to the target user for processing.

According to a second aspect of one or more embodiments of the present specification, an apparatus for implementing cross-system data penetration is provided, which is applied to a client of an application program, and the client integrates a document editing module belonging to a document system and a target function module belonging to a target system different from the document system; the device comprises:

a generation unit: responding to the trigger operation of a local user for the current document, and generating a corresponding to-be-processed event related to a target user by the document editing module;

a transmission unit: the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed to a target function module in a client corresponding to the target user for processing.

According to a third aspect of one or more embodiments of the present specification, there is provided an electronic apparatus including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of the first aspect by executing the executable instructions.

According to a fourth aspect of one or more embodiments of the present specification, a computer-readable storage medium is presented, on which computer instructions are stored, which instructions, when executed by a processor, implement the steps of the method according to the first aspect.

As can be seen from the above technical solutions, in one or more embodiments of the present description, a local user triggers a document editing module belonging to a document system in a client corresponding to the local user to generate a corresponding to-be-processed event associated with a target user for a trigger operation executed by the current document, the document editing module sends the to-be-processed event to a document server corresponding to the document editing module in the document system, and the document server forwards the to-be-processed event to the target server in the target system, so that the target server further forwards the to-be-processed event to a target function module in the client corresponding to the target user for processing. The process realizes cross-system data penetration, so that a user can operate other systems different from a document system while editing the document without jumping back and forth among different systems, thereby greatly reducing the complexity of operation and improving the operation efficiency of the user.

Drawings

FIG. 1 is a system architecture diagram illustrating an implementation of a cross-system data penetration method, according to an exemplary embodiment.

FIG. 2 is a flowchart illustrating a method for implementing cross-system data penetration in accordance with an exemplary embodiment.

FIG. 3a is a schematic diagram of a schedule creation interface in accordance with an illustrative embodiment.

FIG. 3b is a schematic diagram of a calendar information entry interface according to an exemplary embodiment.

FIG. 3c is a schematic diagram of a calendar presentation interface in accordance with an illustrative embodiment.

FIG. 4a is a diagram of a to-do creation interface, provided by an exemplary embodiment.

FIG. 4b is a diagram illustrating a to-do information interface, according to an exemplary embodiment.

FIG. 5 is an interface diagram of a comment notification message provided by an exemplary embodiment.

FIG. 6a is a schematic illustration of a member selection interface provided by an exemplary embodiment.

FIG. 6b is a schematic illustration of a member information insertion interface provided by an exemplary embodiment.

Fig. 7 is a schematic block diagram of an apparatus provided in an exemplary embodiment.

FIG. 8 is a block diagram of an apparatus to implement cross-system data penetration as provided by an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

To further illustrate one or more embodiments of the present disclosure, the following examples are provided:

FIG. 1 is a system architecture diagram illustrating an implementation of a cross-system data penetration method, according to an exemplary embodiment. As shown in fig. 1, may include a local terminal 11, a target terminal 12, a document server 13, and a target server 14.

The local terminal 11 is one type of electronic device that can be used by a local user. Similarly, the target terminal 12 is one type of electronic device that may be used by the target user. Of course, the electronic device referred to in the present specification is not limited to this, and may include, for example: tablet devices, notebook computers, personal Digital Assistants (PDAs), wearable devices (such as smart glasses, smart watches, etc.), etc., which are not limited in this specification. In the operation process, the local terminal 11 runs a client program corresponding to the local user on the application program, so that the local terminal 11 is configured as a client corresponding to the local user on the application program. The document editing module in the client program corresponding to the local user can realize a generation function of generating the to-be-processed event related to the target user, so that the client corresponding to the local user can generate the to-be-processed event related to the target user based on the generation function. The document editing module can also realize a sending function of sending the generated to-be-processed event to the document server, so that the client corresponding to the local user can send the to-be-processed event based on the sending function. And a client program corresponding to a target user on the application program is run on the target terminal 12, so that the target terminal 12 is configured as a client corresponding to the target user on the application program. The target function module in the client program corresponding to the target user can realize a processing function for processing the received event to be processed, so that the client corresponding to the target user can process the received event to be processed based on the processing function. The target terminal 12 may be the same electronic device as the local terminal 11 or a different electronic device, which is not limited in this specification.

The document server 13 and the target server 14 may each be a physical server comprising a separate host, or a virtual server carried by a cluster of hosts. The document server 13 has a server program of the document system running thereon, so that the document server 13 is configured as a server of the document system. The server program of the document system may be adapted to a document editing module in the client corresponding to the local user, for example, to receive the to-be-processed event sent by the document editing module and forward the to-be-processed event to the target server. The target server 14 runs a server program of a target system different from the document system, so that the target server 14 is configured as a server of the target system. The server program corresponding to the target system may be matched with the target function module in the client corresponding to the target user, for example, may receive a to-be-processed event sent by the server of the document system and forward the to-be-processed event to the target function module for processing.

The interaction mode performed among the local terminal 11, the target terminal 12, the document server 13 and the target server 14 may include various types of wired or wireless interaction, and the description does not limit this.

FIG. 2 is a flow chart of a method for implementing cross-system data penetration in accordance with an exemplary embodiment. As shown in fig. 2, the method is applied to a client of an application program, in which a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated, and may include the steps of:

step 202, in response to a trigger operation of a local user on a current document, the document editing module generates a corresponding to-be-processed event related to a target user.

The document editing module and the target function module are SDKs integrated in the client of the application program.

The local user may be the user performing the trigger operation. The target user may be a user associated with the to-be-processed event generated by the trigger operation, and the target user may include a local user or may not include the local user.

The current document may be a document for which a local user performs a triggering operation, and the document may be any text entity associated with data editing, for example, an Excel table or a Word document, which is not limited in this specification.

The triggering operation of the local user may be an operation executed by the local user to trigger the document editing module to perform a relevant action, for example, the triggering operation may be triggered by the user clicking a certain option in an application program, or triggered by the user through voice or the like. Of course, the trigger operation is not limited to click, voice, etc., and this specification does not limit this. The trigger operation is typically associated with a pending event generated by the document editing module, such as: if the triggering operation executed by the local user clicks the schedule insertion option of the current document, the event to be processed generated by the document editing module is a schedule creation event; if the triggering operation executed by the local user is comment adding, the to-be-processed event generated by the document editing module is a comment notification event.

Step 204, the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed further to a target function module in a client corresponding to the target user for processing.

After the document editing module generates the event to be processed, the generated event to be processed can be sent to the document server, and then forwarded by the document server and the target server, and finally sent to the target function module in the client corresponding to the target user, and the event to be processed is processed by the target function module. The process realizes cross-system data penetration, so that a user can operate other systems different from a document system while editing the document without jumping back and forth among different systems, thereby greatly reducing the complexity of operation and improving the operation efficiency of the user.

The to-be-processed event may include a reminding event, where the reminding event includes an end time, and the target function module in the client corresponding to the target user may send a reminder to the target user according to the end time. The reminder event may be generated by the document editing module in response to a trigger action directed to the reminder, e.g., the document editing module may generate a calendar creation event in response to the local user clicking on an insert calendar option or a to-do creation event in response to the local user clicking on a create to-do option.

Taking a schedule creation event as an example, the following describes in detail a method for implementing cross-system data penetration with reference to fig. 3a, 3b, and 3c, where fig. 3a is a schematic diagram of a schedule creation interface provided in an exemplary embodiment, as shown in fig. 3a, the schedule creation interface includes: a table title 302, a cell 304, an insert button 306, and a schedule reminder button 308. The local user may select cell 304 in the interface and then click insert button 306, clicking schedule reminder button 308 in the presentation menu triggers generation of a schedule information entry interface. Fig. 3b is a schematic diagram of a schedule information input interface provided by an exemplary embodiment, and as shown in fig. 3b, the schedule information input interface includes: cell 310, expiration time selection table 312, target user input box 314, preset reminder duration input box 316, schedule item input box 318, and confirmation button 320. The local user may select the expiration time via expiration time selection table 312 and then click on confirmation button 320 to insert a schedule reminder in cell 310. The local user can also complete the schedule information in the input boxes such as the target user input box 314, the preset reminding time input box 316, the schedule item input box 318 and the like, or choose not to input, and the document editing module takes the default value. The local user can trigger the document editing module to generate a schedule creating event aiming at the schedule inserting reminding operation of the current document, the schedule creating event is transmitted to the schedule module of the client corresponding to the target user for processing through the forwarding of the document service terminal and the schedule service terminal, and the schedule module creates a corresponding schedule based on the received schedule creating event. The schedule module may send a reminder to the target user according to an end time included in the schedule, for example, the schedule display interface shown in fig. 3c may be displayed to the target user at the end time, fig. 3c is a schematic diagram of a schedule display interface provided in an exemplary embodiment, as shown in fig. 3c, the schedule display interface includes: calendar 322, deadline 324, target user 326, and document link 328. The target user can view the deadline 324 of the schedule 322 and the target user 326, etc. at the schedule presentation interface and can also open a document associated with the schedule 322 by clicking on the document link 328. The contents of the document link opening document will be described in detail later, and will not be described in detail herein.

The embodiment realizes data penetration between the schedule system and the document system, so that a user can create the schedule when editing the document, the skip operation between different systems is avoided, the complexity of the operation is reduced, and the operation efficiency of the user is improved.

The mode of generating the event to be processed by the document editing module may be: the document editing module acquires user input information provided by a local user, and generates a corresponding to-be-processed event related to a target user according to the user input information. In the example of schedule creation, the document editing module generates a schedule information input interface for the user to input schedule information in response to the schedule insertion reminding operation, and certainly, the manner in which the document editing module obtains the user input information is not limited thereto, and the document editing module may also determine the user input information by providing pictures or playing voices, and the description does not limit this.

Besides the mode of acquiring the information input by the user to generate the event to be processed, the document editing module can also acquire the document information of the current document and generate the corresponding event to be processed related to the target user according to the document information. The document information may include document content, an ID of a current document, and the like, and this specification does not limit this.

In one embodiment, the trigger operation has a corresponding trigger position in the current document, and the document information includes document content in the current document corresponding to the trigger position. The document editing module may acquire document content in the current document corresponding to the trigger position, and generate a to-be-processed event based on the acquired document content. The embodiment provides the method for rapidly acquiring the document information, the document information can be acquired without manually inputting information by a user, and the use experience of the user is improved.

Taking a to-do event as an example, referring to fig. 4a and 4b, a method for generating a to-do event by acquiring document information by a document editing module is described in detail below, where fig. 4a is a schematic diagram of a to-do event creating interface provided by an exemplary embodiment, and as shown in fig. 4a, the to-do event creating interface includes: a table 402, a target cell 404, an insert button 406, and a to-do button 408. The local user may have the target cell 404 in the table 402 as the location to insert the to-do item, and then the local user may click the insert button 406 and then click the to-do button 408 to insert the to-do item. The cell 404 corresponds to the trigger position of the aforementioned trigger operation in the current document, and the content "visual design", "@ Xiaoming" and "2022/3/3" at the cell 404 corresponds to the document content in the current document corresponding to the trigger position. The document editing module may identify the document content at the trigger location and generate a backlog information interface for the local user to view, and fig. 4b is a schematic diagram of a backlog information interface provided by an exemplary embodiment, as shown in fig. 4b, the backlog information interface includes: cell 410, to-do box 412, target user box 414, expiration time box 416, cell location box 418, and confirmation button 420. The local user can check whether the information identified by the document editing module at the trigger location is accurate in the to-do box 412, the target user box 414, and the deadline box 416, and can also check the cell location where the trigger location is located at the cell location box 418. The local user may click the confirmation button 420 to insert a to-do event, so as to trigger the document editing module to generate a to-do event, and the to-do event is finally sent to the to-do module of the client corresponding to "@ xiaoming" for processing.

The embodiment realizes data penetration between the to-be-handled system and the document system, so that a user can create the to-be-handled items when editing the document, jump operation between different systems is avoided, the operation complexity is reduced, and the operation efficiency of the user is improved.

In one embodiment, the document editing module obtains document information of a current document and user input information provided by a local user, and generates a corresponding to-be-processed event related to a target user according to the document information and the user input information. The document editing module can combine the two information acquisition modes, so that part of information required for generating the event to be processed is acquired through the document information, and part of information is acquired through the information input by the user. The embodiment provides a plurality of information acquisition modes for the user, can identify the content of the existing document, avoid inputting information again, simplify the operation steps, and can also provide a user information input interface to prevent the information from being incomplete. The method and the device reduce the operation complexity and improve the use experience of the user while ensuring that the information required by the generation of the event to be processed is complete enough.

Besides the schedule creating event, the to-be-handled event creating event and other reminding events, the to-be-handled event may further include a comment event, the comment event includes comment content, and the processing of the to-be-handled event by the target function module in the client corresponding to the target user may be: and providing the comment content to the target user. And responding to the comment operation of the local user on the current document, generating a comment event related to the target user by the document editing module, sending the comment event to the document service end, finally sending the comment event to a communication module of the client corresponding to the target user through the forwarding of the document service end and the communication service end, and providing comment content contained in the comment event to the target user by the communication module. The specific manner of providing the comment content to the user may be sending the comment content to the target user in a message manner, or reporting the comment content in a voice manner, which is not limited in this specification.

In an embodiment, a preset comment notification template is stored on the communication module, the communication module may generate a comment notification message having a specific format based on the comment notification template and comment content included in the comment event, and send the comment notification message to the target user, where the specific format may be that the comment content is exposed to facilitate viewing by the target user. The embodiment realizes data penetration between the communication system and the document system, so that the target user can be notified without sending a message to a comment-related user when the user comments, thereby avoiding skip operation between different systems, reducing the complexity of operation and improving the operation efficiency of the user.

Furthermore, the target user can reply to the provided comment content, and the document editing module receives a comment reply event sent by the document server and processes the comment reply event; the comment reply event is generated by a target function module in a client corresponding to a target user according to reply operation of the target user on comment content, and the comment reply event is acquired by the target server from the target function module in the client corresponding to the target user and then forwarded to the document server. Responding to the reply operation of the target user for the comment content, the communication module of the client corresponding to the target user generates a corresponding comment reply event and sends the comment reply event to the communication server, the comment reply event is forwarded to the document editing module through the communication server and the document server, and the document editing module processes the comment reply event. The document editing module may generate a reply comment according to the comment reply content included in the comment reply event, or may add the comment reply content to the original comment according to a specific module, which is not limited in this specification.

Referring to fig. 5, a comment notification and a comment reply are described in detail, where fig. 5 is a schematic diagram of an interface of a comment notification message according to an exemplary embodiment, and as shown in fig. 5, the interface mainly includes: a messaging interface 502, a comment notification message 504, a current document title 506, comment content 508, a target user 510, a reply button 512, a reply content input box 514, and a send button 516. After the local user performs comment operation on the current document, the document editing module can generate a comment event and finally send the comment event to the communication module in the client corresponding to the target user for processing. The communication module generates a comment notification message 504 based on a preset comment notification template and displays the comment notification message to the target user in the communication interface 502. In the comment notification message 504, a current document title 506, comment content 508, a target user 510, and a reply button 512 are displayed. Further, after receiving the comment notification message 504, the target user may click on the reply button 512 to input comment reply content in the reply content input box 514, and click on the send button 516 to reply to the comment notification message 504.

In the embodiment, the user can reply the comment content on the communication interface without opening the document, so that data penetration between the comment system and the document system is realized, the user is prevented from jumping back and forth between the systems, the complexity of operation is reduced, and the operation efficiency of the user is improved.

In the aforementioned example of schedule creation, the schedule created by the schedule module contains an access link to the table, and the target user can open the table by clicking on the access link, which can also be applied to other events to be processed.

In an embodiment, the pending event includes an access link of a current document, and a target function module in a client corresponding to a target user processes the pending event, including: responding to the trigger operation of the target user on the access link, sending the access link to the target server by a target function module in the client corresponding to the target user for analysis, sending a document acquisition request to the document server by the target server according to an analysis result, enabling the document server to determine the current document based on the document acquisition request and return the current document to a document editing module in the client corresponding to the target user, and enabling the document editing module to open the current document; or responding to the trigger operation of the target user on the access link, analyzing the access link by a target function module in the client corresponding to the target user, and sending a document acquisition request to the document server according to an analysis result, so that the document server determines the current document based on the document acquisition request and returns the current document to a document editing module in the client corresponding to the target user, and the document editing module starts the current document. The triggering operation of the user on the access link may be to click the access link, or to copy the access link and open the access link in a browser, which is not limited in this specification. In the embodiment, the user can directly open the document through the access link without jumping among different systems, so that the complexity of operation is reduced, and the operation efficiency of the user is improved.

Further, the event to be processed includes information of a trigger position corresponding to the trigger operation in the current document, and the document editing module in the client corresponding to the target user opens the current document, including: and positioning the trigger operation at the corresponding trigger position of the current document based on the information of the trigger position. In the case that the event to be processed includes trigger position information, the document editing module of the client corresponding to the target user may locate the trigger position of the current document based on the trigger position information, for example: the user may click on document link 328 in FIG. 3c to open the document and navigate to cell 310 in FIG. 3 b. The embodiment provides a method for rapidly positioning the relevant position of the processing event, so that when a user opens a document through an access link, the relevant position is automatically positioned, the energy of the user is saved, and the use experience of the user is improved.

In one embodiment, the target system comprises a communication system, and the target function module in the client corresponding to the target user comprises a communication module; the method for realizing cross-system data penetration further comprises the following steps: the document editing module receives the member insertion request, and sends a member information acquisition request to the document server based on the member insertion request so as to instruct the document server to request address book data of a local user from a corresponding communication server of the communication module in the communication system; and the document editing module receives address book data returned by the document server and inserts member information contained in the address book data into the current document. The member insertion request may be triggered by a local user performing a certain operation, for example, the user may click a certain option in an application program, or the user may trigger through voice or the like, although the condition for triggering the member insertion request is not limited thereto, and this specification does not limit this. The position of the member information insertion may be selected by the user in the current document, or may be a default position in the current document, such as the first row and the first column in the table, the beginning of the document, and the like, which is not limited in this specification. The embodiment realizes data penetration between the communication system and the document system, and the user can insert the member information into the document without manually inputting the member information by acquiring the data from the address list, thereby avoiding skip operation between different systems and improving the operation efficiency of the user.

Further, the local user may or may not select the requested address book data.

In one embodiment, the document editing module receives address list member information returned by a document server, determines a target member selected by a local user based on the address list member information and sends the target member to the document server; the document editing module receives address book data returned by the document server, and the method comprises the following steps: and the document editing module receives address book data corresponding to the target member sent by the document server. Compared with the address book data, the target member not only contains member information, but also contains group information, so that the selected target member needs to be sent to the document server by the document editing module, and the document server forwards the selected target member to the communication server for re-determination. The mode for providing the address book member information to the local user for selection by the document editing module may be as follows: the document editing module calls a pre-deployed interface generation function to process the address book member information, and generates a member selection interface for a local user to select, although the selection interface is not the only selection mode, and the description does not limit the selection mode. According to the embodiment, on the basis of inserting the member information contained in the address book data into the document, the right for selecting member information insertion is provided for the user, and the use experience of the user is improved.

Referring to fig. 6a and fig. 6b, a method for inserting member information is described in detail, where fig. 6a is a schematic diagram of a member selection interface provided in an exemplary embodiment, and as shown in fig. 6a, the member selection interface includes: a search box 602, an individual member option 604, a group member option 606, a checkcircle 608, and an insert member information button 610. Member options such as an individual member option 604 and a group member option 606 are listed on the right side of the member selection interface for the user to select, each member option is enlarged to be a check ring 608 for the user to check, the left side of the interface is a search box 602, and the user can search for the member in the search box 602 to check or directly check in the member option on the right side of the interface. As shown in fig. 6a, the user checks the individual member option 604 and the group member option 606, and then clicks the insert member information button 610 to determine the selected target member, which is finally sent to the communication server, and the communication server can identify the target member. Since the group member option 606 is group member information, it is replaced with member information associated with the group, and address book data corresponding to the target member is determined and returned to the document editing module. Fig. 6b is a schematic diagram of a member information insertion interface according to an exemplary embodiment, where as shown in fig. 6b, the member information insertion interface includes: selected cell 612, insert member pinkish 614, insert member pinkish 616, insert member pinkish 618, and insert member pinkish 620. Insert member pinkish 614, insert member pinkish 616, insert member pinkish 618, and insert member pinkish 620 are inserted into the selected cell 612, insert member pinkish 614 corresponding to the individual member option 604, insert member pinkish 616, insert member pinkish 618, and insert member pinkish 620 corresponding to the group member option 606.

Fig. 7 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 7, at the hardware level, the apparatus includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a non-volatile storage 710, although hardware required for other functions may be included. One or more embodiments of the present description can be implemented in software, such as by the processor 702 reading corresponding computer programs from the non-volatile storage 710 into the memory 708 and then executing. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 8, an apparatus for implementing cross-system data penetration may be applied to the device shown in fig. 8 to implement the technical solution of the present specification. The device for realizing cross-system data penetration is applied to a client of an application program, and a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated in the client; the device for realizing cross-system data penetration can comprise:

the generating unit 802 is configured to, in response to a trigger operation of a local user on a current document, generate a corresponding to-be-processed event related to a target user by the document editing module.

A sending unit 804, configured to send the to-be-processed event to a document server corresponding to the document editing module in the document system by the document editing module, and forward the to-be-processed event to a target server in the target system by the document server, so that the target server further forwards the to-be-processed event to a target function module in a client corresponding to the target user for processing.

Optionally, the sending unit 804 is specifically configured to:

the document editing module acquires the document information of the current document and generates a corresponding to-be-processed event related to a target user according to the document information; and/or the presence of a gas in the gas,

and the document editing module acquires user input information provided by the local user and generates a corresponding to-be-processed event related to a target user according to the user input information.

Optionally, the trigger operation has a corresponding trigger position in the current document; wherein the document information includes: the document content in the current document corresponding to the trigger position.

Optionally, the sending unit 804 is specifically configured to:

the event to be processed comprises a reminding event, and the reminding event comprises an ending moment;

the processing of the event to be processed by a target function module in the client corresponding to the target user comprises the following steps: and sending a prompt to the target user according to the ending moment.

Optionally, the event to be processed includes: schedule creation event the proxy creates an event.

Optionally, the sending unit 804 is specifically configured to:

the to-be-processed events comprise comment events, and the comment events comprise comment contents;

the processing of the event to be processed by a target function module in the client corresponding to the target user comprises the following steps: providing the comment content to the target user.

Optionally, the method further includes:

the processing unit 806 is configured to receive, by the document editing module, a comment reply event sent by the document server, and process the comment reply event;

the comment reply event is generated by a target function module in the client corresponding to the target user according to reply operation of the target user on the comment content, and the comment reply event is acquired by the target server from the target function module in the client corresponding to the target user and then forwarded to the document server.

Optionally, the target system includes a communication system, the target function module in the client corresponding to the target user includes a communication module, and the method further includes:

a requesting unit 808, configured to receive a member insertion request by the document editing module, send a member information obtaining request to the document server based on the member insertion request, so as to instruct the document server to request address book data of the local user from a corresponding communication server of the communication module in the communication system;

the inserting unit 810 is configured to receive, by the document editing module, the address book data returned by the document server, and insert member information included in the address book data into the current document.

Optionally, the method further includes:

a determining unit 812, configured to receive address book member information returned by the document server, determine a target member selected by the local user based on the address book member information, and send the target member to the document server by the document editing module;

the insertion unit 810 is specifically configured to: the document editing module receives the address book data returned by the document server, and the method comprises the following steps: and the document editing module receives address book data corresponding to the target member sent by the document server.

Optionally, the to-be-processed event includes an access link of the current document;

the sending unit 804 is specifically configured to:

responding to the trigger operation of the target user on the access link, sending the access link to the target server by a target function module in the client corresponding to the target user for analysis, sending a document acquisition request to the document server by the target server according to an analysis result, enabling the document server to determine the current document based on the document acquisition request and return the current document to a document editing module in the client corresponding to the target user, and enabling the document editing module to open the current document; alternatively, the first and second electrodes may be,

responding to the trigger operation of the target user on the access link, analyzing the access link by a target function module in the client corresponding to the target user, and sending a document acquisition request to the document server according to an analysis result, so that the document server determines the current document based on the document acquisition request and returns the current document to a document editing module in the client corresponding to the target user, and the document editing module starts the current document.

Optionally, the event to be processed includes information of a trigger position corresponding to the trigger operation in the current document;

the sending unit 804 is specifically configured to: and positioning the trigger operation at the corresponding trigger position of the current document based on the information of the trigger position.

The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium, that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus comprising the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein in one or more embodiments to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if," as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A method for realizing cross-system data penetration is characterized in that the method is applied to a client of an application program, and a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated in the client; the method comprises the following steps:

the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed to a target function module in a client corresponding to the target user for processing.

2. The method of claim 1, wherein the document editing module generates a corresponding pending event associated with a target user, comprising:

3. The method of claim 2, further comprising:

the triggering operation has a corresponding triggering position in the current document; wherein the document information includes: the document content in the current document corresponding to the trigger position.

4. The method of claim 1, wherein the pending event comprises a reminder event, the reminder event comprising an expiration time;

5. The method of claim 4, wherein the pending event comprises: schedule creation events, event creation proxies.

6. The method of claim 1, wherein the pending event comprises a comment event, the comment event containing comment content;

7. The method of claim 6, further comprising:

the document editing module receives a comment reply event sent by the document server and processes the comment reply event;

8. The method of claim 1, wherein the target system comprises a communication system, and the target function module in the client corresponding to the target user comprises a communication module; the method further comprises the following steps:

the document editing module receives a member insertion request, and sends a member information acquisition request to the document server based on the member insertion request so as to instruct the document server to request address book data of the local user from a corresponding communication server of the communication module in the communication system;

and the document editing module receives the address book data returned by the document server and inserts member information contained in the address book data into the current document.

9. The method of claim 8,

the method further comprises the following steps: the document editing module receives address list member information returned by the document server, determines a target member selected by the local user based on the address list member information and sends the target member to the document server;

the document editing module receives the address book data returned by the document server, and the method comprises the following steps: and the document editing module receives address book data corresponding to the target member sent by the document server.

10. The method according to claim 1, wherein the pending event includes an access link of the current document;

the processing of the event to be processed by a target function module in the client corresponding to the target user comprises the following steps: responding to the trigger operation of the target user on the access link, sending the access link to the target server by a target function module in the client corresponding to the target user for analysis, sending a document acquisition request to the document server by the target server according to an analysis result, enabling the document server to determine the current document based on the document acquisition request and return the current document to a document editing module in the client corresponding to the target user, and enabling the document editing module to open the current document; alternatively, the first and second electrodes may be,

11. The method according to claim 10, wherein the pending event comprises information of a trigger position corresponding to the trigger operation in the current document;

the document editing module in the client corresponding to the target user opens the current document, and the method comprises the following steps: and positioning the trigger operation at the corresponding trigger position of the current document based on the information of the trigger position.

12. The device for realizing cross-system data penetration is characterized by being applied to a client of an application program, wherein a document editing module belonging to a document system and a target function module belonging to a target system different from the document system are integrated in the client; the device comprises:

a transmission unit: and the document editing module sends the event to be processed to a document server corresponding to the document editing module in the document system, and the document server forwards the event to be processed to a target server in the target system, so that the target server forwards the event to be processed to a target function module in a client corresponding to the target user for processing.

13. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 1-11 by executing the executable instructions.

14. A computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, carry out the steps of the method according to any one of claims 1-11.