CN115016841A

CN115016841A - Software docking method, data acquisition method and device and electronic equipment

Info

Publication number: CN115016841A
Application number: CN202210621207.5A
Authority: CN
Inventors: 陈军; 冯雅玲
Original assignee: Hangzhou Jiache Technology Co ltd
Current assignee: Hangzhou Jiache Technology Co ltd
Priority date: 2022-06-01
Filing date: 2022-06-01
Publication date: 2022-09-06

Abstract

The application provides a software docking method, a data acquisition device and electronic equipment, and relates to the technical field of communication networks. The software docking method comprises the following steps: writing the request data of the target software into a file package; configuring the request data into a newly-built marking file according to the file package; calling a target interface access marker file in the file packet to obtain target request data according to the request data, wherein the code amount of the target request data is less than that of the request data; interfacing with the target software based on the target request data. According to the method and the device, the parameters of the software docking process are configured through the setting file, the accessed interface is modified, the redundant codes which are highly similar in the software docking process are simplified in the interface access file of the file packet, the code amount in docking is reduced, docking between the software is achieved on the basis of the reduced parameters, writing of repeated codes is reduced, and code readability and docking efficiency between the software are improved.

Description

Software docking method, data acquisition method and device and electronic equipment

Technical Field

The present application relates to the field of communications network technologies, and in particular, to a software docking method, a data acquisition device, and an electronic device.

Background

Along with the continuous improvement of living standard of people, the demands of people such as consumption and travel are also greatly improved, more and more people like the form of self-driving travel, and the vehicle-mounted road book system is produced at the same time. The vehicle-mounted road book system can record and display map routes and interest points of restaurants, hospitals, scenic spots, hotels, parks and the like which are passed by users in the traveling process and generate files of comprehensive information for the users to check and refer.

In order to provide rich information for users, the current vehicle-mounted road book system is generally connected with application software with various functions so as to acquire related information of hotels, routes, scenic spots and the like in the software. In the prior art, similar docking processes are required when the road book system is docked with each application software, so that codes in the road book system are complicated and redundant, and the docking efficiency with the application software is low.

Disclosure of Invention

In view of this, an embodiment of the present invention provides a software docking method, a data obtaining device, and an electronic device, so as to solve the problems of code redundancy and low docking efficiency in software docking in the prior art.

In a first aspect, the present application provides a software docking method, including:

writing the request data of the target software into a file package;

configuring the request data into a newly-built marking file according to the file package;

calling a target interface in the file packet to access the markup file so as to obtain target request data according to the request data, wherein the code quantity of the target request data is smaller than that of the request data;

interfacing with the target software based on the target request data.

In the implementation process, when the road book system is in butt joint with target software with various different functions, one or more request data can be correspondingly processed in the file packet by extracting the request data which are extracted from the target software and contain highly similar or repeated codes into the file packet. The request data in the file package are configured into the corresponding mark files, the access ports during butt joint are modified, the target interfaces in the file package are accessed, the request data configured in the mark files can be inquired, the request data are simplified, the target request data with small code quantity are obtained, the butt joint request is responded on the basis of the parameters of the target request data with reduced code quantity, the butt joint between the software is realized, the writing of repeated codes during butt joint is reduced, and the code readability and the butt joint efficiency between the software are improved.

Optionally, the configuring, according to the file package, the request data into a newly created markup file includes:

determining a target item corresponding to the target software, wherein the target item is an item corresponding to a docking request initiated by the target software;

writing the file package into the target project;

establishing a corresponding markup file based on the target project;

configuring the request data in the bundle of files in the markup file.

In the implementation process, the target software can initiate a corresponding docking request after constructing the request data, and according to task scheduling of the project, the target project corresponding to the docking request initiated by the target software can be determined, so that the file package is introduced into the target project during docking, the tag file is newly established in the target project for configuring the request data in the file package, the request data constructed in the target software can be configured into the corresponding tag file, parameters during docking are constructed in the tag file, the request data does not need to be transmitted during docking, and the processing efficiency of the request data is improved.

Optionally, the invoking a target interface in the file package to access the markup file to obtain target request data according to the request data includes:

accessing the corresponding markup file according to the target interface in the file package to determine the request data;

analyzing the request data to obtain a parameter value;

constructing the target request data based on the parameter values.

