Cloud data docking method, device and equipment and storage medium

Abstract

The embodiment of the invention discloses a cloud data docking method and device, equipment and a storage medium, and the method comprises the steps: carrying out the format conversion of target configuration data according to a preset interface rule in response to an input instruction of the target configuration data, and obtaining a target cloud identifier, a target function module identifier and a target access key; performing instantiation configuration according to the target cloud identifier and the function module identifier, and performing cloud login verification according to a configuration result of the instantiation configuration and the target access key; and under the condition that the cloud login verification is successful, obtaining a first key certificate, and accessing a cloud corresponding to the target cloud identifier based on the first key certificate to realize data docking. The docking standards of multiple cloud manufacturers can be unified, and the efficiency of accessing the cloud manufacturers and the switching efficiency among the multiple cloud manufacturers are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a cloud data docking method, device, equipment and storage medium. Background Art

[0002] The cloud is a data storage and processing method based on Internet technology. By storing data on a remote server, data can be accessed anytime and anywhere, and users can access data at any time and any place through any device. Secondly, the cloud has strong scalability and can dynamically adjust resources according to user needs. In addition, the cloud also has high security and can protect data security through various technical means. Cloud vendors refer to providers that provide cloud computing services. They build a data center platform and distribute data, applications and other resources to it through the network to provide services to users. These service providers can help users quickly build their own information systems or develop new applications through their own brands and technical solutions to realize business value.

[0003] In the related technology, during the process of data connection between users and cloud vendors, due to the inconsistent standards of various cloud vendors, each cloud vendor has its own unique interface and management tools, which requires developers to write specific codes for each cloud platform, thereby affecting the efficiency of data connection with the cloud vendor. When switching between multiple cloud vendors, it also affects the switching efficiency between cloud vendors accordingly. Summary of the invention

[0004] The embodiments of the present application provide a cloud data docking method, device, equipment and storage medium, which solves the problem that the inconsistent standards of various cloud vendors affect the efficiency of accessing cloud vendors and the efficiency of switching between cloud vendors. It can unify the docking standards of multiple cloud vendors, improve the efficiency of accessing cloud vendors and the efficiency of switching between multiple cloud vendors.

[0005] In a first aspect, an embodiment of the present application provides a cloud data docking method, comprising:

[0006] In response to an input instruction of target configuration data, the target configuration data is formatted according to a preset interface rule to obtain a target cloud identifier, a target functional module identifier, and a target access key;

[0007] Performing instantiation configuration according to the target cloud identifier and the target functional module identifier, and performing cloud login verification according to the configuration result of the instantiation configuration and the target access key;

[0008] When the cloud login verification is successful, a first key credential is obtained, and based on the first key credential, the cloud corresponding to the target cloud identifier is accessed to achieve data docking.

[0009] Optionally, the target configuration data includes target docking data and docking request data, and the target configuration data is formatted according to a preset interface rule to obtain a target cloud identifier, a target function module identifier, and a target access key, including:

[0010] The target docking data is formatted according to a first preset rule to obtain a target cloud identifier and a target functional module identifier, and the docking request data is formatted according to a second preset rule to obtain a target access key.

[0011] Optionally, the target docking data includes a cloud interface and a functional interface, and the format conversion of the target docking data according to the first preset rule to obtain a target cloud identifier and a target functional module identifier includes:

[0012] Determine a first mapping interface format of the cloud interface and a second mapping interface format of the functional interface according to a first preset rule;

[0013] The cloud interface is format-converted according to the first mapping interface format to obtain a target cloud identifier, and the functional interface is format-converted according to the second mapping interface format to obtain a target functional module identifier.

[0014] Optionally, converting the format of the functional interface according to the second mapping interface format to obtain a target functional module identifier includes:

[0015] Performing format conversion on each functional interface according to the second mapping interface format to obtain a target functional interface corresponding to each functional interface;

[0016] The target functional interfaces corresponding to the functional interfaces are combined to obtain a target functional module identifier.

[0017] Optionally, after obtaining the target cloud identifier, the target function module identifier and the target access key, the method further includes:

[0018] Arrange the target cloud identifier, the target functional module identifier, and the target access key according to the command arrangement sequence in the preset interface rule to obtain a corresponding position tag;

[0019] Accordingly, the instantiation configuration according to the target cloud identifier and the functional module identifier includes:

