CN111988153B - Network exception handling method and device and household electrical appliance - Google Patents

Network exception handling method and device and household electrical appliance Download PDF

Info

Publication number
CN111988153B
CN111988153B CN201910423716.5A CN201910423716A CN111988153B CN 111988153 B CN111988153 B CN 111988153B CN 201910423716 A CN201910423716 A CN 201910423716A CN 111988153 B CN111988153 B CN 111988153B
Authority
CN
China
Prior art keywords
address
network
local area
equipment
area network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910423716.5A
Other languages
Chinese (zh)
Other versions
CN111988153A (en
Inventor
霍伟明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Midea Group Co Ltd
GD Midea Air Conditioning Equipment Co Ltd
Original Assignee
Midea Group Co Ltd
GD Midea Air Conditioning Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Midea Group Co Ltd, GD Midea Air Conditioning Equipment Co Ltd filed Critical Midea Group Co Ltd
Priority to CN201910423716.5A priority Critical patent/CN111988153B/en
Priority to PCT/CN2020/072722 priority patent/WO2020233159A1/en
Publication of CN111988153A publication Critical patent/CN111988153A/en
Application granted granted Critical
Publication of CN111988153B publication Critical patent/CN111988153B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0631Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0823Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • H04L61/5014Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5046Resolving address allocation conflicts; Testing of addresses

Abstract

The application provides a network exception handling method, a device and household electrical appliance equipment, wherein the method comprises the following steps: the method comprises the steps that network connection of equipment fails, after abnormality is determined, an idle first IP address is inquired in a local area network, the equipment modifies the IP address from a second IP address configured in advance to the first IP address, the equipment inquires to obtain a physical address corresponding to the second IP address, and the abnormality is determined to be IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.

Description

Network exception handling method and device and household electrical appliance
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing network anomalies, and a home appliance.
Background
With the rapid development of the internet of things and intelligent household appliance technology, more and more users realize the control of the intelligent household appliance through mobile terminal equipment, so that the intelligent household appliance is firstly connected to a network. In the prior art, when a home appliance connects to a network, a request for obtaining an Internet Protocol Address (hereinafter, referred to as an IP Address) is often made to a router through a Dynamic Host Configuration Protocol (DHCP). And the household appliance uses the acquired IP address to communicate until the lease of the IP address is due, and then applies for an IP address again.
However, when the DHCP protocol is used to acquire an IP address from the router, the DHCP server of the router cannot find that the IP address assigned to the home appliance may have been already allocated to another device by the DHCP protocol, so that when the home appliance uses the acquired IP address to perform network connection, a network connection failure occurs.
Disclosure of Invention
The present application is directed to solving, at least to some extent, one of the technical problems in the related art.
The application provides a network abnormity processing method and device and household electrical appliance equipment, so that the problem that in the network connection process of the equipment in the prior art, when the IP address conflict cannot be connected to a server, a large amount of time is wasted when the abnormity reason needs to be manually checked is solved.
An embodiment of a first aspect of the present application provides a method for processing a network exception, including:
the equipment network connection fails, and the abnormality is determined to exist;
the equipment inquires an idle first IP address in a local area network;
the equipment modifies the IP address from a second pre-configured IP address to the first IP address;
and the equipment queries to obtain a physical address corresponding to the second IP address, and determines that the abnormality is IP address conflict.
An embodiment of a second aspect of the present application provides a network exception handling apparatus, including:
the determining module is used for determining that the network connection fails and the abnormality exists;
the query module is used for querying the idle first IP address in the local area network;
the first modification module is used for modifying the IP address from a second pre-configured IP address to the first IP address;
and the detection module is used for inquiring and obtaining the physical address corresponding to the second IP address and determining that the abnormality is IP address conflict.
In an embodiment of a third aspect of the present application, a home appliance is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the program, the network exception handling method in the foregoing embodiments is implemented.
A fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the network exception handling method as described in the foregoing embodiments.
One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:
on one hand, the device determines that the abnormality exists through network connection failure of the device, the device inquires an idle first IP address in a local area network, the device modifies the IP address from a pre-configured second IP address to the first IP address, the device inquires a physical address corresponding to the second IP address, and the abnormality is determined to be IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.
On the other hand, the physical addresses corresponding to all IP addresses in the network segment of the local area network are sequentially inquired through the equipment, whether all the IP addresses in the network segment have the corresponding physical addresses is judged, whether the idle first IP address exists is determined according to whether all the IP addresses have the corresponding physical addresses, and when the idle first IP address does not exist, the router of the local area network is requested to perform IP address allocation again; and when the IP address of which the physical address is not inquired exists, taking the IP address of which the physical address is not inquired as the idle first IP address. The method determines an idle first IP address or requests a router of the local area network to re-distribute the IP addresses by inquiring physical addresses corresponding to all IP addresses in a network segment of the local area network, thereby ensuring that equipment avoids the technical problem of server connection failure caused by IP address conflict in the network connection process.
In another aspect, after it is determined that the device networking failure is caused by the IP address conflict, the physical address of the device is modified, and the IP address of the device is modified to the third IP address corresponding to the modified physical address, so that the technical problem that the device cannot be connected to the server due to the IP address conflict in the network connection process in the prior art is solved, and the IP address conflict is automatically detected, and the IP address is modified so that the device can be successfully connected to the server.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of a network exception handling method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a network exception handling method according to a second embodiment of the present application;
fig. 3 is a schematic flowchart of a network exception handling method according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of a network exception handling apparatus according to a fourth embodiment of the present application.
Detailed Description
In the prior art, when a device requests a router to acquire a static IP address through a DHCP protocol in a networking process, a DHCP server of the router cannot discover the IP address configured to the device, and may have been allocated to other devices through the DHCP protocol, thereby causing a technical problem of network connection failure when the device uses the IP address to perform network connection.
In order to solve the technical problems in the prior art, the application provides a network exception handling method, which includes determining that an exception exists through network connection failure of equipment, inquiring an idle first IP address in a local area network by the equipment, modifying the IP address from a pre-configured second IP address to the first IP address by the equipment, inquiring by the equipment to obtain a physical address corresponding to the second IP address, and determining that the exception is an IP address conflict.
In order to better understand the above technical solutions, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.
In order to better understand the technical solution, the technical solution will be described in detail with reference to the drawings and the specific embodiments.
Example one
Fig. 1 is a flowchart illustrating a network exception handling method according to an embodiment of the present application.
As shown in fig. 1, the network exception handling method is executed by a home appliance side, and specifically includes the following steps:
step 101, the network connection of the device fails, and it is determined that there is an abnormality.
In the embodiment of the application, in the process of connecting the router, the device requests the router of the local area network to acquire the static IP address through the DHCP protocol so as to connect the server according to the acquired static IP address. Whether the network connection is abnormal is determined by judging whether the network connection is successful when the equipment is connected with the server according to the static IP address.
The static IP address is a fixed IP address which is allocated to the equipment for long term use by using a TCP/IP protocol. An IP address is made up of 4 8 octets separated by dots, for example 192.168.0.1 is an IP address, which is written in dotted decimal format.
It should be noted that the DHCP protocol is a network protocol of a local area network, and works using the UDP protocol, and mainly has the following two purposes: first, an IP address is automatically assigned to an internal network or network service provider; second, users or internal network administrators are given a means to centrally manage all computers.
As a possible situation, when the device requests the router of the local area network to connect to the server through the DHCP protocol, the connection can be successful, and then the device enters a normal working phase.
As another possible case, when the device requests the router of the local area network to connect to the server through the DHCP protocol, the network connection fails, and in this case, it is determined that there is an abnormality in the network connection.
In this embodiment, the static IP address assigned to the device by the router may have been already assigned to other devices by the DHCP protocol for use, but the DHCP protocol of the router cannot discover that the static IP address is already occupied. In this case, when the device uses the static IP address to perform network connection, a network connection failure occurs.
Step 102, the device queries an idle first IP address in the local area network.
In the embodiment of the application, the device connection fails, and the network connection is abnormal, which may be caused by that the static IP address acquired by the DHCP protocol requesting the router is occupied by other devices, so that the IP address conflicts, and the device networking fails.
In this case, the device obtains the idle first IP Address by querying through an Address Resolution Protocol (ARP) within a network segment range of the lan of the router through a DHCP Protocol.
In the local area network, the IP address and the physical address are in a one-to-one correspondence relationship, and the idle first IP address refers to an IP address not allocated to another device. Since the idle IP address has no corresponding physical address, the IP address of which the physical address is not queried may be used as the idle first IP address.
Step 103, the device modifies the IP address from the second pre-configured IP address to the first IP address.
The second IP address is the above-mentioned static IP address requested by the DHCP protocol to the router, and for convenience of distinguishing, the IP address is defined as the second IP address.
The device network connection failure is caused because the device requests the router to acquire the static IP address through the DHCP protocol and the static IP address can be occupied by other devices. In this case, in order to determine that the device networking failure is caused by IP address conflict, after the device queries an idle first IP address in the local area network, the device modifies the IP address from a pre-configured second IP address to the first IP address.
For example, if the second IP address preconfigured for the device after the DHCP protocol requests the router is 192.168.1.1, after the device fails to request the server for networking through the second IP address, the idle first IP address is 192.168.1.2 in the local area network, and at this time, the device modifies the IP address to 192.168.1.2.
And step 104, the device queries to obtain a physical address corresponding to the second IP address, and determines that the abnormality is IP address conflict.
The physical address, also called a Media Access Control (MAC) address, is an identifier for identifying a lan node.
In the embodiment of the application, the device queries the physical address corresponding to the second IP address through the ARP protocol, and if the physical address corresponding to the second IP address can be successfully obtained through querying, it can be determined that the network connection failure of the device is caused by IP address conflict.
It should be explained that the IP addresses of the devices are in one-to-one correspondence with the physical addresses, and if the physical address corresponding to the second IP address can be successfully queried through the ARP protocol, it is indicated that the second IP address has been allocated to another device for use. Therefore, in this embodiment, the device may determine that the abnormality is an IP address conflict when the network connection fails using the pre-configured second IP address.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
according to the network exception handling method, the device determines that an exception exists through network connection failure of the device, the device inquires an idle first IP address in a local area network, the device modifies the IP address from a second IP address configured in advance to the first IP address, the device inquires to obtain a physical address corresponding to the second IP address, and the exception is determined to be an IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.
In the foregoing embodiment, when the device in step 102 queries the idle first IP address in the local area network, as a possible implementation manner, the device may query a physical address corresponding to each IP address in a network segment of the local area network, and further determine whether each IP address in the network segment of the local area network has a corresponding physical address, so as to use an IP address where no physical address is queried as the idle first IP address. The specific implementation process is shown in the second embodiment.
Example two
Fig. 2 is a schematic flowchart of a network exception handling method according to a second embodiment of the present application.
As shown in fig. 2, the method specifically includes the following steps:
step 201, the device sequentially queries the physical addresses corresponding to the IP addresses in the network segment of the local area network.
In the embodiment of the application, when the device requests the router for the acquired static IP address to connect the server through the DHCP protocol, after the network connection fails, the physical address corresponding to each IP address can be sequentially inquired in the network segment of the local area network.
Step 202, judging whether each IP address in the network segment has a corresponding physical address.
After the device is successfully networked according to the network segment IP address of the local area network, a physical address corresponding to the IP address exists. Therefore, whether idle IP addresses exist in the network segments of the local area network can be determined by judging whether the corresponding physical addresses exist in all the IP addresses in the network segments of the local area network.
As a possible situation, after sequentially querying the physical addresses corresponding to the IP addresses in the network segment of the local area network, the device determines that the IP addresses in the network segment all have corresponding physical addresses, and then sequentially executes step 203.
As another possible situation, after sequentially querying the physical addresses corresponding to the IP addresses in the network segment of the local area network, the device determines that the IP addresses in the network segment do not all have corresponding physical addresses. That is, if there is an IP address in the network segment for which no physical address is queried, step 204 is executed.
Step 203, the device determines that there is no idle first IP address, and requests the router of the local area network to re-assign the IP address.
In the embodiment of the application, if the device determines that each IP address in the network segment has a corresponding physical address, it indicates that no idle first IP address exists in the network segment of the local area network. In this case, the device needs to request the router of the local area network to re-assign the IP address through DHCP, so as to perform network connection according to the re-acquired IP address.
And step 204, taking the IP address of which the physical address is not inquired as an idle first IP address.
In the embodiment of the application, after determining that the IP address of the physical address which is not queried exists in each IP address in the network segment, the device can use the IP address of the physical address which is not queried as the idle first IP address.
As a possible implementation manner, in the process that the device sequentially queries the physical addresses corresponding to the IP addresses in the network segment of the local area network, the first IP address that is not queried as the physical address may be used as the idle first IP address. In this case, the physical addresses of the rest of the IP addresses in the network segment do not need to be queried sequentially, so that the query time is saved to a certain extent.
As another possible implementation manner, in the process that the device sequentially queries the physical addresses corresponding to the IP addresses in the network segment of the local area network, one IP address may be randomly selected from all the IP addresses that are not queried to the physical address, and the selected IP address is used as the idle first IP address.
It should be noted that the implementation process of using the IP address without querying the physical address as the idle first IP address is not limited to the above two implementation manners, and this embodiment is merely an exemplary representation, and specifically, the implementation process is not limited in this embodiment.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
in the embodiment of the application, physical addresses corresponding to all IP addresses in a network segment of a local area network are sequentially inquired through equipment, whether all the IP addresses in the network segment have corresponding physical addresses is judged, whether idle first IP addresses exist is determined according to whether all the IP addresses have the corresponding physical addresses, and when the idle first IP addresses do not exist, a router of the local area network is requested to perform IP address allocation again; and when the IP address of which the physical address is not inquired exists, taking the IP address of which the physical address is not inquired as the idle first IP address. The method determines an idle first IP address or requests a router of the local area network to re-distribute the IP addresses by inquiring physical addresses corresponding to all IP addresses in a network segment of the local area network, thereby ensuring that equipment avoids the technical problem of server connection failure caused by IP address conflict in the network connection process.
As a possible situation, after the device network connection fails and the abnormality is determined to be an IP address conflict, the local area network router may be requested to allocate an IP address to the modified physical address through the modified physical address of the device, so as to avoid the problem of IP address conflict. The specific implementation process is shown in the third embodiment.
EXAMPLE III
Fig. 3 is a schematic flowchart of a network exception handling method according to a third embodiment of the present application;
as shown in fig. 3, the specific implementation process of the method includes the following steps:
in step 301, the device requests a router of the local area network to assign a second IP address.
In the embodiment of the application, when the device is connected to a network after being powered on, a second IP address is first requested to be allocated to a router of a local area network through a DHCP protocol.
Step 302, the device configures the IP address as a second IP address.
In the embodiment of the application, after the device acquires the second IP address allocated by the router of the local area network, the IP address of the device is configured as the second IP address, so that the server is connected by using the second IP address.
It should be noted that the second IP address assigned to the device by the router may have been assigned to other devices by the DHCP protocol for use, but the DHCP protocol of the router cannot discover that the second IP address is already occupied. In this case, when the device uses the second IP address to perform network connection, a network connection failure occurs.
Step 303, the device network connection fails, and it is determined that there is an anomaly.
In step 304, the device queries the first IP address for idleness within the local area network.
Step 305, the device modifies the IP address from the second pre-configured IP address to the first IP address.
Step 306, the device queries the physical address corresponding to the second IP address, and determines that the abnormality is an IP address conflict.
In the embodiment of the present application, the implementation process of step 303 to step 306 may refer to the implementation process of step 101 to step 104 in the above embodiment, and is not described herein again.
Step 307, the device modifies the physical address.
In the embodiment of the application, when it is determined that the network connection failure of the device is caused by the IP address conflict of the device, further, the physical address of the device can be modified in a manual operation manner.
Step 308, the device requests the router of the local area network to assign a third IP address to the modified physical address.
In the embodiment of the application, after the device modifies the physical address, the device may request the router of the next local area network to allocate an IP address to the modified physical address through the DHCP protocol. Here, for convenience of distinction, an IP address allocated to the modified physical address may be defined as the third IP address.
Step 309, the device modifies the IP address from the first IP address to a third IP address.
In the embodiment of the application, after the device acquires the third IP address corresponding to the modified physical address, the device modifies the own IP address from the first IP address to the third IP address, so that the problem of IP address conflict is avoided.
It should be explained that, because the first IP address is a temporary IP address queried from a network segment of the lan, the IP address of the device needs to be modified to the third IP address, so as to ensure that when the router is connected by using the third IP address corresponding to the modified physical address, no IP address collision occurs.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
the network exception handling method of the embodiment includes that a router of a local area network is requested by equipment to allocate a second IP address, the IP address is configured as the second IP address, network connection failure is determined by using the second IP address, an idle first IP address is inquired in the local area network, the IP address is modified from the second IP address configured in advance to the first IP address, a physical address corresponding to the second IP address is obtained by inquiry, IP address conflict is determined as the exception, the equipment modifies the physical address, the router of the local area network is requested to allocate a third IP address to the modified physical address, and the IP address is modified from the first IP address to the third IP address. Therefore, after the fact that the IP address conflicts is determined to be the reason of the failure of the device networking, the physical address of the device is modified, and the IP address of the device is modified into the third IP address corresponding to the modified physical address, so that the technical problem that the device cannot be connected to the server due to the IP address conflicts in the network connection process in the prior art is solved, the IP address conflicts are automatically detected, and the IP address is modified to enable the device to be successfully connected to the server.
Based on the same inventive concept, the embodiment of the present application further provides a device corresponding to the method of the embodiment, which is shown in the fourth embodiment.
Example four
Fig. 4 is a schematic structural diagram of a network exception handling device according to an embodiment of the present application.
As shown in fig. 4, the network exception handling apparatus 100 includes: a determination module 110, a query module 120, a first modification module 130, and a detection module 140.
The determining module 110 is configured to determine that there is an abnormality due to a network connection failure.
The query module 120 is configured to query the first IP address that is idle in the lan.
A first modifying module 130, configured to modify the IP address from the preconfigured second IP address to the first IP address.
The detecting module 140 is configured to query a physical address corresponding to the second IP address, and determine that the abnormality is an IP address conflict.
As a possible implementation manner, the network exception handling apparatus 100 may further include:
the second modification module is used for modifying the physical address by the equipment;
the first request module is used for requesting the router of the local area network to distribute a third IP address to the modified physical address by the equipment;
and the third modification module is used for modifying the IP address from the first IP address to a third IP address by the equipment.
As another possible implementation manner, the network exception handling apparatus 100 may further include:
the second request module is used for requesting the router of the local area network to distribute a second IP address by the equipment;
a configuration module, configured to configure the IP address as the second IP address.
As another possible implementation manner, the query module 120 may be further specifically configured to:
the equipment sequentially inquires physical addresses corresponding to all IP addresses in a network segment of the local area network; and taking the IP address without inquiring the physical address as a free first IP address.
As another possible implementation manner, the query module 120 may be further specifically configured to:
corresponding physical addresses exist in all IP addresses in the network segment, and the equipment determines that no idle first IP address exists; the device requests the router of the local area network to re-perform the IP address assignment.
It should be noted that the foregoing explanation of the embodiment of the network exception handling method is also applicable to the network exception handling apparatus of the embodiment, and is not repeated herein.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
the network exception handling device of the embodiment of the application determines that an exception exists through network connection failure of equipment, the equipment inquires an idle first IP address in a local area network, the equipment modifies the IP address from a pre-configured second IP address to the first IP address, the equipment inquires to obtain a physical address corresponding to the second IP address, and the exception is determined to be an IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.
Based on the same inventive concept, the embodiment of the present application provides a home appliance corresponding to the method one in the embodiment, see embodiment five.
EXAMPLE five
The embodiment of the application provides a household appliance, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein when the processor executes the program, the network exception handling method in the embodiment is realized.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
in the embodiment of the application, the existence of the abnormality is determined through the network connection failure of the equipment, the equipment inquires an idle first IP address in the local area network, the equipment modifies the IP address from a pre-configured second IP address to the first IP address, the equipment inquires to obtain a physical address corresponding to the second IP address, and the abnormality is determined to be an IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.
Based on the same inventive concept, embodiments of the present application provide a computer-readable storage medium corresponding to the method in the foregoing embodiments, see embodiment six.
EXAMPLE six
Embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the network exception handling method as described in the above embodiments.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
in the embodiment of the application, the existence of the abnormality is determined through the network connection failure of the equipment, the equipment inquires an idle first IP address in the local area network, the equipment modifies the IP address from a pre-configured second IP address to the first IP address, the equipment inquires to obtain a physical address corresponding to the second IP address, and the abnormality is determined to be an IP address conflict. Therefore, the problem of IP address conflict can be automatically detected when the network connection of the equipment is abnormal, and the technical problem that in the prior art, when the equipment cannot be connected to a server in the network connection process, a user needs to manually search the reason of networking failure, so that a large amount of time is wasted is solved.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.

Claims (7)

1. A method for handling network exceptions, the method comprising the steps of:
the equipment network connection fails, and the abnormality is determined to exist;
the equipment inquires an idle first IP address in a local area network;
the equipment modifies the IP address from a second pre-configured IP address to the first IP address;
the equipment queries to obtain a physical address corresponding to the second IP address, and determines that the abnormality is an IP address conflict;
after the determining that the exception is an IP address conflict, the method further includes:
the device modifies a physical address;
the equipment requests the router of the local area network to allocate a third IP address to the modified physical address;
the device modifies the IP address from the first IP address to the third IP address;
the device queries an idle first IP address in a local area network, including:
the equipment sequentially inquires physical addresses corresponding to all IP addresses in a network segment of the local area network;
and taking the IP address without inquiring the physical address as a free first IP address.
2. The method of claim 1, wherein the device fails to connect to the network and before determining that the exception exists, the method further comprises:
the device requests a router of the local area network to allocate the second IP address;
the device configures an IP address as the second IP address.
3. The method for processing network exception according to claim 1, wherein after the device sequentially queries the physical addresses corresponding to the IP addresses in the segments of the local area network, the method further comprises:
corresponding physical addresses exist in all IP addresses in the network segment, and the equipment determines that no idle first IP address exists;
the device requests the router of the local area network to re-assign the IP address.
4. A network exception handling apparatus, the apparatus comprising:
the determining module is used for determining that the network connection fails and the abnormality exists;
the query module is used for querying the idle first IP address in the local area network;
the first modification module is used for modifying the IP address from a second pre-configured IP address to the first IP address;
the detection module is used for inquiring and obtaining a physical address corresponding to the second IP address and determining that the abnormality is an IP address conflict;
the second modification module is used for modifying the physical address by the equipment;
a first request module, configured to request, by the device, a router of the local area network to allocate a third IP address to the modified physical address;
a third modification module, configured to modify, by the device, an IP address from the first IP address to the third IP address;
the query module is specifically configured to:
the equipment sequentially inquires physical addresses corresponding to all IP addresses in a network segment of the local area network;
and taking the IP address without inquiring the physical address as a free first IP address.
5. The apparatus according to claim 4, wherein said apparatus further comprises:
a second request module, configured to request, by the device, a router of the local area network to allocate the second IP address;
a configuration module, configured to configure the IP address as the second IP address by the device.
6. An appliance comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method of handling network anomalies as claimed in any one of claims 1 to 3.
7. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the network exception handling method according to any one of claims 1 to 3.
CN201910423716.5A 2019-05-21 2019-05-21 Network exception handling method and device and household electrical appliance Active CN111988153B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910423716.5A CN111988153B (en) 2019-05-21 2019-05-21 Network exception handling method and device and household electrical appliance
PCT/CN2020/072722 WO2020233159A1 (en) 2019-05-21 2020-01-17 Network abnormality processing method and apparatus, and household electrical appliance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910423716.5A CN111988153B (en) 2019-05-21 2019-05-21 Network exception handling method and device and household electrical appliance

Publications (2)

Publication Number Publication Date
CN111988153A CN111988153A (en) 2020-11-24
CN111988153B true CN111988153B (en) 2022-02-25

Family

ID=73436155

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910423716.5A Active CN111988153B (en) 2019-05-21 2019-05-21 Network exception handling method and device and household electrical appliance

Country Status (2)

Country Link
CN (1) CN111988153B (en)
WO (1) WO2020233159A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331192A (en) * 2015-06-23 2017-01-11 中兴通讯股份有限公司 Network protocol IP address allocation method and device
CN106899456A (en) * 2017-03-14 2017-06-27 深圳市友华通信技术有限公司 A kind of link detecting and the implementation method repaired
CN107370647A (en) * 2017-07-25 2017-11-21 郑州云海信息技术有限公司 A kind of method interconnected between LAN system and its internal controller system
CN107659934A (en) * 2017-10-19 2018-02-02 上海斐讯数据通信技术有限公司 A kind of control method and wireless network access device of wireless network connection
WO2018033153A1 (en) * 2016-08-18 2018-02-22 中兴通讯股份有限公司 Method and device for processing ip address conflict in evpn
CN109088959A (en) * 2018-11-07 2018-12-25 迈普通信技术股份有限公司 A kind of address distribution method, apparatus and system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7480710B1 (en) * 2004-07-13 2009-01-20 Cisco Technology, Inc. Resolving duplication of IP addresses in IP networks
CN102231764A (en) * 2011-06-22 2011-11-02 华为技术有限公司 Method and device for distributing network addresses
CN103188354B (en) * 2013-03-29 2016-05-25 北京东土科技股份有限公司 A kind of detection method and device of node address conflict
CN105430114B (en) * 2015-11-13 2019-09-10 上海斐讯数据通信技术有限公司 A kind of IP address conflict detection method, system and access layer equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331192A (en) * 2015-06-23 2017-01-11 中兴通讯股份有限公司 Network protocol IP address allocation method and device
WO2018033153A1 (en) * 2016-08-18 2018-02-22 中兴通讯股份有限公司 Method and device for processing ip address conflict in evpn
CN106899456A (en) * 2017-03-14 2017-06-27 深圳市友华通信技术有限公司 A kind of link detecting and the implementation method repaired
CN107370647A (en) * 2017-07-25 2017-11-21 郑州云海信息技术有限公司 A kind of method interconnected between LAN system and its internal controller system
CN107659934A (en) * 2017-10-19 2018-02-02 上海斐讯数据通信技术有限公司 A kind of control method and wireless network access device of wireless network connection
CN109088959A (en) * 2018-11-07 2018-12-25 迈普通信技术股份有限公司 A kind of address distribution method, apparatus and system

Also Published As

Publication number Publication date
WO2020233159A1 (en) 2020-11-26
CN111988153A (en) 2020-11-24

Similar Documents

Publication Publication Date Title
EP2214383B1 (en) Automatically releasing resources reserved for subscriber devices within a broadband access network
US20120023207A1 (en) Automatic assignment of hardware addresses within computer networks
US7152099B1 (en) Friend configuration and method for network devices
CN108777722B (en) Multi-system networking communication method and device, mobile terminal and storage medium
US20050188069A1 (en) Zero-configuring IP addresses for peer-to-peer networks
US20120124242A1 (en) Server and method for testing pxe function of network interface card
JP2002368763A (en) Network system, server unit and client unit, and method and program for providing network ip address
US20140244860A1 (en) Method To Publish Remote Management Services Over Link Local Network For Zero-Touch Discovery, Provisioning And Management
US10148610B2 (en) Method to publish remote management services over link local network for zero-touch discovery, provisioning, and management
CN103957288A (en) Method, device and equipment for IP address dynamic allocation
JP2004048649A (en) Method, program for managing network device and network controller
US20070239860A1 (en) Information processing device, network connection method, and program recording medium
CN107547274B (en) Multi-network-port aggregation method and device
CN110704115A (en) Method, device and system for configuring BMC (baseboard management controller) of server
JP4684283B2 (en) DHCP client / server device and method for providing DHCP server service over a network
EP1993238A1 (en) A device and method and system for acquiring ipv6 address
US20060123102A1 (en) System and method for allocating resources on a network
CN106452860B (en) Equipment deployment method and device
CN111988153B (en) Network exception handling method and device and household electrical appliance
WO2016202016A1 (en) Device management method, apparatus and system
CN106878485B (en) Message processing method and device
US20140122680A1 (en) Information processing apparatus and method, and non-transitory computer readable medium
US10389681B2 (en) Auto discovery of network elements by defining new extension in DHCP options for management server IP addresses
CN111988446B (en) Message processing method and device, electronic equipment and storage medium
CN107070725A (en) A kind of method that server two-level management intermodule communication is shaken hands

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