CN109739535B - Method and system for performing drive maintenance on product - Google Patents

Method and system for performing drive maintenance on product Download PDF

Info

Publication number
CN109739535B
CN109739535B CN201811629063.8A CN201811629063A CN109739535B CN 109739535 B CN109739535 B CN 109739535B CN 201811629063 A CN201811629063 A CN 201811629063A CN 109739535 B CN109739535 B CN 109739535B
Authority
CN
China
Prior art keywords
product
source
model
driver
products
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
CN201811629063.8A
Other languages
Chinese (zh)
Other versions
CN109739535A (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.)
Zhengzhou Yunhai Information Technology Co Ltd
Original Assignee
Zhengzhou Yunhai Information 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 Zhengzhou Yunhai Information Technology Co Ltd filed Critical Zhengzhou Yunhai Information Technology Co Ltd
Priority to CN201811629063.8A priority Critical patent/CN109739535B/en
Publication of CN109739535A publication Critical patent/CN109739535A/en
Application granted granted Critical
Publication of CN109739535B publication Critical patent/CN109739535B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Stored Programmes (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application discloses a method and a system for performing drive maintenance on a product, wherein the method comprises the following steps: selecting a source model product and a plurality of associated model products from a plurality of products of different models driven by the same driver; establishing a product association relation between the source type number product and any associated type number product; and driving and upgrading the source type number product according to the product association relation. The system for performing drive maintenance on a product comprises: the system comprises a source model and associated model setting module, a product associated module and a drive upgrading module. By the method and the system, the drive maintenance efficiency of the server for driving products of different models in the same way can be greatly improved.

Description

Method and system for performing drive maintenance on product
Technical Field
The present application relates to the technical field of website driving maintenance, and in particular, to a method and a system for driving maintenance of a product.
Background
With the development of cloud computing and big data, the storage and processing amount of data in a server system is continuously increased, and correspondingly, the driving amount of product models on various component official networks of the server is also continuously increased. When any product is upgraded, the driver of the product needs to be upgraded and maintained.
At present, a method for performing drive maintenance on products with the same drive and different models on a website generally maintains all drive contents of the products one by one model. Specifically, the drive content is maintained under the model A, and the product with the model A is maintained; and then maintaining the same driving content under the model B, maintaining the product with the model B, and so on until the maintenance of all the models of products under the same driving content is finished.
However, in the current method for performing drive maintenance on products with the same drive and different models on a website, because the same drive content needs to be repeatedly maintained under different models, the drive maintenance takes longer time, and the drive maintenance efficiency is lower.
Disclosure of Invention
The application provides a method and a system for driving and maintaining products, which aim to solve the problem that in the prior art, the driving and maintaining efficiency of the same driving different models of products is low.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method for performing drive maintenance on products, which is applied to the products with different models and the same drive of a server, comprises the following steps:
selecting a source model product and a plurality of associated model products from a plurality of products of different models driven by the same driver;
establishing a product association relation between the source type number product and any associated type number product;
and driving and upgrading the source type number product according to the product association relation.
Optionally, the method for establishing a product association relationship between the source model product and any associated model product includes:
maintaining drivers for all components in a source type number product, the drivers including: a source driver file, a source component type, and a source operating system;
synchronizing the drivers of all the components in the source model product to any relevant model product;
deleting the source component type under any associated model product, and acquiring a pseudo driver of any associated model product;
acquiring associated component types, wherein the associated component types are the component types of all components in any associated model product;
and maintaining the associated component types in the pseudo driver, and acquiring the driver of any associated model product.
Optionally, the method for maintaining the associated component type in the pseudo driver and obtaining the driver of the product of any associated model includes:
and importing the associated component type into a pseudo driver of any associated model product to obtain the driver of any associated model product.
Optionally, the number of components in the source model product is equal to the number of components in any associated model product.
A system for performing drive maintenance on products, which is applied to the products with different models and the same drive of a server, and comprises:
the source model and associated model setting module is used for selecting a source model product and a plurality of associated model products from a plurality of products with the same drive and different models;
the product association module is used for establishing a product association relationship between the source type number product and any associated type number product;
and the drive upgrading module is used for carrying out drive upgrading on the source type number product according to the product association relation.
Optionally, the product association module includes:
the source type number driving and maintaining unit is used for maintaining a driving program of all parts in a source type number product, and the driving program comprises: a source driver file, a source component type, and a source operating system;
the synchronization unit is used for synchronizing the drivers of all the components in the source type product to any relevant type product;
a deleting unit, configured to delete the source component type under any associated model product, and obtain a pseudo driver of the any associated model product;
the related component type obtaining unit is used for obtaining related component types, wherein the related component types are the component types of all components in any related model product;
and the associated component maintenance unit is used for maintaining the associated component type in the pseudo driver and acquiring the driver of any associated model product.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the application provides a method for driving and maintaining products, which is applied to the products with different models driven by the same server. The method comprises the steps of firstly, selecting a source model product and a plurality of related model products from a plurality of products with the same drive and different models; then, establishing a product association relation between the source type number product and any associated type number product; and finally, when the driver is upgraded, the driver upgrading is carried out on the source type product according to the established product association relation, and the driver upgrading of all the associated type products can be realized. Therefore, after the method in the application is adopted to establish product association between the source type number product and each associated type product, when drive upgrading is needed, the drive upgrading of all associated type products under the same drive file can be realized only by changing the drive file of the source type number product, and the efficiency of product drive maintenance can be greatly improved. In addition, only the drive file of the source type number product needs to be changed, so that the operation items are fewer, the maintenance operation error is reduced, and the drive maintenance accuracy is improved.
The application also provides a system for driving and maintaining the products, and the system is applied to the products with the same drive and different models of the server. The system mainly comprises: the system comprises a source model and associated model setting module, a product associated module and a drive upgrading module. Through the source model and the associated model setting module, one product can be selected from a plurality of products with the same drive and different models to serve as a source model product, so that the drive file maintenance can be conveniently carried out subsequently, and products with the same drive except the source model product can be selected to serve as associated model products. Through the product association module, the product association relationship between the source type number product and any associated type number product can be established, so that the association function between the source type number product and any associated type number product is realized. And the source model product is subjected to drive upgrading by using the drive upgrading module, so that the drive upgrading of any relevant model product is realized. By the system, when the drive file is updated, the drive update of all associated model products of the same drive can be realized by only updating the source model drive file and utilizing the association relation, and the maintenance efficiency of the website drive can be effectively improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for performing drive maintenance on a product according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating the principle of performing drive maintenance on products of the same drive and different models in the embodiment of the present application;
fig. 3 is a schematic structural diagram of a system for performing drive maintenance on a product according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, 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 of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In a server product, there is often a case where a plurality of products employ the same drive. When the drive of the server product is updated, the drive update needs to be performed on the service organ network for all products under the drive. The method for updating the drive of the product under the same drive is adopted, and the drive update of all the products under the same drive can be realized only by performing the drive update on one product under the same drive.
For a better understanding of the present application, embodiments of the present application are explained in detail below with reference to the accompanying drawings.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart of a method for performing drive maintenance on a product according to an embodiment of the present application. As can be seen from fig. 1, the method for performing drive maintenance on products of the same drive and different models in the server in this embodiment mainly includes the following steps:
s1: a source model product and a plurality of associated model products are selected among a plurality of products of different models driven identically.
The products in this embodiment are related products in a server, and one source model product or any one related model product includes: display card, chip, network card, RAID card and other parts. And the source model product and any one relevant model product have the same drive and different models.
According to step S1, a model a is established as a source model product, and assuming that the model a includes different components such as a video card, a network card, and a RAID card, the model a is referred to in this embodiment as being composed of the video card, the network card, and the RAID card.
Other models B, C, D … …, etc. are created as associated model products, each of which in turn includes different components. The number of components in the source model product is equal to the number of components in any associated model product in this embodiment. Each associated model product is associated with a source model product.
S2: and establishing a product association relation between the source type number product and any associated type number product.
Specifically, step S2 includes the following process:
s21: the drivers for all components in the source model product are maintained. Wherein, the driver program includes: a source driver file, a source component type, and a source operating system.
In this embodiment, the source model product includes a plurality of components, and the driver of the source model product includes a source driver file, a source component type, and a source operating system. Each component in the source model product, in turn, has its own driver.
Specifically, if the first part, the second part, the third part, and up to the nth part are included in the source type product, the first part includes a first source driver file, a first source part type, and a first source operating system therein; the second component comprises a second source driver file, a second source component type and a second source operating system; and in the same way, the Nth component comprises the Nth source drive file, the Nth source component type and the Nth source operating system.
S22: drivers for all components in the source model product are synchronized to any associated model product.
And copying the drivers of all the components in the source type number product to any associated type number product, wherein the driver of any associated type number product is completely consistent with the driver of the source type number product, and the component type matched by the driver is the component type in the source type number product.
S23: and deleting the source component type under any associated model product, and acquiring the pseudo driver of any associated model product.
And deleting the source component type under any associated model product, only reserving the source drive file, the source operating system and the association relationship between the source drive file and the source operating system, and defining the drive program under any associated model product as a pseudo drive program.
S24: and acquiring the associated component type, wherein the associated component type is the component type of all components in any associated model product.
S25: and maintaining the associated component types in the pseudo driver, and acquiring the driver of any associated model product.
The specific method for maintaining the associated component type in the pseudo driver is as follows:
and importing the associated component type into a pseudo driver of any associated model product to obtain the driver of any associated model product.
As can be seen from the above steps S22-S25, in the present embodiment, when the association relationship between the source model product and any associated model product is established, only the drive file of the source model, the operating system and the association relationship thereof are synchronized to the associated model, and the component types of the source model are not synchronized, so that the association between the same drive and different model products can be realized.
After the product association relationship is established between the source model product and any associated model product, when the drivers of a plurality of products are upgraded, step S3 is executed: and driving and upgrading the source type number product according to the product association relation.
When the drivers of a plurality of products are upgraded, the drivers of all the products can be upgraded only by maintaining the drivers of the source type number products, so that the maintenance efficiency of the website driver can be greatly improved.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating a principle of performing drive maintenance on products of the same drive and different models in the embodiment of the present application. In fig. 2, model a is used as a source model product, model B is an associated model product, and it is assumed that model a includes different components, i.e., a video card a1, a network card a2, and a RAID card a3, in this embodiment, model a is referred to as being composed of a1, a2, and a3, model B also includes the same number of components, and model B is referred to as being composed of B1, B2, and B3.
As shown in fig. 2, in the present embodiment, a model a is first established, where a is composed of a1, a2, a3, and the drivers of a1, a2, a3 all include driver files, component types, and operating systems. Second, model B is established. When the product is selected to be associated with the model B, the driver of the a1 and the association relation are copied to the model B, the component type in the copied content is deleted, only the driver file, the operating system and the association relation of the a1 are reserved, and a dummy B1 is formed. In the same way, a2 and a3 were converted to b2 and b3, respectively. At this time, only the model B is formed by the dummy B1, the dummy B2 and the dummy B3 which retain the drive files, the operating systems and the association relations, the component type of the model B is established under the model B, the component type of the model B is led into the dummy B1, the dummy B2 and the dummy B3, and the complete associated model B is formed by the drive files, the component types and the operating systems which completely contain all the components in the model B, the B1, the B2, the B3, the B1, the B2 and the B3. Because the association relationship is reserved between the driver files and the operating system, when the driver files or the operating system are upgraded for a1, a2 and a3 under the source type A, the driver files or the operating system of the synchronously associated type B can be synchronously changed, so that the driver program is quickly maintained, the maintenance time is saved, and the maintenance efficiency is improved.
Example two
Referring to fig. 3 on the basis of the embodiments shown in fig. 1 and fig. 2, fig. 3 is a schematic structural diagram of a system for performing drive maintenance on a product according to an embodiment of the present application. As can be seen from fig. 3, the system for performing drive maintenance on a product in this embodiment mainly includes: the system comprises a source model and associated model setting module, a product associated module and a drive upgrading module.
The system comprises a source model and associated model setting module, a source model and associated model setting module and a source model and associated model setting module, wherein the source model and associated model setting module is used for selecting a source model product and a plurality of associated model products from a plurality of products with the same drive and different models; the product association module is used for establishing a product association relation between the source type number product and any associated type number product; and the drive upgrading module is used for carrying out drive upgrading on the source type number product according to the product association relation.
Further, the product association module includes: the device comprises a source type number driving maintenance unit, a synchronization unit, a deletion unit, an associated component type acquisition unit and an associated component maintenance unit. The source type number driving maintenance unit is used for maintaining driving programs of all parts in a source type number product, and the driving programs comprise: a source driver file, a source component type, and a source operating system. The synchronization unit is used for synchronizing the drivers of all the components in the source model product to any relevant model product. The deleting unit is used for deleting the source component type under any associated model product and acquiring the pseudo driver of any associated model product. And the associated component type acquisition unit is used for acquiring the associated component types, wherein the associated component types are the component types of all the components in any associated model product. And the associated component maintenance unit is used for maintaining the associated component type in the pseudo driver and acquiring the driver of any associated model product.
The working principle and the working method of the system for performing drive maintenance on a product in this embodiment have already been explained in detail in the first embodiment shown in fig. 1 and fig. 2, and are not described again here.
In summary, taking the model a as the source model and the model B as the associated model as an example, the embodiment synchronizes all the drivers and the association relationships of the model a to the model B through the synchronization unit; secondly, deleting the component type of the content synchronized to the model B by using a deleting unit, only keeping a drive file, an operating system and the association relation of the drive file and the operating system, and acquiring a pseudo drive program of the model B; then, a related component type obtaining unit is used for newly building a component type of the model B, and the component type of the model B is led into a pseudo driver of the model B only keeping a drive file, an operating system and a related relation of the operating system through a related component maintenance unit, so that a driver of the model B is obtained; finally, when the driver is upgraded, the driver upgrading module is used for changing the driver file or the operating system of the model A, and the corresponding driver file or the operating system of the model B can be synchronously changed. Therefore, the system in the embodiment can greatly improve the efficiency and the accuracy of website driving maintenance.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (3)

1. A method for performing drive maintenance on products, which is applied to the same server for driving different models of products, is characterized by comprising the following steps:
selecting a source model product and a plurality of associated model products from a plurality of products of different models driven by the same driver;
establishing a product association relation between the source type number product and any associated type number product;
driving and upgrading the source type number product according to the product association relation;
the method for establishing the product association relationship between the source model product and any associated model product comprises the following steps:
maintaining drivers for all components in a source type number product, the drivers including: a source driver file, a source component type, and a source operating system;
synchronizing the drivers of all the components in the source model product to any relevant model product;
deleting the source component type under any associated model product, and acquiring a pseudo driver of any associated model product;
acquiring associated component types, wherein the associated component types are the component types of all components in any associated model product;
maintaining the associated component types in the pseudo driver, and acquiring the driver of any associated model product;
the method for maintaining the associated component type in the pseudo driver and acquiring the driver of any associated model product specifically comprises the following steps:
and importing the associated component type into a pseudo driver of any associated model product to obtain the driver of any associated model product.
2. The method of claim 1, wherein the number of components in the source model product is equal to the number of components in any associated model product.
3. A system for performing drive maintenance on products, which is applied to the same server for driving different models of products, and is characterized in that the system comprises:
the source model and associated model setting module is used for selecting a source model product and a plurality of associated model products from a plurality of products with the same drive and different models;
the product association module is used for establishing a product association relationship between the source type number product and any associated type number product;
the drive upgrading module is used for carrying out drive upgrading on the source type number product according to the product association relation;
wherein the product association module comprises:
the source type number driving and maintaining unit is used for maintaining a driving program of all parts in a source type number product, and the driving program comprises: a source driver file, a source component type, and a source operating system;
the synchronization unit is used for synchronizing the drivers of all the components in the source type product to any relevant type product;
a deleting unit, configured to delete the source component type under any associated model product, and obtain a pseudo driver of the any associated model product;
the related component type obtaining unit is used for obtaining related component types, wherein the related component types are the component types of all components in any related model product;
the associated component maintenance unit is used for maintaining the associated component type in the pseudo driver and acquiring the driver of any associated model product;
the method for the associated component maintenance unit to maintain the associated component type in the pseudo driver and obtain the driver of any associated model product includes: and importing the associated component type into a pseudo driver of any associated model product to obtain the driver of any associated model product.
CN201811629063.8A 2018-12-28 2018-12-28 Method and system for performing drive maintenance on product Active CN109739535B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811629063.8A CN109739535B (en) 2018-12-28 2018-12-28 Method and system for performing drive maintenance on product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811629063.8A CN109739535B (en) 2018-12-28 2018-12-28 Method and system for performing drive maintenance on product

Publications (2)

Publication Number Publication Date
CN109739535A CN109739535A (en) 2019-05-10
CN109739535B true CN109739535B (en) 2022-02-18

Family

ID=66361957

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811629063.8A Active CN109739535B (en) 2018-12-28 2018-12-28 Method and system for performing drive maintenance on product

Country Status (1)

Country Link
CN (1) CN109739535B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102232304A (en) * 2011-05-04 2011-11-02 华为终端有限公司 Method, system and terminal for system update between mobile communication terminals
CN103942078A (en) * 2014-04-30 2014-07-23 华为技术有限公司 Method for loading driver and embedded device
CN206805462U (en) * 2017-05-19 2017-12-26 郑州云海信息技术有限公司 A kind of hot-swappable component controls protection device
CN107861803A (en) * 2017-10-31 2018-03-30 湖北三江航天万峰科技发展有限公司 Cpci bus RS422 communications driving method under a kind of XP systems based on interruption
CN107967550A (en) * 2017-05-31 2018-04-27 北京空间技术研制试验中心 Product data assure reason system and method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070185969A1 (en) * 2005-08-19 2007-08-09 Davis Wayne R Drive with Server
US10007491B2 (en) * 2014-12-18 2018-06-26 Software Ag Usa, Inc. Systems and/or methods for cloud-based event-driven integration

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102232304A (en) * 2011-05-04 2011-11-02 华为终端有限公司 Method, system and terminal for system update between mobile communication terminals
CN103942078A (en) * 2014-04-30 2014-07-23 华为技术有限公司 Method for loading driver and embedded device
CN206805462U (en) * 2017-05-19 2017-12-26 郑州云海信息技术有限公司 A kind of hot-swappable component controls protection device
CN107967550A (en) * 2017-05-31 2018-04-27 北京空间技术研制试验中心 Product data assure reason system and method
CN107861803A (en) * 2017-10-31 2018-03-30 湖北三江航天万峰科技发展有限公司 Cpci bus RS422 communications driving method under a kind of XP systems based on interruption

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
工序模型驱动的航空发动机零件机加夹具变型设计方法;黄斌达;《航空学报》;20170131;第1-3节 *

Also Published As

Publication number Publication date
CN109739535A (en) 2019-05-10

Similar Documents

Publication Publication Date Title
CN108074177B (en) Data reconciliation method, system and computer-readable storage medium
JP6521402B2 (en) Method for updating data table of KeyValue database and apparatus for updating table data
CN112019369A (en) Dynamic configuration management method and system under micro-service framework
CN104423960A (en) Continuous project integration method and continuous project integration system
CN104572689A (en) Data synchronizing method, device and system
CN108446315B (en) Big data migration method, device, equipment and storage medium
CN104426955A (en) Processing method of shared file, and cloud storage server
CN110162334B (en) Code management method, device and storage medium
CN104636286A (en) Data access method and equipment
CN104065752A (en) Synchronization method of data between terminals
CN104462477A (en) Data synchronizing method, device and system based on timestamp
CN106775498A (en) A kind of data cached synchronous method and system
CN112507020A (en) Data synchronization method and device, computer equipment and storage medium
CN111782235A (en) Data upgrading and querying method and device
CN104092726A (en) Automatic replacing method and apparatus of same-name file
CN102857949A (en) Method and device for planning data consistency guarantees
CN109656595A (en) The method, apparatus and system that client-side program updates
CN110704122A (en) Plug-in loading method and device
CN105338107A (en) Stronghold operation synchronous management system and stronghold operation synchronous management method
CN109617950B (en) Data updating method, device, equipment and readable storage medium
CN111090803A (en) Data processing method and device, electronic equipment and storage medium
CN114064073A (en) Software version upgrading method and device, computer equipment and storage medium
CN112689170B (en) Content playing method of display terminal, display terminal and readable storage medium
CN103955498A (en) Search engine creating method and device
CN106484792B (en) A kind of data power supply management method and device for Persistence Layer Framework

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