In the implementation process, when the road book system is accessed to the target software of the third party, the original access positions of the construction request and the calling interface are not adopted, but the target interface in the calling file packet is accessed to the corresponding label file, so that the corresponding request data in the label file can be inquired and analyzed, and the target request data with smaller code quantity, less repetition and less similar codes is constructed by the analyzed parameter values. The code of the request data can be effectively simplified and reduced, and the code amount of various data which are not strongly related to the service during writing and butting of repeated codes is reduced, so that the readability of the code is improved.

Optionally, before the accessing the corresponding markup file according to the target interface in the package, the method further includes:

determining the target interface in the file package;

and searching the corresponding markup file based on the name information of the target interface.

In the implementation process, because the project can have a plurality of markup files configured corresponding to the target software, the target interface corresponding to the target software in the file package can be determined, and then the markup files are searched in the target project according to the name information of the target interface, so as to query the corresponding markup files. The parameters can be constructed by accessing the corresponding label files through the corresponding interfaces, so that the pertinence and the accuracy in construction are improved.

Optionally, the interfacing with the target software based on the target request data includes:

analyzing the target request data to obtain verification information of the target software;

interfacing with the target software based on the verification information.

In the implementation process, after target request data with a small code amount is constructed, verification information corresponding to the docking request can be obtained by analyzing the target request data, so that the road book system responds to the docking request according to the verification information and completes docking with target software. The butt joint can be carried out on the basis of small code quantity, and the efficiency in butt joint is effectively improved.

Optionally, the writing the request data of the target software into the file package includes:

acquiring the request data constructed by the target software, wherein the request data comprises parameter data and address data;

writing one or more of the requested data into the file package.

In the implementation process, each target software constructs request data before docking, and the request data comprises constructed request parameters and spliced target addresses. In order to simplify highly similar or repeated codes in the request data, the request data constructed by each target software can be obtained and extracted, so that one or more request data can be written into a file package, and the docking of the target software with various different functions can be processed.

In a second aspect, the present application provides a data acquisition method, including:

the method comprises the steps of docking with target software through any one of the software docking methods to obtain initial data in the target software;

screening the initial data according to the acquired user requirements to obtain target data;

and storing the target data into a corresponding database according to the type of the target data.

In the implementation process, after the road book system is in butt joint with the target software, initial data related to the road book in the target software can be obtained based on the butt joint, and the initial data is screened according to the obtained user requirements, so that target data of the user requirements are obtained and stored in a database of a corresponding type for the user to use. The data can be acquired, processed and stored on the basis of quick docking, the data acquisition efficiency is improved, and the user experience is effectively improved.

In a third aspect, the present application further provides a software docking apparatus, including:

the writing module is used for writing the request data of the target software into the file packet;

the configuration module is used for configuring the request data into a newly-built mark file according to the file package;

the access module is used for calling a target interface in the file packet to access the markup file so as to obtain target request data according to the request data, wherein the code amount of the target request data is smaller than that of the request data;

and the docking module is used for docking with the target software based on the target request data.

In the implementation process, the code quantity of the data during the butt joint can be simplified through the writing module, the configuration module and the access module, so that the butt joint module can respond to the butt joint request on the basis of the parameter of reduced code quantity, the butt joint between the software is realized, the writing of repeated codes during the butt joint is reduced, and the code readability and the butt joint efficiency between the software are improved.

In a fourth aspect, the present application further provides a data processing apparatus, comprising:

the acquisition module is used for docking with the target software through any one of the software docking methods to acquire initial data in the target software;

the screening module is used for screening the initial data according to the acquired user requirements to obtain target data;

and the storage module is used for storing the target data into a corresponding database according to the type of the target data.

In the implementation process, the data can be acquired, processed and stored on the basis of quick docking, the data acquisition efficiency is improved, and the user experience is effectively improved.

In a fifth aspect, the present application further provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores program instructions, and the processor executes steps in any implementation manner of the software docking method or the data acquisition method when reading and executing the program instructions.

In a sixth aspect, the present application further provides a computer-readable storage medium, where computer program instructions are stored, and when the computer program instructions are read and executed by a processor, the steps in any implementation manner of the software docking method or the data acquisition method are executed.

In summary, the application provides a software docking method, a data acquisition device and an electronic device, which can simplify and reduce highly similar or repeated codes during software docking, reduce writing of repeated codes, and improve readability of the codes, so that software docking is realized by using parameters with less code amount, and efficiency during software docking is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.

Fig. 1 is a schematic flowchart of a software docking method according to an embodiment of the present application;

fig. 2 is a detailed flowchart of a step S200 according to an embodiment of the present disclosure;

fig. 3 is a detailed flowchart of a step S300 according to an embodiment of the present disclosure;

fig. 4 is a schematic flowchart of another software docking method provided in the embodiment of the present application;

fig. 5 is a detailed flowchart of a step S400 provided in an embodiment of the present application;

fig. 6 is a schematic flowchart of a data acquisition method according to an embodiment of the present application;

fig. 7 is a schematic block diagram of a software docking apparatus according to an embodiment of the present application;

fig. 8 is a block diagram of a data processing apparatus according to an embodiment of the present disclosure.

Icon: 600-a software interfacing means; 610-a write module; 620-configuration module; 630-an access module; 640-a docking module; 700-a data processing apparatus; 710-an acquisition module; 720-screening module; 730-save module.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without any creative effort belong to the protection scope of the embodiments of the present application.

When each application software of the current road book system is docked, a similar docking process needs to be performed, for example: various parameters related to and unrelated to the service, such as a signature verification parameter and request parameters necessary for some services, etc., need to construct a corresponding address to request an interface of each application software, to obtain the parameters in the application software for resolution, etc. However, the correlation between the codes of a lot of data in the docking process and the service is weak, so that a lot of highly similar or repeated contents are in the part of the codes in the docking process, the highly similar or repeated contents need to be written for many times, the code contents are complicated and redundant, the writing cost of the codes when the road book system is docked with the application software is increased, and the docking efficiency is reduced.

In order to solve the above problem, an embodiment of the present application provides a software docking method, which is applied to an electronic device, where the electronic device may be provided with a road book system having a road book function, the road book system is a software program capable of making a detailed plan for a trip, and the road book system may provide a user with a plurality of travel-related services including travel arrangement, traffic information, accommodation information, scenic spot and restaurant recommendation, entertainment reservation, cost information, and the like. The electronic equipment provided with the road book system can be in butt joint with application software with multiple functions through a network by adopting the software butt joint method provided by the embodiment of the application, and the application software can be a software program for providing multiple data related to travel so as to obtain application data in the application software and provide road book service for a user.

Alternatively, the electronic device may be an electronic device having a logic calculation function, such as a server, a Personal Computer (PC), a tablet PC, a smart phone, a Personal Digital Assistant (PDA), or the like.

Alternatively, in order to provide better road book service for the user, the electronic device may be provided in the vehicle of the user, for example, an in-vehicle terminal device provided with a road book system, to provide corresponding service according to real-time data of the vehicle of the user. In an application scene that the electronic equipment is installed in a vehicle, a user can interact with the vehicle-mounted terminal equipment to complete the interface with the application software. The interaction mode can include interaction with keys of the vehicle-mounted terminal device, or interaction with an interaction interface such as a display screen and a display, relevant information and instructions are input, docking with the target software is completed on the basis of the vehicle network communication function, and various data acquired after docking can be displayed on the display screen and the display of the vehicle-mounted terminal device, such as a liquid crystal display or a touch display, so that a user can check and know the data in the driving process.

Optionally, the electronic device may also be a mobile terminal provided with a road book system, such as a mobile phone, a tablet computer, and the like, so as to provide corresponding services according to the personal real-time data of the user. In an application scene in which the electronic device is a mobile terminal, a user can interact with an interactive interface, namely a screen, of the mobile terminal, input related information and instructions, complete the docking with target software on the basis of network function communication of the mobile terminal, and display various data acquired after the docking in the screen so that the user can check and know the data in various scenes such as driving, lodging, playing and the like.

Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a software docking method according to an embodiment of the present disclosure, where the method may include steps S100-S400.

Step S100, writing the request data of the target software into a file packet.

The target software may be third-party application software that provides multiple different data and has multiple different functions, such as hotel application software that provides accommodation data of hotels or residents, navigation software that provides navigation data, and ticket-buying application software that provides scenic spot data. The file package may be in a document format in JAVA or the like, for example, a jar package, which can integrate a plurality of files into one file. Before docking, each target software can initiate a docking request based on task scheduling of items in CPS (Cost Per Sales, a popularization method for charging according to actual Sales), and corresponding request data is constructed to make a request before initiating the request. The request data may include various types of parameter data and address data, such as a signature verification parameter for verification, a request parameter related to a request service, a constructed URL (Uniform Resource Locator) address, and the like.

