Docking method and device

Abstract

The invention provides a docking method and device, and the method comprises the steps: determining docking party information corresponding to an access party and a metadata model in a target service scene according to the information of the access party and a pre-configured scene information code; generating a target script file based on the access party information and a metadata model in a target service scene; and based on the target script file, performing docking between the access party and the docking party in a target service scene. According to the embodiment, through the target script file generated based on the access party information and the metadata model in the target service scene, the flexibility and reusability of the docking method can be improved when facing multiple docking parties, and then the docking efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a docking method and device. Background Art

[0002] With the development of information and Internet technology, the Internet has become an important channel for promotion in various fields. For example, in the field of e-commerce, by connecting with various supply and marketing channels, the supply and marketing channels and exposure of merchants' products can be increased. With the globalization of the market and the coordination of the dual-circulation economy, the connection with well-known foreign companies is also on the rise.

[0003] However, due to the differences between different docking parties and between different modules of the same docking party, the existing technology has a large workload and difficulty in achieving docking between the access party and multiple docking parties, and the docking method lacks reusability and flexibility, resulting in low docking efficiency. Summary of the invention

[0004] In view of this, the embodiments of the present disclosure at least provide a docking method, device, electronic device and storage medium, which can improve the flexibility and reusability of the docking method when facing multiple docking parties, thereby improving the docking efficiency.

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

[0006] Determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code;

[0007] Generate a target script file based on the access party information and the metadata model in the target service scenario;

[0008] Based on the target script file, the access party and the docking party are docked in a target service scenario.

[0009] In an optional implementation, determining a metadata model in a target service scenario includes:

[0010] Searching the first model library for a metadata model under the target service scenario;

[0011] In response to the absence of a metadata model for the target service scenario in the first model library, a metadata model for the target service scenario is created according to the access party information and the scenario information code, and the metadata model is stored in the second model library.

[0012] In an optional implementation, generating a target script file based on the access party information and a metadata model in a target service scenario includes:

[0013] Determine a value converter corresponding to the input data type based on the metadata model in the target service scenario and the access party information;

[0014] The value converter is used to generate a target script file in a format corresponding to the data type of the access party information.

[0015] In an optional implementation manner, after generating the target script file, the method further includes:

[0016] The target script file is saved in a script library, and a backup file of the target script file is generated; the backup file is used to implement the rollback of the target script file.

[0017] In an optional implementation manner, before completing the docking between the access party and the docking party in the target service scenario based on the target script file, the method further includes:

[0018] The target script file is verified; the verification includes at least one of logic verification and validity verification.

[0019] In an optional implementation manner, after the access party and the docking party are docked in the target service scenario, the method further includes:

[0020] An execution result of the target script file is received, and based on the execution result, it is verified whether the target script file is executed successfully.

[0021] In an optional implementation, the method is displayed via a visualization device.

[0022] In a second aspect, an embodiment of the present disclosure provides a docking device, including:

[0023] A model determination module, used to determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code;

[0024] A script generation module, used to generate a target script file based on the access party information and the metadata model in the target service scenario;

[0025] A docking module is used to perform docking between the access party and the docking party in a target service scenario based on the target script file.

[0026] In a third aspect, an embodiment of the present disclosure further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps in the above-mentioned first aspect, or any optional implementation of the first aspect are performed.

[0027] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned first aspect, or any optional implementation of the first aspect are executed.

[0028] Any one of the above aspects or any implementation method of any one of the aspects, by determining the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code; generating a target script file based on the access party information and the metadata model under the target service scenario; and docking the access party with the docking party under the target service scenario based on the target script file. In this way, the docking of the access party and the docking party can be achieved based on the automatically generated target script file. Since the target script file is generated based on the access party information and the metadata model under the target service scenario, different docking parties have different corresponding metadata models. Therefore, the flexibility and reusability of the docking method are improved through the flexible configuration of the target script file, thereby improving the docking efficiency.

