Information acquisition method and device, card reader and storage medium

Abstract

The application discloses an information acquisition method and device, a card reader and a storage medium, relates to the technical field of storage, and is applied to the card reader. The card reader is connected with a storage card and a target device respectively. The method comprises the following steps: receiving a health query instruction sent by the target device, triggering an internal reading command sequence according to the health query instruction, wherein the reading command sequence comprises a bottom-layer command defined according to a storage protocol of the storage card, and the bottom-layer command is a command for reading health state parameters of the storage card; reading the storage card based on the reading command sequence to obtain heterogeneous health data; performing normalization processing on the heterogeneous health data to obtain standard health data, and transmitting the standard health data to the target device.

Description

Technical Field

[0001] This application relates to the field of storage technology, and in particular to an information acquisition method, apparatus, card reader and storage medium. Background Technology

[0002] Currently, in commercial digital signage scenarios (such as distributed devices mounted on walls in large shopping malls and transportation hubs), many digital signs use Secure Digital (SD) cards for storage and resource playback. Since most signs are mounted on walls on a large scale, it is particularly important to remotely monitor the health of the SD cards to see if it affects playback.

[0003] To remotely monitor the health of SD cards storing playback resources, it is necessary to obtain the health information of the SD card (such as production date, serial number, write / erase cycles, number of bad blocks, remaining lifespan, etc.). Currently, SD card health information is typically stored in registers within the SD card, such as the Card Identification Register (CID), Card Specific Data Register (CSD), and SD Configuration Register (SCR), or in the manufacturer-defined Self-Monitoring, Analysis and Reporting Technology (SMART) information area.

[0004] When an SD card is connected to a host via a Universal Serial Bus (USB) card reader, the USB protocol does not support direct access to the SD card's registers or SMART information, making it difficult to obtain the SD card's health status under the USB interface. This poses challenges for remote monitoring and preventative maintenance. Summary of the Invention

[0005] The main purpose of this application is to provide an information acquisition method, device, card reader, and storage medium, which aims to solve the technical problem that traditional card readers have difficulty in acquiring the health status of SD cards.

[0006] To achieve the above objectives, this application proposes an information acquisition method, which is applied to a card reader connected to a memory card and a target device, the method comprising: The system receives a health query command sent by the target device and triggers a built-in read command sequence according to the health query command. The read command sequence contains a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card. The memory card is read based on the read command sequence to obtain heterogeneous health data; The heterogeneous health data is normalized to obtain standard health data, and the standard health data is transmitted to the target device.

[0007] Furthermore, to achieve the above objectives, this application also proposes an information acquisition device, the device comprising: The command module is used to receive a health query command sent by the target device and trigger a built-in read command sequence according to the health query command. The read command sequence contains a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card. The reading module is used to read the memory card based on the read command sequence to obtain heterogeneous health data; A standard module is used to normalize the heterogeneous health data to obtain standard health data, and then transmit the standard health data to the target device.

[0008] In addition, to achieve the above objectives, this application also proposes a card reader, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the information acquisition method described above.

[0009] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the information acquisition method described above. Attached Figure Description

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

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating an embodiment of the information acquisition method for this application. Figure 2 A simplified connection diagram of the card reader provided in Embodiment 1 of this application; Figure 3This is an overall architecture diagram provided for Embodiment 1 of this application; Figure 4 This is an interaction timing diagram of the card reader provided in Embodiment 1 of this application; Figure 5 This is a flowchart illustrating Embodiment 2 of the information acquisition method for this application. Figure 6 This is a flowchart illustrating Embodiment 3 of the information acquisition method for this application. Figure 7 This is a block diagram of the module structure of the information acquisition device according to an embodiment of this application; Figure 8 This is a schematic diagram of the hardware operating environment involved in the card reader in the embodiments of this application.

[0013] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0014] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0015] The main solution of this application is: Currently, in commercial digital signage scenarios (such as distributed devices installed on walls in large shopping malls, transportation hubs, etc.), many digital signs use secure digital storage SD cards for storage and resource playback. Since most signs are mounted on walls on a large scale, it is particularly important to remotely monitor whether the health of the SD card affects playback.

[0016] To remotely monitor the health of SD cards storing playback resources, it is necessary to obtain the health information of the SD card (such as production date, serial number, write / erase cycles, number of bad blocks, remaining lifespan, etc.). Currently, SD card health information is usually stored in registers such as CID, CSD, and SCR inside the SD card, or in the SMART information area of ​​the manufacturer's custom self-monitoring analysis and reporting technology.

[0017] When an SD card is connected to a host via a Universal Serial Bus (USB) card reader, the USB protocol does not support direct access to the SD card's registers or SMART information, making it difficult to obtain the SD card's health status under the USB interface. This poses challenges for remote monitoring and preventative maintenance.

[0018] To address the aforementioned issues, this application provides an information acquisition method. This method is applied to a card reader connected to both a memory card and a target device. First, the card reader receives a health query command from the target device. Based on this command, the card reader triggers a built-in read command sequence containing underlying storage protocol commands. Then, based on this read command sequence, the card reader reads heterogeneous health data from the memory card. This heterogeneous health data is then normalized to obtain standard health data, which is returned to the target device. Compared to existing methods that struggle to access SD card internal registers or SMART information via USB card readers, this application can directly read SD card health status parameters at the USB link layer using a pre-built storage protocol command sequence. This effectively solves the problem of blind spots in remote monitoring caused by the difficulty in obtaining health information through the USB interface in scenarios such as commercial display digital signage.

