Method for auditing the tunnel of tunnelling protocol in generic packet radio protocol

How to monitor the tunnel in the wireless packet service tunneling protocol

1 is a view showing a general mobile communication system to which the present invention is applied;

FIG. 2 is a prior art view showing that an echo message transmits only path information; FIG.

3 is a diagram of the present invention, showing that an echo message transmits a list of TEIDs together with path information;

<backgroundart><p>The present invention relates to a wireless packet service in a mobile communication system, and more particularly to a tunneling protocol.</p><p>Generic Packet Radio Service (GPRS) is a data transmission method used in the 3rd Generation Partnership project (3GPP), and is a method of transmitting data in packet units.</p><p>1 shows a typical mobile communication system that provides the wireless packet service.</p><p>The system includes a terminal 100 , a UMTS Terrestrial Radio Access Network (UTRAN) 110 , an SGSN 120 , and a GGSN 130 . The UTRAN 110 serves as a base station of a conventional mobile communication system. The SGSN (Serving GPRS Support Node: service radio packet service support node) 120 and GGSN (Gateway GPRS Support Node: gateway radio packet service support node) 130 are the GSN (GPRS Support Node: radio packet service support node) of is a kind The radio packet service support node serves as a switching center of the existing mobile communication system. In general, a wireless packet service system establishes a packet data protocol (PDP) environment between the wireless packet service supporting nodes by using a tunneling protocol. As described in the 3GPP TS29.060 document, the radio packet service tunneling protocol is a packet between GSNs, for example, between the service radio packet service support node 120 of FIG. 1 and the gateway radio packet service support node 130. Tunneling protocol is used for data protocol configuration.</p><p>The tunneling protocol uses an echo message as a method for managing a path between the service radio packet service support node 120 and the gateway radio packet service support node 130 . </p><p>2 is a prior art diagram showing echo messages 200 and 210 between the service radio packet service support node 120 and the gateway radio packet service support node 130 .</p><p>As shown in FIG. 2 , the echo message is divided into an echo request message 200 and an echo response message 210 . As shown in FIG. 2, the echo messages 200 and 210 include path information. Using the echo message, it is possible to check whether the counterpart node is operating normally and whether it is restarted. However, several tunnels exist in one path according to the number of serviced terminals. As described above, if the echo message is used, it is possible to check whether the path is operating or not, but it is not possible to check whether the counterpart device (Entity) for each tunnel in the path is operating normally. As a result, the system had to separately define a new audit message to check whether the counterpart device for each tunnel operates normally.</p></backgroundart><abstractproblem><p>Accordingly, it is an object of the present invention to provide a method of performing a monitoring function of a device assigned to a counterpart node using an echo message used in the past without defining a new audit message.</p><p>In order to achieve the above object, the present invention uses a method of adding a TEID item to the private extension field of the echo message. </p></abstractproblem>

<p>Hereinafter, the present invention will be described in detail with reference to the drawings.</p><p>3 is a diagram illustrating the present invention, showing that the echo messages 300 and 310 between the wireless packet service support nodes 120 and 130 include a Tunnel Endpoint IDentifier (TEID) along with path information. is a drawing that In FIG. 3, the echo request message 300 includes a list of peer TEIDs in addition to path information. Also, the echo response message 310 corresponding thereto includes a list of mismatched TEIDs in addition to the route information. The structure of the echo request message 300 is shown in Table 1 below.</p><p><tables id="1"><table colsep="0" frame="top" id="1" rowsep="0"><title /><tgroup align="left" cols="2" colsep="0" rowsep="0" xmlns="http://www.oasis-open.org/tables/exchange/1.0"><colspec align="left" char="0" charoff="0" colname="1" colnum="1" colsep="0" colwidth="3025" rowsep="0" /><colspec align="left" char="0" charoff="0" colname="2" colnum="2" colsep="0" colwidth="3522" rowsep="0" /><tbody valign="top"><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">Information Element</entry><entry align="left" morerows="0" nameend="2" namest="2">Presence Requirement</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">Private Extension</entry><entry align="left" morerows="0" nameend="2" namest="2">Optional</entry></row></tbody></tgroup></table></tables></p><p>In addition, the structure of the echo response message 310 is shown in Table 2 below.</p><p><tables id="2"><table colsep="0" frame="top" id="2" rowsep="0"><title /><tgroup align="left" cols="2" colsep="0" rowsep="0" xmlns="http://www.oasis-open.org/tables/exchange/1.0"><colspec align="left" char="0" charoff="0" colname="1" colnum="1" colsep="0" colwidth="3292" rowsep="0" /><colspec align="left" char="0" charoff="0" colname="2" colnum="2" colsep="0" colwidth="3292" rowsep="0" /><tbody valign="top"><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">Information Element</entry><entry align="left" morerows="0" nameend="2" namest="2">Presence Requirement</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">Recovery</entry><entry align="left" morerows="0" nameend="2" namest="2">Mandatory</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">Private Extension</entry><entry align="left" morerows="0" nameend="2" namest="2">Optional</entry></row></tbody></tgroup></table></tables></p><p>Referring to Tables 1 and 2, it can be seen that the two echo messages, the echo request message 300 and the echo response message 310, include a private extension field in common. The private extension field, which is the common field, is used in the present invention. The Private Extension field has a configuration as shown in Table 3 below.</p><p><tables id="3"><table colsep="0" frame="top" id="3" rowsep="0"><title /><tgroup align="left" cols="2" colsep="0" rowsep="0" xmlns="http://www.oasis-open.org/tables/exchange/1.0"><colspec align="left" char="0" charoff="0" colname="1" colnum="1" colsep="0" colwidth="1364" rowsep="0" /><colspec align="left" char="0" charoff="0" colname="2" colnum="2" colsep="0" colwidth="3707" rowsep="0" /><tbody valign="top"><row rowsep="0" valign="middle"><entry align="left" morerows="4" nameend="1" namest="1"> Octets 1 2-3 4-5 6-m</entry><entry align="left" morerows="0" nameend="2" namest="2">Bits 8 7 6 5 4 3 2 1</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="2" namest="2">Type=255(Decimal)</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="2" namest="2">Length</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="2" namest="2">Extension Identifier</entry></row><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="2" namest="2">Extension Value</entry></row></tbody></tgroup></table></tables></p><p>As Table 3 shows, the Private Extension field includes a form, a length, an extension identifier (Extension Identifier), and an extension value (Extension Value) fields. Used in the present invention are the Extension Identifier and Extension Value fields. In the Extension Identifier area, an identifier (ID) meaning a tunnel audit request and a tunnel audit response for each of the echo request message 300 and the echo response message 310 is provided. define. Meanwhile, a list composed of tunneling identifier (ID) information of the counterpart node is added to the extension value area of the echo request message 300 . The structure of the list is shown in Table 4.</p><p><tables id="4"><table colsep="0" frame="top" id="4" rowsep="0"><title /><tgroup align="left" cols="1" colsep="0" rowsep="0" xmlns="http://www.oasis-open.org/tables/exchange/1.0"><colspec align="center" char="0" charoff="0" colname="1" colnum="1" colsep="0" colwidth="4534" rowsep="0" /><tbody valign="top"><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">1 32</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Peer TEID 1</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Peer TEID 2</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">...</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Peer TEID n</entry></row></tbody></tgroup></table></tables></p><p>Table 4 shows the configuration of information added to the extension value field of the echo request message 300 to implement the present invention. the TE<u>I</u>D is a value defined in the Extension Identifier area. On the other hand, in the Extension Value area of the echo response message 310, TEID information obtained from the echo request message 300 is checked, and only TEIDs that do not operate are listed. The configuration of the extension value of the echo response message 310 is shown in Table 5 below.</p><p><tables id="5"><table colsep="0" frame="top" id="5" rowsep="0"><title /><tgroup align="left" cols="1" colsep="0" rowsep="0" xmlns="http://www.oasis-open.org/tables/exchange/1.0"><colspec align="center" char="0" charoff="0" colname="1" colnum="1" colsep="0" colwidth="4534" rowsep="0" /><tbody valign="top"><row rowsep="0" valign="middle"><entry align="left" morerows="0" nameend="1" namest="1">1 32</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Mismatch TEID 1</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Mismatch TEID 2</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">...</entry></row><row rowsep="0" valign="middle"><entry align="center" morerows="0" nameend="1" namest="1">Mismatch TEID n</entry></row></tbody></tgroup></table></tables></p><p>The mismatch TEID is an identifier (ID) of a non-operational device.</p><p>That is, in order to carry out the present invention, each radio packet service support node must have a list of TEIDs allocated to it and a list of TEIDs that must exist in the counterpart node. When the radio packet service support node sends an echo request message to the counterpart node, it sends the counterpart TEID list. In this case, in the TEIDs each of 4 bytes, the number of TEIDs should be less than 16,000 because the size of the payload should be less than 64,000 bytes in the header structure of the wireless packet service tunneling protocol. In addition, if the number of tunnels operating in the system is larger than the number of tunnels set by the monitoring function, a method of dividing transmission should be used several times. Also, consider reducing the network load by setting the tunnel monitoring period to a value larger than the echo request period. The node receiving the echo request message 300 should always be ready to send the echo response message 310 . The node receiving the echo request message 300 checks the TEID list included in the echo request message 300 and the TEID list allocated to it, and if it does not exist in the TEID list included in the echo request message 300 creates it as a list of mismatched TEIDs. Thereafter, the node receiving the echo request message 300 adds the generated list of mismatched TEIDs to the echo response message 310 and sends it. Therefore, using the above method, it is possible to monitor TEIDs that do not match with respect to the tunnel established by the counterpart node.</p>

<p>By implementing the present invention as described above, it is possible to implement a radio packet service tunneling protocol tunnel monitoring function by adding TEID information to an existing echo message.</p>