CN114138509B - Data interaction method and device and computer readable storage medium - Google Patents

Data interaction method and device and computer readable storage medium Download PDF

Info

Publication number
CN114138509B
CN114138509B CN202111370714.8A CN202111370714A CN114138509B CN 114138509 B CN114138509 B CN 114138509B CN 202111370714 A CN202111370714 A CN 202111370714A CN 114138509 B CN114138509 B CN 114138509B
Authority
CN
China
Prior art keywords
data
fru
fru data
target
descriptor record
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111370714.8A
Other languages
Chinese (zh)
Other versions
CN114138509A (en
Inventor
窦志冲
董世江
刘波
宋凯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN202111370714.8A priority Critical patent/CN114138509B/en
Publication of CN114138509A publication Critical patent/CN114138509A/en
Application granted granted Critical
Publication of CN114138509B publication Critical patent/CN114138509B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application discloses a data interaction method, a device and a computer readable storage medium, wherein the method relates to the technical field of computers and comprises the following steps: a list of platform descriptor records is obtained and a single piece of FRU data is collected. And generating corresponding platform descriptor record information according to the FRU data, adding the information to a platform descriptor record list, judging whether the BMC searches target FRU data from the list added with the platform descriptor record information, and sending the target FRU data to the BMC when the target FRU data is searched. The step of collecting single FRU data is set so that the BMC terminal does not collect the error FRU data when the error FRU data is transmitted, and the efficiency of data interaction is improved. Meanwhile, the situation that all FRU data are lost due to the fact that the Host end is too fast in operation speed and the FRU data volume is too large when the Host end is operated is avoided.

Description

Data interaction method and device and computer readable storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data interaction method, apparatus, and computer readable storage medium.
Background
With the continuous development of computer technology, data interaction methods are updated with the change of technology, and interaction between data is indispensable in the field of computer technology, and data interaction is mainly applied to data interaction between an underlying boot program (Host) of an operating system and a baseboard management controller (Baseboard Manager Controller, BMC).
With the recent change of international information security forms, information security has become an important point of attention in various countries, and information technology has been used as an attack means. Therefore, optimizing the Host end is important in order to make the computer operating system start more stably and efficiently.
The existing Host end needs to perform a large amount of data interaction with the BMC end in the operation process. All hardware information of the bottom layer of the operating system is identified and acquired through data interaction, so that the Host end and the BMC end keep information synchronization, and stable and safe use after the operating system works is realized. However, the Host transmits the data of the field replaceable unit (Field Replace Unit, FRU) in a way of overall transceiving based on a platform-level data transmission protocol (Platfrom Level Data Model, PLDM). According to the data interaction method for integral transceiving, even if only one FRU data is updated, updated data can be identified only by transceiving all original data, and the supplementary synchronization of the data between the Host end and the BMC end is completed. If the updated FRU data is wrong, the interaction of the data is wrong, so that the data transmission efficiency is extremely low.
In view of the above-mentioned problems, it is a matter of great effort for those skilled in the art to find an efficient data interaction method.
Disclosure of Invention
The application aims to provide a data interaction method which is used for efficiently carrying out data interaction.
In order to solve the technical problems, the application provides a data interaction method, which is applied to a Host end and comprises the following steps:
acquiring a platform descriptor record list;
collecting a single FRU data;
generating platform descriptor record information corresponding to FRU data according to the FRU data and adding the platform descriptor record information to a platform descriptor record list;
judging whether the BMC searches a target identifier corresponding to target FRU data from a platform descriptor record list added with the platform descriptor record information;
and if the target identifier is found, sending target FRU data to the BMC.
Preferably, determining whether the BMC finds a target identifier corresponding to the target FRU data from the platform descriptor record list to which the platform descriptor record information is added includes:
sending an acquisition instruction to trigger the BMC to acquire a platform descriptor record list, and analyzing the platform descriptor record list to obtain a target identifier corresponding to target FRU data;
receiving a request for acquiring FRU data sent by the BMC according to the target identifier;
and searching the target FRU data according to the request.
Preferably, after collecting the single FRU data and before generating the platform descriptor record information corresponding to the FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list, the method further comprises:
a single FRU data is stored to the FRU data list.
Preferably, if the target identifier is found, after sending the target FRU data to the BMC, the method further includes:
and receiving an end mark sent by the BMC, wherein the end mark is used for indicating that the BMC receives the target FRU data, and the end mark corresponds to the FRU data one by one.
Preferably, if the target identifier is found, after sending the target FRU data to the BMC, the method further includes:
judging whether the BMC collects all FRU data according to the number of the end marks;
if the number of the ending marks is equal to the number of FRU data, ending;
if the number of end markers is not equal to the number of FRU data, the process proceeds to collect a single FRU data.
In order to solve the technical problem, the application also provides a data interaction method, which is applied to a BMC end and comprises the following steps:
receiving a platform descriptor record list, wherein the platform descriptor record list is a platform descriptor record list recorded by a Host terminal for collecting single FRU data;
searching a target identifier corresponding to target FRU data in a platform descriptor record list;
sending a request for acquiring FRU data to a Host end according to the target identifier;
and receiving target FRU data sent by the Host terminal.
In order to solve the above technical problems, the present application provides a data interaction device, applied to a Host end, including:
the acquisition module is used for acquiring a platform descriptor record list;
the collection module is used for collecting single FRU data;
the generating module is used for generating platform descriptor record information corresponding to FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list;
the searching module is used for judging whether the BMC searches a target identifier corresponding to target FRU data from a platform descriptor record list added with the platform descriptor record information;
and the sending module is used for sending the target FRU data to the BMC if the target identifier is found.
In order to solve the technical problem, the application also provides a data interaction device, which is applied to a BMC end and comprises:
the first receiving module is used for receiving a platform descriptor record list, wherein the platform descriptor record list is a platform descriptor record list recorded by the single FRU data collected by a Host end;
the searching module is used for searching a target identifier corresponding to the target FRU data in the platform descriptor record list;
the sending module is used for sending a request for acquiring FRU data to a Host end according to the target identifier;
and the second receiving module is used for receiving the target FRU data sent by the Host end.
In order to solve the technical problem, the present application further provides a data interaction device, including:
a memory for storing a computer program;
and the processor is used for pointing to the computer program and realizing the steps of the data interaction method.
In order to solve the above technical problem, the present application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the above all data interaction method.
The data interaction method provided by the application comprises the following steps: a list of platform descriptor records is obtained and a single piece of FRU data is collected. And after generating platform descriptor record information corresponding to the FRU data and adding the platform descriptor record information to a platform descriptor record list, judging whether the BMC searches target FRU data from the list added with the platform descriptor record information, and sending the target FRU data to the BMC when the target FRU data is searched. In the application, the step of collecting single FRU data is set, and the Host terminal immediately sends the FRU data marked by the item to the BMC after collecting one FRU data, thereby ensuring the FRU data synchronization between the Host terminal and the BMC terminal. If the FRU data transmitted at this time is error data, the BMC terminal will not collect the FRU data. Compared with the transmission mode of integral transceiving, the transmission mode of single transceiving improves the data interaction efficiency, simultaneously avoids the situation that the upper layer system reads error data in the transmission mode of integral transceiving, and improves the accuracy. Meanwhile, the situation that all FRU data are not transmitted completely and are lost when the Host end runs completely due to the fact that the Host running speed is too high and the FRU data volume is too large is avoided.
The application also provides a data interaction device and a computer readable storage medium, and the effects are the same as the above.
Drawings
For a clearer description of embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described, it being apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is a flowchart of a data interaction method according to an embodiment of the present application;
FIG. 2 is a flowchart of another data interaction method according to an embodiment of the present application;
FIG. 3 is a block diagram of a data interaction device applied to a Host end according to an embodiment of the present application;
fig. 4 is a block diagram of a data interaction device applied to a BMC end according to an embodiment of the present application;
fig. 5 is a block diagram of a device for data interaction according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. Based on the embodiments of the present application, all other embodiments obtained by a person of ordinary skill in the art without making any inventive effort are within the scope of the present application.
The core of the application is to provide a data interaction method which can efficiently conduct data interaction.
In order to better understand the aspects of the present application, the present application will be described in further detail with reference to the accompanying drawings and detailed description.
Along with the increasingly compact international relationship, the form of international information security changes, and the information security becomes the focus of attention of each country, and the information technology is used as an attack means. Such attacks pose serious hazards to national information security, national infrastructure, and security of people's mass properties. To avoid this, the data interaction between Host and BMC in the computer operating system is optimized. The application relates to the technical field of computers, wherein data interaction is performed between a Host and a BMC in a computer operating system, and all hardware information of an operating system bottom layer is identified through the data interaction, so that data between the Host end and the BMC end are kept synchronous, and the data can be safely and stably used after the operating system runs. For a machine with a power architecture, based on a PLDM protocol, a data interaction mode between a Host end and a BMC end is integrated transceiving, and even if only one FRU data is updated, all original FRU data needs to be completely received and sent, further the FRU data is identified to be updated, and the synchronization of the data between the Host end and the BMC end is completed. For The power architecture mentioned above, which is a architecture based on a reduced instruction system (Reduced Instruction Set Computer, RISC) developed by The company of commercial machines in The ten thousand countries (International Business Machines Corporation, IBM), the processor employing The power architecture is more simple and efficient than The conventional X86 architecture (X86) processor.
The existing data interaction mode between the Host end and the BMC end is an integral transceiving mode, and the integral transceiving mode has two disadvantages. Firstly, when the FRU data volume is too large, the situation that the FRU data at the Host end and the BMC end are not transmitted yet, but the booting stage of the whole operation system is completed, which leads to the loss of the FRU data; second, if multiple FRUs are collected at a time to perform data interaction and only one piece of wrong FRU data exists, the data interaction will be wrong, and the upper operating system will acquire wrong bottom hardware information.
The application provides a mode, which uses a single data interaction mode of receiving and transmitting FRU data, and the Host terminal immediately transmits the FRU data to the BMC terminal after collecting the FRU data, so that the synchronization of the Host terminal and the BMC terminal is ensured. If the FRU data is wrong, the BMC terminal does not receive the FRU data.
Fig. 1 is a flowchart of a data interaction method according to an embodiment of the present application. As shown in fig. 1, the data interaction method includes:
s10: acquiring a platform descriptor record list;
the platform descriptor record list (Platformdescriptor record, PDR), also referred to simply as PDR list, referred to in this embodiment is mainly used to provide PLDM monitoring platform events, while describing the relationship between the sensor and control functions, the physical and logical entities being monitored, and the semantic information associated with each unit. Semantic information and associated information on the PLDM monitoring platform can be known through the PDR list, and the information comprises voice information returned by a sensor, such as: resolution, tolerance, accuracy, conversion factors, relationships between sensors and monitored entities, management controllers, effectors, and other platforms. It should be noted that the PDR list is mainly used to describe the subsystem, and not the control system or configuration system.
The platform descriptor record list has a part at the Host end and a part at the BMC end. Obtaining the platform descriptor record list is regarded as realizing FRU data synchronization between the Host end and the BMC end. It should be noted that, the method of obtaining the platform descriptor record list may be that the Host sends a request for obtaining the platform descriptor record list to the BMC, or the BMC updates the platform descriptor record list at regular time and sends the updated platform descriptor record list to the Host autonomously. In this embodiment, the method for obtaining the platform descriptor record list is not limited, as long as it is ensured that the Host end can obtain the platform descriptor record list, and the method for obtaining the platform descriptor record list can be set according to the application scenario in a specific embodiment.
S11: collecting a single FRU data;
the above-mentioned FRU data is the FRU data stored in the BMC terminal, and the Host terminal collects the original single FRU data of the BMC terminal from the BMC terminal. The method of collecting the single FRU data by the Host end may be that the Host end collects the single FRU data when the BMC end sends out a high level value, or that the Host end collects the single FRU data when the BMC end sends out a low level value, or that the BMC end or the Host end sends out an instruction for representing collection of the single FRU data. In this embodiment, the method for collecting single FRU data by the Host is not limited, as long as it can be determined that the Host collects single FRU data, and the method for collecting single FRU data can be set according to the application scenario in the specific embodiment.
S12: generating platform descriptor record information corresponding to FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list;
based on the steps, the FRU data is converted into a form which can be stored in a platform descriptor record list, and the platform descriptor record information corresponding to the FRU data is added into the platform descriptor record list. In this embodiment, the method for adding the platform descriptor record information corresponding to the fri data may be added to the platform descriptor record list by a high-low level method, or may be added to the platform descriptor record list by a sending instruction method. The order of the platform descriptor record information corresponding to the FRU data after addition in the platform descriptor record list may be sorted according to different classifications, or may be sorted according to the order of addition, in this embodiment, the manner of adding the platform descriptor record information corresponding to the FRU data and the order of adding the platform descriptor record information corresponding to the FRU data in the platform descriptor record list are not limited, and may be set according to a specific implementation scenario.
S13: judging whether the BMC searches a target identifier corresponding to target FRU data from the platform descriptor record list added with the platform descriptor record information;
if the target identifier is found, the process proceeds to step S14. In this embodiment, the target identifier is used to identify target FRU data, and it should be noted that each piece of target FRU data corresponds to a target identifier, and the target identifier is generally represented by a number, for example: 1. 2, 3, 4, 5, etc. The above-mentioned representation of the target mark is only a common representation in all embodiments, and does not represent a way of using only one number as the target mark, but may also use english letters, not limited to the case form of english letters, and may use other symbols that are marked and can be distinguished to represent the target mark. The representation form of the target mark can be customized by a user according to the current use scene. In the present embodiment, the number and the representation form of the target mark are not limited, and may be set according to the specific embodiment.
S14: sending the target FRU data to the BMC;
on the basis of the steps, after the target FRU data is found, the target FRU data is sent to the BMC. Note that, the manner of transmitting the target FRU data to the BMC may be to transmit the target FRU data to the BMC by a high-low level manner, or may be to transmit the target FRU data to the BMC by a transmission instruction manner, and in this embodiment, the manner of transmitting the target FRU data to the BMC is not limited, and may be set according to a specific embodiment.
In this embodiment, a step of collecting a single piece of FRU data is provided, and after a Host end collects a piece of FRU data, the FRU data of the item label is immediately sent to the BMC, so that the synchronization of the FRU data between the Host end and the BMC end is ensured. If the FRU data transmitted at this time is error data, the BMC terminal will not collect the FRU data. Compared with the transmission mode of integral transceiving, the transmission mode of single transceiving improves the data interaction efficiency, simultaneously avoids the situation that the upper layer system reads error data in the transmission mode of integral transceiving, and improves the accuracy. Meanwhile, the situation that all FRU data are not transmitted completely and are lost when the Host end runs completely due to the fact that the Host running speed is too high and the FRU data volume is too large is avoided.
On the basis of the above embodiment, determining whether the BMC finds the target identifier corresponding to the target FRU data from the platform descriptor record list to which the platform descriptor record information is added includes:
sending an acquisition instruction to trigger the BMC to acquire a platform descriptor record list, and analyzing the platform descriptor record list to obtain a target identifier corresponding to target FRU data;
receiving a request for acquiring FRU data sent by the BMC according to the target identifier;
and searching the target FRU data according to the request.
In the above embodiment, it is mentioned that the platform descriptor record list is to be acquired first, and in this embodiment, the method of defining the platform descriptor record list is that the Host end sends an acquisition instruction to the BMC end, and accepts a request sent by the BMC according to the target identifier to acquire FRU data, and searches for target FRU data according to the request to acquire FRU data. In this embodiment, since each piece of FRU data corresponds to one target identifier, only one target identifier exists, it is necessary to find one piece of FRU data corresponding to the platform descriptor record information in the platform descriptor record list. One FRU data corresponds to one target identifier, so that the corresponding FRU data can be identified efficiently and accurately, and the situation of transmitting the FRU data in error is avoided.
On the basis of the above embodiment, after collecting a single piece of FRU data and before generating platform descriptor record information corresponding to the FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list, the method further includes:
s20: storing a single piece of FRU data to an FRU data list;
in this embodiment, the location where the single FRU data is stored is defined, and this step is used to prevent the FRU data from being lost in the transmission process, and the backup is performed at the Host end, and when the FRU data at the BMC end is lost, the FRU data at the Host end can be obtained again from the FRU data list at the Host end.
On the basis of the above embodiment, if the target identifier is found, after sending the target FRU data to the BMC, the method further includes:
s21: receiving an end mark sent by the BMC;
the end mark mentioned in this embodiment is used to indicate that the BMC receives the target FRU data, where the end mark corresponds to the FRU data one-to-one. Each FRU data has a corresponding end mark, and when the target FRU data is sent to the BMC terminal, the BMC terminal sends the end mark corresponding to the FRU data to the Host terminal. It should be noted that, each time the BMC receives an FRU data, the BMC sends an end flag corresponding to the FRU data to the Host. The end mark is used as information for representing that the Host receives FRU data, so that the Host can conveniently judge whether all FRU data are collected. Identifying only end markers is more convenient than identifying complex FRU data.
On the basis of the foregoing embodiment, if the target identifier is found, after sending the target FRU data to the BMC, the method further includes:
s22: judging whether the BMC collects all FRU data according to the number of the end marks;
if the number of the ending marks is equal to the number of the FRU data, ending;
and if the number of the end marks is not equal to the number of the FRU data, entering the step of collecting single FRU data.
In this embodiment, before data interaction starts or before data interaction starts but single-piece FRU data is not collected, the Host counts the number of all FRU data to be transmitted by the BMC end, and records the number, and the location where the number is stored is not limited, and may be stored at the Host, may be stored at the BMC end, may also be stored in the memory 50, and may be set according to a specific embodiment. The relationship between the number of the judging end marks and the number of the FRU data is more convenient than that of the FRU data with complex judgment.
The application also provides a data interaction method applied to the BMC end, comprising the following steps:
receiving a platform descriptor record list, wherein the platform descriptor record list is recorded by a Host terminal for collecting single FRU data;
searching a target identifier corresponding to target FRU data in the platform descriptor record list;
sending a request for acquiring FRU data to the Host according to the target identifier;
and receiving the target FRU data sent by the Host.
In this embodiment, a receiving platform descriptor record list is set, where the platform descriptor record list is a step of collecting a platform descriptor record list recorded by single FRU data by a Host, and the Host immediately sends the item of frame FRU data to the BMC after collecting one piece of FRU data, so that FRU data synchronization between the Host and the BMC is ensured. If the transmitted FRU data is wrong, the BMC end cannot collect the FRU data. Compared with the transmission mode of integral transceiving, the transmission mode of single transceiving improves the data interaction efficiency, simultaneously avoids the situation that the upper layer system reads error data in the transmission mode of integral transceiving, and improves the accuracy. Meanwhile, the situation that all FRU data are not transmitted completely and are lost when the Host end runs completely due to the fact that the Host running speed is too high and the FRU data volume is too large can be avoided.
In the above embodiments, the detailed description is given to the data interaction method, and the present application further provides a corresponding embodiment of the data interaction device applied to the Host end. Fig. 3 is a block diagram of a data interaction device applied to a Host end according to an embodiment of the present application. As shown in fig. 3, the present application further provides a data interaction device, including:
the acquisition module is used for acquiring a platform descriptor record list;
the collection module is used for collecting single FRU data;
the generating module is used for generating platform descriptor record information corresponding to FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list;
the searching module is used for judging whether the BMC searches a target identifier corresponding to target FRU data from a platform descriptor record list added with the platform descriptor record information;
and the sending module is used for sending the target FRU data to the BMC if the target identifier is found.
In the foregoing embodiments, the detailed description is provided for the data interaction method, and the application further provides a corresponding embodiment of the data interaction device applied to the BMC end. Fig. 4 is a block diagram of a data interaction device applied to a BMC end according to an embodiment of the present application. As shown in fig. 4, the present application further provides a data interaction device, including:
the first receiving module is used for receiving a platform descriptor record list, wherein the platform descriptor record list is a platform descriptor record list recorded by the single FRU data collected by a Host end;
the searching module is used for searching a target identifier corresponding to the target FRU data in the platform descriptor record list;
the sending module is used for sending a request for acquiring FRU data to a Host end according to the target identifier;
and the second receiving module is used for receiving the target FRU data sent by the Host end.
Since the embodiments of the apparatus portion and the embodiments of the method portion correspond to each other, the embodiments of the apparatus portion are referred to the description of the embodiments of the method portion, and are not repeated herein.
Fig. 5 is a block diagram of a data interaction device according to an embodiment of the present application, where, as shown in fig. 5, the data interaction device provided by the present application includes:
a memory 50 for storing a computer program;
a processor 51 for implementing the steps of the data interaction method as mentioned in the above embodiments when executing a computer program.
The data interaction device provided in this embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like.
Processor 51 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 51 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 51 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 51 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 51 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 50 may include one or more computer-readable storage media, which may be non-transitory. Memory 50 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 50 is at least used for storing a computer program, where the computer program, when loaded and executed by the processor 51, is capable of implementing the relevant steps of the data interaction method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 50 may also include an operating system, data, etc., and the storage manner may be transient storage or permanent storage. The operating system may include Windows, unix, linux, among others.
In some embodiments, the data interaction device may further comprise a display screen, an input-output interface, a communication interface, a power supply and a communication bus.
Those skilled in the art will appreciate that the structure shown in fig. 5 does not constitute a limitation of the data interaction device and may include more or fewer components than shown.
The data interaction device provided by the embodiment of the application comprises a memory 50 and a processor 51, wherein the processor 51 can realize the data interaction method when executing a program stored in the memory 50.
Finally, the application also provides a corresponding embodiment of the computer readable storage medium. The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps described in the method embodiments (the method may be a method corresponding to the Host side or a method corresponding to the BMC side).
It will be appreciated that the methods of the above embodiments, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored on a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in part or in whole or in part in the form of a software product stored in a storage medium for performing all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The data interaction method provided by the application is described in detail above. In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the application can be made without departing from the principles of the application and these modifications and adaptations are intended to be within the scope of the application as defined in the following claims.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Claims (10)

1. The data interaction method is characterized by being applied to a Host end and comprising the following steps of:
acquiring a platform descriptor record list;
collecting a single FRU data;
generating platform descriptor record information corresponding to FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list;
judging whether the BMC searches a target identifier corresponding to target FRU data from the platform descriptor record list added with the platform descriptor record information;
and if the target identifier is found, sending the target FRU data to the BMC.
2. The data interaction method of claim 1, wherein the determining whether the BMC finds a target identifier corresponding to target FRU data from the platform descriptor record list to which the platform descriptor record information is added comprises:
sending an acquisition instruction to trigger the BMC to acquire the platform descriptor record list, and analyzing the platform descriptor record list to obtain a target identifier corresponding to the target FRU data;
receiving a request for acquiring FRU data, which is sent by the BMC according to the target identifier;
and searching the target FRU data according to the request.
3. The data interaction method of claim 1, wherein after the collecting single piece of FRU data and before the generating the platform descriptor record information corresponding to the FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list, further comprises:
and storing a single piece of FRU data into an FRU data list.
4. The data interaction method of claim 1, wherein after the target identifier is found and the target FRU data is sent to the BMC, further comprising:
and receiving an end mark sent by the BMC, wherein the end mark is used for indicating that the BMC receives the target FRU data, and the end mark corresponds to the FRU data one by one.
5. The data interaction method of claim 4, wherein after the target identifier is found and the target FRU data is sent to the BMC, further comprising:
judging whether the BMC collects all FRU data according to the number of the end marks;
if the number of the ending marks is equal to the number of the FRU data, ending;
and if the number of the end marks is not equal to the number of the FRU data, entering the step of collecting single FRU data.
6. The data interaction method is characterized by being applied to a BMC end and comprising the following steps:
receiving a platform descriptor record list, wherein the platform descriptor record list is recorded by a Host terminal for collecting single FRU data;
searching a target identifier corresponding to target FRU data in the platform descriptor record list;
sending a request for acquiring FRU data to the Host according to the target identifier;
and receiving the target FRU data sent by the Host.
7. The data interaction device is characterized by being applied to a Host end and comprising:
the acquisition module is used for acquiring a platform descriptor record list;
the collection module is used for collecting single FRU data;
the generation module is used for generating platform descriptor record information corresponding to the FRU data according to the FRU data and adding the platform descriptor record information to the platform descriptor record list;
the searching module is used for judging whether the BMC searches a target identifier corresponding to target FRU data from the platform descriptor record list added with the platform descriptor record information;
and the sending module is used for sending the target FRU data to the BMC if the target identifier is found.
8. The utility model provides a data interaction device which is characterized in that is applied to the BMC end, includes:
the first receiving module is used for receiving a platform descriptor record list which is recorded by collecting single FRU data for a Host terminal;
the searching module is used for searching a target identifier corresponding to the target FRU data in the platform descriptor record list;
the sending module is used for sending a request for acquiring FRU data to the Host end according to the target identifier;
and the second receiving module is used for receiving the target FRU data sent by the Host end.
9. A data interaction device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of data interaction as claimed in any one of claims 1 to 6 when said computer program is executed.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, realizes the steps of data interaction according to any of claims 1 to 6.
CN202111370714.8A 2021-11-18 2021-11-18 Data interaction method and device and computer readable storage medium Active CN114138509B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111370714.8A CN114138509B (en) 2021-11-18 2021-11-18 Data interaction method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111370714.8A CN114138509B (en) 2021-11-18 2021-11-18 Data interaction method and device and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN114138509A CN114138509A (en) 2022-03-04
CN114138509B true CN114138509B (en) 2023-08-18

Family

ID=80390319

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111370714.8A Active CN114138509B (en) 2021-11-18 2021-11-18 Data interaction method and device and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN114138509B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104317667A (en) * 2014-10-27 2015-01-28 浪潮电子信息产业股份有限公司 Method for synchronizing DMI (desktop management interface) and FRU (field replace unit)
CN105488009A (en) * 2015-12-03 2016-04-13 英业达科技有限公司 FRU read/write method and read/write system
CN108182278A (en) * 2018-01-26 2018-06-19 郑州云海信息技术有限公司 A kind of FRU information maintenance methods and relevant apparatus
WO2021128903A1 (en) * 2019-12-26 2021-07-01 苏州浪潮智能科技有限公司 Method and system for accelerating reading of information of field replace unit, device and medium
CN114817313A (en) * 2022-04-30 2022-07-29 苏州浪潮智能科技有限公司 Method, system, equipment and medium for storing FRU data by firmware

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104317667A (en) * 2014-10-27 2015-01-28 浪潮电子信息产业股份有限公司 Method for synchronizing DMI (desktop management interface) and FRU (field replace unit)
CN105488009A (en) * 2015-12-03 2016-04-13 英业达科技有限公司 FRU read/write method and read/write system
CN108182278A (en) * 2018-01-26 2018-06-19 郑州云海信息技术有限公司 A kind of FRU information maintenance methods and relevant apparatus
WO2021128903A1 (en) * 2019-12-26 2021-07-01 苏州浪潮智能科技有限公司 Method and system for accelerating reading of information of field replace unit, device and medium
CN114817313A (en) * 2022-04-30 2022-07-29 苏州浪潮智能科技有限公司 Method, system, equipment and medium for storing FRU data by firmware

Also Published As

Publication number Publication date
CN114138509A (en) 2022-03-04

Similar Documents

Publication Publication Date Title
CN105357038B (en) Monitor the method and system of cluster virtual machine
WO2022121171A1 (en) Similar text matching method and apparatus, and electronic device and computer storage medium
WO2020108063A1 (en) Feature word determining method, apparatus, and server
JP5423904B2 (en) Information processing apparatus, message extraction method, and message extraction program
CN108399072B (en) Application page updating method and device
CN111737443B (en) Answer text processing method and device and key text determining method
CN104903865B (en) Virtual machine VM images are applied to the method and system of computer system
CN114138509B (en) Data interaction method and device and computer readable storage medium
CN115757054A (en) Log recording method, system, computer equipment and medium
KR20110023580A (en) The method and system for recovering data
CN105188154B (en) A kind of method, apparatus and system being automatically brought into operation smart machine
CN110955709B (en) Data processing method and device and electronic equipment
CN113656378A (en) Server management method, device and medium
CN114547336A (en) Text data processing method, device, equipment and storage medium
CN113553826A (en) Information input method and device combining RPA and AI and electronic equipment
CN114547184A (en) Personnel information synchronization method, terminal device and storage medium
CN112559478B (en) Log generation method and device, terminal equipment and storage medium
CN110750268A (en) File cleaning method and device, computer readable storage medium and electronic equipment
CN106528577B (en) Method and device for setting file to be cleaned
CN115242688B (en) Network fault detection method, device and medium
CN114475631B (en) Driving data processing method, device, automatic driving vehicle medium and product
CN109656961B (en) Method and device for searching homonymous tasks based on data analysis, medium and electronic equipment
CN109547290B (en) Cloud platform garbage data detection processing method, device, equipment and storage medium
CN110881002B (en) Electronic red packet monitoring method and device and terminal equipment
CN113781602A (en) Gantt chart generation method and device, computer readable storage medium and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant