Data processing method and device, electronic equipment, storage medium and program product

Abstract

The invention provides a data processing method and device, electronic equipment, a storage medium and a program product, and relates to the technical fields of cloud technologies, big data and the like. An object link identifier is set for each to-be-added object, so that the corresponding to-be-added object is uniquely identified in a target service link; sending an import request to a server based on the object contact information and the object link identifier of each to-be-added object; and sending an invitation request for joining the target service link to each object to be joined by the server. Moreover, the corresponding object can be uniquely positioned through the object link identifier of the added object sent by the server, so that the added object in each to-be-added object can be effectively distinguished, and the adding progress condition can be clearly and specifically displayed based on the object contact information of the added object. Therefore, the first device can accurately and clearly sense the joining condition of the related object, and the accuracy of the determined joining progress is improved.

Description

Technical Field

[0001] The present application relates to technical fields such as cloud technology and big data, and the present application relates to a data processing method, device, electronic device, storage medium and program product. Background Art

[0002] Some office applications can provide cross-enterprise collaboration functions by building business chains, such as enterprise members who join the business chain can communicate and collaborate without adding each other as friends. For example, business chain A may include enterprise 1, enterprise 2, and enterprise 3; among them, enterprise 1 can create a business chain and invite relevant members from enterprise 2 and enterprise 3 to join, thereby successfully building business chain A.

[0003] In the related art, after enterprise 1 creates a business chain and sends an invitation, it needs to wait for the relevant members to accept the invitation before they can successfully join the business chain. During this process, enterprise 1 cannot perceive the joining progress of the relevant members. Therefore, a data processing method that can effectively obtain the joining progress is urgently needed. Summary of the invention

[0004] The present application provides a data processing method, device, electronic device, storage medium and program product. The technical solution is as follows:

[0005] In one aspect, the present application provides a data processing method, which is applied to a first device and includes:

[0006] Obtaining an object link identifier of at least one object to be added in a target service link, wherein the object link identifier is used to uniquely identify a corresponding object to be added in the target service link;

[0007] Based on the object contact information and object link identifier of each object to be added, sending an import request to the server, wherein the import request indicates sending an invitation request to the corresponding object to be added, wherein the invitation request is used to invite the corresponding object to be added to join the target service link;

[0008] receiving an object link identifier of a joined object sent by the server, and determining object contact information of the joined object based on the received object link identifier, wherein the joined object is an object among the objects to be joined that joins the target service link based on an invitation request;

[0009] Based on the object contact information of the added objects, the progress indication information of the target service link is displayed, and the progress indication information indicates the joining progress of each of the objects to be added to the target service link.

[0010] In one possible implementation, the method further includes:

[0011] Associatively storing the corresponding relationship between the object link identifier and the object contact information of each object to be added;

[0012] The determining the object contact information of the added object based on the received object link identifier includes:

[0013] Based on the object link identifier of the added object, the object contact information of the added object is obtained from the corresponding relationship stored in association.

[0014] On the other hand, the present application provides a data processing method, which is applied to a server and includes:

[0015] receiving an import request sent by the first device, and acquiring object contact information and an object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request;

[0016] Based on the object contact information of each of the objects to be added and the link identifier of the target service link, an invitation request is sent to the corresponding object to be added, where the invitation request is used to invite the corresponding object to be added to join the target service link;

[0017] receiving a confirmation message fed back by each of the objects to be added based on the invitation request, and adding each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added;

[0018] Send the object link identifier of the joined object to the first device, so that the first device displays the progress indication information of the target service link based on the object link identifier of the joined object, and the progress indication information indicates the joining progress of each object to be joined to the target service link; the joined object is an object among the objects to be joined that joins the target service link based on an invitation request.

[0019] On the other hand, the present application provides a data processing apparatus, which is applied to a first device, and includes:

[0020] A first acquisition module, configured to acquire an object link identifier of at least one object to be added in a target service link, wherein the object link identifier is used to uniquely identify the corresponding object to be added in the target service link;

[0021] An import request sending module, used to send an import request to the server based on the object contact information and object link identifier of each object to be added, wherein the import request indicates sending an invitation request to the corresponding object to be added, and the invitation request is used to invite the corresponding object to be added to join the target service link;

[0022] A first receiving module is configured to receive an object link identifier of a joined object sent by the server, and determine object contact information of the joined object based on the received object link identifier, wherein the joined object is an object among the objects to be joined that joins the target service link based on an invitation request;

[0023] The progress display module is used to display the progress indication information of the target service link based on the object contact information of the added object, wherein the progress indication information indicates the joining progress of each of the to-be-added objects in joining the target service link.

[0024] In a possible implementation, for each object to be added, a method for obtaining the object link identifier of the object to be added includes any one of the following:

[0025] Acquire an unoccupied identification number from a plurality of identification numbers corresponding to the target service link as the object link identification number of the object to be added, wherein the unoccupied identification number is an identification number among the plurality of identification numbers that is not currently used by any object;

[0026] An object link identifier of the object to be added is generated based on the object identifier, the enterprise identifier and the link identifier of the target service link of the object to be added.

[0027] In a possible implementation, the first receiving module is used for any of the following:

[0028] Sending a first query request to a server based on the object identifier, enterprise identifier and link identifier of the target business link of each of the objects to be added; receiving the object link identifier of the added object returned by the server based on the first query request, wherein the first query request is used to query the objects added to the target business link among the objects to be added;

[0029] In response to the confirmation message fed back by each object to be added to the server based on the invitation request, a notification message fed back by the receiving server based on each confirmation message is received, and the object link identifier of the added object is obtained based on the notification message, and the notification message is used to notify each object to be added whether to join the target service link.

[0030] In a possible implementation, the progress display module is used for at least one of the following:

[0031] Based on the object contact information of the added objects, counting and displaying the number of people who have joined the target service link in each of the objects to be added, wherein the progress indication information includes the number of people who have joined;

[0032] Displaying the object contact information of the added object as the progress indication information;

[0033] Based on the object contact information of the added objects, the number of non-joined persons who have not joined the target service link in each of the to-be-joined objects is counted and displayed, and the progress indication information includes the number of non-joined persons.

[0034] In a possible implementation, the device further includes a business collaboration module, and the business collaboration module is used to:

[0035] Sending a service collaboration request to the server, wherein the service collaboration request is used to request initiation of a multi-person collaboration service in the target service link, wherein the target service link includes a plurality of joined objects;

[0036] In response to the object collaboration progress fed back by each of the joined objects to the server, receiving the object link identifier of the first object sent by the server, the first object is a joined object whose object collaboration progress is a target progress, and the object collaboration progress is the completion progress of the single-person service corresponding to the multi-person collaboration service;

[0037] The object contact information of the first object is obtained based on the object link identifier of the first object, and the business progress information of the target collaborative business is displayed based on the object contact information of the first object.

[0038] In one possible implementation, the device further includes:

[0039] An association storage module, used for associating and storing the corresponding relationship between the object link identifier and the object contact information of each object to be added;

[0040] The first receiving module is used for:

[0041] Based on the object link identifier of the added object, the object contact information of the added object is obtained from the corresponding relationship stored in association.

[0042] On the other hand, the present application provides a data processing device, which is applied to a server, and includes:

[0043] A second receiving module, configured to receive an import request sent by the first device, and acquire object contact information and an object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request;

[0044] An invitation request sending module, used for sending an invitation request to a corresponding object to be added based on the object contact information and link identifier of each object to be added, wherein the invitation request is used to invite the corresponding object to be added to join the target service link;

[0045] A third receiving module is used to receive a confirmation message fed back by each of the objects to be added based on the invitation request, and add each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added;

[0046] The first sending module is used to send the object link identifier of the added object to the first device, so that the first device displays the progress indication information of the target business link based on the object link identifier of the added object, and the progress indication information indicates the joining progress of each object to be joined to the target business link; the added object is an object among the objects to be joined that joins the target business link based on an invitation request.

