WO2014019389A1

WO2014019389A1 - Data transmission method and network side device

Info

Publication number: WO2014019389A1
Application number: PCT/CN2013/075054
Authority: WO
Inventors: 席辉; 伍锐恒
Original assignee: 华为技术有限公司
Priority date: 2012-07-31
Filing date: 2013-05-02
Publication date: 2014-02-06
Also published as: CN102821413A

Abstract

Embodiments of the invention provide a data transmission method and a network side device. The data transmission method comprises: determining whether a CAPWAP data channel has data transmission or not; and in a case where the CAPWAP data channel has the data transmission, stopping sending of a keep-alive message. In the embodiments of the present invention, because the keep-alive message is not sent in the data transmission process, CAPWAP link breaking caused by keep-alive message loss can be prevented, thereby improving the reliability of a CAPWAP link.

Description

Method for transmitting data and network side device This application claims to be submitted to the Chinese Patent Office on July 31, 2012, and the application number is

201210268377. 6 , the title of the invention is the priority of the Chinese patent application of the "Method of transmitting data and the network side device", the entire contents of which are incorporated herein by reference.

Technical field

Embodiments of the present invention relate to the field of communication technologies, and, more particularly, to a method of transmitting data and a network side device. Background technique

Control and Provisioning of Wireless Access Points (CAPWAP) is a standard protocol for managing Access Controllers (ACs) and Wireless Termination Points (WTP). . CAPWAP includes data tunneling. The AC and WTP periodically detect the status of the data tunnel through keep-alive packets. If the keepalive packet of the data tunnel is lost during the data transmission, the CAPWAP is broken, which affects the WTP service. Summary of the invention

The present invention proposes a method for transmitting data and a network side device, which can improve the reliability of the CAPWAP link.

In one aspect, the present invention provides a method of transmitting data, including:

Determine whether the wireless access point controls and configures whether the CAPWAP data tunnel has data transmission. If the CAPWAP data tunnel has data transmission, stop sending keep-alive packets.

It determines whether the CAPWAP data tunnel has data transmission, including:

In the case that the data packet is sent through the CAPWAP data tunnel, it is determined that the CAPWAP data tunnel has data transmission;

In the case that the data packet is received through the CAPWAP data tunnel, it is determined that the CAPWAP data tunnel has data transmission; or

In the case that a data message response is received through the CAPWAP data tunnel, the The CAPWAP data tunnel has data transmission.

Optionally, if no data transmission occurs in the CAPWAP data tunnel within a preset time, the keep-alive message is resumed.

The method is performed by the access controller AC and the wireless terminal point WTP.

In another aspect, the present invention provides a network side device, including:

a sending module, configured to send a keep-alive message;

a determining module, configured to determine whether the wireless access point controls and configures whether the CAPWAP data tunnel has data transmission;

And a control module, configured to control the sending module to stop sending the keep-alive message if the determining module determines that the CAPWAP data tunnel has data transmission.

Optionally, the sending module is further configured to send a data packet by using the CAPWAP data tunnel. In the case that the sending module sends the data packet through the CAPWAP data tunnel, the determining module determines that the CAPWAP data tunnel has data transmission. Optionally, the device further includes: a timing module, configured to start timing when the sending module sends the data packet through the CAPWAP data tunnel; and the control module is further configured to preset the timing of the timing module If the sending module does not send the data packet through the CAPWAP data tunnel again in the preset time, the sending module is controlled to resume sending the keep-alive message.

Optionally, the device further includes: a receiving module, configured to receive a data packet by using a CAPWAP data tunnel; and when the receiving module receives the data packet by using the CAPWAP data tunnel, the determining module determines that the CAPWAP data tunnel has data transmission. Optionally, the device further includes: a timing module, configured to start timing when the receiving module receives the data packet through the CAPWAP data tunnel; and the control module is further configured to achieve timing in the timing module If the receiving module does not receive the data packet through the CAPWAP data tunnel in the preset time, the sending module is controlled to resume sending the keep-alive message.

Optionally, the device further includes: a receiving module, configured to receive a data packet response by using a CAPWAP data tunnel; and determining, by the receiving module, the CAPWAP data, when the receiving module receives the data packet response through the CAPWAP data tunnel The tunnel has data transmission. Optionally, the device further includes: a timing module, configured to start timing when the receiving module receives the data message response through the CAPWAP data tunnel; and the control module is further configured to meet the timing of the timing module Controlling the sending module to resume sending the keep-alive report if the receiving module does not receive the data packet response through the CAPWAP data tunnel within the preset time. Text.

The device is a wireless terminal point WTP or an access controller AC.

In the embodiment of the present invention, the keep-alive packet is not sent in the data transmission process, which can prevent the CAPWAP disconnection caused by the loss of the keep-alive packet and improve the reliability of the CAPWAP link. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