[0029] In a further embodiment of the present disclosure, the general metadata model and the special metadata model can be classified and stored by setting the first model library and the second model library, thereby avoiding the problem of certain coupling between some specific functional interfaces and general interfaces in the docking party, further improving the reusability and flexibility of the docking method, and thus improving the docking efficiency. In addition, in a further embodiment of the present disclosure, it can also be realized through a visual display device, which can further improve the docking efficiency.

[0030] The effects of the above-mentioned docking device, electronic device and storage medium refer to the description of the above-mentioned docking method, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0032] Figure 1 A flow chart of a docking method provided by an embodiment of the present disclosure is shown;

[0033] Figure 2 A schematic diagram showing a target script file execution process in a docking method provided by an embodiment of the present disclosure;

[0034] Figure 3 A schematic diagram of a docking device provided by an embodiment of the present disclosure is shown;

[0035] Figure 4 An exemplary system architecture is shown in which embodiments of the present disclosure may be applied;

[0036] Figure 5 A schematic diagram of the structure of a computer system of a terminal device or a server used to implement an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0038] It should be noted that in the technical solution of the present invention, the collection, use, storage, sharing and transfer of user personal information involved are in compliance with the provisions of relevant laws and regulations, and it is necessary to inform the user and obtain the user's consent or authorization. When applicable, the user's personal information is de-identified and / or anonymized and / or encrypted.

[0039] Research has found that with the development of information and Internet technology, the Internet has become an important channel for promotion in various fields. For example, in the field of e-commerce, by connecting with various supply and marketing channels, the supply and marketing channels and exposure of merchants' products can be increased, and with the synergy of market globalization and the dual-circulation economy, the connection with well-known foreign companies is also on the rise.

[0040] However, due to the differences between different docking parties and between different modules of the same docking party, the existing technology has a large workload and difficulty in achieving docking between the access party and multiple docking parties, and the docking method lacks reusability and flexibility, resulting in low docking efficiency. In addition, due to the certain coupling between some specific functional interfaces and general interfaces in the docking party, when the general interface definition changes, it will affect the specific functional interface, resulting in reduced docking efficiency.

[0041] Based on the above research, the embodiment of the present disclosure provides a docking method, which can determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code; generate a target script file based on the access party information and the metadata model under the target service scenario; and perform docking between the access party and the docking party under the target service scenario based on the target script file. In this way, the docking of the access party and the docking party can be realized based on the automatically generated target script file. Since the target script file is generated based on the access party information and the metadata model under the target service scenario, the metadata model corresponding to different docking parties is different. Therefore, the flexibility of the docking method is improved through the flexible configuration of the target script file, thereby improving the docking efficiency. In addition, the general metadata model and the special metadata model can be classified and stored by setting the first model library and the second model library, avoiding the problem of certain coupling between some specific functional interfaces and general interfaces in the docking party, improving the reusability of the docking method, and thereby improving the docking efficiency. In addition, it can also be realized through a visual display device, which can further improve the docking efficiency.

[0042] The raising of the above problems and the solutions are the results obtained by the inventor after practice and careful research. The discovery process of the above problems and the solutions proposed for the above problems should be the contributions made by the inventor to the present disclosure during the disclosure process.

