JP2003224610A - System and method for header compressed packet transfer - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To eliminates expansion/compression processing and to increase line use efficiency by transferring information in a header-compressed state. <P>SOLUTION: A wireless/wired hybrid system which compresses and transfers header information comprises a wireless network controller 5 which transfers header-compressed information received from a mobile terminal after a line is established as a header-compressed packet including the information, and a gateway node equipped with a transfer table which contains pieces of connection path information on the mobile terminal and a request transmission- destination terminal in a related state at a connection request from the mobile terminal when the request is made and a transfer management part which transfers following header-compressed packets to the request transmission destination terminal according to the transfer table. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus or method for transferring header-compressed IP data in a mobile information terminal such as a mobile phone.

[0002]

BACKGROUND OF THE INVENTION For the transfer of conventional compressed IP data, for example, proposals and standards for third generation mobile communication systems are available from the International Telecommunications Union (ITU), the European Telecommunications Standards Institute (ETSI), or It is described in the Third Generation Partnership Project (3GPP). In the prior art, when transferring header-compressed IP data transmitted from an arbitrary mobile information terminal to a destination mobile information terminal, a radio network controller (RN) is used.
In the mobile network device such as C), the header is expanded once. Therefore, in some transmission path sections of the mobile network, the data is converted into non-header compressed data and transferred.

FIG. 14 is a network configuration diagram of such a third-generation mobile communication system, in which a mobile information terminal user transmits header compressed IP data and the same GGSN is transmitted.
(Gateway (General Packet R
audio System) Support Node)
Data is being transferred to the destination mobile information terminal user who is connected to. In the figure, 1 and 2 are mobile information terminals (hereinafter referred to as User Equipment: UE), 3 and 4 are radio base stations whose radio interfaces are connected to the mobile information terminals, and 5 and 6 control radio base stations. Wireless network controller (Radio Network)
rk Controller: hereinafter referred to as RNC),
Servos 107 and 108 are also called subscriber nodes that perform connection control of mobile information terminals and subscriber information management.
ing GPRS Support Node (hereinafter,
SGSN), 109 is the Internet Ser
GatewayGPRS Support Nod, which is a gateway node of a mobile network that performs access control and address management with a Vice Provider (ISP).
e (hereinafter, referred to as GGSN) 10 is an Internet Multimedia S that provides an IP multimedia service to a mobile information terminal connected to a mobile network.
It is an IP network such as a subsystem (hereinafter referred to as IMS).

Next, the procedure of the conventional method will be described with reference to this figure. The two mobile information terminals 1 and 2 for communication are both connected to the same GGSN via the radio base stations 3 and 4, and for the RNC1 5 and RNC2 6, information and parameters of the header compression method to be used, etc. Information is notified. Then, the RNC 15 and the RNC 26, based on the information of the non-header compressed IP data transmitted from the mobile information terminal 1, sequentially transmit static fields such as an IP address included in the header to be compressed as a header compression context, Create both on the receiving side. Further, the mobile information terminal 1 transmits the header compression IP data including the header information not included in the information of the header compression context on the transmission side and the header compression context identifier being used. In the RNC5 that receives this header-compressed IP data, the fields that are not included are restored to the fields that were header-compressed using the reception-side header compression context of the RNC5, and then the normal IP data is transferred to the SGSN 107. To do. At this time, the transfer between the mobile information terminals 1 and 2 within the same system is performed by the IP routing via the GGSN 109 using the restored header information, and the IP is sent to the mobile information terminal 2. Data is transferred. The header compression between the RNC 26 on the receiving side and the mobile information terminal 2 is performed by the same method.

[0005]

Since the IP data in the data transmission between the wireless terminals of the prior art is subjected to the IP routing in the GGSN 109, the mobile information terminal 1 is required.
There is a problem that it is necessary to perform IP header compression / expansion processing on the header compressed IP data transmitted from the. Also,
Since the non-header compressed IP data is used in the transmission path between the RNCs via the GGSN 109, the effect of header compression cannot be obtained, and there is a problem that the band utilization efficiency in the transmission path in the mobile network becomes poor.

The present invention has been made in order to solve the above-mentioned problems, and the header information is not expanded / compressed during the transfer, but the information is transferred with the header compressed, and the expansion / compression processing is performed. Eliminates and improves line usage efficiency.

[0007]