Optionally, the manner of writing the request data may include: acquiring request data constructed by target software; one or more request data are written to the file package. The data sent by one or more target software can be obtained through the network, and one or more request data are extracted from the data, so that a plurality of request data are written into the file packet to be combined into one file. In order to simplify highly similar or repeated codes in the request data, the request data constructed by each target software can be obtained and extracted, so that one or more request data can be written into a file package, and the docking of the target software with various different functions can be processed.

Optionally, when the target software constructs the request data, various parameters, such as a timestamp, an access Secret (key), a page, a size (generic element function), a channel, a format (formatting function), a signature, and a user (user data), may be set in a declared Map (a container storing elements according to keys (keys)), so that some of the parameters, such as the timestamp, the format, the signature, and the user, belong to parameters required for verification and have a small association with the service, but are necessary at the time of docking, resulting in more highly similar or repeated codes in the request data.

Optionally, the request parameters in the request data may further include Http Headers (claim request header), a content Type (media Type information) set in the request header, a body (claim request body), a page Size (page Size), a page Index (page subscript) set in the request body, and the like. After the request data is constructed, the target software constructs a corresponding docking request.

And step S200, configuring the request data into a newly-built marking file according to the file package.

The Markup file newly created in the project corresponding to the docking may be in a plurality of Markup Language formats such as xml (eXtensible Markup Language), and the parameter codes in the request data included in the package of files may be configured in the Markup file, so that the parameters during the docking may be subjected to component processing in the Markup file.

Step S300, a target interface in the file packet is called to access the markup file, so as to obtain target request data according to the request data.

In the selection of the interface, the target software is accessed at the access position without adopting the construction request and the calling interface, but the target interface in the calling file packet is selected, and the request data can be directly accessed into the marking file to be processed, so that the target request data with the code quantity smaller than that of the request data is obtained. By directly accessing the markup file to process the request data, highly similar or repeated code contents in the request data can be effectively reduced, and codes of multiple lines in the request data can be reduced into fewer lines, so that the request data is simplified, and the target request data with smaller code amount is obtained.

Alternatively, the target Interface in the file package may be an api (Application Programming Interface) Interface in the jar package.

And S400, interfacing with the target software based on the target request data.

The road book system can correspond to the docking request of the target software on the basis of the parameters of the target request data with small code quantity, and can realize docking with the target software only by calling the data with small code quantity.

In the embodiment shown in fig. 1, the writing of repeated codes during docking is effectively reduced, the writing cost of the codes is reduced, and the readability of the codes and the efficiency of docking between software are improved.

Optionally, referring to fig. 2, fig. 2 is a detailed flowchart of step S200 according to an embodiment of the present disclosure, and step S200 may include steps S210 to S240.

Step S210, determining a target item corresponding to the target software.

The target item is an item corresponding to a docking request initiated by the target software, namely an Pom (project object model) file in use.

Step S220, writing the file package into the target item.

The file package can be written into the target project, so that the file package is stored in the target project, and the file package is introduced into the target project to be correspondingly processed.

Step S230, creating a corresponding markup file based on the target project.

In order to simplify the code of the parameter, the request data is configured by newly establishing a corresponding tag file in the target project.

Alternatively, the newly created markup file may be named according to parameters such as name, type, and request of the target software, for example xx (name of target software) hoteliquest.

Step S240, configuring the request data in the file package in the markup file.

The request data in the markup file can be directly configured in the corresponding markup file without transmitting a code called in the request data during docking, so that parameters during docking are constructed in the markup file.

Alternatively, the configuration mode may include various modes such as copying, writing and the like.

In the embodiment shown in fig. 2, the processing efficiency of the requested data is effectively improved by configuring in the newly created markup file.

Optionally, referring to fig. 3, fig. 3 is a detailed flowchart illustrating a step S300 according to an embodiment of the present disclosure, where the step S300 may include steps S310 to S330.

Step S310, accessing the corresponding markup file according to the target interface in the file package to determine the request data.

When the target software is accessed, the target interface in the calling file packet is accessed into the corresponding tag file instead of the access part of the original construction request and the calling interface so as to determine the corresponding request data, and parameters during the butt joint can be constructed in the tag file in a unified manner.

Step S320, analyzing the request data to obtain a parameter value.

In order to simplify the highly similar or repeated parameter codes in the request data, the corresponding parameter values can be obtained through analysis, the parameter values can include the relevant contents of elements and features in various different parameters, and the forms of the parameter values can include numerical values, character strings and the like.

Step S330, the target request data is constructed based on the parameter values.

The request parameters are reconstructed according to the parameter values, and target request data with small code quantity, less repeated and similar codes can be constructed.