[0020] Automatic instantiation configuration is performed according to the location tag of the target cloud identifier and the location tag of the functional module identifier.

[0021] Optionally, performing instantiation configuration according to the target cloud identifier and the functional module identifier, and performing cloud login verification according to the configuration result of the instantiation configuration and the target access key, includes:

[0022] Perform attribute configuration and method configuration according to the target cloud identifier and the functional module identifier to generate a target constructor;

[0023] The target constructor is called through the target access key to perform cloud login verification.

[0024] Optionally, after obtaining the first key certificate, the method further includes:

[0025] Determine the validity of the first key certificate, and when the first key certificate is invalid, connect to a preset time interface, obtain a first time parameter through the preset time interface, and obtain a source code file of the target cloud according to the target cloud identifier;

[0026] A second time parameter in the source code file is identified, the second time parameter is replaced with the first time parameter, and a second key credential is obtained.

[0027] In a second aspect, an embodiment of the present application provides a cloud data docking device, including:

[0028] A format conversion module, configured to respond to an input instruction of target configuration data and convert the target configuration data into a format according to a preset interface rule to obtain a target cloud identifier, a target function module identifier, and a target access key;

[0029] An instantiation configuration module, used to perform instantiation configuration according to the target cloud identifier and the functional module identifier;

[0030] A login verification module, used to perform cloud login verification according to the configuration result of the instantiated configuration and the target access key;

[0031] The data docking module is used to obtain a first key certificate when the cloud login verification is successful, and access the cloud corresponding to the target cloud identifier based on the first key certificate to achieve data docking.

[0032] In a third aspect, an embodiment of the present application provides a cloud data docking device, comprising: one or more processors; a storage device configured to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the cloud data docking method described in the first aspect.

[0033] In a fourth aspect, an embodiment of the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the cloud data docking method as described in the first aspect.

[0034] The embodiment of the present application converts the target configuration data into a format according to preset interface rules in response to an input instruction of the target configuration data, obtains a target cloud identifier, a target functional module identifier, and a target access key; performs instantiation configuration according to the target cloud identifier and the functional module identifier, and performs cloud login verification according to the configuration result of the instantiation configuration and the target access key; in the case of successful cloud login verification, obtains the first key credential, and accesses the cloud corresponding to the target cloud identifier based on the first key credential to achieve data docking. The target configuration data can be formatted by setting a unified interface rule so that the access format of each cloud is the same, thereby performing data instantiation configuration based on a unified format, avoiding the impact of the format of the target configuration data on the instantiation configuration efficiency, improving the configuration efficiency, and correspondingly improving the efficiency of data docking with the cloud. By obtaining the first key credential and accessing the target cloud based on the first key credential, the security of cloud data can be guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 is a flow chart of a cloud data docking method provided in an embodiment of the present application;

[0036] Figure 2 is a flow chart of a method for format conversion of target configuration data provided by an embodiment of the present application;

[0037] Figure 3 is a flow chart of a key credential acquisition method provided in an embodiment of the present application;

[0038] Figure 4 It is a structural schematic diagram of a cloud data docking device provided in an embodiment of the present application;

[0039] Figure 5 It is a structural diagram of a cloud data docking device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

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

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

[0043] In the following, in conjunction with the accompanying drawings, a cloud data docking method, device, equipment and medium provided by the embodiments of the present application are described in detail through specific embodiments and their application scenarios.

[0044] The cloud data docking method provided in the embodiment of the present application is used in the scenario of data docking between physical storage and cloud, such as migrating resources on physical storage to the cloud or downloading resources from the cloud to physical storage devices. Based on the above usage scenarios, it can be understood that the execution subject of this solution can be a server or a client, etc., and the server or the client can be a notebook.

[0045] Figure 1 is a flow chart of a cloud data connection method provided in an embodiment of the present application. Figure 1As shown, including:

[0046] Step S101, in response to an input instruction of target configuration data, convert the format of the target configuration data according to a preset interface rule to obtain a target cloud identifier, a target functional module identifier and a target access key.

