WO2020108418A1 - 数据传输方法、装置及系统 - Google Patents

数据传输方法、装置及系统 Download PDF

Info

Publication number
WO2020108418A1
WO2020108418A1 PCT/CN2019/120451 CN2019120451W WO2020108418A1 WO 2020108418 A1 WO2020108418 A1 WO 2020108418A1 CN 2019120451 W CN2019120451 W CN 2019120451W WO 2020108418 A1 WO2020108418 A1 WO 2020108418A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
log server
log
received
receive
Prior art date
Application number
PCT/CN2019/120451
Other languages
English (en)
French (fr)
Inventor
盛建
韩涛
姜伟
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19888578.2A priority Critical patent/EP3869741B1/en
Publication of WO2020108418A1 publication Critical patent/WO2020108418A1/zh
Priority to US17/327,019 priority patent/US11444913B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803Home automation networks
    • H04L12/2807Exchanging configuration information on appliance services in a home automation network
    • H04L12/2812Exchanging configuration information on appliance services in a home automation network describing content present in a home automation network, e.g. audio video content
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/256NAT traversal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/16Threshold monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/251Translation of Internet protocol [IP] addresses between different IP versions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2514Translation of Internet protocol [IP] addresses between local and global IP addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/663Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/686Types of network addresses using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks

Definitions

  • This application relates to the field of communication technology, and in particular, to a data transmission method, device, and system.
  • IP Internet Protocol
  • IPv4 Internet Protocol version 4, IPv4
  • IPv6 Internet Protocol version 6, IPv6
  • IPv4 addresses are continuously allocated to network equipment, and the problem of address exhaustion occurs.
  • IPv6 addresses have not been widely used, so the network is proposed.
  • Address translation (NAT) technology is proposed.
  • NAT technology is a technology that realizes the conversion between private network addresses and public network addresses. It can be widely used in various types of network access and various types of networks.
  • NAT can be divided into static NAT (Static) NAT and dynamic NAT (Dynamic NAT).
  • static NAT the mapping relationship between private network addresses and public network addresses is fixed;
  • dynamic NAT the mapping relationship between private network addresses and public network addresses is variable, for example, multiple different private network addresses at different time periods Can be mapped to the same public network address.
  • dynamic NAT is more flexible in deployment and has higher utilization of public network IPv4 addresses.
  • the mapping relationship log contains the correspondence between the private network address and the public network address of the user equipment; the NAT device refers to a network device that can dynamically map the public network address and the private network address.
  • the NAT device includes a carrier-grade NAT (carrier -grade NAT, CGN) equipment.
  • NAT devices generally send dynamic mapping relationship logs to the log server based on User Datagram Protocol (User Datagram Protocol, UDP). Since UDP is an unreliable transmission protocol, there is no guarantee that the log server can certainly receive the mapping relationship log sent by the NAT device, so the storage reliability of the mapping relationship log in the prior art is low.
  • UDP User Datagram Protocol
  • the embodiments of the present application provide a data transmission method, device and system, which can solve the problem of low reliability of log storage in the prior art.
  • a data transmission method is provided.
  • the method is applied to a network device, and the method includes:
  • the packet contains the correspondence between the public IP address and the private IP address.
  • the network device is a NAT device.
  • Customer equipment (CPE) located in a private network can communicate with equipment located in the Internet through a NAT device.
  • the user equipment located in the private network sends a data message to the NAT device, and the data message carries the private network IP address of the user equipment; after receiving the data message carrying the private network IP address, the NAT device sends the data message
  • the private network IP address in the article is converted into a public network IP address, and the correspondence between the private network IP address and the public network IP address is established; the NAT device sends a data message carrying the public network IP address to the device located on the Internet .
  • the network device periodically sends a probe message to the log server.
  • the network device sends a probe message to the log server, and detects whether the log server can receive the message based on whether the probe response message returned by the log server is received. After receiving the message, the log message is sent to the log server, which improves the reliability of log message transmission and storage.
  • the detection message is a heartbeat detection message
  • the detection response message is a heartbeat detection response message, based on whether the detection response message returned by the log server is received, it is detected whether the log server can receive the report Articles, including:
  • the heartbeat detection message may be a request message, and the heartbeat detection response message may be an acknowledgement (ACKnowledgement, ACK) message.
  • ACK acknowledgement
  • the network device receives the ACK message, it means that the log server has successfully received the request message.
  • the log server cannot receive the heartbeat detection message sent by the network device, then The log server does not return a heartbeat detection response message to the network device. Therefore, after the network device sends the heartbeat detection message to the log server, it can determine whether the heartbeat detection response message returned by the log server is received within the first specified time period to determine Whether the log server can receive messages.
  • both the heartbeat detection message and the heartbeat detection response message include a payload field, and the payload field is used to carry a message type flag, a heartbeat detection message message type flag, and a heartbeat detection response message.
  • the text type tag is different.
  • the network device periodically sends heartbeat detection messages to the log server, and determines whether the log server is determined by receiving a heartbeat detection response message returned by the log server Whether the message can be received. After determining that the log server can receive the message, the log message is sent to the log server to ensure the reliability of log message transmission and storage.
  • the probe message includes an Internet Control Message Protocol (ICMP) probe message and a UDP probe message
  • the probe response message includes an ICMP probe response message and a UDP port. Reaching the message, based on whether the probe response message returned by the log server is received, to detect whether the log server can receive the message, including:
  • the UDP detection message may be a log message.
  • the method further includes: stopping sending other log messages to the log server.
  • the ICMP detection message is used to detect whether the IP address of the log server is reachable.
  • the log server cannot receive the ICMP probe message, that is, the log server's IP address is unreachable.
  • the method further includes:
  • the cumulative count is updated. The number of times the device sends ICMP probe messages to the log server; when the cumulative number of updates reaches the specified threshold, it is determined that the log server cannot receive messages.
  • the method further includes:
  • n is a positive integer.
  • an ICMP detection mechanism and a UDP detection mechanism are established between the network device and the log server.
  • the ICMP detection mechanism is used to detect whether the IP address of the log server is reachable, and the UDP detection mechanism is used to detect whether the UDP port of the log server is available.
  • the combination of the two detection mechanisms can detect whether the log server can receive messages. After determining that the log server can receive messages, it can send log messages to the log server to ensure the reliability of log message transmission and storage.
  • a data transmission device is provided.
  • the device is applied to a network device.
  • the device includes:
  • the sending unit is used to send a probe message to the log server
  • the detection unit is configured to detect whether the log server can receive the message based on whether the probe response message returned by the log server is received;
  • the sending unit is further configured to send a log message to the log server when it is determined that the log server can receive the message, the log message including the correspondence between the public network IP address and the private network IP address .
  • the detection message is a heartbeat detection message
  • the detection response message is a heartbeat detection response message
  • the device further includes: a determining unit
  • the detection unit is configured to detect whether a heartbeat detection response message returned by the log server is received within a first specified time period
  • the determining unit is configured to determine that the log server can receive the message when the heartbeat detection response message returned by the log server is received within the first specified time period;
  • the determining unit is further configured to determine that the log server cannot receive the message when the heartbeat detection response message returned by the log server is not received within the first specified time period.
  • the detection message includes an ICMP detection message and a UDP detection message
  • the device further includes: a determination unit;
  • the detection unit is configured to detect whether an ICMP probe response message returned by the log server is received within a second specified time period
  • the sending unit is configured to send the UDP probe message to the log server when the ICMP probe response message returned by the log server is received within the second specified time period;
  • the determining unit is configured to determine that the log server cannot receive the message when the UDP port unreachable message returned by the log server is received within the third specified time period;
  • the determining unit is further configured to determine that the log server can receive the message when the UDP port unreachable message returned by the log server is not received within the third specified time period.
  • the device further includes: a processing unit;
  • the processing unit is configured to update the cumulative number of times when the ICMP probe response message returned by the log server is not received within the second specified time period, and the cumulative number of updates is from the last time the log server was received After the returned ICMP probe response message to the current moment, the number of times the network device sent the ICMP probe message to the log server;
  • the determining unit is further configured to determine that the log server cannot receive the message when the updated cumulative number of times reaches the specified number of times threshold.
  • the sending unit is further configured to periodically send a UDP probe message to the log server after determining that the log server cannot receive the message;
  • the detection unit is configured to determine that the log server can receive the message when the UDP port unreachable message returned by the log server is not received within n consecutive cycles, where n is a positive integer.
  • a data transmission device including: a processor and a memory;
  • the memory is used to store a computer program, and the computer program includes program instructions
  • the processor is configured to call the program instructions to implement the data transmission method according to any one of the first aspect.
  • a computer-readable storage medium stores instructions, and when the instructions are executed by a processor, the data transmission method according to any one of the first aspect is implemented.
  • a data transmission system includes: a network device and at least one log server.
  • the network device includes the data transmission device according to any one of the second aspects.
  • FIG. 1 is a schematic structural diagram of a data transmission system provided by an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of another data transmission system provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of yet another data transmission system provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a heartbeat detection message/heartbeat detection response message provided by an embodiment of the present application
  • FIG. 6 is a flowchart of another data transmission method provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a data transmission device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another data transmission device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another network device provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a data transmission system provided by an embodiment of the present application. As shown in FIG. 1, the system includes: a network device 101 and at least one log server 102.
  • the network device 101 refers to a network device with a network address translation function.
  • the network device 101 is a NAT device, such as a CGN device, and the NAT device may be a router or a switch.
  • the embodiment of the present application does not limit the type of network device.
  • the log server 102 may be one server, or a server cluster composed of several servers, or a cloud computing service center.
  • the user equipment located in the private network can communicate with the equipment located in the Internet through the network equipment 101.
  • the user equipment located in the private network sends a data message to the network device 101, which carries the private network IP address of the user equipment; after receiving the data message carrying the private network IP address, the network device 101 will The private network IP address in the data packet is converted to the public network IP address, and the correspondence between the private network IP address and the public network IP address is established; the network device 101 sends the device with the public network IP address to the device located on the Internet Data message.
  • the user equipment located in the private network may be a tablet computer, a mobile phone, a computer, or other terminal equipment.
  • the network device 101 after establishing the correspondence between the private network IP address and the public network IP address, the network device 101 generates a dynamic mapping relationship log between the private network IP address and the public network IP address, hereinafter referred to as a log message
  • the log server 102 is used to receive and store log messages.
  • the network device 101 may perform the following work process: send a probe message to the log server; detect whether the log server can receive the message based on whether the probe response message returned by the log server is received; Make sure that the log server can receive messages and send log messages to the log server.
  • the network device 101 may periodically send a probe message to the log server 102.
  • a network device may be periodically triggered to send a detection message to the log server through a timer.
  • the timer may be integrated in the network device, or the timer may be an independent timing device.
  • the network device may send a detection message to the log server every 2 seconds, which is not limited in the embodiment of the present application.
  • the network device when the network device generates a large number of log messages during operation, it is usually necessary to deploy multiple log servers to receive the log messages generated by the network device.
  • the network device is a CGN device
  • the number of log messages it generates is huge. Therefore, each CGN device usually needs to set up multiple log servers.
  • FIG. 2 is a schematic structural diagram of another data transmission system provided by an embodiment of the present application.
  • the data transmission system includes one network device 101 and multiple log servers 102, and the network device 101 Probe messages are periodically polled to multiple log servers 102.
  • the log server 102 is polled to send log messages to skip the one that cannot receive messages.
  • Log server is polled to send log messages to skip the one that cannot receive messages.
  • FIG. 3 is a schematic structural diagram of yet another data transmission system provided by an embodiment of the present application.
  • the data transmission system includes multiple network devices 101 and multiple log servers 102, and multiple networks The device shares the multiple log servers to maximize the utilization of log server resources.
  • FIG. 4 is a flowchart of a data transmission method provided by an embodiment of the present application. The method can be applied to a data transmission system as shown in any one of FIGS. 1 to 3. As shown in FIG. 4, the method includes:
  • Step 401 The network device sends a heartbeat detection message to the log server.
  • the network device may periodically send a heartbeat detection message to the log server.
  • the heartbeat detection message is a UDP-based message.
  • the heartbeat detection message may be a request message.
  • the heartbeat detection packet includes an IP header, a UDP header, and a payload field.
  • the IP header includes the IP address of the network device that sent the heartbeat detection message (that is, the source address) and the IP address of the log server that received the heartbeat detection message (that is, the destination address), and the UDP header includes the source port number and The destination port number and payload field are used to carry the packet type flag (type).
  • the message type mark of the heartbeat detection message may be a single character, character string, letter, or number. The embodiment of the present application does not limit the form of the message type mark. For example, when the type in FIG. 5 is 0, it means that the packet is a heartbeat detection packet.
  • Step 402 The network device detects whether a heartbeat detection response message returned by the log server is received within the first specified time period; when a heartbeat detection response message returned by the log server is received within the first specified time period, step 403 is executed; When the heartbeat detection response message returned by the log server is not received within the first specified time period, step 405 is executed.
  • the log server may generate a heartbeat detection response message, and send the heartbeat detection response message to the network device.
  • the heartbeat detection response message may be an ACK message.
  • the log server returns an ACK message to the network device, indicating that the log server has successfully received the request message.
  • the data frame structure of the heartbeat detection response message is the same as the data frame structure of the heartbeat detection message, and the packet type flag of the heartbeat detection message and the packet type flag of the heartbeat detection response message are different. For example, when the type in FIG. 5 is 0, it indicates that the message is a heartbeat detection message, and when the type in FIG. 5 is 1, it indicates that the message is a heartbeat detection response message.
  • the log server cannot receive the heartbeat detection message sent by the network device , The log server will not return a heartbeat detection response message to the network device. Therefore, after sending the heartbeat detection message to the log server, the network device can check whether the heartbeat detection response message returned by the log server is received within the first specified time period. To determine whether the log server can receive messages.
  • the first specified period of time may also be referred to as a heartbeat timeout waiting time.
  • the first specified period of time may be 1 second.
  • the network device After the network device sends the heartbeat detection message, the heartbeat detection returned by the log server is not received within 1 second. In response to the message, the network device can determine that the log server cannot receive the message.
  • Step 403 The network device determines that the log server can receive the message.
  • Step 404 The network device sends a log message to the log server.
  • the network device After determining that the log server can receive the message, the network device sends the log message to the log server, which can improve the reliability of log message transmission and storage.
  • Step 405 The network device determines that the log server cannot receive the message.
  • the network device stops sending the log message to the log server to avoid the loss of the log message.
  • step 405 after performing step 405, it may return to the above step 401 and repeat the steps of the above data transmission method.
  • the network device by establishing a heartbeat detection mechanism between the network device and the log server, the network device periodically sends a heartbeat detection message to the log server, by detecting whether the log server returns The heartbeat detection response message determines whether the log server can receive the message. After determining that the log server can receive the message, the log message is sent to the log server, which improves the reliability of log message transmission and storage.
  • the probe message includes an ICMP probe message and a UDP probe message
  • the probe response message includes an ICMP probe response message and a UDP port unreachable message.
  • FIG. 6 is a flowchart of another data transmission method provided by an embodiment of the present application. The method can be applied to a data transmission system as shown in any of FIGS. 1 to 3. As shown in FIG. 6, the method includes :
  • Step 601 The network device sends an ICMP detection message to the log server.
  • the network device periodically sends an ICMP probe message to the log server.
  • the ICMP probe message may be a ping message.
  • the ICMP probe response message may be a pong message.
  • Step 602 The network device detects whether an ICMP probe response message returned by the log server is received within the second specified time period; when an ICMP probe response message returned by the log server is received within the second specified time period, step 603 is executed; When the ICMP probe response message returned by the log server is not received within the second specified time period, step 610 is performed.
  • the ICMP detection message is used to detect whether the IP address of the log server is reachable.
  • the log server cannot receive the ICMP probe message, that is, the log server's IP address is unreachable.
  • the log server may generate an ICMP detection response message and return the ICMP detection response message to the network device.
  • the second specified time period may also be referred to as an ICMP timeout wait time.
  • the second specified time period may be 1 second.
  • the network device sends the ICMP probe message, if the ICMP probe returned by the log server is not received within 1 second
  • the network device can determine that the IP address of the log server is unreachable, and can further mark the log server as unavailable; if an ICMP probe response message returned by the log server is received within 1 second, the network device can The IP address of the log server is determined to be reachable, and the log server can be further marked as available.
  • Step 603 The network device sends a UDP probe message to the log server.
  • the working principle of UDP detection is: when the UDP port of the log server fails or the UDP port is not opened, the UDP port is unavailable, the log server will return the UDP port unreachable after receiving the UDP detection message sent by the network device Message; when the UDP port of the log server is available, the log server does not respond after receiving the UDP probe message sent by the network device, that is, the log server does not return a probe response message to the network device.
  • the UDP port refers to the log service port of the log server, which may also be called an application port or a software port.
  • the UDP detection message is used to detect whether the software application layer of the log server is available.
  • the UDP probe message sent by the network device to the log server in step 603 may be a log message.
  • the UDP detection message may also be an empty message, that is, the payload of the message is empty. In this case, the UDP detection message only plays the role of UDP detection, which is not limited in this embodiment of the present application.
  • Step 604 The network device detects whether the UDP port unreachable message returned by the log server is received within the third specified period; when the UDP port unreachable message returned by the log server is not received within the third specified period, the step is performed 605; When the UDP port unreachable message returned by the log server is received within the third specified time period, step 607 is performed.
  • the third specified time period may also be referred to as UDP timeout waiting time.
  • the third specified time period may be 1 second.
  • the network device sends a UDP probe message, the UDP port returned by the log server cannot be received within 1 second.
  • the network device can determine that the log server cannot receive the message.
  • Step 605 The network device determines that the log server can receive the message.
  • Step 606 The network device sends a log message to the log server.
  • the network device After determining that the log server can receive the message, the network device sends the log message to the log server, which can improve the reliability of log message transmission and storage.
  • Step 607 The network device determines that the log server cannot receive the message.
  • the network device stops sending other log reports to the log server To avoid the loss of log messages.
  • Step 608 The network device periodically sends a UDP probe message to the log server.
  • the network device when the log server is marked as available, that is, when the IP address of the log server is reachable, the network device periodically sends a UDP probe message to the log server.
  • the UDP detection message in step 608 is an empty message, and the UDP detection message is only used to detect whether the UDP port of the log server is available.
  • Step 609 When the UDP port unreachable message returned by the log server is not received within n consecutive cycles, the network device determines that the log server can receive the message, and n is a positive integer.
  • the network device determines that the log server can receive the message.
  • the network device executes the above step 606.
  • Step 610 The network device updates the cumulative number of times.
  • the cumulative number of updates is the number of times the network device sent an ICMP probe message to the log server from the last time it received the ICMP probe response message returned by the log server to the current time.
  • the network device receives the ICMP probe response message returned by the log server, the above cumulative number of times is cleared; when the network device sends the ICMP probe message to the log server, the log server is not received within the second specified time period The returned ICMP probe response message will increase the accumulated number by 1.
  • the cumulative number of times the network device has been updated is 0; if m consecutive times before the current time During the sending period of the ICMP probe message, none of the network devices receives the ICMP probe response message returned by the log server.
  • the cumulative number of times the network device has been updated is m+1, and m ⁇ 1.
  • Step 611 When the cumulative number of times after the update reaches the specified number of times threshold, the network device determines that the log server cannot receive the message.
  • the specified number of times threshold may be 3.
  • the embodiment of the present application does not limit the set specified number of times threshold.
  • the network device may determine that the IP address of the log server is unreachable, and then determine that the log server cannot receive messages.
  • the above steps 601 to 611 may be repeatedly executed.
  • step 611 after performing step 611, it may return to step 601 described above and repeat the steps of the data transmission method described above.
  • the data transmission method establishes an ICMP detection mechanism and a UDP detection mechanism between the network device and the log server.
  • the network device detects whether the log server's IP address is reachable based on the ICMP detection method, and based on The UDP detection method detects whether the UDP port of the log server is available, and then determines whether the log server can receive messages. After determining that the log server can receive messages, it sends log messages to the log server, which improves the transmission and storage of log messages. reliability.
  • a data transmission method based on heartbeat detection a heartbeat detection mechanism is established between the network device and the log server, and the network device only needs to send a heartbeat detection message to the log server to detect the log Whether the server can receive messages.
  • the data transmission method used in this data transmission method consumes less transmission resources; the data based on the combination of ICMP detection and UDP detection Transmission method, there is no need to establish a new communication mechanism between the network device and the log server, and its versatility is high. For the operator scenario, there are more types and numbers of third-party server manufacturers that are connected to the CGN equipment, and their achievability is higher. .
  • heartbeat detection, ICMP detection, and UDP detection can also be combined to detect whether the log server can receive packets to further improve the reliability of log storage; or, it can be detected based on other detection mechanisms. Whether the log server can receive the message, the embodiment of the present application does not limit the detection mechanism used.
  • the data transmission device 700 includes a sending unit 701, a detecting unit 702, a determining unit 703, and a processing unit 704. These units can perform the corresponding functions of the network device in the above method embodiments.
  • the sending unit 701 is used to support the network device to execute step 401 and step 404 in FIG. 4, and/or the step 601, step 603, step 606 and step 608 in FIG. 6;
  • the detection unit 702 is used to support the network device execution diagram Step 402 in FIG. 4, and/or, step 602 and step 604 in FIG.
  • the determining unit 703 is used to support the network device to perform step 403 and step 405 in FIG. 4, and/or, step 605 in FIG. Step 607, Step 609, and Step 611;
  • the processing unit 704 is used to support the network device to perform step 610 in FIG. 6, and/or other processes performed by the network device in the technology described herein.
  • the sending unit 701 is used to perform various information transmission performed by the network device in the above method embodiment; the detection unit 702 is used to perform the detection action performed by the network device in the above method embodiment; and the determination unit 703 is used to perform The determination action performed by the network device in the above method embodiment; the processing unit 704 is configured to perform other processes performed by the network device in the above method embodiment except for the information transmission, detection action, and determination action.
  • the sending unit 701 is used to send a probe message to the log server;
  • the detection unit 702 is used to detect whether the log server can receive the message based on whether a probe response message returned by the log server is received; the sending unit 701 also When it is determined that the log server can receive messages, send log messages to the log server.
  • the specific execution process please refer to the detailed description of the corresponding steps in the embodiments shown in FIG. 4 or FIG. 6, and the embodiments of the present application will not repeat them one by one here.
  • FIG. 8 shows another possible structural schematic diagram of the data transmission device involved in the above embodiment, and the data transmission device 800 can also implement the implementation shown in FIG. 4 or FIG. 6 Examples of network device functions.
  • the data transmission device 800 includes a storage unit 801, a processing unit 802, and a communication unit 803.
  • the communication unit 803 is used to support communication between the network device and other network entities, for example, to the log server shown in FIG. 4 or FIG. 6, for example, the communication unit 803 is used to support the network device to execute the Step 401 and step 404, and/or, step 601, step 603, step 606 and step 608 in FIG.
  • the processing unit 802 is used to control and manage the actions of the network device.
  • the processing unit 802 is used to support the network device to perform step 402, step 403, and step 405 in FIG. 4, step 602, step 604, and step 605 in FIG. Step 607, Step 609, Step 610 and Step 611, and/or other processes performed by the network device in the technology described herein.
  • the storage unit 801 is used to store program codes and data of network devices. For the specific execution process, please refer to the detailed description of the corresponding steps in the embodiments shown in FIG. 4 or FIG. 6, and the embodiments of the present application will not repeat them one by one here.
  • the processing unit 802 may be a processor, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present application.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of DSP and microprocessor, and so on.
  • the communication unit 803 may be a transceiver, and the storage unit 801 may be a memory.
  • the processing unit 802 is a processor
  • the communication unit 803 is a transceiver
  • the storage unit 801 is a memory
  • the structure of the network device involved in the embodiment of the present application may be as shown in FIG. 9.
  • the network device 900 includes a processor 902, a transceiver 903, a memory 901, and a bus 904.
  • the processor 902, the transceiver 903 and the memory 901 are connected to each other through a bus 904;
  • the bus 904 may be a peripheral component interconnection (PCI) bus or an extended industry standard architecture (extended industry architecture (EISA) bus) Wait.
  • PCI peripheral component interconnection
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, and a control bus. For ease of representation, only a thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the network device 900 can realize the functions of the network device in the embodiment shown in FIG. 4 or FIG. 6.
  • the processor 902 and the transceiver 903 may perform corresponding functions of the network device in the above method example.
  • the transceiver 903 is used to support the network device 900 to perform step 401 and step 404 in FIG. 4 and/or step 601, step 603, step 606 and step 608 in FIG.
  • the processor 902 is used to support the network device 900 to perform step 402, step 403, and step 405 in FIG. 4, step 602, step 604, step 605, step 607, step 609, step 610, and step 611 in FIG. 6, and/or Or other processes performed by network devices in the technology described herein.
  • the memory 901 is used to store program codes and data of the network device 900.
  • For the specific execution process please refer to the detailed description of the corresponding steps in the embodiments shown in FIG. 4 or FIG. 6, and the embodiments of the present application will not repeat them one by one here.
  • FIG. 10 is a schematic structural diagram of another network device 1000 provided by an embodiment of the present application.
  • the network device 1000 may be a network device that has a network address translation function and can forward data, such as a router or a switch, and the network device 1000 can implement the functions of the network device in the foregoing method embodiments.
  • the network device 1000 includes a main control board 1001 and an interface board 1002.
  • the main control board 1001 includes: a processor 1003 and a memory 1004.
  • the interface board 1002 includes: a processor 1005, a memory 1006, and an interface card 1007.
  • the main control board 1001 and the interface board 1002 are coupled.
  • the hardware can perform the corresponding functions in the above method examples.
  • the memory 1006 can be used to store the program code of the interface board 1002, and the processor 1005 can be used to call the program code in the memory 1006 to trigger the interface card 1007 to perform the network in the above method embodiment.
  • the processor 1005 calls the program code in the memory 1006 to trigger the interface card 1007 to support the network device 1000 to perform the steps 401 and 404 in FIG. 4 and/or the steps in FIG. 6 601, step 603, step 606 and step 608.
  • the processor 1005 is also used to send the service identification to the main control board 1001.
  • the memory 1004 may be used to store the program code of the main control board 1001, and the processor 1003 is used to call the program code in the memory 1004 to perform other processing of the network device in addition to information transmission and reception in the foregoing method embodiment.
  • the processor 1003 is used to support the network device 1000 to perform step 402, step 403, and step 405 in FIG. 4, step 602, step 604, step 605, step 607, step 609, step 610, and step 611 in FIG. 6, And/or other processes performed by the network device in the techniques described herein.
  • the memory 1004 is used to store the program codes and data of the main control board 1001.
  • the specific execution process please refer to the detailed description of the corresponding steps in the embodiments shown in FIG. 4 or FIG. 6, and the embodiments of the present application will not repeat them one by one here.
  • an IPC control channel is established between the main control board 1001 and the interface board 1002, and the IPC control channel is used for communication between the main control board 1001 and the interface board 1002.
  • An embodiment of the present application provides a computer-readable storage medium having instructions stored thereon, and when the instructions are executed by a processor, a data transmission method as described in any of the method-side embodiments is implemented .
  • any of the device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be The physical unit may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.
  • the steps of the method or algorithm described in the disclosure of the embodiments of the present application may be implemented by hardware, or by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (read only memory (ROM), erasable programmable read-only memory (erasable (programmable ROM, EPROM), electrically erasable programmable read only memory (electrically EPROM, EEPROM), hard disk, removable hard disk, optical disk or any other form of storage medium well known in the art.
  • An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • Computer-readable media includes computer storage media and communication media, where communication media includes any medium that facilitates transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • Automation & Control Theory (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Debugging And Monitoring (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请公开了一种数据传输方法、装置及系统,属于通信技术领域。该方法应用于网络设备,包括:向日志服务器发送探测报文;基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文;当确定日志服务器能够接收报文,向该日志服务器发送日志报文。本申请通过在网络设备与日志服务器之间建立探测机制,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,提高了日志报文传输和存储的可靠性。

Description

数据传输方法、装置及系统
本申请要求于2018年11月29日提交中国国家知识产权局、申请号201811440792.9、申请名称为“数据传输方法、装置及系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,特别涉及一种数据传输方法、装置及系统。
背景技术
互联网协议(Internet Protocol,IP)地址也称为网际协议地址,IP地址是互联网协议提供的一种统一的地址格式,可以由地址服务器分配给互联网中支持互联网协议的每一台网络设备。目前,比较常见的互联网协议为第四版互联网协议(Internet Protocol version 4,IPv4)和第六版互联网协议(Internet Protocol version 6,IPv6)。
随着互联网中网络设备规模的不断扩大,IPv4地址被不断的分配给网络设备,出现了地址枯竭的问题,而由于目前众多网络设备均采用IPv4地址,IPv6地址还未广泛应用,因此提出了网络地址转换(network address translation,NAT)技术。
NAT技术是一种实现私网地址和公网地址相互转换的技术,其可以广泛应用于各种类型的网络接入方式和各种类型的网络中。NAT可分为静态NAT(Static NAT)和动态NAT(Dynamic NAT)。对于静态NAT,私网地址和公网地址的映射关系是固定的;对于动态NAT,私网地址和公网地址的映射关系是可变的,例如在不同时间段,多个不同的私网地址可以分别映射到同一公网地址。相比于静态NAT,动态NAT在部署上更加灵活且对公网IPv4地址的利用率更高。但对于动态NAT,基于对安全问题的考虑和法律法规的溯源要求,需要部署日志服务器存储NAT设备产生的映射关系日志(映射关系日志亦可简称为日志报文)。其中,映射关系日志包含用户设备的私网地址和公网地址之间的对应关系;NAT设备指能够对公网地址和私网地址进行动态映射的网络设备,NAT设备包括运营商级NAT(carrier-grade NAT,CGN)设备。
目前NAT设备一般基于用户数据报协议(User Datagram Protocol,UDP)向日志服务器发送动态映射关系日志。由于UDP为非可靠的传输协议,无法保证日志服务器一定能够接收到NAT设备发送的映射关系日志,因此现有技术中映射关系日志的存储可靠性较低。
发明内容
本申请实施例提供了一种数据传输方法、装置及系统,可以解决现有技术中日志存储可靠性低的问题。
第一方面,提供了一种数据传输方法,该方法应用于网络设备,所述方法包括:
向日志服务器发送探测报文;基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文;当确定日志服务器能够接收报文时,向日志服务 器发送日志报文,该日志报文包含公网IP地址和私网IP地址之间的对应关系。
可选地,该网络设备为NAT设备。位于专用网(也称为内网或接入网)中的用户设备(customer premise equipment,CPE)可通过NAT设备与位于因特网中的设备进行通信。位于专用网中的用户设备向NAT设备发送数据报文,该数据报文中携带有用户设备的私网IP地址;NAT设备在接收到携带有私网IP地址的数据报文后,将数据报文中的私网IP地址转换为公网IP地址,并建立私网IP地址与公网IP地址之间的对应关系;NAT设备向位于因特网中的设备发送携带有公网IP地址的数据报文。
可选地,网络设备周期性地向日志服务器发送探测报文。
需要说明的是,本申请提供的数据传输方法,网络设备向日志服务器发送探测报文,并基于是否接收到日志服务器返回的探测响应报文检测日志服务器是否能够接收报文,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,提高了日志报文传输和存储的可靠性。
在一种可能的实现方式中,探测报文为心跳探测报文,探测响应报文为心跳探测响应报文,则基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文,包括:
检测在第一指定时段内是否接收到日志服务器返回的心跳探测响应报文;当在第一指定时段内接收到日志服务器返回的心跳探测响应报文时,确定该日志服务器能够接收报文;当在第一指定时段内未接收到日志服务器返回的心跳探测响应报文时,确定该日志服务器无法接收报文。
其中,心跳探测报文可以是请求(request)报文,心跳探测响应报文可以是确认字符(acknowledgement,ACK)报文。网络设备接收到ACK报文,即表示日志服务器已成功接收request报文。
需要说明的是,当网络设备与日志服务器之间的通信链路中断或日志服务器发生故障(硬件故障或应用级层软件故障)时,日志服务器无法接收到网络设备发送的心跳探测报文,则日志服务器不会向网络设备返回心跳探测响应报文,因此网络设备向日志服务器发送心跳探测报文后,可以通过检测第一指定时段内是否接收到日志服务器返回的心跳探测响应报文,以确定该日志服务器是否能够接收报文。
可选地,心跳探测报文和心跳探测响应报文中均包括载荷(payload)字段,载荷字段用于携带报文类型标记,心跳探测报文的报文类型标记和心跳探测响应报文的报文类型标记不同。
需要说明的是,通过在网络设备与日志服务器之间建立心跳探测机制,网络设备周期性向日志服务器发送心跳探测报文,通过检测是否接收到日志服务器返回的心跳探测响应报文,以确定日志服务器是否能够接收报文,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,保证了日志报文传输和存储的可靠性。
在另一种可能的实现方式中,探测报文包括因特网控制报文协议(Internet Control Message Protocol,ICMP)探测报文和UDP探测报文,探测响应报文包括ICMP探测响应报文和UDP端口不可达报文,则基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文,包括:
检测在第二指定时段内是否接收到日志服务器返回的ICMP探测响应报文;当在 第二指定时段内接收到日志服务器返回的ICMP探测响应报文时,向日志服务器发送UDP探测报文;当在第三指定时段内接收到日志服务器返回的UDP端口不可达报文时,确定该日志服务器无法接收报文;当在第三指定时段内未接收到日志服务器返回的UDP端口不可达报文时,确定该日志服务器能够接收报文。
可选地,UDP探测报文可以为一个日志报文,则在确定日志服务器无法接收报文之后,所述方法还包括:停止向日志服务器发送其他日志报文。
需要说明的是,ICMP探测报文用于检测日志服务器的IP地址是否可达。当网络设备与日志服务器之间的通信链路中断,或者日志服务器发生硬件故障导致日志服务器的物理端口不可用时,日志服务器无法接收到ICMP探测报文,即日志服务器的IP地址不可达。
可选地,在检测第二指定时段内是否接收到日志服务器返回的ICMP探测响应报文之后,所述方法还包括:
当在第二指定时段内未接收到日志服务器返回的ICMP探测响应报文,更新累计次数,更新后的累计次数为从最近一次接收到日志服务器返回的ICMP探测响应报文之后至当前时刻,网络设备向日志服务器发送ICMP探测报文的次数;当更新后的累计次数达到指定次数阈值,确定该日志服务器无法接收报文。
可选地,当网络设备在第二指定时段内接收到日志服务器返回的ICMP探测响应报文,且向日志服务器发送UDP报文后,在第三指定时段内接收到日志服务器返回的UDP端口不可达报文,进而确定日志服务器无法接收报文之后,所述方法还包括:
周期性向日志服务器发送UDP探测报文;
当连续n个周期内未接收到所述日志服务器返回的UDP端口不可达报文,确定所述日志服务器能够接收报文,n为正整数。
需要说明的是,在网络设备与日志服务器之间建立ICMP探测机制和UDP探测机制,ICMP探测机制用于检测日志服务器的IP地址是否可达,UDP探测机制用于检测日志服务器的UDP端口是否可用,结合该两种探测机制可以检测日志服务器是否能够接收报文,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,保证了日志报文传输和存储的可靠性。
第二方面,提供了一种数据传输装置,所述装置应用于网络设备,所述装置包括:
发送单元,用于向日志服务器发送探测报文;
检测单元,用于基于是否接收到所述日志服务器返回的探测响应报文,检测所述日志服务器是否能够接收报文;
所述发送单元,还用于当确定所述日志服务器能够接收报文时,向所述日志服务器发送日志报文,所述日志报文包含公网IP地址和私网IP地址之间的对应关系。
可选地,所述探测报文为心跳探测报文,所述探测响应报文为心跳探测响应报文,所述装置还包括:确定单元;
所述检测单元,用于检测在第一指定时段内是否接收到所述日志服务器返回的心跳探测响应报文;
所述确定单元,用于当在所述第一指定时段内接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器能够接收报文;
所述确定单元,还用于当在所述第一指定时段内未接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器无法接收报文。
可选地,所述探测报文包括ICMP探测报文和UDP探测报文,所述装置还包括:确定单元;
所述检测单元,用于检测在第二指定时段内是否接收到所述日志服务器返回的ICMP探测响应报文;
所述发送单元,用于当在所述第二指定时段内接收到所述日志服务器返回的ICMP探测响应报文时,向所述日志服务器发送所述UDP探测报文;
所述确定单元,用于当在第三指定时段内接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器无法接收报文;
所述确定单元,还用于当在所述第三指定时段内未接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器能够接收报文。
可选地,所述装置还包括:处理单元;
所述处理单元,用于当在所述第二指定时段内未接收到所述日志服务器返回的ICMP探测响应报文,更新累计次数,更新后的累计次数为从最近一次接收到所述日志服务器返回的ICMP探测响应报文之后至当前时刻,所述网络设备向所述日志服务器发送ICMP探测报文的次数;
所述确定单元,还用于当所述更新后的累计次数达到所述指定次数阈值,确定所述日志服务器无法接收报文。
可选地,所述发送单元,还用于在确定所述日志服务器无法接收报文之后,周期性向所述日志服务器发送UDP探测报文;
所述检测单元,用于当连续n个周期内未接收到所述日志服务器返回的UDP端口不可达报文,确定所述日志服务器能够接收报文,其中n为正整数。
第三方面,提供了一种数据传输装置,包括:处理器和存储器;
所述存储器,用于存储计算机程序,该计算机程序包括程序指令;
所述处理器,用于调用所述程序指令,实现如第一方面任一所述的数据传输方法。
第四方面,提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有指令,当所述指令被处理器执行时,实现如第一方面任一所述的数据传输方法。
第五方面,提供了一种数据传输系统,所述系统包括:网络设备和至少一个日志服务器,所述网络设备包括如第二方面任一所述的数据传输装置。
附图说明
图1是本申请实施例提供的一种数据传输系统的结构示意图;
图2是本申请实施例提供的另一种数据传输系统的结构示意图;
图3是本申请实施例提供的又一种数据传输系统的结构示意图;
图4是本申请实施例提供的一种数据传输方法的流程图;
图5是本申请实施例提供的一种心跳探测报文/心跳探测响应报文的结构示意图;
图6是本申请实施例提供的另一种数据传输方法的流程图;
图7是本申请实施例提供的一种数据传输装置的结构示意图;
图8是本申请实施例提供的另一种数据传输装置的结构示意图;
图9是本申请实施例提供的一种网络设备的结构示意图;
图10是本申请实施例提供的另一种网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施方式作进一步地详细描述。
图1是本申请实施例提供的一种数据传输系统的结构示意图,如图1所示,该系统包括:网络设备101和至少一个日志服务器102。
其中,网络设备101指具备网络地址转换功能的网络设备。可选地,网络设备101为NAT设备,如CGN设备,NAT设备可以是路由器或交换机,本申请实施例对网络设备的类型不做限定。日志服务器102可以是一台服务器,或者由若干台服务器组成的服务器集群,或者是一个云计算服务中心。
可选地,位于专用网中的用户设备可通过网络设备101与位于因特网中的设备进行通信。位于专用网中的用户设备向网络设备101发送数据报文,该数据报文中携带有用户设备的私网IP地址;网络设备101在接收到携带有私网IP地址的数据报文后,将数据报文中的私网IP地址转换为公网IP地址,并建立私网IP地址与公网IP地址之间的对应关系;网络设备101向位于因特网中的设备发送携带有公网IP地址的数据报文。其中,位于专用网中的用户设备可以是平板电脑、手机、计算机或其它终端设备等。在本申请实施例中,网络设备101在建立私网IP地址与公网IP地址之间的对应关系后,生成私网IP地址和公网IP地址的动态映射关系日志,以下简称为日志报文,日志服务器102用于接收并存储日志报文。
可选地,网络设备101生成日志报文后,可以执行以下工作过程:向日志服务器发送探测报文;基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文;当确定日志服务器能够接收报文,向日志服务器发送日志报文。
可选地,网络设备101可以周期性向日志服务器102发送探测报文。例如可以通过定时器定期触发网络设备向日志服务器发送探测报文,该定时器可以集成在网络设备中,该定时器也可以是独立的定时装置。示例的,网络设备可以每隔2秒向日志服务器发送一次探测报文,本申请实施例对此不做限定。
可选地,当网络设备在运行过程中产生的日志报文数量较大时,通常需要部署多台日志服务器接收该网络设备产生的日志报文。例如当该网络设备为CGN设备,由于CGN设备部署在核心网中,其产生的日志报文的数量巨大,因此每台CGN设备通常需要对应设置多台日志服务器。
可选地,图2是本申请实施例提供的另一种数据传输系统的结构示意图,如图2所示,该数据传输系统中包括一台网络设备101和多台日志服务器102,网络设备101向多台日志服务器102定期轮询发送探测报文,当确定某台日志服务器无法接收报文后,则向该多台日志服务器102轮询发送日志报文时跳过该台无法接收报文的日志服务器。
需要说明的是,本申请实施例通过部署多台日志服务器,当网络设备确定某台日 志服务器无法接收报文后(由通信链路中断或服务器故障导致),在向该多台日志服务器轮询发送日志报文时可以跳过该台无法接收报文的日志服务器,提高了日志存储的可靠性。
可选地,图3是本申请实施例提供的又一种数据传输系统的结构示意图,如图3所示,该数据传输系统中包括多台网络设备101和多台日志服务器102,多台网络设备共享该多台日志服务器,可以实现日志服务器资源最大化利用。
当网络设备向日志服务器发送的探测报文的类型不同,则对应的数据传输方法不同,本申请以下实施例针对不同类型的探测报文提供了不同的数据传输方法的实现过程。
在一个示例中,探测报文为心跳探测报文,探测响应报文为心跳探测响应报文。相应的,图4是本申请实施例提供的一种数据传输方法的流程图,该方法可以应用于如图1至3任一所示的数据传输系统,如图4所示,该方法包括:
步骤401、网络设备向日志服务器发送心跳探测报文。
可选地,网络设备可以周期性向日志服务器发送心跳探测报文。该心跳探测报文为基于UDP的报文。心跳探测报文可以是request报文。
示例的,参见图5,心跳探测报文中包括IP包头(Header)、UDP包头和载荷字段。其中,IP包头中包括发送该心跳探测报文的网络设备的IP地址(即源地址)和接收该心跳探测报文的日志服务器的IP地址(即目的地址),UDP包头中包括源端口号和目的端口号,载荷字段用于携带报文类型标记(type)。可选地,心跳探测报文的报文类型标记可以是单个字符、字符串、字母或数字,本申请实施例对报文类型标记的形式不做限定。例如,当图5中的type为0时,表示该报文为心跳探测报文。
步骤402、网络设备检测在第一指定时段内是否接收到日志服务器返回的心跳探测响应报文;当在第一指定时段内接收到日志服务器返回的心跳探测响应报文时,执行步骤403;当在第一指定时段内未接收到日志服务器返回的心跳探测响应报文时,执行步骤405。
可选地,日志服务器接收到网络设备发送的心跳探测报文后,可以生成心跳探测响应报文,并向网络设备发送该心跳探测响应报文。心跳探测响应报文可以是ACK报文。日志服务器向网络设备返回ACK报文,表示日志服务器已成功接收request报文。
其中,心跳探测响应报文的数据帧结构与心跳探测报文的数据帧结构相同,心跳探测报文的报文类型标记和心跳探测响应报文的报文类型标记不同。例如,当图5中的type为0时,表示该报文为心跳探测报文,当图5中的type为1时,表示该报文为心跳探测响应报文。
需要说明的是,当网络设备与日志服务器之间的通信链路中断或日志服务器发生故障(硬件故障和/或应用级层软件故障)时,日志服务器无法接收到网络设备发送的心跳探测报文,则日志服务器不会向网络设备返回心跳探测响应报文,因此网络设备向日志服务器发送心跳探测报文后,可以通过检测第一指定时段内是否接收到日志服务器返回的心跳探测响应报文,以确定该日志服务器是否能够接收报文。
可选地,第一指定时段也可称为心跳超时等待时间,例如该第一指定时段可以为 1秒,当网络设备发送心跳探测报文后,1秒内未接收到日志服务器返回的心跳探测响应报文,则网络设备可以确定该日志服务器无法接收报文。
步骤403、网络设备确定日志服务器能够接收报文。
步骤404、网络设备向日志服务器发送日志报文。
需要说明的是,网络设备确定日志服务器能够接收报文后,向该日志服务器发送日志报文,可以提高日志报文传输和存储的可靠性。
步骤405、网络设备确定日志服务器无法接收报文。
可选地,网络设备确定日志服务器无法接收报文后,停止向该日志服务器发送日志报文,避免日志报文的丢失。
可选地,在本申请实施例中,在执行步骤405之后,可以返回上述步骤401,并重复执行上述数据传输方法的步骤。
综上所述,本申请实施例提供的数据传输方法,通过在网络设备与日志服务器之间建立心跳探测机制,网络设备周期性向日志服务器发送心跳探测报文,通过检测是否接收到日志服务器返回的心跳探测响应报文,以确定日志服务器是否能够接收报文,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,提高了日志报文传输和存储的可靠性。
在另一个示例中,探测报文包括ICMP探测报文和UDP探测报文,探测响应报文包括ICMP探测响应报文和UDP端口不可达报文。相应的,图6是本申请实施例提供的另一种数据传输方法的流程图,该方法可以应用于如图1至3任一所示的数据传输系统,如图6所示,该方法包括:
步骤601、网络设备向日志服务器发送ICMP探测报文。
可选地,网络设备周期性向日志服务器发送ICMP探测报文,ICMP探测报文可以是ping报文,相应的,ICMP探测响应报文可以是pong报文。
步骤602、网络设备检测在第二指定时段内是否接收到日志服务器返回的ICMP探测响应报文;当在第二指定时段内接收到日志服务器返回的ICMP探测响应报文时,执行步骤603;当在第二指定时段内未接收到日志服务器返回的ICMP探测响应报文时,执行步骤610。
需要说明的是,ICMP探测报文用于检测日志服务器的IP地址是否可达。当网络设备与日志服务器之间的通信链路中断,或者日志服务器发生硬件故障导致日志服务器的物理端口不可用时,日志服务器无法接收到ICMP探测报文,即日志服务器的IP地址不可达。
可选地,当日志服务器接收到网络设备发送的ICMP探测报文后,可以生成ICMP探测响应报文,并向网络设备返回该ICMP探测响应报文。
可选地,第二指定时段也可称为ICMP超时等待时间,例如该第二指定时段可以为1秒,网络设备发送ICMP探测报文后,若1秒内未接收到日志服务器返回的ICMP探测响应报文,则网络设备可以确定该日志服务器的IP地址不可达,进一步可以将该日志服务器标记为不可用状态;若1秒内接收到日志服务器返回的ICMP探测响应报文,则网络设备可以确定该日志服务器的IP地址可达,进一步可以将该日志服务器标 记为可用状态。
步骤603、网络设备向日志服务器发送UDP探测报文。
需要说明的是,UDP探测的工作原理是:当日志服务器的UDP端口发生故障或UDP端口未开启导致UDP端口不可用时,日志服务器接收到网络设备发送的UDP探测报文后会返回UDP端口不可达报文;当日志服务器的UDP端口可用时,日志服务器接收到网络设备发送的UDP探测报文后不做响应,即日志服务器不向网络设备返回探测响应报文。其中,UDP端口指日志服务器的日志服务端口,也可称为应用端口或软件端口,UDP探测报文用于检测日志服务器的软件应用层是否可用。
可选地,由于本申请实施例中,网络设备基于UDP向日志服务器发送日志报文,因此步骤603中网络设备向日志服务器发送的UDP探测报文可以是一个日志报文。可选地,UDP探测报文也可以是空报文,即报文净荷部分为空,此时该UDP探测报文仅起到UDP探测的作用,本申请实施例对此不做限定。
步骤604、网络设备检测在第三指定时段内是否接收到日志服务器返回的UDP端口不可达报文;当在第三指定时段内未接收到日志服务器返回的UDP端口不可达报文时,执行步骤605;当在第三指定时段内接收到日志服务器返回的UDP端口不可达报文时,执行步骤607。
可选地,第三指定时段也可称为UDP超时等待时间,例如该第三指定时段可以为1秒,当网络设备发送UDP探测报文后,1秒内接收到日志服务器返回的UDP端口不可达报文,则网络设备可以确定该日志服务器无法接收报文。
步骤605、网络设备确定日志服务器能够接收报文。
步骤606、网络设备向日志服务器发送日志报文。
需要说明的是,网络设备确定日志服务器能够接收报文后,向该日志服务器发送日志报文,可以提高日志报文传输和存储的可靠性。
步骤607、网络设备确定日志服务器无法接收报文。
可选地,当上述步骤603中网络设备向日志服务器发送的UDP探测报文为一个日志报文时,在网络设备确定日志服务器无法接收报文之后,网络设备停止向该日志服务器发送其他日志报文,以避免日志报文的丢失。
步骤608、网络设备向日志服务器周期性发送UDP探测报文。
需要说明的是,当日志服务器被标记为可用状态,即日志服务器的IP地址可达时,网络设备向日志服务器周期性发送UDP探测报文。
其中,步骤608中的UDP探测报文为空报文,该UDP探测报文仅用于探测日志服务器的UDP端口是否可用。
步骤609、当连续n个周期内未接收到日志服务器返回的UDP端口不可达报文,网络设备确定日志服务器能够接收报文,n为正整数。
示例的,当网络设备连续3个周期向日志服务器发送UDP探测报文后,均未接收到日志服务器返回的UDP端口不可达报文,则网络设备确定日志服务器能够接收报文。
可选地,网络设备确定日志服务器能够接收报文后,执行上述步骤606。
步骤610、网络设备更新累计次数。
其中,更新后的累计次数为从最近一次接收到日志服务器返回的ICMP探测响应 报文之后至当前时刻,网络设备向日志服务器发送ICMP探测报文的次数。
需要说明的是,每当网络设备接收到日志服务器返回的ICMP探测响应报文,上述累计次数清零;当网络设备向日志服务器发送ICMP探测报文后在第二指定时段内未接收到日志服务器返回的ICMP探测响应报文,将累计次数加1。
示例的,若上一个ICMP探测报文发送周期内,网络设备接收到日志服务器返回的ICMP探测响应报文,则步骤610中,网络设备更新后的累计次数为0;若当前时刻之前连续m个ICMP探测报文发送周期内,网络设备均未接收到日志服务器返回的ICMP探测响应报文,则步骤610中,网络设备更新后的累计次数为m+1,m≥1。
步骤611、当更新后的累计次数达到指定次数阈值时,网络设备确定日志服务器无法接收报文。
示例的,指定次数阈值可以为3,本申请实施例对设置的指定次数阈值不做限定。
可选地,当更新后的累计次数达到指定次数阈值时,网络设备可以确定日志服务器的IP地址不可达,进而确定该日志服务器无法接收报文。当更新后的累计次数未达到指定次数阈值时,可以重复执行上述步骤601至步骤611。
可选地,在本申请实施例中,在执行步骤611之后,可以返回上述步骤601,并重复执行上述数据传输方法的步骤。
综上所述,本申请实施例提供的数据传输方法,在网络设备与日志服务器之间建立ICMP探测机制和UDP探测机制,网络设备基于ICMP探测方式检测日志服务器的IP地址是否可达,并基于UDP探测方式检测日志服务器的UDP端口是否可用,进而确定日志服务器是否能够接收报文,在确定日志服务器能够接收报文后再向该日志服务器发送日志报文,提高了日志报文传输和存储的可靠性。
需要说明的是,上述两种数据传输方法中,基于心跳探测的数据传输方法,网络设备与日志服务器之间建立有心跳探测机制,网络设备仅需向日志服务器发送心跳探测报文即可探测日志服务器是否能够接收报文,与基于ICMP探测和UDP探测结合的数据传输方法相比,该数据传输方法中用于探测的报文所占用的传输资源较少;基于ICMP探测和UDP探测结合的数据传输方法,网络设备与日志服务器之间无需建立新的通信机制,其通用性较高,对于运营商场景,与CGN设备对接的第三方服务器厂商的种类和数量较多,其可实现性更高。
可选地,在本申请实施例中,还可以结合心跳探测、ICMP探测和UDP探测以检测日志服务器是否能够接收报文,以进一步提高日志存储的可靠性;或者,还可以基于其他探测机制检测日志服务器是否能够接收报文,本申请实施例对所采用的探测机制不做限定。
需要说明的是,本申请实施例提供的数据传输方法的步骤先后顺序可以进行适当调整,步骤也可以根据情况进行相应增减。任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化的方法,都应涵盖在本申请的保护范围之内,因此不再赘述。
图7是本申请实施例提供的一种数据传输装置的结构示意图,应用于网络设备,可以实现图4或图6所示的实施例中的网络设备的功能。如图7所示,该数据传输装 置700包括:发送单元701、检测单元702、确定单元703和处理单元704。这些单元可以执行上述方法实施例中网络设备的相应功能。发送单元701,用于支持网络设备执行图4中的步骤401和步骤404,和/或,图6中的步骤601、步骤603、步骤606和步骤608;检测单元702用于支持网络设备执行图4中的步骤402,和/或,图6中的步骤602和步骤604;确定单元703,用于支持网络设备执行图4中的步骤403和步骤405,和/或,图6中的步骤605、步骤607、步骤609和步骤611;处理单元704,用于支持网络设备执行图6中的步骤610,和/或本文所描述的技术中网络设备执行的其它过程。示例的,发送单元701,用于执行上述方法实施例中网络设备执行的各种信息发送;检测单元702,用于执行上述方法实施例中网络设备执行的检测动作;确定单元703,用于执行上述方法实施例中网络设备执行的确定动作;处理单元704,用于执行上述方法实施例中网络设备执行的除信息发送、检测动作和确定动作之外的其他处理。举例来说,发送单元701,用于向日志服务器发送探测报文;检测单元702,用于基于是否接收到日志服务器返回的探测响应报文,检测日志服务器是否能够接收报文;发送单元701还用于当确定日志服务器能够接收报文,向日志服务器发送日志报文。具体执行过程请参考上述图4或图6所示实施例中对相应步骤的详细描述,本申请实施例在此不做一一赘述。
在采用集成的单元的情况下,图8示出了上述实施例中所涉及的数据传输装置的另一种可能的结构示意图,该数据传输装置800同样可以实现图4或图6所示的实施例中的网络设备的功能。数据传输装置800包括:存储单元801、处理单元802和通信单元803。通信单元803用于支持网络设备与其他网络实体的通信,例如与图4或图6中示出的日志服务器之间的通信,举例来说,通信单元803用于支持网络设备执行图4中的步骤401和步骤404,和/或,图6中的步骤601、步骤603、步骤606和步骤608。处理单元802用于对网络设备的动作进行控制管理,例如,处理单元802用于支持网络设备执行图4中的步骤402、步骤403和步骤405,图6中的步骤602、步骤604、步骤605、步骤607、步骤609、步骤610和步骤611,和/或本文所描述的技术中网络设备执行的其它过程。存储单元801,用于存储网络设备的程序代码和数据。具体执行过程请参考上述图4或图6所示实施例中对相应步骤的详细描述,本申请实施例在此不做一一赘述。
其中,处理单元802可以是处理器,例如可以是中央处理器(central processing unit,CPU)、通用处理器,数字信号处理器(digital signal processor,DSP)、专用集成电路(application-specific integrated circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信单元803可以是收发器,存储单元801可以是存储器。
当处理单元802为处理器,通信单元803为收发器,存储单元801为存储器时,本申请实施例所涉及的网络设备的结构可以如图9所示。
参见图9,网络设备900包括:处理器902、收发器903、存储器901以及总线904。 其中,处理器902、收发器903以及存储器901通过总线904相互连接;总线904可以是外设部件互连标准(peripheral component interconnect,PCI)总线或扩展工业标准结构(extended industry standard architecture,EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图9中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。该网络设备900可以实现图4或图6所示的实施例中的网络设备的功能。处理器902和收发器903可以执行上述方法示例中网络设备的相应功能。收发器903用于支持网络设备900执行图4中的步骤401和步骤404,和/或,图6中的步骤601、步骤603、步骤606和步骤608。处理器902用于支持网络设备900执行图4中的步骤402、步骤403和步骤405,图6中的步骤602、步骤604、步骤605、步骤607、步骤609、步骤610和步骤611,和/或本文所描述的技术中网络设备执行的其它过程。存储器901,用于存储网络设备900的程序代码和数据。具体执行过程请参考上述图4或图6所示实施例中对相应步骤的详细描述,本申请实施例在此不做一一赘述。
图10是本申请实施例提供的另一种网络设备1000的结构示意图。网络设备1000可以为路由器或交换器等具有网络地址转换功能且能够转发数据的网络设备,网络设备1000能够实现前述方法实施例中的网络设备的功能。所述网络设备1000包括:主控板1001和接口板1002。主控板1001包括:处理器1003和存储器1004。接口板1002包括:处理器1005、存储器1006和接口卡1007。主控板1001和接口板1002耦合。
这些硬件可以执行上述方法示例中的相应功能,例如,存储器1006可以用于存储接口板1002的程序代码,处理器1005用于调用存储器1006中的程序代码触发接口卡1007执行上述方法实施例中网络设备执行的各种信息接收和发送,例如,处理器1005调用存储器1006中的程序代码触发接口卡1007支持网络设备1000执行图4中的步骤401和步骤404,和/或,图6中的步骤601、步骤603、步骤606和步骤608。处理器1005,还用于将业务标识向主控板1001发送。存储器1004可以用于存储主控板1001的程序代码,处理器1003用于调用存储器1004中的程序代码执行上述方法实施例中网络设备除了信息收发之外的其他处理。例如,处理器1003用于支持网络设备1000执行图4中的步骤402、步骤403和步骤405,图6中的步骤602、步骤604、步骤605、步骤607、步骤609、步骤610和步骤611,和/或本文所描述的技术中网络设备执行的其它过程。存储器1004用于存储主控板1001的程序代码和数据。具体执行过程请参考上述图4或图6所示实施例中对相应步骤的详细描述,本申请实施例在此不做一一赘述。
在一种可能的实现方式中,主控板1001和接口板1002之间建立IPC控制通道,主控板1001和接口板1002之间利用该IPC控制通道进行通信。
本申请实施例提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有指令,当所述指令被处理器执行时,实现如方法侧实施例任一所述的数据传输方法。
需要说明的是,以上描述的任意装置实施例都仅仅是示意性的,其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外, 本申请提供的网络设备实施例附图中,模块之间的连接关系表示它们之间具有通信连接,具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。
本申请实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于随机存取存储器(random access memory,RAM)、闪存、只读存储器(read only memory,ROM)、可擦除可编程只读存储器(erasable programmable ROM,EPROM)、电可擦可编程只读存储器(electrically EPROM,EEPROM)、硬盘、移动硬盘、光盘或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于核心网接口设备中。当然,处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本申请的可选实施例,并不用以限制本申请,凡在本申请的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本申请的保护范围之内。

Claims (13)

  1. 一种数据传输方法,其特征在于,所述方法应用于网络设备,所述方法包括:
    向日志服务器发送探测报文;
    基于是否接收到所述日志服务器返回的探测响应报文,检测所述日志服务器是否能够接收报文;
    当确定所述日志服务器能够接收报文时,向所述日志服务器发送日志报文,所述日志报文包含公网互联网协议IP地址和私网IP地址之间的对应关系。
  2. 根据权利要求1所述的方法,其特征在于,所述探测报文为心跳探测报文,所述探测响应报文为心跳探测响应报文,所述基于是否接收到所述日志服务器返回的探测响应报文,检测所述日志服务器是否能够接收报文,包括:
    检测在第一指定时段内是否接收到所述日志服务器返回的心跳探测响应报文;
    当在所述第一指定时段内接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器能够接收报文;
    当在所述第一指定时段内未接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器无法接收报文。
  3. 根据权利要求1所述的方法,其特征在于,所述探测报文包括因特网控制报文协议ICMP探测报文和用户数据报协议UDP探测报文,所述探测响应报文包括ICMP探测响应报文和UDP端口不可达报文,所述基于是否接收到所述日志服务器返回的探测响应报文,检测所述日志服务器是否能够接收报文,包括:
    检测在第二指定时段内是否接收到所述日志服务器返回的ICMP探测响应报文;
    当在所述第二指定时段内接收到所述日志服务器返回的ICMP探测响应报文时,向所述日志服务器发送所述UDP探测报文;
    当在第三指定时段内接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器无法接收报文;
    当在所述第三指定时段内未接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器能够接收报文。
  4. 根据权利要求3所述的方法,其特征在于,在所述检测第二指定时段内是否接收到所述日志服务器返回的ICMP探测响应报文之后,所述方法还包括:
    当在所述第二指定时段内未接收到所述日志服务器返回的ICMP探测响应报文,更新累计次数,更新后的累计次数为从最近一次接收到所述日志服务器返回的ICMP探测响应报文之后至当前时刻,所述网络设备向所述日志服务器发送ICMP探测报文的次数;
    当所述更新后的累计次数达到指定次数阈值时,确定所述日志服务器无法接收报文。
  5. 根据权利要求3所述的方法,其特征在于,在所述确定所述日志服务器无法接 收报文之后,所述方法还包括:
    周期性向所述日志服务器发送UDP探测报文;
    当连续n个周期内未接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器能够接收报文,其中n为正整数。
  6. 一种数据传输装置,其特征在于,所述装置应用于网络设备,所述装置包括:
    发送单元,用于向日志服务器发送探测报文;
    检测单元,用于基于是否接收到所述日志服务器返回的探测响应报文,检测所述日志服务器是否能够接收报文;
    所述发送单元,还用于当确定所述日志服务器能够接收报文时,向所述日志服务器发送日志报文,所述日志报文包含公网互联网协议IP地址和私网IP地址之间的对应关系。
  7. 根据权利要求6所述的装置,其特征在于,所述探测报文为心跳探测报文,所述探测响应报文为心跳探测响应报文,所述装置还包括:确定单元;
    所述检测单元,用于检测在第一指定时段内是否接收到所述日志服务器返回的心跳探测响应报文;
    所述确定单元,用于当在所述第一指定时段内接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器能够接收报文;
    所述确定单元,还用于当在所述第一指定时段内未接收到所述日志服务器返回的心跳探测响应报文时,确定所述日志服务器无法接收报文。
  8. 根据权利要求6所述的装置,其特征在于,所述探测报文包括因特网控制报文协议ICMP探测报文和用户数据报协议UDP探测报文,所述装置还包括:确定单元;
    所述检测单元,用于检测在第二指定时段内是否接收到所述日志服务器返回的ICMP探测响应报文;
    所述发送单元,用于当在所述第二指定时段内接收到所述日志服务器返回的ICMP探测响应报文时,向所述日志服务器发送所述UDP探测报文;
    所述确定单元,用于当在第三指定时段内接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器无法接收报文;
    所述确定单元,还用于当在所述第三指定时段内未接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器能够接收报文。
  9. 根据权利要求8所述的装置,其特征在于,所述装置还包括:处理单元;
    所述处理单元,用于当在所述第二指定时段内未接收到所述日志服务器返回的ICMP探测响应报文,更新累计次数,更新后的累计次数为从最近一次接收到所述日志服务器返回的ICMP探测响应报文之后至当前时刻,所述网络设备向所述日志服务器发送ICMP探测报文的次数;
    所述确定单元,还用于当所述更新后的累计次数达到指定次数阈值时,确定所述 日志服务器无法接收报文。
  10. 根据权利要求8所述的装置,其特征在于,
    所述发送单元,还用于在确定所述日志服务器无法接收报文之后,周期性向所述日志服务器发送UDP探测报文;
    所述检测单元,用于当连续n个周期内未接收到所述日志服务器返回的UDP端口不可达报文时,确定所述日志服务器能够接收报文,其中n为正整数。
  11. 一种数据传输装置,其特征在于,包括:处理器和存储器;
    所述存储器,用于存储计算机程序,所述计算机程序包括程序指令;
    所述处理器,用于调用所述程序指令,实现如权利要求1至5任一所述的数据传输方法。
  12. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有指令,当所述指令被处理器执行时,实现如权利要求1至5任一所述的数据传输方法。
  13. 一种数据传输系统,其特征在于,所述系统包括:网络设备和至少一个日志服务器,所述网络设备包括如权利要求6至10任一所述的数据传输装置。
PCT/CN2019/120451 2018-11-29 2019-11-23 数据传输方法、装置及系统 WO2020108418A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19888578.2A EP3869741B1 (en) 2018-11-29 2019-11-23 Data transmission method and apparatus and system
US17/327,019 US11444913B2 (en) 2018-11-29 2021-05-21 Data transmission method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811440792.9A CN111245666B (zh) 2018-11-29 2018-11-29 数据传输方法、装置及系统
CN201811440792.9 2018-11-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/327,019 Continuation US11444913B2 (en) 2018-11-29 2021-05-21 Data transmission method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2020108418A1 true WO2020108418A1 (zh) 2020-06-04

Family

ID=70853802

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/120451 WO2020108418A1 (zh) 2018-11-29 2019-11-23 数据传输方法、装置及系统

Country Status (4)

Country Link
US (1) US11444913B2 (zh)
EP (1) EP3869741B1 (zh)
CN (1) CN111245666B (zh)
WO (1) WO2020108418A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396529A (zh) * 2022-08-25 2022-11-25 深圳市元征科技股份有限公司 多通道通信方法、装置、终端设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112230623B (zh) * 2020-10-15 2022-09-06 京东科技信息技术有限公司 故障监控方法和装置、机器人功能装置和巡检机器人
CN113207144A (zh) * 2021-05-06 2021-08-03 北京字跳网络技术有限公司 投屏设备无线网络探测方法、装置、介质和投屏设备
CN114500632A (zh) * 2022-01-24 2022-05-13 重庆奥普泰通信技术有限公司 一种通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103532752A (zh) * 2013-10-10 2014-01-22 北京首信科技股份有限公司 移动互联网络用户上网日志实现融合的管理装置和方法
CN103532943A (zh) * 2013-10-08 2014-01-22 北京神州绿盟信息安全科技股份有限公司 web应用防火墙设备和安全防护日志的异步处理方法
WO2018004600A1 (en) * 2016-06-30 2018-01-04 Sophos Limited Proactive network security using a health heartbeat

Family Cites Families (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5959974A (en) * 1996-12-02 1999-09-28 International Business Machines Corporation System and method for discovering path MTU of internet paths
US6662223B1 (en) * 1999-07-01 2003-12-09 Cisco Technology, Inc. Protocol to coordinate network end points to measure network latency
US6952421B1 (en) * 1999-10-07 2005-10-04 Cisco Technology, Inc. Switched Ethernet path detection
US6826172B1 (en) * 2000-06-09 2004-11-30 Steven Augart Network probing using overlapping probe packets
US7200673B1 (en) * 2000-06-09 2007-04-03 Steven Augart Determining the geographic location of a network device
KR20020034280A (ko) * 2000-10-31 2002-05-09 정규석 Pc환경에서 효율적인 nat 테이블 관리 및 검색을위한 nat 테이블 구조 및 방법
US8473620B2 (en) * 2003-04-14 2013-06-25 Riverbed Technology, Inc. Interception of a cloud-based communication connection
US7463590B2 (en) * 2003-07-25 2008-12-09 Reflex Security, Inc. System and method for threat detection and response
US8938553B2 (en) * 2003-08-12 2015-01-20 Riverbed Technology, Inc. Cooperative proxy auto-discovery and connection interception through network address translation
US20080181215A1 (en) * 2007-01-26 2008-07-31 Brooks Bollich System for remotely distinguishing an operating system
US7852774B2 (en) * 2007-11-28 2010-12-14 Cisco Technology, Inc. User datagram protocol traceroute probe extension
CN101808043B (zh) * 2010-03-12 2012-09-05 成都市华为赛门铁克科技有限公司 端口汇聚trunk成员业务报文转发状态的检测方法及装置
CN102177681B (zh) * 2011-04-21 2013-04-24 华为技术有限公司 检测故障的方法和系统
CN102843373A (zh) * 2012-08-28 2012-12-26 北京星网锐捷网络技术有限公司 一种获知udp服务不可达的方法、装置及网络设备
CN103036961A (zh) * 2012-12-07 2013-04-10 蓝盾信息安全技术股份有限公司 一种日志分布式收集及存储方法
US9313116B2 (en) * 2013-02-13 2016-04-12 ViaviSolutions Inc. Enhanced retry method
US9680948B2 (en) * 2013-03-14 2017-06-13 Arista Networks, Inc. System and method for device failure notification
CN105100137B (zh) * 2014-04-26 2019-05-24 华为终端有限公司 一种服务发现的方法及电子设备
US10110668B1 (en) * 2015-03-31 2018-10-23 Cisco Technology, Inc. System and method for monitoring service nodes
CN106301832B (zh) * 2015-05-21 2020-04-03 中兴通讯股份有限公司 一种处理系统日志报文的方法和装置
US9841965B2 (en) * 2015-06-15 2017-12-12 Lear Corporation Centralized system for software updating vehicle components
US10171361B1 (en) * 2015-09-10 2019-01-01 Cisco Technology, Inc. Service-specific probes in a native load balancer
CN105939327A (zh) * 2016-01-19 2016-09-14 杭州迪普科技有限公司 审计日志的生成方法及装置
CN107196777A (zh) * 2016-03-14 2017-09-22 阿里巴巴集团控股有限公司 一种应用处理的方法和装置
CN106027326B (zh) * 2016-05-10 2019-06-07 杭州迪普科技股份有限公司 链路健康探测方法及装置
CN106101264B (zh) * 2016-07-20 2019-05-24 腾讯科技(深圳)有限公司 内容分发网络日志推送方法、装置和系统
US20190190774A1 (en) * 2017-03-16 2019-06-20 Krishnamurty Kambhampati Network connectivity monitor
EP4020940A1 (en) * 2017-08-28 2022-06-29 Bright Data Ltd. Content fetching by selecting tunnel devices
US10498622B2 (en) * 2017-09-08 2019-12-03 Vmware, Inc. Tunnel state detection for overlay networks
CN108737170A (zh) * 2018-05-09 2018-11-02 中国银行股份有限公司 一种批量日志异常数据告警方法及装置
CN109039825B (zh) * 2018-08-30 2021-12-21 湖北微源卓越科技有限公司 一种网络数据保护设备及方法
US10834044B2 (en) * 2018-09-19 2020-11-10 Amazon Technologies, Inc. Domain name system operations implemented using scalable virtual traffic hub
US10708144B2 (en) * 2018-11-14 2020-07-07 Juniper Networks, Inc. Predicting application quality of experience metrics using adaptive machine learned probes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103532943A (zh) * 2013-10-08 2014-01-22 北京神州绿盟信息安全科技股份有限公司 web应用防火墙设备和安全防护日志的异步处理方法
CN103532752A (zh) * 2013-10-10 2014-01-22 北京首信科技股份有限公司 移动互联网络用户上网日志实现融合的管理装置和方法
WO2018004600A1 (en) * 2016-06-30 2018-01-04 Sophos Limited Proactive network security using a health heartbeat

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3869741A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396529A (zh) * 2022-08-25 2022-11-25 深圳市元征科技股份有限公司 多通道通信方法、装置、终端设备及存储介质

Also Published As

Publication number Publication date
CN111245666A (zh) 2020-06-05
EP3869741B1 (en) 2023-07-26
EP3869741A1 (en) 2021-08-25
CN111245666B (zh) 2022-12-06
EP3869741A4 (en) 2021-12-29
US20210281541A1 (en) 2021-09-09
US11444913B2 (en) 2022-09-13

Similar Documents

Publication Publication Date Title
WO2020108418A1 (zh) 数据传输方法、装置及系统
US9560126B2 (en) Stateless load balancing of connections
US7839848B2 (en) Method, device and system for message transmission
US7515549B2 (en) Managing devices across NAT boundaries
US7388829B2 (en) Method and apparatus for detecting and recovering from faults associated with transport protocol connections across network address translators
US20140330977A1 (en) Stateless recognition of keep-alive packets
US8583831B2 (en) Thin client discovery
US11419171B2 (en) Method for establishing subflow of multipath connection, apparatus, and system
US20140280792A1 (en) System and method for device failure notification
US20150271086A1 (en) Reducing Network Traffic By Intercepting Address Resolution Messages
CN108667957B (zh) Ip地址分配方法、第一电子设备以及第一服务器
CN110418375B (zh) 自动确定网络设备的网状网角色
US20100238930A1 (en) Router and method of forwarding ipv6 packets
US20080056263A1 (en) Efficient transport layer processing of incoming packets
US10063675B2 (en) Performing duplicate address detection for an integrated routing and bridging device
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco AppleTalk Routing Commands
Cisco AppleTalk Commands

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19888578

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019888578

Country of ref document: EP

Effective date: 20210519

NENP Non-entry into the national phase

Ref country code: DE