CN113992736A

CN113992736A - Interconnection method of structured data based on cloud computing service platform and server

Info

Publication number: CN113992736A
Application number: CN202111635516.XA
Authority: CN
Inventors: 彭杉; 李斌
Original assignee: Xiwei Technology Guangzhou Co ltd
Current assignee: Xiwei Technology Guangzhou Co ltd
Priority date: 2021-12-29
Filing date: 2021-12-29
Publication date: 2022-01-28
Anticipated expiration: 2041-12-29
Also published as: CN113992736B

Abstract

The application is suitable for the technical field of data sharing, and provides a structured data interconnection method and a server based on a cloud computing service platform, wherein the structured data interconnection method comprises the following steps: receiving an interconnection data acquisition request from a target tenant, wherein the interconnection data acquisition request carries an identifier of the target tenant; based on the identification of the target tenant, inquiring information of target structured data corresponding to the identification of the target tenant from a sharing record table of the tenant establishing an interconnection relationship with the target tenant, wherein the information of the target structured data comprises a sharing state of the target structured data; and sending the information of the target structured data with the sharing state allowed to be shared to the target tenant so that the target tenant can display and/or operate the information of the target structured data, thereby enabling the tenants with the interconnection relationship to perform cooperative operation on the shared data, and improving the cooperative work efficiency among different tenants.

Description

Interconnection method of structured data based on cloud computing service platform and server

Technical Field

The application belongs to the technical field of data sharing, and particularly relates to a structured data interconnection method and a server based on a cloud computing service platform.

Background

In the industrial chain of an enterprise, there are suppliers that provide raw materials, equipment, etc. for the enterprise, assembly centers that assemble products of the enterprise, customers that receive products of the enterprise, and regulatory agencies that supervise product quality of the enterprise, etc., and these different roles can be regarded as different links in the industrial chain of the enterprise. Data sharing is often required between different segments of the industry chain throughout the production of a product.

In the existing data sharing mode among all links of an industrial chain, the industrial chain link needing data sharing records data to be shared in a document, and sends the document to a target industrial chain link. When the target industrial chain link needs to modify the shared data, the target industrial chain link can edit the document and return the edited document to the industrial chain link needing to share the data. The data sharing mode can not enable the shared data to be operated cooperatively among all links of the industrial chain, and the cooperative work efficiency among all links of the industrial chain is reduced.

Disclosure of Invention

In view of this, embodiments of the present application provide an interconnection method and a server for structured data based on a cloud computing service platform, so as to solve the technical problem that an existing data sharing manner cannot enable shared data to be cooperatively operated among links of an industrial chain, so that cooperative work efficiency among the links of the industrial chain is reduced.

In a first aspect, an embodiment of the present application provides an interconnection method for structured data based on a cloud computing service platform, which is applied to a server, where the server is configured to provide a data interconnection service based on the cloud computing service platform; the interconnection method comprises the following steps:

receiving an interconnection data acquisition request from a target tenant, wherein the interconnection data acquisition request carries an identifier of the target tenant;

based on the identification of the target tenant, inquiring information of target structured data corresponding to the identification of the target tenant from a sharing record table of a tenant establishing an interconnection relationship with the target tenant, wherein the information of the target structured data comprises a sharing state of the target structured data;

and sending the information of the target structured data of which the sharing state is allowed to be shared to the target tenant, so that the target tenant can display and/or operate the information of the target structured data.

In a second aspect, an embodiment of the present application provides a server, where the server is configured to provide a data interconnection service based on the cloud computing service platform; the server includes:

the device comprises a first receiving unit, a first sending unit and a second receiving unit, wherein the first receiving unit is used for receiving an interconnection data acquisition request from a target tenant, and the interconnection data acquisition request carries an identifier of the target tenant;

the first query unit is used for querying information of target structured data corresponding to the identifier of the target tenant from a sharing record table of a tenant establishing an interconnection relationship with the target tenant based on the identifier of the target tenant, wherein the information of the target structured data comprises a sharing state of the target structured data;

the first communication unit is configured to send the information of the target structured data, which is in the sharing state allowed to be shared, to the target tenant, so that the target tenant displays and/or operates the information of the target structured data.

In a third aspect, an embodiment of the present application provides another server, where the server includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor, when executing the computer program, implements the interconnection method according to the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the interconnection method according to the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product, which, when run on a server, causes the server to perform the interconnection method according to the first aspect.

The implementation of the interconnection method, the server, the computer-readable storage medium and the computer program product of the structured data based on the cloud computing service platform provided by the embodiment of the application has the following beneficial effects:

according to the interconnection method of the structured data based on the cloud computing service platform, when a target tenant needs to acquire target structured data shared by other tenants, the target tenant can send an interconnection data acquisition request to a server, the server can acquire information of the target structured data from a sharing record table of the tenant establishing an interconnection relationship with the target tenant, and the information of the target structured data is sent to the target tenant, so that the target tenant can display or operate the target structured data. Because the data shared by the tenants with the interconnection relationship with the target tenant is the structured data, and the structured data can be directly edited, the target tenant can directly edit the target structured data shared by other tenants when needing to edit the shared data, so that the tenants with the interconnection relationship can cooperatively operate the shared data, and the cooperative work efficiency of different tenants is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic architecture diagram of an interconnection system of structured data based on a cloud computing service platform according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a window lift system of an automobile according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to an embodiment of the present application;

fig. 4 is a schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application;

fig. 5 is a schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application;

fig. 6 is a second schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application;

fig. 7 is a third schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application;

fig. 8 is a fourth schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to yet another embodiment of the present application;

fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a server according to another embodiment of the present application.

Detailed Description

It is noted that the terminology used in the description of the embodiments of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. In the description of the embodiments of the present application, "a plurality" means two or more, "at least one", "one or more" means one, two or more. The terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless otherwise noted.

The interconnection method of the structured data based on the cloud computing service platform can be applied to an interconnection system of the structured data based on the cloud computing service platform. The cloud computing service platform may be a service platform based on a platform-as-a-service (PaaS) technology, may also be a service platform based on a software-as-a-service (SaaS) technology, or may also be another type of cloud computing service platform, which is not particularly limited herein. Fig. 1 is a schematic architecture diagram of an interconnection system of structured data based on a cloud computing service platform according to an embodiment of the present application. As shown in fig. 1, the interconnect system may include: the server 10 and n client devices (client device 1 to client device n) connected to the server 10, where n is an integer.

Wherein the server 10 may be a cluster of servers or a single server. The server 10 may provide a data interconnection service based on a cloud computing service platform to each client device connected thereto.

For example, the connection between the server 10 and each client device may be a wireless connection. Client devices may include, but are not limited to, cell phones, tablets, laptops, desktops, and the like.

In the embodiment of the application, one client device may correspond to one tenant in the cloud computing service platform, and one tenant may correspond to one or more client devices. For example, client device 1 and client device 2 may correspond to tenant a, client device 3 may correspond to tenant B, and client device n may correspond to tenant C, that is, client device 1 and client device 2 may belong to tenant a, client device 2 may belong to tenant B, and client device n may belong to tenant C. The tenants can be regarded as enterprises with tenant accounts registered in the cloud computing service platform, and the client device corresponding to each tenant can log in the cloud computing service platform through the tenant account of the tenant.

In the industry chain of an enterprise, there are upstream suppliers that provide raw materials and/or equipment for the enterprise, and downstream customers that receive the products of the enterprise, and thus, upstream and downstream relationships may exist between different tenants. For example, tenant a may be an upstream provider of tenant B and tenant C may be a downstream customer of tenant B, i.e., tenant a may be an upstream tenant of tenant B and tenant C may be a downstream tenant of tenant B. It should be noted that the number of upstream tenants and the number of downstream tenants of one tenant may be one or more, and may be determined specifically according to actual situations, and is not particularly limited herein.

In the embodiment of the application, an interconnection relationship can be established between tenants with an upstream and downstream relationship, and each tenant can establish an interconnection relationship with one or more tenants.

In a possible implementation manner, the server 10 may allocate a unique interconnection code to each tenant, and each tenant may share the interconnection code with other tenants, so that the other tenants establish an interconnection relationship with the tenant through the interconnection code. In this implementation manner, for example, when a first tenant needs to establish an interconnection relationship with a target tenant, a client device corresponding to the first tenant may send an interconnection request carrying an interconnection code of the target tenant and information of the first tenant to the server 10. After receiving the interconnection request from the first tenant, the server 10 may send an interconnection application notification to the client device corresponding to the target tenant based on the interconnection code of the target tenant carried in the interconnection request. The interconnection application notification is used for notifying the target tenant that the first tenant needs to establish an interconnection relationship with the target tenant. The interconnection application notification may carry information of the first tenant. For example, the information of the first tenant may include, but is not limited to, a name of a business corresponding to the first tenant, a dockee name, a dockee contact, an upstream and downstream relationship between the first tenant and the target tenant, and the like.

After receiving the interconnection application notification from the server 10, the client device corresponding to the target tenant may determine whether to establish an interconnection relationship with the first tenant based on the information of the first tenant carried in the interconnection application notification. If the target tenant determines to establish an interconnection relationship with the first tenant, the client device corresponding to the target tenant may send a first interconnection result indicating that the target tenant agrees to establish an interconnection relationship with the first tenant to the server 10. After receiving the first interconnection result, the server 10 establishes an interconnection relationship between the first tenant and the second tenant, and records the interconnection relationship in the interconnection relationship table. In addition, the server 10 may further send an interconnection result notification carrying the first interconnection result to the client device corresponding to the first tenant, so as to inform the first tenant that the target tenant agrees to establish an interconnection relationship with the first tenant. If the target tenant determines that the interconnection relationship with the first tenant is not established, the client device corresponding to the target tenant may send a second interconnection result to the server 10, where the second interconnection result is used to indicate that the interconnection relationship with the first tenant is not approved. After receiving the second interconnection result, the server 10 may send an interconnection result notification carrying the second interconnection result to the client device corresponding to the first tenant, so as to inform the first tenant that the target tenant does not agree with establishing an interconnection relationship with the target tenant.

In another possible implementation manner, when a first tenant needs to establish an interconnection relationship with a target tenant or a target enterprise for which a tenant account is not registered in a cloud computing service platform, a client device corresponding to the first tenant may send an interconnection invitation link application request to the server 10. After receiving the request for applying for the interconnection invitation from the first tenant, the server 10 may create an interconnection invitation link related to the first tenant, and send the interconnection invitation link to the client device corresponding to the first tenant. The first tenant may send the interconnection invitation link to a target tenant or target enterprise that the first tenant wants to establish an interconnection relationship. The target tenant or the target enterprise may enter a tenant login interface of the cloud computing service platform by clicking the interconnection invitation link, and after the target tenant or the target enterprise successfully logs in the cloud computing service platform through the tenant login interface or successfully registers an account in the cloud computing service platform, the server 10 may establish an interconnection relationship between the first tenant and the tenant corresponding to the target tenant or the target enterprise, and store the interconnection relationship in the interconnection relationship table.

The target tenant can be any tenant except the first tenant in the interconnected system.

In the embodiment of the application, the interconnection relationship table is used for recording the corresponding relationship between the information of each tenant establishing the interconnection relationship. The tenant information may include, but is not limited to, an identification of the tenant, a dockee name, a dockee contact, an upstream and downstream relationship between the first tenant and the target tenant, and the like. The identity of the tenant is used for uniquely identifying the identity of the tenant. For example, the identity of the tenant may be the name or credit code of the enterprise to which the tenant corresponds.

In the embodiment of the present application, the interconnection relationship table may be stored in the server 10.

Data sharing can be carried out between the tenants with the interconnection relationship. In the embodiment of the application, the data sharing object is structured data. The structured data can include structured data having a hierarchical structure and structured data of a list class. The structured data having a hierarchical structure may include at least one hierarchy, each hierarchy may include at least one data node, and for example, a data node of a first hierarchy in the structured data may be referred to as a primary data node, a data node of a second hierarchy in the structured data may be referred to as a secondary data node, and so on. In particular applications, different data nodes in the structured data may correspond to different links in the enterprise industry chain.

For example, taking a window lift system of an automobile as an example, fig. 2 shows a schematic structural diagram of a window lift system of an automobile. As shown in fig. 2, if the window regulator system 200 includes a lift motor 21, a lift mechanism 22 and a guide mechanism 23, the lift motor 21 includes a commutation system 211, an electromagnetic converter system 212 and a magnetic converter system 213, the commutation system 211 includes a brush box base 2111, a carbon brush 2112 and an electronic control unit 2113, and the electromagnetic converter system 212 includes a magnetic steel 2121, an armature winding 2122, a motor housing 2123 and a gear box 2124. Each component in the window lift system 200 then corresponds to a data node. Specifically, the data nodes corresponding to the lifting motor 21, the lifting mechanism 22, and the guiding mechanism 23 are primary data nodes, the data nodes corresponding to the commutation system 211, the electromagnetic conversion system 212, and the magnetic conversion system 213 are secondary data nodes, and the data nodes corresponding to the brush box base 2111, the carbon brush 2112, the electronic control unit 2113, the magnetic steel 2121, the armature winding 2122, the motor housing 2123, and the gear box 2124 are tertiary data nodes. All the data nodes constitute the corresponding structured data of the window regulator system 200.

In the embodiment of the application, each piece of structured data has a unique identifier. Each data node in the structured data also has a unique identification. By way of example, and not limitation, the identification of the structured data can be a number of the structured data. The identifier of the data node may be composed of the number of the structured data to which the data node belongs and the number of the data node, and may be specifically set according to actual requirements.

By way of example and not limitation, the structured data may be structured quality data or structured other data, and is not particularly limited herein. Wherein the quality data is used to provide a basis for quality analysis of its corresponding product. In particular applications, the quality data may include, but is not limited to: failure Mode and Effects Analysis (FMEA) data of a product, problem source data of the product, problem location data of the product, inspection result data of each part of the product, sample data of the product, detection result data of the product, audit project data of the product, production preparation data of the product, project management data of the product, performance data of the parts provided by each supplier related to the product, inspection tool and Analysis result data of each supplier related to the product, raw material data provided by each supplier related to the product, result report data of the product, and the like.

In the embodiment of the present application, the server 10 may create an independent data space for each tenant in the cloud computing service platform, and isolate the data spaces of different tenants. The server 10 can store the structured data of each tenant in its respective data space based on the identity of each tenant. Specifically, the server may maintain a data table in the data space of each tenant, for recording the structured data of each tenant respectively.

Based on the interconnection system of the structured data based on the cloud computing service platform provided in the foregoing embodiment, an embodiment of the present application further provides an interconnection method of the structured data based on the cloud computing service platform, and an execution subject of the interconnection method of the structured data is the server 10 in the foregoing embodiment. Specifically, a target script file may be configured for the server 10, and the target script file describes the interconnection method of the structured data based on the cloud computing service platform provided in the embodiment of the present application, so that the server 10 executes the target script file when interconnection between structured data of different tenants is required, and further executes each step in the interconnection method of the structured data based on the cloud computing service platform provided in the embodiment of the present application.

Referring to fig. 3, a schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to an embodiment of the present application is provided. As shown in FIG. 3, the method for interconnecting the structured data may include S31-S33, which is detailed as follows:

s31: receiving an interconnection data acquisition request from a target tenant, wherein the interconnection data acquisition request carries an identifier of the target tenant.

In the embodiment of the application, the target tenant may be any tenant in the cloud computing service platform.

When any client device corresponding to the target tenant needs to acquire the structured data shared by other tenants to the target tenant, the client device corresponding to the target tenant may generate an interconnection data acquisition request carrying an identifier of the target tenant, and send the interconnection data acquisition request to the server.

S32: based on the identification of the target tenant, inquiring information of target structured data corresponding to the identification of the target tenant from a sharing record table of a tenant establishing an interconnection relationship with the target tenant, wherein the information of the target structured data comprises a sharing state of the target structured data.

In the embodiment of the application, the server may further maintain a sharing record table in the data space of each tenant, and the sharing record table is used for respectively recording information of structured data shared by each tenant to other tenants. The information of the structured data may include, but is not limited to, the structured data itself, an identifier of the structured data, an identifier of a tenant to which the structured data belongs, an identifier of a target tenant to which the structured data is to be shared, and a sharing status of the structured data.

The sharing state of the structured data can include approval, permission to share and non-permission to share. When the sharing state of the structured data is in approval and is not allowed to be shared, the structured data is shown to be not approved and is not allowed to be shared to the target tenant; when the sharing state of the structured data is the sharing permission state, the structured data is approved and is permitted to be shared to the target tenant.

In the embodiment of the application, after receiving the interconnection data acquisition request from the target tenant, the server may first query, based on the identifier of the target tenant, the tenant having an interconnection relationship with the target tenant from the interconnection relationship table, and then query, from the sharing record table in the data space of the tenant having an interconnection relationship with the target tenant, information of the target structured data corresponding to the identifier of the target tenant. The number of the tenants that establish the interconnection relationship with the target tenant may be one or more, and is not particularly limited herein.

In an embodiment of the present application, before S32, the method for interconnecting structured data may further include S301 to S304 shown in fig. 4, which are detailed as follows:

s301: receiving a data sharing request from a first tenant, wherein the data sharing request carries information of structured data to be shared.

In this embodiment, the first tenant may be any tenant in the cloud computing service platform.

When any client device corresponding to the first tenant needs to share data with the tenant having the interconnection relationship with the first tenant, the client device corresponding to the first tenant may send a data sharing request carrying information of structured data to be shared to the server. The information of the structured data to be shared may refer to the above description related to the information of the structured data, and is not described herein again.

S302: and judging whether an interconnection relation is established between the first tenant and the target tenant.

After receiving the data sharing request from the first tenant, the server may query, based on the identifier of the first tenant carried in the data sharing request and the identifier of the target tenant to which the structured data to be shared is to be shared, whether the interconnection relationship table stores the corresponding relationship between the identifier of the first tenant and the identifier of the target tenant. In a possible implementation manner, if the interconnection relationship table stores the corresponding relationship between the identifier of the first tenant and the identifier of the target tenant, the server determines that an interconnection relationship is established between the first tenant and the target tenant, and the server may execute S303 at this time; in another possible implementation manner, if the interconnection relationship table does not store the corresponding relationship between the identifier of the first tenant and the identifier of the target tenant, the server determines that the interconnection relationship is not established between the first tenant and the target tenant, and at this time, the server may execute S303.

S303: and if the interconnection relationship is established between the first tenant and the target tenant, recording the information of the structured data to be shared in a sharing record table of the first tenant.

In this embodiment, after determining that the interconnection relationship is established between the first tenant and the target tenant, the server may record information of the structured data to be shared in the sharing record table of the first tenant. It should be noted that the information of each piece of structured data to be shared, which is recorded in the sharing record table of the first tenant, may be acquired by the corresponding target tenant. In addition, the first tenant can also view the information of the structured data shared to other tenants, which is recorded in the shared record table.

S304: and if the interconnection relation between the first tenant and the target tenant is not established, sending second prompt information to the first tenant.

The second prompt information is used for prompting that the first tenant does not establish an interconnection relationship with the target tenant, and the structured data to be shared cannot be shared with the target tenant, namely the data sharing fails.

In addition, the server may further intercept the information of the structured data to be shared, that is, the server does not record the information of the structured data to be shared in the sharing record table of the first tenant, so that a target tenant that does not establish an interconnection relationship with the first tenant cannot acquire the information of the structured data. Therefore, data sharing can be performed between tenants only establishing the interconnection relationship, data sharing cannot be performed between tenants not establishing the interconnection relationship, and the safety of the structured data of each tenant is improved.

In this embodiment, S303 and S304 are parallel steps. The server does not execute S304 when executing S303, and the server does not execute S303 when executing S304.

S33: and sending the information of the target structured data of which the sharing state is allowed to be shared to the target tenant, so that the target tenant can display and/or operate the information of the target structured data.

In the information of each structured data stored in the sharing record table of each tenant, only the information of the structured data whose sharing state is allowed to be shared to the corresponding target tenant, so that the server can send the information of the target structured data whose sharing state is allowed to be shared to the client device corresponding to the target tenant after querying the information of the target structured data corresponding to the identifier of the target tenant from the sharing record table of the tenant establishing an interconnection relationship with the target tenant. After receiving the information of the target structured data, the client device corresponding to the target tenant may display the information of the target structured data for a user using the client device to view.