[0047] Among them, the target configuration data can be the operation data to be executed entered by the developer in the client or server. The target configuration data can be the access data of the cloud. The input instruction of the target configuration data can be the instruction sent by the developer to indicate the completion of the input by selecting the corresponding completion option after the configuration data input is completed. The preset interface rule is the data used to represent the interface configuration standard, and the interface configuration rule can be the naming rule of the interface and the calling rule of the interface, etc. Among them, the format conversion can be the conversion of the execution order of the data according to the corresponding format, or the conversion of the programming language of the data. The target cloud identifier can be an identifier used to indicate the cloud to be accessed, which can be the name of the cloud vendor and the ID of the cloud, etc. The target function module identifier can be a function module corresponding to the function to be executed, and the target function module identifier can also be the name of the function module. The target access key is the login credential used to log in to the cloud vendor, which can be the cloud merchant login password set when registering a cloud merchant account.

[0048] In one embodiment, the input behavior of the user or developer is monitored in real time. When the user or developer is detected to input the target configuration data, the target configuration data is obtained, and the target configuration data is formatted according to the preset interface rules to obtain the target cloud identifier, target function module identifier and target access key of the unified rules. In another possible embodiment, after obtaining the target configuration data, the cloud identifier, function module identifier and key in the target configuration data are identified, and the corresponding rules are used to format the identified cloud identifier, function module identifier and key respectively to obtain the target cloud identifier, target function module identifier and target access key.

[0049] Step S102: perform instantiation configuration according to the target cloud identifier and the target functional module identifier, and perform cloud login verification according to the configuration result of the instantiation configuration and the target access key.

[0050] Among them, the instantiation configuration can be the configuration of a specific instance object and the specific operation method of configuring the instance object. Cloud login verification is a security verification performed during the cloud login process to ensure the security of cloud data. In one embodiment, the instance object is initialized, such as initializing an executor, and the executor is configured according to the target cloud identifier and the functional module identifier, so that the executor can access the corresponding cloud vendor's response functional module based on the configuration information. According to the access location indicated by the target cloud identifier and the target functional module identifier, the executor uses the target access key to make a cloud login request to the target location.

[0051] Step S103: when the cloud login verification is successful, obtain a first key credential, and access the cloud corresponding to the target cloud identifier based on the first key credential to achieve data docking.

[0052] Among them, the first key credential is a security credential for accessing the cloud, and the first key can be a temporary verification code. Data docking refers to the data interaction process between two or more devices, such as uploading, downloading, thawing, valid file verification, and file retrieval. In one embodiment, after receiving the cloud login request, the target cloud performs security verification on the target access key, and returns the first key credential if the verification passes. The client or server accesses the cloud indicated by the target cloud identifier based on the received first key credential and performs data docking with the cloud.

[0053] In the above, by responding to the input instruction of the target configuration data, the target configuration data is formatted according to the preset interface rules to obtain the target cloud identifier, the target function module identifier and the target access key; the instantiation configuration is performed according to the target cloud identifier and the target function module identifier, and the cloud login verification is performed according to the configuration result of the instantiation configuration and the target access key; in the case of successful cloud login verification, the first key credential is obtained, and the cloud corresponding to the target cloud identifier is accessed based on the first key credential to achieve data docking. The target configuration data can be formatted by setting a unified interface rule so that the access format of each cloud is the same, thereby performing data instantiation configuration based on a unified format, avoiding the impact of the format of the target configuration data on the instantiation configuration efficiency, improving the configuration efficiency, and correspondingly improving the efficiency of data docking with the cloud. By obtaining the first key credential and accessing the target cloud based on the first key credential, the security of cloud data can be guaranteed.

[0054] In one embodiment, after obtaining the target cloud identifier, the target function module identifier and the target access key, the method further includes:

[0055] Arrange the target cloud identifier, the target functional module identifier, and the target access key according to the command arrangement sequence in the preset interface rule to obtain a corresponding position tag;

[0056] Accordingly, the instantiation configuration according to the target cloud identifier and the functional module identifier includes:

[0057] Automatic instantiation configuration is performed according to the location tag of the target cloud identifier and the location tag of the functional module identifier.

[0058] Among them, the command arrangement order can be used to indicate the positional relationship between the various configuration parameters, such as configuring the target cloud identifier first, configuring the target function module identifier associated with it based on the target cloud identifier after the configuration is completed, and finally configuring the target access key. The location tag can be used to indicate the configuration position or identification position of the configuration parameter. In one embodiment, the position arrangement is performed in the order of the target cloud identifier, the target function module identifier and the target access key according to the command arrangement order in the preset interface rules, and the location tags of the target cloud identifier, the target function module identifier and the target access key are determined respectively. In the instantiation configuration process, the required configuration parameters are quickly determined based on the location tags, such as obtaining the target cloud identifier of tag 1 and the function module identifier of tag 2 respectively, and performing instantiation configuration based on the target cloud identifier and the function module identifier corresponding to the corresponding location tags obtained.

