A data access method, apparatus and device

By utilizing standard data formats and carriers on edge computing devices for data access, the issues of application (APP) interface customization and version dependency are resolved, thereby improving the security and efficiency of data access.

CN115081023BActive Publication Date: 2026-06-12SHANGHAI ELECTRIC WIND POWER GRP CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
SHANGHAI ELECTRIC WIND POWER GRP CO LTD
Filing Date
2022-07-29
Publication Date
2026-06-12

Smart Images

  • Figure CN115081023B_ABST
    Figure CN115081023B_ABST
Patent Text Reader

Abstract

The application provides a data access method, device and equipment. An electronic device downloads a target application carrying an application requirement description file, so that when the target application is running, the electronic device can provide a data read-write interface service to the target application by using a standard data carrier and a standard data format recorded in the application requirement description file. It can be seen that the application restricts the target application to read and write to-be-input and to-be-output data only in the standard data carrier and the standard data format declared in the application requirement description file, the data access range is clear, other unauthorized data is not leaked, and the data security can be effectively improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application pertains to the technical field of data processing technology, and particularly relates to a data access method, apparatus, and device. Background Technology

[0002] The high-frequency data generated by real-time monitoring equipment during operation is of great value for condition monitoring, online diagnostics, and offline analysis. Taking the monitoring of industrial equipment's operating status as an example, edge computing devices located on the equipment side of the edge computing platform can provide real-time and historical data for various applications running on them, enabling the value mining of industrial data. Applications running on edge computing devices typically utilize database interfaces, APIs (Application Programming Interfaces), or communication protocol interfaces to access data and provide feedback. Specifically, database interfaces directly provide input data tables and return result tables through common databases such as MySQL or Redis; API interfaces access data for reading and writing through platform-provided API functions; and communication protocol interfaces receive data and send results through communication ports and associated protocols.

[0003] However, this presents at least the following technical challenges for applications running on edge computing devices: First, interface (such as API, database, or communication protocol interfaces) dependency: applications need to be custom-developed specifically for the communication interfaces on edge computing devices to access data. Second, version dependency: when interfaces need upgrading or adjustment, applications also need to be adapted accordingly. Third, unclear definition of the data access scope for applications: users may receive unwanted data in addition to the data they need, leading to reduced data security. Summary of the Invention

[0004] This application provides a data access method, apparatus, and device that can improve data security without relying on a specific interface for accessing data.

[0005] The technical solution provided in this application includes:

[0006] In a first aspect, embodiments of this application provide a data access method applied to an electronic device, the method comprising:

[0007] Download the released target application that carries the defined application requirement description file, wherein the application requirement description file records the standard data format requirements, standard data carrier requirements, data input information, data output information, and operating cycle supported by the target application.

[0008] According to the aforementioned operating cycle, the target application is run to read the input data stored in the first data format from the first data carrier and process the read target data; wherein, the first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from the data source that matches the data input information;

[0009] The processed data to be output is transmitted to the designated data destination using the second data carrier in the second data format; wherein, the second data carrier is the standard data carrier corresponding to the data carrier requirement information, and the second data format is the standard data format corresponding to the data format requirement information; the data to be output is the data that matches the data output information.

[0010] Secondly, embodiments of this application provide a data access device applied to an electronic device, the device comprising:

[0011] The application download unit is used to download the released target application carrying the set application requirement description file, wherein the application requirement description file records the standard data format requirement information, standard data carrier requirement information, data input information, data output information and running cycle supported by the target application.

[0012] The data reading unit is configured to run the target application according to the running cycle, so as to read the input data stored in the first data format from the first data carrier through the target application, and process the read target data; wherein, the first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from the data source that matches the data input information;

[0013] The data writing unit is used to transmit the processed data to be output to a specified data destination using the second data carrier in a second data format; wherein, the second data carrier is a standard data carrier corresponding to the data carrier requirement information, and the second data format is a standard data format corresponding to the data format requirement information; the data to be output is data that matches the data output information.