In another embodiment of the present application, the information of the structured data may further include a sharing expiration time of the structured data. Based on the information, the server can send the information of the target structured data with the sharing state of allowing sharing and the current time being earlier than the sharing expiration time of the structured data to the target tenant. And for the target structured data of which the sharing state is allowed to be shared and the current time is later than the sharing expiration time of the structured data, the target tenant cannot acquire the information of the target structured data. This may improve the security of the target structured data.

In yet another embodiment of the present application, the information of the structured data may further include a storage right of the structured data. Wherein the stored rights may include permission to be stored and permission not to be stored. The target tenants to which the stored representation allows the structured data to be shared are allowed to store the structured data, and the target tenants to which the stored representation does not allow the structured data to be shared are not allowed to store the structured data. Based on this, after S33, the method for interconnecting structured data may further include the steps of:

and if the storage authority of the target structured data is allowed to be stored, storing the information of the target structured data in the data space of the target tenant.

In this embodiment, when the storage authority of the target structured data is allowed to be stored, the server may store the information of the target structured data in the data space of the target tenant. Specifically, the server may maintain an interconnection data table in a data space of each tenant, so as to record information of structured data shared by other tenants to each tenant. Based on this, when the storage authority of the target structured data is allowed to be stored, the server may store the information of the target structured data in an interconnected data table in the data space of the target tenant, so that the target tenant may perform operations on the target structured data in its own data space, including but not limited to: interconnection, mounting, modification and the like. By storing the target structured data in the data space of the target tenant, the operating efficiency of the target tenant on the target structured data can be improved, and the communication resources of the server when the target tenant operates on the target structured data can be saved.

As can be seen from the above, according to the interconnection method of structured data based on a cloud computing service platform provided in this embodiment, when a target tenant needs to obtain target structured data shared by other tenants, the target tenant may send an interconnection data obtaining request to a server, and the server may obtain information of the target structured data from a sharing record table of a tenant having an interconnection relationship with the target tenant, and send the information of the target structured data to the target tenant, so that the target tenant displays or operates the target structured data. Because the data shared by the tenants with the interconnection relationship with the target tenant is the structured data, and the structured data can be directly edited, the target tenant can directly edit the target structured data shared by other tenants when needing to edit the shared data, so that the tenants with the interconnection relationship can cooperatively operate the shared data, and the cooperative work efficiency of different tenants is improved.

Referring to fig. 5, a schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application is provided. As shown in fig. 5, the difference between the present embodiment and the embodiment corresponding to fig. 4 is that the present embodiment may further include S51 to S55 after S303, which are detailed as follows:

s51: creating a sharing approval process for the structured data to be shared for the first tenant, wherein the sharing approval process comprises at least one approval node, and each approval node is associated with at least one client device corresponding to the first tenant.

In this embodiment, each tenant corresponds to multiple client devices, but not all the client devices can freely share the structured data of the tenant with other tenants, and only after approval of the client device having the data sharing permission and the approval, the structured data to be shared is allowed to be shared with other tenants. Based on this, after recording the information of the structured data to be shared in the sharing record table of the first tenant, the server may further create a sharing approval process for the structured data to be shared for the first tenant.

In a specific application, different approval process templates can be configured for different approval processes in advance, an identifier for uniquely identifying the identity of each approval process template is allocated to each approval process template, and the identifier of the approval process and the approval process template configured for the approval process in advance are stored in an associated manner. The identifier of the approval process may be a name of the approval process, and the approval process may include, but is not limited to, a data sharing approval process, a data modification approval process, and the like. The data sharing examination and approval can comprise data first-time sharing examination and approval, data multiple-time sharing examination and approval and the like. Specifically, the time may be set according to time requirements, and is not particularly limited herein.

Based on the data sharing approval process, the server can create a sharing approval process aiming at the structural data to be shared for the first tenant based on the approval process template corresponding to the data sharing approval process. The sharing approval process may include at least one approval node, and each approval node may correspond to at least one approver in the first tenant, that is, each approval node may be associated with at least one client device corresponding to the first tenant.

S52: and sequentially sending an approval notice aiming at the structured data to be shared to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment.

In this embodiment, after the server creates the sharing approval process for the structured data to be shared, the server may sequentially send an approval notification for the structured data to be shared to the client device associated with each approval node in the sharing approval process. The examination and approval notification can include the information of the structured data to be shared, so that the corresponding approver can know the information of the structured data to be shared.

After receiving an approval notification from the server for the structured data to be shared, the client device associated with each approval node may display the approval notification to prompt the corresponding approver to determine whether to allow the structured data to be shared. When the approver determines that the structured data to be shared are allowed to be shared, the corresponding client device can return an approval result for representing approval to pass to the server; when the approver determines that the structured data to be shared is not allowed to be shared, the corresponding client device may return an approval result indicating that the approval is not passed to the server.

The server receives the approval results returned by the client devices associated with the respective approval nodes.

S53: and if an approval result corresponding to at least one approval node is not received, setting the sharing state of the structured data to be shared in the sharing record table of the first tenant to be in approval.

In this embodiment, when at least one client device associated with the approval node does not return an approval result to the server, that is, the server does not receive the approval result corresponding to the at least one approval node, the server may set the sharing state of the structured data to be shared in the sharing record table of the first tenant to be in approval, so as to indicate that the data sharing approval for the structured data has not passed yet, and the structured data is not currently allowed to be shared to the target tenant.

S54: and if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, setting the sharing state of the structured data to be shared as allowed to be shared in the sharing record table of the first tenant.

In this embodiment, when the client devices associated with all the approval nodes all return approval results to the server, that is, the server receives approval results corresponding to all the approval nodes, and the approval results corresponding to all the approval nodes are approved, the server may set the sharing state of the structured data to be shared as permitted to be shared in the sharing record table of the first tenant, so as to indicate that the structured data is currently permitted to be shared to the target tenant.

S55: and if the approval results corresponding to all the approval nodes are received and at least one approval result corresponding to one approval node is approved, setting the sharing state of the structured data to be shared as not-allowed sharing in the sharing record table of the first tenant.

In this embodiment, when the server receives the approval results corresponding to all the approval nodes and the approval results corresponding to at least one approval node are approved and not passed, the server may set the sharing state of the structured data to be shared as not permitted to be shared in the sharing record table of the first tenant to indicate that the data sharing for the structured data is not approved and the structured data is not permitted to be shared to the target tenant.

In another embodiment of the present application, for structured data whose sharing state is allowed to be shared, when the current time reaches the sharing expiration time of the structured data, the server may further update the sharing state of the structured data to be sharing expiration, so as to indicate that the sharing validity period of the structured data has passed, and the structured data is not allowed to be shared to the target tenant currently.

In another embodiment of the present application, the server may further maintain a shared record approval table for each tenant in a data space of each tenant, and the shared record approval table is used for recording information of various approval processes related to each tenant. Based on this, after receiving the approval results returned by the clients associated with the respective approval nodes, the server may further record information of the sharing approval process for the structured data to be shared in the shared record approval table of the first tenant. The information of the shared approval process may include an identifier of the structured data to be shared, an identifier of the shared approval process, an identifier of an approval process template used by the shared approval process, and approval results corresponding to each approval node included in the shared approval process.