[0059] In the above, the target cloud identifier, the target functional module identifier, and the target access key are arranged in position according to the command arrangement order in the preset interface rules, and the corresponding location tags are obtained, and the instantiation configuration is automatically performed according to the location tags of the target cloud identifier and the location tags of the functional module identifier. The required configuration parameters can be quickly determined based on the location tags, and the instantiation configuration is performed based on the obtained configuration parameters, further improving the efficiency of the instantiation configuration.

[0060] In one embodiment, the instantiation configuration is performed according to the target cloud identifier and the functional module identifier, and the cloud login verification is performed according to the configuration result of the instantiation configuration and the target access key, including:

[0061] Perform attribute configuration and method configuration according to the target cloud identifier and the functional module identifier to generate a target constructor;

[0062] The target constructor is called through the target access key to perform cloud login verification.

[0063] Among them, property configuration is to configure the specific content that can be obtained or the operations that can be performed through the interface. Method configuration can be a method for configuring the call to the docking interface. The target constructor is a special function, which is mainly used to initialize the object when creating the object. The parameters in the constructor can represent specific operation data. The corresponding interface and the data obtained through the interface are further called by calling the constructor. In one embodiment, the access interface of the target cloud and the access interface of the target functional module are determined according to the target cloud identifier, and the interface calling method is configured according to the access interface of the target cloud and the access interface of the target functional module. The properties are configured according to the functions that the target functional module can realize, and the target constructor is generated based on the method configuration results and the property configuration results. The target constructor is called and executed through the target access key to perform cloud login verification, which can provide a standardized, flexible and reliable way for object creation and initialization by generating a target constructor.

[0064] Figure 2 is a flow chart of a method for format conversion of target configuration data provided by an embodiment of the present application, such as Figure 2 As shown, including:

[0065] Step S201, in response to the input instruction of the target configuration data, the target docking data is formatted according to the first preset rule to obtain the target cloud identifier and the target function module identifier, the docking request data is formatted according to the second preset rule to obtain the target access key, and the target cloud identifier, the target function module identifier and the target access key are obtained.

[0066] In one embodiment, the target configuration data includes target docking data and docking request data, wherein the target docking data may be used to indicate the data docking address such as the interface name, the cloud name, the function module name, or may be used to indicate the data docking method, such as methods such as uploading data, downloading data, and verifying data. The docking request data may be data for requesting data docking or data for ensuring the security of the request, such as the cloud login account, login password, and identity information of data docking related personnel. The first preset rule may be a preset docking data conversion rule, and the second preset rule may be a preset docking request data conversion rule. In one embodiment, in response to the input instruction of the target configuration data, the target docking data is formatted according to the preset docking data conversion rule, and the docking request data is formatted according to the preset docking request data conversion rule. Exemplarily, the first preset rule is used to convert the original cloud name and the function module name into a unified interface address to obtain the target cloud identifier and the target function module identifier. A unified http call method is used to access the target cloud identifier and the target function module identifier. The second preset rule is used to convert the login password or access key in the docking request data into binary to obtain the target access key.

[0067] Step S202: perform instantiation configuration according to the target cloud identifier and the target functional module identifier, and perform cloud login verification according to the configuration result of the instantiation configuration and the target access key.

[0068] Step S203: When the cloud login verification is successful, obtain a first key certificate, and access the cloud corresponding to the target cloud identifier based on the first key certificate to achieve data docking.

[0069] In the above, the target cloud identifier and the target functional module identifier are obtained by formatting the target docking data according to the first preset rule, and the target access key is obtained by formatting the docking request data according to the second preset rule. Different conversion rules can be used based on different types of configuration data, thereby improving the accuracy of configuration data conversion.

[0070] In one embodiment, the target docking data includes a cloud interface and a functional interface, and the format conversion of the target docking data according to the first preset rule to obtain a target cloud identifier and a target functional module identifier includes:

[0071] Determine a first mapping interface format of the cloud interface and a second mapping interface format of the functional interface according to a first preset rule;

[0072] The cloud interface is format-converted according to the first mapping interface format to obtain a target cloud identifier, and the functional interface is format-converted according to the second mapping interface format to obtain a target functional module identifier.

[0073] Among them, the cloud interface is an access interface for accessing cloud data, and the functional interface is an access interface for accessing the functional module. The first mapping interface format is a format for representing the cloud interface, such as the cloud name, cloud ID, and cloud access address. The second mapping interface format is a format for representing the functional module interface, such as the module name, function name, and module address. In one embodiment, a combination of the first mapping interface format and the second mapping interface format can be set in the first preset rule. Exemplarily, combination one: the first mapping interface format is the cloud name, and the second mapping interface format is the function name. Combination two: the first mapping interface format is the cloud ID, and the second mapping interface format is the function ID. Combination three: the first mapping interface format is the cloud ID, and the second mapping interface format is the function name. In order to facilitate the distinction between the cloud interface and the function interface, the first mapping interface format can be determined as the cloud ID, the second mapping interface format can be obtained as the function name, and the cloud interface can be converted into the corresponding cloud ID, the cloud interface to be accessed is represented by the cloud ID, the function interface is converted into the corresponding function name, and the function interface to be accessed is represented by the function name.

[0074] In one embodiment, converting the format of the functional interface according to the second mapping interface format to obtain a target functional module identifier includes:

[0075] Performing format conversion on each functional interface according to the second mapping interface format to obtain a target functional interface corresponding to each functional interface;

[0076] The target functional interfaces corresponding to the functional interfaces are combined to obtain a target functional module identifier.

[0077] Among them, the target function interface can be an interface that satisfies the second mapping interface format. Optionally, the target configuration data may include one or more cloud identifiers and function module identifiers. When the target configuration data includes multiple function module identifiers, each function module identifier is formatted according to the second mapping interface format to obtain a target function interface corresponding to each function interface, and the interface identifiers of each target function interface are combined. For example, if each target function interface is function A, function B, function C, and function D, the interface identifiers of the function interface are combined to obtain a target function module identifier of A→B→C→D. In an embodiment of the present application, the target function module identifiers obtained by combining multiple target function interfaces are configured simultaneously, and the interfaces can be automatically combined according to actual needs, thereby realizing timed function development and improving user experience.

[0078] Figure 3 is a flowchart of a key credential acquisition method provided in an embodiment of the present application, such as Figure 3 As shown, including:

[0079] Step S301, determine the validity of the first key certificate. When the first key certificate is invalid, connect to a preset time interface, obtain a first time parameter through the preset time interface, and obtain a source code file of the target cloud according to the target cloud identifier.

[0080] Among them, the first time parameter is the current time of the server. The source code file of the target cloud is used to store all configuration information of the target cloud. In one embodiment, in order to ensure the security of cloud data, the first key certificate used to access the cloud has a certain timeliness. The client may need to change the time of the device based on actual business needs. Therefore, there will be a situation where the time of the client and the cloud is inconsistent, which will cause the first key certificate obtained to be invalid. Therefore, after obtaining the first key certificate, the timeliness of the first key certificate is determined. When the first key certificate expires, the preset time interface is connected, and the current time of the server is obtained through the preset time interface, and the source code file of the target cloud is obtained at the same time.

[0081] Step S302: Identify a second time parameter in the source code file, replace the second time parameter with the first time parameter, and obtain a second key certificate.

[0082] The second key credential is a valid access credential of the target cloud. The second time parameter is the current time of the target cloud. The source code file of the target cloud is parsed to obtain the parsed data of the target cloud, the second time parameter in the parsed data is identified, the second time parameter is replaced with the first time parameter and the source code file of the target cloud is updated after the replacement, and the cloud login verification is re-performed through the method of step S102. If the cloud login verification is successful, the second key credential is obtained.

[0083] In the above, by judging the validity of the first key certificate, when the first key certificate is invalid, the preset time interface is connected, the first time parameter is obtained through the preset time interface, and the source code file of the target cloud is obtained according to the target cloud identifier; the second time parameter in the source code file is identified, the second time parameter is replaced with the first time parameter, and the second key certificate is obtained. The replacement of the time parameter can avoid the problem of access failure caused by the inconsistency between the client system time and the cloud time, and correspondingly improve the data docking effect.

[0084] Figure 4 is a schematic diagram of the structure of a cloud data docking device provided in an embodiment of the present application, such as Figure 4 As shown, including:

[0085] The format conversion module 41 is used to respond to the input instruction of the target configuration data and convert the format of the target configuration data according to the preset interface rules to obtain the target cloud identifier, the target function module identifier and the target access key;