SUMMARY OF THE INVENTION A header compression packet transfer system according to the present invention provides header compression information received from a mobile terminal after establishing a line in a wireless / wired mixed system for compressing and transferring header information. When a connection request is sent from the wireless network control device and the mobile terminal that transfer the header packet as a header-compressed packet, the transfer table stores the connection route information of the mobile terminal and the request destination terminal in association with each other based on the connection request. And a gateway node including a transfer management unit that transfers the subsequent header compressed packet to the request destination terminal based on this transfer table.

Alternatively, in a wireless / wired mixed system in which header information is compressed and transferred, the header compression information received from the mobile terminal after the line is established is transferred as a header compression packet containing this information, and a mobile network controller. When there is a connection request from the mobile terminal, a transfer table that stores the connection route information of the mobile terminal and the request destination terminal in association with each other based on this connection request, and a subsequent header compression packet is requested based on this transfer table. And a subscriber node having a transfer management unit for transferring to a destination terminal.

Furthermore, a system management device for managing a gateway node name passing through the mobile terminal and a request transmission destination from the mobile terminal is provided, and the gateway node receives a connection request from the mobile terminal. , The system management device is inquired to identify the request destination gateway node, and if the identified gateway node can receive the header compressed packet, the header compressed packet is transferred to the request destination terminal thereafter. .

Alternatively, in a wireless / wired mixed system in which a mobile terminal that compresses and transfers header information joins,
The mobile terminal has a function of storing a wireless communication quality judgment threshold value and a function of transmitting a header uncompressed packet from a header compressed packet when the communication quality deteriorates based on the stored threshold value.

A header compression packet transfer method according to the present invention is a method of compressing and transferring header information in a wireless / wired mixed system, and when a connection request is made from a mobile terminal, the mobile terminal moves based on this connection request. The step of registering and storing in the transfer table the connection route information of the mobile terminal and the request destination terminal in association with each other, and the wireless network control for transferring the header compression information received from the mobile terminal after the line is established as a header compression packet including this information. A transfer step and a transfer management step of transferring the header compressed packet received in the wireless network control transfer step to the request destination terminal based on the transfer table are provided.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiment 1. Hereinafter, a preferred embodiment of a header compression packet transfer system in which a transfer is performed without decompressing a header in the wired section according to the present invention except for the first, will be described with reference to the drawings. Figure 1
FIG. 3 is a network configuration diagram for performing a header compression packet transfer system according to the present embodiment. In the figure, 1, 2
Is a mobile information terminal (UE), 3, 4 is a radio base station whose radio interface is connected to the mobile information terminal, 5, 6
Is a radio network controller (R
NC), 7 and 8 are Serving GPRS Sups for controlling connection of mobile information terminals and managing subscriber information.
port Node (SGSN), 9 is Interne
t A Gateway GPRS Suppo, which is a gateway node of a mobile network that controls access with a Service Provider (ISP) and manages addresses.
rt Node (GGSN) 10 is an Internet Multimedia S that provides IP multimedia services to mobile information terminals connected to a mobile network.
It is an IP network such as a web system (IMS).

FIG. 2 shows RF, which is one of header compression methods.
C3095: Robust Header Compr
mobile information terminal 1 in session (ROHC),
IP / UDP / of the header compression context corresponding to 2
This is Static part information of the RTP header. In the figure, 12 is the IP address area of the mobile information terminal 1 on the transmission side in the IPv4 header of the header compression context, and 13 is the mobile information terminal 2 on the reception side communicating with the mobile information terminal 1 on the transmission side. This is the IP address area. FIG. 3 shows the mobile information terminal 1 on the transmitting side and the GG on the receiving side.
It is a part of the header compression context in SN 9, and is information for restoring the header compression IP data. In the figure, 20 is a sender header compression context generated by the mobile information terminal 1, 21 is a reception header compression context generated by the GGSN 9, 22 is a mobile information terminal defined in the header compression contexts 20 and 21. 1 is the IP address, 23 is the destination mobile information terminal 2 defined in the header compression contexts 20 and 21.
IP address.