As can be seen from the above, according to the interconnection method of the structured data based on the cloud computing service platform provided in this embodiment, when a certain client device corresponding to a first tenant needs to share the structured data with a target tenant, the structured data needs to be approved by the client device corresponding to the tenant and having the data sharing permission, and after the approval is passed, the structured data is allowed to be shared, and the target tenant can acquire information of the structured data from a sharing record table of the first tenant, so that the security of the structured data of the first tenant is further improved.

In another embodiment of the present application, the server may further obtain an upstream-downstream relationship between the first tenant and the target tenant recorded in the interconnection relationship table.

In a possible implementation manner, when the target tenant is an upstream tenant of the first tenant, the server may create a data reception approval process for the target tenant. At least one approval node can be included in the data receiving approval process, and each approval node can be associated with at least one client device corresponding to a target tenant. The server can send an approval notification for the structured data to be shared to the client device corresponding to each approval node in the data receiving approval process, so as to prompt the target tenant to confirm whether the target tenant needs the structured data to be shared. The approval notification may include: the method comprises the steps of identifying the first tenant, identifying the item to which the structured data to be shared belongs, identifying the product to which the structured data to be shared belongs, version information of the structured data to be shared and the like.

If the server receives the approval results returned by all the approval nodes in the data receiving approval process, and the approval results are approved, the server can store the information of the structured data to be shared in the sharing record table of the first tenant. And if the approval result returned by at least one approval node is that the approval is not passed, the server does not record the structured data to be shared in the sharing record table of the first tenant.

In another possible implementation manner, when the target tenant is a downstream tenant of the first tenant, the server may acquire the shared data receiving authority of the target tenant. If the shared data receiving authority of the server is to allow data to be received, the server may store information of the structured data to be shared in the sharing record table of the first tenant. And if the shared data receiving authority of the server is that the data is not allowed to be received, the server does not record the structured data to be shared in the sharing record table of the first tenant.

According to the interconnection method of the structured data based on the cloud computing service platform, each tenant has the authority to select whether to receive shared data shared by other tenants.

Referring to fig. 6, a second schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application is provided. As shown in fig. 6, the difference between the present embodiment and the embodiments corresponding to fig. 3 to fig. 5 is that the present embodiment may further include S61 to S64 after S33, which are detailed as follows:

s61: receiving a modification request from the target tenant for the target structured data.

In this embodiment, the information of the structured data may further include an operation authority of the target tenant for the structured data. Wherein, the operation authority includes but not limited to read only or modification.

In a possible implementation manner, if the operation permission of the target structured data shared by the first tenant to the target tenant is modifiable, when the target tenant needs to modify the target structured data, the client device corresponding to the target tenant may send a modification request for the target structured data to the server. For example, the modification request may carry an identifier of a target tenant, an identifier of target structured data to be modified, content to be modified, and an identifier of a second tenant to which the target structured data to be modified belongs.

S62: creating a modification approval process for the target structured data to be modified for the second tenant, wherein the modification approval process comprises at least one approval node, and each approval node is associated with at least one client device corresponding to the second tenant.

After receiving a modification request aiming at the target structured data from the target tenant, the server can create a modification approval process aiming at the target structured data to be modified for the second tenant based on an approval process template corresponding to the data modification approval process. The modification approval process may include at least one approval node, and each approval node may correspond to at least one approver of the second tenant, that is, each approval node may be associated with at least one client device corresponding to the second tenant.

S63: and sequentially sending an approval notice aiming at the target structured data to be modified to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment.

In this embodiment, after the server creates the modification approval process for the target structured data to be modified, the server may sequentially send an approval notification for the target structured data to be modified to the client device associated with each approval node in the modification approval process. The approval notification may include an identifier of the target tenant, an identifier of the target structured data to be modified, and the content to be modified.

After receiving an approval notification from the server for the target structured data to be modified, the client device associated with each approval node may display the approval notification to prompt the corresponding approver to determine whether to allow the target structured data to be modified by the target tenant. When the approver determines that the target structured data is allowed to be modified by the target tenant, the corresponding client device can return an approval result for representing approval to pass to the server; when the approver determines that the target structured data is not allowed to be modified by the target tenant, the corresponding client device may return an approval result indicating that the approval is not passed to the server.

S64: and if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, modifying the target structured data to be modified in the sharing record table of the second tenant based on the identification of the target structured data to be modified and the content to be modified.

In an embodiment of the application, when the client devices associated with all the approval nodes respectively return approval results to the server, that is, the server receives the approval results corresponding to all the approval nodes, and the approval results corresponding to all the approval nodes are approved, the server may modify the target structured data recorded in the shared record table of the second tenant based on the identifier of the target structured data to be modified and the content to be modified.

In a possible implementation manner of this embodiment, if the server records the target structured data shared by the second tenant to the target tenant in the interconnected data table of the target tenant when sharing the target structured data to be modified with the target tenant, the server may further modify the target structured data recorded in the interconnected data table of the target tenant based on the identifier of the target structured data to be modified and the content to be modified. Therefore, synchronous modification of the interconnection data in different tenants can be realized.

In another embodiment of the present application, when the server does not receive the approval result corresponding to the at least one approval node, or the server receives the approval results corresponding to all approval nodes, but the approval results corresponding to at least one approval node fail, the server may send third prompt information to the target tenant to prompt the target tenant that the target structured data to be modified is not allowed to be modified. At this time, the server does not modify the information of the target structured data recorded in the shared record table of the second tenant or the interconnected data table of the target tenant.

As can be seen from the above, according to the interconnection method of structured data provided in this embodiment, when a target tenant needs to modify structured data shared by a second tenant, a server may create an approval process across tenants (that is, the target tenant and the second tenant), and when the second tenant agrees to modify the process, the server may modify information of the target structured data recorded in a shared record table of the second tenant or an interconnection data table of the target tenant, so as to ensure that structured data shared by each tenant cannot be modified randomly.

Referring to fig. 7, a third schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application is provided. As shown in fig. 7, the difference between the present embodiment and the embodiment corresponding to fig. 3 to 5 is that the present embodiment may further include S71 to S76 after S33, which is detailed as follows:

s71: receiving a sharing request from the target tenant for the target structured data.

In this embodiment, when a target tenant needs to share some target structured data shared by other tenants to another other tenant, the target tenant may send a sharing request for the target structured data (i.e., the structured data to be shared) to the server.

The sharing request for the target structured data to be shared may carry an identifier of a target tenant, an identifier of the target structured data to be shared, an identifier of a tenant to which the target structured data to be shared belongs, and an identifier of a tenant to which the target structured data to be shared is to be shared.