[0014] As can be seen from the above technical solutions, in this application, the electronic device downloads a target application carrying an application requirement description file. When running the target application, the electronic device can use the standard data carrier recorded in the application requirement description file to read data in a standard data format that matches the input data recorded therein, process the data, and transmit the processed data that matches the output data recorded therein to the designated data destination using the standard data carrier in a standard data format. Therefore, this application embodiment no longer directly reads the input data from the database through the application, but writes the input data in a standard data format into a standard data carrier. This allows the target application to directly read the input data in a standard data format from the standard data carrier, eliminating the need to customize a dedicated communication interface for the target application and thus avoiding dependence on existing communication interface versions. Furthermore, since the read data matches the input data recorded in the application requirement file, only the output and input data required by the application requirement file can be obtained from the data carrier. The data access scope is clearly defined, preventing the leakage of other unnecessary data and thus improving data security. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0016] Figure 1 A flowchart illustrating a data access method provided in this application;

[0017] Figure 2 A flowchart illustrating an authorization confirmation method provided in this application;

[0018] Figure 3 A schematic diagram of the structure of a data access device provided in this application;

[0019] Figure 4 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0021] See Figure 1 , Figure 1The flowchart of a data access method provided in this application is applied to an electronic device. This electronic device can belong to an edge computing platform or a cloud platform. Taking an edge computing platform as an example, the edge computing platform includes at least edge computing devices and a central server. Each edge computing device connects to different industrial devices to obtain data on the operating status of those industrial devices. All edge computing devices are interconnected and connected to the central server, enabling them to display applications running on them to different users. Therefore, the electronic device can be any edge computing device or a central server; this embodiment is not limited in this respect.

[0022] like Figure 1 As shown, the process of implementing this method may include the following steps:

[0023] Step 101: Download the published target application that carries the defined application requirements description file. If the application meets the runtime resource requirements, proceed to step 102.

[0024] The application requirements description file contains information on the standard data format requirements, standard data carrier requirements, data input information, data output information, and operating cycle supported by the target application.

[0025] The target application can be developed or tested on a device within the platform of the electronic device, or on a device independent of the electronic device. To reduce the processing burden on devices within the platform of the electronic device, some embodiments include applications developed and tested on electronic devices outside the platform. In this embodiment, the application can be developed, tested, and evolved independently of the platform, without affecting or depending on each other.

[0026] In this embodiment, the target application can choose from common data formats such as BIN, CSV, JSON, or XML, depending on user preference; JSON is recommended. The standard data carrier can also be chosen from common formats such as files, shared memory, named pipes, or communication ports, with files being recommended. Under these conditions, when running the target application, the electronic device does not need to prepare a separate data format and data carrier for the target application. It only needs to use common standard data formats and data carriers to run the target application, reducing the additional burden on the electronic device for running the target application.

[0027] In some embodiments, the communication interface supported by the target application for interfacing with other applications can adopt a standard communication interface to interact with other devices on the same platform as the electronic device or with devices independent of the same platform. Here, the development of the target application can choose a preferred mainstream technology stack.

[0028] After performing step 101, in some embodiments, based on the standard data format and standard data carrier recorded in the application requirements description document, the standard data format and standard data carrier are prepared in advance for the target application to access data according to user needs.

[0029] In one embodiment, the application requirements description file can be written according to the set application requirements template, and the application requirements template can serve as the only interface between the application and the electronic device, which is clear at a glance and less prone to errors.

[0030] Step 102: Run the target application according to the running cycle, so as to read the input data stored in the first data format from the first data carrier through the target application, and process the read target data.

[0031] Wherein, the first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from the data source that matches the data input information.

[0032] The first data carrier does not refer to a specific, fixed data carrier, but is named to distinguish it from other data carriers; this will not be repeated in subsequent embodiments of the present invention. The first data carrier is prepared in advance based on the standard data carrier corresponding to the data carrier requirement information, and belongs to the standard data carrier corresponding to the data carrier requirement information.

[0033] Accordingly, the first data format does not specifically refer to a fixed data format, but is named to distinguish it from other data formats, and will not be repeated hereafter in the embodiments of the present invention. The first data format is prepared in advance according to the standard data format corresponding to the data carrier requirement information, and belongs to the standard data format corresponding to the data format requirement information.