FIG. 4 is a diagram for explaining the association between the header compression context for the mobile information terminal 1 and the header compression context for the mobile information terminal 2 in the GGSN 9. In the figure, 30 is a header compression context on the transmission side of the mobile information terminal 1, 31 is the first embodiment to transmit only the header compression context on the reception side for the mobile information terminal 1 in the GGSN 9, 3
2 is the header compression context on the transmission side for the mobile information terminal 2 in the corresponding GGSN 9, 33 is the header compression context on the reception side of the mobile information terminal 2, 34 is the header compression context 31 and 3
2 is a header compression context for the mobile information terminal 1 in the GGSN 9 when 2 is associated. Three
Reference numeral 5 is a header compression context for the mobile information terminal 2 in the GGSN 9 when the header compression context 31 and the header compression context 32 are associated, and 36 is virtually associated with the header compression context 31 and the header compression context 32. It is a unified pseudo-header compression context.

FIG. 5 is a view for explaining the transfer mechanism of header compressed IP data in GGSN 9. In the figure, 40 is a header compression / decompression unit, 41 is a header compression IP.
A transfer management unit that controls the header compression / decompression process for the data transfer destination and the header compression / decompression unit, 42 is a transfer table generated in the transfer management unit 41, and 43 is a transfer path established by the transfer table 42. Is.

The header compression IP data transfer operation according to the first embodiment is performed by the mobile information terminal 1 on the transmitting side and the GGSN.
9. FIG. 6 showing a sequence between the mobile information terminal 2 on the receiving side and FIG. 1 to FIG. First, the mobile information terminal 1 receives the RNC 5, SG via the radio base station 3.
A connection procedure is performed with SN7 and GGSN9 to establish a route from mobile information terminal 1 to GGSN9. This route is a route that can uniquely identify the mobile information terminal 1. The mobile information terminal 2 receives the RNC via the radio base station 4.
6, SGSN 8 and GGSN 9 connection procedure,
A route from the mobile information terminal 2 to the GGSN 9 has been established. This route is a route that can uniquely identify the mobile information terminal 2.

The header compression method used when establishing this connection has already been notified, and the mobile information terminals 1 and 2 and the GGSN 9 perform header compression / decompression processing using this notified compression method. . This compression method is specified by
It is outside the scope of this specification. The mobile information terminal 1 starts transmitting non-header compressed IP data in response to the data transmission request to the mobile information terminal 2 (S100). Upon receiving the non-header compressed IP data, the GGSN 9 generates a header compression context corresponding to the CID: 1 of the mobile information terminal 1 (S101), and Sta of the non-header compressed IP data is generated.
The header compression context generation is completed for both the mobile information terminal 1 and the GGSN 9 by incorporating the tic part information into the header compression context, and the header compression / decompression function for the header compressed IP data between the mobile information terminal 1 and the GGSN 9 is provided. It can be used. The GGSN 9 transfers the non-header compressed IP data to the mobile information terminal 2 by IP routing, and generates a header compression context for the mobile information terminal 2 (S102). Then, in the present embodiment, the information of the header compression contexts 31 and 32 in the GGSN 9 is newly associated and registered in the transfer table 42 of the transfer management unit 41 (S103). After that, since the static part information of the associated header compression contexts 31 and 32 is the same, one header compression context 3 is artificially created.
Handle as 6.

After the header compression IP data transfer path 43 is established, when the header compression / decompression unit 40 for the mobile information terminal 1 receives the header compression IP data from the mobile information terminal 1, according to the present embodiment. Since the connection destination has already been registered according to the contents of the transfer table 42, the header information compressed without performing the header decompression process is directly used as the connection ID:
The IP data is transferred to the transfer route of No. 3 (S104). The process of the header compression / decompression unit at this time is the same as the process of transferring the non-header compressed IP data. In this way, the decompression process of the header information after the transfer route is established is unnecessary, the processing time can be shortened, and the use efficiency of the transmission line is improved.
If the connection destination is not registered in the transfer table 42, header restoration processing is performed and normal transfer processing is performed.

The above system has the configuration shown in FIG.
In the GSN 9, a header compression context is associated with the source mobile information terminal 1 and the destination mobile information terminal 2 and the compressed header information is transferred to the destination terminal without being restored. The following description enables the transfer to the destination mobile information terminal 2 without restoring the compressed header by performing the same processing in the SGSN 11. FIG. 7 is a network configuration diagram showing another header compression packet transfer system according to the present embodiment. In the figure, 11 is an SGSN holding a header compression context. That is, FIG.
5 is performed to perform the association shown in FIG.

FIG. 8 shows the mobile information terminal 1 on the transmitting side and the SGS.
It is a figure which shows the sequence which transfers the header compression IP data between N11 and the receiving side mobile information terminal 2. The operations performed by the SGSN 11 shown in FIG. 7 are shown in FIGS.
This will be described using 8. First, the mobile information terminal 1 receives the RNC 5, SGSN 11, and GGSN via the radio base station 3.
9 perform connection procedure with SGS from mobile information terminal 1.
Establish a path to N 11. The mobile information terminal 2 receives the RNC 6, SGSN 11, GG via the radio base station 4.
Perform connection procedure with SN 9, and from mobile information terminal 2 to S
Establish a route to GSN11.

The header compression method used when establishing this connection has already been notified, and the mobile information terminals 1 and 2 and the SGSN 11 perform header compression / decompression processing using the notified compression method. . First, the mobile information terminal 1
Starts transmission of non-header compressed IP data in response to a data transmission request to mobile information terminal 2 (S110). Upon receiving the non-header compressed IP data, the SGSN 11 generates a header compression context corresponding to the mobile information terminal 1 (S111), and the Stat of the non-header compressed IP data is generated.
The header compression context generation is completed for both the mobile information terminal 1 and the SGSN 11 by incorporating the ic part information into the header compression context. Thus, the header compression / decompression function of the header compression IP data between the mobile information terminal 1 and the SGSN 11 can be used. SGNS
11 transfers the non-header compressed IP data to the mobile information terminal 2 by IP routing, and generates a header compression context for the mobile information terminal 2 (S112).
Then, the information of the header compression contexts 31 and 32 in the SGSN 11 which is a feature of this embodiment is associated and registered in the transfer table 42 of the transfer management unit 41 (S113). The Static part information of the associated header compression contexts 31, 32 is treated as one header compression context 36.

After the header compression IP data transfer path 43 is established, when the header compression IP data from the mobile information terminal 1 is received by the header compression / decompression unit 40 of the SGSN 11, the connection destination is determined by the contents of the transfer table 42. Knowing that it has been registered, connection ID: 3 without performing header restoration processing
IP data is transferred to the transfer path of That is, the transfer to the GGSN 9 is not performed. At this time, the header compression / decompression unit for the mobile information terminal 2 performs only the transfer process with the transferred header-compressed IP data as the output of its own module (S
114). The process of the header compression / decompression unit at this time is the same as the process of transferring the non-header compressed IP data. If the connection destination is not registered in the transfer table 42, header restoration processing is performed and normal transfer processing is performed.

Thus, according to the configuration of FIG. 7, since the SGSN has the function of generating the header compression context, the header decompression process is not required in S114, and the time is shortened and the use efficiency of the route is improved. Further, since it is not necessary to transfer to the GGSN, efficient header compressed IP data transfer is possible.

Embodiment 2. GG in the first embodiment
Since the SN needs to identify whether the destination terminal and the source terminal are connected to the same GGSN, the identification process occurs even when a transmission request is made to a destination terminal that is not connected.
In this embodiment, the GG for IP data communication in the mobile network is used.
By dividing the SN and the GGSN for IP data communication outside the mobile network, it is possible to reduce the processing load due to the identification processing. FIG. 9 is a configuration diagram of a header compression packet transfer system according to the present embodiment. In FIG. 9, 14 is a GGSN (APN) for IP data communication into a mobile network.
1) and 15 are GGS for IP data communication outside the mobile network.
N (APN2).

FIG. 10A is a sequence diagram showing the transfer operation of the system shown in FIG. See also FIG.
FIG. 9B is a diagram showing access point name (APN) management information held by a management department (DNS) that receives an address inquiry, for explaining the transfer operation. The transfer operation will be described with reference to these figures. As the information on the mobile information terminal 1, the information on the destination mobile information terminal 2 and the information on the contracted carrier are registered. After the wireless connection is established, as shown in FIG. 10A, when the mobile information terminal 1 makes a connection request to the ASP 2 (S1).
21), the SGSN 11 inquires of the DNS about the destination mobile information terminal 2 to the DNS (S122).

When a response is obtained (S123) and the carrier information of the mobile information terminal 1 is the same as that of the mobile information terminal 2, it is possible to connect to the same mobile network, and thus the APN1 for IP data communication into the mobile network. Secondary PDP using
Connection processing is performed to the GGSN 14 according to the context (S124). The GGSN 14 creates the header compression context 1 and transfers the IP data to the mobile information terminal 2 by IP routing. After this, the mobile information terminal 2
AP to perform IP data communication with the mobile information terminal 1
Make a connection to GGSN 14 using N2. The mobile information terminal 1 continues the header compression context associating process for a certain time until the mobile information terminal 2 is connected and the header compression context 2 is generated. After the completion of the association of the header compression contexts, the header compression IP data transfer similar to that of the first embodiment becomes possible. However, if the header compression context 2 is not generated for a certain period of time, A
The connection is switched to the GGSN 15 of PN2.

In FIG. 9, when the carrier information of the mobile information terminal 1 is different from that of the mobile information terminal 2, the GGSN is used by using the APN 1 for IP data communication outside the mobile network.
Connected to 15, IP data transfer by normal IP routing is performed. At this time, the GGSN 15 does not perform the header compression context associating process for IP data communication outside the mobile network. According to this system configuration, SG
The SN 11 increases the number of inquiries (S122) and responses (S123) to the DNS. However, since the destination GGSN is known thereafter, the compressed header transfer is performed only to the corresponding GGSN.
Thus, the GGSN 1 for IP data communication into the mobile network
4 and the GGSN 15 for IP data communication to the outside of the mobile network, the same GG generated in the first embodiment
Since it is not necessary to perform the identification processing of the intra-mobile network communication and the intra-mobile network communication within the SN, the processing of each GGSN can be unified, and the load can be reduced.

Embodiment 3. In the present embodiment, another method of improving header compression packet transfer, particularly regarding reduction of transfer time, will be described. That is, when the communication distance with other devices such as between mobile information terminals becomes long, normal restoration cannot be performed when the header compression context is restored due to waveform distortion, loss of synchronization, delay, etc. As a result, the compression is stopped, and when the system recovers again, the compression is restarted. Delay due to such progress processing, Round
A system for reducing Trip Time (RTT) will be described. The system configuration diagrams are shown in FIG. 1, FIG. 7, and FIG.
Either of them may be used. The mobile information terminal whose functional flow diagram is shown in FIG. 11 transfers the header-compressed packet or the header-uncompressed packet in the sequence shown in FIG.

Prior to the description of the operation, a conventional header compression / non-compression transfer state will be described for comparison. FIG. 13 is a conventional sequence diagram, and particularly shows a case where the compressed header cannot be normally transferred due to an error or delay in the device / line. That is, conventionally, the compressed packet is started to be transferred in S313 and subsequent steps, and the header restoration fails in S316a.
When the header compression context is out of sync with S, S
Data loss, a so-called RTT state, continues over a period of 318. When the communication distance becomes long, this RTT state occurs, the processing time becomes long, and the line congestion degree also increases.

On the other hand, the RNC in the present embodiment
Performs the operation shown in FIG. First, a parameter serving as a criterion for shifting to a header uncompressed packet is selected in advance (S201). Similarly, the threshold value in that case is set to, for example, 5
Percentage, that is, it is set to be uncompressed when it exceeds this (202). A line connection is established and IP packet transmission is started (S203). After that, the state check of FIG. 11 is repeated through the transfer operation shown in the sequence diagram 12 (S204 to S207). The sequence will be described with reference to FIG. 12. In this case, the parameter BLE in FIG.
Since R is set to the set threshold value of 5% (S202), when the line state deteriorates with the passage of time and the state where BLER exceeds 5% is detected (S215), the transfer management unit 41 causes header non-compression. The packet transmission is started (S216).

Thus, when the BLER is larger than the 5% threshold value, the header compression state is changed to the non-header compression state (S216), so that the next reception is performed even if the synchronization shift occurs due to the IP data loss in the wireless section. If the IP data is normal, all necessary information is transmitted by non-header compression I, and a procedure for synchronization recovery is unnecessary. BLER
Is smaller than the threshold value of 5%, the header compression state is changed again to the header compression state (S219), and the header compression IP
Resume data transfer. In this way, BLE of wireless section
In order to prevent the synchronization deviation of the header compression context by predicting the IP data loss in the wireless section where the possibility of IP data loss is high from the R measurement, by reducing the number of times the synchronization deviation of the header compression context occurs, RTT until recovery is achieved. Can be reduced.

