Data access method and device, equipment and storage medium
By receiving and verifying data access requests in automotive electronic systems, determining the device domain number and verifying it, the problems of nuclear error access and resource isolation are solved, and the system security and stability are improved.
Patent Information
- Application Number
- CN202411273506.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-11
- Publication Date
- 2024-12-20
AI Technical Summary
The prior art cannot effectively avoid nuclear error access and realize system resource isolation in automotive electronics, resulting in insufficient security.
By receiving data access requests, the domain number corresponding to the device is determined and verification is performed based on the domain number and access verification information, ensuring that only the authorized master device can access the slave device and achieve resource isolation.
It effectively avoids incorrect access, improves resource security, realizes system resources isolation, and ensures the stability and security of automotive electronic systems.
Smart Images
Figure CN119167397A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a data access method, device, equipment and storage medium. Background Art
[0002] With the development and popularization of automotive electronics, the requirements for the functions of automotive core control systems are constantly increasing. When many complex functions are integrated into an electronic control unit (ECU), it is necessary to fully consider the safety requirements of automotive electronics during application.
[0003] At present, the memory management unit (MMU) and memory protection unit (MPU) are often used to manage data access, but they are resource protection methods used in the core, which is slightly insufficient for the entire operating system. The above method cannot avoid the problem of A core erroneously accessing M core resources, which is prone to erroneous access and difficult to achieve system resource isolation. Summary of the invention
[0004] In view of this, the purpose of the present application is to provide a data access method, device, equipment and storage medium, which can effectively avoid erroneous access and achieve system resource isolation.
[0005] To achieve the above objectives, the present application discloses the following technical solutions:
[0006] In a first aspect, the present application provides a data access method, comprising:
[0007] Receiving a first data access request sent by a first master device, wherein the first data access request includes: verification attribute information and a slave device identifier;
[0008] Determining a domain number corresponding to the first master device;
[0009] Allocating the domain number to the first data access request to obtain a second data access request, wherein the second data access request includes: the domain number, the verification attribute information, and the slave device identifier;
[0010] Determining access verification information for the second data access request based on the slave device identification;
[0011] Verifying the second data access request based on the access verification information;
[0012] If the verification of the second data access request is successful, the second data access request is sent to the slave device, so that the first master device completes the data access to the slave device.
[0013] Optionally, the first data access request further includes: a process identifier of the first master device;
[0014] Before allocating the domain number for the first data access request, the method further includes:
[0015] The process identifier of the first master device is verified, and if the verification of the process identifier of the first master device is successful, the domain number is allocated to the first data access request.
[0016] Optionally, the method further includes: obtaining a verification identifier, and the verifying the process identifier of the first master device includes:
[0017] The process identifier of the first master device is verified according to the verification identifier.
[0018] Optionally, the method further includes:
[0019] If the verification of the second data access request fails, error access information is generated, and the error access information includes the cause of the error.
[0020] Optionally, the first data access request further includes: a first master device identifier;
[0021] The determining the domain number corresponding to the first master device includes: determining the domain number corresponding to the first master device according to the first master device identifier.
[0022] Optionally, the first data access request further includes: a data access type; wherein the data access type includes a read request and / or a write request;
[0023] Then, determining the access verification information for the second data access request based on the slave device identification includes: determining the access verification information for the second data access request based on the data access type and the slave device identification.
[0024] Optionally, when the data access type is a write request, the first data access request further includes write information; and the method further includes:
[0025] When the first master device writes write information to the slave device, a lock flag is generated, and the lock flag is used to reject a third data access request sent by the second master device. The data access type of the third data access request is a write type, and the domain number corresponding to the first master device is different from the domain number corresponding to the second master device.
[0026] In a second aspect, the present application provides a data access device, comprising:
[0027] A receiving unit, configured to receive a first data access request sent by a first master device, wherein the first data access request includes: verification attribute information and a slave device identifier;
[0028] A determining unit, configured to determine a domain number corresponding to the first master device;
[0029] an allocating unit, configured to allocate the domain number to the first data access request to obtain a second data access request, wherein the second data access request includes: the domain number, the verification attribute information, and the slave device identifier;
[0030] The determining unit is further configured to determine access verification information for the second data access request based on the slave device identifier;
[0031] a verification unit, configured to verify the second data access request based on the access verification information;
[0032] A sending unit is used to send the second data access request to the slave device if the verification of the second data access request is passed, so that the first master device completes the data access to the slave device.
[0033] In a third aspect, the present application provides a data access device, including:
[0034] Memory for storing computer programs;
[0035] A processor is used to execute the computer program stored in the memory to implement the steps of the data access method provided in the first aspect.
[0036] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the steps of the data access method provided in the first aspect.
[0037] The present application provides a data access method, apparatus, device and storage medium. In a data access method, a first data access request sent by a first master device is received, and a domain number corresponding to the first master device is determined; a domain number is assigned to the first data access request to obtain a second data access request, and the second data access request includes: a domain number, verification attribute information and a slave device identifier; based on the slave device identifier, access verification information for the second data access request is determined; based on the access verification information, the second data access request is verified; if the verification of the second data access request is passed, the second data access request is sent to the slave device so that the master device completes the data access to the slave device. Based on the above method, by adding a domain number for subsequent verification, the slave device can only be accessed by the master device with the specified domain number, which can effectively avoid erroneous access, improve resource security, and achieve system resource isolation. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0039] Figure 1 It is a flowchart of a data access method provided by an embodiment of the present application;
[0040] Figure 2 is a schematic diagram of access verification information provided by an embodiment of the present application;
[0041] Figure 3 It is a structural diagram of a data access system provided in an embodiment of the present application;
[0042] Figure 4 is a structural diagram of another data access system provided in an embodiment of the present application;
[0043] Figure 5 It is a schematic diagram of the structure of a data access device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0044] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0045] To facilitate understanding of the technical solution provided by the present application, a data access method provided by the present application will be described below in conjunction with the accompanying drawings. Figure 1 , which is a flow chart of a data access method provided by an embodiment of the present application, such as Figure 1 As shown, the method includes S101-S106.
[0046] S101: Receive a first data access request sent by a first master device, where the first data access request includes: verification attribute information and a slave device identifier.
[0047] In the embodiment of the present application, the master device needs to perform read / write operations on the slave device, thereby realizing resource access to the slave device, and the first master device refers to a device that can access the slave device. As an example, the master device can be any of the following, such as the core of a chip, an Advanced High Performance Bus (AHB), a high-speed serial computer expansion bus (peripheral component interconnect express, PCIE) and other buses, and a direct memory access (Data Memory Access, DMA) controller and an interrupt controller.
[0048] The slave device identification is used to indicate which slave device's resources the first data access request needs to access. The present application does not limit the specific content of the slave device identification. As an example, the slave device identification includes the address information of the slave device. The present application does not limit the specific content of the slave device. The slave device can be a peripheral device, memory, etc.
[0049] It is understandable that the verification attribute information can be used to verify the master device. This application does not limit the specific content of the verification attribute information. As an example, the verification attribute information includes: security attributes and privileged attributes; the security attribute refers to whether the master device has a secure access to the reading and writing of the slave device, which is divided into secure access and unsecure access. The privileged attribute refers to whether the current host is in privileged mode or user mode. The privileged mode has greater hardware operation permissions than the user mode. This application can set different access rights for different master devices under different verification attribute information for the same slave device, so as to perform verification. The specific verification process is described below.
[0050] The present application does not limit the specific content of the first data access request. In addition to the verification attribute information and the slave device identification, the first data access request may also include the master device identification, data access type, read-write information, etc. It can be understood that the master device identification is used to uniquely identify the master device, and the data access type includes a read request and / or a write request, which is used to identify whether the request is a read operation and / or a write operation. The read-write information includes read information and / or write information, which is used to indicate the content to be read and / or written in this request.
[0051] S102: Determine a domain number corresponding to the first master device.
[0052] After receiving the first data access request sent by the first master device, the present application can directly determine the domain number corresponding to the first master device, where the domain number refers to an identifier of the domain where the master device is located.
[0053] The present application does not limit the specific method of determining the domain number corresponding to the first master device, as an example, when the first data access request also includes: the first master device identifier. Then S102 determines the domain number corresponding to the first master device, including: determining the domain number corresponding to the first master device according to the first master device identifier.
[0054] It is understandable that the present application can pre-set the correspondence between the first master device identifier and the domain number of the master device, so that when the first data access request is obtained, the domain number corresponding to the first master device can be quickly and accurately determined, thereby improving subsequent verification efficiency.
[0055] S103: Allocate a domain number for the first data access request to obtain a second data access request, where the second data access request includes: a domain number, verification attribute information, and a slave device identifier.
[0056] In the embodiment of the present application, after obtaining the first data access request and the domain number corresponding to the first master device, the domain number can be allocated to the first data access request and the domain number can be added to the first data access request.
[0057] It can be understood that the present application adds the domain number to the first data access request, so that the second data access request includes not only the data possessed by the first data access request recorded above, but also the domain number, that is, the second data access request can include not only the domain number, verification attribute information and slave device identification, but also the master device identification, data access type, and read and write information.
[0058] S104: Determine access verification information for the second data access request based on the slave device identification.
[0059] In the embodiment of the present application, the corresponding access verification information is pre-set for different slave devices. The access verification information of the slave device can be used to verify the data access request for accessing the slave device.
[0060] This application does not limit the specific content of the access verification information. The access verification information of this application corresponds to the domain number and the content of the verification attribute information.
[0061] As a possible implementation method, when the first data access request also includes: a data access type; wherein the data access type includes a read request and / or a write request, access verification information for the second data access request is determined based on a slave device identifier, including: determining access verification information for the second data access request based on the data access type and the slave device identifier.
[0062] In the embodiment of the present application, when the first data access request further includes: data access type, the access verification information in the present application can also be set for the data access type. As an example, Figure 2 As shown, Figure 2 A schematic diagram of access verification information provided for an embodiment of the present application, it can be understood that the access verification information is set for verification attribute information including data access type, security attributes and privilege attributes. Figure 2 Pollcy represents different policy configurations, which are used to correspond to different domain numbers and to determine the access rights in different Domains. Secure represents secure access, Nonsecure represents non-secure access, Priv represents privileged mode, and User represents user mode. r represents read permission, w represents write permission, and none represents neither read permission nor write permission. It can be understood that the access verification information for the second data access request is determined based on the data access type and the slave device identification, which can effectively distinguish between read requests and write requests and better manage system resources.
[0063] Of course, the present application is not limited to this, and the present application may not distinguish between read and write operations, and only set whether there is operation permission.
[0064] S105: Verify the second data access request based on the access verification information.
[0065] In the embodiment of the present application, after obtaining the access verification information, the second data access request can be verified.
[0066] S106: If the verification of the second data access request is successful, the second data access request is sent to the slave device, so that the master device completes the data access to the slave device.
[0067] In the embodiment of the present application, if it is determined that the access authorization information satisfies the access authorization of the second data access request, it is determined that the verification of the second data access request is passed, and the second data access request is sent to the slave device so that the master device completes the data access to the slave device. If it is determined that the access authorization information does not satisfy the access authorization of the second data access request, it is determined that the verification of the second data access request is not passed, and the access of the second data access request is terminated.
[0068] This application is Figure 2 Taking the access verification information provided as an example, assuming that the domain number carried by the second data access is 001, and the verification attribute information includes: security access and privileged mode, the present application can determine the permission of the second data access request through the access verification information: there is read permission, thereby verifying the second data access request. If the second data access request is a read request, it is determined that the verification of the second data access request is passed, and the second data access request is sent to the slave device so that the master device completes the data access to the slave device. If the second data access request is a write request, it is determined that the verification of the second data access request is not passed, and the access of the second data access request is terminated.
[0069] Based on the above method, by adding the domain number for subsequent verification, the slave device can only be accessed by the specified master device. For example, the A core and the M core can be placed in two different domains, and the resources of the domain where the M core is located cannot be accessed by the A core, so as to achieve the purpose of isolating the resources of the A core and the M core. It can effectively avoid erroneous access, improve the security of resources, and realize system resource isolation. The present application can be applied to the processor to realize the resource isolation of processing, such as realizing the processor resource isolation of S32G. In addition, the present application can also divide the resources into smaller granularity and protect the memory address more specifically.
[0070] As a possible implementation method, the first data access request also includes: the process identifier of the first master device; then before S102 allocates a domain number to the first data access request, a data access method provided in the present application also includes: verifying the process identifier of the first master device, and if the verification of the process identifier of the first master device is passed, allocating a domain number to the first data access request.
[0071] It is understandable that there can be multiple master devices in a domain, and a master device can be used by multiple software processes. This application also needs to verify the process identifier of the first master device. After the verification is passed, a domain number is assigned to the first data access request to carry out the subsequent transmission process. If the verification fails, the transmission of the first data access request is terminated.
[0072] The present application does not limit the specific method of verifying the process identifier of the first master device. As an example, a data access method provided by the present application also includes: obtaining a verification identifier, then verifying the process identifier of the first master device, including: verifying the process identifier of the first master device according to the verification identifier.
[0073] It is understandable that the present application may pre-set a verification identifier that meets the requirements. As an example, the present application may originally set the verification identifier so that the verification identifier and the verification identifier satisfy the following formula, and then determine that the verification of the process identifier of the first master device is passed:
[0074] PID_Master&~PID_Mask==PID[id]&~PID_Mask, wherein PID_Master represents the verification identifier, PID_Mask represents the mask, PID[id] represents the process identifier of the first master device, and &~ represents first performing bitwise inversion and then performing a bitwise AND operation.
[0075] This application pre-sets verification identifiers that meet the requirements, so as to perform verification on different process identifiers. Only the process identifiers corresponding to the process identifiers that meet the requirements proceed to the subsequent steps, thereby achieving the goal that some of the multiple software processes running on the same host cannot access the slave device, thereby better realizing the system's resource security management.
[0076] As a possible implementation method, if S105 fails to verify the second data access request in the step of verifying the second data access request based on the access verification information, a data access method provided by the present application also includes: if the verification of the second data access request fails, generating error access information, and the error access information includes the cause of the error.
[0077] In the embodiment of the present application, after determining that the verification of the second data access request fails, the error cause is also determined, and error access information is generated. The present application does not limit the specific content of the error cause, and the error cause may be, for example, the domain number of the master device initiating the access is incorrect to access the slave device without permission, the access type of the master device does not match the permission type allowed by the slave device, etc.
[0078] This application can be used to generate error access information to remind users of the cause of the error, thereby effectively reducing the occurrence of error access.
[0079] As a possible implementation, when the data access type is a write request, the first data access request also includes write information; then in S106, enabling the first master device to complete the data access to the slave device includes: enabling the first master device to write the write information to the slave device; a data access method provided by the present application also includes:
[0080] When the first master device writes write information to the slave device, a lock flag is generated. The lock flag is used to reject the third data access request sent by the second master device. The data access type of the third data access request is a write type, and the domain number corresponding to the first master device is different from the domain number corresponding to the second master device.
[0081] In an embodiment of the present application, the first data access request also includes write information, so that the second data access request with the domain number added also includes write information. After the second data access request is verified, the present application generates a lock mark when writing the write information to the slave device, and the lock mark is used to reject the third data access request sent by the second master device. The second master device and the first master device belong to different domains.
[0082] It is understandable that the present application sets a lock flag so that when the first master device performs a write operation on a certain address, the second master device of other domains will not be allowed to perform a write operation on this address, even if the other domains also have read and write permissions to this address. As a possible implementation method, the lock flag can also temporarily and dynamically modify the permissions of other domains to read-only permissions to avoid confusion when two domains that have write permissions to the same address perform write operations on the address at the same time.
[0083] See also Figure 3 and Figure 4 , Figure 3 A structural diagram of a data access system provided for an embodiment of the present application. It can be understood that a data access method provided by the present application can be applied to the data access system, and the data access system may include a domain allocation control unit, a memory control unit, a peripheral control unit and a switch.
[0084] In the embodiment of the present application, the slave device is divided into a memory slave device (Salve memory) and a peripheral slave device (Salve peripheral), and the domain allocation control unit is used to intercept the first data access request issued by the corresponding master device, and allocate the corresponding domain number allocated to the request, obtain the second data access request, and send the newly generated second data access request and the security attributes and privilege attributes carried by the request to the bus, and send the request to the memory control unit or the peripheral control unit through the switch. The memory control unit intercepts the second data access request for accessing the corresponding memory, and evaluates and verifies the second data access request, compares the domain number, security attributes, and privilege attributes of the second data access request, thereby intercepting the second data access request that does not match the set access rights. The peripheral control unit intercepts the second data access request for accessing the corresponding peripheral, and verifies this request, compares the domain number, security attributes, and privilege attributes of the request, thereby intercepting the second data access request that does not match the access rights. The specific verification method is the same as above, and will not be repeated here.
[0085] like Figure 4 As shown, Figure 4 A schematic diagram of the structure of another data access system provided in an embodiment of the present application, Figure 4 It is also shown that the data access system of the present application may also include: an information storage unit and an error protection unit. The error protection unit can generate error access information when the verification of the second data access request fails, and can quickly determine the cause of the error, locate the domain where the error occurred and the type of error, so as to remind the user of the cause of the error and effectively reduce the occurrence of error access. The information storage unit can store the access verification information set by each slave device, so that the access verification information of the corresponding slave device can be taken out from the information storage unit for verification.
[0086] See also Figure 5 , Figure 5 A schematic diagram of the structure of a data access device provided by an embodiment of the present invention, the device comprises a receiving unit 501, a determining unit 502, an allocating unit 503, a verifying unit 504 and a sending unit 505.
[0087] A receiving unit 501 is configured to receive a first data access request sent by a first master device, wherein the first data access request includes: verification attribute information and a slave device identifier;
[0088] A determining unit 502, configured to determine a domain number corresponding to the first master device;
[0089] An allocating unit 503 is configured to allocate the domain number to the first data access request to obtain a second data access request, wherein the second data access request includes: the domain number, the verification attribute information, and the slave device identifier;
[0090] The determining unit 502 is further configured to determine access verification information for the second data access request based on the slave device identifier;
[0091] A verification unit 504, configured to verify the second data access request based on the access verification information;
[0092] The sending unit 505 is configured to send the second data access request to the slave device if the verification of the second data access request is successful, so that the first master device completes the data access to the slave device.
[0093] As a possible implementation manner, the first data access request further includes: a process identifier of the first master device;
[0094] The verification unit is further used to verify the process identifier of the first master device;
[0095] The allocation unit is further configured to allocate the domain number to the first data access request if the verification of the process identifier of the first master device is successful.
[0096] As a possible implementation, the acquisition unit is further used to acquire a verification identifier;
[0097] The verification unit is specifically configured to verify the process identifier of the first master device according to the verification identifier.
[0098] As a possible implementation manner, the device further includes:
[0099] A generating unit is configured to generate error access information if the verification of the second data access request fails, wherein the error access information includes an error cause.
[0100] As a possible implementation manner, the first data access request further includes: a first master device identifier;
[0101] The determining unit is further configured to determine a domain number corresponding to the first master device according to the first master device identifier.
[0102] As a possible implementation, the first data access request further includes: a data access type; wherein the data access type includes a read request and / or a write request;
[0103] The determining unit is specifically configured to determine access verification information for the second data access request based on the data access type and the slave device identifier.
[0104] As a possible implementation, when the data access type is a write request, the first data access request also includes write information; the sending unit is further used to: send the second data access request to the slave device, so that the first master device writes the write information into the slave device;
[0105] The device also includes:
[0106] The generation unit is also used to generate a lock flag when the first master device writes write information to the slave device, and the lock flag is used to reject a third data access request sent by the second master device, the data access type of the third data access request is a write type, and the domain number corresponding to the first master device is different from the domain number corresponding to the second master device.
[0107] The present application also provides a data access device, which may include a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps provided in the above embodiment may be implemented. Of course, the terminal may also include various network interfaces, power supplies and other components.
[0108] It should be noted that a data access device provided in an embodiment of the present application has the technical effects of any of the above embodiments, and the embodiments of the present application are not described in detail here.
[0109] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed, the steps provided in the above embodiment can be implemented. The storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.
[0110] It should be noted that a computer-readable storage medium provided in an embodiment of the present application has the technical effects of any of the above embodiments, and the embodiments of the present application are not described in detail here.
[0111] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0112] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0113] Specific examples are used herein to illustrate the principles and implementation methods of the present application, and the description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.
Claims
1. A data access method, It is characterized in that The method comprises: Receiving a first data access request sent by a first master device, wherein the first data access request includes: verification attribute information and a slave device identifier; Determining a domain number corresponding to the first master device; Allocating the domain number to the first data access request to obtain a second data access request, wherein the second data access request includes: the domain number, the verification attribute information, and the slave device identifier; Determining access verification information for the second data access request based on the slave device identification; Verifying the second data access request based on the access verification information; If the verification of the second data access request is successful, the second data access request is sent to the slave device, so that the first master device completes the data access to the slave device.
2. The method according to claim 1, It is characterized in that The first data access request also includes: a process identifier of the first master device; Before allocating the domain number for the first data access request, the method further includes: The process identifier of the first master device is verified, and if the verification of the process identifier of the first master device is successful, the domain number is allocated to the first data access request.
3. The method according to claim 2, It is characterized in that The method further includes: obtaining a verification identifier, and then verifying the process identifier of the first master device includes: The process identifier of the first master device is verified according to the verification identifier.
4. The method according to claim 1, It is characterized in that The method further comprises: If the verification of the second data access request fails, error access information is generated, and the error access information includes the cause of the error.
5. The method according to claim 1, It is characterized in that The first data access request also includes: a first master device identifier; The determining the domain number corresponding to the first master device includes: determining the domain number corresponding to the first master device according to the first master device identifier.
6. The method according to claim 1, It is characterized in that The first data access request further includes: a data access type; wherein the data access type includes a read request and / or a write request; Then, determining the access verification information for the second data access request based on the slave device identification includes: determining the access verification information for the second data access request based on the data access type and the slave device identification.
7. The method according to claim 1, It is characterized in that When the data access type is a write request, the first data access request further includes write information; The step of enabling the first master device to complete the data access to the slave device includes: enabling the first master device to write the write information into the slave device; The method further comprises: When the first master device writes the write information to the slave device, a lock flag is generated, and the lock flag is used to reject a third data access request sent by the second master device. The data access type of the third data access request is a write type, and the domain number corresponding to the first master device is different from the domain number corresponding to the second master device.
8. A data access device, It is characterized in that The device comprises: A receiving unit, configured to receive a first data access request sent by a first master device, wherein the first data access request includes: verification attribute information and a slave device identifier; A determining unit, configured to determine a domain number corresponding to the first master device; an allocating unit, configured to allocate the domain number to the first data access request to obtain a second data access request, wherein the second data access request includes: the domain number, the verification attribute information, and the slave device identifier; The determining unit is further configured to determine access verification information for the second data access request based on the slave device identifier; a verification unit, configured to verify the second data access request based on the access verification information; A sending unit is used to send the second data access request to the slave device if the verification of the second data access request is passed, so that the first master device completes the data access to the slave device.
9. A data access device, It is characterized in that include: Memory for storing computer programs; A processor, configured to execute the computer program stored in the memory to implement the steps of the data access method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, It is characterized in that The computer program is executed by a processor to implement the steps of the data access method according to any one of claims 1 to 7.