[0043] The technical solutions in the present disclosure will be clearly and completely described below in conjunction with the drawings in the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure claimed for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0044] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0045] To facilitate understanding of the present embodiment, a docking method disclosed in the embodiment of the present disclosure is first introduced in detail. The execution subject of the docking method provided in the embodiment of the present disclosure is generally a computer device with certain computing capabilities, and the computer device includes, for example: a terminal device or a server or other processing device, and the terminal device can be a user equipment (User Equipment, UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementations, the docking method can be implemented by a processor calling a computer-readable instruction stored in a memory.

[0046] See also Figure 1 As shown, it is a flow chart of the docking method provided by the embodiment of the present disclosure, and the method includes S101 to S103, wherein:

[0047] S101: Determine, according to access party information and a pre-configured scenario information code, docking party information corresponding to the access party and a metadata model in a target service scenario.

[0048] In the embodiment of the present disclosure, the access party information may include information used to record the access party system, such as the system name, system identifier, etc., and may also include the access party's input data in the target service scenario, the type of input data, and the docking party information that needs to be docked.

[0049] In the disclosed embodiment, the target service scene can be addressed through the scene information code. Specifically, the target service scene can be any function, service or scene in the docking party. Taking the e-commerce field as an example, the target service scene can be product release, price release, etc.

[0050] In the disclosed embodiment, the metadata model of the access party and multiple docking parties in each target service scenario can be pre-configured to generate the scenario information code in the corresponding target service scenario. When the access party needs to call the function of the docking party in the target service scenario, it only needs to pass in the scenario information code to find the corresponding service, function or scenario through the previously established mapping relationship.

[0051] In the embodiment of the present disclosure, the metadata model refers to the mapping relationship established between the data structures of the access party and the docking party, which may include data fields, data content, data types, and association relationships between data.

[0052] For example, in the e-commerce field, it is necessary to push the products of e-commerce website A (access party) to channel B (connection party) for sale. The product attributes and corresponding values ​​of e-commerce website A are: product ID "1234", product name "test product a", and the data types of product ID and product name are both string types, and the length of product name attribute is 20; while the product attributes of channel B are: wareid, name, and wareid is a numeric type, name is a string type and the length is 10. In order for e-commerce website A to push products to channel B for sale, the product data must meet the requirements of channel B, so it is necessary to convert the product ID of e-commerce website A into the data type required by name, and convert the product name into the length 10 required by name; the above-mentioned mapping relationship established between the data structure of the access party and the connection party is the metadata model in the embodiment of the present disclosure.

[0053] It should be noted that in addition to supporting the simple one-to-one metadata mapping mentioned above, the embodiments of the present disclosure can also indicate the mapping of complex business scenarios, that is, to achieve one-to-many or many-to-one attribute combinations for the target service scenarios. Exemplarily, the example of the e-commerce field is still to push the goods of e-commerce website A (access party) to channel B (connection party) for sale. According to domestic practice, the user's name is an attribute, while foreign names are divided into two attributes: last name and first name. Therefore, when transmitting data from e-commerce website A to channel B (input), the "name" needs to be split into: first name and lastname; conversely, when transmitting data from Amazon to e-commerce website A (output), the first name and last name need to be integrated into "name".

[0054] In one possible implementation, determining a metadata model under a target service scenario includes: searching a first model library for a metadata model under the target service scenario; in response to the metadata model under the target service scenario not existing in the first model library, creating a metadata model under the target service scenario based on the access party information and the scenario information code, and storing the metadata model in the second model library.

[0055] In a specific implementation, the first model library here can be a general model library, and each docking party can correspond to a general model library, which can include the general metadata model extracted by the docking party for different target service scenarios, and can also be a metadata model saved by relevant staff and can be shared with other staff. The second model library can be a custom model library, which can include metadata models customized for different target service scenarios in each docking party. After completing the setting of the custom metadata model, it can be saved in the custom model library for subsequent use.

[0056] S102: Generate a target script file based on the access party information and the metadata model in the target service scenario.

[0057] In this step, the format of the target script file is determined by the input data type in the access party information; illustratively, when the input data type is XML type, the format of the generated target script file is also XML.

[0058] In an embodiment of the present disclosure, a target script file is generated based on the access party information and a metadata model in a target service scenario, including: determining a value converter corresponding to the input data type based on the metadata model in the target service scenario and the access party information; and using the value converter to generate a target script file in a format corresponding to the data type of the access party information.

[0059] In a specific implementation, when the access party calls the corresponding function or service of the docking party in the target service scenario, it can first determine the call address of the corresponding service or function of the docking party, and then determine the data type of the access party's input data in combination with the metadata model in the target service scenario and the access party information, and find the value converter corresponding to the data type according to the data type; wherein the data type can be JSON, XML, Java, etc. After determining the corresponding value converter, the value converter can be used to obtain the value under the corresponding attribute according to the metadata model in the target service scenario and the access party information (for example, the product identification in the previous example is the attribute, and 1234 is the value under the attribute), and set it to the corresponding data model of the docking party through the mapping relationship of the metadata model. After completing all the relevant attributes of the access party's input data model and the values ​​under the corresponding attributes, the value converter can be used to generate a target script file in a format corresponding to the access party's input data type. The corresponding script file format can be JSON, XML, file, form, etc.

[0060] In the embodiment of the present disclosure, after the target script file is generated, it can also be saved in a script library and a corresponding backup file can be generated.

[0061] In a specific implementation, each time the target script file is updated and saved, a corresponding backup file will be automatically generated. The file name can be in the format of "script name + save time + self-increment data sequence number". When the access party calls the function or service of the docking party in the target service scenario next time, if the metadata model has changed at this time, a new script file can be generated to overwrite the current version of the script file. If the metadata model has not changed, the corresponding script file can be determined by the scene code information to directly call the target script file in the script library.

[0062] It should be noted that the generated backup file can be used to roll back to the previous target script file to ensure system stability when the new script file is abnormal or inapplicable. The abnormality or inapplicability here can be system abnormality, such as script execution failure, service call failure, etc.; it can also be business abnormality, such as script execution results do not meet business requirements, etc.

[0063] S103: Based on the target script file, the access party and the docking party are docked in a target service scenario.

[0064] In the embodiment of the present disclosure, the value converter can be divided into two parts, namely, an input value converter and an output value converter. Figure 2As shown, after the input value converter generates the target script file, it can be pre-processed. Specifically, the target script file can be logically verified, such as whether the sum of the two sides of a triangle is greater than the third side, and its validity can also be verified, such as whether the value under the data model attribute is empty, whether the data model value is legal, etc.

[0065] like Figure 2 As shown, after executing the remote call according to the target script file, before the execution data result is returned to the output value converter, the result data returned by the remote call can also be post-processed. Specifically, it can be verified whether the remote call is successful, whether the returned data format is complete, etc., so as to avoid erroneous data from entering the output value converter.

[0066] In the embodiment of the present disclosure, the above method can be displayed by a visual display device, and the user can complete the docking between the access party and the docking party by dragging or clicking the corresponding modules or files of the access party and the docking party in the target service scenario on the front-end device.

[0067] According to a second aspect of the embodiment of the present disclosure, Figure 3 As shown, a docking device 300 is provided, comprising:

[0068] The model determination module 301 is used to determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code;

[0069] A script generation module 302, configured to generate a target script file based on the access party information and a metadata model in a target service scenario;

[0070] The docking module 303 is used to perform docking between the access party and the docking party in a target service scenario based on the target script file.

[0071] Optionally, the model determination module 301 is specifically used for:

[0072] Searching the first model library for a metadata model under the target service scenario;

[0073] In response to the absence of a metadata model for the target service scenario in the first model library, a metadata model for the target service scenario is created according to the access party information and the scenario information code, and the metadata model is stored in the second model library.

[0074] Optionally, the script generation module 302 is specifically used for:

[0075] Determine a value converter corresponding to the input data type based on the metadata model in the target service scenario and the access party information;

[0076] The value converter is used to generate a target script file in a format corresponding to the data type of the access party information.

[0077] Optionally, the script generation module 302 is further used to:

[0078] The target script file is saved in a script library, and a backup file of the target script file is generated; the backup file is used to implement the rollback of the target script file.

[0079] Optionally, the docking module 303 is further used for:

[0080] The target script file is verified; the verification includes at least one of logic verification and validity verification.

[0081] Optionally, the docking module 303 is further used for:

[0082] An execution result of the target script file is received, and based on the execution result, it is verified whether the target script file is executed successfully.

[0083] Optionally, the method is displayed by a visualization device.

[0084] According to the third aspect of an embodiment of the present disclosure, a docked electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided by the first aspect of the embodiment of the present disclosure.

[0085] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method provided by the first aspect of the embodiment of the present disclosure is implemented.

[0086] Figure 4 An exemplary system architecture 400 to which the docking method or docking device implemented by the present disclosure can be applied is shown.

[0087] like Figure 4 As shown, system architecture 400 may include terminal devices 401, 402, 403, network 404 and server 405. Network 404 is used to provide a medium for communication links between terminal devices 401, 402, 403 and server 405. Network 404 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0088] Users can use terminal devices 401, 402, 403 to interact with server 405 through network 404 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 401, 402, 403, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0089] The terminal devices 401 , 402 , and 403 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0090] The server 405 may be a server that provides various services, such as a background management server (only as an example) that provides support for shopping websites browsed by users using the terminal devices 401, 402, and 403. The background management server may process the received connection request and feed back the processing result (only as an example) to the terminal device.