[0034] The input data stored in the first data carrier is stored in a first data format. As an example, the input data at the data source can be stored in a data format different from the first data format, which is called the first specified data format. When reading the input data, the internal data format is first converted into the first data format and transmitted in the first data carrier. Based on this, the target application reads the input data stored in the first data format from the first data carrier.

[0035] The input data required by the target application may be the same as that required by other applications. Therefore, the same input data can be read from the database once and written into its respective data carrier in its own data format, achieving batch processing. In contrast, the conventional method requires each application to query the same input data once. If there are many applications, this increases the number of queries for the same input data, thus increasing the system's processing burden. Therefore, as an embodiment, if the input data for the target application is the same as that for other target applications, the same input data is extracted from the data source all at once and written into the first data carrier in the first standard data format corresponding to the target application, and into its corresponding standard data carrier in the standard data format corresponding to the other target applications. It is evident that the technical solution provided in this embodiment can improve system processing efficiency. As another embodiment, the application requirement description files corresponding to the target application and other target applications are obtained. According to the data input information in each of the obtained application requirement description files, the data to be input that matches each data input information is read from the data source. The read data to be input is stored in a pre-defined subset. The subset is then distributed to the target application corresponding to it. In this embodiment, the subset is a subset that corresponds one-to-one with each target application.

[0036] In some embodiments, the application requirements description file further includes: runtime resource requirements; and implementing step 102, running the target application according to the runtime cycle, includes:

[0037] If the runtime resource requirements are met, then the step in step 102, which involves running the target application according to the stated runtime cycle, is executed.

[0038] In this embodiment, the runtime resource requirement can be understood as the resource usage requirement of the target application, so as to determine whether the electronic device has enough storage space and CPU computing power to run the target application based on the resource usage requirement. At the same time, for electronic devices that do not meet the runtime resource requirement, the application is refused to run and an error is reported.

[0039] Step 103: The processed output data is transmitted to the specified data destination using the second data carrier in the second data format.

[0040] Wherein, the second data carrier is a standard data carrier corresponding to the data carrier requirement information, the second data format is a standard data format corresponding to the data format requirement information, and the data to be output is data that matches the data output information.

[0041] Here, the second data carrier does not specifically refer to a fixed data carrier, but is named to distinguish it from other data carriers; this will not be repeated in subsequent embodiments of the present invention. The second data carrier is prepared in advance based on the standard data carrier corresponding to the data carrier requirement information, and belongs to the standard data carrier corresponding to the data carrier requirement information. The second data carrier can be the same as the first data carrier, or it can be a different data carrier. This embodiment does not limit this, and it can be selected according to personal preference.

[0042] Accordingly, the second data format does not specifically refer to a fixed data format, but is named to distinguish it from other data formats, and will not be repeated hereafter in this embodiment. The second data format is prepared in advance according to the standard data format corresponding to the data carrier requirement information, and belongs to the standard data format corresponding to the data format requirement information. The second data format can be the same as the first data format, or it can be a different data format. This embodiment does not limit this, and it can be selected according to personal preference.

[0043] It should be noted that after step 103, the method further includes: converting the data to be output stored in the second data format into a second specified data format that is different from the second data format and stored therein. The second specified data format may be the same as or different from the first specified data format. This embodiment does not limit this.

[0044] In some embodiments, after step 103, the data to be output is displayed to the user in a second data format according to the user's request.

[0045] Therefore, in the technical solution provided in this application embodiment, the electronic device downloads a target application carrying an application requirement description file. When running the target application, the electronic device can use the standard data carrier recorded in the application requirement description file to read data in a standard data format that matches the input data recorded therein, process the data, and transmit the processed data that matches the output data recorded therein to the designated data destination using the standard data carrier in a standard data format. Thus, this application embodiment no longer directly reads the input data from the database through the application, but writes the input data in a standard data format into a standard data carrier. This allows the target application to directly read the input data in a standard data format from the standard data carrier, eliminating the need to customize a dedicated communication interface for the target application and thus avoiding dependence on existing communication interface versions. Furthermore, since the read data matches the input data recorded in the application requirement file, only the output and input data required by the application requirement file can be obtained from the data carrier. The data access scope is clearly defined, preventing the leakage of other unnecessary data and improving data security.

