CN111092765A - Intelligent driving method, system, electronic device and readable storage medium - Google Patents
Intelligent driving method, system, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN111092765A CN111092765A CN201911323651.3A CN201911323651A CN111092765A CN 111092765 A CN111092765 A CN 111092765A CN 201911323651 A CN201911323651 A CN 201911323651A CN 111092765 A CN111092765 A CN 111092765A
- Authority
- CN
- China
- Prior art keywords
- protocol
- driver
- equipment
- matched
- information
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- 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/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Abstract
The application provides an intelligent driving method, an intelligent driving system, an electronic device and a readable storage medium, wherein each installed-driver instance and a corresponding protocol channel are created according to information of a plurality of pre-registered installed drivers, the driving capability of the device is detected through the protocol channels when the device is on line, the installed-driver instance matched with the device is detected, the corresponding relation between the matched installed-driver instance and the device is further established, the matched installed-driver instance is called, and service configuration is issued to the device through the corresponding protocol channel. Therefore, the compatibility of various drives is realized, different network controllers do not need to be configured for different devices, the device cost of network networking is saved, and the uniform management of the devices in the network becomes possible to a certain extent. In addition, the scheme of the application has good expandability, and when new equipment needs to be connected, only corresponding drivers need to be newly installed and registered.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an intelligent driving method, an intelligent driving system, an electronic device, and a readable storage medium.
Background
At present, most network networking systems have network devices of different manufacturers, different models and different versions, and the different devices often adopt different communication protocols and different control modes.
In a network, a network controller needs to manage and control all devices in the network to implement a service function, but at present, it is not possible to implement a general device driver that is compatible with all devices and capable of communicating and controlling with all devices, so that different network controllers need to be configured for different devices in an actual use process, which brings difficulty to uniform management of devices in the network.
Disclosure of Invention
An object of the embodiments of the present application is to provide an intelligent driving method, an intelligent driving system, an electronic device, and a readable storage medium, so as to solve the problem that it is difficult to perform unified management on devices in a network because different network controllers need to be configured for different devices in an existing network.
The embodiment of the application provides an intelligent driving method, which comprises the following steps:
creating an instance of each installed driver and a corresponding protocol channel according to information of a plurality of kinds of installed drivers registered in advance;
when the equipment is on line, detecting the driving capability of the equipment through the protocol channel so as to detect an installed driving example matched with the equipment;
establishing a corresponding relation between the matched instances of the installed drivers and the equipment;
and calling the matched installed drive example, and issuing service configuration to the equipment through a corresponding protocol channel.
In the implementation process, each installed-driver instance and a corresponding protocol channel are created according to information of a plurality of pre-registered installed drivers, and when the device is on line, the driving capability of the device is detected through the protocol channels to detect the installed-driver instance matched with the device, so that the corresponding relation between the matched installed-driver instance and the device is established, the matched installed-driver instance is called, and service configuration is issued to the device through the corresponding protocol channel. Therefore, the compatibility of various drives can be realized through the scheme of the embodiment of the application, different network controllers do not need to be configured for different devices, the device cost of network networking is saved, and the uniform management of the devices in the network is possible to a certain extent. In addition, the scheme of the embodiment of the application has good expandability, and when new equipment needs to be connected, only corresponding drivers need to be newly installed and registered, so that the method and the device can adapt to various network application scenes.
Further, the information of the installed driver includes: drive type and protocol information; the creating of each instance of the installed driver and the corresponding protocol channel includes: and creating an instance which meets the driver type and the protocol information of the installed driver and a protocol channel required by the instance of the installed driver.
In the implementation process, the information of the installed driver includes the driver type and the protocol information, so that the created protocol channel meeting the requirements of the instance of the driver type and the protocol information of the installed driver and the instance of the installed driver can effectively implement the detection on whether the device supports the driver type of the protocol information, thereby improving the reliability of the scheme of the embodiment of the application.
Further, the detecting the driving capability of the device through the protocol channel includes: sending a detection message encapsulated by a protocol corresponding to the protocol channel to the equipment through the protocol channel; and when receiving an identification notice returned by the equipment, determining that the instance of the installed driver corresponding to the protocol channel is matched with the equipment.
In the implementation process, the detection message encapsulated by the protocol is sent through the corresponding protocol channel, and if the equipment can identify the detection message, the equipment supports the driving instance corresponding to the protocol channel; otherwise, it indicates that the device does not support the driving instance corresponding to the protocol channel. Therefore, the device capability is effectively detected, and the reliability of the scheme of the embodiment of the application is improved.
Further, the protocol information includes a communication protocol and a protocol version.
It should be appreciated that as communication technologies continue to evolve, new versions of certain communication protocols are also continually pushed out, which results in different devices targeting the same protocol, possibly some supporting new versions of the protocol and some supporting older versions of the protocol. In order to improve the compatibility of the scheme of the present application, in the implementation process, both the communication protocol and the protocol version may be used as protocol information and placed in the information of the installed driver. Therefore, different protocol versions can correspond to different installed drivers, and during detection, the capacity of the equipment can be detected according to different protocol versions, so that which version of communication protocol is supported by the equipment is determined, and the reliability of the scheme is further improved.
Further, the information of the installed driver includes a unique identifier; the establishing of the corresponding relationship between the matched instances of the installed drivers and the equipment comprises: and associating and storing the matched unique identifier of the installed driver and the unique identifier of the equipment.
In the implementation process, after the installed driver matched with the equipment is detected, the unique identifier of the matched installed driver and the unique identifier of the equipment can be stored in a correlated mode (namely mounting is carried out), so that when communication is carried out, the driving information corresponding to the equipment can be accurately known according to the unique identifier of the installed driver and the unique identifier of the equipment which are stored in a correlated mode, and then the driving instance corresponding to the driving information is used for communication, so that the reliability of the scheme of the application is improved.
The embodiment of the present application further provides an intelligent driving system, including: the device comprises a preprocessing module, a driving capability detection module and a management module;
the preprocessing module is used for creating each installed driver instance and a corresponding protocol channel according to the information of various pre-registered installed drivers;
the driving capability detection module is used for detecting the driving capability of the equipment through the protocol channel when the equipment is on line so as to detect an example of the installed driver matched with the equipment;
the management module is used for establishing the corresponding relation between the matched instances of the installed drivers and the equipment; and calling the matched installed drive example, and issuing service configuration to the equipment through a corresponding protocol channel.
In the implementation process, automatic drive detection can be realized only by pre-installing and registering the drives of various devices, so that the installed drives supported by the connected devices are detected, and communication with the devices can be realized according to the detected matched installed drive examples. Therefore, the compatibility of various drives can be realized through the scheme of the embodiment of the application, different network controllers do not need to be configured for different devices, the device cost of network networking is saved, and the uniform management of the devices in the network is possible to a certain extent. In addition, the scheme of the embodiment of the application has good expandability, and when new equipment needs to be connected, only corresponding drivers need to be newly installed and registered, so that the method and the device can adapt to various network application scenes.
Further, the preprocessing module is further configured to scan and register all installed drivers when the intelligent drive system is started, so as to obtain information of a plurality of registered installed drivers.
In the implementation process, when the intelligent driving system is started, the intelligent driving system automatically drives and registers, so that the automatic detection of the capability of the equipment needing to communicate can be realized after the intelligent driving system is started, the situation that the equipment needing to communicate is on line is avoided, but the driving and registering are not reached, the communication cannot be carried out, and the reliability of the scheme is further improved.
Further, the information of the installed driver includes a unique identifier; the management module is specifically configured to store the matched unique identifier of the installed driver and the unique identifier of the device in an associated manner.
The embodiment of the application also provides electronic equipment, which comprises a processor, a memory and a communication bus; the communication bus is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement any of the intelligent driving methods described above.
Also provided in an embodiment of the present application is a readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the intelligent driving method of any one of the above.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of an intelligent driving method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an intelligent driver system, an SDN controller, and a network device according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an intelligent driving system according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The first embodiment is as follows:
the embodiment of the present application provides an intelligent driving method, which can be seen in fig. 1, and the intelligent driving method includes:
s101: creating an instance of each installed driver and a corresponding protocol channel according to information of a plurality of kinds of installed drivers registered in advance;
in the embodiment of the present application, the drivers may include an interface driver, an Access Control List (ACL) driver, a Quality of Service (QOS) driver, and the like, and each driver needs to be implemented by a corresponding protocol.
It should be noted that the solutions provided in the embodiments of the present application may be applied to a network controller, or may be applied to an electronic device that is connected to the network controller and is capable of helping the network controller to implement communication with devices in a network. For convenience of description, in the embodiments of the present application, an electronic device to which the scheme provided by the embodiments of the present application can be applied is described as an intelligent driving system.
In the embodiment of the application, various types of drivers can be installed in the intelligent driving system in advance, and when the intelligent driving system is used, all installed drivers are scanned in advance for registration, so that information of various installed drivers is obtained through registration in advance. For example, the intelligent drive system may be registered when the intelligent drive system is started, that is, all installed drives are scanned, so as to ensure the execution reliability of the intelligent drive system for the solution provided by the embodiment of the present application.
It should be noted that an instance of a driver (also referred to as a driver implementation, or driver implementation class in some documents) may correspond to a specific driver and may be called to implement communication with a device. In the embodiment of the present application, each instance of an installed driver is created, so that after the instance of the installed driver matched with the device is detected, the detected instance can be called, and after the instance of the installed driver is called, encapsulation and analysis of a corresponding protocol data packet can be realized, thereby realizing data communication.
S102: when the equipment is on line, the driving capability of the equipment is detected through the protocol channel so as to detect the installed driving example matched with the equipment.
In the embodiment of the application, when the device comes online, the driver information supported by the device needs to be detected, so that a matched driver instance is selected from installed drivers to realize communication between the network controller and the device. In order to detect the drivers supported by the online device, a protocol channel corresponding to each installed driver needs to be created first, and then the drivers (i.e., the driving capabilities) supported by the device are detected according to the protocol channels corresponding to the installed drivers, so that the communication with the device can be realized through the detected instances of the drivers supported by the online device.
In the embodiment of the present application, the information of the pre-registered installed driver may include a driver type and protocol information. The protocol channel created in step S101 should be a protocol channel that satisfies the driver type and protocol information requirements in the installed driver, and the instance of each installed driver created in step S101 should be an instance that satisfies the driver type and protocol information of the installed driver.
In the embodiment of the present application, the Protocol channels that can be created include, but are not limited to, NETCONF (Extensible Markup Language-based network configuration Protocol) channels, SNMP (simple network Management Protocol) channels, SSH (Secure Shell, remote login security Protocol) channels, and the like.
In the embodiment of the present application, the driving capability of the device may be detected by sending a corresponding detection message. For example, a probe packet encapsulated by the protocol information corresponding to the protocol channel may be sent to the device through the protocol channel. If the device can identify the detection message, an identification notification can be returned to the intelligent driving system, at this time, the device supports the driver corresponding to the protocol channel, and the driver corresponding to the protocol channel can be determined to be matched with the device. After the drivers supported by the equipment are detected, the instance of the installed driver matched with the equipment can be determined according to the corresponding relation between each driver and the created instance.
In the foregoing example, one possible way is that if the identification notification returned by the device is not received after the preset time period, the device may be considered not to support the driving corresponding to the protocol channel.
S103: and establishing the corresponding relation between the matched instance of the installed driver and the equipment.
In the embodiment of the present application, in order to improve the stability of the subsequent communication process, after detecting the drivers supported by the device, the device may be mounted, that is, a corresponding relationship between the matched instances of the installed drivers and the device is established. For example, a unique identifier may be configured in an installed driver, and after driving information supported by the device is detected, the unique identifier of the installed driver, which is matched with the device, is associated with the unique identifier of the device for storage, so that in a subsequent process, a corresponding driver instance may be quickly invoked according to the association relationship to implement data communication.
It should be noted that, in a possible implementation manner of the embodiment of the present application, after the device is offline or the protocol channel between the device and the device is disconnected, if the device is online again or the protocol channel is reestablished, it is necessary to confirm the driving information again, that is, to perform driving capability detection again, because it is not possible to confirm whether the device that is reconnected is the original device. In order to avoid conflict between the re-mount and the information mounted before the reconnection after the re-drive detection, the mounted drive information of the device (i.e. the unique identifier of the mounted drive matching with the device and the unique identifier of the device stored in association with each other) may be deleted (i.e. the uninstall operation is performed). Therefore, after the device is re-online or the protocol channel is re-established, the driving capability of the device is re-detected according to the scheme of the embodiment of the application and re-mounted, so that the risk of protocol management disorder is reduced while the memory space of the system is saved.
Of course, it should be understood that in a possible implementation manner of the embodiment of the present application, the unique identifier of the device may be a unique identifier that is sent by the device and is not changed by the device, such as a motherboard UUID (universal unique identifier) of the device. In this feasible embodiment, after the device goes offline or the protocol channel between the device and the device is disconnected, the device may also create a corresponding protocol channel according to the mounted driving information for the next device that goes online, and perform driving capability detection on the device through the protocol channel, without deleting the mounted driving information of the device. If the detection result is that the equipment supports the installed drive corresponding to the protocol channel, the unique identification of the equipment can be obtained through the protocol channel and is compared with the unique identification of the equipment in the mounted drive information, and if the unique identification of the equipment is consistent with the unique identification of the equipment in the mounted drive information, the mounted drive information is reserved, and mounting is not required to be carried out again; if the detection result is that the device does not support the installed driver corresponding to the protocol channel, or supports the installed driver corresponding to the protocol channel, but the obtained unique identifier of the device is different from the unique identifier of the device in the mounted drive information, the mounted drive information may be deleted, and mounting operation may be performed for the device.
However, it should be understood that the unique identifier may also be a unique identifier assigned to the device by the intelligent drive system, and after the drive information of the mounted device is deleted, if the device is newly online or the protocol channel is reestablished, the unique identifier may be reassigned, and the unique identifier reassigned may be different from the unique identifier before the uninstalling operation is performed. It should be understood that the unique identifier assigned to the device by the intelligent drive system only needs to satisfy that the unique identifier does not exist in the mounted information when the unique identifier is assigned.
It should be noted that, with the development of communication technology, some communication protocols are continuously pushed out of new versions, which results in that in the practical application process, different devices are directed to the same protocol, and some may support new versions of the protocol, and some may support old versions of the protocol. In order to improve the compatibility of the solution of the present application, in the embodiment of the present application, the protocol information in the information of the aforementioned installed driver may include a communication protocol and a protocol version. It should be understood that the difference in any one of the information contained in the information of the two installed drives results in the difference between the two installed drives. Therefore, different protocol versions can correspond to different installed drivers, and during detection, the capacity of the equipment can be detected according to the installed drivers of different protocol versions, so that which communication protocol of which version is supported by the equipment is determined, and the reliability of the scheme of the application is further improved. The communication protocol included in the protocol information is a protocol name.
It should be noted that, in practical applications, there may be a case where one device can support a plurality of kinds of drive information. In this embodiment of the present application, corresponding priority information may be configured in advance in each installed driver, so that, of the installed drivers that match the device, an instance of the installed driver with the highest priority communicates with the device.
For example, during probing, a corresponding protocol channel may be created for all installed drivers to probe, and after all probing is completed, an installed driver with the highest priority is selected from the probed installed drivers to communicate with the device. It should be noted that, at this time, the device may be mounted with all the supported drive information thereof (i.e., the unique identifier of the device is stored in association with the unique identifiers of all the installed drives supported by the device), but the device may also be mounted with only the selected installed drive (i.e., the unique identifier of the device is stored in association with the unique identifier of the installed drive with the highest priority among all the installed drives supported by the device).
In addition, during the detection, the driving capabilities of the devices may be detected in sequence from high to low in priority of each installed driver, and when the first installed driver supported by the device is detected, the priority of the installed driver is necessarily the highest priority among the installed drivers supported by the device, and at this time, the detection is not continued, and the installed driver may communicate with the device.
It should be noted that, in the embodiment of the present application, the communication operation that can be performed with the device includes, but is not limited to, an operation of issuing a service configuration to the device.
S104: and calling the matched instance of the installed driver, and issuing service configuration to the equipment through a corresponding protocol channel.
It should be understood that when the matching installed driver instance is invoked to issue a service configuration to the device through the corresponding protocol channel, the corresponding protocol channel needs to be reserved and maintained to ensure that data can interact normally.
In summary, the intelligent driving method provided by the embodiment of the application can realize compatibility of multiple types of driving, does not need to configure different network controllers for different devices, saves the device cost of network networking, and makes uniform management of devices in a network possible to a certain extent. In addition, the scheme of the embodiment of the application has good expandability, and when new equipment needs to be connected, only corresponding drivers need to be newly installed and registered, so that the method and the device can adapt to various network application scenes.
Example two:
in this embodiment, based on the first embodiment, ACL driving is taken as an example to further illustrate the present application.
It should be noted that, in the embodiment of the present application, the intelligent drive system is disposed in an electronic device that is independent from the Network controller, and the Network controller is an SDN (Software Defined Network) controller. Referring to fig. 2, the intelligent driving system is connected with the SDN controller through a standard northbound interface, and realizes communication with devices in the network through a protocol channel.
Assume that the ACL driver provided in the embodiment of the present application implements a NETCONF 1.0-based driver, a NETCONF 1.1-based driver, an SNMP 1.0-based driver, and an SSH 1.0-based driver in advance, and is installed in a driver system directory of an intelligent driver system. When the intelligent driving system is started, namely, the directory of the driving system is automatically scanned for driving registration, and the following registered information of installed drivers is obtained:
watch 1
Watch two
| Type of drive | IACLdriver (ACL drive) |
| Communication protocol | NETCONF |
| Protocol version | 1.1 |
| Driving priority | 1 |
| Driving example | com.driver.acl.AclDriverNetconfV11 |
| Drive ID | 2 |
Watch III
| Type of drive | IACLdriver (ACL drive) |
| Communication protocol | SNMP |
| Protocol version | 1.0 |
| Driving priority | 2 |
| Driving example | com.driver.acl.AclDriverSnmpV10 |
| Drive ID | 3 |
Watch four
| Type of drive | IACLdriver (ACL drive) |
| Communication protocol | SSH |
| Protocol version | 1.0 |
| Driving priority | 3 |
| Driving example | com.driver.acl.AclDriverSshV10 |
| Drive ID | 4 |
In the embodiment of the present application, it is assumed that the other drivers are not pre-installed, and if the information of the installed driver registered by pre-installing the other drivers is similar to the above expression, it should be noted that the driver ID of each installed driver is globally unique. It should be noted that, in the embodiment of the present application, the smaller the driving priority value is, the higher the priority is.
It is assumed that there are a device a with ID 1 and a device B with ID 2, where the device a supports NETCONF1.0 protocol and the device B supports SNMP1.0 protocol. After the devices a and B are on-line, according to the registered information of each installed driver, through each created protocol channel, capability detection is performed on the devices a and B, the protocol and version of each driver supported by the devices a and B are identified, the association relationship between the device ID and the driver ID is registered, and the mounting of the driver is completed, wherein the registered information is shown in the following table five:
watch five
| Device ID | Drive ID |
| 1 | 1 |
| 2 | 3 |
When the SDN controller needs to issue an ACL policy to the equipment A, an ACL driving interface IACLriver of the intelligent driving system is called, the intelligent driving system can acquire a driving ID of 1 according to the ID of the equipment A, and then the information of the installed driver with the driving ID of 1 can be known according to the registered information, as shown in the first table.
As can be seen from table one, the intelligent drive system finally calls com.driver.acll.aclldrivernetconf v10 implementation classes to provide NETCONF1.0 protocol to complete the issuance of the ACL policy.
Similarly, when the SDN controller needs to issue an ACL policy to the device B, the intelligent drive system ACL drive interface IACLDriver is called, the intelligent drive system can obtain a drive ID of 3 according to the ID of the device B, and then can know the information of the installed drive with the drive ID of 3 according to the registered information, as shown in the foregoing table three.
As can be seen from table three, the intelligent drive system finally calls com.driver.acll.aclldriversnmpv10 implementation classes to provide SNMP1.0 protocol to complete the issuance of the ACL policy.
By the scheme, the SDN controller and the equipment in the network are decoupled by the intelligent driving system, details of communication with the equipment do not need to be concerned by upper-layer application, and the upper-layer application development process is simplified. In addition, the intelligent driving system selects proper driving and mounting, the compatibility of the system to different devices is enhanced, and the system can well control the complex network environment. In addition, the intelligent driving system can easily and flexibly increase the driving of new equipment, and has good expandability.
Example three:
based on the same inventive concept, the embodiment of the present application further provides an intelligent driving system 100. Referring to fig. 3, fig. 3 illustrates an intelligent drive system using the method of fig. 1. It should be understood that the specific functions of the intelligent drive system 100 can be referred to the above description, and the detailed description is omitted here as appropriate to avoid redundancy. The smart drive system 100 includes at least one software functional module that can be stored in a memory in the form of software or firmware or solidified in an operating system of the smart drive system 100.
Specifically, the method comprises the following steps:
referring to fig. 3, the smart driving system 100 includes: a preprocessing module 101, a driving capability detection module 102 and a management module 103;
the preprocessing module 101 is configured to create, according to information of a plurality of installed drivers registered in advance, instances of the installed drivers and corresponding protocol channels;
the driving capability detection module 102 is configured to, when a device is online, perform driving capability detection on the device through the protocol channel to detect an installed-driver instance matching the device;
the management module 103 is configured to establish a corresponding relationship between the matched instances of the installed driver and the device; and calling the matched installed drive example, and issuing service configuration to the equipment through a corresponding protocol channel.
In one possible implementation of the embodiment of the present application, the information of the installed driver includes: drive type and protocol information; the preprocessing module 101 is specifically configured to create a protocol channel that satisfies the instance of the driver type and protocol information of the installed driver, and the requirements of the instance of the installed driver.
In the above feasible implementation manner, the driving capability detection module 102 is specifically configured to send a detection packet encapsulated by a protocol corresponding to a protocol channel to a device through the protocol channel; and when receiving the identification notification returned by the equipment, determining that the instance of the installed driver corresponding to the protocol channel is matched with the equipment.
In the above possible embodiment, the protocol information includes a communication protocol and a protocol version. .
In a possible implementation manner of the embodiment of the present application, the preprocessing module 101 is further configured to scan and register all installed drivers when the intelligent drive system is started, so as to obtain information of a plurality of registered installed drivers.
In one possible implementation of the embodiments of the present application, the information of the installed driver includes a unique identifier. The management module 103 is specifically configured to associate and store the matched unique identifier of the installed driver and the unique identifier of the device, and complete the mounting of the driver.
In a possible implementation manner of the embodiment of the present application, the management module 103 is further configured to delete the unique identifier of the installed driver and the unique identifier of the device, which are stored in an associated manner and matched with the device, when the device is offline.
In a possible implementation manner of the embodiment of the present application, the installed driver includes priority information; when detecting a plurality of installed drivers matching the device, the management module 103 is specifically configured to communicate with the device using an installed driver with the highest priority among the detected installed drivers.
It should be understood that, for the sake of brevity, the contents described in some embodiments are not repeated in this embodiment.
Example four:
the present embodiment provides an electronic device, which is shown in fig. 4 and includes a processor 401, a memory 402, and a communication bus 403. Wherein:
the communication bus 403 is used to enable connection communication between the processor 401 and the memory 402.
The processor 401 is configured to execute one or more first programs stored in the memory 402 to implement the intelligent driving method in the first embodiment.
It will be appreciated that the configuration shown in fig. 4 is merely illustrative and that the electronic device may include more or fewer components than shown in fig. 4 or have a different configuration than shown in fig. 4. For example, the electronic device may be a network controller, or an auxiliary device connected between the network controller and the network device. In addition, it is understood that the electronic device should have a data communication interface, which can realize data interaction between different devices.
The present embodiment also provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash Memory, a usb (secure digital Card), an MMC (Multimedia Card), etc., in which one or more programs for implementing the above steps are stored, and the one or more programs can be executed by one or more processors to implement the intelligent driving method in the first embodiment. And will not be described in detail herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be 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.
In this context, a plurality means two or more.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. An intelligent driving method, comprising:
creating an instance of each installed driver and a corresponding protocol channel according to information of a plurality of kinds of installed drivers registered in advance;
when the equipment is on line, detecting the driving capability of the equipment through the protocol channel so as to detect an installed driving example matched with the equipment;
establishing a corresponding relation between the matched instances of the installed drivers and the equipment;
and calling the matched installed drive example, and issuing service configuration to the equipment through a corresponding protocol channel.
2. The intelligent driving method according to claim 1, wherein the information of the installed driver comprises: drive type and protocol information;
the creating of each instance of the installed driver and the corresponding protocol channel includes:
and creating an instance which meets the driver type and the protocol information of the installed driver and a protocol channel required by the instance of the installed driver.
3. The intelligent driving method of claim 2, wherein the probing of the driving capability of the device through the protocol channel comprises:
sending a detection message encapsulated by a protocol corresponding to the protocol channel to the equipment through the protocol channel;
and when receiving an identification notice returned by the equipment, determining that the instance of the installed driver corresponding to the protocol channel is matched with the equipment.
4. The intelligent driving method according to claim 2 or 3, wherein the protocol information includes a communication protocol and a protocol version.
5. The intelligent driving method according to claim 2 or 3, wherein the information of the installed driver includes a unique identifier;
the establishing of the corresponding relationship between the matched instances of the installed drivers and the equipment comprises:
and associating and storing the matched unique identifier of the installed driver and the unique identifier of the equipment.
6. An intelligent drive system, comprising: the device comprises a preprocessing module, a driving capability detection module and a management module;
the preprocessing module is used for creating each installed driver instance and a corresponding protocol channel according to the information of various pre-registered installed drivers;
the driving capability detection module is used for detecting the driving capability of the equipment through the protocol channel when the equipment is on line so as to detect an example of the installed driver matched with the equipment;
the management module is used for establishing the corresponding relation between the matched instances of the installed drivers and the equipment; and calling the matched installed drive example, and issuing service configuration to the equipment through a corresponding protocol channel.
7. The intelligent drive system according to claim 6, wherein the preprocessing module is further configured to scan and register all installed drives when the intelligent drive system is started, so as to obtain information of the registered multiple installed drives.
8. The intelligent drive system according to claim 6 or 7, wherein the information of the installed drive includes a unique identification;
the management module is specifically configured to store the matched unique identifier of the installed driver and the unique identifier of the device in an associated manner.
9. An electronic device, comprising: a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the intelligent drive method of any of claims 1-5.
10. A readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the smart driving method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911323651.3A CN111092765B (en) | 2019-12-19 | 2019-12-19 | Intelligent driving method, system, electronic device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911323651.3A CN111092765B (en) | 2019-12-19 | 2019-12-19 | Intelligent driving method, system, electronic device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111092765A true CN111092765A (en) | 2020-05-01 |
| CN111092765B CN111092765B (en) | 2022-11-08 |
Family
ID=70396158
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911323651.3A Active CN111092765B (en) | 2019-12-19 | 2019-12-19 | Intelligent driving method, system, electronic device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111092765B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116155721A (en) * | 2022-12-30 | 2023-05-23 | 珠海奔图电子有限公司 | Port configuration method, device, storage medium and computer equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080276010A1 (en) * | 2007-05-04 | 2008-11-06 | Fuchs Michael A | System and method for implementing and/or operating network interface devices to achieve network-based communications |
| CN104753746A (en) * | 2013-12-30 | 2015-07-01 | 华为技术有限公司 | Device accessing method and control server |
| CN104932926A (en) * | 2015-07-09 | 2015-09-23 | 上海联彤网络通讯技术有限公司 | System and method for achieving dynamic matching of equipment and drives in intelligent operation system platform |
| CN105379198A (en) * | 2014-06-11 | 2016-03-02 | 华为技术有限公司 | Forwarding control method, driver and SDN |
| CN105610615A (en) * | 2015-12-29 | 2016-05-25 | 国网辽宁省电力有限公司 | Method and system for dispatching power distribution network based on software-defined network |
| CN107528919A (en) * | 2017-09-25 | 2017-12-29 | 江苏英索纳智能科技有限公司 | The method and device that a kind of lan device is found and driver is installed automatically |
| US20180288726A1 (en) * | 2017-03-31 | 2018-10-04 | Futurewei Technologies, Inc. | Active Position Driven Mobility Content Delivery in Information Centric Networks |
| CN108989066A (en) * | 2017-05-31 | 2018-12-11 | 中兴通讯股份有限公司 | device management method and device |
| CN109040178A (en) * | 2018-06-22 | 2018-12-18 | 北京星网锐捷网络技术有限公司 | Configuration information transmitting method and device |
-
2019
- 2019-12-19 CN CN201911323651.3A patent/CN111092765B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080276010A1 (en) * | 2007-05-04 | 2008-11-06 | Fuchs Michael A | System and method for implementing and/or operating network interface devices to achieve network-based communications |
| CN104753746A (en) * | 2013-12-30 | 2015-07-01 | 华为技术有限公司 | Device accessing method and control server |
| CN105379198A (en) * | 2014-06-11 | 2016-03-02 | 华为技术有限公司 | Forwarding control method, driver and SDN |
| CN104932926A (en) * | 2015-07-09 | 2015-09-23 | 上海联彤网络通讯技术有限公司 | System and method for achieving dynamic matching of equipment and drives in intelligent operation system platform |
| CN105610615A (en) * | 2015-12-29 | 2016-05-25 | 国网辽宁省电力有限公司 | Method and system for dispatching power distribution network based on software-defined network |
| US20180288726A1 (en) * | 2017-03-31 | 2018-10-04 | Futurewei Technologies, Inc. | Active Position Driven Mobility Content Delivery in Information Centric Networks |
| CN108989066A (en) * | 2017-05-31 | 2018-12-11 | 中兴通讯股份有限公司 | device management method and device |
| CN107528919A (en) * | 2017-09-25 | 2017-12-29 | 江苏英索纳智能科技有限公司 | The method and device that a kind of lan device is found and driver is installed automatically |
| CN109040178A (en) * | 2018-06-22 | 2018-12-18 | 北京星网锐捷网络技术有限公司 | Configuration information transmitting method and device |
Non-Patent Citations (2)
| Title |
|---|
| HASAN M. JAMIL: "Improving Integration Effectiveness of ID Mapping Based Biological Record Linkage", 《 IEEE/ACM TRANSACTIONS ON COMPUTATIONAL BIOLOGY AND BIOINFORMATICS》 * |
| 刘登诚: "嵌入式Linux设备驱动程序开发技术的研究", 《中国优秀硕士学位论文数据库》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116155721A (en) * | 2022-12-30 | 2023-05-23 | 珠海奔图电子有限公司 | Port configuration method, device, storage medium and computer equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111092765B (en) | 2022-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101989205B (en) | Software system upgrading method for universal serial bus (USB) equipment | |
| EP3043261A1 (en) | Software installation method, device and system | |
| US20070204069A1 (en) | Port number emulation for wireless usb connections | |
| CN101930411B (en) | Information processing apparatus, and method for controlling the same | |
| CN111143256B (en) | Method and device for reading field replaceable unit information | |
| US20100261464A1 (en) | Mobile terminal, associated storage devices and methods of using the same | |
| EP2611226A1 (en) | Processing method and system for over-the-air bootstrap | |
| EP3208723A1 (en) | Usb wireless network card configuration method, host, usb wireless network card and communication system | |
| US20140273973A1 (en) | Method and system for replacing key deployed in se of mobile terminal | |
| CN107566518A (en) | The method and apparatus of management equipment information during installation file | |
| US10078532B2 (en) | Resource management method and device for terminal system among multiple operating systems | |
| CN111092765B (en) | Intelligent driving method, system, electronic device and readable storage medium | |
| CN109787789B (en) | Compatibility management method, device and equipment for software upgrading and storage medium | |
| US20170094353A1 (en) | System and method for sharing bluetooth hardware | |
| CN112231251B (en) | Board card slot identification method and device, communication equipment and readable storage medium | |
| CN111209125B (en) | Multi-process command line implementation method | |
| CN101593282B (en) | Image forming apparatus performing user authentication using a card | |
| KR101264315B1 (en) | Method, apparatus and record carrier for interworking between applications on a mobile platform | |
| CN110943975B (en) | Service registration method, device, computer equipment and storage medium | |
| US9870217B2 (en) | Toolkit event configuration of applets on a card computing device with installation parameters | |
| US9332374B2 (en) | Communication interface method for SE equipped on mobile terminal and SE using the same | |
| CN115993979A (en) | Configuration conversion method, smooth upgrading method, device, equipment and storage medium | |
| US8171183B2 (en) | Information processing apparatus and program and method for setting identification information | |
| CN112579165A (en) | Batch operation execution method and device, readable medium and electronic equipment | |
| CN115918116A (en) | Information processing method, device 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 |