In the embodiment shown in fig. 3, the code of the requested data can be effectively simplified and reduced, and the code amount of various data which are not strongly related to the business when writing and docking repeated codes is reduced, so that the readability of the code is improved.

Optionally, referring to fig. 4, fig. 4 is a schematic flowchart of another software docking method provided in the embodiment of the present application, and before step S310, steps S340 to S350 may also be included.

Step S340, determining the target interface in the file package.

Because the project can have a plurality of label files which are obtained by corresponding configuration of the target software, the target interface corresponding to the target software in the file package can be determined first, so that the accuracy in accessing is improved.

Step S350, searching the corresponding markup file based on the name information of the target interface.

The name information of the target interface may include information related to the name, type, docking request, and the like of the target software, and the markup files with names corresponding to the name information may be searched for by searching in the plurality of markup files according to the name information.

In the embodiment shown in fig. 4, the parameters can be built by accessing the corresponding markup files through the corresponding interfaces, so that the pertinence and the accuracy during building are improved.

Optionally, referring to fig. 5, fig. 5 is a detailed flowchart of step S400 provided in the present embodiment, where step S400 may include steps S410 to S420.

Step S410, analyzing the target request data to obtain the verification information of the target software.

The verification information is data obtained by analyzing various parameters in the target request data, and may include various data used for verifying the connection, such as a timestamp, a key, a signature, and the like in the request.

And step S420, interfacing with the target software based on the verification information.

The road book system can verify data such as a timestamp, a key and a verification label which are summarized by verification information, and respond to a docking request when verification is successful to complete docking with target software.

In the embodiment shown in fig. 5, the docking can be performed on the basis of a small code amount, and the efficiency in the docking is effectively improved.

Referring to fig. 6, fig. 6 is a schematic flowchart of a data acquisition method according to an embodiment of the present disclosure, where the method may include steps S500 to S520.

Step S500, the initial data in the target software is obtained by butting with the target software.

After the road book system responds to the docking request of the target software and completes docking, the target software can be accessed through the network, and initial data applied in the target software is obtained.

Optionally, the initial data may include various types of data, such as hotel, and accommodation data, including location, price, evaluation, and other related data of the hotel; the scenic spot data comprise the positions of the scenic spots, the prices of entrance tickets, scenic spot pictures and other related data; and the navigation data comprises related data such as a route, a length, road conditions and the like.

And step S510, screening the initial data according to the acquired user requirements to obtain target data.

The method comprises the steps that the road book service is required by users, the user requirements can be obtained in order to improve the use experience of the users, initial data are screened according to the user requirements, fields in the initial data can be extracted according to keywords in the user requirements in a screening mode, and target data meeting the user requirements can be generated.

And S520, storing the target data into a corresponding database according to the type of the target data.

The method includes the steps of storing the target data into a database according to the type of the target data, for example, the target data belongs to hotel data, scenic spot data or navigation data, and generating a corresponding hotel data list, scenic spot data list or navigation data list.

Optionally, after entering the front-end page of the road book system, the user may also input location information, such as longitude and latitude, to obtain various road book lists stored in the database, and the user may also select an interested road book to place an order, or enter a mall to select an interested commodity to place an order.

In the embodiment shown in fig. 6, data can be acquired, processed and stored on the basis of quick docking, so that the data acquisition efficiency is improved, and the user experience is effectively improved.

Referring to fig. 7, fig. 7 is a schematic block diagram of a software docking device according to an embodiment of the present disclosure, where the software docking device 600 may include:

a writing module 610, configured to write request data of the target software into the file package;

a configuration module 620, configured to configure the request data into a newly created markup file according to the file package;

an access module 630, configured to invoke a target interface in the file package to access the markup file, so as to obtain target request data according to the request data, where a code amount of the target request data is smaller than a code amount of the request data;

a docking module 640 configured to dock with the target software based on the target request data.

In an optional embodiment, the configuration module 620 may further include a determination sub-module, a lead-in sub-module, a new sub-module, and a configuration sub-module;

the determining submodule is used for determining a target item corresponding to the target software, wherein the target item is an item corresponding to a docking request initiated by the target software;

the import submodule is used for writing the file package into the target project;

the new sub-module is used for creating a corresponding markup file based on the target project;

and the configuration submodule is used for configuring the request data in the file packet in the tag file.

In an optional embodiment, the access module 630 may further include an access sub-module, a first parsing sub-module, and a building sub-module;

the access sub-module is used for accessing the corresponding tag file according to the target interface in the file packet to determine the request data;

the first analysis submodule is used for analyzing the request data to obtain a parameter value;

a construction submodule for constructing the target request data based on the parameter values.

In an optional embodiment, the access module 630 may further include an interface determination sub-module and a search sub-module;

the interface determining submodule is used for determining the target interface in the file package;

and the searching submodule is used for searching the corresponding markup file based on the name information of the target interface.

In an optional embodiment, the docking module 640 may further include a second parsing sub-module and a verification sub-module;

the second analysis submodule is used for analyzing the target request data to obtain the verification information of the target software;

and the verification sub-module is used for docking with the target software based on the verification information.

In an optional embodiment, the writing module 610 may further include an obtaining sub-module and an extracting sub-module;

the acquisition submodule is used for acquiring the request data constructed by the target software, wherein the request data comprises parameter data and address data;

and the extraction sub-module is used for writing one or more request data into the file packet.

Since the principle of the software docking apparatus 600 in the embodiment of the present application for solving the problem is similar to that in the foregoing embodiment of the software docking method, the implementation of the software docking apparatus 600 in the embodiment of the present application can refer to the description in the foregoing embodiment of the software docking method, and repeated details are not repeated.

Referring to fig. 8, fig. 8 is a block diagram of a data processing apparatus according to an embodiment of the present disclosure, where the data processing apparatus 700 may include:

an obtaining module 710, configured to obtain initial data in target software by interfacing with the target software;

the screening module 720 is configured to screen the initial data according to the obtained user requirement to obtain target data;

a storage module 730, configured to store the target data in a corresponding database according to the type of the target data.

Since the principle of the data processing apparatus 700 in the embodiment of the present application for solving the problem is similar to that in the foregoing embodiment of the data processing method, the implementation of the data processing apparatus 700 in the embodiment of the present application can refer to the description in the foregoing embodiment of the data processing method, and repeated descriptions are omitted.

The embodiment of the present application further provides a computer-readable storage medium, where computer program instructions are stored, and when the computer program instructions are read and executed by a processor, the steps in any implementation manner of the software docking method or the data acquisition method provided in this embodiment are executed.

In summary, the embodiments of the present application provide a software docking method, a data obtaining device, and an electronic device, which can simplify and reduce highly similar or repeated codes during software docking, reduce writing of repeated codes, and improve readability of codes, thereby implementing software docking with parameters with a small code amount, and improving efficiency during software docking.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices according to various embodiments of the present application. In this regard, each block in the block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams, and combinations of blocks in the block diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. The present embodiment further provides a readable storage medium, which stores computer program instructions, and when the computer program instructions are read and executed by a processor, the computer program instructions perform the steps of any one of the block data storage methods. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a Read-Only Memory (ROM), a RanDom Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application.

It should be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Claims

1. A method of software docking, the method comprising:

writing the request data of the target software into a file packet;

interfacing with the target software based on the target request data.

2. The method of claim 1, wherein the configuring the request data into a newly created markup file according to the package of files comprises:

writing the file package into the target project;

establishing a corresponding markup file based on the target project;

configuring the request data in the bundle of files in the markup file.

3. The method of claim 1, wherein the invoking a target interface in the bundle of files to access the markup file to obtain target request data according to the request data comprises:

analyzing the request data to obtain a parameter value;

constructing the target request data based on the parameter values.

4. The method of claim 3, wherein before accessing the corresponding markup file according to the target interface in the bundle, the method further comprises:

determining the target interface in the file package;

5. The method of claim 1, wherein interfacing with the target software based on the target request data comprises:

interfacing with the target software based on the verification information.

6. The method of claim 1, wherein writing the requested data of the target software into a file package comprises:

writing one or more of the requested data into the file package.

7. A method for data acquisition, the method comprising:

interfacing with target software by the method of any one of claims 1-6 to obtain initial data in the target software;

8. A software docking apparatus, the apparatus comprising:

the configuration module is used for configuring the request data into a newly-built marking file according to the file package;

9. A data processing apparatus, characterized in that the apparatus comprises:

an acquisition module, configured to interface with target software by the method according to any one of claims 1 to 6, to acquire initial data in the target software;

10. An electronic device comprising a memory having stored therein program instructions and a processor that, when executed, performs the steps of the method of any of claims 1-7.

11. A computer-readable storage medium having computer program instructions stored thereon for execution by a processor to perform the steps of the method of any one of claims 1-7.