Memory read-write method, intelligent terminal and storage medium
By introducing permission verification and security checks into memory read and write methods, ensuring that virtual memory addresses are mapped to physical memory addresses and performing secure read and write operations, the memory read and write methods in the prior art cannot effectively protect data and privacy information. Problem, achieving higher memory access security.
Patent Information
- Application Number
- CN202411195749.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-28
- Publication Date
- 2025-02-07
AI Technical Summary
The memory reading and writing methods of existing electronic products lack the necessary permission verification and security checks, and cannot effectively ensure the security of data access to each application and the protection of privacy information.
Provides a memory reading and writing method, including receiving memory access requests sent by an application, performing permission verification and security checks, mapping virtual memory addresses to physical memory addresses in response to passed requests, and using physical memory addresses to read or write to memory data.
Through permission verification and security checks, we ensure the legality and security of memory access requests, effectively protect application data and privacy information, and improve the security of memory access.
Smart Images
Figure CN119397585A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a memory reading and writing method, a smart terminal and a storage medium. Background Art
[0002] Nowadays, there are endless electronic products on the market, and people's dependence on electronic products is also increasing. In the daily use of electronic products, especially smart phones, memory reading and writing are particularly important.
[0003] However, existing memory reading and writing methods for electronic products usually lack the necessary permission verification and security checks, and thus cannot effectively guarantee the security of data access by each application and the protection of privacy information. Summary of the invention
[0004] The main technical problem solved by the present application is to provide a memory reading and writing method, an intelligent terminal and a storage medium to solve the problem that the memory reading and writing method in the prior art cannot effectively guarantee the security of data access of each application and the protection of privacy information.
[0005] In order to solve the above problems, the first aspect of the present application provides a memory reading and writing method, wherein the memory reading and writing method includes: receiving a memory access request sent by an application; performing permission verification and security check on the memory access request; in response to passing the permission verification and security check, mapping the virtual memory address of the memory access request to a physical memory address; and reading or writing memory data using the physical memory address.
[0006] The steps of performing permission verification and security check on the memory access request include: detecting whether the application has permission to access the specified memory area; and in response to the application having permission to access the specified memory area, detecting whether the memory access request violates the system security policy.
[0007] The step of mapping the virtual memory address of the memory access request to the physical memory address includes: mapping the virtual memory address of the memory access request to the physical memory address by looking up a page table data structure.
[0008] Among them, after the step of reading or writing memory data using the physical memory address, it also includes: detecting whether there is an abnormality in the current memory reading or memory writing; in response to the abnormality in the current memory reading or memory writing, performing abnormal management response processing.
[0009] The steps of performing exception management response processing include: terminating the memory access request and recording the error information, or eliminating the memory access violation and page fault exception.
[0010] After the step of reading or writing memory data using the physical memory address, the method further includes: returning the currently read memory data to the application program so that the application program processes the data and displays the result.
[0011] In order to solve the above problems, the second aspect of the present application provides a memory reading and writing method, wherein the memory reading and writing method includes: issuing a memory access request to the operating system so that the operating system performs permission verification and security check on the memory access request, and when the permission verification and security check pass, mapping the virtual memory address of the memory access request to a physical memory address; using the physical memory address to read or write memory data.
[0012] After the step of reading or writing memory data using the physical memory address, the method further includes: receiving memory data returned by the operating system; processing the memory data and displaying the result.
[0013] In order to solve the above problems, the third aspect of the present application provides an intelligent terminal, wherein the intelligent terminal includes a memory and a processor coupled to each other, and the processor is used to execute program instructions stored in the memory to implement the memory reading and writing method as described in any of the above items.
[0014] In order to solve the above problems, the fourth aspect of the present application provides a computer-readable storage medium on which program instructions are stored. When the program instructions are executed by a processor, the memory reading and writing method as described in any of the above items is implemented.
[0015] The beneficial effect of the present invention is as follows: Different from the prior art, the memory reading and writing method of the present application, when receiving a memory access request sent by an application, performs permission verification and security checks on the memory access request, so that when the permission verification and security checks pass, the virtual memory address of the memory access request is mapped to a physical memory address, and the physical memory address is used to read or write memory data, thereby effectively ensuring the security of data access of each application and the protection of privacy information. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 It is a flowchart of the first embodiment of the memory reading and writing method of the present application;
[0017] Figure 2 It is a flowchart of the second embodiment of the memory reading and writing method of the present application;
[0018] Figure 3 It is a flowchart of the third embodiment of the memory reading and writing method of the present application;
[0019] Figure 4 It is a flowchart of the fourth embodiment of the memory reading and writing method of the present application;
[0020] Figure 5It is a flowchart of the fifth embodiment of the memory reading and writing method of the present application;
[0021] Figure 6 It is a schematic diagram of the framework of an embodiment of the intelligent terminal of the present application;
[0022] Figure 7 It is a schematic diagram of a framework of an embodiment of a computer-readable storage medium of the present application. DETAILED DESCRIPTION
[0023] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0024] The terms "first", "second" and "third" in this application are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first", "second" and "third" can explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "multiple" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined. All directional indications (such as up, down, left, right, front, back...) in the implementation mode of this application are only used to explain the relative position relationship, movement, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication also changes accordingly. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.
[0025] Reference to "embodiment" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0026] The present application is described in detail below with reference to the accompanying drawings and implementation methods.
[0027] See also Figure 1 , Figure 1 This is a flowchart of the first embodiment of the memory reading and writing method of the present application. Specifically, it may include the following steps:
[0028] S11: receiving a memory access request sent by an application.
[0029] The memory reading and writing process describes a key part of memory management in the operating system, which is usually managed by the MMU (Memory Management Unit) or virtual memory subsystem in the operating system kernel, or implemented by the reading and writing program auxiliary tools embedded in the operating system kernel. The operating system can be understood as a built-in program that cooperates with various hardware of the computer to interact with the user.
[0030] Specifically, the operating system or the reading and writing program auxiliary tool receives a memory access request sent by an application program.
[0031] It is worth noting that when an application needs to access memory, it will issue a request to read or write memory, which is usually implemented by calling the API (Application Programming Interface) provided by the operating system. The application will specify the memory address and amount of data to be read or written. Since applications run in user space, they cannot directly access physical memory, so all memory access requests need to be forwarded through the operating system kernel.
[0032] In addition, the API is a set of predefined functions that aims to provide applications and developers with the ability to access a set of routines based on certain software or hardware without having to access the source code or understand the details of the internal working mechanism.
[0033] S12: Perform permission verification and security check on the memory access request.
[0034] Furthermore, permission verification and security checks are performed on each memory access request to ensure that the application does not access memory areas beyond its permission range. This includes checking whether the requested memory address is within the application's address space, whether the access type (read or write) is allowed, and checking whether the application initiating the request has sufficient permissions to access the specified memory area and ensuring that the request does not violate the system's security policy.
[0035] It is worth mentioning that system security policy is a set of rules and measures to ensure the security of computer systems and their data. These policies are designed to protect systems from unauthorized access and potential attacks by limiting access to system resources, monitoring potential security threats, and implementing necessary access controls. The following are some key aspects of system security policy:
[0036] Precise matching conditions: When configuring security policies, try to avoid using overly broad matching conditions. Instead, try to limit them to specific IP (Internet Protocol) addresses and services to reduce potential security risks.
[0037] Time limit for temporary security policies: Setting a time period for temporary security policies is an important security practice. For example, when a third-party partner needs to access a service, in addition to limiting access to specific destination IP addresses and services, you should also set a time period for the security policy to take effect. After the cooperation ends, the security policy automatically becomes invalid, which helps reduce the security risks caused by long-term opening of unnecessary access rights.
[0038] Pay attention to the direction of security policy: When configuring security devices such as firewalls, you should pay attention to the direction of security policy. The stateful inspection firewall only needs to allow the active initiator of the service to establish a connection, and the return traffic can pass smoothly.
[0039] Regularly update and review security policies: Administrators or users should regularly update and review security policies to adapt to the ever-changing security environment and threats. This includes timely updating of operating system updates and patches, updating of antivirus software virus databases, regular inspection and update of network security measures, etc.
[0040] By implementing these policies and practices, you can significantly improve the security of your system and protect user data from unauthorized access and potential attacks.
[0041] S13: In response to the permission verification and security check passing, the virtual memory address of the memory access request is mapped to a physical memory address.
[0042] If the current permission verification and security check pass, the virtual memory address of the memory access request is mapped and converted into a physical memory address. This process involves querying the page table, which records the mapping relationship between virtual addresses and physical addresses. The MMU uses part of the virtual address as an index to find the page table entry to obtain the corresponding physical address.
[0043] S14: Read or write memory data using the physical memory address.
[0044] After obtaining the physical address, the physical memory can be directly accessed to perform read or write operations. This is usually achieved through DMA (Direct Memory Access) or other hardware mechanisms to ensure efficient data transfer.
[0045] The read operation is to obtain data from the physical memory and return it to the application, while the write operation is to write data to a specified location in the physical memory. The entire process ensures the security and isolation of memory access, preventing one application from mistakenly modifying the data of another application or accessing the kernel space of the operating system. In addition, virtual memory technology also allows the operating system to run multiple applications simultaneously when the physical memory is limited, and to achieve efficient use of memory by exchanging pages to disk.
[0046] The above solution performs permission verification and security checks on memory access requests, so that memory data can be read or written when the permission verification and security checks pass, effectively ensuring the security of data access by each application and the protection of privacy information.
[0047] Furthermore, in one embodiment, the above S13 may specifically include: mapping the virtual memory address of the memory access request to the physical memory address by looking up the page table data structure.
[0048] It is worth mentioning that the page table is a special data structure used to store the correspondence between logical pages and physical page frames. Each process has its own page table, which is stored in the page table area of the system space. The page table is essentially a physical memory page and can be regarded as an array, in which the elements are PTEs (Page Table Entry). Each PTE is specifically used to store the starting address of the physical memory page mapped behind the virtual page. This data structure allows the operating system to implement virtual memory management. Through the page table, the logical address can be converted into a physical address, thereby realizing the dynamic expansion and exchange of memory.
[0049] In computer systems, the design and implementation of page tables are crucial for memory management, and are used to store physical addresses and corresponding access permissions. Each level of page table occupies a physical page (4KB) in physical memory and contains multiple page table entries, each of which points to a physical page frame. This multi-level page table design allows for more flexible memory management while optimizing the efficiency of memory access.
[0050] In addition, page table lookups and operations are implemented through specific functions and algorithms. Given a virtual memory address, the kernel extracts the offset within the page table and the starting address of the page table, and then calculates the PTE corresponding to the virtual memory address in the page table. This lookup process is part of the MMU, which ensures that the operating system can efficiently and accurately access data in the virtual address space.
[0051] In addition, the process of mapping virtual memory addresses to physical memory addresses involves multiple steps and components, including MMU, page tables, TLB (Translation Lookaside Buffer), etc.
[0052] The virtual address is converted between the physical address and the virtual address through the MMU. Each process has a page table, which maps the page number and the frame number. The frame number is queried through the page number, and the CPU determines whether the current frame number is accessed out of bounds. If so, an interrupt occurs; otherwise, the physical address is calculated through the page offset and the frame number. In order to increase the access speed, the MMU contains a TLB. The operating system will first check the mapping between the virtual address and the physical address in the TLB. If there is a mapping relationship, it will be used directly to avoid checking the page table. Otherwise, the TLB data will be updated after querying the page table.
[0053] In addition, page fault handling is also an important part of the virtual memory to physical memory mapping process. If the corresponding page table entry of the virtual address is not loaded into the memory, or the virtual address exceeds the address space of the process, a page fault will occur. At this time, the operating system will respond to the page fault interrupt and execute the corresponding page scheduling algorithm (such as page replacement algorithm) according to the demand to load the required page into the memory and update the mapping relationship in the page table for subsequent access.
[0054] Furthermore, in one embodiment, after the above S12, the following may be specifically included: returning the currently read memory data to the application program, so that the application program processes and displays the result, so as to complete its specific function or task.
[0055] See also Figure 2 , Figure 2 This is a flow chart of the second embodiment of the memory reading and writing method of the present application. The memory reading and writing method of this embodiment is Figure 1 A flowchart of a detailed embodiment of the memory reading and writing method in FIG. 1 includes the following steps:
[0056] S21: Receive a memory access request sent by an application.
[0057] Among them, S21 and Figure 1 For details, please refer to S11 and its related text descriptions, which will not be repeated here.
[0058] S22: Detect whether the application has permission to access the specified memory area.
[0059] Specifically, when the operating system or the reading and writing program auxiliary tool receives a memory access request sent by an application, it first detects whether the application has the permission to access the specified memory area.
[0060] The specified memory area may be understood as the memory area that the memory access request is intended to access.
[0061] If the application has the permission to access the specified memory area, S23 is executed; if the application does not have the permission to access the specified memory area, S24 is executed.
[0062] S23: Detect whether the memory access request violates the system security policy.
[0063] Furthermore, it is detected whether the currently received memory access request violates the system security policy. The system security policy is a series of rules and measures to ensure the security of the computer system and its data. These policies are designed to protect the system from unauthorized access and potential attacks by limiting access to system resources, monitoring potential security threats, and implementing necessary access controls.
[0064] If the memory access request does not violate the system security policy, S25 is executed; if the application does not have the permission to access the specified memory area, S24 is executed.
[0065] S24: Deny the current access request.
[0066] It is understandable that when it is determined that the current memory access request does not have permission to access the specified memory area and / or violates the system security policy, the current access request is rejected and the memory access request is deleted, or a reminder message is returned to the corresponding application that it does not have permission to access the specified memory area and / or violates the system security policy.
[0067] S25: Map the virtual memory address of the memory access request to a physical memory address.
[0068] S26: Read or write memory data using the physical memory address.
[0069] Among them, S25 and S26 are Figure 1 S13 and S14 are the same. For details, please refer to S13 and S14 and their related text descriptions, which will not be repeated here.
[0070] See also Figure 3 , Figure 3 This is a flow chart of the third embodiment of the memory reading and writing method of the present application. The memory reading and writing method of this embodiment is Figure 1 A flowchart of a detailed embodiment of the memory reading and writing method in FIG. 1 includes the following steps:
[0071] S31: receiving a memory access request sent by an application.
[0072] S32: Perform permission verification and security check on the memory access request.
[0073] S33: In response to the permission verification and security check passing, the virtual memory address of the memory access request is mapped to a physical memory address.
[0074] S34: Read or write memory data using the physical memory address.
[0075] Among them, S31, S32, S33 and S34 are Figure 1 S11, S12, S13 and S14 are the same, please refer to S11, S12, S13 and S14 and their related text descriptions for details, which will not be repeated here.
[0076] S35: Detect whether there is an abnormality in the current memory reading or memory writing.
[0077] Specifically, detect whether there is an abnormality in the current memory reading or memory writing, such as whether there is a memory access violation, whether a page error occurs, etc.
[0078] If there is an exception in the current memory reading or memory writing, S36 is executed; if there is no exception in the current memory reading or memory writing, S36 is executed.
[0079] S36: Perform abnormal management response processing.
[0080] When it is determined that an exception exists in memory reading or memory writing, corresponding exception management response processing is performed according to the exception type.
[0081] S37: Return the currently read memory data to the application so that the application processes and displays the result.
[0082] The currently read memory data is returned to the application so that the application can process and display the results to complete its specific functions or tasks.
[0083] Furthermore, in one embodiment, the above S36 may specifically include: terminating the memory access request, and recording the current error information, or eliminating abnormalities such as memory access violations and page errors.
[0084] See also Figure 4 , Figure 4 This is a flowchart of the fourth embodiment of the memory reading and writing method of the present application. Specifically, it may include the following steps:
[0085] S41: a memory access request is issued to the operating system, so that the operating system performs permission verification and security check on the memory access request, and maps the virtual memory address of the memory access request to the physical memory address when the permission verification and security check pass.
[0086] Specifically, when an application needs to access memory, it sends a request to the operating system or a read-write program auxiliary tool to read or write memory. This is usually achieved by calling the API provided by the operating system. The application specifies the memory address and amount of data to be read or written. Since applications run in user space, they cannot directly access physical memory, so all memory access requests need to be forwarded through the operating system kernel.
[0087] The operating system or the reader-writer assistant will perform permission verification and security checks on each memory access request to ensure that the application does not access memory areas beyond its permission range. This includes checking whether the requested memory address is within the application's address space, whether the access type (read or write) is allowed, and checking whether the application initiating the request has sufficient permissions to access the specified memory area and ensuring that the request does not violate the system's security policy.
[0088] If the current permission verification and security check pass, the virtual memory address of the memory access request is mapped and converted into a physical memory address. This process involves querying the page table, which records the mapping relationship between virtual addresses and physical addresses. The MMU uses part of the virtual address as an index to find the page table entry to obtain the corresponding physical address.
[0089] S42: Read or write memory data using the physical memory address.
[0090] Furthermore, the application will use the physical memory address to read or write memory data through the operating system or a read-write program auxiliary tool.
[0091] The read operation is to obtain data from the physical memory and return it to the application, while the write operation is to write data to a specified location in the physical memory. The entire process ensures the security and isolation of memory access, preventing one application from mistakenly modifying the data of another application or accessing the kernel space of the operating system. In addition, virtual memory technology also allows the operating system to run multiple applications simultaneously when the physical memory is limited, and to achieve efficient use of memory by exchanging pages to disk.
[0092] See also Figure 5 , Figure 5 This is a flow chart of the fifth embodiment of the memory reading and writing method of the present application. The memory reading and writing method of this embodiment is Figure 4 A flowchart of a detailed embodiment of the memory reading and writing method in FIG. 1 includes the following steps:
[0093] S51: a memory access request is issued to the operating system, so that the operating system performs permission verification and security check on the memory access request, and maps the virtual memory address of the memory access request to a physical memory address when the permission verification and security check pass.
[0094] S52: Read or write memory data using the physical memory address.
[0095] Among them, S51 and S52 are Figure 4 S41 and S42 are the same. For details, please refer to S41 and S42 and their related text descriptions, which will not be repeated here.
[0096] S53: Receive memory data returned by the operating system.
[0097] Specifically, the application receives memory data returned by the operating system according to the memory access request.
[0098] S54: Process the memory data and display the result.
[0099] Furthermore, the currently received memory data is processed and the results are displayed to complete its specific functions or tasks.
[0100] See also Figure 6 , Figure 6 The smart terminal 61 includes a memory 611 and a processor 612 coupled to each other, and the processor 612 is used to execute program instructions stored in the memory 611 to implement the steps of any of the above memory reading and writing method embodiments.
[0101] In a specific implementation scenario, the smart terminal 61 may include, but is not limited to, any reasonable smart terminal such as a computer, a tablet computer, a smart phone, and a smart watch, and this application does not limit this.
[0102] Specifically, the processor 612 is used to control itself and the memory 611 to implement the steps of any of the above-mentioned video display method embodiments. The processor 612 can also be called a CPU (Central Processing Unit). The processor 612 may be an integrated circuit chip with signal processing capabilities. The processor 612 can also be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field-programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. In addition, the processor 612 can be implemented by an integrated circuit chip.
[0103] See also Figure 7 , Figure 7 The computer-readable storage medium 71 stores program instructions 711 that can be executed by a processor, and the program instructions 711 are used to implement the steps of any of the above-mentioned memory reading and writing method embodiments.
[0104] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.
[0105] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0106] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0107] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.
Claims
1. A memory reading and writing method, characterized in that: The memory reading and writing method comprises: Receive memory access requests sent by applications; Performing permission verification and security check on the memory access request; In response to the permission verification and the security check passing, mapping the virtual memory address of the memory access request to a physical memory address; The memory data is read or written using the physical memory address.
2. The memory reading and writing method according to claim 1, characterized in that: The step of performing permission verification and security check on the memory access request comprises: Detecting whether the application has permission to access a specified memory area; In response to the application having permission to access the designated memory area, detecting whether the memory access request violates a system security policy.
3. The memory reading and writing method according to claim 1, characterized in that: The step of mapping the virtual memory address of the memory access request to a physical memory address comprises: The virtual memory address of the memory access request is mapped to the physical memory address using a lookup page table data structure.
4. The memory reading and writing method according to claim 1, characterized in that: After the step of using the physical memory address to read or write memory data, the method further includes: Check whether there is an abnormality in the current memory reading or memory writing; In response to an exception in the current memory read or memory write, an exception management response process is performed.
5. The memory reading and writing method according to claim 1, characterized in that: The steps of performing abnormal management and response processing include: The memory access request is terminated and error information is recorded, or memory access violation and page fault exception are eliminated.
6. The memory reading and writing method according to claim 1, characterized in that: After the step of using the physical memory address to read or write memory data, the method further includes: The memory data currently read is returned to the application program so that the application program processes the data and displays the result.
7. A memory reading and writing method, characterized in that: The memory reading and writing method comprises: Sending a memory access request to an operating system so that the operating system performs permission verification and security check on the memory access request, and mapping a virtual memory address of the memory access request to a physical memory address when the permission verification and security check pass; The memory data is read or written using the physical memory address.
8. The memory reading and writing method according to claim 7, characterized in that: After the step of using the physical memory address to read or write memory data, the method further includes: Receiving the memory data returned by the operating system; The memory data is processed and the result is displayed.
9. An intelligent terminal, characterized in that: The intelligent terminal includes a memory and a processor coupled to each other, and the processor is used to execute program instructions stored in the memory to implement the memory reading and writing method according to any one of claims 1 to 6, or any one of claims 7 to 8.
10. A computer-readable storage medium having program instructions stored thereon, characterized in that: When the program instructions are executed by the processor, a memory reading and writing method as described in any one of claims 1 to 6 or any one of claims 7 to 8 is implemented.