[0091] It should be noted that the docking method provided in the embodiment of the present invention is generally performed by the server 405, and accordingly, the docking device is generally set in the server 405. The docking method provided in the embodiment of the present invention can also be performed by the terminal devices 401, 402, 403, and accordingly, the docking device can be set in the terminal devices 401, 402, 403.

[0092] It should be understood that Figure 4 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0093] Reference below Figure 5 , which shows a schematic diagram of the structure of a computer system 500 of a terminal device suitable for implementing an embodiment of the present invention. Figure 5 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0094] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the system 500 are also stored. The CPU 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0095] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage section 508 as needed.

[0096] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processing unit (CPU) 501, the above-mentioned functions defined in the system of the present invention are executed.

[0097] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0098] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0099] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor. For example, a processor includes a model determination module, a script generation module, and a docking module. The names of these modules do not constitute a limitation on the modules themselves in some cases. For example, the model determination module may also be described as a "metadata model determination module."

[0100] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device implements the following method:

[0101] Determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code;

[0102] Generate a target script file based on the access party information and the metadata model in the target service scenario;

[0103] Based on the target script file, the access party and the docking party are docked in a target service scenario.

[0104] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be based on the protection scope of the claims.

Claims

1. A docking method, characterized in that: include: Determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code; Generate a target script file based on the access party information and the metadata model in the target service scenario; Based on the target script file, the access party and the docking party are docked in a target service scenario.

2. The method according to claim 1, characterized in that Determine the metadata model for the target service scenario, including: Searching the first model library for a metadata model under the target service scenario; In response to the absence of a metadata model for the target service scenario in the first model library, a metadata model for the target service scenario is created according to the access party information and the scenario information code, and the metadata model is stored in the second model library.

3. The method according to claim 1, characterized in that Based on the access party information and the metadata model in the target service scenario, a target script file is generated, including: Determine a value converter corresponding to the input data type based on the metadata model in the target service scenario and the access party information; The value converter is used to generate a target script file in a format corresponding to the data type of the access party information.

4. The method according to claim 1, characterized in that: After generating the target script file, it also includes: The target script file is saved in a script library, and a backup file of the target script file is generated; the backup file is used to implement the rollback of the target script file.

5. The method according to claim 1, characterized in that Before completing the docking between the access party and the docking party in the target service scenario based on the target script file, the method further includes: The target script file is verified; the verification includes at least one of logic verification and validity verification.

6. The method according to claim 1, characterized in that After the access party and the docking party are docked in the target service scenario, the method further includes: An execution result of the target script file is received, and based on the execution result, it is verified whether the target script file is executed successfully.

7. The method according to any one of claims 1 to 6, characterized in that: The method is displayed by means of a visualization device.

8. A docking device, characterized in that: include: A model determination module, used to determine the docking party information corresponding to the access party and the metadata model under the target service scenario according to the access party information and the pre-configured scenario information code; A script generation module, used to generate a target script file based on the access party information and the metadata model in the target service scenario; A docking module is used to perform docking between the access party and the docking party in a target service scenario based on the target script file.

9. An electronic device, characterized in that: include: 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 method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images