[0019] It should be noted that the executing entity of this application embodiment can be an electronic device with data processing, network communication, and program execution functions, such as an adapter, SD-to-USB bridge, or other card reader capable of executing the information acquisition method of this application. This embodiment does not limit this. The following uses a card reader as an example to describe this embodiment and the following embodiments.

[0020] Based on this, this application proposes an information acquisition method according to the first embodiment, referring to... Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the information acquisition method of this application. In this embodiment, the information acquisition method is applied to a card reader, which is connected to both a memory card and a target device. The information acquisition method may include steps S10 to S30: Step S10: Receive a health query command sent by the target device, and trigger a built-in read command sequence according to the health query command. The read command sequence contains a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card.

[0021] It should be noted that the card reader can be a device used for protocol conversion and data transfer between the memory card and the target device, also known as an SD card to USB bridging device. The memory card can be a removable storage medium based on flash memory storage, such as an SD card, a compact flash (CF) card, an embedded multimedia card (eMMC), etc. For ease of understanding, this embodiment and the following embodiments use an SD card as an example for explanation.

[0022] It should also be noted that the target device can be an upstream device that needs to read data from the memory card or monitor the status of the memory card, such as a host, personal computer, or embedded motherboard in a commercial display digital signage system. For ease of understanding, this embodiment and the following embodiments use a host in a commercial display digital signage system as an example for illustration.

[0023] For example, refer to Figure 2 , Figure 2 This is a simplified connection diagram of the card reader provided in Embodiment 1 of this application. When the card reader executes the information acquisition method of this embodiment, the SD card is connected to the card reader through the SD interface, and the card reader is connected to the host through the USB interface.

[0024] Understandably, a health query command can be a custom command issued by the target device to request the card reader to return information about the health status of the memory card.

[0025] It is also understood that the read command sequence can be an ordered set of low-level commands pre-stored in the reader firmware. The commands in this sequence are defined according to the memory card's storage protocol and are used to read health-related parameters from various registers and private data areas within the memory card. There can be multiple read command sequences, such as reading the CID register (e.g., production date, manufacturer ID, serial number), reading the CSD register (e.g., capacity, speed class), reading the SCR register (e.g., supported function modes), and reading manufacturer-extended SMART information (e.g., write cycles, bad block count, remaining lifetime). This embodiment does not limit this.

[0026] It should be understood that health status parameters can be parameters that characterize the internal physical state and lifespan of the memory card, including but not limited to production date, serial number, number of erase / write cycles, number of bad blocks, and percentage of remaining lifespan.

[0027] Step S20: Read the memory card based on the read command sequence to obtain heterogeneous health data.

[0028] It should be noted that heterogeneous health data can refer to a collection of raw health information read from a memory card that comes from different sources and has different data formats. Because different registers and private data areas of the memory card use different data structures or encoding methods, this data exhibits structural heterogeneity. For example, the serial number in the CID register is ASCII encoded, the capacity parameter in the CSD register is a binary value with dispersed bit fields, and the number of erase / write cycles in the manufacturer's proprietary SMART information area may be a big-endian or little-endian integer value.

[0029] In practical use, refer to Figure 3 , Figure 3This is an overall architecture diagram provided for Embodiment 1 of this application. The card reader has an internal USB protocol extension. Under this extension, it maintains a connection with the target device (i.e., a commercial display digital signage) via a USB interface, and simultaneously maintains a connection with the memory card (i.e., an SD card) via a memory card protocol interface. When the target device needs to obtain the health status of the memory card, the main controller issues a health query command and sends it to the card reader via the connected USB interface. After receiving the health query command from the target device, the card reader begins to collect health data. At this time, it retrieves a pre-programmed read command sequence from its internal firmware storage area, preparing to execute the sequence to access the memory card's registers. Then, by controlling the SD protocol according to the timing requirements of the storage protocol, it sequentially sends each low-level command to the SD card. After each low-level command is sent, the memory card returns corresponding response data, and finally, the heterogeneous health data is obtained by summarizing the data.

[0030] Furthermore, in order to obtain the aforementioned heterogeneous health data, in this embodiment, the read command sequence includes a first low-level command, a second low-level command, and a third low-level command; the step of reading the memory card based on the read command sequence to obtain the heterogeneous health data includes: Step S21: Read the identification information from the card identification register of the memory card according to the first underlying command.

[0031] It should be noted that the card identifier register can be a read-only register inside the memory card, used to store data that uniquely identifies the memory card, such as manufacturer information, product name, product serial number, and production date. The first low-level command can be the low-level command in the read command sequence used to access the memory card's card identifier register. According to the memory protocol definition, this command is used to obtain the memory card's unique identification information, such as CMD10 in the SD protocol.

[0032] The first low-level command can read the identification information used to uniquely identify the memory card from the card identification register, including but not limited to manufacturer ID, original equipment manufacturer identifier (OEM ID), product name, product version, serial number, production date, etc.

[0033] Step S22: Read the specification parameters from the card-specific data register of the memory card according to the second underlying command.

[0034] Understandably, the card-specific data register can be a read-only register inside the memory card, used to store specifications and performance parameters, such as capacity, transfer rate level, data block length, and whether certain functions are supported. The second low-level command can be the low-level command in the read command sequence used to access the memory card's card-specific data register. According to the memory protocol definition, this command is used to obtain the memory card's specification parameter information, such as CMD9 in the SD protocol.

[0035] The second low-level command can be used to read the specifications that describe the physical characteristics and performance indicators of the memory card from the card's dedicated data register, including but not limited to storage capacity, speed class, maximum clock frequency, data verification method, etc.

[0036] Step S23: Based on the third underlying command, determine the private data block of the manufacturer's private area of ​​the memory card, and read the life characteristic parameters characterizing the wear level of the memory card from the private data block.

[0037] Step S24: Use the identification information, the specification parameters, and the lifespan characteristic parameters as heterogeneous health data extracted from the memory card.

[0038] It should be understood that a vendor-specific area can be a dedicated data storage region within the memory card that is not explicitly defined in the standard storage protocol and is planned and used by each memory card manufacturer. This region is typically read using vendor-defined commands and is used to store depth information beyond standard registers, such as flash write cycles, bad block lists, and SMART information such as remaining lifespan. The third-level low-level command can be the underlying command in the read command sequence used to access the vendor-specific area of ​​the memory card. This command is usually not a command uniformly defined in the standard protocol, but rather a specific command or command sequence defined by the memory card manufacturer. It is used to read deep health information in the vendor's private data blocks, such as specific commands supported by some SD card manufacturers for reading SMART information (e.g., CMD56 with specific parameters).

[0039] It is also understandable that a private data block can be a continuous data segment in the manufacturer's private area of ​​the memory card. The data block contains multiple health-related parameters according to the manufacturer's custom data structure. The format of private data blocks may be different for different manufacturers or even different models of the same manufacturer.

[0040] It should be noted that lifetime characteristic parameters can be read from private data blocks and are raw parameters used to directly or indirectly calculate the remaining lifetime of the memory card. Examples include the number of write / erase cycles already performed, the number of bad blocks generated, and the proportion of spare blocks consumed. Lifetime characteristic parameters can be used to characterize the wear and tear of the memory card; the higher the wear and tear, the shorter the remaining usable lifetime of the memory card. These parameters are typically quantified using parameters such as the number of write / erase cycles.

[0041] For example, to facilitate understanding of the above implementation process, refer to Figure 3 and Figure 4 , Figure 4 This is a timing diagram of the interaction of the card reader provided in Embodiment 1 of this application. The commercial display controller, acting as the initiator, first sends a health query request to the card reader. Upon receiving the request, the card reader autonomously switches to query takeover mode and sequentially sends low-level commands to the SD card via the SD protocol to read the CID register, CSD register, and the manufacturer-defined SMART information area, respectively. The specific process is as follows: (1) Automatically send CMD10 to switch the SD card status and read the 128-bit CID register to extract identification information such as production date and manufacturer ID.

[0042] (2) Automatically send CMD9 to read the 128-bit CSD register, extract and calculate the capacity and other specifications.

[0043] (3) Automatically issue the corresponding specific command CMD56 to read the SCR register and the manufacturer's private SMART data block to obtain lifetime characteristic parameters such as the number of physical erases and the number of bad blocks remaining.

[0044] Based on the aforementioned low-level commands from the card reader, the SD card returns the corresponding raw register data and SMART data to the card reader. After obtaining these heterogeneous health parameters, the card reader performs cleaning and normalization processing locally. After normalization, it packages the standard health data into a unified format health information data packet and returns it to the commercial display main controller via the USB interface.

[0045] Upon receiving the health information data packet, the commercial display controller immediately uploads it to the cloud monitoring platform. The cloud monitoring platform performs a health analysis based on preset thresholds (such as a total remaining lifespan below 60% or a bad block count exceeding a threshold), and returns the health analysis results or alarm information to the commercial display controller. When a severe decline in the memory card's health or impending damage is detected, the cloud monitoring platform can optionally trigger data migration or memory card replacement commands, allowing the commercial display controller to perform subsequent maintenance operations, thus forming a complete closed loop of remote monitoring and preventative maintenance.

[0046] In this embodiment, identification information is read from the card identification register according to the first underlying command, specification parameters are read from the card dedicated data register according to the second underlying command, and lifespan characteristic parameters representing the degree of wear are read from the manufacturer's private area according to the third underlying command. The identification information, specification parameters, and lifespan characteristic parameters are then used together as heterogeneous health data. Compared to the traditional pass-through method that requires the host to issue multiple commands and control the entire process, this embodiment uses a single command sequence to simultaneously cover the static identity specification information and dynamic wear and health information of the memory card. This reduces the need for multiple independent accesses and additional command interactions required due to the scattered storage of different information sources, and improves the efficiency of obtaining complete heterogeneous health data.

[0047] Step S30: Normalize the heterogeneous health data to obtain standard health data, and transmit the standard health data to the target device.

[0048] Understandably, standard health data can be a health information dataset with a predefined uniform format obtained after normalization. For example, standard health data can be a data packet of fixed byte length, where bytes 0 to 3 store the percentage of remaining lifespan, bytes 4 to 7 store the total number of bad blocks, etc. This embodiment does not impose any restrictions on this.

[0049] In practical use, after obtaining heterogeneous health data, the card reader parses each segment of raw data within the heterogeneous health data. Based on the data source (such as the CID register, CSD register, SCR register, or vendor-specific SMART area), it calls the corresponding parsing logic to clean and convert the data, uniformly transforming these parameters into a predefined format and unit. After completing the conversion of all parameters, the standardized health parameter fields are filled into a unified data structure according to a predefined order and length, forming standard health data. For example... Figure 3 As shown, the standard health data is finally returned to the main controller, which then uploads it to the cloud monitoring platform. This allows for remote centralized monitoring by obtaining SD card health information via USB interface without modifying the host's underlying system drivers. This method is widely applicable to distributed devices such as digital signage. It improves the maintainability of real-time monitoring storage devices and reduces playback abnormalities in digital signage devices caused by SD card problems.