FIG. 1 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention.

FIG. 2 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention.

FIG. 4 is a schematic block diagram of a network side device according to an embodiment of the present invention.

FIG. 5 is a schematic block diagram of a network side device according to another embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work shall fall within the scope of the present invention.

WTP can be an access point (AP), which is responsible for simple functions such as encryption and decryption of packets and statistics of radio slots. The AC is responsible for managing one or more WTPs.

FIG. 1 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention. The method of Figure 1 can be performed by a network side device, such as by a WTP or AC.

101. Determine whether the CAPWAP data tunnel has data transmission.

102. Stop sending the keep-alive message when the CAPWAP data tunnel has data transmission. In the embodiment of the present invention, the keep-alive packet is not sent in the data transmission process, which can prevent the CAPWAP disconnection caused by the loss of the keep-alive packet and improve the reliability of the CAPWAP link.

Optionally, as an embodiment, the method shown in FIG. 1 may be used in a case where a first network side device sends a data message to a second network side device. For example, in step 101, the first network side is set. The device can determine that the CAPWAP data tunnel has data transmission when the data packet is sent to the second network side device through the CAPWAP data tunnel. Alternatively, the second network side device may determine that the CAPWAP data tunnel has data transmission if the data packet is received through the CAPWAP data tunnel. Alternatively, the first network side device may determine that the CAPWAP data tunnel has data transmission if the data message response is received through the CAPWAP data tunnel. Generally, after the first network side device sends the data packet to the second network side device, the second network side device sends a data packet response to the first network side device, to confirm that the second network side device receives the data. Message.

It should be noted that in the specification of the present application, the terms "first" and "second" are merely used to distinguish different objects from each other, and are not limited to the modified objects. For example, the function or operation of the objects modified by the "first" and "second" may be interchanged, and such modifications are still within the scope of the embodiments of the present invention.

Optionally, in another embodiment, if there is no data transmission in the CAPWAP data tunnel within the preset time, the keep-alive message may be resumed. For example, the keep-alive message can be sent in the existing manner. In this way, the state of the data tunnel can be detected by the keep-alive message. For example, the first network side device may resume sending the keep-alive message to the second network side device if it is determined that the CAPWAP data tunnel has no data transmission. Alternatively, the second network side device may send a keep-alive message to the first network side device if it is determined that the CAPWAP data tunnel has no data transmission. In the above case, the first network side device and the second network side device determine CAPWAP data tunneling. The foregoing process may also be initiated by the second network side device, and the process is similar to the foregoing process, and details are not described herein.

Optionally, as an embodiment, the first network side device may be WTP or AC; and the second network side device may be AC or WTP. For example, in a case where the first network side device is a WTP, the second network side device is an AC; and in a case where the first network side device is an AC, the second network side device is a WTP.

FIG. 2 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention. The method is a specific embodiment of the method shown in FIG. 1. The second network side device stops transmitting the keep-alive message when receiving the data packet sent by the first network side device.

201. Receive a data packet from the first network side device by using a CAPWAP data tunnel.

202. Stop sending the keep-alive message to the first network side device.

203. If the data packet is received from the first network side device by using the CAPWAP data tunnel, the keepalive message is sent to the first network side device.

Optionally, as an embodiment, the second network side device receives the information from the first network side device. In the case of the data packet, the data packet response is sent to the first network side device, and is used to confirm that the second network side device receives the data packet.

Optionally, as another embodiment, the first network side device may be WTP or AC; and the second network side device may be AC or WTP. In the case where the first network side device is WTP, the second network side device is AC; in the case where the first network side device is AC, the second network side device is WTP.

In the embodiment of the present invention, the keep-alive packet is not sent in the data transmission process, which can prevent the CAPWAP disconnection caused by the loss of the keep-alive packet and improve the reliability of the CAPWAP link. In addition, if the data message is not received again within a certain period of time, the keepalive message is continuously sent, and the state of the data tunnel can be detected through the keep-alive message.

The method of FIG. 2 can be similarly applied to other situations, for example, when the second network side device stops transmitting the keep-alive message when receiving the data message response, and the second network side device stops sending the data when sending the data message. The situation of live messages. For the sake of brevity, we will not repeat them.

301. The first network side device sends a data packet to the second network side device by using the CAPWAP data tunnel.

In the case that the first network side device sends a data packet through the CAPWAP data tunnel, the first network side device may determine that the CAPWAP data tunnel has data transmission. In this case, the first network side device may stop sending the keep-alive message to the second network side device.

302. The second network side device sends a data packet response to the first network side device, where the second network side device receives the data packet from the first network side device, and is configured to confirm that the second network side device receives the data packet. Data message.