[0086] An instantiation configuration module 42, configured to perform instantiation configuration according to the target cloud identifier and the functional module identifier;

[0087] A login verification module 43, configured to perform cloud login verification according to the configuration result of the instantiated configuration and the target access key;

[0088] The data docking module 44 is used to obtain a first key certificate when the cloud login verification is successful, and access the cloud corresponding to the target cloud identifier based on the first key certificate to achieve data docking.

[0089] In a possible embodiment, the target configuration data includes target docking data and docking request data, and the format conversion module 41 is used to:

[0090] The target docking data is formatted according to a first preset rule to obtain a target cloud identifier and a target functional module identifier, and the docking request data is formatted according to a second preset rule to obtain a target access key.

[0091] In a possible embodiment, the target docking data includes a cloud interface and a functional interface, and the format conversion module 41 is further used to:

[0092] Determine a first mapping interface format of the cloud interface and a second mapping interface format of the functional interface according to a first preset rule;

[0093] The cloud interface is format-converted according to the first mapping interface format to obtain a target cloud identifier, and the functional interface is format-converted according to the second mapping interface format to obtain a target functional module identifier.

[0094] In a possible embodiment, the format conversion module 41 is further used for:

[0095] Performing format conversion on each functional interface according to the second mapping interface format to obtain a target functional interface corresponding to each functional interface;

[0096] The target functional interfaces corresponding to the functional interfaces are combined to obtain a target functional module identifier.

[0097] In a possible embodiment, the cloud data docking device further includes a location orchestration module, and the location orchestration module is used to:

[0098] The target cloud identifier, the target functional module identifier and the target access key are arranged in position according to the command arrangement sequence in the preset interface rule to obtain a corresponding position tag.

[0099] The instantiation configuration module 42 is used to:

[0100] Automatic instantiation configuration is performed according to the location tag of the target cloud identifier and the location tag of the functional module identifier.

[0101] In a possible embodiment, the login verification module 43 is used to:

[0102] Perform attribute configuration and method configuration according to the target cloud identifier and the functional module identifier to generate a target constructor;

[0103] The target constructor is called through the target access key to perform cloud login verification.

[0104] In a possible embodiment, the cloud data docking device further includes a parameter acquisition module and a parameter replacement module, and the parameter acquisition module is used to:

[0105] Determine the validity of the first key certificate, and when the first key certificate is invalid, connect to a preset time interface, obtain a first time parameter through the preset time interface, and obtain a source code file of the target cloud according to the target cloud identifier;

[0106] The parameter substitution module is used to:

[0107] A second time parameter in the source code file is identified, the second time parameter is replaced with the first time parameter, and a second key credential is obtained.

[0108] The embodiment of the present application also provides a cloud data docking device, which can integrate a cloud data docking apparatus provided in the embodiment of the present application. Figure 5 Schematic diagram of a cloud data docking device provided in an embodiment of the present application. Figure 5 The cloud data docking device includes: an input device 53, an output device 54, a memory 52 and one or more processors 51; the memory 52 is used to store one or more programs; when one or more programs are executed by one or more processors 51, the one or more processors 51 implement the cloud data docking method provided in the above embodiment. The input device 53, the output device 54, the memory 52 and the processor 51 can be connected by a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0109] The memory 52, as a computing device readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the cloud data docking method provided in any embodiment of the present application. The memory 52 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, at least one application required for a function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 52 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 52 may further include a memory remotely arranged relative to the processor 51, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0110] The input device 53 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 54 may include a display device such as a display screen.

[0111] The processor 51 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 52, that is, realizes the above-mentioned cloud data docking method.

[0112] The cloud data docking device, equipment and computer provided above can be used to execute the cloud data docking method provided in any of the above embodiments, and have corresponding functions and beneficial effects.

[0113] The present application also provides a storage medium storing computer executable instructions. When the computer executable instructions are executed by a computer processor, they are used to execute the cloud data docking method provided in the above embodiment. The cloud data docking method includes:

[0114] In response to an input instruction of target configuration data, the target configuration data is formatted according to a preset interface rule to obtain a target cloud identifier, a target functional module identifier, and a target access key;

[0115] Performing instantiation configuration according to the target cloud identifier and the target functional module identifier, and performing cloud login verification according to the configuration result of the instantiation configuration and the target access key;