[0046] After completion Figure 1 Following the flowchart, in some embodiments, the application requirements description document contains a tamper-proof digital fingerprint. After step 101, the method includes: verifying whether the target application has been tampered with using the digital fingerprint; if not, determining that the target application has not been tampered with, and proceeding to step 102; if yes, determining that the target application has been tampered with. Upon determining that the target application and the application requirements description document have been tampered with, a prompt message indicating that the target application and / or the application requirements document has been tampered with can be displayed, allowing the user to determine, based on the prompt message, that the target application or the application requirements document is illegal and is the source of illegal copying, and thus decide how to handle the target application. The digital fingerprint can provide a non-repudiation mechanism for both parties.

[0047] To ensure the validity and security of the target application and application requirement description file (APDR) uploaded to the edge computing server, as an example, before executing step 101, after the target application has been approved by the platform to which the electronic device belongs, the platform assigns an authorization certificate to the target application. This authorization certificate is used to verify the platform authorization validity of the target application and the APDR when the target application is uploaded to the platform. Therefore, the authorization certificate serves as an endorsement of the target application by the platform to which the electronic device belongs, allowing users to use it with confidence.

[0048] In this embodiment, the validity of the target application can be verified manually using an authorized certificate, or the target application can be verified using an electronic device using an authorized certificate, or the target application can be verified using an authorized certificate by a device independent of the electronic device but belonging to the same platform. This embodiment does not limit the scope of the verification.

[0049] To ensure the effectiveness and security of the target application running on the edge computing device, after step 101, the following steps A to B are also included:

[0050] Step A: Based on the authorization certificate carried by the target application, perform platform authorization validity authentication on the target application and the application requirements description file.

[0051] The authorization certificate is downloaded along with the target application. The validity of the target application is then checked using the authorization certificate. If the authorization certificate is valid, the application passes the validity authentication and proceeds to step B. If not, a message indicating that the application's validity authentication failed is displayed.

[0052] Step B: If both the digital fingerprint and the authorization certificate of the target application pass the validity authentication, proceed to step 102.

[0053] Digital fingerprints can be used to ensure that a target application has not been tampered with.

[0054] As an example, such as Figure 2 As shown, after performing step 101, steps 201 to 203 are also included:

[0055] Step 201: Receive the authorization confirmation request sent by the target device.

[0056] Wherein, the target device is a designated electronic device in the platform of the electronic device, and the authorization confirmation request includes authorization settlement information; the authorization requirement settlement information is determined by the target device based on the resource usage information, authorization requirement information, and authorization period recorded in the application requirement description file, or the duration between the time of the last authorization requirement settlement and the time of cancellation of the target application;

[0057] Resource usage information includes at least CPU computing power requirements, memory requirements, persistent storage requirements, input and output data traffic, service information corresponding to the data provided to the user, and service information required by the target application within a license period. The purpose of setting resource usage information is to prevent too many applications from running on a single device with the target application installed, thereby avoiding lag issues.

[0058] The target device determines the authorization settlement information based on the traffic required for the input and output data, the service information corresponding to the data provided to the user, and the service information required by the target application within an authorization period.

[0059] It should be noted that resource usage information, authorization requirements, and authorization periods have been pre-filled in the application requirements description file, making authorization settlement transparent, simple, and independent of the system, thus avoiding contradictions caused by authorization settlement information.

[0060] As an example, the start time of the first authorization period can be the download time corresponding to the download of the target application, a set time specified after the download of the target application, or the authorization time corresponding to the running of the target application.

[0061] This embodiment stops the settlement when the target application is logged out.

[0062] Step 202: Output authorization confirmation message.

[0063] The authorization confirmation prompt message is used to prompt for authorization confirmation, and includes authorization request settlement information.

[0064] The authorization confirmation message in this step is to display the authorization request settlement information to the user so that the user can proceed to step 203 based on the authorization confirmation message.