[0047] In a possible implementation, the device further includes a verification module, wherein the verification module is configured to:

[0048] Based on the first object table and the object contact information of each object to be added, verifying the object link identifier of each object to be added, wherein the first object table stores the objects included in the target service link;

[0049] For each object to be added, if the object link identifier of the object to be added passes the verification, the correspondence between the object contact information and the object link identifier of the object to be added is associated and stored in the second object table, and the second object table is used to store the objects to be added to the target service link.

[0050] In a possible implementation, the verification module is used to:

[0051] For each object to be added, obtaining a target enterprise where the object to be added is located based on the object contact information of the object to be added;

[0052] Extracting each target object belonging to the target enterprise from the first object table;

[0053] The object link identifiers between the object to be added and each target object are compared respectively, and based on the comparison results between the object to be added and each target object respectively, a verification result corresponding to the object to be added is obtained.

[0054] In a possible implementation, the third receiving module is configured to:

[0055] In response to receiving a confirmation message of any object to be added, the correspondence between the object contact information and the object link identifier of any object to be added is stored in the first object table, and the object contact information and the object link identifier of any object to be added are deleted from the second object table.

[0056] In a possible implementation, the device further includes a business collaboration module, and the business collaboration module is used to:

[0057] Receive a service collaboration request sent by the first device, and send service information for a multi-person collaboration service to each of the joined objects based on the service collaboration request, wherein the service collaboration request is used to request initiation of a multi-person collaboration service in the target service link, and the target service link includes multiple joined objects;

[0058] In response to receiving the object collaboration progress feedback from each of the joined objects, the object link identifier of the first object is sent to the first device, so that the first device displays the business progress information of the target collaboration business based on the object link identifier of the first object; the first object is a joined object whose object collaboration progress is the target progress, and the object collaboration progress is the completion progress of the single-person business corresponding to the multi-person collaboration business.

[0059] In one possible implementation, the device further includes:

[0060] A second sending module, configured to send the correspondence between the object link identifier and the object contact information of each of the added objects to a second device, where the second device is a device where the object with the management role in each of the added objects is located;

[0061] The business collaboration module is used to:

[0062] In response to receiving the object collaboration progress fed back by each of the joined objects, the object link identifier of the first object is sent to the second device, so that the second device displays the service progress information of the target collaborative service based on the object link identifier of the first object.

[0063] On the other hand, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the above-mentioned data processing method.

[0064] On the other hand, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned data processing method is implemented.

[0065] On the other hand, a computer program product is provided, comprising a computer program, wherein the computer program implements the above data processing method when executed by a processor.

[0066] The beneficial effects of the technical solution provided by the embodiment of the present application are:

[0067] The data processing method provided by the present application sets an object link identifier for each object to be added, so as to uniquely identify the corresponding object to be added in the target business link; and sends an import request to the server based on the object contact information and object link identifier of each object to be added; so that the server sends an invitation request to join the target business link to each object to be added. In addition, the object link identifier of the added object sent by the server can uniquely locate the corresponding object, thereby effectively distinguishing the added object from each object to be added, and the object contact information of the added object can clearly and specifically display the joining progress, so that the first device can accurately and clearly perceive the joining status of the relevant object, thereby improving the accuracy of the determined joining progress. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0069] Figure 1 A schematic diagram of an implementation environment of a data processing method provided in an embodiment of the present application;

[0070] Figure 2 A flowchart of a data processing method provided in an embodiment of the present application;

[0071] Figure 3 A schematic diagram of an application page of an office application provided in an embodiment of the present application;

[0072] Figure 4 A flowchart of a data processing method provided in an embodiment of the present application;

[0073] Figure 5 A schematic diagram of a verification process of an object link identifier provided in an embodiment of the present application;

[0074] Figure 6 A schematic diagram of an object link identifier migration provided in an embodiment of the present application;

[0075] Figure 7 A schematic diagram of an identification information conversion process provided in an embodiment of the present application;

[0076] Figure 8 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0077] Fig. 9 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0078] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0079] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0080] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said", and "the" used herein may also include plural forms. The terms "include" and "comprise" used in the embodiments of the present application mean that the corresponding features can be implemented as the presented features, information, data, steps, and operations, but do not exclude the implementation as other features, information, data, steps, operations, etc. supported by the technical field.

[0081] It can be understood that in the specific implementation of the present application, any object-related data involving the target business link, the object contact information of the object, the object link identifier, the enterprise identifier, the link identifier, the object information, the business information, the joining progress or the business progress, when the above embodiments of the present application are applied to specific products or technologies, it is necessary to obtain the object's permission or consent, and the collection, use and processing of the relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0082] The following is an introduction and explanation of the terms and related technologies involved in this application:

[0083] Target business link: It is a business link composed of various object sets with business collaboration relationships. An object set can be an enterprise or organization composed of multiple objects with association relationships. For example, an object set can be an enterprise, a business department in an enterprise, a group, an organization, etc. A business link can be an upstream and downstream space.

[0084] Upstream and downstream: A cross-enterprise address book used for B2B (Business-to-Business) collaboration in office applications. Objects added to the upstream and downstream can communicate and collaborate without adding each other as friends; usually, an upstream and downstream may include one upstream enterprise and multiple downstream enterprises.

[0085] Upstream enterprises: Generally, those involved in the collaboration process are upstream distributors and brands; upstream enterprises can create upstream and downstream.

[0086] Downstream enterprises: After the upstream enterprise creates upstream and downstream, the downstream enterprise can join the upstream and downstream to collaborate and communicate with the upstream enterprise. Downstream enterprises are generally suppliers, and one upstream enterprise generally collaborates with multiple downstream enterprises.

[0087] Chain ID: chainid, a unique identifier for a single upstream and downstream in office applications.

[0088] Object link identifier: When an upstream enterprise imports downstream enterprise members through Excel / API, a unique ID is set for the downstream enterprise members within the downstream enterprise; it can be a custom ID.

[0089] userid: The unique ID of an enterprise-defined user within the enterprise.

[0090] corpid: A unique identifier for a single enterprise within an office application.

[0091] vid: a unique identifier for a single user within an office application.

[0092] External chainid: It is the encrypted chainid, which is the unique identifier of a single upstream and downstream.

[0093] External corpid: It is the encrypted corpid, which is the unique identifier of a single enterprise.

[0094] Figure 1 A schematic diagram of an implementation environment of a data processing method provided in this application. Figure 1 As shown, the implementation environment includes: a server 11, a first device 12 and a second device 13. The server 11 may be a background server of an office application. The first device 12 and the second device 13 are installed with office applications.

[0095] This office application has business collaboration functions, such as providing upstream and downstream services. Upstream and downstream is a business space where an enterprise gathers certain partners, and its core is the upstream and downstream address book and shared applications. The upstream and downstream function supports collaboration between users who join the upstream and downstream. For example, if a user joins a certain upstream and downstream, the user can click on the upstream and downstream in the client of the target application to view the address books and shared applications shared between the enterprises or members within the enterprise in the upstream and downstream. Users who join the upstream and downstream can collaborate on business through shared address books, applications, etc.

[0096] In the present application, the first device 12 is a device that creates upstream and downstream and initiates an import request. For example, the first device 12 can be a management platform device in an upstream enterprise that is used to uniformly manage the application clients of various objects in the upstream enterprise; or, it can also be a device where an object of a management role is located in an upstream enterprise; or, it can also be a device where any object in the upstream enterprise that has joined the target business link is located. The import request indicates that an invitation request is sent to the corresponding object to be added, and the invitation request is used to invite the corresponding object to be added to join the target business link.

[0097] The third device 13 may be a device where the object to be added is located.