[0116] When the cloud login verification is successful, a first key credential is obtained, and based on the first key credential, the cloud corresponding to the target cloud identifier is accessed to achieve data docking.

[0117] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0118] Of course, the storage medium containing computer executable instructions provided in the embodiment of the present application, whose computer executable instructions are not limited to the cloud data docking method described above, can also execute related operations in the cloud data docking method provided in any embodiment of the present application.

[0119] The cloud-based data docking apparatus, device and storage medium provided in the above embodiments can execute the cloud-based data docking method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the cloud-based data docking method provided in any embodiment of the present application.

[0120] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. A cloud data docking method, characterized in that: include: In response to an input instruction of target configuration data, the target configuration data is formatted according to a preset interface rule to obtain a target cloud identifier, a target functional module identifier, and a target access key; Performing instantiation configuration according to the target cloud identifier and the target functional module identifier, and performing cloud login verification according to the configuration result of the instantiation configuration and the target access key; When the cloud login verification is successful, a first key credential is obtained, and based on the first key credential, the cloud corresponding to the target cloud identifier is accessed to achieve data docking.

2. The cloud data docking method according to claim 1, characterized in that: The target configuration data includes target docking data and docking request data, and the target configuration data is formatted according to a preset interface rule to obtain a target cloud identifier, a target function module identifier, and a target access key, including: The target docking data is formatted according to a first preset rule to obtain a target cloud identifier and a target functional module identifier, and the docking request data is formatted according to a second preset rule to obtain a target access key.

3. The cloud data docking method according to claim 2, characterized in that: The target docking data includes a cloud interface and a functional interface, and the target docking data is formatted according to a first preset rule to obtain a target cloud identifier and a target functional module identifier, including: Determine a first mapping interface format of the cloud interface and a second mapping interface format of the functional interface according to a first preset rule; The cloud interface is format-converted according to the first mapping interface format to obtain a target cloud identifier, and the functional interface is format-converted according to the second mapping interface format to obtain a target functional module identifier.

4. The cloud data docking method according to claim 3, characterized in that: The step of converting the format of the functional interface according to the second mapping interface format to obtain a target functional module identifier includes: Performing format conversion on each functional interface according to the second mapping interface format to obtain a target functional interface corresponding to each functional interface; The target functional interfaces corresponding to the functional interfaces are combined to obtain a target functional module identifier.

5. The cloud data docking method according to claim 1, characterized in that: After obtaining the target cloud identifier, the target function module identifier and the target access key, the method further includes: Arrange the target cloud identifier, the target functional module identifier, and the target access key according to the command arrangement sequence in the preset interface rule to obtain a corresponding location tag; Accordingly, the instantiation configuration according to the target cloud identifier and the functional module identifier includes: Automatic instantiation configuration is performed according to the location tag of the target cloud identifier and the location tag of the functional module identifier.

6. The cloud data docking method according to claim 1, characterized in that: The instantiation configuration is performed according to the target cloud identifier and the functional module identifier, and the cloud login verification is performed according to the configuration result of the instantiation configuration and the target access key, including: Perform attribute configuration and method configuration according to the target cloud identifier and the functional module identifier to generate a target constructor; The target constructor is called through the target access key to perform cloud login verification.

7. The cloud data connection method according to claim 1, characterized in that: After obtaining the first key certificate, the method further includes: Determine the validity of the first key certificate, and when the first key certificate is invalid, connect to a preset time interface, obtain a first time parameter through the preset time interface, and obtain a source code file of the target cloud according to the target cloud identifier; A second time parameter in the source code file is identified, the second time parameter is replaced with the first time parameter, and a second key credential is obtained.

8. A cloud data docking device, characterized in that: include: A format conversion module, configured to respond to an input instruction of target configuration data and convert the target configuration data into a format according to a preset interface rule to obtain a target cloud identifier, a target function module identifier, and a target access key; An instantiation configuration module, used to perform instantiation configuration according to the target cloud identifier and the functional module identifier; A login verification module, used to perform cloud login verification according to the configuration result of the instantiated configuration and the target access key; The data docking module is used to obtain a first key certificate when the cloud login verification is successful, and access the cloud corresponding to the target cloud identifier based on the first key certificate to achieve data docking.

9. A cloud data docking device, the device comprising: one or more processors; A storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the cloud data docking method as described in any one of claims 1-7.

10. A storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the cloud data docking method according to any one of claims 1 to 7 when executed by a computer processor.

Images