[0065] Step 203: Perform the authorization confirmation operation according to the operation command input in response to the authorization confirmation prompt information.

[0066] As can be seen, the technical solution provided in this application can perform authorization confirmation operations for each running target application, avoiding contradictions and disputes caused by different authorization settlement information of the target applications.

[0067] This concludes the description of the method embodiment.

[0068] To better illustrate the above embodiments, a specific example is provided below. Company A decides to develop two demonstration applications (APPs) for an edge computing platform. The development team, after technology selection, decides to use C and Python to develop the two demonstration APPs respectively, using a unified standard file interface for data interaction with the edge computing platform. Demonstration application 01 (hereinafter referred to as demo01) is developed in C. demo01 is developed and tested independently of the edge computing platform, using standard and universal communication interfaces during development to avoid being affected by changes in the APP interface on the edge computing platform. Furthermore, to ensure the developed application supports universal standard data formats and standard data carriers for data interaction, JSON format is chosen here, with files as the data carrier.

[0069] After demo01 is developed, fill in the standard template provided by the designated device of the edge computing platform as shown in Table 1. This template includes input data such as current wind speed and yaw angle, output data in JSON format indicating whether to shut down, JSON format corresponding to the current wind speed, JSON format for the yaw angle, a 100ms runtime cycle, and runtime resource requirements (maximum resource usage: 1% CPU usage, 50MB memory, 1MB disk usage). See Table 2 for details. Then, use the designated device of the edge computing platform to export the table as a plain text "Application Requirements Description File" JSON file. Finally, use Company A's certificate and private key to generate digital fingerprints for demo01 and the "Application Requirements Description File" JSON file (e.g., demo1.json) to ensure that the demo application and the application requirements description file are not tampered with.

[0070] Table 1 Standard Template

[0071]

[0072]

[0073] Table 2 Application Requirements Description Document

[0074]

[0075]

[0076] After verifying and approving the "Application Requirements Description Document" of Company A's application demo01 through designated devices in the edge computing platform, an authorization certificate is provided to confirm the legality and validity of the APP and its "Application Requirements Description Document".

[0077] After the validity of the target application and the validity of the application requirements description document have both been verified, the platform publishes Company A's application demo01. User B browses and views the application requirements description document of demo01. This process is ensured by the application verification algorithm specified in the edge computing platform, guaranteeing the authenticity and validity of demo01's "application requirements description document."

[0078] The edge computing device downloads demo01, which carries an "application requirements description file," from the designated device on the edge computing platform. After verifying the validity of the "application requirements description file" of demo01 through the target authorization certificate, the local platform of the edge computing device prepares the corresponding data format according to the read and write requirements of the input and output data in the application requirements description file corresponding to the application. For example, it prepares JSON format and accurate files as data carriers for demo01.

[0079] Demo01 runs periodically with a 100ms cycle. It reads current wind speed and yaw angle from a file in JSON format, processes the data, and transmits the resulting decision information (whether to shut down) in JSON format to a designated data destination. When a target application needs to read the current wind speed, if both demo01 and other target applications require it, the current wind speed is retrieved from the database all at once and written to a file in JSON format and to its corresponding standard data carrier in its respective standard data format. This improves system processing efficiency.

[0080] If there are any changes, the corresponding data targets in Table 2 will be updated, and the edge computing platform will then uniformly complete their respective actions (such as sending a shutdown command).

[0081] The designated device on the edge computing platform calculates data traffic and resource consumption based on the resource usage information, authorization requirements, and authorization period recorded in the "Application Requirements Description File" of demo01 to obtain authorization settlement information. This information is then used to charge Company A the application operating costs corresponding to the new authorization period. All items are open and transparent. Furthermore, if demo01 is deregistered, the authorization requirement settlement information is determined based on the resource usage information and authorization requirements recorded in the application requirements description file, and the duration between the last authorization requirement settlement time and the time of deregistration of the target application. Additionally, to prevent the application requirements description from consuming excessive resources, one implementation method is to settle accounts at a fixed fee. Here, the authorization requirement settlement information is a fixed value, such as the monthly APP operation fee and usage fee charged by Company A to User B being a fixed value. Even if the edge computing device undergoes two major upgrades and Company A updates demo01 once, because the standard template defined in the "Application Requirements Description File" and the standard communication interface of demo01 remain unchanged, neither the application nor the edge computing platform is affected.

[0082] One day, user B reported to company A that demo01 was malfunctioning. Company A quickly located and fixed the internal defect by checking the input file / tmp / demo01 / in.json and the output file / tmp / demo01 / out.json of demo01, directly ruling out the possibility that the problem was with the platform interface.

[0083] The above example description is now complete.

[0084] The apparatus provided in this application is described below:

[0085] See Figure 3 , Figure 3A data access device 300 provided in this application includes:

[0086] Application download unit 301 is used to download a published target application carrying a set application requirement description file, wherein the application requirement description file records the standard data format requirement information, standard data carrier requirement information, data input information, data output information, and running cycle supported by the target application.

[0087] The data reading unit 302 is used to run the target application according to the running cycle, so as to read the input data stored in the first data format from the first data carrier through the target application, and process the read target data; wherein, the first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from the data source that matches the data input information;

[0088] The data writing unit 303 is used to transmit the processed data to be output to a specified data destination using the second data carrier in a second data format; wherein, the second data carrier is a standard data carrier corresponding to the data carrier requirement information, and the second data format is a standard data format corresponding to the data format requirement information; the data to be output is data that matches the data output information.

[0089] As an example, the application requirements description file further includes: runtime resource requirements; and a data reading unit, specifically used for: if the runtime resource requirements are met, then executing the step of running the target application according to the runtime cycle.

[0090] As one example, the target application includes applications developed and tested on electronic devices outside the platform to which the electronic device belongs.

[0091] As one embodiment, the application requirements description document contains a tamper-proof digital fingerprint; the device also includes:

[0092] The digital fingerprint verification unit is used to verify whether the target application has been tampered with through the digital fingerprint; if yes, it determines that the target application has not been tampered with and executes the step of running the target application according to the running cycle; if no, it determines that the target application has been tampered with.

[0093] As an example, after the target application is approved by the platform to which the electronic device belongs, the platform to which the electronic device belongs generates an authorization certificate for the target application. The authorization certificate is used to verify the validity of the target application and the application requirement description file when the target application is listed on the platform to which the electronic device belongs.

[0094] As one embodiment, the device further includes:

[0095] The valid authentication unit is used to perform validity authentication on the target application and the application requirement description file based on the authorization certificate carried by the target application;

[0096] The application execution unit is used to trigger the data reading form when both the validity of the target application and the validity of the application requirement description file are successfully authenticated.

[0097] As one embodiment, the device further includes: a data acquisition unit, configured to extract the same input data from the data source at once if the input data corresponding to the target application is the same as the input data corresponding to other target applications, and write the same input data into the first data carrier in the first standard data format corresponding to the target application and into the corresponding standard data carrier in the standard data format corresponding to other target applications, respectively.

[0098] As one embodiment, the application requirements description file records authorization requirements information and authorization period, and the device further includes:

[0099] A request receiving unit is configured to receive an authorization confirmation request issued by a target device; wherein the target device is a designated electronic device in the platform of the electronic device, and the authorization confirmation request includes authorization settlement information; the authorization requirement settlement information is determined by the target device based on the resource usage information, authorization requirement information, and authorization period recorded in the application requirement description file, or the duration between the time of the last authorization requirement settlement and the time of cancellation of the target application;

[0100] An information output unit is used to output authorization confirmation prompt information, which prompts for authorization confirmation operation and includes authorization request settlement information.

[0101] The authorization execution unit is used to execute the authorization confirmation operation based on the operation instruction input in response to the authorization confirmation prompt information.

[0102] Therefore, in the technical solution provided in this application embodiment, the electronic device downloads a target application carrying an application requirement description file. When running the target application, the electronic device can use the standard data carrier recorded in the application requirement description file to read data in a standard data format that matches the input data recorded therein, process the data, and transmit the processed data that matches the output data recorded therein to the designated data destination using the standard data carrier in a standard data format. Thus, this application embodiment no longer directly reads the input data from the database through the application, but writes the input data in a standard data format into a standard data carrier. This allows the target application to directly read the input data in a standard data format from the standard data carrier, eliminating the need to customize a dedicated communication interface for the target application and thus avoiding dependence on existing communication interface versions. Furthermore, since the read data matches the input data recorded in the application requirement file, only the output and input data required by the application requirement file can be obtained from the data carrier. The data access scope is clearly defined, preventing the leakage of other unnecessary data and improving data security.

[0103] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0104] The electronic device provided in this application, from a hardware perspective, can be found in the hardware architecture diagram. Figure 4 As shown, it includes a machine-readable storage medium and a processor, wherein: the machine-readable storage medium stores machine-executable instructions that can be executed by the processor; the processor is used to execute the machine-executable instructions to implement the data access operations disclosed in the above example.

[0105] The machine-readable storage medium provided in this application embodiment stores machine-executable instructions. When the machine-executable instructions are invoked and executed by a processor, the machine-executable instructions cause the processor to perform the data access operations disclosed in the above examples.

[0106] Here, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, etc. For example, a machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0107] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0108] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0109] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0110] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0111] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0112] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0113] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0114] This concludes the process. Figure 4 Description of the device shown.

[0115] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A data access method, characterized by, Applied to electronic devices, the method includes: Download the released target application carrying the defined application requirements description file, wherein the application requirements description file records the standard data format requirements, standard data carrier requirements, data input information, data output information, and operating cycle supported by the target application; the target application includes applications developed and tested on the platform to which the electronic device belongs and on electronic devices outside the platform to which it belongs; According to the stated operating cycle, the target application is run to read input data stored in a first data format from a first data carrier and process the read target data. The first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from a data source that matches the data input information. Before reading the input data stored in the first data format from the first data carrier through the target application, the process further includes: if the input data corresponding to the target application is the same as the input data corresponding to other target applications, then the same input data is extracted from the data source at once and written into the first data carrier in the first standard data format corresponding to the target application and into the corresponding standard data carrier in the standard data format corresponding to other target applications, respectively. The processed output data is transmitted to a designated data destination using a second data carrier in a second data format; wherein the second data carrier is a standard data carrier corresponding to the data carrier requirement information, and the second data format is a standard data format corresponding to the data format requirement information; the output data is data that matches the data output information.

2. The method according to claim 1, characterized in that, The application requirements description file also includes: runtime resource requirements; Running the target application according to the stated operating cycle includes: If the runtime resource requirements are met, then the step of running the target application according to the runtime cycle is executed.

3. The method according to claim 1, characterized in that, The application requirements description file contains a tamper-proof digital fingerprint; after downloading the published target application carrying the configured application requirements description file, the following is also included: The target application is verified by the digital fingerprint to determine whether it has been tampered with; if not, it is determined that the target application has not been tampered with, and the step of running the target application according to the running cycle is executed; if yes, it is determined that the target application has been tampered with.

4. The method according to claim 1, characterized in that, After the target application is approved by the platform to which the electronic device belongs, the platform to which the electronic device belongs generates an authorization certificate for the target application. The authorization certificate is used to verify the platform authorization validity of the target application and the application requirement description file when the target application is listed on the platform to which the electronic device belongs.

5. The method according to claim 3, characterized in that, After downloading the published target application carrying the defined application requirements description file, the process also includes: Based on the authorization certificate carried by the target application, the platform authorization validity is verified for the target application and the application requirements description file; If both the digital fingerprint and authorization certificate of the target application pass verification, the step of running the target application according to the stated operating cycle is determined.

6. The method according to any one of claims 1 to 5, characterized in that, The application requirements description file contains authorization requirements information and an authorization period. After downloading the published target application carrying the configured application requirements description file, the following is also included: The system receives an authorization confirmation request from a target device; wherein the target device is a designated electronic device within the platform of the electronic device, and the authorization confirmation request includes authorization settlement information; the authorization settlement information is determined by the target device based on the resource usage information, authorization requirement information, and authorization period recorded in the application requirement description file, or the duration between the last authorization requirement settlement time and the time of cancellation of the target application; Output authorization confirmation prompt information, which is used to prompt for authorization confirmation operation, and includes authorization settlement information; The authorization confirmation operation is performed based on the operation command entered in response to the authorization confirmation prompt information.