[0098] In an example of a possible scenario, if the first device 12 creates an upstream and downstream and sends an import request to the server 11, the server 11 may send an invitation request to the second device 13 based on the import request. The second device 13 may feedback a confirmation message of the object to be added to the server 11 based on the invitation request. The server 11 may add the corresponding object to be added to the target business link based on the received confirmation message; and return the object link identifier of the added object to the first device 12. The first device 12 may determine the object contact information of the added object based on the received object link identifier, and display the joining progress of each object to be added based on the object contact information of the added object; for example, display the number of objects added to the upstream and downstream A, or display the object contact information of the newly added object whenever there is a new object added.

[0099] The server 11 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server or server cluster that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, and big data and artificial intelligence platforms. The first device 12 and the second device 13 may be terminals, and the terminals may be smart phones, tablet computers, laptop computers, digital broadcast receivers, desktop computers, vehicle terminals (such as vehicle navigation terminals, vehicle computers, etc.), smart speakers, smart watches, etc. The terminal and the server may be directly or indirectly connected via wired or wireless communication, and may also be determined based on the actual application scenario requirements, which is not limited here.

[0100] Figure 2 The flowchart of a data processing method provided in the embodiment of the present application is shown in FIG. The execution subject of the method may be a first device. Figure 2 As shown, the method includes the following steps 201-204.

[0101] Step 201: A first device obtains an object link identifier of at least one object to be added in a target service link.

[0102] The object link identifier is used to uniquely identify the corresponding object to be added in the target business link. The target business link can be a business link composed of a set of objects that have a collaborative relationship with the target business. For example, the target business link can be an upstream and downstream space, and an object set can be an enterprise or a business department in an enterprise, etc. In this application, the upstream enterprise can create upstream and downstream, and initiate an import request to import each member of the downstream enterprise into the target business link, thereby constructing an upstream and downstream space for business collaboration between the upstream enterprise and the downstream enterprise.

[0103] In a possible implementation, the object link identifier may be a unique identifier of an object in a specified service link. The object link identifier may be obtained based on an identifier set of the service link or various identifier information of the object. Exemplarily, for each object to be added, the object link identifier of the object to be added is obtained by any one of the following methods 1 and 2:

[0104] Mode 1: The first device obtains an unoccupied identification number from multiple identification numbers corresponding to the target service link as the object link identification of the object to be added, where the unoccupied identification number is an identification number among the multiple identification numbers that is not currently used by any object;

[0105] Mode 2: The first device generates an object link identifier of the object to be added based on the object identifier, the enterprise identifier and the link identifier of the target service link of the object to be added.

[0106] In method 1, the target service link may correspond to an identification number set, which includes multiple identification numbers for uniquely identifying an object added to the target service link. Each time an object to be added is pulled to join the target service link, an unoccupied identification number may be classified for each object to be added. For example, the maximum object capacity of the target service link is 1000, that is, a maximum of 1000 objects can be added to the target service link, then the identification number set may include identification numbers 1, 2, 3...999, 1000, for a total of 1000 identification numbers. The first device may record the usage status of each identification number in the identification number set so as to assign an unoccupied identification number to each object to be added.

[0107] In mode 2, the first device may obtain the object identifier and enterprise identifier of each object to be added in advance, and calculate the object identifier, enterprise identifier and link identifier of the target service link of each object to be added according to the preconfigured algorithm to generate the object link identifier of the object to be added. For example, the hash value of the object identifiers userid, corpid and chainid may be calculated, and the hash value may be used as the object link identifier.

[0108] Step 202: The first device sends an import request to the server based on the object contact information and object link identifier of each object to be added.

[0109] The import request indicates sending an invitation request to the corresponding object to be added, and the invitation request is used to invite the corresponding object to be added to join the target service link. The import request may carry the object contact information and object link identifier of each object to be added.

[0110] It should be noted that the object contact information of an object may be information used to contact the object in the upstream and downstream. Exemplarily, the object contact information may include but is not limited to the information of the object, the information of the enterprise to which the object belongs, etc.; the information of the object may include but is not limited to the name of the object, the object identifier (such as userid), the contact information of the object, the role type of the object (is it the person in charge of the management role, or the ordinary member of the non-management role, etc.); the information of the enterprise to which the object belongs may include but is not limited to the enterprise name, enterprise identifier (such as corpid), the upstream and downstream grouping information of the enterprise, etc.

[0111] In one example, the first device may generate a request data packet based on object contact information and object link identifiers of multiple objects to be added, and call a preconfigured import interface API based on the request data packet to request the server to send an invitation request to each object to be added.

[0112] For example, a request data packet including data of multiple objects to be added may be in the following form:

[0113]

[0114]

[0115] The meanings of the codes in the request data packet are as follows:

[0116] chain_id: is the upstream and downstream id, and the objects to be added can be imported into the upstream and downstream in batches.

[0117] contact_list: is the upstream and downstream contact list. The contacts in this list will be imported into the upstream and downstream.

[0118] contact_list.corp_name: is the name of the upstream and downstream enterprises, such as xxx enterprise.

[0119] contact_list.group_path: It is the group where the enterprise is located after import, that is, the corresponding group of the enterprise where the object to be added is located in the upstream and downstream.

[0120] contact_list.custom_id: is the object link identifier of the object to be added, such as the object Zhang San's identification number in the upstream and downstream is 100, and the object Li Si's identification number in the upstream and downstream is 101. The object link identifier can be a custom id set for the object to be added.

[0121] contact_list.contact_info_list: is the information list of the upstream and downstream objects to be added.

[0122] contact_list.contact_info_list.name: is the name of the object to be added.

[0123] contact_list.contact_info_list.identity_type: is the role type of the object to be added. 1 indicates that the role type is a member, and 2 indicates that the role type is a management role, such as the person in charge.

[0124] contact_list.contact_info_list.mobile: is the mobile phone number.

[0125] In another example, the first device may generate a document for calling an interface, such as an Excel table, based on object contact information and object link identifiers of multiple objects to be added; and call an import interface API based on the data file to request the server to send an invitation request to each object to be added.

[0126] For example, the Excel table of the calling interface may be as shown in Table 1 below:

[0127] Table 1

[0128]

[0129]

[0130] It should be noted that the server can obtain the object contact information and object link identifier of each object to be added based on the import request, and send an invitation request to each object to be added to invite each object to be added to join the target service link.

[0131] For the object to be added, such as Figure 3 As shown, after receiving the invitation request from the server, the second device where it is located can display the notification message of the invitation request in the page of the office application, and display the inviter, that is, the company name of the upstream company "distributor of xxx company" in the invitation page, and can also display a join button for confirming to join the upstream and downstream. In addition, it can also support which identity the object to be joined uses to join the upstream and downstream. For example, the invitation page displays the join button corresponding to each candidate identity, such as a join button with the current company identity (such as joining with the current xx company identity), a join button with other company identities, etc.

[0132] like Figure 3As shown, when the object to be joined triggers the join button, the second device can feedback a confirmation message to the server, and display a notification page based on the notification message returned by the server indicating whether the joining is successful; such as displaying a notification page of "Distributors who have joined xxx company", the notification page can also display an entry for pulling other colleagues to join the upstream and downstream, such as a button of "Go to the office application client to add colleagues".

[0133] Step 203: The first device receives the object link identifier of the added object sent by the server, and determines the object contact information of the added object based on the received object link identifier.

[0134] The joined object is an object that joins the target service link based on an invitation request among the objects to be joined. In one example, the server can feed back the joining dynamics of each object to be joined to the first device in real time. In another example, the first device can also actively send a query request to the server to query the currently joined objects. Accordingly, in step 203, the implementation method of the first device obtaining the object link identifier of the joined object can include any one of the following methods 1 and 2.

[0135] Mode 1: The first device sends a first query request to the server based on the object identifier, enterprise identifier and link identifier of the target business link of each object to be added; receives the object link identifier of the added object returned by the server based on the first query request, and the first query request is used to query the object added to the target business link among the objects to be added;

[0136] Method 2: The first device responds to the confirmation message fed back by each object to be joined to the server based on the invitation request, receives the notification message fed back by the server based on each confirmation message, and obtains the object link identifier of the joined object based on the notification message, and the notification message is used to notify each object to be joined whether to join the target service link.

[0137] In mode 1, the first device can generate a request data packet corresponding to the query request based on the object identifier, enterprise identifier and link identifier of the target business link of each object to be added, and send the request data packet to the server based on the preconfigured query interface. The server obtains the link identifier to be queried, the object identifier and enterprise identifier of each object to be added, and queries whether the object to be added is added to the target business link based on the request data packet corresponding to the query request, and queries whether the object to be added is added to the target business link; based on the query result, the server feeds back to the first device the object link identifier of each object to be added.

[0138] For example, the query request packet may be as follows:

[0139]

[0140] Among them, userid is the object ID of the object to be added to be queried; corpid is the ID of the enterprise where the object to be added to be queried is located; chain_id is the upstream and downstream ID.

[0141] In mode 2, whenever the server adds any object to be added to the target service link based on a confirmation message fed back by any object to be added, the server can send the object link identifier of any object to be added (that is, the object that has been added) to the first device. The first device receives the object link identifier of the object that has been added.

[0142] In a possible implementation, after the first device obtains the object link identifier of each object to be added, the following steps may be further performed: the first device associates and stores the corresponding relationship between the object link identifier of each object to be added and the object contact information. Accordingly, in step 203, the implementation of determining the object contact information of the added object based on the received object link identifier may include: the first device acquires the object contact information of the added object from the associated stored corresponding relationship based on the object link identifier of the added object.

[0143] Step 204: The first device displays progress indication information of the target service link based on the object contact information of the added object.

[0144] The progress indication information indicates the progress of each object to be added to the target service link. The first device can clearly identify the specific information of the object and which objects among the objects to be added have currently joined the target service link based on the object contact information of the objects that have joined.

[0145] In one possible manner, the progress indication information may include the number of people who have joined, the object contact information of the objects who have joined, or the number of people who have not joined, etc. Accordingly, the implementation of step 204 may include at least one of the following:

[0146] The progress indication information includes the number of people who have joined; the first device counts and displays the number of people who have joined the target service link in each of the objects to be joined based on the object contact information of the objects that have joined;

[0147] The progress indication information includes object contact information of the added object; the first device displays the object contact information of the added object as the progress indication information;

[0148] The progress indication information includes the number of non-joined persons; the first device counts and displays the number of non-joined persons who have not joined the target service link in each of the objects to be joined based on the object contact information of the joined objects.

[0149] In some possible examples, the progress indication information may also include: the number of people who have joined or not joined in each enterprise, the proportion of people who have joined in each object to be joined, etc. For example, each object to be joined may be a member of a plurality of different enterprises; the first device may also count the number of people who have joined or not joined in each enterprise based on the object contact information of each object to be joined. For another example, the first device may also count the proportion of people who have joined in each object to be joined, such as 80% of the objects to be joined have joined the target service link.

[0150] Of course, the progress indication information may also include any other information that can represent the progress of joining. This application only uses the above-mentioned examples for illustration, and the specific information content of the progress indication information is not limited in this application. For example, the progress indication information also includes a progress bar, and the progress bar is marked with a progress status, which may be the proportion of people who have joined or a full state, etc.

[0151] In some embodiments, when using the target business link for business collaboration, the object link identifier of each object can also be used to provide real-time feedback on the completion progress of each object in the business assistance process. Exemplarily, after the first device invites each object to join the target business link based on the import request, the process of the first device initiating a multi-person collaborative business and querying the collaboration progress of each object includes the following steps S1 to S3:

[0152] Step S1: The first device sends a service collaboration request to the server.

[0153] The service collaboration request is used to request to initiate a multi-person collaboration service in the target service link, and the target service link includes multiple joined objects.

[0154] Step S2: The first device receives the object link identifier of the first object sent by the server in response to the object collaboration progress fed back by each of the joined objects to the server.

[0155] The first object is a joined object whose object collaboration progress is a target progress, and the object collaboration progress is the completion progress of the corresponding single-person business in the multi-person collaboration business.

[0156] Exemplarily, the multi-person collaboration service includes, but is not limited to, collaboration services such as online document multi-person collaboration or multi-person online conference. The multi-person collaboration service may include a portion of business content that each joined object needs to collaborate to complete. Based on the business collaboration request initiated by the first device, the server sends business information of the multi-person collaboration service to each joined object; for example, an online document link that needs to be filled in by multiple people, or an online conference link that needs to be attended by multiple people. Each joined object can complete its corresponding part of the business content based on the information sent by the server, and feedback the completion progress to the server, that is, the object collaboration progress.

[0157] Exemplarily, the object collaboration progress indicates the completion status of the object for the corresponding part of the business in the multi-person collaboration business. The object collaboration progress may include: not started, in progress, and completed.

[0158] In one example, the target progress may be completed; the server may also filter out the first object of the target progress based on the object collaboration progress of each object that has been added, and send the object link identifier of the first object to the first device. Based on this, the server may feed back the identifier of the completed object in the multi-person collaboration service to the first device in real time.

[0159] In another example, the server may receive and send the object collaboration progress of each added object to the first device, for example, sending the object link identifier and the object collaboration progress of each added object to the first device.

[0160] Step S3: The first device obtains the object contact information of the first object based on the object link identifier of the first object, and displays the service progress information of the target collaborative service based on the object contact information of the first object.

[0161] The first device can determine the object contact information of the first object based on the object link identifier of the first object; and generate the business progress information based on the object contact information of the first object; for example, the business progress information may include but is not limited to: object contact information such as the name and company of the completed object, the number of completed people, the proportion of completed people, etc.

[0162] It should be noted that, in view of the problem that after the upstream enterprise imports the downstream enterprise in the related technology, it is impossible to efficiently, accurately and reliably obtain the progress of the downstream enterprise members joining. In this application, firstly, by using Excel documents or requesting data packets to import downstream enterprise members in the upstream enterprise, the upstream enterprise is supported to set the object link identifier for the object to be added, such as setting a member custom id to uniquely identify the corresponding object to be added in the target business link; secondly, after the downstream enterprise members join the upstream and downstream, the member custom id of the downstream enterprise members is bound to the upstream and downstream through the server; finally, when the upstream enterprise receives the downstream enterprise member joining through the server, the corresponding member custom id can be obtained through the userid, external chainid, and external corpid, and the only downstream enterprise member in the upstream and downstream can be further accurately located, so as to accurately know the progress of the downstream enterprise members joining. It is convenient for upstream enterprises to efficiently, accurately and reliably obtain the progress of downstream enterprise members joining, so that upstream enterprises can quickly understand the joining status of downstream enterprise members, and then conveniently communicate and share applications with their dealers, suppliers, and partners to achieve efficient business collaboration.

[0163] The data processing method provided by the present application sets an object link identifier for each object to be added, so as to uniquely identify the corresponding object to be added in the target business link; and sends an import request to the server based on the object contact information and object link identifier of each object to be added; so that the server sends an invitation request to join the target business link to each object to be added. In addition, the object link identifier of the added object sent by the server can uniquely locate the corresponding object, thereby effectively distinguishing the added object from each object to be added, and the object contact information of the added object can clearly and specifically display the joining progress, so that the first device can accurately and clearly perceive the joining status of the relevant object, thereby improving the accuracy of the determined joining progress.

[0164] Figure 4 The flowchart of a data processing method provided in the embodiment of the present application is shown in FIG. The execution subject of the method may be a server. Figure 4 As shown, the method includes the following steps 401-404.

[0165] Step 401: The server receives an import request sent by a first device, and acquires object contact information and an object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request.

[0166] In this step, the server may also associate and store the corresponding relationship between the object contact information and the object link identifier of each object to be added.