When the second network side device receives the data packet sent by the first network side device through the CAPWAP data tunnel, it may also determine that the CAPWAP data tunnel has data transmission. In this case, the second network side device may also stop sending the keep-alive message to the first network side device.

On the other hand, in a case where the first network side device receives the data packet response from the second network side device through the CAPWAP data tunnel, the first network side device may determine that the CAPWAP data tunnel has data transmission. At this time, the first network side device may stop sending the keep-alive message to the second network side device.

303. When the second network side device receives the data packet from the first network side device, the second network side device starts timing. For example, timing is performed by a timing module provided on the second network side device. When the second network side device receives the data message from the first network side device again within the preset time, the timing module of the second network side device restarts timing. When the first network side device receives the data packet, the second network side device resumes sending the keep-alive message to the first network side device.

305. If the first network side device receives the keep-alive message from the second network side device, send a keep-alive message to the second network side device, to confirm that the data tunnel of the CAPWAP is not broken.

In this embodiment, the first network side device may be WTP or AC; and the second network side device may be AC or WTP. For example, in a case where the first network side device is a WTP, the second network side device is an AC; and in a case where the first network side device is an AC, the second network side device is a WTP.

The method shown in FIG. 3 is a case where the first network side device sends a data message to the second network side device. The second network side device may also send a data packet to the first network side device. The method of setting the second network side is similar to the method shown in FIG. 3, and need not be described here.

According to the method shown in FIG. 3, in the data transmission process, the CAPWAP broken link caused by the loss of the data tunnel keep-alive packet can be prevented, and the reliability of the CAPWAP link is improved.

FIG. 4 is a schematic block diagram of a network side device according to an embodiment of the present invention. The network side device 400 of FIG. 4 includes a transmitting module 401, a determining module 402, and a control module 403.

The sending module 401 sends a keep-alive message. The determination module 402 determines if the CAPWAP data tunnel has data transmission. The control module 403, when the determining module 402 determines that the CAPWAP data tunnel has data transmission, controls the transmitting module 401 to stop transmitting the keep-alive message.

In the embodiment of the present invention, the keep-alive packet is not sent in the data transmission process, which can prevent the CAPWAP disconnection caused by the loss of the keep-alive packet and improve the reliability of the CAPWAP link.

The network side device 400 of FIG. 4 may be WTP or AC, and may perform various steps of the method shown in FIG. 1 to FIG. 3, and will not be described in detail in order to avoid redundancy.

FIG. 5 is a schematic block diagram of a network side device according to another embodiment of the present invention. The network side device 500 of Fig. 5 is one embodiment of the network side device 400. For example, the network side device 500 may be the first network side device and the second network side device in FIG. The network side device 500 includes: a sending module 501, a determining module 502, a control module 503, a receiving module 504, and a timing module 505.

The sending module 501 can send a keep-alive message. The determining module 502 determines the CAPWAP data tunnel Whether the channel has data transmission. The control module 503 stops the transmission of the keep-alive message if the determining module 502 determines that the CAPWAP data tunnel has data transmission.

Optionally, as an embodiment, the sending module 501 can also send a data packet by using a CAPWAP data tunnel. In the case that the transmitting module 501 transmits a data message through the CAPWAP data tunnel, the determining module 502 determines that the CAPWAP data tunnel has data transmission. At this time, the control module 503 controls the transmitting module 501 to stop transmitting the keep-alive message.

In this case, the network side device 500 may further include a timing module 505 for starting timing when the transmitting module 501 transmits a data message through the CAPWAP data tunnel. The control module 503, when the timing of the timing module 505 reaches the preset time and the transmitting module 501 does not send the data packet through the CAPWAP data tunnel, the control sending module 501 resumes transmitting the keep-alive message. In this way, the state of the data tunnel can be detected through the keep-alive message.

Optionally, as another embodiment, the network side device 500 may further include a receiving module 504, configured to receive a data message by using a CAPWAP data tunnel. In the event that the receiving module 504 receives the data message through the CAPWAP data tunnel, the determining module 502 determines that the CAPWAP data tunnel has data transmission. At this time, the control module 503 controls the transmitting module 501 to stop transmitting the keep-alive message.

In this case, the network side device 500 may further include a timing module 505 for starting timing when the receiving module receives the data message through the CAPWAP data tunnel. The control module may resume transmitting the keep-alive message if the timing of the timer module 505 reaches the preset time and the receiving module 504 does not receive the data packet through the CAPWAP data tunnel within the preset time. In this way, the state of the data tunnel can be detected through the keep-alive message.

Optionally, as another embodiment, the receiving module 504 can receive a data packet response by using a CAPWAP data tunnel. In the event that the receiving module 504 receives the data message response through the CAPWAP data tunnel, the determining module 502 determines that the CAPWAP data tunnel has data transmission. At this time, the control module 503 controls the transmitting module 501 to stop transmitting the keep-alive message.

In this case, the network side device 500 may further include a timing module 505 for starting timing when the receiving module receives the data message response through the CAPWAP data tunnel. The control module 503 can control the sending module 501 to resume sending the keep-alive message if the timing of the timing module reaches the preset time and the receiving module 504 does not receive the data message response through the CAPWAP data tunnel within the preset time. In this way, the state of the data tunnel can be detected through the keep-alive message.

In the embodiment of the present invention, the keep-alive packet is not sent in the data transmission process, which can prevent the CAPWAP disconnection caused by the loss of the keep-alive packet, and improve the reliability of the CAPWAP link. The network side device 500 of FIG. 5 may be WTP or AC, and various steps of the method shown in FIG. 1 to FIG. 3 may be performed. To avoid repetition, details are not described in detail.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in a combination of electronic hardware or computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that the specific working process of the system, the device and the unit described above can be referred to the corresponding process in the foregoing method embodiments for the convenience and brevity of the description, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise. The components displayed for the unit may or may not be physical units, ie may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), A random access memory (RAM, Random Access Memory), a disk or an optical disk, and other media that can store program codes.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any change or replacement that can be easily conceived by those skilled in the art within the technical scope of the present invention is All modifications are intended to be included within the scope of the invention, and the scope of the invention should be determined by the scope of the appended claims.

Claims

claims

1. A method of transmitting data, characterized by including:

Determine whether the wireless access point control and configuration CAPWAP data tunnel has data transmission; if the CAPWAP data tunnel has data transmission, stop sending keep-alive messages.

2. The method of claim 1, wherein determining whether there is data transmission in the CAPWAP data tunnel includes:

In the case of sending data packets through the CAPWAP data tunnel, it is determined that the CAPWAP data tunnel has data transmission;

In the case of receiving a data message through the CAPWAP data tunnel, determine the

There is data transmission in the CAPWAP data tunnel; or

When a data message response is received through the CAPWAP data tunnel, it is determined that the CAPWAP data tunnel has data transmission.

3. The method of claim 1 or 2, wherein the method further includes: resuming sending keep-alive messages when there is no data transmission in the CAPWAP data tunnel within a preset time.

4. The method according to any one of claims 1-3, characterized in that the method is executed by the access controller AC and the wireless terminal point WTP.

5. A network side device, characterized by including:

Sending module, used to send keep-alive messages;

Determination module, used to determine whether there is data transmission in the wireless access point control and configuration CAPWAP data tunnel;

The control module is configured to control the sending module to stop sending the keep-alive message when the determining module determines that there is data transmission in the CAPWAP data tunnel.

6. The device according to claim 5, characterized in that,

The sending module is also configured to send a data message through the CAPWAP data tunnel; wherein, when the sending module sends the data message through the CAPWAP data tunnel, the determining module determines that the CAPWAP Data tunnels have data transmission.

7. The device according to claim 6, wherein the device further includes: a timing module, configured to start timing when the sending module sends the data message through the CAPWAP data tunnel, The control module is also configured to control the timing when the timing of the timing module reaches a preset time and the sending module does not send a data message through the CAPWAP data tunnel within the preset time. The sending module resumes sending keep-alive messages.

8. The device according to claim 5, wherein the device further includes: a receiving module, configured to receive data packets through the CAPWAP data tunnel;

Wherein, when the receiving module receives the data message through the CAPWAP data tunnel, the determining module determines that there is data transmission in the CAPWAP data tunnel.

9. The device according to claim 8, wherein the device further includes: a timing module, configured to start timing when the receiving module receives the data message through the CAPWAP data tunnel. ,

The control module is also configured to control all data packets when the timing of the timing module reaches a preset time and the receiving module no longer receives a data message through the CAPWAP data tunnel within the preset time. The sending module described above resumes sending keep-alive messages.

10. The device of claim 5, wherein the device further includes: a receiving module, configured to receive a data message response through the CAPWAP data tunnel; wherein, the receiving module passes the CAPWAP data When the tunnel receives the data message response, the determining module determines that the CAPWAP data tunnel has data transmission.

11. The device according to claim 10, wherein the device further includes: a timing module, configured to start when the receiving module receives the data message response through the CAPWAP data tunnel. timing,

The control module is also configured to control when the timing of the timing module reaches a preset time and the receiving module does not receive a data message response through the CAPWAP data tunnel within the preset time. The sending module resumes sending keep-alive messages.

12. The device according to any one of claims 5-11, characterized in that the device is a wireless terminal point WTP or an access controller AC.