[0050] Furthermore, in order to trigger the aforementioned read command sequence, in this embodiment, the step of receiving a health query command sent by the target device and triggering the built-in read command sequence according to the health query command includes: receiving a health query command sent by the target device through a first interface between the card reader and the target device, wherein the first interface is a Universal Serial Bus interface; detecting whether the health query command conforms to a preset aggregation command; if it conforms to the preset aggregation command, then initiating a query takeover mode; in the query takeover mode, connecting to the communication channel of the memory card through a second interface between the card reader and the memory card, wherein the second interface is a memory card protocol interface; and obtaining the built-in read command sequence after the communication channel connection is completed.

[0051] It should be noted that the first interface can be the physical and protocol interface for data communication between the card reader and the target device, used to transmit commands and data between the target device and the card reader, such as a Universal Serial Bus interface (i.e., a USB interface). The second interface can be the physical and protocol interface for data communication between the card reader and the memory card, used to transmit low-level commands and response data between the card reader and the memory card, such as a memory card protocol interface (i.e., an SD interface).

[0052] It should also be noted that the preset aggregation command can be a special format of health query command predefined in the card reader firmware. This command is different from the regular read and write commands and is used to trigger the card reader to execute an aggregated health information collection process.

[0053] Understandably, the communication channel can be a logical connection path established between the card reader and the memory card through a second interface. After the channel is established, the card reader can send low-level commands to the memory card and receive the returned data in accordance with the memory card protocol.

[0054] It is also understandable that query takeover mode can be a specific operating state of the card reader. In this state, the card reader temporarily suspends responses to regular USB read / write commands, actively takes over all low-level communication timing control with the memory card, and independently executes the subsequent health information collection process. In query takeover mode, the target device no longer participates in the sending and response processing of each low-level command; instead, the card reader autonomously completes all low-level interactions.

[0055] In this embodiment, the host sends a single health query command to the card reader via a standard USB interface. If the health query command is a custom aggregated query command, the card reader will suspend the current USB regular read / write bus according to the aggregated query command and independently take over all subsequent communication sequences with the SD card's underlying layer. The host is completely released and no longer participates in the underlying state machine transitions. Thus, by using a preset single-trigger mechanism for aggregated commands and autonomous channel management in the query takeover mode, the overhead and protocol conversion latency of the target device participating in underlying communication interactions are reduced, improving the response efficiency of health information collection and the degree of system automation.

[0056] This application provides an information acquisition method applied to a card reader connected to both a memory card and a target device. The method first receives a health query command from the target device and triggers a built-in read command sequence containing underlying storage protocol commands. Then, based on this read command sequence, the card reader reads heterogeneous health data from the memory card. This heterogeneous health data is then normalized to obtain standard health data, which is returned to the target device. Compared to existing methods that struggle to access SD card internal registers or SMART information via USB card readers, this embodiment allows direct reading of SD card health status parameters at the USB link layer via a pre-built storage protocol command sequence. This effectively solves the problem of blind spots in remote monitoring caused by the difficulty in obtaining health information through the USB interface in scenarios such as commercial display digital signage.

[0057] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to the above embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, a second embodiment of the information acquisition method of this application is proposed, please refer to... Figure 5 , Figure 5 This is a flowchart illustrating a second embodiment of the information acquisition method for this application. To obtain the aforementioned standard health data, such as... Figure 5 As shown, in this embodiment, the step of normalizing the heterogeneous health data to obtain standard health data includes: Step S31: Extract the identification information from the heterogeneous health data and match it with the pre-built manufacturer parsing feature table based on the identification information.

[0058] It should be noted that the manufacturer resolution characteristic table can be a mapping table pre-stored in the card reader firmware. This table records the correspondence between the identification characteristics of different memory card manufacturers and the corresponding resolution rules. Each entry in the table contains the manufacturer's identification information (such as manufacturer ID, OEM ID), the version number identification rule for the memory card of that manufacturer, the flash memory chip type identification rule, and various resolution parameters required for subsequent capacity calculation and lifespan conversion.

[0059] Step S32: Determine the version number and flash memory chip type of the memory card according to the manufacturer parsing feature table.

[0060] It should also be noted that the version number can be an identifier for the protocol version or specification version of the memory card, used to distinguish different generations of memory card standards. Memory cards with different version numbers may differ in terms of capacity calculation methods, command support sets, register structures, etc. For example, the version bit of the CSD register can distinguish whether the SD card is v1.0 (i.e., a standard capacity card) or v2.0 (i.e., a high capacity card).

[0061] Understandably, flash memory chip type can refer to the type of flash memory storage unit used inside a memory card. Different flash memory chip types have different physical characteristics and theoretical lifespans. Common types include single-level cell (SLC) and multi-level cell (MLC).

[0062] Step S33: Based on the heterogeneous health data, determine the standard capacity and current lifespan index of the memory card by means of the version number and the flash memory chip type.

[0063] Step S34: Determine the standard health data of the memory card based on the standard capacity and the current lifespan indicator.

[0064] It is also understandable that standard capacity can refer to the physical storage capacity of a memory card, expressed in a unified unit, after normalization.