[0167] In a possible implementation, the server may also verify each object link identifier in the import request, and if the verification passes, then associate and store it. The process may include the following steps A1-A2:

[0168] Step A1: The server verifies the object link identifier of each object to be added based on the first object table and the object contact information of each object to be added. The first object table stores the objects included in the target service link.

[0169] Step A2: For each object to be added, if the object link identifier of the object to be added passes the verification, the server associates the correspondence between the object contact information and the object link identifier of the object to be added and stores it in the second object table, where the second object table is used to store the objects to be added to the target service link.

[0170] It should be noted that when the target service link is created, the server can maintain two tables corresponding to the target service link in real time, one is a first object table for maintaining added objects; the other is a second object table for maintaining objects to be added. In each table, the corresponding relationship between the object link identifier and the object contact information of each object is stored in association.

[0171] For example, the second object table may be an upstream and downstream member table to be added, which maintains the members to be added in the upstream and downstream, as shown below:

[0172] message ChainPendingMemberStore

[0173] {

[0174] optional uint64 storeid=1; / / kv auto inc

[0175] optional uint64 gid = 2;

[0176] optional uint64 partyid=3; / / The node of the enterprise to be joined

[0177] optional string name = 4;

[0178] optional uint64 inviter_vid=5;

[0179] optional uint64 createtime=6;

[0180] optional string mobile=7;

[0181] optional uint32 role_type = 8; / / 0, ordinary member, 1 person in charge;

[0182] optional uint32 source = 9; / / 0 default, 1 import

[0183] optional uint64 user_custom_id = 10; / / member custom id

[0184] }

[0185] For another example, the first object table may be an enterprise upstream and downstream table, which is used to maintain members or departments of an enterprise that join the upstream and downstream, as shown below:

[0186] message ChainCorpRangeDB

[0187] {

[0188] optional uint64 autoid=1; / / PKV auto-increment id

[0189] optional uint64 chainid=2;

[0190] optional uint64 id = 3; / / employee vid or partyid

[0191] optional uint64 type = 4; / / id type @ChainCorpRangeType

[0192] optional uint32 source = 5; / / Source @ChainCorpRangeSource

[0193] optional uint32 is_join=6; / / to be confirmed status @ChainJoinStatus

[0194] optional uint64 join_time=7;

[0195] optional uint64 update_time=8;

[0196] optional uint32 import_template_type = 9; / / store the corresponding import type

[0197] optional uint64 user_custom_id = 10; / / member custom id

[0198] }

[0199] Exemplarily, there cannot be a duplicate object link identifier in the target service link, and the server can perform verification based on this. The verification process may include the following steps A11-A13:

[0200] Step A11: for each object to be added, obtaining the target enterprise where the object to be added is located based on the object contact information of the object to be added;

[0201] Step A12, extracting each target object belonging to the target enterprise from the first object table;

[0202] Step A13: Compare the object link identifiers between the object to be added and each target object respectively, and obtain the verification result corresponding to the object to be added based on the comparison results between the object to be added and each target object respectively.

[0203] Exemplarily, the server may obtain the object link identifier of each target object of each enterprise corresponding to the target business link from the first object table; each enterprise corresponding to the target business link may include an enterprise that has currently joined or is about to join the target business link. Each target object of each enterprise may include an object that has joined the target business link.

[0204] Exemplarily, for each object to be added, the object link identifier of the object to be added is compared with the object link identifier of each target object in the target enterprise. If the comparison result shows that the object link identifier of the object to be added is different from that of each target object, the verification is passed. Otherwise, if there is any target object whose object link identifier is the same as that of the object to be added, the verification is not passed.

[0205] It should be noted that the server may store the objects to be added that have passed the verification in the second object table, and send an invitation request to the objects to be added that have passed the verification.

[0206] For the to-be-added object that has not passed the verification, that is, the verification failed object, the server may not store it in the second object table; the server may feedback a notification message to the first device to notify the first device of the object link identifier of the verification failed object. At this time, the first device may re-acquire and send a new object link identifier of the verification failed object to the server, so that the server can re-verify until the verification passes.

[0207] Step 402: The server sends an invitation request to the corresponding object to be added based on the object contact information and link identifier of each object to be added.

[0208] The invitation request is used to invite the corresponding object to be added to join the target service link. In this step, the server may send an invitation request to the second device where each object to be added is located.

[0209] In a possible example, the data format, data content, etc. of each object link identifier may also be verified. For example, the server may verify the object link identifier of each object to be added based on at least one preconfigured condition. The at least one condition may include at least one of the following (1)-(4):

[0210] (1) Positive integers less than or equal to 64 bits, without punctuation or spaces;

[0211] (2) It is not an unencrypted mobile phone number, including: it is not an 11-digit or 13-digit number;

[0212] (3) The same object corresponds to only one object link identifier;

[0213] (4) The same enterprise cannot have duplicate object link identifiers in the target business link.

[0214] like Figure 5 As shown, for example, after receiving the import request, the server may determine the downstream enterprise member to be imported based on the import request, and perform the following steps of checking and writing the object link identifier of the object to be added:

[0215] Step 1. Obtain the enterprises where each downstream enterprise member to be added is located, and pull the object link identifiers of all existing members in each enterprise, such as member custom IDs.

[0216] Step 2. Based on the above conditions (1)-(4), check whether the custom ID format of the object to be added complies with the specifications, whether it is unique in the upstream and downstream lists and the list of objects to be added, and whether it is unique within the enterprise. If the conditions are not met, the import fails.

[0217] Step 3, check whether the member to be added has joined the upstream and downstream. If it has joined, write the custom ID of the member to the first object table, such as the enterprise upstream and downstream table, and maintain the mapping relationship between the userid and the member to be added in the table. If it has not joined, write the member's custom ID to the second object table, such as the upstream and downstream member table to be added, and maintain the mapping relationship between the userid and the member to be added.

[0218] like Figure 5As shown, for example, for each member to be imported, it is possible to check whether the member to be imported has a custom ID for the member. If so, it is further checked whether the format of the custom ID is correct and whether it is unique within the enterprise. If the format is incorrect or it is repeated within the enterprise, the import fails. If the format is correct and unique within the enterprise, it is further confirmed whether the member has joined the upstream and downstream. If so, the member information is written into the enterprise upstream and downstream table; if not, it is written into the upstream and downstream member to be joined table. In addition, if the member to be imported does not have a corresponding custom ID, that is, it is a member that does not need to define an ID, it is directly determined whether the member has joined the upstream and downstream. If so, it is written into the enterprise upstream and downstream table; otherwise, it is written into the to-be-joined table.

[0219] Step 403: The server receives a confirmation message fed back by each of the objects to be added based on the invitation request, and adds each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added.

[0220] In a possible implementation, the server may maintain information of objects added to the target service link in real time through the first object table. Then step 403 may include: in response to receiving a confirmation message of any object to be added, the server associates and stores the corresponding relationship between the object contact information and the object link identifier of any object to be added in the first object table, and deletes the object contact information and the object link identifier of any object to be added from the second object table.

[0221] like Figure 6 As shown, for example, the server may perform the following steps to migrate the custom ID of the added object to the enterprise upstream and downstream tables:

[0222] Step 1. If a message confirming joining is received from a downstream enterprise member, the member custom ID of the downstream enterprise member in the upstream and downstream member-to-be-joined table can be read.

[0223] Step 2: Add the member to the upstream and downstream tables of the enterprise, and associate and store the corresponding relationship between the member's object contact information and the custom ID.

[0224] Step 3. Delete the corresponding relationship of the member from the upstream and downstream member lists to be added.

[0225] It should be noted that, in the information sent by the first device to the server, the enterprise identification of each object to be added, the object identification and the link identification of the target service link are all external identification information, such as identification information encrypted by an encryption algorithm. The server can convert the external identification information to obtain the real identification information. Figure 7 As shown, the process may include the following steps:

[0226] Step 1: The first device imports the userid, external corpid, and upstream and downstream external chainid of each member to be added by calling the import interface.

[0227] Step 2: The server converts the relevant ID input by the first device into the following: userid→vid, external corpid→corpid, external chainid→chainid. If the conversion is successful, execute Step 3;

[0228] Step 3. The server reads the upstream and downstream tables of the enterprise through the vid, chainid, and corpid inside the office application to query the member custom ids associated with these internal ids.

[0229] Step 404: The server sends the object link identifier of the added object to the first device, so that the first device displays the progress indication information of the target service link based on the object link identifier of the added object.

[0230] The progress indication information indicates the progress of each of the to-be-joined objects joining the target service link; the joined objects are objects among the to-be-joined objects that join the target service link based on an invitation request.

[0231] In some embodiments, when using the target service link for service collaboration, the object link identifier of each object can also be used to provide real-time feedback on the completion progress of each object in the service assistance process. Exemplarily, corresponding to steps S1 to S3 on the first device side, the process of the server providing feedback on the progress of the service based on the multi-person collaboration service initiated by the first device may include the following steps B1 to B2:

[0232] Step B1, the server receives a business collaboration request sent by the first device, and sends business information for a multi-person collaborative business to each of the joined objects based on the business collaboration request.

[0233] The service collaboration request is used to request to initiate a multi-person collaboration service in the target service link, and the target service link includes multiple joined objects.

[0234] Step B2: In response to receiving the object collaboration progress fed back by each of the joined objects, the server sends the object link identifier of the first object to the first device, so that the first device displays the service progress information of the target collaboration service based on the object link identifier of the first object.

[0235] The first object is a joined object whose object collaboration progress is a target progress, and the object collaboration progress is the completion progress of the corresponding single-person business in the multi-person collaboration business.

[0236] The server may also synchronize the object link identifier corresponding to the designated object in the added object, and based on the synchronization service progress, the process may include:

[0237] Before sending the business information for the multi-person collaboration business to each of the joined objects based on the business collaboration request, the server sends the corresponding relationship between the object link identifier and the object contact information of each of the joined objects to the second device, where the object of the management role in each of the joined objects is located. For example, the second device is the device where the person in charge of the downstream enterprise is located.

[0238] Correspondingly, after sending business information for the multi-person collaborative business to each of the joined objects based on the business collaboration request, the server sends the object link identifier of the first object to the second device in response to receiving the object collaboration progress feedback from each of the joined objects, so that the second device displays the business progress information of the target collaborative business based on the object link identifier of the first object.

[0239] For example, the second device may determine the object contact information of the first object from the corresponding relationship between the object link identifiers and the object contact information of each added object stored in association, based on the object link identifier of the first object; generate and display the business progress information based on the object contact information of the first object; for example, the business progress information may include but is not limited to: the name of the completed object, the company where the object is located, and other object contact information, the number of completed people, the percentage of completed people, etc.

[0240] By sending the object link identifier of the first object to the second device, the second device can display the business progress information of the relevant object, which helps the company leaders to timely understand the business collaboration of their internal company members, strengthen the promotion of multiple collaborative businesses, and improve the convenience and efficiency of multi-person business collaboration.

[0241] The data processing method provided by the present application obtains an object link identifier for each object to be added based on an import request of the first device, so as to uniquely identify the corresponding object to be added in the target business link; and sends an invitation request to each object to be added to join the target business link. Moreover, based on the confirmation message received from the object to be added, it is added to the target business chain; at the same time, the object link identifier of the added object sent is fed back to the first device, so that the first device can use the received object link identifier to uniquely locate the corresponding added object, thereby effectively distinguishing the added object from each object to be added. The first device can clearly and specifically display the joining progress based on the object contact information of the added object, and then provide accurate and clear joining status of related objects to the outside, thereby improving the accuracy of the determined joining progress.

[0242] The data processing method provided in this application relates to technical fields such as cloud technology and big data.

[0243] Cloud computing is a computing model that distributes computing tasks on a resource pool composed of a large number of computers, allowing various application systems to obtain computing power, storage space and information services as needed. The network that provides resources is called a "cloud". From the user's perspective, the resources in the "cloud" are infinitely scalable and can be obtained at any time, used on demand, expanded at any time, and paid for by use.

[0244] As a provider of basic cloud computing capabilities, a cloud computing resource pool (referred to as a cloud platform, generally referred to as an IaaS (Infrastructure as a Service) platform) will be established, and various types of virtual resources will be deployed in the resource pool for external customers to choose to use. The cloud computing resource pool mainly includes: computing devices (virtualized machines, including operating systems), storage devices, and network devices.

[0245] According to the logical function division, the PaaS (Platform as a Service) layer can be deployed on the IaaS (Infrastructure as a Service) layer, and the SaaS (Software as a Service) layer can be deployed on the PaaS layer. SaaS can also be deployed directly on IaaS. PaaS is a platform for software operation, such as databases, web containers, etc. SaaS is a variety of business software, such as web portals, SMS mass senders, etc. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.

[0246] It should be understood that big data refers to a collection of data that cannot be captured, managed, and processed by conventional software tools within a certain time frame. It is a massive, high-growth, and diverse information asset that requires new processing models to have stronger decision-making power, insight discovery, and process optimization capabilities. With the advent of the cloud era, big data has also attracted more and more attention. Big data requires special technologies to effectively process large amounts of data within a tolerable time frame. Technologies applicable to big data include large-scale parallel processing databases, data mining, distributed file systems, distributed databases, cloud computing platforms, the Internet, and scalable storage systems.

[0247] Figure 8 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application. The device is applied to a first device, such as Figure 8 As shown, the device comprises:

[0248] A first acquisition module 801 is used to acquire an object link identifier of at least one object to be added in a target service link, where the object link identifier is used to uniquely identify the corresponding object to be added in the target service link;

[0249] An import request sending module 802 is used to send an import request to the server based on the object contact information and object link identifier of each object to be added, and the import request indicates to send an invitation request to the corresponding object to be added, and the invitation request is used to invite the corresponding object to be added to join the target service link;

[0250] A first receiving module 803 is used to receive an object link identifier of a joined object sent by the server, and determine object contact information of the joined object based on the received object link identifier, where the joined object is an object among the objects to be joined that joins the target service link based on an invitation request;

[0251] The progress display module 804 is used to display the progress indication information of the target service link based on the object contact information of the added object, and the progress indication information indicates the joining progress of each object to be added to the target service link.

[0252] In a possible implementation, for each object to be added, a method for obtaining the object link identifier of the object to be added includes any one of the following:

[0253] Acquire an unoccupied identification number from the multiple identification numbers corresponding to the target service link as the object link identification of the object to be added, the unoccupied identification number being an identification number among the multiple identification numbers that is not currently used by any object;

[0254] An object link identifier of the object to be added is generated based on the object identifier, the enterprise identifier and the link identifier of the target service link of the object to be added.

[0255] In a possible implementation, the first receiving module is used for any of the following:

[0256] Sending a first query request to a server based on the object identifier, enterprise identifier and link identifier of the target business link of each object to be added; receiving the object link identifier of the added object returned by the server based on the first query request, wherein the first query request is used to query the objects added to the target business link in each object to be added;

[0257] In response to the confirmation message fed back by each object to be added to the server based on the invitation request, a notification message fed back by the receiving server based on each confirmation message is received, and the object link identifier of the added object is obtained based on the notification message. The notification message is used to notify each object to be added whether to join the target service link.

[0258] In a possible implementation, the progress display module is used for at least one of the following:

[0259] Based on the object contact information of the added object, count and display the number of people who have joined the target service link in each of the objects to be added, and the progress indication information includes the number of people who have joined;

[0260] Displaying the object contact information of the added object as the progress indication information;

[0261] Based on the object contact information of the added object, the number of non-joined persons who have not joined the target service link in each of the to-be-joined objects is counted and displayed, and the progress indication information includes the number of non-joined persons.

[0262] In a possible implementation, the device further includes a business collaboration module, where the business collaboration module is configured to:

[0263] Sending a service collaboration request to the server, the service collaboration request being used to request initiation of a multi-person collaboration service in the target service link, the target service link including a plurality of joined objects;

[0264] In response to the object collaboration progress fed back by each of the joined objects to the server, receiving the object link identifier of the first object sent by the server, the first object being the joined object whose object collaboration progress is the target progress, the object collaboration progress being the completion progress of the single-person service corresponding to the multi-person collaboration service;

[0265] The object contact information of the first object is obtained based on the object link identifier of the first object, and the business progress information of the target collaborative business is displayed based on the object contact information of the first object.

[0266] In one possible implementation, the device further includes:

[0267] An association storage module, used for associating and storing the corresponding relationship between the object link identifier and the object contact information of each object to be added;

[0268] The first receiving module is used for:

[0269] Based on the object link identifier of the added object, the object contact information of the added object is obtained from the corresponding relationship stored in the association.

[0270] The data processing method provided by the present application sets an object link identifier for each object to be added, so as to uniquely identify the corresponding object to be added in the target business link; and sends an import request to the server based on the object contact information and object link identifier of each object to be added; so that the server sends an invitation request to join the target business link to each object to be added. In addition, the object link identifier of the added object sent by the server can uniquely locate the corresponding object, thereby effectively distinguishing the added object from each object to be added, and the object contact information of the added object can clearly and specifically display the joining progress, so that the first device can accurately and clearly perceive the joining status of the relevant object, thereby improving the accuracy of the determined joining progress.

[0271] Fig. 9 The structure diagram of a data processing device provided in an embodiment of the present application is shown in FIG. Fig. 9 As shown, the device comprises:

[0272] The second receiving module 901 is used to receive the import request sent by the first device, and obtain object contact information and object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request;

[0273] An invitation request sending module 902, configured to send an invitation request to a corresponding object to be added based on the object contact information and link identifier of each object to be added, wherein the invitation request is used to invite the corresponding object to be added to join the target service link;

[0274] The third receiving module 903 is used to receive a confirmation message fed back by each of the to-be-added objects based on the invitation request, and add each of the to-be-added objects to the target service link based on the confirmation message of each of the to-be-added objects;

[0275] The first sending module 904 is used to send the object link identifier of the added object to the first device, so that the first device displays the progress indication information of the target business link based on the object link identifier of the added object, and the progress indication information indicates the joining progress of each object to be joined to the target business link; the added object is an object among the objects to be joined that joins the target business link based on an invitation request.

[0276] In a possible implementation, the device further includes a verification module, the verification module being configured to:

[0277] Based on the first object table and the object contact information of each object to be added, the object link identifier of each object to be added is verified, and the first object table stores the objects included in the target service link;

[0278] For each object to be added, if the object link identifier of the object to be added passes the verification, the correspondence between the object contact information and the object link identifier of the object to be added is associated and stored in the second object table, and the second object table is used to store the objects to be added to the target service link.

[0279] In a possible implementation, the verification module is used to:

[0280] For each object to be added, obtaining the target enterprise where the object to be added is located based on the object contact information of the object to be added;

[0281] Extracting each target object belonging to the target enterprise from the first object table;

[0282] The object link identifiers between the object to be added and each target object are compared respectively, and based on the comparison results between the object to be added and each target object respectively, a verification result corresponding to the object to be added is obtained.

[0283] In a possible implementation, the third receiving module is used to:

[0284] In response to receiving a confirmation message of any object to be added, the correspondence between the object contact information and the object link identifier of any object to be added is stored in the first object table, and the object contact information and the object link identifier of any object to be added are deleted from the second object table.

[0285] In a possible implementation, the device further includes a business collaboration module, where the business collaboration module is configured to:

[0286] Receive a service collaboration request sent by the first device, and send service information for a multi-person collaboration service to each of the joined objects based on the service collaboration request, wherein the service collaboration request is used to request initiation of a multi-person collaboration service in the target service link, and the target service link includes multiple joined objects;

[0287] In response to receiving the object collaboration progress feedback from each of the joined objects, the object link identifier of the first object is sent to the first device, so that the first device displays the business progress information of the target collaboration business based on the object link identifier of the first object; the first object is a joined object whose object collaboration progress is the target progress, and the object collaboration progress is the completion progress of the single-person business corresponding to the multi-person collaboration business.

[0288] In one possible implementation, the device further includes:

[0289] A second sending module, configured to send the corresponding relationship between the object link identifier and the object contact information of each of the added objects to a second device, the second device being the device where the object with the management role in each of the added objects is located;

[0290] The business collaboration module is used to:

[0291] In response to receiving the object collaboration progress fed back by each of the joined objects, an object link identifier of the first object is sent to the second device, so that the second device displays the service progress information of the target collaboration service based on the object link identifier of the first object.

[0292] The data processing method provided by the present application obtains an object link identifier for each object to be added based on an import request of the first device, so as to uniquely identify the corresponding object to be added in the target business link; and sends an invitation request to each object to be added to join the target business link. Moreover, based on the confirmation message received from the object to be added, it is added to the target business chain; at the same time, the object link identifier of the added object sent is fed back to the first device, so that the first device can use the received object link identifier to uniquely locate the corresponding added object, thereby effectively distinguishing the added object from each object to be added. The first device can clearly and specifically display the joining progress based on the object contact information of the added object, and then provide accurate and clear joining status of related objects to the outside, thereby improving the accuracy of the determined joining progress.

[0293] The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

[0294] Fig.10 1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig.10 As shown, the electronic device includes: a memory, a processor and a computer program stored in the memory, and the processor executes the above computer program to implement the steps of the data processing method. Compared with the related art, it can achieve:

[0295] The data processing method provided by the present application sets an object link identifier for each object to be added, so as to uniquely identify the corresponding object to be added in the target business link; and sends an import request to the server based on the object contact information and object link identifier of each object to be added; so that the server sends an invitation request to join the target business link to each object to be added. In addition, the object link identifier of the added object sent by the server can uniquely locate the corresponding object, thereby effectively distinguishing the added object from each object to be added, and the object contact information of the added object can clearly and specifically display the joining progress, so that the first device can accurately and clearly perceive the joining status of the relevant object, thereby improving the accuracy of the determined joining progress.

[0296] In an alternative embodiment, an electronic device is provided, such as Fig.10 As shown, Fig.10 The electronic device 1000 shown includes: a processor 1001 and a memory 1003. The processor 1001 and the memory 1003 are connected, such as through a bus 1002. Optionally, the electronic device 1000 may also include a transceiver 1004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 1004 is not limited to one, and the structure of the electronic device 1000 does not constitute a limitation on the embodiments of the present application.

[0297] Processor 1001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 1001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0298] The bus 1002 may include a path to transmit information between the above components. The bus 1002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 1002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0299] The memory 1003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage medium\other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.

[0300] The memory 1003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the computer program stored in the memory 1003 to implement the steps shown in the above method embodiment.

[0301] Among them, electronic equipment includes but is not limited to: servers, terminals or cloud computing center equipment, etc.

[0302] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented.

[0303] The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned method embodiment when executed by a processor.

[0304] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said", and "the" used herein may also include plural forms. The terms "include" and "comprise" used in the embodiments of the present application mean that the corresponding features can be implemented as the presented features, information, data, steps, and operations, but do not exclude the implementation as other features, information, data, steps, operations, etc. supported by the technical field.

[0305] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.

[0306] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.

[0307] The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.

Claims

1. A data processing method, characterized in that: The method is applied to a first device, and the method includes: Obtaining an object link identifier of at least one object to be added in a target service link, wherein the object link identifier is used to uniquely identify a corresponding object to be added in the target service link; Based on the object contact information and object link identifier of each object to be added, sending an import request to the server, wherein the import request indicates sending an invitation request to the corresponding object to be added, wherein the invitation request is used to invite the corresponding object to be added to join the target service link; receiving an object link identifier of a joined object sent by the server, and determining object contact information of the joined object based on the received object link identifier, wherein the joined object is an object among the objects to be joined that joins the target service link based on an invitation request; Based on the object contact information of the added objects, the progress indication information of the target service link is displayed, and the progress indication information indicates the joining progress of each of the objects to be added to the target service link.

2. The method according to claim 1, characterized in that For each object to be added, the method for obtaining the object link identifier of the object to be added includes any one of the following: Acquire an unoccupied identification number from a plurality of identification numbers corresponding to the target service link as the object link identification of the object to be added, wherein the unoccupied identification number is an identification number among the plurality of identification numbers that is not currently used by any object; An object link identifier of the object to be added is generated based on the object identifier, the enterprise identifier and the link identifier of the target service link of the object to be added.

3. The method according to claim 1, characterized in that The receiving the object link identifier of the added object sent by the server includes any one of the following: Sending a first query request to the server based on the object identifier, the enterprise identifier and the link identifier of the target business link of each of the objects to be added; receiving an object link identifier of an already added object returned by the server based on the first query request, wherein the first query request is used to query an object added to a target service link among the objects to be added; In response to the confirmation message fed back by each object to be added to the server based on the invitation request, a notification message fed back by the receiving server based on each confirmation message is obtained, and the object link identifier of the added object is obtained based on the notification message, and the notification message is used to notify each object to be added whether to join the target service link.

4. The method according to claim 3, characterized in that The displaying of the progress indication information of the target service link based on the object contact information of the added object includes at least one of the following: Based on the object contact information of the added objects, counting and displaying the number of people who have joined the target service link in each of the objects to be added, wherein the progress indication information includes the number of people who have joined; Displaying the object contact information of the added object as the progress indication information; Based on the object contact information of the added objects, the number of non-joined persons who have not joined the target service link in each of the to-be-joined objects is counted and displayed, and the progress indication information includes the number of non-joined persons.

5. The method according to any one of claims 1 to 4, characterized in that After sending the import request to the server based on the object contact information and the object link identifier of each object to be added, the method further includes: Sending a service collaboration request to the server, wherein the service collaboration request is used to request initiation of a multi-person collaboration service in the target service link, wherein the target service link includes a plurality of joined objects; In response to the object collaboration progress fed back by each of the joined objects to the server, receiving the object link identifier of the first object sent by the server, the first object is a joined object whose object collaboration progress is a target progress, and the object collaboration progress is the completion progress of the single-person service corresponding to the multi-person collaboration service; The object contact information of the first object is obtained based on the object link identifier of the first object, and the business progress information of the target collaborative business is displayed based on the object contact information of the first object.

6. A data processing method, characterized in that: The method is applied to a server, and the method comprises: receiving an import request sent by the first device, and acquiring object contact information and an object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request; Based on the object contact information of each of the objects to be added and the link identifier of the target service link, an invitation request is sent to the corresponding object to be added, where the invitation request is used to invite the corresponding object to be added to join the target service link; receiving a confirmation message fed back by each of the objects to be added based on the invitation request, and adding each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added; Send the object link identifier of the joined object to the first device, so that the first device displays the progress indication information of the target service link based on the object link identifier of the joined object, and the progress indication information indicates the joining progress of each object to be joined to the target service link; the joined object is an object among the objects to be joined that joins the target service link based on an invitation request.

7. The method according to claim 6, characterized in that Before sending an invitation request to the corresponding object to be added based on the object contact information and link identifier of each object to be added, the method further includes: Based on the first object table and the object contact information of each object to be added, verifying the object link identifier of each object to be added, wherein the first object table stores the objects included in the target service link; For each object to be added, if the object link identifier of the object to be added passes the verification, the correspondence between the object contact information and the object link identifier of the object to be added is associated and stored in the second object table, and the second object table is used to store the objects to be added to the target service link.

8. The method according to claim 7, characterized in that The verifying the object link identifier of each object to be added based on the first object table and the object contact information of each object to be added includes: For each object to be added, obtaining a target enterprise where the object to be added is located based on the object contact information of the object to be added; Extracting each target object belonging to the target enterprise from the first object table; The object link identifiers between the object to be added and each target object are compared respectively, and based on the comparison results between the object to be added and each target object respectively, a verification result corresponding to the object to be added is obtained.

9. The method according to claim 7, characterized in that: The adding each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added includes: In response to receiving a confirmation message of any object to be added, the correspondence between the object contact information and the object link identifier of any object to be added is stored in the first object table, and the object contact information and the object link identifier of any object to be added are deleted from the second object table.

10. The method according to claim 6, characterized in that The method further comprises: Receive a service collaboration request sent by the first device, and send service information for a multi-person collaboration service to each of the joined objects based on the service collaboration request, wherein the service collaboration request is used to request initiation of a multi-person collaboration service in the target service link, and the target service link includes multiple joined objects; In response to receiving the object collaboration progress feedback from each of the joined objects, the object link identifier of the first object is sent to the first device, so that the first device displays the business progress information of the target collaboration business based on the object link identifier of the first object; the first object is a joined object whose object collaboration progress is the target progress, and the object collaboration progress is the completion progress of the single-person business corresponding to the multi-person collaboration business.

11. The method according to claim 10, characterized in that Before sending the service information for the multi-person collaboration service to each of the joined objects based on the service collaboration request, the method further includes: Sending a correspondence between an object link identifier and object contact information of each of the added objects to a second device, where the second device is a device where an object with a management role in each of the added objects is located; After sending the service information for the multi-person collaboration service to each of the joined objects based on the service collaboration request, the method further includes: In response to receiving the object collaboration progress fed back by each of the joined objects, the object link identifier of the first object is sent to the second device, so that the second device displays the service progress information of the target collaborative service based on the object link identifier of the first object.

12. A data processing device, characterized in that: The device is applied to a first device, and includes: A first acquisition module, configured to acquire an object link identifier of at least one object to be added in a target service link, wherein the object link identifier is used to uniquely identify the corresponding object to be added in the target service link; An import request sending module, used to send an import request to the server based on the object contact information and object link identifier of each object to be added, wherein the import request indicates sending an invitation request to the corresponding object to be added, and the invitation request is used to invite the corresponding object to be added to join the target service link; A first receiving module is configured to receive an object link identifier of a joined object sent by the server, and determine object contact information of the joined object based on the received object link identifier, wherein the joined object is an object among the objects to be joined that joins the target service link based on an invitation request; The progress display module is used to display the progress indication information of the target service link based on the object contact information of the added object, wherein the progress indication information indicates the joining progress of each of the to-be-added objects in joining the target service link.

13. A data processing device, characterized in that: The device is applied to a server, and comprises: A second receiving module, configured to receive an import request sent by the first device, and acquire object contact information and an object link identifier of at least one object to be added, and a link identifier of a target service link based on the import request; An invitation request sending module, used for sending an invitation request to a corresponding object to be added based on the object contact information and link identifier of each object to be added, wherein the invitation request is used to invite the corresponding object to be added to join the target service link; A third receiving module is used to receive a confirmation message fed back by each of the objects to be added based on the invitation request, and add each of the objects to be added to the target service link based on the confirmation message of each of the objects to be added; A sending module is used to send the object link identifier of the joined object to the first device, so that the first device displays the progress indication information of the target business link based on the object link identifier of the joined object, and the progress indication information indicates the joining progress of each object to be joined to the target business link; the joined object is an object among the objects to be joined that joins the target business link based on an invitation request.

14. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the data processing method according to any one of claims 1 to 11.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the data processing method according to any one of claims 1 to 11 is implemented.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the data processing method according to any one of claims 1 to 11 is implemented.

Images