In an embodiment of the present application, the information of the structured data may further include multiple sharing rights of the structured data. When the multiple sharing permission of the structured data is to allow multiple sharing, the target tenant is allowed to share the structured data for the second time after the structured data is shared by the target tenant, namely the target tenant is allowed to share the structured data for another tenant; when the multiple sharing permission of the structured data is that multiple sharing is not allowed, the structural data is shared with the target tenant, and then the target tenant is not allowed to share the structural data for the second time, namely the target tenant is not allowed to share the structural data with other tenants.

Based on this, after receiving a sharing request for the target structured data from the target tenant, the server may query, based on the identifier of the tenant to which the target structured data to be shared belongs and the identifier of the target structured data to be shared, which are carried in the sharing request, multiple sharing permissions of the target structured data from a sharing record table of the tenant to which the target structured data to be shared belongs, and if the multiple sharing permissions of the target structured data are multiple sharing permissions, the server may execute S72; if the multi-sharing authority of the target structured data is not to allow multi-sharing, the server may execute S73-S76.

S72: and if the multiple sharing permission of the target structured data is to allow multiple sharing, recording the information of the target structured data in a sharing record table of the target tenant.

In this embodiment, when the multiple sharing permission of the target structured data is multiple sharing permission, the server may record information of the target structured data in the sharing record table of the target tenant, so that the tenant to be shared of the target structured data may obtain the target structured data from the sharing record table of the target tenant.

S73: and if the multiple sharing permission of the target structured data is that multiple sharing is not allowed, creating a multiple sharing approval process aiming at the target structured data to be shared for the tenant to which the target structured data belongs.

In this embodiment, when the multiple sharing permission of the target structured data is that multiple sharing is not allowed, the server may create, for a tenant to which the target structured data to be shared belongs, a multiple sharing approval process for the target structured data based on an approval process template corresponding to the data sharing approval process. The multiple-sharing approval process may include at least one approval node, and each approval node may correspond to at least one approver in a tenant to which the target structured data to be shared belongs, that is, each approval node may be associated with at least one client device corresponding to the tenant to which the target structured data belongs.

S74: and sequentially sending an approval notice aiming at the target structured data to be shared to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment.

In this embodiment, after the server creates a multiple-sharing approval process for the target structured data to be shared, an approval notification for the target structured data to be shared may be sequentially sent to the client device associated with each approval node in the multiple-sharing approval process. The examination and approval notification can include information of the target structured data to be shared, so that a corresponding approver can know the information of the target structured data to be shared.

After receiving an approval notification from the server for the target structured data to be shared, the client device associated with each approval node may display the approval notification to prompt the corresponding approver to determine whether to allow the target structured data to be shared for multiple times. When the approver determines that the structured data to be shared is allowed to be shared for multiple times, the corresponding client device can return an approval result for representing approval to pass to the server; when the approver determines that the structured data to be shared is not allowed to be shared for multiple times, the corresponding client device may return an approval result indicating that the approval is not passed to the server.

S75: and if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, recording the information of the target structured data in a sharing record table of the target tenant.

In this embodiment, when the client devices associated with all the approval nodes all return approval results to the server, that is, the server receives approval results corresponding to all the approval nodes, and the approval results corresponding to all the approval nodes are approved, it indicates that the target structured data is allowed to be shared for multiple times, and at this time, the server may record information of the target structured data in a shared record table of the target tenant. In this way, the tenant to which the target structured data is to be shared can obtain the information of the target structured data from the sharing record table of the target structured data.

S76: and if the approval results corresponding to all the approval nodes are received and at least one approval result corresponding to the approval node is approved, sending first prompt information to the target tenant, wherein the first prompt information is used for prompting that the target structured data to be shared is not allowed to be shared for multiple times.

In this embodiment, when the server receives the approval results corresponding to all the approval nodes, but at least the approval results corresponding to the expensive approval nodes are that the approval is not passed, it indicates that the target structured data is not allowed to be shared for multiple times, and at this time, the server may send first prompt information to the target tenant to prompt the target tenant that the target structured data is not allowed to be shared for multiple times.

As can be seen from the above, according to the interconnection method of the structured data based on the cloud computing service platform, multiple sharing permissions of the structured data are set in the information of the structured data, so that multiple sharing opportunities can be provided for each structured data, when the multiple sharing permissions of the structured data are not allowed to be shared for multiple times, multiple sharing approval is provided for a tenant to which the structured data belongs, and the target structured data is allowed to be shared for multiple times after approval is passed, so that the security of the target structured data is improved.

Referring to fig. 8, a fourth schematic flowchart of a method for interconnecting structured data based on a cloud computing service platform according to another embodiment of the present application is provided. As shown in fig. 8, the difference between the present embodiment and the embodiments corresponding to fig. 3 to 5 is that the present embodiment may further include S81 to S83 after S33, which is detailed as follows:

s81: receiving an interconnection data mounting request from the target tenant, wherein the interconnection data mounting request carries information of target structured data to be mounted.

In this embodiment, when a target tenant wants to mount a certain target structured data shared by other tenants to a certain data node of a certain structured data of the target tenant, the target tenant may send an interconnection data mount request carrying information of the target structured data to be mounted to a server.

The information of the target structured data to be mounted may include an identifier of the target structured data to be mounted, an identifier of a data node to be mounted in the target structured data to be mounted, an identifier of structured data to be mounted in the target structured data to be mounted, an identifier of a data node to be mounted in the structured data to be mounted, and an identifier of a tenant to which the target structured data to be mounted belongs.

S82: and mounting the data node to be mounted under the data node to be mounted based on the information of the target structured data to be mounted.

After receiving an interconnection data mounting request from target data, the server may query, from a data sharing table of a tenant, information of a data node to be mounted under the target structured data to be mounted, based on an identifier of the tenant to which the target structured data to be mounted belongs, an identifier of the target structured data to be mounted, and an identifier of the data node to be mounted, which are carried in the interconnection data mounting request, and mount the information of the data node to be mounted under the data node to be mounted.

In one possible implementation manner, the mounting, by the server, the data node to be mounted to the server may include: and creating a new data node under the data node to be mounted, and associating the information of the data node to be mounted with the new data node.

S83: and recording the information of the target structured data to be mounted in a data mounting table of the tenant.

In this embodiment, the server may further maintain a data mount table in the data space of each tenant, and the data mount table is used to record information of structured data mounted by other tenants in the structured data of each tenant.

Based on this, after the server mounts the data node to be mounted under the data node to be mounted, the server may further record information of the target structured data to be mounted in the data mounting table of the tenant to which the target structured data belongs.

It should be noted that structured data of a list class cannot be mounted.

As can be seen from the above, according to the interconnection method of the structured data based on the cloud computing service platform provided by the embodiment, the target structured data shared by other tenants to the target tenant is mounted under the structured data of the target tenant, so that the linkage analysis of the structured data of the target tenant and the target structured data to be mounted can be realized.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Based on the interconnection method of the structured data based on the cloud computing service platform provided by the embodiment, the embodiment of the invention further provides an embodiment of a server for implementing the embodiment of the method. Please refer to fig. 9, which is a schematic structural diagram of a server according to an embodiment of the present application. For convenience of explanation, only the portions related to the present embodiment are shown. As shown in fig. 9, the server 90 may include: a first receiving unit 91, a first querying unit 92 and a first communication unit 93. Wherein:

the first receiving unit 91 is configured to receive an interconnection data acquisition request from a target tenant, where the interconnection data acquisition request carries an identifier of the target tenant.

The first query unit 92 is configured to query, based on the identifier of the target tenant, information of target structured data corresponding to the identifier of the target tenant from a sharing record table of a tenant that has an interconnection relationship with the target tenant, where the information of the target structured data includes a sharing state of the target structured data.

The first communication unit 93 is configured to send the information of the target structured data, which is in the sharing state allowed to be shared, to the target tenant, so that the target tenant displays and/or operates the information of the target structured data.

Optionally, the server 90 may further include: a second receiving unit, a judging unit and a first recording unit.

The second receiving unit is configured to receive a data sharing request from a first tenant, where the data sharing request carries information of structured data to be shared, and the information of the structured data to be shared includes an identifier of the first tenant, an identifier of the structured data to be shared, and an identifier of a target tenant to which the structured data to be shared is to be shared.

The judging unit is used for judging whether an interconnection relationship is established between the first tenant and the target tenant.

The first recording unit is configured to record information of the structured data to be shared in a sharing record table of the first tenant if an interconnection relationship is established between the first tenant and the target tenant.

Optionally, the server 90 may further include: the device comprises a first approval process creating unit, a second communication unit and a sharing state setting unit. Wherein:

the first approval process creating unit is configured to create a shared approval process for the structured data to be shared for the first tenant, where the shared approval process includes at least one approval node, and each approval node is associated with at least one client device corresponding to the first tenant.

The second communication unit is used for sequentially sending an approval notice aiming at the structured data to be shared to the client equipment associated with each approval node and receiving an approval result returned by the client equipment.

The sharing state setting unit is used for setting the sharing state of the structured data to be shared in the sharing record table of the first tenant to be approved if an approval result corresponding to at least one approval node is not received; if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, setting the sharing state of the structured data to be shared as allowed to be shared in the sharing record table of the first tenant; and if the approval results corresponding to all the approval nodes are received and at least one approval result corresponding to one approval node is approved, setting the sharing state of the structured data to be shared as not-allowed sharing in the sharing record table of the first tenant.

Optionally, the information of the target structured data further includes a storage right of the target structured data; the server 90 may also include an information storage unit.

The information storage unit is used for storing the information of the target structured data in the data space of the target tenant if the storage authority of the target structured data is allowed to be stored.

Optionally, the server 90 may further include a third communication unit, a second approval process creating unit, a fourth communication unit, and a data updating unit. Wherein:

the third communication unit is configured to receive a modification request for the target structured data from the target tenant, where the modification request carries an identifier of the target tenant, an identifier of the target structured data to be modified, content to be modified, and an identifier of a second tenant to which the target structured data to be modified belongs.

The second approval process creating unit is configured to create, for the second tenant, a modification approval process for the target structured data to be modified, where the modification approval process includes at least one approval node, and each approval node is associated with at least one client device corresponding to the second tenant.

The fourth communication unit is configured to sequentially send an approval notification for the target structured data to be modified to the client device associated with each approval node, and receive an approval result returned by the client device, where the approval notification carries an identifier of the target tenant, an identifier of the target structured data to be modified, and the content to be modified.

And the data updating unit is used for modifying the target structured data to be modified in the sharing record table of the second tenant based on the identification of the target structured data to be modified and the content to be modified if all the approval results corresponding to the approval nodes are received and all the approval results corresponding to the approval nodes are approved.

Optionally, the information of the target structured data further includes multiple sharing permissions for the target structured data; the server 90 may further include: the system comprises a fifth communication unit, a second recording unit, a third approval process creating unit, a sixth communication unit, a third recording unit and a seventh communication unit. Wherein:

the fifth communication unit is configured to receive a sharing request for the target structured data from the target tenant, where the sharing request carries an identifier of the target tenant, an identifier of the target structured data to be shared, an identifier of a tenant to which the target structured data to be shared belongs, and an identifier of a tenant to which the target structured data to be shared is to be shared.

The second recording unit is configured to record information of the target structured data in a sharing record table of the target tenant if the multiple sharing permission of the target structured data is to allow multiple sharing.

The third approval process creating unit is configured to create, for the tenant to which the target structured data belongs, a multiple-sharing approval process for the target structured data to be shared if multiple-sharing permission of the target structured data is not allowed for multiple sharing, where the multiple-sharing approval process includes at least one approval node, and each approval node is associated with at least one client device corresponding to the tenant to which the target structured data belongs.

The sixth communication unit is configured to send an approval notification for the target structured data to be shared to the client device associated with each approval node in sequence, and receive an approval result returned by the client device.

And the third recording unit is used for recording the information of the target structured data in a sharing record table of the target tenant if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved.

The seventh communication unit is configured to send first prompt information to the target tenant if all the approval results corresponding to the approval nodes are received and at least one approval result corresponding to the approval node is that the approval is not passed, where the first prompt information is used to prompt that the target structured data to be shared is not allowed to be shared for multiple times.

Optionally, the server 90 may further include: an eighth communication unit, a data mounting unit, and a fourth recording unit. Wherein:

the eighth communication unit is configured to receive an interconnection data mount request from the target tenant, where the interconnection data mount request carries information of target structured data to be mounted, and the information of the target structured data to be mounted includes an identifier of the target structured data to be mounted, an identifier of a data node to be mounted in the target structured data to be mounted, an identifier of structured data to be mounted in the target structured data to be mounted, an identifier of a data node to be mounted in the structured data to be mounted, and an identifier of a tenant to which the target structured data to be mounted belongs.

The data mounting unit is used for mounting the data node to be mounted to the data node to be mounted based on the information of the target structured data to be mounted.

The fourth recording unit is used for recording the information of the target structured data to be mounted in the data mounting table of the tenant.

It should be noted that, for the information interaction, the execution process, and other contents between the above units, the specific functions and the technical effects brought by the method embodiments of the present application are based on the same concept, and specific reference may be made to the method embodiment part, which is not described herein again.

It is obvious to those skilled in the art that, for convenience and simplicity of description, the above division of each functional unit is merely illustrated, and in practical applications, the above function distribution may be performed by different functional units according to needs, that is, the internal structure of the server is divided into different functional units to perform all or part of the above described functions. Each functional unit in the embodiments may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the application. The specific working process of the units in the system may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.

Please refer to fig. 10, which is a schematic structural diagram of a server according to another embodiment of the present application. As shown in fig. 10, the server 10 provided in the present embodiment may include: a processor 100, a memory 101 and a computer program 102 stored in the memory 101 and executable on the processor 100, for example a program corresponding to an interconnect method for structured data. The processor 100, when executing the computer program 102, implements the steps of the above-described embodiments of the method for interconnecting structured data, such as S31-S33 shown in FIG. 3. Alternatively, the processor 100, when executing the computer program 102, implements the functions of the modules/units in the server embodiment described above, such as the functions of the units 91-93 shown in FIG. 9.

Illustratively, the computer program 102 may be partitioned into one or more modules/units, which are stored in the memory 101 and executed by the processor 100 to accomplish the present application. One or more of the modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 102 in the server 10. For example, the computer program 102 may be divided into a first receiving unit, a first querying unit and a first communication unit, and the specific functions of each unit refer to the related descriptions in the embodiment corresponding to fig. 9, which are not described herein again.

Those skilled in the art will appreciate that FIG. 10 is merely an example of a server 10 and is not intended to limit server 10 and may include more or less components than those shown, or some components in combination, or different components.

The processor 100 may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 101 may be an internal storage unit of the server 10, such as a hard disk or a memory of the server 10. The memory 101 may also be an external storage device of the server 10, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, or a flash memory card (flash card) provided on the server 10. Further, the memory 101 may also include both an internal storage unit of the server 10 and an external storage device. The memory 101 is used for storing computer programs and other programs and data required by the server. The memory 101 may also be used to temporarily store data that has been output or is to be output.

The embodiments of the present application further provide a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

The embodiments of the present application provide a computer program product, which when running on a server, enables the server to implement the steps in the above method embodiments when executed.

In the above embodiments, the description of each embodiment has its own emphasis, and parts that are not described or illustrated in a certain embodiment may refer to the description of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. The interconnection method of the structured data based on the cloud computing service platform is characterized by being applied to a server, wherein the server is used for providing data interconnection service based on the cloud computing service platform; the interconnection method comprises the following steps:

2. The interconnection method according to claim 1, wherein before the obtaining of the information of the target structured data corresponding to the identifier of the target tenant from the sharing record table of the tenant having an interconnection relationship with the target tenant, the interconnection method further comprises:

receiving a data sharing request from a first tenant, wherein the data sharing request carries information of structured data to be shared, and the information of the structured data to be shared comprises an identifier of the first tenant, an identifier of the structured data to be shared and an identifier of a target tenant to which the structured data to be shared is to be shared;

judging whether an interconnection relation is established between the first tenant and the target tenant;

and if the interconnection relationship is established between the first tenant and the target tenant, recording the information of the structured data to be shared in a sharing record table of the first tenant.

3. The interconnection method according to claim 2, wherein after recording the information of the structured data to be shared in the sharing record table of the first tenant, the interconnection method further comprises:

creating a sharing approval process for the structured data to be shared for the first tenant, wherein the sharing approval process comprises at least one approval node, and each approval node is associated with at least one client device corresponding to the first tenant;

sequentially sending an approval notice aiming at the structured data to be shared to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment;

if an approval result corresponding to at least one approval node is not received, setting the sharing state of the structured data to be shared in the sharing record table of the first tenant to be in approval;

if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, setting the sharing state of the structured data to be shared as allowed to be shared in the sharing record table of the first tenant;

and if the approval results corresponding to all the approval nodes are received and at least one approval result corresponding to one approval node is approved, setting the sharing state of the structured data to be shared as not-allowed sharing in the sharing record table of the first tenant.

4. The interconnection method according to any one of claims 1 to 3, wherein the information of the target structured data further includes a stored authority of the target structured data; correspondingly, after the information of the target structured data in the sharing state allowed to be shared is sent to the target tenant, the interconnection method further includes:

5. The interconnection method according to any one of claims 1 to 3, wherein after the sending the information of the target structured data whose sharing status is allowed to be shared to the target tenant, the interconnection method further comprises:

receiving a modification request aiming at the target structured data from the target tenant, wherein the modification request carries an identifier of the target tenant, an identifier of the target structured data to be modified, content to be modified and an identifier of a second tenant to which the target structured data to be modified belongs;

creating a modification approval process for the target structured data to be modified for the second tenant, wherein the modification approval process comprises at least one approval node, and each approval node is associated with at least one client device corresponding to the second tenant;

sequentially sending an approval notice aiming at the target structured data to be modified to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment, wherein the approval notice carries the identification of the target tenant, the identification of the target structured data to be modified and the content to be modified;

and if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, modifying the target structured data to be modified in the sharing record table of the second tenant based on the identification of the target structured data to be modified and the content to be modified.

6. The interconnection method according to any one of claims 1 to 3, wherein the information of the target structured data further includes multiple sharing rights for the target structured data; correspondingly, after the information of the target structured data in the sharing state allowed to be shared is sent to the target tenant, the interconnection method further includes:

receiving a sharing request aiming at the target structured data from the target tenant, wherein the sharing request carries an identifier of the target tenant, an identifier of the target structured data to be shared, an identifier of a tenant to which the target structured data to be shared belongs, and an identifier of a tenant to which the target structured data to be shared is to be shared;

if the multiple sharing permission of the target structured data is to allow multiple sharing, recording the information of the target structured data in a sharing record table of the target tenant;

if the multiple sharing permission of the target structured data is that multiple sharing is not allowed, a multiple sharing approval process for the target structured data to be shared is established for the affiliated tenant, wherein the multiple sharing approval process comprises at least one approval node, and each approval node is associated with at least one client device corresponding to the affiliated tenant;

sequentially sending an approval notice aiming at the target structured data to be shared to the client equipment associated with each approval node, and receiving an approval result returned by the client equipment;

if the approval results corresponding to all the approval nodes are received and the approval results corresponding to all the approval nodes are approved, recording the information of the target structured data in a sharing record table of the target tenant;

and if the approval results corresponding to all the approval nodes are received and at least one approval result corresponding to the approval node is approved, sending first prompt information to the target tenant, wherein the first prompt information is used for prompting that the target structured data to be shared is not allowed to be shared for multiple times.

7. The interconnection method according to any one of claims 1 to 3, wherein after sending the information of the target structured data whose sharing status is allowed to be shared to the target tenant, the interconnection method further comprises:

receiving an interconnection data mounting request from the target tenant, wherein the interconnection data mounting request carries information of target structured data to be mounted, and the information of the target structured data to be mounted comprises an identifier of the target structured data to be mounted, an identifier of a data node to be mounted in the target structured data to be mounted, an identifier of structured data to be mounted in the target structured data to be mounted, an identifier of a data node to be mounted in the structured data to be mounted, and an identifier of a tenant to which the target structured data to be mounted belongs;

based on the information of the target structured data to be mounted, mounting the data node to be mounted under the data node to be mounted;

and recording the information of the target structured data to be mounted in a data mounting table of the tenant.

8. The server is characterized in that the server is used for providing data interconnection services based on a cloud computing service platform; the server includes:

9. A server comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor implementing the interconnection method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the interconnection method according to any one of claims 1 to 7.