CN114138509A - Data interaction method and device and computer readable storage medium - Google Patents
Data interaction method and device and computer readable storage medium Download PDFInfo
- Publication number
- CN114138509A CN114138509A CN202111370714.8A CN202111370714A CN114138509A CN 114138509 A CN114138509 A CN 114138509A CN 202111370714 A CN202111370714 A CN 202111370714A CN 114138509 A CN114138509 A CN 114138509A
- Authority
- CN
- China
- Prior art keywords
- data
- fru
- fru data
- descriptor record
- target
- 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.)
- Granted
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 78
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000004590 computer program Methods 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000012636 effector Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
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 data interaction 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 after generating corresponding platform descriptor record information according to the FRU data and adding the information into a platform descriptor record list, judging whether the target FRU data is searched by the BMC 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 the single FRU data is set so that the BMC end cannot collect the wrong FRU data when the wrong FRU data is transmitted, and the efficiency of data interaction is improved. Meanwhile, the situation that data loss is caused because all FRU data are not transmitted completely when the Host end finishes running due to the fact that the Host end runs at a too high speed and the FRU data amount is too large is avoided.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data interaction method and apparatus, and a computer-readable storage medium.
Background
With the continuous development of computer technology, data interaction methods are updated along with the change of the technology, the interaction between data is indispensable in the technical field of computers, and the data interaction is mainly applied to the data interaction between a bottom layer boot program (Host) of an operating system and a Baseboard Management Controller (BMC).
In recent years, with the change of international information security forms, information security has become a focus of attention in various countries, and information technology has been used as an attack means. Therefore, in order to make the computer operating system more stable and efficient to start, it is important to optimize the Host end.
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 of the operating system after working is realized. However, the Host transmits Field Replaceable Unit (FRU) Data in a whole transceiving mode on the basis of a Platform Level Data Model (PLDM). Even if only one FRU data is updated, the data interaction method of the whole receiving and sending needs to receive and send all original data to identify the updated data, and the data supplementary synchronization between the Host end and the BMC end is completed. If the updated FRU data is wrong, the data interaction is also wrong, and thus the data transmission efficiency is extremely low.
In view of the above problems, it is an endeavor of 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 carrying out data interaction with high efficiency.
In order to solve the above technical problem, the present application provides a data interaction method, applied to a Host end, including:
acquiring a platform descriptor record list;
collecting a single piece of FRU data;
generating platform descriptor record information corresponding to the FRU data according to the FRU data and adding the platform descriptor record information to a platform descriptor record list;
judging whether the BMC finds 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 identification is found, transmitting target FRU data to the BMC.
Preferably, the 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 so as 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 a BMC according to a target identifier;
and searching 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 from the FRU data and adding the platform descriptor record information to the platform descriptor record list, the method further includes:
storing a single piece of FRU data in a FRU data list.
Preferably, if the target identifier is found, after the target FRU data is sent 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 to one.
Preferably, if the target identifier is found, after the target FRU data is sent to the BMC, the method further includes:
judging whether the BMC collects all FRU data or not according to the number of the end marks;
if the number of the end marks is equal to the number of the FRU data, ending;
if the number of the end marks is not equal to the number of the FRU data, the step of collecting single FRU data is carried out.
In order to solve the above technical problem, the present application further provides a data interaction method, applied to a BMC terminal, including:
receiving a platform descriptor record list, wherein the platform descriptor record list is a platform descriptor record list recorded by single FRU data collected by a Host end;
searching a target identifier corresponding to target FRU data in the 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 end.
In order to solve the above technical problem, the present application provides a data interaction device, which is applied to a Host end, and includes:
the acquisition module is used for acquiring a platform descriptor record list;
a collection module for collecting single FRU data;
the generating 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 a platform descriptor record list;
the searching module is used for judging whether the BMC searches a target identifier corresponding to the 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.
In order to solve the above technical problem, the present application further provides a data interaction device, which is applied to a BMC terminal, and includes:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is used for receiving a platform descriptor record list, and the platform descriptor record list is a platform descriptor record list recorded by a 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 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.
In order to solve the above technical problem, the present application further provides a data interaction apparatus, 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, where a computer program is stored, and when the computer program is executed by a processor, the steps of the above all data interaction methods are implemented.
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 data according to the FRU data and adding the platform descriptor record information to a platform descriptor record list, judging whether the BMC finds the 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 found. The method has the advantages that the step of collecting single FRU data is set, the entry mark FRU data is immediately sent to the BMC after the Host end collects the FRU data, and the FRU data synchronization between the Host end and the BMC end is guaranteed. If the FRU data transmitted at this time is error data, the BMC end cannot collect the FRU data. Compared with the integral transceiving transmission mode, the single transceiving transmission mode improves the data interaction efficiency, avoids the situation that an upper layer system reads wrong data under the integral transceiving transmission mode, and improves the accuracy. Meanwhile, the situation that data loss is caused because all FRU data are not transmitted completely when the Host end finishes running due to the fact that the Host running speed is too high and the quantity of the FRU data 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 above.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a data interaction method according to an embodiment of the present application;
FIG. 2 is a flow chart of another data interaction method provided by an embodiment of the present application;
fig. 3 is a structural diagram of a data interaction device applied to a Host end according to an embodiment of the present application;
fig. 4 is a structural diagram of a data interaction device applied to a BMC end according to an embodiment of the present disclosure;
fig. 5 is a block diagram of a data interaction apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the present application.
The core of the application is to provide a data interaction method which can carry out data interaction with high efficiency.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings.
With the increasingly compact international relations, the international information security forms change, information security becomes a key point of attention of various countries, and information technology is used as an attack means. Such attacks pose serious hazards to national information security, national infrastructure, and the security of the people's property. To avoid this, data interaction between Host and BMC in the computer operating system is optimized. The application relates to the technical field of computers, data interaction is carried out between a Host and a BMC in a computer operating system, and all hardware information of the bottom layer of the operating system is identified through the data interaction, so that the data between the Host end and the BMC end are kept synchronous, and the operating system can be safely and stably used after running. For a power-architecture machine, on the basis of a PLDM protocol, a data interaction mode between a Host end and a BMC end is integrated receiving and sending, and even if only one FRU data is updated, all original FRU data need to be completely received and sent, so that the FRU data update is identified, and the data synchronization between the Host end and the BMC end is completed. The above-mentioned power architecture is a Reduced Instruction Set Computer (RISC) -based architecture developed by International Business Machines Corporation (IBM), and a processor adopting The power architecture has The characteristics of simple structure and high efficiency compared with a processor adopting a common X86 architecture (The X86 architecture, X86).
The existing data interaction mode between the Host end and the BMC end is integral receiving and sending, and the integral receiving and sending mode has two disadvantages. Firstly, when the FRU data volume is too large, the situation that FRU data of the Host end and the BMC end are not transmitted yet, but the boot phase of the whole operating system is completed, occurs, which results in the loss of FRU data; secondly, if a plurality of FRU data are collected for data interaction at one time and only one piece of wrong FRU data exists, the FRU data interaction is wrong, and then the upper operating system can acquire wrong bottom-layer hardware information.
The method includes that a single-receiving and sending data interaction mode is used for FRU data, and after a Host end collects one piece of FRU data, the FRU data are immediately sent to a BMC end, so that synchronization of the Host end and the BMC end is guaranteed. If the FRU data is wrong, the BMC end cannot 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 (PDR), also referred to as PDR list for short, is mainly used to provide PLDM monitoring platform events, and describes the relationship between sensors and control functions, monitored physical and logical entities, and semantic information of each unit. Semantic information and associated information on the PLDM monitoring platform can be obtained through the PDR list, and the information includes voice information returned by the sensor, such as: resolution, tolerances, 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 subsystems, not the control system or configuration system.
The platform descriptor record list has a part at the Host side and a part at the BMC side. And acquiring the platform descriptor record list to realize FRU data synchronization between the Host end and the BMC end. It should be noted that the manner 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 that 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 manner of 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 manner of obtaining the platform descriptor record list may be set according to an application scenario in a specific embodiment.
S11: collecting a single piece of FRU data;
the FRU data mentioned above is FRU data stored in the BMC, and the Host collects original single FRU data of the BMC from the BMC. The mode of collecting the single FRU data by the Host end can be that the Host end collects the single FRU data when the BMC end sends a high level value, or the Host end collects the single FRU data when the BMC end sends a low level value, or the Host end collects the single FRU data when the BMC end or the Host end sends an instruction for representing the collection of the single FRU data. In this embodiment, the manner in which the Host end collects the single FRU data is not limited, as long as it can be determined that the Host end collects the single FRU data, and the manner in which the single FRU data is collected may be set according to the application scenario in the specific embodiment.
S12: 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;
on the basis of the steps, the obtained FRU data is converted into a form capable of being stored in a platform descriptor record list, and platform descriptor record information corresponding to the FRU data is added to the platform descriptor record list. It should be noted that in this embodiment, the manner of adding the platform descriptor record information corresponding to the piece of FRU data may be adding the platform descriptor record information to the platform descriptor record list in a high-low level manner, or adding the platform descriptor record information to the platform descriptor record list in a manner of sending an instruction. In addition, the order of the platform descriptor record information corresponding to the added FRU data in the platform descriptor record list may be sorted according to different classifications, or may be sorted according to the order of addition.
S13: judging whether the BMC finds 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 identifiers are 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 usually represented by a number, for example: 1. 2, 3, 4, 5, etc. The above mentioned target mark is only a common expression form in all embodiments, and does not represent a way of using only one number as the target mark, but also uses english letters, and does not limit the case form of the english letters, and other symbols which have marking property and can be distinguished can be used to represent the target mark. The representation form of the target identification can be customized by a user according to the current use scene. In this embodiment, the number and the representation form of the target identifier are not limited, and may be set according to a specific implementation manner.
S14: sending the target FRU data to the BMC;
and on the basis of the steps, after the target FRU data is found, the target FRU data is sent to the BMC. It should be noted that the manner for sending the target FRU data to the BMC may be sending the target FRU data to the BMC in a high-low level manner, or sending the target FRU data to the BMC in a command manner.
In the embodiment, a step of collecting single FRU data is set, and the Host end immediately sends the item mark FRU data to the BMC after collecting one piece of FRU data, so that the FRU data synchronization between the Host end and the BMC end is ensured. If the FRU data transmitted at this time is error data, the BMC end cannot collect the FRU data. Compared with the integral transceiving transmission mode, the single transceiving transmission mode improves the data interaction efficiency, avoids the situation that an upper layer system reads wrong data under the integral transceiving transmission mode, and improves the accuracy. Meanwhile, the situation that data loss is caused because all FRU data are not transmitted completely when the Host end finishes running due to the fact that the Host running speed is too high and the quantity of the FRU data 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 so as 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 a BMC according to a target identifier;
and searching target FRU data according to the request.
In the above embodiment, the platform descriptor record list is to be acquired first, and in this embodiment, the manner of defining the acquisition of the platform descriptor record list is that the Host end sends an acquisition instruction to the BMC end, receives a request for acquiring FRU data sent by the BMC according to the target identifier, and searches for the target FRU data according to the request for acquiring FRU data. In this embodiment, each piece of FRU data corresponds to one target identifier, so that one piece of FRU data corresponding to the platform descriptor record information in the platform descriptor record list can be found as long as one target identifier exists. An FRU data corresponds to a target mark and can efficiently and accurately identify the corresponding FRU data, thereby avoiding the situation of error transmission of the FRU data.
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 from 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 the FRU data in an FRU data list;
in this embodiment, the location where a single FRU data is stored is defined, and this step is used to prevent FRU data from being lost during transmission, and backup is performed at the Host end, and when FRU data at the BMC end is lost, 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 the target FRU data is sent to the BMC, the method further includes:
s21: receiving an end mark sent by the BMC;
the end flag mentioned in this embodiment is used to indicate that the BMC receives the target FRU data, where the end flag corresponds to the FRU data one to one. Each FRU data has a corresponding end mark, and after the target FRU data is sent to the BMC end, the BMC end sends the end mark corresponding to the FRU data to the Host end. It should be noted that, whenever 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 end receives FRU data, and is convenient for the Host end to judge whether all FRU data are collected. Identifying only the end marker is more convenient than identifying complex FRU data.
On the basis of the above embodiment, if the target identifier is found, after the target FRU data is sent to the BMC, the method further includes:
s22: judging whether the BMC collects all the FRU data or not according to the number of the end marks;
if the number of the end marks is equal to the number of the FRU data, ending;
if the number of the end markers is not equal to the number of the FRU data, entering the step of collecting single FRU data.
In this embodiment, before the start of data interaction or before the start of data interaction but before collection of a single piece of FRU data is not performed, the Host counts the number of all FRU data to be transmitted by the BMC, and records the number, where the number is stored is not limited, and may be stored in the Host, the BMC, or the memory 50, where the storage location may be set according to a specific implementation manner. Compared with the judgment of complex FRU data, the relation between the number of the judgment end marks and the number of the FRU data is more convenient.
The application also provides a data interaction method, which is applied to the BMC terminal 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 collecting single FRU data by a Host end;
finding a target identifier corresponding to target FRU data in the platform descriptor record list;
sending a request for acquiring FRU data to the Host terminal according to the target identifier;
and receiving the target FRU data sent by the Host terminal.
In this embodiment, a receiving platform descriptor record list is set, where the platform descriptor record list is a step of a platform descriptor record list recorded by a Host collecting a single piece of FRU data, and the Host collects a piece of FRU data and then immediately sends the FRU data to the BMC, so as to ensure FRU data synchronization between the Host and the BMC. If the transmitted FRU data is wrong, the BMC end cannot collect the FRU data. Compared with the integral transceiving transmission mode, the single transceiving transmission mode improves the data interaction efficiency, avoids the situation that an upper layer system reads wrong data in the integral transceiving transmission mode, and improves the accuracy. Meanwhile, the situation that data loss is caused because all FRU data are not transmitted completely when the Host end finishes running due to the fact that the Host running speed is too high and the quantity of the FRU data is too large can be avoided.
In the foregoing embodiments, the data interaction method is described in detail, and the present application also provides an embodiment corresponding to the data interaction device applied to the Host side. Fig. 3 is a structural 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 apparatus, including:
the acquisition module is used for acquiring a platform descriptor record list;
a collection module for collecting single FRU data;
the generating 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 a platform descriptor record list;
the searching module is used for judging whether the BMC searches a target identifier corresponding to the 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.
In the foregoing embodiment, a detailed description is given for the data interaction method, and the application also provides an embodiment corresponding to the data interaction device applied to the BMC terminal. Fig. 4 is a structural diagram of a data interaction device applied to a BMC end according to an embodiment of the present disclosure. As shown in fig. 4, the present application further provides a data interaction apparatus, including:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is used for receiving a platform descriptor record list, and the platform descriptor record list is a platform descriptor record list recorded by a 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 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.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
Fig. 5 is a structural diagram of a data interaction device according to an embodiment of the present application, and as shown in fig. 5, the data interaction device according to the present application includes:
a memory 50 for storing a computer program;
the processor 51, when executing the computer program, is configured to implement the steps of the data interaction method as mentioned in the above embodiments.
The data interaction device provided by the embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, or a desktop computer.
The processor 51 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 51 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 51 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 51 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 51 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
In some embodiments, the data interaction device may further include a display screen, an input/output interface, a communication interface, a power source, and a communication bus.
Those skilled in the art will appreciate that the configuration shown in FIG. 5 does not constitute a limitation of data interaction means and may include more or fewer components than those shown.
The data interaction device provided by the embodiment of the application comprises a memory 50 and a processor 51, and the processor 51 can realize the data interaction method when executing the 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 thereon a computer program, and when executed by the processor, the computer program implements the steps described in the above method embodiments (which may be a method corresponding to the Host side or a method corresponding to the BMC side).
It is to be understood that if the method in the above embodiments is implemented in the form of software functional units and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application may be substantially or partially implemented in the form of a software product, which is stored in a storage medium and executes all or part of the steps of the methods of the embodiments of the present application, or all or part of the technical solutions. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The data interaction method provided by the present application is described in detail above. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present 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. Also, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A data interaction method is applied to a Host end and comprises the following steps:
acquiring a platform descriptor record list;
collecting a single piece of FRU data;
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;
judging whether the BMC finds 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 identification 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 the target identifier corresponding to the target FRU data from the platform descriptor record list to which the platform descriptor record information is added comprises:
sending an acquisition instruction so as 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 collecting the single piece of FRU data and before generating the platform descriptor record information corresponding to the FRU data from the FRU data and adding the platform descriptor record information to the platform descriptor record list, further comprising:
storing a single piece of the FRU data in a FRU data list.
4. The data interaction method of claim 1, wherein after sending the target FRU data to the BMC if the target identifier is found, further comprising:
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 to one.
5. The data interaction method of claim 4, wherein after sending the target FRU data to the BMC if the target identifier is found, further comprising:
judging whether the BMC collects all the FRU data or not according to the number of the end marks;
if the number of the end marks is equal to the number of the FRU data, ending;
if the number of the end markers is not equal to the number of the FRU data, entering the step of collecting single FRU data.
6. A data interaction method is applied to a BMC terminal, 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 collecting single FRU data by a Host end;
finding a target identifier corresponding to target FRU data in the platform descriptor record list;
sending a request for acquiring FRU data to the Host terminal according to the target identifier;
and receiving the target FRU data sent by the Host terminal.
7. A data interaction device is applied to a Host end and comprises:
the acquisition module is used for acquiring a platform descriptor record list;
a collection module for collecting single FRU data;
a generating module, configured to generate platform descriptor record information corresponding to the FRU data according to the FRU data and add 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. A data interaction device is applied to a BMC (baseboard management controller) end and comprises:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is used for receiving a platform descriptor record list, and the platform descriptor record list is a platform descriptor record list recorded by a single FRU data collected by a Host end;
the searching module is used for searching a target identifier corresponding to 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 according to any one of claims 1 to 6 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the data interaction according to any one of claims 1 to 6.
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 true CN114138509A (en) | 2022-03-04 |
| CN114138509B 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)
| 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 |
-
2021
- 2021-11-18 CN CN202111370714.8A patent/CN114138509B/en active Active
Patent Citations (5)
| 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 |
|---|---|
| CN114138509B (en) | 2023-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107220142B (en) | Method and device for executing data recovery operation | |
| CN108845930B (en) | Interface operation test method and device, storage medium and electronic device | |
| CN102866961A (en) | Memory transfer with extended data and user privacy protection | |
| CN107800757B (en) | User behavior recording method and device | |
| CN110532056B (en) | Control identification method and device applied to user interface | |
| CN109101412B (en) | Test file generation method, test file generation device, test file testing method, test file testing device, storage medium and computer equipment | |
| US9213759B2 (en) | System, apparatus, and method for executing a query including boolean and conditional expressions | |
| CN103902543A (en) | Database inquiry method and device and database system | |
| CN110352410A (en) | Track the access module and preextraction index node of index node | |
| CN106453544B (en) | Cloud environment and monitoring method and system thereof | |
| CN106897063B (en) | Method and system for permanently adding OS boot entry to BIOS based on EFI | |
| CN114138509B (en) | Data interaction method and device and computer readable storage medium | |
| CN111290915A (en) | Multipath equipment shielding system, method, equipment and readable storage medium | |
| CN110955562A (en) | Data recovery method, system, equipment and readable storage medium | |
| CN115328736A (en) | Probe deployment method, device, equipment and storage medium | |
| CN113703753B (en) | Method and device for product development and product development system | |
| KR20110023580A (en) | The method and system for recovering data | |
| CN115481025A (en) | Script recording method and device for automatic test, computer equipment and medium | |
| CN111399759B (en) | Method for reading data and writing data and object file system | |
| CN114610577A (en) | Target resource locking method, device, equipment and medium | |
| CN105188154B (en) | A kind of method, apparatus and system being automatically brought into operation smart machine | |
| CN113656378A (en) | Server management method, device and medium | |
| CN113687920A (en) | Object strategy operation method, device and equipment of distributed system | |
| CN107818136B (en) | Method and device for recycling garbage object data | |
| CN112559478B (en) | Log generation method and device, terminal equipment and storage medium |
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 |