[0065] It should be understood that the current lifetime indicator can refer to a calculated value or level used to quantitatively characterize the current remaining usable lifetime of the memory card. This current lifetime indicator can be a percentage of remaining lifetime (e.g., 0% to 100%), the absolute value of the number of erase / write cycles consumed, or an estimated number of remaining erase / write cycles; this embodiment does not limit this.

[0066] In practical use, after receiving heterogeneous health data, the card reader extracts the identification information from the heterogeneous health data and matches it against the built-in manufacturer resolution feature table. Based on this table, it determines the version number and flash memory type of the memory card. Then, based on the version number and flash memory type, it performs branching processing on the heterogeneous health data to determine the corresponding standard capacity and current lifespan indicators, ultimately generating standard health data. Compared to traditional methods that require the host or cloud to adapt the resolution logic separately for each card, this embodiment can normalize heterogeneous data through local manufacturer feature matching and branch cleaning conversion on the card reader, avoiding the highly fragmented differences in health data storage formats between different brands and specifications of SD cards on the market.

[0067] Based on the first and / or second embodiments of this application, in the third embodiment of this application, the content that is the same as or similar to that in embodiments one and two above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 6 , Figure 6 This is a flowchart illustrating Embodiment 3 of the information acquisition method for this application. To obtain the aforementioned standard capacity and current lifetime indicators, such as... Figure 6 As shown, in this embodiment, the step of determining the standard capacity and current lifespan index of the memory card based on the heterogeneous health data, through the version number and the flash memory chip type, includes: Step S331: Extract the heterogeneous health data to obtain the specifications and lifespan characteristics of the memory card.

[0068] Step S332: Detect the capacity type of the card-specific data register of the memory card according to the version number.

[0069] Understandably, capacity type can refer to the category of capacity expression methods that are distinguished according to different memory card protocol versions, mainly including two types: standard capacity card type and high capacity card type.

[0070] Step S333: Standardize the specification parameters based on the capacity type to obtain the standard capacity.

[0071] Step S334: Calculate the lifetime characteristic parameters according to the flash memory chip type to obtain the current lifetime index.

[0072] It should be noted that, since the original capacity parameter formats and calculation methods differ for different capacity types, the capacity-related information in the original specifications of the memory card can be converted into a universally applicable capacity value through standardization processing, according to unified calculation rules and units.

[0073] In this embodiment, the card reader first extracts specification parameters and lifespan characteristic parameters from heterogeneous health data. Then, it detects the capacity type of the card's dedicated data register based on the version number, and performs branching and standardization processing on the specification parameters based on the capacity type to obtain the standard capacity. Simultaneously, it converts the lifespan characteristic parameters according to the flash memory chip type to obtain the current lifespan index. Thus, through the card reader's internal automatic identification and branching calculation of capacity type, as well as adaptive lifespan conversion for flash memory chip type, the heterogeneous data cleaning work that originally required multiple interactions and complex adaptations from the host is directly completed in a local processing flow triggered by a single instruction. This improves the efficiency and accuracy of unified acquisition of health data for SD cards across versions and flash memory chip types.

[0074] Furthermore, in order to obtain the aforementioned standard capacity, in this embodiment, the step of standardizing the specification parameters based on the capacity type to obtain the standard capacity includes: Step S3331: Extract the capacity indication value, capacity multiplier value, and read block length value from the specification parameters.

[0075] Understandably, the capacity indicator value can be a binary field stored in the memory card's dedicated data register, used in capacity calculations. The meaning and calculation method of this field differ depending on the capacity type. For standard capacity cards, this field corresponds to the C_SIZE parameter and is a 12-bit value; for high-capacity cards, it corresponds to the C_SIZE parameter and is a 22-bit value.

[0076] It is also understood that the capacity multiplier can be a binary field stored in the card's dedicated data register, used in conjunction with the capacity indicator value to calculate the standard capacity, corresponding to the C_SIZE_MULT parameter, and typically a 3-digit value. This field is only used on standard capacity card types to indicate the multiplier factor of the capacity indicator value.

[0077] It should be understood that the read block length value can be a binary field stored in the memory card's card-specific data register, used to indicate the length of the data block during a read operation of the memory card, corresponding to the READ_BL_LEN parameter, and is typically a 4-bit value. This field is only used on standard capacity card types to calculate the physical capacity of the memory card.

[0078] Step S3332: When the capacity type is a standard capacity card, determine the standard capacity corresponding to the standard capacity card based on the capacity indication value, the capacity multiplier value, and the read block length value.

[0079] Specifically, if the capacity type is determined to be CSDv1.0 (i.e., standard capacity card), since its capacity data spans multiple non-contiguous bit fields, it is necessary to extract the 12-bit C_SIZE, the 3-bit C_SIZE_MULT, and the 4-bit READ_BL_LEN separately, and perform underlying shift and exponent concatenation operations. According to the protocol, the calculation formula is (C_SIZE+1)<<(C_SIZE_MULT+2+READ_BL_LEN) to restore the actual number of bytes and obtain the standard capacity corresponding to the standard capacity card.

[0080] Step S3333: When the capacity type is a high-capacity card, perform a linear operation on the capacity indication value to obtain the standard capacity corresponding to the high-capacity card.

[0081] It should be noted that for high-capacity card types, the standard capacity can be calculated by simply adding 1 to the capacity indicator value and then multiplying it by a fixed unit (such as 512KB).

[0082] Specifically, if the capacity type is determined to be CSDv2.0 (i.e., high-capacity card), then it switches to another branch, only needs to extract the 22-bit C_SIZE field and perform a simple linear multiplication operation, the calculation formula of which is (C_SIZE+1)*512KB.

[0083] This embodiment extracts the capacity indicator value, capacity multiplier value, and read block length value from the specification parameters. When a standard capacity card is detected, the standard capacity is determined by shifting and exponentially concatenating these three values. When a high capacity card is detected, the standard capacity is obtained by performing only a linear operation on the capacity indicator value. Thus, through the adaptive identification and branch calculation of the CSD register version within the card reader, the capacity parsing logic, which originally required the host to manually concatenate or handle different cases according to complex protocol formulas, is completely decentralized to be completed locally on the chip. Through full branch coverage within the card reader, the completely different bit widths and calculation logic at the underlying level can be uniformly cleansed into a standard physical total number of bytes.

[0084] Furthermore, in order to obtain the aforementioned current lifespan index, in this embodiment, the step of converting the lifespan characteristic parameters according to the flash memory chip type to obtain the current lifespan index includes: determining the offset address of the original erase / write count field in the lifespan characteristic parameters; reversing the byte order of the original erase / write count field based on the offset address to obtain the corresponding current erase / write count; obtaining the maximum theoretical erase / write threshold corresponding to the flash memory chip type; and determining the current lifespan index of the memory card based on the current erase / write count and the maximum theoretical erase / write threshold.

[0085] It should be noted that the raw erase / write count field can be a binary field in the lifespan characteristic parameters used to record the raw value of the physical erase / write count that has currently occurred on the memory card. The offset address can be the byte distance between the start position of the manufacturer's proprietary data block and the start position of the raw erase / write count field. For example, if the start address of the proprietary data block is 0 and the raw erase / write count field is located at the 5th byte, then the offset address is 5.

[0086] The byte order reversal process described above involves reversing the byte storage order of multi-byte values ​​in memory, such as converting big-endian to little-endian or vice versa, to obtain the correct value. For example, if the original order of two bytes read from a private data block is 0x03 0xE8 (big-endian), after byte order reversal, it becomes 0xE80x03.

[0087] It should also be noted that the current number of erase / write cycles can be obtained after byte order reversal and numerical conversion, representing the integer value of the number of physical erase / write cycles that the memory card has completed from its first use to the current moment.

[0088] Understandably, the maximum theoretical erase / write threshold can be predetermined based on the type of flash memory chip in the memory card, which is the maximum number of erase / write cycles that the type of flash memory chip can withstand under factory design.

[0089] Specifically, for the proprietary SMART data packets hidden by each manufacturer, the card reader first accurately locates the offset address of the original erase / write count field and performs byte order reversal calculation to obtain the corresponding current erase / write count. Then, it calls the built-in flash memory lifespan assessment model for dynamic conversion. Specifically, since flash memory with different manufacturing processes has completely different theoretical maximum lifespans (for example, TLC chips typically have a maximum erase / write count of 1000, while MLC chips have 3000), the reader dynamically retrieves the corresponding maximum theoretical erase / write threshold as the denominator based on the aforementioned flash memory chip type, and applies the built-in conversion model (i.e., the formula: Remaining lifespan percentage = 100 - (Current erase / write count / Maximum theoretical erase / write threshold) * 100) to dynamically convert the rigid underlying physical count value into a unified remaining lifespan percentage that upper-layer applications can directly understand, serving as the current lifespan indicator of the memory card.

[0090] After obtaining the above data, the card reader can fill it into a predefined, completely transparent, and uniformly formatted standard health data structure (e.g., Bytes 0-3 store the calculated percentage of remaining lifetime, Bytes 4-7 store the total number of extracted bad blocks, and Bytes 8-15 store the total physical capacity after cleaning), thus obtaining standard health data. This method solves the compatibility issues caused by inconsistent proprietary data formats and fragmented calculation formulas from various manufacturers, and provides a unified underlying data decision-making basis for subsequent devices to trigger automatic data migration and self-rescue when data risks exist on the storage medium.

[0091] In this embodiment, by accurately locating and adapting the byte order of the manufacturer's proprietary SMART data area within the card reader chip, and dynamically retrieving different wear threshold lifetime calculation models based on flash memory chip type, the underlying physical count value is directly converted into a standardized percentage of remaining lifetime. Compared to the traditional method that requires the host to manually parse proprietary data formats and match lifetime algorithms for different flash memory types, this embodiment encapsulates all deep extraction and dynamic calculation within the card reader firmware. This reduces the burden on the upper-layer system to adapt to the proprietary data structures and lifetime models of various manufacturers, improves the standardization of lifetime indicators, and enhances the universality of cross-brand SD card health monitoring.

[0092] It should be noted that the above examples are for understanding this application only and do not constitute a limitation on the information acquisition method of this application. Any simple modifications based on this technical concept are within the scope of protection of this application. All actions involving the acquisition of signals, information, or data in this application are carried out in compliance with the relevant data protection regulations of the country where the application is located and with authorization from the owner of the relevant device.

[0093] This application also provides an information acquisition device, please refer to... Figure 7 , Figure 7 This is a block diagram of the module structure of the information acquisition device according to an embodiment of this application; in this embodiment, the information acquisition device includes: Command module 701 is used to receive a health query command sent by the target device and trigger a built-in read command sequence according to the health query command. The read command sequence includes a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card. The reading module 702 is used to read the memory card based on the reading command sequence to obtain heterogeneous health data; The standard module 703 is used to normalize the heterogeneous health data to obtain standard health data, and transmit the standard health data to the target device.

[0094] This embodiment first receives a health query command sent by the target device through a card reader, and triggers a read command sequence containing underlying storage protocol commands built into the card reader according to the command. Then, it reads the memory card based on the read command sequence to obtain heterogeneous health data, and then normalizes the heterogeneous health data to obtain standard health data before returning it to the target device. Compared with existing methods that make it difficult to access the internal registers or SMART information of the SD card through a USB card reader, this embodiment can directly read the health status parameters of the SD card at the underlying USB link through a pre-built storage protocol command sequence, thereby effectively solving the problem of blind spots in remote monitoring caused by the difficulty in obtaining health information through the USB interface in scenarios such as commercial display digital signage.

[0095] In one implementation, the read command sequence includes a first low-level command, a second low-level command, and a third low-level command; the read module 702 is further configured to read identification information from the card identification register of the memory card according to the first low-level command; read specification parameters from the card-specific data register of the memory card according to the second low-level command; determine the private data block of the manufacturer's private area of ​​the memory card according to the third low-level command, and read lifespan characteristic parameters characterizing the wear level of the memory card from the private data block; and use the identification information, the specification parameters, and the lifespan characteristic parameters as heterogeneous health data extracted from the memory card.

[0096] In one implementation, the standard module 703 is further configured to extract identification information from the heterogeneous health data and match it with a pre-built manufacturer parsing feature table; determine the version number and flash memory chip type of the memory card based on the manufacturer parsing feature table; determine the standard capacity and current lifespan index of the memory card based on the heterogeneous health data, using the version number and flash memory chip type; and determine the standard health data of the memory card based on the standard capacity and the current lifespan index.

[0097] In one implementation, the standard module 703 is further configured to extract the heterogeneous health data to obtain the specification parameters and lifespan characteristic parameters of the memory card; detect the capacity type of the card-specific data register of the memory card according to the version number; standardize the specification parameters based on the capacity type to obtain the standard capacity; and convert the lifespan characteristic parameters according to the flash memory chip type to obtain the current lifespan index.

[0098] In one implementation, the standard module 703 is further configured to extract the capacity indication value, the capacity multiplier value, and the read block length value from the specification parameters; when the capacity type is a standard capacity card, determine the standard capacity corresponding to the standard capacity card based on the capacity indication value, the capacity multiplier value, and the read block length value; when the capacity type is a high capacity card, perform a linear operation on the capacity indication value to obtain the standard capacity corresponding to the high capacity card.

[0099] In one implementation, the standard module 703 is further configured to determine the offset address of the original erase / write count field in the lifetime characteristic parameters; based on the offset address, reverse the byte order of the original erase / write count field to obtain the corresponding current erase / write count; obtain the maximum theoretical erase / write threshold corresponding to the flash memory chip type; and determine the current lifetime index of the memory card based on the current erase / write count and the maximum theoretical erase / write threshold.

[0100] In one implementation, the command module 701 is further configured to receive a health query command sent by the target device through a first interface between the card reader and the target device, wherein the first interface is a universal serial bus interface; detect whether the health query command conforms to a preset aggregation command; if it conforms to the preset aggregation command, initiate a query takeover mode; in the query takeover mode, connect to the communication channel of the memory card through a second interface between the card reader and the memory card, wherein the second interface is a memory card protocol interface; and after the communication channel connection is completed, obtain a built-in read command sequence.

[0101] Other embodiments or specific implementations of the information acquisition device of this application can be found in the above-described method embodiments, and will not be repeated here.

[0102] The information acquisition device provided in this application, employing the information acquisition method described in the above embodiments, can solve the technical problem that traditional card readers have difficulty in acquiring the health status of SD cards. Compared with the prior art, the beneficial effects of the information acquisition device provided in this application are the same as those of the information acquisition method described in the above embodiments, and other technical features in the information acquisition device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0103] This application provides a card reader, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the information acquisition methods described in the above embodiments.

[0104] The following is for reference. Figure 8 , Figure 8 This is a schematic diagram of the hardware operating environment involved in the card reader in the embodiments of this application, which shows a schematic diagram of the structure of the card reader suitable for implementing the embodiments of this application. Figure 8 The card reader shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0105] like Figure 8As shown, the card reader may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to a program stored in read-only memory 1002 or a program loaded from storage device 1003 into random access memory 1004. Random access memory 1004 also stores various programs and data required for card reader operation. The processing device 1001, read-only memory 1002, and random access memory 1004 are interconnected via bus 1005. Input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to input / output interface 1006: input devices 1007 and output devices 1008, including, for example, USB interfaces, SD interfaces, etc.; storage devices 1003, including, for example, hard disks; and communication devices 1009. Communication device 1009 allows the card reader to communicate wirelessly or wiredly with other devices to exchange data. Although card readers with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. It can be implemented alternatively or with more or fewer systems.

[0106] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0107] The card reader provided in this application, employing the information acquisition method described in the above embodiments, can solve the technical problem that traditional card readers have difficulty in obtaining the health status of SD cards. Compared with the prior art, the beneficial effects of the card reader provided in this application are the same as those of the information acquisition method provided in the above embodiments, and other technical features of this card reader are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0108] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0109] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0110] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the information acquisition method described in the above embodiments.

[0111] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0112] The aforementioned computer-readable storage medium may be included in the card reader or may exist independently without being assembled into the card reader.

[0113] The aforementioned computer-readable storage medium carries one or more programs. When the card reader executes the aforementioned one or more programs, the card reader causes the card reader to: receive a health query command sent by the target device, and trigger a built-in read command sequence according to the health query command, wherein the read command sequence contains low-level commands defined according to the storage protocol of the memory card, and the low-level commands are commands for reading the health status parameters of the memory card; read the memory card based on the read command sequence to obtain heterogeneous health data; normalize the heterogeneous health data to obtain standard health data, and transmit the standard health data to the target device.

[0114] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0115] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation that may be implemented in systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0116] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0117] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described information acquisition method, thereby solving the technical problem that traditional card readers have difficulty in obtaining the health status of SD cards. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the information acquisition method provided in the above embodiments, and will not be repeated here.

[0118] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the information acquisition method described above.

[0119] The computer program product provided in this application can solve the technical problem that traditional card readers have difficulty obtaining the health status of SD cards. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the information acquisition method provided in the above embodiments, and will not be repeated here.

[0120] The above description is only a part of the embodiments of this application and does not limit the scope of protection of this application. All equivalent structural transformations made under the technical concept of this application and using the content of this application specification and drawings, or direct / indirect applications in other related technical fields, are included in the scope of protection of this application.

Claims

1. An information acquisition method, characterized in that, The information acquisition method is applied to a card reader, which is connected to both a memory card and a target device. The method includes: The system receives a health query command sent by the target device and triggers a built-in read command sequence according to the health query command. The read command sequence contains a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card. The memory card is read based on the read command sequence to obtain heterogeneous health data; The heterogeneous health data is normalized to obtain standard health data, and the standard health data is transmitted to the target device.

2. The method as described in claim 1, characterized in that, The read command sequence includes a first low-level command, a second low-level command, and a third low-level command; The step of reading the memory card based on the read command sequence to obtain heterogeneous health data includes: According to the first underlying command, read the identification information from the card identification register of the memory card; According to the second underlying command, read the specification parameters from the card-specific data register of the memory card; According to the third underlying command, the private data block of the manufacturer's private area of ​​the memory card is determined, and the life characteristic parameters characterizing the wear degree of the memory card are read from the private data block; The identification information, the specification parameters, and the lifespan characteristic parameters are used as heterogeneous health data extracted from the memory card.

3. The method as described in claim 1, characterized in that, The step of normalizing the heterogeneous health data to obtain standard health data includes: Extract the identification information from the heterogeneous health data, and match the identification information with a pre-built manufacturer parsing feature table; The version number and flash memory chip type of the memory card are determined based on the manufacturer's parsing feature table; Based on the heterogeneous health data, the standard capacity and current lifespan of the memory card are determined by the version number and the flash memory chip type. The standard health data of the memory card is determined based on the standard capacity and the current lifespan indicator.

4. The method as described in claim 3, characterized in that, The step of determining the standard capacity and current lifespan index of the memory card based on the heterogeneous health data, using the version number and the flash memory chip type, includes: Extract the heterogeneous health data to obtain the specifications and lifespan characteristics of the memory card; The capacity type of the card-specific data register of the memory card is detected based on the version number; The specification parameters are standardized based on the capacity type to obtain the standard capacity. The lifetime characteristic parameters are converted according to the flash memory chip type to obtain the current lifetime index.

5. The method as described in claim 4, characterized in that, The step of standardizing the specification parameters based on the capacity type to obtain the standard capacity includes: Extract the capacity indication value, capacity multiplier value, and read block length value from the specifications; When the capacity type is a standard capacity card, the standard capacity corresponding to the standard capacity card is determined according to the capacity indication value, the capacity multiplier value, and the read block length value. When the capacity type is a high-capacity card, a linear operation is performed on the capacity indication value to obtain the standard capacity corresponding to the high-capacity card.

6. The method as described in claim 4, characterized in that, The step of converting the lifetime characteristic parameters according to the flash memory chip type to obtain the current lifetime index includes: Determine the offset address of the original erase / write count field in the lifetime characteristic parameters; Based on the offset address, the original erase / write count field is reversed byte order to obtain the corresponding current erase / write count; Obtain the maximum theoretical erase / write threshold corresponding to the flash memory chip type; The current lifespan index of the memory card is determined based on the current number of erase / write cycles and the maximum theoretical erase / write threshold.

7. The method according to any one of claims 1 to 6, characterized in that, The step of receiving a health query command sent by the target device and triggering a built-in read command sequence according to the health query command includes: The reader receives a health query command sent by the target device through a first interface between the card reader and the target device. The first interface is a universal serial bus interface. Detect whether the health query command conforms to the preset aggregation command; If the preset aggregation instruction is met, the query takeover mode is activated; In the query takeover mode, the communication channel of the memory card is connected through the second interface between the card reader and the memory card. The second interface is the memory card protocol interface. After the communication channel connection is completed, the built-in read command sequence is obtained.

8. An information acquisition device, characterized in that, The device includes: The command module is used to receive a health query command sent by the target device and trigger a built-in read command sequence according to the health query command. The read command sequence contains a low-level command defined according to the storage protocol of the memory card. The low-level command is a command to read the health status parameters of the memory card. The reading module is used to read the memory card based on the read command sequence to obtain heterogeneous health data; A standard module is used to normalize the heterogeneous health data to obtain standard health data, and then transmit the standard health data to the target device.

9. A card reader, characterized in that, The card reader includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the information acquisition method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the information acquisition method as described in any one of claims 1 to 7.

Images