[0032]

As described above, according to the present invention, the wireless network control device for transferring the header compressed packet and the GGSN or SGSN for transferring the header compressed packet to the request destination by the transfer table are provided. , The information is transferred while the header is compressed, the decompression / compression process is not required, and the processing time can be shortened, and the line use efficiency is improved.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a header compression packet transfer system according to a first embodiment of the present invention.

[Fig. 2] Static in one of the header compression methods
It is a figure which shows part information.

FIG. 3 is a diagram showing a part of a header compression context in a mobile terminal.

FIG. 4 is an explanatory diagram of a header compression context according to the first embodiment.

FIG. 5 is a diagram illustrating a transfer process with reference to a transfer table in a transfer management unit.

FIG. 6 is a diagram showing a transfer sequence performed by a transfer management unit according to the first embodiment.

FIG. 7 is a configuration diagram of another header compression packet transfer system according to the first embodiment.

FIG. 8 is a diagram showing a transfer sequence performed by another transfer management unit according to the first embodiment.

FIG. 9 is a configuration diagram of a header compression packet transfer system according to a second embodiment of the present invention.

FIG. 10 is a diagram showing an example of a transfer sequence performed by a transfer management unit according to the second embodiment and a table held by a system management device.

FIG. 11 is a flowchart of operations performed by the mobile terminal according to the third embodiment of the present invention.

FIG. 12 is a diagram showing an example of the sequence of the system in the third embodiment.

FIG. 13 is a conventional sequence diagram shown for comparison.

FIG. 14 is a diagram of a conventional packet transfer system between mobile terminals.

[Explanation of Codes] 1, 2 Mobile Information Terminals, 3, 4 Radio Base Stations, 5, 6
A wireless network control device (R
NC), 7, 8, 11 Serving GPRS S
upport Node (SGSN), 10 IP network,
9,14,15 Gateway GPRS Suppo
rt Node (GGSN), 12, 13, 20-2
3, 30 to 36 Header compression context information, 40
Header compression / decompression unit, 41 transfer management unit, 42 transfer table, 43 transfer route of header compressed IP data.

Claims (5)

[Claims] 1. In a wireless / wired mixed system for compressing and transferring header information, header compression information received from a mobile terminal after establishing a line,
When there is a connection request from the wireless network control device that transfers as a header compressed packet including the information, the mobile terminal associates the connection route information of the mobile terminal with the request destination terminal based on the connection request. A header compressed packet transfer system comprising a transfer table to be stored and a gateway node having a transfer management unit for transferring the header compressed packet thereafter to the request destination terminal based on the transfer table. . 2. In a wireless / wired mixed system for compressing and transferring header information, header compression information received from a mobile terminal after establishing a line,
When there is a connection request from the wireless network control device that transfers as a header compressed packet including the information, the mobile terminal associates the connection route information of the mobile terminal with the request destination terminal based on the connection request. Header compression packet transfer comprising a transfer table to be stored, and a subscriber node having a transfer management unit for transferring the header compression packet thereafter to the request destination terminal based on the transfer table system. 3. A system management device for managing a gateway node name that passes through a mobile terminal and a request destination from the mobile terminal, wherein the gateway node receives a connection request from the mobile terminal. , The system management apparatus is inquired to specify the gateway node of the request transmission destination, and if the specified gateway node can receive the header compression packet, thereafter, the header compression packet is transferred to the request transmission destination terminal. The header compression packet transfer system according to claim 1, wherein 4. In a wireless / wired mixed system to which a mobile terminal that compresses and transfers header information joins, the mobile terminal has a function of storing a wireless communication quality judgment threshold value, and based on the stored threshold value. A header-compressed packet transfer system having a function of transmitting a header-uncompressed packet from a header-compressed packet when communication quality deteriorates. 5. A method of compressing and transferring header information in a wireless / wired mixed system, wherein when a connection request is issued from a mobile terminal, the mobile terminal and the request destination terminal are connected based on the connection request. The step of associating and storing the connection route information in the transfer table and the header compression information received from the mobile terminal after the line is established,
A wireless network control transfer step of transferring as a header compressed packet containing the information, and a transfer management step of transferring the header compressed packet received in the wireless network control transfer step to a request destination terminal based on the transfer table. A header-compressed packet transfer method comprising: