Data interaction method and related equipment

Abstract

The embodiment of the present application discloses a data interaction method and related equipment, which are used to obtain object information from a server once and display it in different interfaces to reduce the load pressure of the client and the server. The method of the embodiment of the present application includes: responding to a viewing instruction input based on the object information interface, obtaining the object identification collected by the third-party device; wherein the object information interface includes an information display area and multiple tabs, and each tab has a pre-set interface type; sending the object identification to the server through an application programming interface api, and receiving the object information corresponding to the object identification returned by the server; determining the target tab in the selected state among the multiple tabs of the object information interface; and displaying the object information in the information display area according to the target interface type corresponding to the target tab.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular, to a data interaction method and related equipment. Background Art

[0002] With the popularization of digitalization, more and more industries are trying to store important data on servers. In this way, users do not need to build data centers by themselves, nor do they need to spend energy on IT management that is not related to their main business. They only need to issue instructions to the server to get the corresponding data.

[0003] In the solutions provided by the related art, the client usually initiates a request to the server based on the browser page to request the data to be displayed on the browser page. However, if there are multiple browser pages, each browser page needs to obtain the corresponding data from the server separately, which puts a large load pressure on the client and the server. Summary of the invention

[0004] The embodiments of the present application provide a data interaction method and related devices for obtaining object information from a server at one time and displaying it on different interfaces to reduce the load pressure on the client and the server.

[0005] A first aspect of an embodiment of the present application provides a data interaction method, wherein the client establishes communication connections with a third-party device and a server respectively, including:

[0006] In response to a viewing instruction input based on an object information interface, obtaining an object identifier collected by the third-party device; wherein the object information interface includes an information display area and a plurality of tabs, and each tab has a preset interface type;

[0007] Sending the object identifier to the server through an application programming interface (API), and receiving object information corresponding to the object identifier returned by the server;

[0008] Determine a target tab in a selected state among multiple tabs of the object information interface;

[0009] The object information is displayed in the information display area according to the target interface type corresponding to the target tab.

[0010] In a specific implementation, displaying the object information in the information display area according to the target interface type corresponding to the target tab includes:

[0011] Generate an information sub-interface corresponding to the target interface type, and fill the object information into the information sub-interface according to the target interface type;

[0012] In the information display area, the information sub-interface is displayed.

[0013] In a specific implementation, filling the object information into the information sub-interface according to the target interface type includes:

[0014] If the information sub-interface is a predefined cloud interface, sending the object information to the browser process;

[0015] Monitor the browser process through the custom control in the cloud interface to obtain object information;

[0016] Binding the obtained object information to the custom control;

[0017] The information sub-interface is displayed in the information display area, including:

[0018] The cloud interface is displayed in the information display area, wherein the custom control displays the obtained object information in the cloud interface.

[0019] In a specific implementation, filling the object information into the information sub-interface according to the target interface type includes:

[0020] If the information sub-interface is a local interface, the attribute type of the object information is set to a dependent attribute;

[0021] The object information set as the dependency property is filled into the local interface.

[0022] In a specific implementation, displaying the object information in the information display area according to the target interface type corresponding to the target tab includes:

[0023] Determine the object information corresponding to the target tab from the object information;

[0024] According to the target interface type corresponding to the target tab, the object information corresponding to the target tab is displayed in the information display area.

[0025] In a specific implementation, the method further includes:

[0026] If the interface type of the information sub-interface displayed in the information display area is the first interface, and newly added object information related to the object identifier is detected in the information sub-interface through the custom control of the information sub-interface, the newly added object information is obtained through the browser process;

[0027] Fill the newly added object information into the information sub-interface whose interface type is the second interface;

[0028] In the information display area, an information sub-interface whose interface type is a second interface is displayed; wherein, the first interface is a cloud interface or a local interface, the second interface is a cloud interface or a local interface, and the first interface and the second interface are different interface types.

[0029] In a specific implementation, the method further includes:

[0030] The newly added object information is sent to the server through the API or the custom control for storage.

[0031] A second aspect of an embodiment of the present application provides a data interaction device, including:

[0032] An acquisition unit, configured to respond to a viewing instruction input based on an object information interface and acquire the object identifier collected by the third-party device; wherein the object information interface includes an information display area and a plurality of tabs, and each tab has a preset interface type;

[0033] A sending unit, configured to send the object identifier to the server via an application programming interface (API), and receive object information corresponding to the object identifier returned by the server;

[0034] A determination unit, used to determine a target tab in a selected state among a plurality of tabs in the object information interface;

[0035] A display unit is used to display the object information in the information display area according to the target interface type corresponding to the target tab.

[0036] In a specific implementation, the display unit is specifically used to generate an information sub-interface corresponding to the target interface type, and fill the object information into the information sub-interface according to the target interface type;

[0037] In the information display area, the information sub-interface is displayed.

[0038] In a specific implementation, the display unit is specifically used to send the object information to the browser process if the information sub-interface is a predefined cloud interface;

[0039] Monitor the browser process through the custom control in the cloud interface to obtain object information;

[0040] Binding the obtained object information to the custom control;

[0041] The information sub-interface is displayed in the information display area, including:

[0042] The cloud interface is displayed in the information display area, wherein the custom control displays the obtained object information in the cloud interface.

[0043] In a specific implementation, the display unit is specifically configured to, if the information sub-interface is a local interface, set the attribute type of the object information to a dependent attribute;

[0044] The object information set as the dependency property is filled into the local interface.

[0045] In a specific implementation, the display unit is specifically used to determine the object information corresponding to the target tab from the object information;

[0046] According to the target interface type corresponding to the target tab, the object information corresponding to the target tab is displayed in the information display area.

[0047] In a specific implementation, the acquisition unit is further used to, if the interface type of the information sub-interface displayed in the information display area is the first interface, and the information sub-interface is monitored through the custom control of the information sub-interface to have newly added object information related to the object identifier, then obtain the newly added object information through the browser process;

[0048] The device further comprises: a new adding unit,

[0049] The adding unit is used to fill the newly added object information into the information sub-interface whose interface type is the second interface;

[0050] The display unit is also used to display, in the information display area, an information sub-interface whose interface type is a second interface; wherein the first interface is a cloud interface or a local interface, the second interface is a cloud interface or a local interface, and the first interface and the second interface are different interface types.

[0051] In a specific implementation, the sending unit is further used to send the newly added object information to the server for storage through the API or the custom control.

[0052] A third aspect of an embodiment of the present application provides a data interaction device, including:

[0053] CPU, memory and input / output interface;

[0054] The memory is a short-term storage memory or a persistent storage memory;

[0055] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect.

[0056] A fourth aspect of the embodiments of the present application provides a computer program product comprising instructions, and when the computer program product is run on a computer, the computer is caused to execute the method described in the first aspect.

[0057] A fourth aspect of an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the method described in the first aspect.

[0058] From the above technical solution, it can be seen that the embodiment of the present application has the following advantages: unlike the prior art that requires data to be requested from the server for different browser pages, the embodiment of the present application can display the object information obtained from the server in the information display area according to the target interface type corresponding to the target tab. There is no need to obtain data from the server for each interface, thereby effectively reducing the load pressure on the client and the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] Figure 1 A system architecture diagram of the data interaction method disclosed in the embodiment of the present application;

[0060] Figure 2 A flow chart of a data interaction method disclosed in an embodiment of the present application;

[0061] Figure 3 An example diagram of the object information interface disclosed in the embodiment of the present application;

[0062] Figure 4 A schematic diagram of the structure of the data interaction device disclosed in the embodiment of the present application;

[0063] Figure 5 This is another structural schematic diagram of the data interaction device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0065] The embodiments of the present application provide a data interaction method and related devices, which can improve the effectiveness of data interaction between a client and a server and reduce the load pressure on the client and the server. At the same time, data display is not limited to the browser, which can improve the diversity of data display and enhance the viewing experience of the client user.

[0066] The application scenario of the embodiment of the present application may include a client, a third-party device and a server, wherein the client is used to request an object identifier from a third-party device and to request object information from a server, the third-party device is used to collect object identifiers, and the server is used to maintain the object information corresponding to each object identifier. Among them, the specific form of the client, the third-party device and the server is not limited, depending on the specific situation. For example, the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server (such as a cloud server provided by a cloud platform) that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The client can run on a terminal, and the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, an intelligent speaker, a smart watch, etc., but is not limited thereto. The terminal and the server can be directly or indirectly connected by wired or wireless communication, which is not limited in the embodiment of the present application.

[0067] In some embodiments, the client is a Windows Presentation Foundation (WPF) client program based on .Net 5. Third-party devices can directly interact with the client through the software development kit SDK or dynamic link library DLL released by the third-party device manufacturer, and the client and the server can interact with each other through the API or custom controls of the cloud platform.

[0068] Specifically, the client main framework uses the characteristics of software design components such as Autofac and MVVM, taking full account of decoupling; the graphical interface is compatible with at least one of WPF, Winform and HTML5. At the same time, the interface developed by the cloud low code is displayed through CefSharp. Specifically, the local interface in the embodiment of the present application is implemented through WPF or Winform, and the cloud interface is implemented through an embedded browser kernel, which is not limited here.

[0069] In addition, in the embodiment of the present application, a CefSharp browser based on the webkit kernel is embedded in the client to mount the cloud service website. The client can access the JS engine thread in the browser through the browser. The browser can only have one JS engine thread running the JS program at the same time, and JS is single-threaded. Therefore, in the embodiment of the present application, the embedded browser of the client and the JS program used by the custom control of the cloud service belong to the same one, and the data interaction between the two parties is to interact through JS as a bridge.

[0070] Among them, the cloud platform is a website mounted in the browser. The Java plug-in is a Java code written under the rules of the cloud platform, registered in the server, and provides data and interface operation functions for the web pages in the cloud service website. The custom control is a front-end UI visualization component built under the rules of the cloud platform. By default, it integrates jquery and built-in JS scripts, and supports front-end frameworks such as React and Vue. The KDApi.register method in the custom control registers the control to the platform at runtime, and loads JS and CSS through the KDApi.loadFile method, and generates an HTML string through the KDApi.getHTMLStringBytemplate method, which can be assigned to innerHTML and provide a DOM node for setting innerHTML, thereby achieving the function of rendering web page components or web page DOM operations. The custom control sends the custom control event to the platform backend through the instruction function (invoke), and receives two parameters, eventName execution event name, eventArgs execution event required parameters, and the parameter format can be a string. The Java plug-in listens to the request issued by the custom control Invoke through the customEvent event. The Java plug-in sets the business data required by the custom control through the setData method.

[0071] The system architecture of the data interaction method in the embodiment of the present application is as follows Figure 1 As shown, the entire data interaction method includes a server, a third-party device and a client, wherein the client is respectively connected to the third-party device and the server to provide data interaction between the third-party device and the server, and at the same time, displays data obtained from the third-party device or the server to the object.

[0072] Specifically, third-party devices can directly interact with the client, while the client and the server can interact with each other through APIs or custom controls on the cloud platform.

[0073] See also Figure 2 Based on the above system architecture, a data interaction method according to an embodiment of the present application is described below, including:

[0074] 201. Responding to a viewing instruction input based on an object information interface, obtaining an object identifier collected by a third-party device; wherein the object information interface includes an information display area and multiple tabs, and each tab has a preset interface type.

[0075] When the user needs to view the object information of any object, he will enter the object information interface of the client and wait. At this time, the object information interface has not yet displayed the object information. When the third-party device collects the object ID of the object and sends it to the client, the client can obtain the object information of the object from the server based on the object ID. Among them, the object information interface includes an information display area and multiple tabs. Each tab has a pre-set interface type. The user can browse different object information of the object by selecting different tabs.

[0076] Specifically, the interface types include local interface, cloud interface and third-party web interface. Among them, the local interface is implemented through WPF or Winform, and is mainly used to display object identifiers obtained from third-party devices or information that is not displayed in the cloud interface; the cloud interface is implemented through an embedded browser kernel, and is mainly used to display object information obtained from the server; the third-party web page is implemented through an embedded browser kernel, and is mainly used to display relevant information obtained from the third-party web page on the client.

[0077] In a specific embodiment, the object identifier collected by the third-party device is determined by a software development kit SDK or a dynamic link library DLL released by the third-party device manufacturer.

[0078] 202. Send an object identifier to a server via an application programming interface (API), and receive object information corresponding to the object identifier returned by the server.

[0079] When the client obtains the object identifier collected from the third-party device, in order to obtain all the object information of the object referred to by the object identifier, the client will send an object information acquisition request to the server through the API according to the object identifier, and then receive all the object information of the object referred to by the object identifier returned by the server. Specifically, the client can send the request through an Http request.

[0080] In a specific embodiment, the object information may also be obtained through an API and a Java plug-in, and the method of obtaining the object information from the server is not limited here.

[0081] 203. Determine a target tab in a selected state among multiple tabs in the object information interface.

[0082] After obtaining the object information from the server, the client first determines that the tab selected by the user in the object information interface is the target tab, so as to display the object information according to the interface type of the target tab.

[0083] 204. According to the target interface type corresponding to the target tab, the object information is displayed in the information display area.

[0084] After the target tab is determined, the interface type of the target tab is determined to be the target interface type, and part of the object information that needs to be displayed on the target tab is displayed in the information display area according to the target interface type.

[0085] In a specific embodiment, a corresponding information sub-interface can be generated according to the target interface type, and the information sub-interface does not include any object information at this time. Then, at least part of the object information is filled into the information sub-interface according to the target interface type and the object information that needs to be displayed on the target tab. Finally, the information sub-interface is displayed in the information display area. Among them, different tabs can correspond to different contents in the object information, and the corresponding relationship can be determined according to the actual application scenario.

[0086] In the embodiment of the present application, unlike the prior art where different data display pages need to obtain object information from the server respectively, the embodiment of the present application can display the object information obtained from the server in the information display area according to the target interface type corresponding to the target tab. It is not necessary to obtain data from the server for each interface separately, which reduces the server load pressure.

[0087] In a specific embodiment, based on the aforementioned steps 201 to 204, the data interaction method of the embodiment of the present application also includes the following steps: if the interface type of the information sub-interface displayed in the information display area is a first interface, and the custom control of the information sub-interface is used to monitor that new object information related to the object identifier is added to the information sub-interface, then the newly added object information is obtained through the browser process; the newly added object information is filled into the information sub-interface whose interface type is a second interface; in the information display area, the information sub-interface whose interface type is the second interface is displayed; wherein the first interface is a cloud interface or a local interface, the second interface is a cloud interface or a local interface, and the first interface and the second interface are different interface types; the newly added object information is sent to the server for storage through an API or a custom control.

[0088] Specifically, if the user adds object information to the information display area and the interface type of the information sub-interface displayed in the information display area is a cloud interface, the custom control that implements the cloud interface display can monitor the newly added object information related to the object identifier in the information sub-interface and obtain the newly added object information through the JS process of the embedded browser. When the newly added object information contains information that needs to be displayed on a tab with a local interface type, the custom control will send the newly added object information that needs to be displayed on the tab with a local interface type to the client in a format that can be used by the local interface. Fill the acquired newly added object information into the information sub-interface with a local interface type, and then display the information sub-interface in the information display area.

[0089] It can be known that users can also add object information in the local interface, and then transmit it to the JS process of the embedded browser, so that the custom control can detect it and send it to the client in a format that can be used by the cloud interface. Finally, fill in the information sub-interface with the interface type of cloud and display it through the information display area, which is similar to the aforementioned display of the object information added by the user through the cloud interface in the local interface, and will not be repeated here.

[0090] In actual applications, users can also delete object information in one interface and synchronize it to other interfaces for display. The steps are similar to the steps for adding new object information mentioned above, so they will not be repeated here, and there are no restrictions on the types of modifications that users can make to object information.

[0091] In addition, in a specific embodiment, the aforementioned step 204 is specifically implemented in the following two ways: if the information sub-interface is a pre-defined cloud interface, the object information is sent to the browser process; the browser process is monitored through the custom control in the cloud interface to obtain the object information corresponding to the custom control; the object information corresponding to the custom control is bound to the custom control; if the information sub-interface is a local interface, the attribute type of the object information is set to a dependent attribute; and the object information set as a dependent attribute is filled into the information sub-interface.

[0092] Specifically, if the target interface type of the target tab selected by the user is a cloud interface, the object information is sent to the JS process of the embedded browser, the custom control monitors and obtains the object information in the JS process of the embedded browser, and then binds the object information to be displayed in the target tab to the custom control in a format that can be used by the cloud interface, so that the custom control fills the information to be displayed into the information sub-interface.

[0093] If the target interface type of the target tab selected by the user is the local interface, the attribute type of the object information to be displayed on the target tab is set to the dependent attribute, and then the object information set as the dependent attribute is filled into the information sub-interface, and the information sub-interface is displayed in the information display area.

[0094] In the embodiments of the present application, multiple implementation methods of displaying object information in the information display area according to the target interface type corresponding to the target tab are provided, thereby improving the feasibility of the solution.

[0095] The above method describes multiple embodiments of the data interaction method of the present application, please refer to Figure 3 The data interaction method of the embodiment of the present application is described below in conjunction with a specific scenario:

[0096] Figure 3The figure shows a scenario in which a hospital uses the data interaction method in an embodiment of the present application. The area displayed in the entire figure is the object information interface, wherein the dotted box 301 is the patient information in the header; the solid-line box 302 is different tabs that can be switched at will, wherein there are multiple types of interfaces corresponding to different tabs, such as a WPF interface (local interface), a cloud interface embedded in a web browser, and a third-party web page interface embedded in a web browser; the solid-line box 303 is the information display area. Specifically in the scenario of the embodiment of the present application, the solid-line box 303 in the figure is a cloud interface.

[0097] When a patient seeks medical treatment, the client needs to obtain the barcode (object identifier) ​​on the patient's medical record through a third-party device (such as hardware equipment in the medical industry), and then obtain all the medical information (object information) of the corresponding patient based on the object identifier.

[0098] When the client gets the data, it will determine the interface type (target interface type) of the tab (target tab) according to the current tab (target tab), and determine the interface type of the information sub-interface displayed in the information display area. When the module is a cloud interface, the custom control binding is used to implement the corresponding object information to fill in the information sub-interface; when the module is a normal web page, the JS thread is used directly to implement the corresponding object information to fill in the information sub-interface of the corresponding interface type.

[0099] Specifically, if it is displayed in the WPF interface, it is necessary to call the API (such as the API interface based on the cloud platform) to obtain the patient information in the patient form in the database in the cloud server. Then, through the data conversion tool in the client, the Json string transmitted by the kapi is converted into a dependency property type that can be used by the C# end, and displayed in the WPF interface. Among them, the type that can be used by the C# end is the entity class.

[0100] When the user switches to the diagnosis interface, the patient's diagnosis results need to be obtained through the patient information.

[0101] Specifically, the client passes the acquired object information to the JS process in the embedded browser kernel. The custom control listens to the methods in the JS process, converts the acquired patient information into information that can be used by the cloud interface, and displays it on the cloud interface through the cefsharp browser (embedded browser kernel).

[0102] When the user adds diagnostic information in the cloud interface, it needs to be displayed in the WPF interface and saved to the cloud platform database.

[0103] The WPF interface in another tab needs to obtain the newly added diagnostic information in the current diagnostic result interface. At this time, the diagnostic information is not saved in the cloud platform database. Therefore, the newly added diagnostic information is obtained through custom controls, converted into a data format that can be used by the WPF interface, and then passed to the client through the JS process, so that it can be viewed by users in the WPF interface.

[0104] At the same time, when the custom control obtains new diagnostic information and needs to save it, it can save it to the cloud platform database by sending the new information to the corresponding Java plug-in or directly calling the API to save it to the cloud platform database.

[0105] The above describes the data exchange method of this application in a specific business scenario. Figure 4 , the following is a data exchange device in an embodiment of the present application, including:

[0106] The acquisition unit 401 is used to respond to the viewing instruction input based on the object information interface and acquire the object identification collected by the third-party device; wherein the object information interface includes an information display area and multiple tabs, and each tab has a preset interface type;

[0107] The sending unit 402 is used to send the object identifier to the server through the application programming interface (API), and receive the object information corresponding to the object identifier returned by the server;

[0108] A determination unit 403, used to determine a target tab in a selected state among multiple tabs in the object information interface;

[0109] The display unit 404 is used to display the object information in the information display area according to the target interface type corresponding to the target tab.

[0110] In a specific implementation, the display unit 404 is specifically used to generate an information sub-interface corresponding to the target interface type, and fill the object information into the information sub-interface according to the target interface type;

[0111] In the information display area, the information sub-interface is displayed.

[0112] In a specific implementation, the display unit 404 is specifically configured to send the object information to the browser process if the information sub-interface is a predefined cloud interface;

[0113] Monitor the browser process through custom controls in the cloud interface to obtain object information;

[0114] Bind the obtained object information to the custom control;

[0115] In the information display area, the information sub-interface is displayed, including:

[0116] In the information display area, a cloud interface is displayed, wherein the custom control displays the obtained object information in the cloud interface.

[0117] In a specific implementation, the display unit 404 is specifically configured to, if the information sub-interface is a local interface, set the attribute type of the object information to a dependent attribute;

[0118] Fill the local interface with the object information set as the dependency property.

[0119] In a specific implementation, the display unit 404 is specifically used to determine the object information corresponding to the target tab from the object information;

[0120] According to the target interface type corresponding to the target tab, the object information corresponding to the target tab is displayed in the information display area.

[0121] In a specific implementation, the acquisition unit 401 is further used to, if the interface type of the information sub-interface displayed in the information display area is the first interface, and the information sub-interface is monitored through the custom control of the information sub-interface to have newly added object information related to the object identifier, then obtain the newly added object information through the browser process;

[0122] The device also includes: a new unit,

[0123] A new unit is added, used to fill in the newly added object information into the information sub-interface whose interface type is the second interface;

[0124] The display unit 404 is also used to display an information sub-interface whose interface type is the second interface in the information display area; wherein the first interface is a cloud interface or a local interface, the second interface is a cloud interface or a local interface, and the first interface and the second interface are different interface types.

[0125] In a specific implementation, the sending unit 402 is further used to send the newly added object information to the server for storage through an API or a custom control.

[0126] In the embodiment of the present application, different from the prior art where different data display pages need to obtain object information from the server respectively, the embodiment of the present application can display the object information obtained by the acquisition unit 401 from the server in the information display area through the display unit 404 according to the target interface type corresponding to the target tab. It is not necessary to obtain data from the server for each interface separately, which reduces the server load pressure.

[0127] Figure 51 is a schematic diagram of the structure of a data conversion device provided in an embodiment of the present application. The data conversion device 500 may include one or more central processing units (CPU) 501 and a memory 505. The memory 505 stores one or more application programs or data.

[0128] The memory 505 may be a volatile storage or a persistent storage. The program stored in the memory 505 may include one or more modules, each of which may include a series of instruction operations in the data conversion device. Furthermore, the central processing unit 501 may be configured to communicate with the memory 505 and execute a series of instruction operations in the memory 505 on the data conversion device 500.

[0129] The data conversion device 500 may also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input and output interfaces 504, and / or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0130] The CPU 501 can execute the aforementioned Figures 1 to 4 The operations performed by the data conversion device in the illustrated embodiment will not be described in detail here.

[0131] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0132] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0133] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0134] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0135] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

[0136] The embodiment of the present application also provides a computer program product comprising instructions, and when the computer program product is run on a computer, the computer is enabled to execute the aforementioned method.

Claims

1. A data interaction method, It is characterized in that Applied to a client, the client establishes communication connections with a third-party device and a server respectively, and the method includes: In response to a viewing instruction input based on an object information interface, obtaining an object identifier collected by the third-party device; wherein the object information interface includes an information display area and a plurality of tabs, and each tab has a preset interface type; Sending the object identifier to the server through an application programming interface (API), and receiving object information corresponding to the object identifier returned by the server; Determine a target tab in a selected state among multiple tabs of the object information interface; Displaying the object information in the information display area according to the target interface type corresponding to the target tab; The displaying of the object information in the information display area according to the target interface type corresponding to the target tab includes: Generate an information sub-interface corresponding to the target interface type, and if the information sub-interface is a predefined cloud interface, send the object information to the browser process; monitor the browser process through a custom control in the cloud interface to obtain the object information; bind the obtained object information to the custom control; display the cloud interface in the information display area, wherein the custom control displays the obtained object information in the cloud interface; or, Generate an information sub-interface corresponding to the target interface type. If the information sub-interface is a local interface, set the attribute type of the object information as a dependent attribute; fill the object information set as the dependent attribute into the local interface, and display the information sub-interface in the information display area.

2. The method according to claim 1, It is characterized in that The method further comprises: If the interface type of the information sub-interface displayed in the information display area is the first interface, and newly added object information related to the object identifier is detected in the information sub-interface through the custom control of the information sub-interface, the newly added object information is obtained through the browser process; Fill the newly added object information into the information sub-interface whose interface type is the second interface; In the information display area, an information sub-interface whose interface type is a second interface is displayed; wherein, the first interface is a cloud interface or a local interface, the second interface is a cloud interface or a local interface, and the first interface and the second interface are different interface types.

3. The method according to claim 2, It is characterized in that The method further comprises: The newly added object information is sent to the server through the API or the custom control for storage.

4. A data interaction device, It is characterized in that include: An acquisition unit, configured to respond to a viewing instruction input based on the object information interface and acquire an object identifier collected by a third-party device; The object information interface includes an information display area and multiple tabs, and each tab has a preset interface type; A sending unit, used to send the object identifier to a server via an application programming interface (API), and receive object information corresponding to the object identifier returned by the server; A determination unit, used to determine a target tab in a selected state among a plurality of tabs in the object information interface; A display unit, configured to display the object information in the information display area according to the target interface type corresponding to the target tab; The display unit is specifically used to generate an information sub-interface corresponding to the target interface type, and fill the object information into the information sub-interface according to the target interface type; and display the information sub-interface in the information display area; The display unit is specifically used to generate an information sub-interface corresponding to the target interface type, and if the information sub-interface is a pre-defined cloud interface, the object information is sent to the browser process; the browser process is monitored by the custom control in the cloud interface to obtain the object information; the obtained object information is bound to the custom control; and the cloud interface is displayed in the information display area, wherein the custom control displays the obtained object information in the cloud interface; or, The display unit is specifically used to generate an information sub-interface corresponding to the target interface type. If the information sub-interface is a local interface, the attribute type of the object information is set as a dependent attribute; the object information set as the dependent attribute is filled into the local interface; and the information sub-interface is displayed in the information display area.

5. A data interaction device, It is characterized in that include: CPU, memory and input / output interface; The memory is a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 3.

6. A computer storage medium, It is characterized in that The computer storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 3.

Images