CN109947578B - System docking method and device - Google Patents
System docking method and device Download PDFInfo
- Publication number
- CN109947578B CN109947578B CN201910217420.8A CN201910217420A CN109947578B CN 109947578 B CN109947578 B CN 109947578B CN 201910217420 A CN201910217420 A CN 201910217420A CN 109947578 B CN109947578 B CN 109947578B
- Authority
- CN
- China
- Prior art keywords
- docking
- key function
- new
- configuration information
- function node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The application provides a system docking method and device, comprising the following steps: when the butt joint of a new system and a local system is detected, the system type and the system identification of the new system are obtained; searching whether a docking routing table item corresponding to the system type and the system identification exists in the recorded docking routing table; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node; if the key function node exists, docking is carried out with the key function node in the new system based on the docking configuration information recorded in the searched docking routing table item. The system docking method provided by the application can greatly improve the efficiency of system docking.
Description
Technical Field
The present application relates to computer communications, and in particular, to a system docking method and apparatus.
Background
With the explosion of the internet, more and more enterprises open the mode of offline collaboration and online information sharing. As a result, enterprise systems are being docked more and more frequently.
Existing enterprise system docking requires manual labor to dock. However, when the enterprise system needs to be docked with a large number of different other enterprise systems, the efficiency of system docking can be greatly reduced by adopting a manual docking mode, and the error rate of system docking is increased.
Disclosure of Invention
In view of the above, the present application provides a system docking method and apparatus for improving system docking efficiency.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, there is provided a system docking method, which is applied to an electronic device, the method including:
when the butt joint of a new system and a local system is detected, the system type and the system identification of the new system are obtained;
searching whether a docking routing table item corresponding to the system type and the system identification exists in the recorded docking routing table; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node;
if the key function node exists, docking is carried out with the key function node in the new system based on the docking configuration information recorded in the searched docking routing table item.
Optionally, the method further includes:
if not, searching a key function node corresponding to the acquired system type in a preset corresponding relation between the system type and the key function node;
acquiring docking configuration information aiming at the key function node;
and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
Optionally, the docking configuration information includes: and interface docking logic and data format conversion logic on the key function node.
Optionally, the system identifier includes: system vendor identification and system version identification.
Optionally, the local system is a supply chain logistics system; the new system may include: an Enterprise Resource Planning (ERP) system, an Order Management System (OMS) system, a Transportation Management System (TMS) system and a Warehouse Management System (WMS) system;
when the new system is an ERP system, the key function nodes corresponding to the ERP system comprise: order creation, order reception and order management;
when the new system is the TMS system, the key function nodes corresponding to the TMS system comprise: the method comprises the steps of (1) carrying a bill pushing function, calling back a bill message, synchronizing the state of the bill and tracking an order;
when the new system is a WMS system, the key function nodes corresponding to the WMS system comprise: a warehouse-in pushing function, a warehouse-out and warehouse-in message callback function and an order state synchronization function;
when the new system is an OMS system, the key function node corresponding to the OMS system comprises: order creation, order reception, and order status synchronization.
According to a second aspect of the present application, there is provided a system docking apparatus, which is applied to an electronic device, the apparatus including:
the acquisition unit is used for acquiring the system type and the system identification of the new system when the new system is detected to be in butt joint with the local system;
a searching unit, configured to search, in a recorded docking routing table, whether a docking routing table entry corresponding to the system type and the system identifier exists; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node;
and the docking unit is used for docking with the key function node in the new system based on the docking configuration information recorded in the searched docking routing table entry if the docking configuration information exists.
Optionally, the docking unit is further configured to search, if the key function node does not exist, the key function node corresponding to the acquired system type in a preset correspondence between the system type and the key function node; acquiring docking configuration information aiming at the key function node; and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
Optionally, the docking configuration information includes: and interface docking logic and data format conversion logic on the key function node.
Optionally, the system identifier includes: system vendor identification and system version identification.
Optionally, the local system is a supply chain logistics system; the new system may include: an Enterprise Resource Planning (ERP) system, an Order Management System (OMS) system, a Transportation Management System (TMS) system and a Warehouse Management System (WMS) system;
when the new system is an ERP system, the key function nodes corresponding to the ERP system comprise: order creation, order reception and order management;
when the new system is the TMS system, the key function nodes corresponding to the TMS system comprise: the method comprises the steps of (1) carrying a bill pushing function, calling back a bill message, synchronizing the state of the bill and tracking an order;
when the new system is a WMS system, the key function nodes corresponding to the WMS system comprise: a warehouse-in pushing function, a warehouse-out and warehouse-in message callback function and an order state synchronization function;
when the new system is an OMS system, the key function node corresponding to the OMS system comprises: order creation, order reception, and order status synchronization.
The configuration information of the key function node of a certain new system is required to be acquired only when the system is accessed for the first time, when other clients access the same system, the docking routing table entry corresponding to the system can be directly searched, and docking is carried out based on the configuration information of the key function node recorded by the docking routing table entry, so that the system docking efficiency can be greatly improved, and the error rate of system docking is reduced.
Drawings
FIG. 1 is a flow chart illustrating a method for system docking according to an exemplary embodiment of the present application;
FIG. 2 is a block diagram of a system docking device shown in an exemplary embodiment of the present application;
fig. 3 is a hardware block diagram of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
With the explosion of the internet, more and more enterprises open the mode of offline collaboration and online information sharing. Thus, existing enterprise systems do not merely interface with one other enterprise system, but rather require interfacing with a large number of different other enterprise systems.
For example, when the Enterprise System is a supply chain logistics System, the Enterprise System needs to interface with an upstream ERP (Enterprise Resource Planning) System, and needs to interface with a downstream OMS (Order Management System) System, a TMS (Transportation Management System) System, and a WMS (Warehouse Management System) System. Each type of system is divided into a plurality of different systems according to different system manufacturers and system versions. For example, an ERP system may include: an ERP system of version 1.0 produced by golden butterfly, an ERP system of version 2.0 produced by golden butterfly, and so on.
Therefore, the number of other enterprise systems that an enterprise needs to interface with is very large. If the enterprise system is in manual docking mode with each other enterprise system, the efficiency of system docking can be greatly reduced, and the error rate of system docking is improved.
The application aims to provide a system docking method, when detecting that a certain client is firstly accessed to a local system by a new system, electronic equipment can acquire configuration information of key function nodes of the new system, generate a docking routing table item and add the docking routing table item into the docking routing table.
When the electronic device detects that other clients access the system by the new system again, the electronic device can directly search the routing table to obtain the configuration information of the key function node corresponding to the new system, and then the configuration information of the key function node is used for docking with the new system.
The configuration information of the key function node of a certain new system is required to be acquired only when the system is accessed for the first time, when other clients access the same system, the docking routing table entry corresponding to the system can be directly searched, and docking is carried out based on the configuration information of the key function node recorded by the docking routing table entry, so that the system docking efficiency can be greatly improved, and the error rate of system docking is reduced.
Referring to fig. 1, fig. 1 is a flowchart illustrating a system docking method according to an exemplary embodiment of the present application, where the flowchart may be applied to an electronic device, and the method may include the following steps.
Step 101: and when the new system is detected to be in butt joint with the local system, acquiring the system type and the system identification of the new system.
In implementation, when the electronic device receives a new system access message, the electronic device may obtain a system type and a system identifier of the new system from the new system access message.
Among them, the system types may include: an ERP system, an SCM (Supply Chain Management system) system, an OMS system, a TMS system, a WMS system, etc. The system type is only exemplary and not particularly limited.
The local system may be an SCM system or other systems, and here, the local system is only exemplified and not specifically limited.
System identification to uniquely identify a system. The system identification may include: system vendor identification, system version identification, and the like.
For example, the system identifier may be composed of a system vendor identifier and a system version identifier, and for example, the system identifier of a system may be: Kingdee-V1.0. Wherein Kingdee represents the system manufacturer golden butterfly, and V1.0 represents the system version number.
Of course, the system identifier is only illustrated by way of example and is not particularly limited.
Step 102: the electronic equipment can search whether a docking routing table item corresponding to the system type and the system identification exists in a recorded docking routing table; the routing table entry records a system type, a system identifier and docking configuration information for the key function node.
Step 103: if the key function node exists, the electronic equipment can be in butt joint with the key function node in the new system based on the found butt joint configuration information recorded in the butt joint routing table entry.
Step 104: if not, the electronic equipment can search the key function node corresponding to the acquired system type in the corresponding relation between the preset system type and the key function node; acquiring docking configuration information aiming at the key function node; and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
In an embodiment of the present application, the docking routing table includes a plurality of docking routing table entries. Each pair of routing table entries records therein: system type, system identification, and configuration information for key function nodes.
The format of the pair of routing table entries is shown in table 1.
TABLE 1
Of course, in practical applications, table 1 may also include other information, which is only exemplary and not specifically limited herein.
The key function node refers to some functions that are specified in advance by a user among various functions of the system.
For example, when the system is an ERP system, the key function node corresponding to the ERP system may include: order creation, order reception, order management, and the like.
When the system is the TMS system, the key function nodes corresponding to the TMS system comprise: the waybill pushing function, the waybill message callback function, the waybill state synchronization function, the order tracking function and the like.
When the system is a WMS system, the key function nodes which are in butt joint with the WMS system comprise: the system comprises a warehouse entering pushing function, a warehouse entering and exiting message callback function, an order state synchronization function and the like.
When the system is an OMS system, the key function nodes which are in butt joint with the OMS system comprise: order creation, order reception, order status synchronization, and the like.
Here, the functions of the key nodes corresponding to the systems are only exemplarily described, and are not specifically limited.
The configuration information of the key function node is used for configuring with the key function node of the new system, and the configuration information of the key function node may include: the key function node comprises interface docking logic on the key function node, data format conversion logic on the key function node and the like. Here, the configuration information of the key functional node is merely exemplified and not particularly limited.
After introducing the basic concept, step 102 is described in detail below.
After the electronic device obtains the system type and the system identifier of the new system, the electronic device may use the system type and the system identifier of the new system as a keyword, and search, in the docking routing table, whether a docking routing table entry corresponding to the keyword exists.
If the docking routing table has a docking routing table entry corresponding to the keyword, docking with the key function node of the new system based on the configuration information of the key function node recorded in the docking routing table entry.
For example, when the electronic device is docked, the electronic device may use the interface docking logic recorded in the configuration information to dock with the interface on the key function node of the new system, and use the data format conversion logic recorded in the configuration information to perform data format conversion on the data input by the key function node of the new system, so as to be uniform with the data format of the system.
If the docking routing table item corresponding to the keyword does not exist in the docking routing table, it indicates that the new system is a system accessed for the first time. At this time, the electronic device may obtain configuration information of the key function node of the first access system, generate a docking routing entry corresponding to the new system, and dock the key function node of the new system based on the obtained configuration information of the key function node.
During implementation, the corresponding relationship between the system type and the key function node is recorded on the electronic device. When the electronic device determines that the docking routing table does not have the docking routing table entry corresponding to the keyword, the electronic device may search the key function node corresponding to the system type of the new system in the correspondence between the system type and the key function node.
The electronic device may then obtain docking configuration information for the key function node. When acquiring, the electronic device may acquire the docking configuration information of the key function node, which is input by the user, and the like. Here, the acquisition method is merely exemplary and is not particularly limited.
And then, the electronic equipment can be in butt joint with the joint function node of the access system by using the acquired configuration information of the key function node. Meanwhile, the electronic device may further generate an docking routing table entry corresponding to the new system based on the system type of the new system, the system identifier, and the configuration information of the key function node of the new system, and store the docking routing table entry in the docking routing table.
As can be seen from the above description, on one hand, when there is a docking routing entry corresponding to the system identifier and the system type of the new system, the electronic device may directly complete docking with the key function node of the new system based on the docking configuration information recorded in the routing entry, thereby implementing an automatic docking system of the electronic device. Because the mode of manual butt joint is not adopted any more, but the mode of an automatic butt joint system of the electronic equipment is adopted, the butt joint efficiency of the system can be greatly improved, and the error rate of the butt joint of the system is reduced.
On the other hand, when the docking routing table does not have a docking routing table entry corresponding to the system identifier and the system type of the new system, the electronic device may further obtain configuration information of the key node of the new system, generate a docking routing table entry for the new system and add the docking routing table entry to the docking routing table, so that the subsequent same system can be directly docked by looking up the docking routing table entry when accessing the system.
The system docking method provided by the present application is described in detail below by specific examples.
Assume that the docking routing table configured on the electronic device is shown in table 2.
TABLE 2
Example 1:
when the electronic device detects that the new system of the client 1 is docked with the native system, the electronic device may obtain the system type and system identification of the new system.
Suppose that the system type of the obtained new system is an ERP system, and the system identifier is Kingdee-V2.0.
The electronic device may use the ERP system and Kingdee-V2.0 as a key to search in table 2 whether a docking routing table entry corresponding to the key exists.
In this example, no docking routing entry corresponding to the new system for client 1 exists in Table 2.
The electronic device may search for a key function node corresponding to the new system of the client 1 in a preset correspondence between the system type and the key function node. For example, the key function nodes corresponding to the ERP system are: a function node 1 and a function node 2.
Then, the electronic device may acquire the docking configuration information 2 of the functional node 1, the docking configuration information 2 of the functional node 2.
The electronic device may dock with the functional node 1 and the functional node 2 in the new system of the client 1 based on the obtained docking configuration information. In addition, the electronic device may further generate a docking routing table entry for the new system of the client 1 based on the system type (i.e., ERP system) of the new system of the client 1, the system identifier (i.e., kingde-V2.0), and the docking configuration information 2 of the functional node 1 and the docking configuration information 2 of the functional node 2, and the generated docking routing table entry is as shown in the third row of table 3.
TABLE 3
Example 2:
when the electronic device detects that the new system of the client 2 is docked with the native system, the electronic device may obtain the system type and system identification of the new system of the client 2.
Suppose that the system type of the obtained new system is an ERP system, and the system identifier is Kingdee-V2.0.
The electronic device may use the ERP system and Kingdee-V2.0 as a key to search in table 2 whether a docking routing table entry corresponding to the key exists.
In this example, there is an docking routing entry in Table 2 that corresponds to the new system for this client 1 (i.e., the third row of docking routing entries in Table 3). The electronic device may obtain configuration information of the key function node (i.e., configuration information 2 of the function node 1 and configuration information 2 of the function node 2) recorded in the third row of the docking routing table entry in table 3, and dock with the function node 1 and the function node 2 of the new system based on the obtained configuration information 2 of the function node 1 and the obtained configuration information 2 of the function node 2.
Referring to fig. 2, fig. 2 is a block diagram of a system docking apparatus according to an exemplary embodiment of the present application. The apparatus may comprise the following elements.
An obtaining unit 201, configured to obtain a system type and a system identifier of a new system when it is detected that the new system is docked with a local system;
a searching unit 202, configured to search, in the recorded docking routing table, whether a docking routing table entry corresponding to the system type and the system identifier exists; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node;
and the docking unit 203 is configured to dock, if the key function node exists, the key function node in the new system with the docking configuration information recorded in the found docking routing table entry.
Optionally, the docking unit 203 is further configured to search, if the key function node does not exist, the key function node corresponding to the acquired system type in a preset correspondence between the system type and the key function node; acquiring docking configuration information aiming at the key function node; and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
Optionally, the docking configuration information includes: and interface docking logic and data format conversion logic on the key function node.
Optionally, the system identifier includes: system vendor identification and system version identification.
Optionally, the local system is a supply chain logistics system; the new system may include: an Enterprise Resource Planning (ERP) system, an Order Management System (OMS) system, a Transportation Management System (TMS) system and a Warehouse Management System (WMS) system;
when the new system is an ERP system, the key function nodes corresponding to the ERP system comprise: order creation, order reception and order management;
when the new system is the TMS system, the key function nodes corresponding to the TMS system comprise: the method comprises the steps of (1) carrying a bill pushing function, calling back a bill message, synchronizing the state of the bill and tracking an order;
when the new system is a WMS system, the key function nodes corresponding to the WMS system comprise: a warehouse-in pushing function, a warehouse-out and warehouse-in message callback function and an order state synchronization function;
when the new system is an OMS system, the key function node corresponding to the OMS system comprises: order creation, order reception, and order status synchronization.
Correspondingly, the application also provides a hardware structure diagram of the electronic equipment.
Referring to fig. 3, fig. 3 is a hardware structure diagram of an electronic device according to an exemplary embodiment of the present application.
The electronic device includes: a communication interface 301, a processor 302, a machine-readable storage medium 303, and a bus 304; wherein the communication interface 301, the processor 302, and the machine-readable storage medium 303 communicate with each other via a bus 304. The processor 302 may perform the system docking method described above by reading and executing machine-executable instructions in the machine-readable storage medium 303 corresponding to the system docking control logic.
The machine-readable storage medium 303 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 303 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (8)
1. A system docking method, applied to an electronic device, comprising:
when the butt joint of a new system and a local system is detected, the system type and the system identification of the new system are obtained; the new system and the native system are software systems;
searching whether a docking routing table item corresponding to the system type and the system identification exists in the recorded docking routing table; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node;
if yes, docking the key function node in the new system based on the docking configuration information recorded in the searched docking routing table item;
the docking configuration information includes: interface docking logic and/or data format conversion logic on the key function node;
the docking configuration information recorded in the docking routing table entry based on the finding is docked with the key function node in the new system, and the docking configuration information comprises:
and performing data format conversion on data input by the key function node of the new system by adopting interface docking logic in the recorded docking configuration information and using data format conversion logic in the recorded docking configuration information so as to unify the data format of the local system.
2. The method of claim 1, further comprising:
if not, searching a key function node corresponding to the acquired system type in a preset corresponding relation between the system type and the key function node;
acquiring docking configuration information aiming at the key function node;
and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
3. The method of claim 1, wherein the system identification comprises: system vendor identification and system version identification.
4. The method of claim 1, wherein the local system is a supply chain logistics system; the new system includes one or more of:
an Enterprise Resource Planning (ERP) system, an Order Management System (OMS) system, a Transportation Management System (TMS) system and a Warehouse Management System (WMS) system;
when the new system is an ERP system, the key function nodes corresponding to the ERP system comprise: order creation, order reception and order management;
when the new system is the TMS system, the key function nodes corresponding to the TMS system comprise: the method comprises the steps of (1) carrying a bill pushing function, calling back a bill message, synchronizing the state of the bill and tracking an order;
when the new system is a WMS system, the key function nodes corresponding to the WMS system comprise: a warehouse-in pushing function, a warehouse-out and warehouse-in message callback function and an order state synchronization function;
when the new system is an OMS system, the key function node corresponding to the OMS system comprises: order creation, order reception, and order status synchronization.
5. A system docking apparatus, applied to an electronic device, the apparatus comprising:
the acquisition unit is used for acquiring the system type and the system identification of the new system when the new system is detected to be in butt joint with the local system; the new system and the native system are software systems;
a searching unit, configured to search, in a recorded docking routing table, whether a docking routing table entry corresponding to the system type and the system identifier exists; the routing table entry records a system type, a system identifier and docking configuration information aiming at the key function node;
the docking unit is used for docking the key function node in the new system based on the docking configuration information recorded in the searched docking routing table item if the key function node exists;
the docking configuration information includes: interface docking logic and/or data format conversion logic on the key function node;
the search unit is configured to perform data format conversion on data input by the key function node of the new system by using interface docking logic in the recorded docking configuration information and using data format conversion logic in the recorded docking configuration information when docking configuration information recorded in the searched docking routing table entry is docked with the key function node of the new system, so as to be unified with the data format of the local system.
6. The apparatus according to claim 5, wherein the docking unit is further configured to, if the key function node does not exist, search for a key function node corresponding to the acquired system type in a preset correspondence between the system type and the key function node; acquiring docking configuration information aiming at the key function node; and generating a new docking routing table item based on the acquired docking configuration information, the system type of the new system and the system identification, adding the new docking routing table item into the docking routing table, and docking the key function node of the new system by adopting the acquired docking configuration information of the key function node.
7. The apparatus of claim 5, wherein the system identification comprises: system vendor identification and system version identification.
8. The apparatus of claim 5, wherein the local system is a supply chain logistics system; the new system includes one or more of:
an Enterprise Resource Planning (ERP) system, an Order Management System (OMS) system, a Transportation Management System (TMS) system and a Warehouse Management System (WMS) system;
when the new system is an ERP system, the key function nodes corresponding to the ERP system comprise: order creation, order reception and order management;
when the new system is the TMS system, the key function nodes corresponding to the TMS system comprise: the method comprises the steps of (1) carrying a bill pushing function, calling back a bill message, synchronizing the state of the bill and tracking an order;
when the new system is a WMS system, the key function nodes corresponding to the WMS system comprise: a warehouse-in pushing function, a warehouse-out and warehouse-in message callback function and an order state synchronization function;
when the new system is an OMS system, the key function node corresponding to the OMS system comprises: order creation, order reception, and order status synchronization.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910217420.8A CN109947578B (en) | 2019-03-21 | 2019-03-21 | System docking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910217420.8A CN109947578B (en) | 2019-03-21 | 2019-03-21 | System docking method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109947578A CN109947578A (en) | 2019-06-28 |
| CN109947578B true CN109947578B (en) | 2021-06-29 |
Family
ID=67010501
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910217420.8A Active CN109947578B (en) | 2019-03-21 | 2019-03-21 | System docking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109947578B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110942285A (en) * | 2019-11-22 | 2020-03-31 | 深圳前海微众银行股份有限公司 | System access method, device, service system and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634829A (en) * | 2016-03-08 | 2016-06-01 | 浙江安正科技股份有限公司 | Network device management method |
| CN107171922A (en) * | 2017-07-03 | 2017-09-15 | 中国人民解放军63893部队 | Heterogeneous system bridge service method based on middleware Technology |
| CN108270855A (en) * | 2018-01-15 | 2018-07-10 | 司中明 | A kind of method of platform of internet of things access device |
| CN108664344A (en) * | 2018-05-14 | 2018-10-16 | 浪潮通用软件有限公司 | A kind of adaption system and method for supporting more electric business platform docking |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103746812B (en) * | 2013-12-30 | 2017-06-16 | 迈普通信技术股份有限公司 | A kind of access authentication method and system |
| CN103870274A (en) * | 2014-03-14 | 2014-06-18 | 浪潮集团山东通用软件有限公司 | Visual development assembly for realizing data interaction between heterogeneous systems based on web service technology |
| US9857265B2 (en) * | 2015-04-03 | 2018-01-02 | Richard Andrew DeVerse | Methods and systems for detecting fluidic levels and flow rate and fluidic equipment malfunctions |
| CN107302762B (en) * | 2016-04-14 | 2019-11-19 | 大唐移动通信设备有限公司 | A kind of business access and its control method, device |
| CN106326352A (en) * | 2016-08-08 | 2017-01-11 | 歌尔股份有限公司 | Universal interface design method and system in butt joint with plurality of service systems |
| CN108052380B (en) * | 2017-12-07 | 2020-10-30 | 金蝶软件（中国）有限公司 | Business function docking method and device, computer equipment and storage medium |
-
2019
- 2019-03-21 CN CN201910217420.8A patent/CN109947578B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634829A (en) * | 2016-03-08 | 2016-06-01 | 浙江安正科技股份有限公司 | Network device management method |
| CN107171922A (en) * | 2017-07-03 | 2017-09-15 | 中国人民解放军63893部队 | Heterogeneous system bridge service method based on middleware Technology |
| CN108270855A (en) * | 2018-01-15 | 2018-07-10 | 司中明 | A kind of method of platform of internet of things access device |
| CN108664344A (en) * | 2018-05-14 | 2018-10-16 | 浪潮通用软件有限公司 | A kind of adaption system and method for supporting more electric business platform docking |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109947578A (en) | 2019-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100592748C (en) | Method and system for processing object | |
| CN101061475B (en) | Maintaining time-date information for syncing low fidelity devices | |
| US11023251B2 (en) | Efficient sharing of artifacts between collaboration applications | |
| US11487745B2 (en) | Workflow dependency management system | |
| US20090259455A1 (en) | Method and system for automatic tracking of a computerized process using a relationship model | |
| CN103118140B (en) | By sharing files to the method, system and device of relation loop other user terminals outer | |
| CN102932415A (en) | Method and device for storing mirror image document | |
| WO2010045331A2 (en) | Method and apparatus for gathering and organizing information pertaining to an entity | |
| CN109783076A (en) | Code administration method, apparatus, equipment and storage medium based on git | |
| CN103379129A (en) | Data synchronization method, servers and distributed system | |
| CN101620609A (en) | Multi-tenant data storage and access method and device | |
| CN101568919A (en) | Single view of data in a networked computer system with distributed storage | |
| US8924336B2 (en) | Feature and deployment recommendation systems and methods for content management systems to provide recommendations for enhanced feature usage based on usage patterns | |
| CN107911249A (en) | Order line sending method, device and the equipment of a kind of network equipment | |
| CN106547646B (en) | Data backup and recovery method and data backup and recovery device | |
| US11314550B2 (en) | User specific event threading | |
| CN109857377B (en) | API (application program interface) arrangement method and device | |
| US20180203869A1 (en) | Application Programming Interface | |
| CN103942209A (en) | Data processing method | |
| CN109947578B (en) | System docking method and device | |
| CN102325078A (en) | Application identification method and device | |
| CN109829678B (en) | Rollback processing method and device and electronic equipment | |
| CN111858355B (en) | Test case processing method and device, computer equipment and readable storage medium | |
| CN112328575A (en) | Data asset blood margin generation method and device and electronic equipment | |
| CN112785248A (en) | Human resource data cross-organization interaction method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |