CN109412830B - Method and device for curing internet card name, computer equipment and storage medium - Google Patents
Method and device for curing internet card name, computer equipment and storage medium Download PDFInfo
- Publication number
- CN109412830B CN109412830B CN201811031779.8A CN201811031779A CN109412830B CN 109412830 B CN109412830 B CN 109412830B CN 201811031779 A CN201811031779 A CN 201811031779A CN 109412830 B CN109412830 B CN 109412830B
- Authority
- CN
- China
- Prior art keywords
- name
- network card
- network
- card
- network interface
- 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
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/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3005—Mechanisms for avoiding name conflicts
Abstract
The invention relates to a method and a device for curing network card names, computer equipment and a storage medium, which are applied to a network connection technology. The method comprises the following steps: acquiring a unique identifier of a network card to be solidified in a system as an equipment identifier; acquiring a first name of the network card to be solidified through a preset mapping table; the first name is a curing interface name corresponding to the equipment identifier in the mapping table; determining that the first name is not occupied by a registered network card; and setting the network interface name of the network card to be solidified as the first name. The embodiment of the invention solves the problem of low efficiency of the existing mode of network card name solidification, and is beneficial to ensuring the network communication stability of the system.
Description
Technical Field
The invention relates to the technical field of network connection, in particular to a method and a device for curing network card names, computer equipment and a storage medium.
Background
In an embedded system, in order to meet communication between the embedded system and an external network, one or more network cards are generally required to be arranged, and one or more local area networks can be constructed by expanding the network cards, so that the embedded system meets more complex application scenarios.
In the process of implementing the present invention, the inventor finds that, taking a linux system as an example, network interface names of network cards included in the linux system have randomness, and when the system is applied to performing communication, it is necessary to preset a network interface thereof, such as eth0 for external network connection, eth1 for communicating with the internal communication lan1, eth2 for communicating with the internal communication lan 2, and the like, and if the network interface names of the network cards are not fixed, the system application may use the network cards that do not correspond to the network cards, resulting in abnormal communication. In order to solve the problem, a common method is to modify network interface names of network cards one by one to be expected names in an ip command mode after all the network cards in the system are initialized, and the mode causes low effective efficiency of network card name solidification.
Disclosure of Invention
In view of the above, it is necessary to provide a method, an apparatus, a computer device and a storage medium for network card name solidification, which solve the problem of low efficiency of network card name solidification in the prior art.
According to a first aspect of the present invention, there is provided a method for curing a network card name, comprising:
acquiring a unique identifier of a network card to be solidified in a system as an equipment identifier;
acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
determining that the first name is not occupied by a registered network card;
and setting the network interface name of the network card to be solidified as the first name.
In one embodiment, the determining that the first name is not occupied by a registered network card further includes:
traversing the registered equipment chain aiming at the first name, and judging whether the network interface name of the network card in the equipment chain is the same as the first name or not; the equipment chain comprises a network card which is registered currently and a network interface name thereof;
and if the network interface name of any network card in the equipment chain is different from the first name, determining that the first name is not occupied by the registered network card.
In one embodiment, the determining that the first name is not occupied by a registered network card further includes:
querying a preset variable aiming at the first name; the variable comprises n bits, and the value of n is equal to the total amount of network cards which can be accessed by the system; each bit in the variable is used for marking whether the n network interface names are registered currently;
if the value of bit corresponding to the first name in the variable is a first set value, determining that the first name is not occupied by the registered network card;
and if the value of bit corresponding to the first name in the variable is a second set value, determining that the first name is occupied by the registered network card.
In one embodiment, the method further comprises:
determining that the first name is occupied by a registered network card;
acquiring a conflict network card; the conflict network card is a registered network card, and the name of the network interface of the conflict network card is the same as the first name;
modifying the network interface name of the conflict network card into a second name;
and after the network interface name of the conflict network card is modified to a second name, setting the network interface name of the network card to be solidified as the first name.
In one embodiment, the modifying the network interface name of the conflicting network card to a second name further includes:
acquiring a second name; the second designation satisfies the condition: not occupied by a registered network card and not identical to the first designation.
In one embodiment, the modifying the network interface name of the conflicting network card to a second name includes:
changing the system network state into a temporary storage state;
calling a target function, wherein when the target function is called, the target function is used for modifying the network interface name of the conflict network card into a second name and synchronizing the network interface name modified by the conflict network card to each association point of a system kernel space;
and restoring the network state of the system.
In one embodiment, the setting the network interface name of the network card to be cured as the first name includes:
and assigning the network interface name variable of the network card to be solidified as the first name.
In one embodiment, the system is a linux kernel-based operating system; the network card to be solidified is an expansion network card;
the acquiring of the unique identifier of the network card to be cured in the system includes: and acquiring a busid identifier of the network card to be solidified in the operating system.
In one embodiment, the method further comprises:
setting a first mapping relation between a network card and a curing interface name;
obtaining a second mapping relation between the equipment identifier and the curing interface name according to the first mapping relation and the equipment identifier corresponding to the network card;
establishing a mapping table according to the second mapping relation;
and storing the mapping table.
According to a second aspect of the present invention, there is provided an apparatus for curing a name of an internet card, comprising:
the identification acquisition module is used for acquiring the unique identification of the network card to be solidified in the system as the equipment identification;
the name acquisition module is used for acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
the first confirmation module is used for determining that the first name is not occupied by the registered network card;
and the name curing module is used for setting the network interface name of the network card to be cured as the first name.
In one embodiment, the method further comprises:
the equipment chain checking module is used for traversing the network card equipment chain aiming at the first name and judging whether the network interface name of the network card in the network card equipment chain is the same as the first name or not; the network card equipment chain comprises a currently registered network card and a network interface name thereof;
the first confirmation module is specifically configured to determine that the first name is not occupied by the registered network card if the network interface name of any network card in the network card device chain is different from the first name.
In one embodiment, the method further comprises:
the variable checking module is used for inquiring preset variables aiming at the first name; the variable comprises n bits, and the value of n is equal to the total amount of network cards which can be accessed by the system; each bit in the variable is used for marking whether the n network interface names are registered currently;
the second confirmation module is used for determining that the first name is occupied by the registered network card if the value of bit corresponding to the first name in the variable is a second set value;
the first confirmation module is specifically configured to determine that the first name is not occupied by the registered network card if the value of bit corresponding to the first name in the variable is a first set value.
In one embodiment, the method further comprises:
the second confirmation module is used for determining that the first name is occupied by the registered network card;
the conflict acquisition module is used for acquiring a conflict network card; the conflict network card is a registered network card, and the name of the network interface of the conflict network card is the same as the first name;
the name modification module is used for modifying the network interface name of the conflict network card into a second name;
the name curing module is specifically configured to set the network interface name of the to-be-cured network card as the first name after the network interface name of the conflicting network card is modified to the second name.
In one embodiment, the method further comprises:
a modified name determining module for obtaining a second name; the second designation satisfies the condition: not occupied by a registered network card and not identical to the first designation.
In one embodiment, the name modification module includes:
the temporary storage unit is used for changing the system network state into a temporary storage state;
the function calling unit is used for calling a target function, and when the target function is called, the function calling unit is used for modifying the network interface name of the conflict network card into a second name and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space;
and the recovery unit is used for recovering the system network state.
In one embodiment, the method further comprises:
the first mapping relation establishing module is used for setting a first mapping relation between the network card and the curing interface name;
the second mapping relation establishing module is used for obtaining a second mapping relation between the equipment identifier and the curing interface name according to the first mapping relation and the equipment identifier corresponding to the network card;
the mapping table establishing module is used for establishing a mapping table according to the second mapping relation;
and the mapping table storage module is used for storing the mapping table.
According to a third aspect of the present invention, there is provided a computer device comprising a memory, a display screen with touch functionality and a processor; the memory for storing a computer program; the computer program, when executed by the processor, causes the processor to implement the steps of the method for network card name curing of any of the above embodiments.
According to a fourth aspect of the present invention, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of web name curing as in any of the embodiments described above.
The embodiment provided by the invention is implemented, the only identification of the network card in the system is taken as the equipment identification, and the preset mapping table is inquired based on the equipment identification to obtain the target solidification interface name of the network card; further, whether the target curing interface name is occupied by other network cards or not can be determined, and if the target curing interface name is not occupied, the network interface name of the network card is directly set as the target curing interface name. By the technical scheme, the network interface name of the network card is solidified based on the kernel space, and the method is different from the traditional technical scheme of modifying the network interface name based on the user space, and can improve the effective efficiency of the network card.
Further, according to some embodiments, if the target cured interface name is occupied by the registered network card, the network interface name of the network card does not need to be modified until all the network cards are initially finished, so that the problem of abnormal communication caused by the fact that the network interface names in a period of time are not corresponding is solved.
Furthermore, through some embodiments, a mapping table containing a mapping relationship between the device identifier and the network interface name is constructed, so that the configuration of the network card name solidification is flexible, and the network card name solidification can adapt to systems of different network architectures.
Drawings
FIG. 1 is a diagram of a system architecture in which the method for Netscard name curing is used in one embodiment;
FIG. 2 is a schematic flow chart diagram of a method for web card name curing in one embodiment;
FIG. 3 is a schematic flow chart diagram of a method of NIC name curing in another embodiment;
FIG. 4 is a schematic flow chart diagram of modifying the network interface name of a registered network card, according to an embodiment;
FIG. 5 is a diagram illustrating the result of variable tagging according to one embodiment;
FIG. 6 is a schematic diagram illustrating an application scenario of a method for Internet card name solidification according to an embodiment;
FIG. 7 is a schematic block diagram of an apparatus for Netscard name curing in one embodiment;
FIG. 8 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The method for curing the network card name provided by the application can be applied to a multi-network card access system as shown in fig. 1, wherein the multi-network card access system comprises a main controller, and the main controller is used for accessing an external network and/or constructing a local area network; further, the main controller includes a built-in network card 0 (generally an ethernet card), and the internet can be accessed through the network card 0; in addition, the system also comprises a plurality of external network cards which are expanded through USB interfaces, for example, the network cards comprise a network card 1, a network card 2, network cards 3 and … … and a network card n, and the main controller can construct a plurality of local area networks through the external network cards. Both the built-in network card and the expansion network card are hardware devices.
The main controller runs an operating system based on a Linux kernel, such as an android system. The operating system can be divided into a kernel space and a user space, wherein the kernel space is a core part of the system, has a plurality of most basic functions, is responsible for managing processes, memories, device drivers, files and network systems of the system, is mainly used for running system kernel codes and codes closely related to hardware, and determines the performance and stability of the system. The user space is used for running a plurality of user-level application programs, the application programs cannot use certain specific system functions, cannot directly access hardware equipment, cannot directly access kernel space, each application program or process has a specific address and a specific private data space, and the programs cannot be influenced mutually generally. The kernel space may communicate with the user space through a system call interface. From the safety perspective, the user space and the kernel space are arranged under the asymmetric access mechanism, the snooping of malicious users can be resisted, and the invasion of user programs with poor quality can also be prevented, so that the system can run more stably and reliably.
In embodiments, the kernel space of the operating system may also communicate with the hardware device through a kernel driver.
In addition, in the embodiment, all hardware devices can be found in the/sys/bus/usb/devices path of the kernel space, that is, the above-mentioned internal network card and the expansion network card can be found in the/sys/bus/usb/devices path of the kernel space.
Further, the multi-network card access system may be embedded in a virtual electronic device, which may be a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, a game console, an interactive smart tablet, a wearable device, a smart car, an unmanned automobile, a smart refrigerator, other smart home devices, or a combination of any of these devices. Various applications required by the user can be installed in the electronic equipment, such as a text editing application, a manuscript presentation application, an instant messaging application, an image editing application, a social contact application, an e-commerce application, a search application, a browser application and the like. The system comprises a text editing application program, a document demonstration application program, an instant messaging application program and a video conference application program, wherein the text editing application program comprises an electronic whiteboard application and an electronic blackboard application, the document demonstration application program comprises a wireless screen projection application, and the instant messaging application program comprises a video conference application.
In the embodiment, an interactive smart tablet is taken as an example of an electronic device for description, where the interactive smart tablet may be an integrated device that controls content displayed on a display tablet and implements human-computer interaction operations through a touch technology, and integrates one or more functions of a projector, an electronic whiteboard, a curtain, a sound, a television, a video conference terminal, and the like.
In one embodiment, as shown in fig. 2, a method for curing a network card name is provided, which can be applied to the multi-network card access system shown in fig. 1, and specifically includes the following steps:
and S110, acquiring the unique identifier of the network card to be solidified in the system as the equipment identifier.
The network card to be solidified can be understood as a network card which is not provided with a network interface name; specifically, the network card to be cured may be a built-in network card to be cured, or may be an expansion network card to be cured.
In an operating system based on a Linux kernel, each device is identified by a unique busid; and in the case that the physical circuit is fixed, the busid corresponding to the device is uniquely fixed. Therefore, for the ethernet card and each usb expansion network card, there is a unique busid in the system for identification, and the respective busid is fixed.
In some embodiments, the unique identifier of the network card in the system can be obtained by looking at the system device, for example, by the path:/sys/bus/usb/devices, and the busid of the corresponding network card in the system is obtained as the device identifier.
S120, acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relationship between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table.
In an embodiment, the cured interface name may be understood as a network interface name that a user desires a certain network card to be cured. Based on the network interface name, the application program in the user space can access the corresponding network card to access an external network or construct a local area network.
S130, determining that the first name is not occupied by the registered network card.
In an embodiment, when the network interface name of a certain registered network card is the same as the first name, it is determined that the first name is occupied by the registered network card, and if the network interface name of any one registered network card is different from the first name, it may be determined that the first name is not occupied by the registered network card.
S140, setting the network interface name of the network card to be solidified as the first name.
In an embodiment, if the first name is not occupied by the registered network card, the network interface name variable of the network card to be solidified may be assigned as the first name. Then, the network card and the corresponding network interface name are registered in the system kernel space, and the application program in the user space can access the network card through the network interface name.
According to the embodiment, the only identification of the network card in the system is used as the equipment identification, and the preset mapping table is inquired based on the equipment identification to obtain the target solidified interface name of the network card; further, whether the target curing interface name is occupied by other network cards or not can be determined, and if the target curing interface name is not occupied, the network interface name of the network card is directly set as the target curing interface name. By the technical scheme, the network interface name of the network card is solidified based on the kernel space, and the effective efficiency of the network card can be improved unlike the traditional technical scheme of modifying the network interface name based on the user space.
In addition, in the conventional method of modifying and curing the network interface names through the user space (such as a standard ip command), the network interface names of the network cards can be modified one by one after all the network cards are initially completed, so that the network communication stability of the system is affected when the network interface names of a period of time do not correspond to the network cards. By the method for curing the network card name, the network card name is cured based on the kernel space, and the condition that the network interface name does not correspond to the network card within a period of time does not exist, so that the network communication stability of the system can be ensured.
With continued reference to the multi-network card access system shown in fig. 1, the method for curing the network card name of the above embodiment is further described by a specific example.
In the multi-network card access system shown in fig. 1, it is assumed that the user desires the network interface names of the network cards to be fixed according to the fixed interface names (i.e., the network interface names desired to be fixed) shown in table 1 according to the actual application logic.
Table 1:
| network card | Solidified interface |
| Network card | |
| 1 | |
| Network card | |
| 2 | |
| Network card | |
| 3 | |
| Network card | |
| 4 | eth2 |
| …… | …… |
| Network card n | ethX |
In an embodiment, as shown in table 1, the network cards that the user desires to cure include network card 1, network cards 2, …, and network card n; the name of the cured interface of the network card 1 is eth3, the name of the cured interface of the network card 2 is eth1, and the name of the cured interface of the network card 3 is eth0, which is specifically shown in table 1.
It should be noted that the network card and the corresponding cured interface name shown in table 1 are only an example, and in other cases, the user may also construct a mapping relationship between other network cards and cured interface names, so that the network card corresponds to other cured interface names.
Under the condition that a unique and fixed device identifier of each network card in the system is obtained, the mapping relationship between the network card and the curing interface name shown in the table 1 is combined, so that the mapping relationship between the curing interface name and the busid shown in the table 2 can be obtained.
Table 2:
it should be noted that the mapping relationship between the curing interface name and the busid shown in table 2 is only an example, and in other cases, based on table 1 set by the user and the unique and fixed device identifier of the network card in the system, other forms of mapping relationships between the curing interface name and the busid may also be constructed.
After the mapping relationship in table 2 is determined, a network card driver is loaded based on the system kernel space, and further, the network interface name of the network card can be solidified according to the following method. Referring to fig. 3, the method for curing the network interface name of the network card may include the following processes:
step S310, setting the mapping relation between the solidified interface name and the busid, and constructing a mapping table.
The specific form of the mapping table can refer to the above table 2, and the constructed mapping table is stored.
In addition, in some embodiments, in the system kernel space, the driver needs to be matched and bound with the corresponding device in advance, that is, in this embodiment, the network card driver is matched and bound with the network card. The specific implementation mode can refer to a matching binding method of the kernel driver and the corresponding network card equipment of the existing Android system.
In an embodiment, after the network card driver and the network card are matched and bound, the information of the mapping table may be recorded through a preset array, that is, the mapping relationship between the fixed interface name and the busy in the mapping table may be recorded through the array. For example:
the mapping relation between 5 curing interface names and the busid is recorded in the array force _ phy _ table, wherein 'RESERVED',/eth 0 represents the mapping relation between the RESERVED busid and the 'eth 0' of the curing interface name, '3-1.3: 1.0',/eth 1 represents the mapping relation between the busid '3-1.3: 1.0' and the 'eth 1' of the curing interface name, and so on.
Furthermore, ethi may be denoted by the index i of the array force _ phy _ table. For example, busid is 3-1.3:1.0, the index of the array is 1, which can be expressed as force _ phy _ table [1], and the name of the curing interface corresponding to the network card is eth 1; for example, busid is 3-1.2:1.0, the index of the array is 3, which may be represented as force _ phy _ table [3], and the name of the curing interface corresponding to the network card is eth 3. Of course, the curing interface name of the wireless network card may also be defined according to the rules of wlan x, for example, the network card with busid of 3-1.3:1.0, the corresponding curing interface name may also be wlan1, the network card with busid of 3-1.2:1.0, and the corresponding curing interface name may also be wlan 3.
Step S320, obtaining the busid of the network card to be cured.
The busid of the network card in the system can be obtained through the path,/sys/bus/usb/devices.
And step S330, acquiring the curing interface name of the network card to be cured according to the busid and the mapping table.
Step S340, determining whether the cured interface name is occupied by the registered network card.
In an embodiment, an implementation of the process may include:
and traversing the currently registered equipment chain aiming at the solidified interface name, wherein the equipment chain comprises the currently registered network card and the network interface name thereof. The devices in the device chain are all network devices that have been registered in the kernel with network interface names such as: ethX, wlan X, lo, etc.
Through traversal, detecting whether a registered network card exists in the device chain, wherein the network interface name of the registered network card is the same as the solidified interface name (in the embodiment, such a registered network card is also referred to as a conflict network card); if the conflict network card exists, the step S350 is entered, and if the conflict network card does not exist, the step S360 is entered.
Step S350: confirming that the curing interface name is occupied by other network cards, modifying the network interface name of the registered network card (i.e. the conflict network card) occupying the curing interface name into other network interface names, and then executing the step S360 to set the network interface name of the current network card to be cured as the curing interface name.
In an embodiment, if the network interface name of any network card in the device chain is different from the curing interface name, it is determined that the curing interface name is not occupied by the registered network card, otherwise, it is determined that the curing interface name is occupied by the registered network card.
In some embodiments, whether the cured interface name is occupied by other registered network cards is confirmed, the cured interface name can be obtained by querying preset variables, n variables of bits can be generated for n default names of n network cards when the system is initialized, and the variables are used for recording whether the current n default names are registered in real time. The following "traversal mark" method may be specifically adopted:
first, a variable of n bits is initialized for n default names (eth0, eth1, …, ethn-1) of n network cards.
Secondly, traversing the currently registered equipment chain aiming at the (k + 1) th default name ethk in the n network cards, detecting whether the network interface name of the registered network card is the same as the ethk, recording the traversal result of the ethk by using the (k + 1) th bit of the variable, and regarding the (k + 1) th bit, 0 represents that the name ethk is not occupied, and 1 represents that the name ethk is occupied. For example, for 16 default names of 16 network cards, a 16-bitd variable is generated, the traversal marking result recorded by the variable is shown in fig. 5, the bit numbered i +1 records the traversal result of the ith default name (ethi), for example, the bit numbered 4 records the traversal result of the 3 rd default name (eth3), which indicates that the name eth3 is not occupied by other current network cards.
After acquiring the busid of the network card to be cured in step S320, the curing interface name of the network card to be cured may be obtained based on the mapping table or the array, and whether the curing interface name is occupied by other network cards may be obtained by querying the variable of the n bits. For example, if the curing interface name of the network card to be cured is eth3, the 4 th bit of the variable of the n bits is inquired, and if the bit is 0, it indicates that the curing interface name eth3 is not occupied by other network cards currently; if the bit is 1, it indicates that the fixed interface name eth3 is currently occupied by other network cards, in this case, the interface name of the registered network card with the network interface name eth3 needs to be modified first.
Through setting up the preset variable to corresponding the occupied condition of naming for real-time recording through each bit of presetting the variable, after obtaining the busid of the network card of treating the solidification, can directly inquire and preset the variable, can obtain the condition that the solidification interface name of treating the solidification network card is occupied fast, need not to traverse the equipment chain temporarily, be favorable to improving the interface name solidification efficiency of treating the solidification network card.
In some embodiments, referring to fig. 4, step S350 may further include:
and step 53, modifying the network interface name of the conflict network card.
It should be noted that modifying the network interface name of the conflicting network card is not simply modifying the value of a name variable (a variable used for representing the network interface name), and the name variable may permeate through the entire network card drive, and must be modified through a specific function of the system kernel, and synchronize the modified network interface name to each association point of the kernel, otherwise it is easy to cause an exception.
Therefore, in some embodiments, the implementation manner of step 53 is to invoke a target function of the system kernel, and when the target function is invoked, the target function may be used to modify the network interface name of the conflicting network card to the second name, and synchronize the modified network interface name of the conflicting network card to each association point of the network card driver; wherein the second naming satisfies the condition: the network card is not occupied by the registered network card and has a curing interface name different from that of the network card to be cured.
And step 54, restoring the original state of the network interface state, and unlocking the system resource, for example, unlocking the system resource through the UNLOCK interface operation.
The temporary storage and recovery of the network interface state are completed in the kernel driver, the kernel for changing the state value of the network interface state is provided with a standard interface, and the interface state value is transmitted through parameters.
RTNL _ LOCK/UNLOCK is an action which needs to be added when the linux kernel space calls the standard interface operation, and the purpose is to protect resources.
In one embodiment, before step 53, the method further comprises: the second name (available network interface) is obtained, and then step 53 is executed to modify the network interface name of the conflict network card by using the obtained available network interface name.
In some embodiments, the obtaining of the second name may be obtained by querying the preset variable, for example, if the curing interface name of the network card to be cured is eth3, querying a 4 th bit of the preset variable, where the bit is 1, which indicates that the curing interface name eth3 is currently occupied by other network cards, and in this case, obtaining a bit of 0, for example, a 2 nd bit, in the preset variable, so that it can be known that the name eth1 corresponding to the 2 nd bit is not currently occupied by other network cards, and therefore eth1 may be used as the second name, and the network interface name of the conflicting network card is eth 1.
Step S360, the network interface name of the network card to be cured is named as the curing interface name.
In an embodiment, the network interface name variable of the network card to be cured may be assigned as the curing interface name, so as to implement curing of the network interface of the network card to be cured.
Step S370: after the step S360 is completed, the network card to be cured may be registered in the system kernel.
In some embodiments, the registration card may be implemented by a standard function in the system kernel, for example, by a register _ netdev function in the Linux kernel, and copy the determined and fixed network interface name into the dev- > name memory. The network interface name of the network card is validated after the network card is successfully registered in the kernel system. So far, the information of the network card and the solidified interface name thereof can be viewed in the registered network card device chain.
Referring to the application scenario of fig. 6, an example of the method for curing the network card name is further given below, where the application scenario is: the interactive intelligent tablet system comprises a main controller, a computer module 1 and a computer module 2, wherein the main controller runs in an Android system, the computer module 1 and the computer module 2 can run in the Android system or a Windows system, an Ethernet card is arranged in the main controller and used for connecting an external network and accessing the Internet, for example, eth0 is used as a network interface name of the Ethernet card by default to connect the Internet through a network interface name eth0, the main controller is further provided with two expansion network cards (the expansion network card 1 and the expansion network card 2), and the busid and the cured interface name of the two expansion network cards are shown in FIG. 6. The application in the host controller wishes to communicate with the external computer modules according to the hardened interface names, constituting a local area network (subnet 1 and subnet 2).
In the process of starting the interactive intelligent tablet system, the network interface names of the expansion network card 1 and the expansion network card 2 can be respectively solidified into eth2 and eth1 by the method for solidifying the network card names of the above embodiment, and after the interactive intelligent tablet system is started, the main controller application program accesses the expansion network card 1 and the expansion network card 2 through the network interface names eth2 and eth1, so that the interactive intelligent tablet system can communicate with the computer module 1 and the computer module 2. In the starting process of the interactive intelligent tablet system, complex network card identification and network card renaming actions are not needed, communication failure caused by unfixed network interface names of the network cards in each starting-up process is avoided, and the stability and the rapidity of the network cards are guaranteed.
Different from the modification of the network interface name of the network card in the user space, the method for curing the network card name of the embodiment cures the network interface name of the network card through the kernel space, can finish the curing of the network interface name when the network card is driven and loaded, has higher efficiency, and can adapt to systems with different network architectures through the flexible configuration of the busid-cured interface name.
It should be understood that for the foregoing method embodiments, although the steps in the flowcharts are shown in order indicated by the arrows, the steps are not necessarily performed in order indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the flow charts of the method embodiments may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least a portion of the sub-steps or stages of other steps.
Based on the same idea as the method for internet card name curing in the above embodiments, an apparatus for internet card name curing is also provided herein.
In one embodiment, as shown in fig. 7, the apparatus for curing the internet card name of the present embodiment includes: an identifier obtaining module 701, a name obtaining module 702, a first confirming module 703 and a name solidifying module 704, which are detailed as follows:
an identifier obtaining module 701, configured to obtain a unique identifier of the network card to be cured in the system, where the unique identifier is used as an equipment identifier;
a name obtaining module 702, configured to obtain a first name of the network card to be cured through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
a first confirming module 703, configured to determine that the first name is not occupied by a registered network card;
a name curing module 704, configured to set the network interface name of the network card to be cured as the first name.
Further, in an embodiment, the apparatus further includes:
the equipment chain checking module is used for traversing the network card equipment chain aiming at the first name and judging whether the network interface name of the network card in the network card equipment chain is the same as the first name or not; the network card equipment chain comprises a currently registered network card and a network interface name thereof;
the first confirmation module is specifically configured to determine that the first name is not occupied by the registered network card if the network interface name of any network card in the network card device chain is different from the first name.
In another embodiment, the above apparatus further comprises: further comprising:
the variable checking module is used for inquiring preset variables aiming at the first name; the variable comprises n bits, and the value of n is equal to the total amount of network cards which can be accessed by the system; each bit in the variable is used for marking whether the n network interface names are registered currently;
the second confirmation module is used for determining that the first name is occupied by the registered network card if the value of bit corresponding to the first name in the variable is a second set value;
the first confirmation module is specifically configured to determine that the first name is not occupied by the registered network card if the value of bit corresponding to the first name in the variable is a first set value.
Further, in an embodiment, the apparatus further includes:
the second confirmation module is used for determining that the first name is occupied by the registered network card;
the conflict acquisition module is used for acquiring a conflict network card; the conflict network card is a registered network card, and the name of the network interface of the conflict network card is the same as the first name;
the name modification module is used for modifying the network interface name of the conflict network card into a second name;
the name curing module is specifically configured to set the network interface name of the to-be-cured network card as the first name after the network interface name of the conflicting network card is modified to the second name.
In an embodiment, the apparatus further includes:
a modified name determining module for obtaining a second name; the second designation satisfies the condition: not occupied by a registered network card and not identical to the first designation.
In one embodiment, the name modifying module includes:
the temporary storage unit is used for changing the system network state into a temporary storage state;
the function calling unit is used for calling a target function, and when the target function is called, the function calling unit is used for modifying the network interface name of the conflict network card into a second name and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space;
and the recovery unit is used for recovering the system network state.
In an embodiment, the name curing module 704 is specifically configured to assign a network interface name variable of the network card to be cured as the first name.
In an embodiment, the apparatus further includes:
the first mapping relation establishing module is used for setting a first mapping relation between the network card and the curing interface name;
the second mapping relation establishing module is used for obtaining a second mapping relation between the equipment identifier and the curing interface name according to the first mapping relation and the equipment identifier corresponding to the network card;
the mapping table establishing module is used for establishing a mapping table according to the second mapping relation;
and the mapping table storage module is used for storing the mapping table.
For specific limitations of the device for curing the internet card names, reference may be made to the above limitations of the method for curing the internet card names, which are not described herein again. The modules in the network card name solidifying device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In addition, in the embodiment of the foregoing exemplary apparatus for fixing network card names, the logical division of each program module is only an example, and in practical applications, the foregoing function distribution may be performed by different program modules according to needs, for example, due to configuration requirements of corresponding hardware or due to convenience of implementation of software, that is, the internal structure of the apparatus for fixing network card names is divided into different program modules to perform all or part of the functions described above.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 8. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor is configured to provide computing and control capabilities; the memory comprises a nonvolatile storage medium and an internal memory, wherein the nonvolatile storage medium stores an operating system and a computer program, and the internal memory provides an environment for the operation of the operating system and the computer program in the nonvolatile storage medium; the network interface is used for connecting and communicating with an external terminal through a network; the computer program is executed by a processor to implement a method for web name curing; the display screen can be a liquid crystal display screen or an electronic ink display screen; the input device may be a touch layer covered on a display screen, or may be a key, a track ball or a touch pad arranged on a casing of the computer device, or may be an external keyboard, a touch pad or a mouse, etc.
In particular embodiments, the computer device may be an interactive smart tablet.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a display screen with touch functionality, and a processor; the memory for storing a computer program; the computer program, when executed by the processor, causes the processor to carry out the steps of:
acquiring a unique identifier of a network card to be solidified in a system as an equipment identifier;
acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
determining that the first name is not occupied by a registered network card;
and setting the network interface name of the network card to be solidified as the first name.
In one embodiment, the computer program, when executed by the processor, further causes the processor to implement the steps included in the method for curing a network card name of any of the other embodiments described above.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a unique identifier of a network card to be solidified in a system as an equipment identifier;
acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
determining that the first name is not occupied by a registered network card;
and setting the network interface name of the network card to be solidified as the first name.
In some other embodiments, the computer program, when executed by the processor, further implements the steps included in the method for curing a network card name according to any of the other embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features. The above description of each embodiment has different emphasis, and reference may be made to related descriptions of other embodiments for parts that are not described in detail in a certain embodiment.
The terms "comprising" and "having" and any variations thereof in the embodiments are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or (module) elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The "plurality" mentioned in the embodiments means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
In the embodiments, the references to "first \ second" are merely to distinguish similar objects and do not represent a specific ordering for the objects, and it is to be understood that "first \ second" may be interchanged with a specific order or sequence, where permitted. It should be understood that "first \ second" distinct objects may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced in sequences other than those illustrated or described herein.
The above examples only represent several embodiments of the present invention, but should not be construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (14)
1. A method for curing a network card name is characterized by comprising the following steps:
in the starting process of the interactive intelligent tablet system, acquiring a unique identifier of a network card to be solidified in the system as an equipment identifier; the interactive intelligent tablet system is an operating system based on a linux kernel, and the operating system is divided into a kernel space and a user space; a built-in network card and a USB expansion network card are arranged in the mutual intelligent flat plate, and the network card to be solidified is the USB expansion network card without a network interface name; the kernel space of the operating system is communicated with the built-in network card and the USB expansion network card through a kernel driver;
acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
determining whether the first name is occupied by a registered network card, including: querying a preset variable aiming at the first name; the variable comprises n bits, and the value of n is equal to the total amount of network cards which can be accessed by the system; each bit in the variable is used for marking whether the n network interface names are registered currently; if the value of bit corresponding to the first name in the variable is a first set value, determining that the first name is not occupied by the registered network card; if the value of bit corresponding to the first name in the variable is a second set value, determining that the first name is occupied by the registered network card;
if the first name is determined not to be occupied by the registered network card, setting the network interface name of the network card to be solidified as the first name;
if the first name is determined to be occupied by other registered network cards, locking and protecting system resources, temporarily storing the current network interface state of the system, modifying the network interface name of the conflict network card occupying the first name into a second name, and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space; then, the original state of the network interface state is recovered, and the system resources are unlocked; setting the network interface name of the network card to be cured as the first name; the second name is obtained by querying the preset variable.
2. The method of claim 1, wherein the determining whether the first name is occupied by a registered network card further comprises:
traversing the registered equipment chain aiming at the first name, and judging whether the network interface name of the network card in the equipment chain is the same as the first name or not; the equipment chain comprises a network card which is registered currently and a network interface name thereof;
and if the network interface name of any network card in the equipment chain is different from the first name, determining that the first name is not occupied by the registered network card.
3. The method of claim 1, wherein the modifying the network interface name of the conflicting network card to a second name further comprises:
inquiring the preset variable to obtain a second name; the second designation satisfies the condition: the variable is not occupied by the registered network card and is different from the first name, and the value of bit corresponding to the second name in the variable is a first set value.
4. The method according to claim 1, wherein the modifying the network interface name occupying the first named conflicting network card to a second name and synchronizing the modified network interface name of the conflicting network card to each association point of the system kernel space comprises:
and calling a target function, wherein when the target function is called, the target function is used for modifying the network interface name of the conflict network card into a second name and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space.
5. The method according to claim 1, wherein the setting the network interface name of the network card to be cured to the first name comprises:
and assigning the network interface name variable of the network card to be solidified as the first name.
6. The method according to any one of claims 1 to 5,
the acquiring the unique identifier of the network card to be cured in the system comprises the following steps:
and acquiring a busid identifier of the network card to be solidified in the operating system.
7. The method of any of claims 1 to 5, further comprising:
setting a first mapping relation between a network card and a curing interface name;
obtaining a second mapping relation between the equipment identification and the curing interface name according to the first mapping relation and the equipment identification corresponding to the network card;
establishing a mapping table according to the second mapping relation;
and storing the mapping table.
8. An apparatus for curing internet card names, comprising:
the identification acquisition module is used for acquiring a unique identification of the network card to be solidified in the system as an equipment identification in the starting process of the interactive intelligent tablet system; the interactive intelligent tablet system is an operating system based on a linux kernel, and the operating system is divided into a kernel space and a user space; a built-in network card and a USB expansion network card are arranged in the mutual intelligent flat plate, and the network card to be solidified is the USB expansion network card without a network interface name; the kernel space of the operating system is communicated with the built-in network card and the USB expansion network card through a kernel driver;
the name acquisition module is used for acquiring a first name of the network card to be solidified through a preset mapping table; the mapping table records the mapping relation between the equipment identifier and the curing interface name, and the first name is the curing interface name corresponding to the equipment identifier in the mapping table;
the variable checking module is used for inquiring preset variables aiming at the first name; the variable comprises n bits, and the value of n is equal to the total amount of network cards which can be accessed by the system; each bit in the variable is used for marking whether the n network interface names are registered currently;
the first confirmation module is used for determining that the first name is not occupied by the registered network card if the value of bit corresponding to the first name in the variable is a first set value;
the name curing module is used for setting the network interface name of the network card to be cured as the first name under the condition that the first name is not occupied by the registered network card;
the second confirmation module is used for determining that the first name is occupied by the registered network card if the value of bit corresponding to the first name in the variable is a second set value;
the name modification module is used for locking and protecting system resources under the condition that the first name is occupied by the registered network card, temporarily storing the current network interface state of the system, modifying the network interface name occupying the first named conflict network card into a second name, and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space; then, the original state of the network interface state is recovered, and the system resources are unlocked; the second name is obtained by querying the preset variable.
9. The apparatus of claim 8, further comprising:
the equipment chain checking module is used for traversing the network card equipment chain aiming at the first name and judging whether the network interface name of the network card in the network card equipment chain is the same as the first name or not; the network card equipment chain comprises a currently registered network card and a network interface name thereof;
the first confirmation module is further configured to determine that the first name is not occupied by the registered network card if the network interface name of any network card in the network card device chain is different from the first name.
10. The apparatus of claim 8, further comprising:
the modified name determining module is used for inquiring the preset variable to obtain a second name; the second designation satisfies the condition: the name is different from the first name, and the value of bit corresponding to the second name in the variable is a first set value.
11. The apparatus of claim 8, wherein the name modification module comprises:
the temporary storage unit is used for changing the system network state into a temporary storage state;
the function calling unit is used for calling a target function, and when the target function is called, the function calling unit is used for modifying the network interface name of the conflict network card into a second name and synchronizing the modified network interface name of the conflict network card to each association point of a system kernel space;
and the recovery unit is used for recovering the system network state.
12. The apparatus of any one of claims 8 to 11, further comprising:
the first mapping relation establishing module is used for setting a first mapping relation between the network card and the curing interface name;
the second mapping relation establishing module is used for obtaining a second mapping relation between the equipment identifier and the curing interface name according to the first mapping relation and the equipment identifier corresponding to the network card;
the mapping table establishing module is used for establishing a mapping table according to the second mapping relation;
and the mapping table storage module is used for storing the mapping table.
13. A computer device comprising a memory and a processor;
the memory is used for storing a computer program; it is characterized in that the preparation method is characterized in that,
the computer program, when executed by the processor, causes the processor to carry out the steps of the method of any one of claims 1 to 7.
14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, causes the processor to carry out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811031779.8A CN109412830B (en) | 2018-09-05 | 2018-09-05 | Method and device for curing internet card name, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811031779.8A CN109412830B (en) | 2018-09-05 | 2018-09-05 | Method and device for curing internet card name, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109412830A CN109412830A (en) | 2019-03-01 |
| CN109412830B true CN109412830B (en) | 2022-05-06 |
Family
ID=65463948
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811031779.8A Active CN109412830B (en) | 2018-09-05 | 2018-09-05 | Method and device for curing internet card name, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109412830B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112003960B (en) * | 2020-08-06 | 2022-11-15 | 杭州安恒信息技术股份有限公司 | Network interface management method and device of industrial control equipment and electronic device |
| CN113835783A (en) * | 2021-09-24 | 2021-12-24 | 青岛海信移动通信技术股份有限公司 | Method and device for controlling start of Wi-Fi network card and terminal equipment |
| CN114265554B (en) * | 2021-12-22 | 2023-08-15 | 苏州浪潮智能科技有限公司 | NVME (network video memory equipment) limit name mapping method, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102801553A (en) * | 2012-06-28 | 2012-11-28 | 南京智达康无线通信科技股份有限公司 | Adaptation method for adaptive modulation and coding (AMC) daughter cards |
| CN102868568A (en) * | 2011-07-06 | 2013-01-09 | 瑞昱半导体股份有限公司 | Network unit replacing system and embedded system device |
| CN103186484A (en) * | 2011-12-28 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Network card naming method and system |
| CN103533096A (en) * | 2013-10-09 | 2014-01-22 | 杭州华三通信技术有限公司 | Binding method and device of network card interface |
| CN105847053A (en) * | 2016-03-23 | 2016-08-10 | 成都民航空管科技发展有限公司 | Method and system for automatically setting arbitrary bonding for multi-network card and multi-network segment under LINUX system |
| CN107135280A (en) * | 2016-02-29 | 2017-09-05 | 上海格尔软件股份有限公司 | The method that many network card equipments based on (SuSE) Linux OS adjust network interface card order |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10367688B2 (en) * | 2016-08-17 | 2019-07-30 | Red Hat Israel, Ltd. | Discovering changes of network interface controller names |
-
2018
- 2018-09-05 CN CN201811031779.8A patent/CN109412830B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102868568A (en) * | 2011-07-06 | 2013-01-09 | 瑞昱半导体股份有限公司 | Network unit replacing system and embedded system device |
| CN103186484A (en) * | 2011-12-28 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Network card naming method and system |
| CN102801553A (en) * | 2012-06-28 | 2012-11-28 | 南京智达康无线通信科技股份有限公司 | Adaptation method for adaptive modulation and coding (AMC) daughter cards |
| CN103533096A (en) * | 2013-10-09 | 2014-01-22 | 杭州华三通信技术有限公司 | Binding method and device of network card interface |
| CN107135280A (en) * | 2016-02-29 | 2017-09-05 | 上海格尔软件股份有限公司 | The method that many network card equipments based on (SuSE) Linux OS adjust network interface card order |
| CN105847053A (en) * | 2016-03-23 | 2016-08-10 | 成都民航空管科技发展有限公司 | Method and system for automatically setting arbitrary bonding for multi-network card and multi-network segment under LINUX system |
Non-Patent Citations (1)
| Title |
|---|
| 插入外置网卡端口顺序混乱--linux系统;肥而不腻;《https://www.cnblogs.com/yuzhaoxin/p/4083760.html》;20160131;第一至三部分 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109412830A (en) | 2019-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109412830B (en) | Method and device for curing internet card name, computer equipment and storage medium | |
| US8452934B2 (en) | Controlled data access to non-volatile memory | |
| CN100489782C (en) | Virtual machine system and accessing control method of hardware equipment | |
| CN100580642C (en) | Universal serial bus storage device and access control method thereof | |
| CN110798466B (en) | Verification method and system for software license in virtual machine scene | |
| US20180046399A1 (en) | Storage Partitioning Method and Terminal | |
| CN114707147A (en) | Service request processing method and electronic equipment | |
| CN110765428A (en) | Behavior control method and device based on enterprise browser | |
| CN116055664B (en) | Method, device and storage medium for sharing memory for video processing process | |
| CN105183799A (en) | Authority management method and client | |
| US20080098166A1 (en) | Data storage device and data controlling method | |
| CN109711193B (en) | Storage space sharing method and device | |
| CN109299053B (en) | File operation method, device and computer storage medium | |
| CN116089327A (en) | Data protection method and related equipment | |
| WO2021073440A1 (en) | Access control method and device for embedded universal integrated circuit card, and storage medium | |
| CN113568881A (en) | Method, system, equipment and medium for realizing read-write sharing | |
| US20190391750A1 (en) | Control of a data storage device | |
| CN111400778A (en) | Encryption method, system, equipment and medium for virtual disk file | |
| CN115599929B (en) | File management method and electronic equipment | |
| CN111881435B (en) | Method and system for realizing safe memory | |
| CN112631720B (en) | Memory control method, medium and equipment | |
| CN112738219B (en) | Program running method, program running device, vehicle and storage medium | |
| CN110677378A (en) | Control method of MAC address, intelligent terminal and storage medium | |
| US20230281304A1 (en) | Method for switching execution environment and related device thereof | |
| JP5454230B2 (en) | Information processing system, program, and authentication transfer method |
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 |