7. A data access device, characterized in that, Applied to electronic devices, the device includes: The application download unit is used to download a released target application carrying a defined application requirement description file. The application requirement description file contains information on the standard data format requirements, standard data carrier requirements, data input information, data output information, and operating cycle supported by the target application. The target application includes applications developed and tested on the platform to which the electronic device belongs and on electronic devices outside the platform. A data reading unit is configured to run the target application according to the stated operating cycle, so as to read input data stored in a first data format from a first data carrier through the target application, and process the read target data; wherein, the first data carrier is a standard data carrier corresponding to the data carrier requirement information, the first data format is a standard data format corresponding to the data format requirement information, and the input data is data obtained from the data source that matches the data input information; wherein, before reading the input data stored in the first data format from the first data carrier through the target application, the unit further includes: if the input data corresponding to the target application is the same as the input data corresponding to other target applications, then the same input data is extracted from the data source at once, and written into the first data carrier in the first standard data format corresponding to the target application and into the corresponding standard data carrier in the standard data format corresponding to other target applications respectively; The data writing unit is used to transmit the processed output data to a specified data destination using a second data carrier in a second data format; wherein, the second data carrier is a standard data carrier corresponding to the data carrier requirement information, and the second data format is a standard data format corresponding to the data format requirement information; the output data is data that matches the data output information.

8. The apparatus according to claim 7, characterized in that, The application requirements description file also includes: runtime resource requirements; and a data reading unit, specifically used for... If the runtime resource requirements are met, then the step of running the target application according to the runtime cycle is executed.

9. The apparatus according to claim 7, characterized in that, The application requirements description document records a tamper-proof digital fingerprint; the device also includes: A digital fingerprint verification unit is used to verify whether the target application has been tampered with through the digital fingerprint; if not, it is determined that the target application has not been tampered with, and the step of running the target application according to the running cycle is executed; if yes, it is determined that the target application has been tampered with.

10. The apparatus according to claim 7, characterized in that, After the target application is approved by the platform to which the electronic device belongs, the platform to which the electronic device belongs generates an authorization certificate for the target application. The authorization certificate is used to verify the platform authorization validity of the target application and the application requirement description file when the target application is listed on the platform to which the electronic device belongs.

11. The apparatus according to claim 7, characterized in that, The device also includes: The valid authentication unit is used to perform validity authentication on the target application and the application requirement description file based on the authorization certificate carried by the target application; The application execution unit is used to trigger the data reading unit when both the validity of the target application and the validity of the application requirement description file are successfully authenticated.

12. The apparatus according to claim 7, characterized in that, The device further includes a data acquisition unit, configured to extract the same input data from the data source at once if the input data corresponding to the target application is the same as the input data corresponding to other target applications, and write the same input data into the first data carrier in the first standard data format corresponding to the target application and into the corresponding standard data carrier in the standard data format corresponding to other target applications, respectively.

13. The apparatus according to any one of claims 11-12, characterized in that, The application requirements description file contains authorization requirements information and authorization period. The device also includes: A request receiving unit is configured to receive an authorization confirmation request issued by a target device; wherein the target device is a designated electronic device in the platform, and the authorization confirmation request includes authorization settlement information; the authorization settlement information is determined by the target device based on the resource usage information, authorization requirement information, and authorization period recorded in the application requirement description file; An information output unit is used to output authorization confirmation prompt information, which prompts for authorization confirmation operation and includes authorization settlement information. The authorization execution unit is used to execute the authorization confirmation operation based on the operation instruction input in response to the authorization confirmation prompt information.

14. An electronic device, characterized in that, The method includes a processor and a machine-readable storage medium storing machine-executable instructions that can be executed by the processor; the processor is configured to execute the machine-executable instructions to implement the steps of the method according to any one of claims 1-6.