KR20090031186A - Method of transferring header-compressed packet, mobile station, base station, and control station in wireless communication system - Google Patents

Abstract

A method for processing a header compressed packet in a wireless communication system, a terminal, a base station, and a control station are provided to identify whether the packet header is compressed or not and classify IP flow separated from compression context identifier by using IP flow and mapping information of header compressed context identifier. A method for processing a header compressed packet in a wireless communication system, a terminal, a base station, and a control station comprises following processes. The CSN(Connectivity Service Network)(102) transmits a ROHC(Robust Header Compression) downlink packet to a terminal(120). The terminal transmits ROHC uplink packet to CSN. CSN conducts authentication, authorization and accounting functions for ASN(Access Service Network)(108) and the terminal, and makes network service policy and billing rule. ASN carries out connection setup function for wireless interface and layer-2 between the terminal and a base station, network discovery and network selection function, and a pass-through function for the terminal to Layer-3 and radio resource management function to support mobility of the terminal. An ASN- GW(Access Service Network Gateway)(110) performs a ROHC compression to the downlink packet and transmits the result to a base station(118), and then decompresses ROHC uplink packet and transmits the result to CSN.

Description

Method of processing header compression packet in wireless communication system, terminal, base station, and control station {Method of Transferring Header-compressed Packet, Mobile Station, Base Station, and Control Station in Wireless Communication System}

The present invention relates to a header compression packet processing method, a terminal, a base station, and a control station in a wireless communication system, and more particularly, to a packet transmission path mapped to a service flow in a broadband wireless system. The present invention relates to a method for processing a header compressed packet through a terminal, a base station, and a control station.

In wireless communication systems, it is particularly important to utilize limited resources as efficiently as possible. However, this makes it more difficult to utilize the IP protocol on the air interface, since in IP-based protocols the share of the various headers in the data to be transmitted is very large, resulting in a smaller share of the payload. For example, if you implement VoIP using IPv4, a significant amount of radio frequency bandwidth will be wasted in transmitting the header, and IPv6 will result in an even higher bandwidth loss due to the increased header size.

In addition, under poor conditions, the bit error rate (BER) of the air interface and the round trip time (RTT) of the uplink and downlink are greatly increased, which causes problems for most prior art header compression schemes.

For this reason, there is a need to revise header compression methods suitable for various IP protocols and packet transmissions over the air interface, and in particular, there is a demand for an efficient header compression method that can be utilized under conditions in which bit error rates and delays are greatly increased. Was generated. For this reason, the Internet Engineering Task Force (IETF) has recently standardized a header compression method known as Robust Header Compression (ROHC).

One of the major reasons for the development of ROHC is the large number of duplicates not only in packets but also between packets, or between the various IP headers used for packet transmission. That is, most of the information in the header does not change at all during data packet transmission, and in this case, the information contained in the header can be easily reconstructed at the receiving end even if not transmitted at all.

For the foregoing reasons, the WiBRO technology and the WiMAX NWG (Wireless Interoperability for Microwave Access Forum Network Working Group) are based on the IEEE 802.16 technology standard to provide the wireless Internet service of the terminal through a header compression method such as ROHC. I'm trying to provide.

However, although there is a need for a structure and procedure for the ROHC function for implementing the ROHC function in the WiMAX network, no solution has been proposed.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-described problem, and provides a header compression packet processing method, a terminal, a base station, and a control station in a wireless communication system capable of processing header compressed packets through a transmission path mapped to a service flow. Let it be technical problem.

The present invention also provides a method for processing a header compressed packet in a wireless communication system capable of mapping and transmitting an IP flow separated by a header compression context identifier to a service flow, a connection identifier, or a data path tag, a terminal, and a base station. It is another technical problem to provide a control station and a control station.

Another object of the present invention is to provide a header compression packet processing procedure in an ASN and a terminal including a control station and a base station.

In the method for processing a header compression packet in a wireless communication system according to an aspect of the present invention for achieving the above object, if a service flow of a downlink packet is mapped to a header compression transmission channel at a control station, the header of the downlink packet is Obtaining a second packet including a header compression context identifier (Context ID) mapped to an IP flow of the downlink packet to a first packet compressed with the first packet; Adding a data path tag mapped to a service flow of the downlink packet to the second packet; And transmitting a second packet to which the data path tag is added to a base station that maintains mapping information of the data path tag and a connection identifier corresponding to the terminal to be transmitted to a terminal using the header compressed transmission channel. Characterized in that it comprises a step.

According to another aspect of the present invention, there is provided a method of processing a header compressed packet in a wireless communication system, in a control station, mapping a first packet in which a header of an uplink packet is compressed to an IP flow of the uplink packet. Receiving, from a base station receiving a second packet with a header compression context identifier added thereto, the second packet with a data path tag mapped to a connection identifier of the uplink packet; And if the service flow corresponding to the data path tag of the second packet is mapped to a header compressed transport channel including the header compressed transport identifier, decompressing the second packet through the header compressed transport context identifier Restoring a header of the uplink packet.

According to another aspect of the present invention, there is provided a method for processing a header compressed packet in a wireless communication system according to another aspect of the present invention. Receiving; When the service flow of the downlink packet is mapped to a header compression transport channel, a second packet including a header compression context identifier mapped to the IP flow of the downlink packet is added to the first packet that compresses the header of the downlink packet. Obtaining; And transmitting the second packet to the terminal corresponding to the connection identifier mapped to the data path tag so that the second packet is transmitted to the terminal using the header compression transmission channel.

According to another aspect of the present invention, there is provided a method for processing a header compressed packet in a wireless communication system. Receiving a second packet appended with a mapped header compression context identifier; If the service flow corresponding to the connection identifier of the second packet is mapped to a header compression transport channel including the header compression context identifier, the second packet is decompressed through the header compression context identifier to decompress the uplink packet. Restoring the header; And adding a data path tag mapped to the connection identifier to the uplink packet whose header is restored, and transmitting the data path tag to the control station mapped to the data path tag.

According to another aspect of the present invention, there is provided a method for processing a header compression packet in a wireless communication system, the method comprising: performing ROHC compression on the data packet such that a service flow of the data packet and a ROHC channel are one-to-one mapping; And adding the data path identifier mapped to the service flow to transmit the ROHC compressed data packet.

According to another aspect of the present invention, there is provided a method for processing a header compression packet in a wireless communication system, the method comprising: performing ROHC compression on the data packet such that a service flow of the data packet and a ROHC channel are one-to-one mapping; And adding the connection identifier mapped to the service flow to transmit the ROHC compressed data packet.

In order to achieve the above object, a control station in a wireless communication system according to an aspect of the present invention includes a first header context identifier mapped to an IP flow of the downlink packet in a first packet that compresses a header of a downlink packet. A header compression unit generating an added second packet; If a fourth packet including a second header compression context identifier mapped to the IP flow of the uplink packet is transmitted to a third packet in which a header of an uplink packet is compressed, the second packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress an uplink packet to restore a header of the uplink packet; And appending a data path tag mapped to the service flow of the downlink packet to the second packet to transmit to the base station mapped to the data path tag, and assigning the second header compression context identifier to the service flow of the uplink packet. And a data path management unit for transmitting the fourth packet to the header decompression unit when the header compression transport channel is mapped.

In the wireless communication system according to an aspect of the present invention for achieving the above object, the base station includes a first header compression context identifier mapped to an IP flow of the downlink packet in a first packet that compresses a header of the downlink packet. A header compression unit generating an added second packet; When a fourth packet including a second header compression context identifier mapped to an IP flow of the uplink packet is transmitted to a third packet that compresses a header of an uplink packet, the fourth packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress a packet to restore a header of the uplink packet; And transmitting the second packet to the terminal according to a connection identifier added to the downlink packet and mapped to a data path tag transmitted from a control station, wherein the second header compression context identifier is added to a service flow of the uplink packet. And a data path manager for transmitting the fourth packet to the header decompressor when the included header compressed transport channel is mapped.

In a wireless communication system according to an aspect of the present invention for achieving the above object, a terminal receives a first header compression context identifier mapped to an IP flow of an uplink packet in a first packet that compresses a header of an uplink packet. A header compression unit generating an added second packet;

If a fourth packet including a second header compression context identifier mapped to an IP flow of the downlink packet is transmitted to a third packet in which a header of a downlink packet is compressed, the fourth packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress a packet to restore a header of the downlink packet; And transmitting the second packet to a base station mapped to a connection identifier corresponding to a service flow of the uplink packet, and decompressing the fourth packet when the header compression transport channel is mapped to the connection identifier of the downlink packet. It characterized in that it comprises a data path management unit for transmitting to.

As described above, according to the present invention, by using mapping information of an IP flow belonging to a service flow and a header compression context identifier, a radio capable of classifying whether the packet compression is applied and whether the IP flow separated by the header compression context identifier can be classified. The header compression packet processing method, a terminal, a base station, and a control station in a communication system can be implemented.

In addition, the present invention can be transmitted by mapping the IP flow separated by the header compression context identifier in the terminal, base station, and control station to the service flow, the connection identifier, and the data path tag by using the service flow information. The header compression packet processing method, a terminal, a base station, and a control station in a wireless communication system can have other effects.

In addition, the present invention defines a mapping process of packet classification and header compression context identifiers in a terminal, a base station, or a control station including a header compression unit and a header decompression unit, and thus, another effect of clearly implementing a header compression packet transmission and reception procedure. There is.

Before describing the embodiments of the present invention, the terms used in the present invention will be briefly described.

ROHC function: A functional entity that includes a ROHC decompressor and a ROHC decompressor defined in RFC 3095.

ROHC Service Flow (ROHC SF): An 802.16e service flow that maps to an ROHC channel. In other words, a Convergence Sub-layer (CS) type is defined as "Packet, ROHC Header Compressed IP" in the service flow.

ROHC Channel: A logical unidirectional point to point channel that transmits ROHC packets from the ROHC compressor to the decompressor. See Section 2 of RFC3757.

ROHC Compressor: A functional entity that inspects IP headers and compresses them into ROHC headers having a ROHC header context. See the definition of the ROCH compression section in the RFC3757 document.

ROHC Decompressor: A functional entity that maintains the header context and reconstructs from the compressed headers to the original header. See the definition of the ROHC decompressor example in RFC3757.

Per-channel Negotiation: A procedure for negotiating channel-level parameters between the ROHC compression unit and the ROHC decompression unit.

Per-channel Parameters: The ROHC channel is based on a number of parameters to form part of the established channel state and the per-context state.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of a wireless communication system including a control station and a terminal having a ROHC function (Robust Header Compression function) according to an embodiment of the present invention.

Referring to FIG. 1, a wireless communication system according to an embodiment of the present invention includes a connectivity service network (CSN) 102, an access service network (ASN) 108, and a mobile station 120 (CSN) 102. ) Transmits the ROHC downlink packet from the mobile station 120 to the terminal, and transmits the ROHC uplink packet from the terminal MS 120 to the CSN 102.

CSN 102 includes AAA (Authentication-Authorization-Accounting: 104) and PCRF (Policy and Charging Rules Function (106)), and for ASN 108 and UE 120, through AAA 104 It performs authentication, authorization, and account management functions, and generates rules related to user's network service policy and billing through PCRF 106. In addition, to support the mobility of the terminal 120 includes a home agent (HA) (not shown), and delivers the packet from the HA to the terminal 120 through the ASN (108).

The AAA 104 transmits a Subscriber Profile including an ROHC policy to an Access Service Network GateWay 110 (ASN-GW) during a user authentication process for a pre-provisioned service flow. . It also maintains a subscriber profile that includes the ROHC policy. Accordingly, the AAA 104 performs the above-described function so that the ASN-GW 110 serving as the terminal 120 and the control station (not shown) can recognize whether the ROHC is applied.

The PCRF 106 transmits the subscriber profile including the ROHC policy to the ASN-GW 110 for the dynamic service flow, so that the terminal 120 and the ASN-GW 110 transmit and receive the ROHC packet. To recognize whether or not

The ASN 108 includes a control station ASN-GW 110 and a base station 118, and includes a radio interface between the base station BS1 118 and the terminal 120 and a layer-2 connection establishment function, and network discovery. A network discovery and a network selection function, a delivery function for establishing a layer-3 connection of the terminal 120, and a radio resource management function are provided.

The ASN-GW 110 includes a service flow authorization unit 112, a data path function 114, and a ROHC function (not shown) as a control station, and includes a downlink packet. The ROHC compression is transmitted to the base station 118 and the ROHC uplink packet is decompressed to the ROHC and transmitted to the CSN 102.

Here, the ROHC function unit is disposed together with the data path management unit 114, and includes a ROHC compression unit (not shown) and a ROHC decompression unit (not shown).

The service flow approval unit (SFA) 112 receives the ROHC policy from the AAA 104 or the PCRF 106. Then, a classification rule for ROHC is generated and distributed. In addition, the service flow management (SFM) of the base station 118 exchanges information of the service flow with the ROHC function unit 124 of the terminal 120.

If the terminal 120 accepts the service flow containing the ROHC classification, the service flow approval unit 112 performs the ROHC per-channel parameter negotiation after the procedure of the service flow negotiation. To start.

The service flow approval unit 112 generates service flow information of a service flow for ROHC packet transmission and reception, so that the ASN-GW 110, the base station 118, and the terminal 120 may obtain the service flow information. do.

The data path ID, which is a sub-TLV of the service flow information, includes a data path tag such as a general routing encapsulation key (GRE key) mapped with the service flow.

In addition, the service flow information includes ROHC parameters obtained through information exchange with the ROHC compression unit and the ROHC decompression unit of the ASN-GW 110. Here, the ROHC parameters include ROHC per-channel parameters, ROHC per-context parameters, profiles, contexts, ROHC context identifiers, and whether they apply ROHC. Classifier for may be included.

Therefore, before receiving the ROHC packet, the ASN-GW 110 and the terminal 120 include whether the service flow for receiving the ROHC packet is received through the service flow information and the ROHC context identifier mapped to the service flow. The ROHC parameter can be obtained and stored.

The ROHC function of the ASN-GW 110 initiates perchannel parameter negotiation with the ROHC function 124 in the terminal 120.

Perchannel parameter negotiation is achieved by ROHC compression and decompression units in the ASN-GW 110 and the terminal 120 negotiate the perchannel parameters. And, since the ROHC channel is mapped one-to-one with the service flow, the perchannel parameters are included in the service flow information, and a dynamic service addition (DSA) message (DSA-REQ / DSA-RSP) including the service flow information negotiates negotiation. Used for.

The ROHC compression unit of the ASN-GW 110 compresses the IP headers into a ROHC packet header that maintains the ROHC context, and the ROHC decompression unit maintains the header context and restores the compressed headers to the original header.

The data path management unit 114 (DPF) performs classification for downlink (DL) packets and checks whether ROHC is applied.

If the DL packets belong to the ROHC channel, the data path manager 114 forwards the DL packets to the ROHC compressor. Then, encapsulation of the R6 (data path between the terminal and the base station) data path tag is performed and transmitted to the base station 118 (B1).

The data path manager 114 receives an UpLink (UL) packet from the base station 118, and if the UL packets belong to the ROHC channel, forward the UL packet to the ROHC decompressor.

Base station 118 maintains a mapping relationship between the R6 data path tag and the connection identifier (802.16e CID). Then, DL packets are processed by replacing an R6 GRE key, which is an R6 data path tag, with an 802.16e CID, and UL packets are processed by replacing an 802.16e CID with an R6 GRE key.

If the DSA mesh includes the ROHC type, the MS 120 establishes a channel between the ROHC function 124 and the CS layer. If the DL packets belong to the ROHC channel, the DL packets are delivered to the ROHC decompression unit included in the ROHC function 124.

In addition, the terminal 120 performs classification to determine whether the ROHC is applied to the UL traffic. If the UL packet belongs to the ROHC channel, the terminal 120 performs ROHC compression. The UL packet is then sent to the base station 118 using the appropriate 802.16e CID mapped to the ROHC channel of the UL packet.

Hereinafter, a mapping relationship between a service flow for ROHC packet transmission and an ROHC context identifier will be described.

2 is a diagram illustrating a mapping relationship between a service flow and a ROHC context identifier for ROHC packet transmission and reception in a wireless communication system according to an embodiment of the present invention. Hereinafter, the service flow is mapped to the ROHC channel in a 1: 1 manner, and one ROHC channel may have an IP flow using multiple ROHCs. Here, the ROHC channel means a header compressed transmission channel to which the ROHC is applied.

As an example, a downlink packet that may have N kinds of IP flows 208 transmitted from the CSN 102 is described. First, the IP flow 208 and the service flow identifier (SFID) 202 may be N: 1 (N). Is a positive integer), and the ROHC context identifier 206 and IP flow 208 are mapped 1: 1.

In the ASN 108, the service flow identifier 202 is mapped 1: 1 to the ROHC channel 204, which is a logical channel. Here, ROHC channel 204 and ROHC context identifier 206 are mapped to 1: N. As a result, the service flow identifier 202 and the ROHC context identifier 206 are mapped to 1: N via the ROHC channel 204.

In addition, since the service flow identifier 202 is mapped 1: 1 to a connection identifier (Connection ID: 210) between the base station 118 and the terminal 120, the connection identifier 210 and the ROHC context identifier 206 are also illustrated in FIG. Mapped to N. Here, the aforementioned mapping relationship is equally applied to the ASN 108 or the terminal 120.

The above mapping relationship is recognized by the ASN 108 and the terminal 120 when generating a service flow for ROHC. In addition, the ASN-GW 118 and the terminal 120 may know whether to apply the ROHC to the packet with reference to the mapping relationship. And, the mapping relationship enables the ASN-GW, base station, or terminal to which the ROHC packet should be transmitted to be identified. The base station 118 and the terminal 120 obtain the mapping relationship through service flow information.

The service flow information may be a packet classification rule, an enhanced compressed RTP (ROHC / ECRTP) context identifier, a classifier type, or a CS parameter encoding rule as a sub TLV. It may include.

Whether to apply the ROHC is defined by a classifier type or a CS parameter encoding rule, and the ROHC context identifier 206 is defined by the ROHC / ECRTP context identifier. Accordingly, the ASN-GW 110 and the terminal 120 know whether the corresponding service flow is applied to the ROHC through the service flow information, and obtain the ROHC context identifier 206 mapped to the IP flow belonging to the corresponding service flow. .

In addition, the base station 118 obtains mapping information of the data path identifier (GRE key) and the connection identifier 210 corresponding to the service flow with reference to the service flow information.

In addition, the terminal 120 refers to the service flow information and the ROHC channel 204 including the connection identifier 210 and the ROHC context identifier 206 between the base station 118 and the terminal 120 corresponding to the service flow. Obtains the mapping information.

Through the above-described mapping information, the ASN-GW 110 may know whether to apply the ROHC to the received DL packet, and may know the base station 118 to transmit the ROHC packet after performing the ROHC compression. In addition, the base station 118 may know the terminal 120 to transmit the received ROHC packet. In addition, the terminal 120 knows whether the ROHC is applied to the received ROHC packet and performs ROHC decompression. The case of the UL packet may be described as an inverse process of the above-described process.

Referring back to FIG. 1, service flow information generated by the service flow approval unit 112 and including ROHC parameters such as whether the ROHC is applied and a ROHC context identifier is included in the data path setup request (Path_Reg_Req) message. Is transmitted from the GW 110 to the base station 118.

Thereafter, the service flow information may be included in the dynamic service addition (DSA-REQ) message from the base station 118 to the terminal 120 and transmitted. Here, the Path_Reg_Req message and the DSA-REQ message can include the service flow information in the TLV, so that the ROHC parameter can be transmitted.

In addition, service flow information including a predetermined ROHC parameter is transmitted from the terminal 120 to the ASN-GW 110 through a Path_Reg_Rsp message and a DSA-RSP message.

That is, the ASN-GW 110 and the UE 120 may perform ROHC negotiation by exchanging ROHC parameters through service flow information included in Path_Reg_Req / Rsp and DSA-REQ / RSP.

Hereinafter, with reference to FIGS. 3A and 3B, a description will be made of what TLV hierarchical structure the service flow information including the ROHC context identifier and the ROHC applied by the Path_Reg_Req / Rsp message and the DSA-REQ / RSP message have.

3A is a diagram illustrating a TLV layer structure of service flow information included in a message between an ASN-GW and a base station according to an embodiment of the present invention.

Service flow information (302a) may be included as a TLV in an ASN-GW and a base station message such as a Path_Reg_Req / Rsp message, and a packet classification rule 304a is included in the service flow information 302a. It may be included as a sub TLV.

The packet classification rule 304a may be included as a ROHC / ECRTP Context ID 304a and a Classifier 308a sub-TLV, and the classifier 308a includes a Classifier Type: 310a) may be included as a sub TLV.

Referring to FIG. 3A, ROHC header compression may be defined in the classifier type 310a, and the ROHC context identifier mapped to the service flow for ROHC packet transmission may be the ROHC / ECRTP context identifier 304a. Can be defined in

3B illustrates a TLV hierarchy structure of service flow information included in a message between a base station and a terminal according to an embodiment of the present invention.

In the message between the base station and the terminal, such as the DSA-REQ / RSP message, a service flow information (Serviceb) 302b may be included as a TLV, and the service flow information 302b includes a packet classification rule parameter 304b. ) And a CS Parameter Encoding Rule (308b) may be included as a sub TLV. In addition, the packet classification rule parameter 304b may include a ROHC / ECRTP context ID 306b as a sub-TLV.

Referring to FIG. 3B, whether ROHC is applied (ROHC header compression) may be defined by the CS parameter encoding rule 308b of the TLV, and the ROHC context identifier mapped to the service flow for the ROHC packet transmission is the ROHC / ECRTP. Defined by context identifier 306b.

In addition, the above-described service flow information 302b may have a sub TLV (not shown) including ROHC parameters other than ROHC application and ROHC context identifier.

Accordingly, through the service flow information 302b carried by the Path_Reg_Req / Rsp message and the DSA-REQ / RSP message and having the above-described TLV hierarchy, ROHC parameters such as the ROHC context identifier and whether the corresponding service flow is applied to the ROHC are determined. The ASN-GW 110 and the terminal 120 may be recognized before the ROHC packet transmission.

Referring back to FIG. 1, when the downlink packet is received from the CSN 102, the data path manager 114 classifies the downlink packet by determining whether to apply the ROHC.

When the service flow of the downlink packet uses ROHC packet transmission, the mapping information of the service flow identifier and the ROHC channel is previously stored in the data path manager 114. Therefore, whether to apply the ROHC of the downlink packet may be determined based on the mapping information of the service flow identifier and the ROHC channel.

In one embodiment, in the ROHC channel mapped to the ROHC context identifier N: 1, the data path management unit 114, through the mapping information of the service flow identifier and the ROHC channel identifier, the downlink packet is ROHC It can be determined whether transmission is required.

According to an embodiment, the mapping information is information generated when generating a service flow for ROHC, and entities 110, 118, and 120 of a wireless communication system using ROHC are service flow information (SF Info) transmitted and received in a service flow generation procedure for ROHC. ) May generate and maintain mapping information of the ROHC channel from the obtained information.

In a modified embodiment, whether to apply the ROHC of the downlink packet may be determined by referring to a packet classification rule which is a sub-TLV included in the service flow information of the downlink packet.

In one embodiment of the present invention, if it is determined that the downlink packet uses the ROHC channel, the data path manager 114 transmits the downlink packet to the ROHC compression unit of the ROHC function unit.

In addition, when the data path management unit 114 receives the ROHC downlink packet that is ROHC compressed from the ROHC compression unit of the ROHC function unit and adds the ROHC context identifier mapped to the IP flow of the downlink packet, the data path manager 114 transmits the ROHC downlink packet to the ROHC downlink packet. After performing an encapsulation process of adding a data path tag mapped to a service flow of a downlink packet, the encapsulation process is transmitted to the base station 118 mapped to the data path tag.

The data path tag is mapped 1: 1 with the service flow. Thus, if there are N types of ROHC context identifiers, the data path tag and the ROHC context identifier are mapped to 1: N. The mapping information of the data path tag and the service flow is information previously recognized by the ASN-GW 110 for the transmission of the ROHC packet.

In one embodiment, the data path tag may be a data path identifier included in service flow information of a service flow for transmitting the ROHC packet. In addition, the data path identifier may be a general routing encapsulation key (GRE Key).

In one embodiment, when the data path manager 114 classifies the downlink packet into a packet that does not require ROHC decompression, the data path manager 114 may transmit the downlink packet to the base station 118 without transmitting it to the ROHC compression unit.

The ROHC downlink packet is added to the data path tag and transmitted to the base station 118 through the tunnel between the ASN-GW 110 and the base station 118.

In addition, when the ROHC uplink packet is received from the base station 118, the data path manager 114 classifies the ROHC uplink packet by determining whether to apply the ROHC uplink packet.

The data path manager 114 determines a service flow that is added to the ROHC uplink packet and mapped to the received data path tag, and checks whether there is an ROHC channel mapped to the service flow through predetermined mapping information. If the corresponding ROHC channel is present, the ROHC uplink packet is de-capsulated and transmitted to the ROHC decompression unit.

The data path tag transmitted in addition to the uplink packet is mapped 1: 1 with the service flow of the ROHC uplink packet, and if there are N kinds of ROHC context identifiers, the data path tag and the ROHC context identifier are Can be mapped to 1: N. In addition, the mapping information is pre-stored in the data path manager 114.

In addition, the data path management unit 114 may transmit the uplink packet in which the header transmitted from the ROHC decompression unit is restored, to the CSN 102.

The ROHC compression unit ROHC compresses the downlink packet classified and transmitted from the data path management unit 114 and generates a ROHC downlink packet added with an ROHC context identifier mapped to the IP flow of the downlink packet, and then the data path management unit 114. To send).

The ROHC compression unit stores mapping information of the IP flow and the ROHC context identifier of the downlink packet and ROHC parameters corresponding to the IP flow. Then, a service flow generation request for the ROHC transmission is made to the service flow approval unit 112 so that the ROHC parameter is transmitted to the terminal 120 in the service flow information.

The ROHC decompression unit restores the header of the ROHC uplink packet classified and transmitted from the data path manager 114 using the pre-stored ROHC context identifier and transmits the header to the data path manager 114.

Here, the ROHC decompression unit obtains and stores a context corresponding to the ROHC context identifier through service flow information of an uplink packet. The header of the ROHC uplink packet is recovered through the context.

When the ROHC downlink packet to which the data path tag is added is transmitted, the base station 118 passes through the decapsulation process and transmits the ROHC downlink packet to the terminal 120 corresponding to the connection identifier mapped to the data path tag.

When the service flow uses ROHC packet transmission, a data path tag mapped to the service flow is received by the base station 118 via service flow information.

In addition, the data path tag and the connection identifier are mapped 1: 1, and this mapping information is maintained in the base station 118. Accordingly, the base station 118 can find the connection identifier mapped to the data path tag using the mapping information.

In addition, when the ROHC uplink packet is transmitted, the base station 118 performs an encapsulation process of adding a data path tag mapped to the service flow of the ROHC uplink packet, and the ASN-GW 110 mapped to the data path tag. To send.

The terminal 120 includes a ROHC function 124 and a data path manager (not shown).

The ROHC function unit 124 of the terminal 120 includes a ROHC compression unit (not shown) and a ROHC decompression unit (not shown).

When the CSA message contains the ROHC type, the terminal 120 establishes a channel between the ROHC functional entity and the Convergence Sublayer. If the downlink packet received by the terminal 120 belongs to the ROHC channel, the downlink packet is transmitted to the ROHC decompression unit of the ROHC function unit 124.

Terminal 120 performs classification to identify whether uplink packets require ROHC compression. The ROHC channel is then mapped to the appropriate connection identifier (802.16e CID) for transmission to base station 118.

Hereinafter, in the description related to the terminal 120 of FIG. 1, the data path management unit, the ROHC compression unit, and the ROHC decompression unit will be described as being components included in the terminal 120.

When the data path manager of the terminal 120 receives the ROHC downlink packet from the base station 118, the data path manager classifies the ROHC downlink packet by determining whether to apply the ROHC downlink packet.

The connection identifier mapped to the service flow of the ROHC downlink packet and the ROHC channel including the ROHC context identifier are mapped 1: 1, and this mapping information is maintained in the terminal 120. Therefore, the data path manager may determine whether the ROHC is applied to the ROHC downlink packet using the mapping information.

If there is the ROHC channel identifier mapped to the connection identifier of the ROHC downlink packet in the mapping information, the data path manager classifies the packet as a packet to which the ROHC is applied and transmits the packet to the ROHC decompression unit.

In addition, the data path management unit transmits the downlink packet whose header is recovered from the ROHC decompression unit to an IP layer which is a higher layer for IP classification.

When the data path management unit receives the uplink packet from the IP layer, which is the upper layer, the data path manager performs a classification procedure for determining whether to apply the ROHC to the uplink packet before transmitting it to the MAC layer.

The data path manager determines that ROHC packet transmission is used when the ROHC channel is mapped to the service flow of the uplink packet using the mapping information maintained. In a modified embodiment, whether to apply the ROHC may be determined as a CS parameter encoding rule that is a sub TLV in service flow information of the uplink packet.

When the data path manager determines that ROHC is applied to the uplink packet, the data path manager transmits the uplink packet to the ROHC compression unit.

In addition, when the data path manager receives the ROHC uplink packet from the ROHC compression unit, the data path manager transmits the ROHC uplink packet to the base station 118 corresponding to the connection identifier corresponding to the service flow of the uplink packet.

The service flow of the ROHC uplink packet and the connection identifier are mapped in a 1: 1, and this mapping information is maintained in the terminal 120. Therefore, the data path manager can find the connection identifier of the ROHC uplink packet using the mapping information.

The ROHC compression unit compresses the uplink packet classified and transmitted from the data path management unit, generates an ROHC uplink packet added with the ROHC context identifier mapped to the IP flow of the uplink packet, and transmits the uplink packet to the data path management unit.

The ROHC decompression unit reconstructs a header by using a previously stored ROHC context identifier for the ROHC downlink packet classified and transmitted from the data path management unit and transmits the header to the data path management unit.

Here, the ROHC decompressor stores the context corresponding to the ROHC context identifier and restores the header through the context.

Here, the ROHC decompression unit obtains and maintains the ROHC context identifier through the server flow information of the downlink packet, and performs ROHC decompression using the ROHC context identifier.

4A and 4B are flowcharts illustrating a method of processing a ROHC packet in a wireless communication system including a control station and a terminal having a ROHC compression unit and a ROHC decompression unit according to an embodiment of the present invention.

4A illustrates a method of processing an ROHC downlink packet when the control station and the terminal have a ROHC compression unit and a ROHC decompression unit.

First, when the anchor data path management unit (Anchor DP function) of the control station ASN-GW receives the downlink packet from the CSN toward the MS (S402a), the downlink packet is determined by a packet classification rule. A classification procedure for determining whether to apply the ROHC is performed (S404a).

In one embodiment, the ASN-GW refers to the mapping information of the ROHC channel identifier and the service flow identifier including the ROHC context identifier, and if there is an ROHC channel identifier mapped to the service flow identifier of the downlink packet, the ROHC is Can be classified as applicable. Here, the mapping information is information held by the ASN-GW.

When the ASN-GW determines to apply the ROHC, the ASN-GW transmits the downlink packet to the ROHC compression unit, and when it is determined that the ROHC is not applied, does not perform the ROHC compression.

Next, a downlink packet classified to be applied to the ROHC is compressed and an ROHC downlink packet added with an ROHC context identifier mapped to the IP flow of the downlink packet is generated (S406a). The ROHC context identifier is information held by the ROHC compression unit.

Next, the ASN-GW classifies the ROHC downlink packet according to a mapping table of a service flow identifier (SFID) and an ROHC channel identifier to determine a data path tag mapped to the service flow and a base station to transmit the ROHC downlink packet. (S408a). Here, the base station is a base station mapped to the data path tag. In addition, the data path tag may be a GRE key.

Since a tunnel with a data path tag as a key is created between the ASN-GW and the base station, when the data path tag is determined, the base station is determined.

Next, the ASN-GW adds the data path tag to the ROHC downlink packet and transmits the data path tag to the base station through the data path R6 (between base station and ASN-GW) / R4 (between ASN-GW and ASN-GW) (S410a). ).

Next, the base station decapsulates the ROHC downlink packet and identifies a connection identifier based on the data path tag (S412a).

The base station obtains mapping information of a data path tag and a connection identifier mapped to the service flow of the ROHC downlink packet through service flow information. And this mapping information is maintained at the base station. Accordingly, when the base station receives the ROHC downlink packet, the base station can find the correct connection identifier mapped to the data path tag using the mapping information.

Next, the ROHC downlink packet having the correct connection identifier is transmitted to the terminal (S414a). Here, the terminal corresponds to the connection identifier.

Subsequently, upon receiving the ROHC downlink packet (S416a), the terminal performs a classification procedure for determining whether to apply the ROHC to the ROHC downlink packet (S418a).

The UE may classify that the ROHC is applied to the ROHC downlink packet if the corresponding ROHC channel identifier exists by using the mapping information of the connection identifier and the ROHC channel identifier maintained.

Next, for the ROHC downlink packet classified to be applied to the ROHC, the header is restored by decompressing the ROHC downlink packet through the ROHC context identifier maintained by the ROHC decompressor (S420a).

Here, the determination of whether to apply the ROHC (S418a) process may be performed in the Convergence Sublayer (CS) of IEEE 802.16e for the ROHC downlink packet transmitted from the MAC / PHY layer, the ROHC decompression (S420a) process It can be executed at the IP or ROHC layer that is contacted through CS and Service Access Point (SAP).

Next, classify the IP version of the downlink packet whose header is restored or classify the IP version of the downlink packet which has not undergone the header restoring process (S422a). In operation S424a, the downlink packet is transmitted to a higher layer.

4B illustrates a method of processing an ROHC uplink packet when the control station and the terminal have a ROHC compression unit and a ROHC decompression unit.

First, when the terminal MS acquires an uplink packet (S402b), the data packet is transmitted from the upper layer of the terminal to the IP layer, the IP version of the uplink packet is classified (S404b), and the uplink packet A classification procedure for determining whether to apply the ROHC is performed (S406b). This is a classification for determining whether a packet will pass through an ROHC entity before delivering the data packet to the MAC layer. Here, the classification rule may be implemented in a shim layer or a ROHC layer between the IP layer and the ROHC layer.

The terminal may determine whether to apply the ROHC by referring to the service flow of the uplink packet obtained through the service flow generation procedure for the ROHC and mapping information of the ROHC channel.

Next, the ROHC compression unit of the terminal compresses the uplink packet classified as to which the ROHC is applied, and generates an ROHC uplink packet to which the ROHC context identifier mapped to the IP flow of the uplink packet is added (S408b). Here, the IP flow, the service flow, and the ROHC channel have a mapping relationship of N: 1: 1.

Next, in order to transmit the ROHC uplink packet, a classification procedure for identifying a correct connection identifier is performed (S410b). This is to perform the classification procedure again by determining the connection identifier for the ROHC compressed packet using the connection identifier (802.16e CID) and the mapping table of the ROHC channel in the CS.

Here, since the connection identifier is mapped 1: 1 with the service flow of the ROHC uplink packet, the connection identifier may be identified through the service flow identifier. If it is classified that no ROHC is applied, the connection identifier identification process S410b is performed without the compression process S408b.

Next, the ROHC uplink packet having the correct connection identifier is transmitted to the base station BS (S412b). Here, the base station corresponds to the connection identifier.

Next, the base station performs a classification procedure for determining the correct data path tag and ASN-GW for the received ROHC uplink packet (S414b). In one embodiment, the in-base station data path management unit (DPF) receives the data packet from the terminal, and performs the classification procedure (S414b).

The data path tag is delivered to the base station through service flow information and is mapped 1: 1 with the service flow of the ROHC uplink packet. The base station can find the data path tag by using the mapping information of the data path tag and the connection identifier which are maintained.

In addition, since a tunnel having a data path tag as a key is created between the ASN-GW and the base station, when the data path tag is determined, the ASN-GW is determined.

Next, the base station transmits the ROHC uplink packet having the data path tag to the ASN-GW (S416b). That is, the compressed packet having the data path tag is transmitted to the ASN-GW based on the 802.16e CID.

Subsequently, the control station ASN-GW performs a classification procedure for determining whether to apply ROHC to the ROHC uplink packet (S418b).

If the service flow identifier (SFID) of the compressed packet is mapped to the ROHC channel, the data packet is sent to the ROHC entity for decompression for decompression.

Subsequently, the ROHC decompressor decompresses the ROHC uplink packet through the ROHC context identifier to restore the header of the uplink packet (S420b).

Next, the ROHC decompressed uplink packet is transmitted to the CSN (S422b).

5 is a configuration diagram of a wireless communication system including a base station and a terminal having a ROHC compression unit and a ROHC decompression unit according to another embodiment of the present invention.

Referring to FIG. 5, a wireless communication system including a base station and a terminal having a ROHC compression unit and a ROHC decompression unit according to another embodiment of the present invention includes a CSN 102, an ASN 502, and a terminal 120. The CSN 102 transmits the ROHC downlink packet from the terminal 120 to the terminal 120, and transmits the ROHC uplink packet from the terminal 120 to the CSN 102.

Hereinafter, among the components shown in FIG. 5, components having functions overlapping with those shown in FIG. 1 will be omitted.

The ASN 502 includes an ASN-GW 504 serving as a control station and a base station (BS1) 510 that performs ROHC compression of downlink packets and ROHC decompression of uplink packets.

The ASN-GW 504 includes a service flow approval unit (SFA) 506 and a data path management unit (DPF) 508.

The service flow approval unit 506 may generate service flow information of a service flow for ROHC packet transmission, so that the ASN-GW 504, the base station 510, and the terminal 120 may obtain the service flow information. To be.

The data path identifier which is a sub TLV of the service flow information includes a data path tag such as a GRE key mapped with the service flow.

In addition, the service flow information includes ROHC parameters obtained by exchanging information with the ROHC compression unit and the ROHC decompression unit included in the ROHC function unit 514 of the base station 510. Here, the ROHC parameter may include a ROHC perchannel parameter, a ROHC percontext parameter, a profile, a context, a ROHC context identifier, and a classifier for whether the ROHC is applied.

Therefore, before receiving the ROHC packet, the base station 510 and the terminal 120 may acquire ROHC parameters by performing ROHC negotiation through the service flow information.

The service flow information including the ROHC parameter may be included in the Path_Reg_Req / Rsp message and transmitted between the ASN-GW 504 and the base station 510 in the process of generating a service flow for transmitting the ROHC packet, and the base station 510 and The terminal 120 may be included in the DSA-REQ message and transmitted. Here, the Path_Reg_Req / Rsp message and the DSA-REQ / RSP message may include the service flow information in the TLV, so that the ROHC parameter may be transmitted.

Whether the ROHC is applied and the ROHC context identifier may be included in the Path_Reg_Req / Rsp message and the DSA-REQ / RSP message by the service flow information having the TLV hierarchy shown in FIGS. 3A and 3B.

The data path management unit 508 of the ASN-GW 504 performs an encapsulation process of adding a data path tag mapped to a service flow of the downlink packet to a downlink packet transmitted from a CSN, and is mapped to the data path tag. Transmit to 510.

In this case, the data path tag mapped to the service flow is pre-stored in the ASN-GW 504, and a tunnel using the data path tag as a key is created between the ASN-GW 504 and the base station 510. Once the tag is selected, base station 510 is determined.

In addition, when an uplink packet is transmitted from the base station 510, the data path manager 508 decapsulates the uplink packet and transmits the uplink packet to the CSN 102.

The base station 510 includes a ROHC function 514 and a data path management unit (not shown), and transmits the downlink packet to the terminal 120 by ROHC compression, and decompresses the ROHC uplink packet by ROHC. Send to ASN-GW 504.

Here, the ROHC function unit 514 is disposed together with the data path management unit, and includes a ROHC compression unit (not shown) and a ROHC decompression unit (not shown).

The base station 510 transmits service flow information including the ROHC parameter to the terminal 102 so that the ROHC context identifier is stored in the terminal 120 and ROHC negotiation is performed.

Hereinafter, in the description related to the base station 510 of FIG. 5, the data path management unit, the ROHC compression unit, and the ROHC decompression unit will be described as being components included in the base station 510.

The data path management unit of the base station 510 decapsulates the downlink packet to which the data path tag is added, and performs a classification procedure for determining whether to apply ROHC.

The data path tag added to the downlink packet is mapped 1: 1 with the corresponding service flow, and the service flow and ROHC channel are also mapped 1: 1. Therefore, by using the ROHC channel and service flow mapping information maintained by the data path management unit, it is possible to determine whether to apply the ROHC to the downlink packet.

If the data path manager classifies that the ROHC is applied to the downlink packet, the data path manager transmits the downlink packet to the ROHC compression unit.

When the data path manager receives the ROHC downlink packet from the ROHC compression unit, the data path manager transmits the data to the terminal 120 corresponding to the connection identifier mapped to the data path tag.

The data path manager may maintain mapping information of the data path tag and the connection identifier and find the connection identifier by using the mapping information.

When the ROHC uplink packet is transmitted from the terminal 120, the data path manager determines whether to apply the ROHC to classify the ROHC uplink packet. If there is a ROHC channel mapped to the service flow corresponding to the connection identifier of the ROHC uplink packet, the ROHC is classified as applying the ROHC to the ROHC uplink packet and transmitted to the ROHC decompressor. Here, the mapping information of the ROHC channel and the service flow is information held by the base station.

In addition, when the data path manager receives the uplink packet from the ROHC decompressor, the data path manager performs an encapsulation process of adding a data path tag mapped to the connection identifier of the uplink packet to the uplink packet, and mapping the data path tag to the data path tag. To the ASN-GW 504.

Here, the mapping information of the connection identifier and the data path tag is information maintained by the data path manager, and the corresponding data path tag can be found using the mapping information.

In addition, since a tunnel having a data path tag as a key is generated between the ASN-GW 504 and the base station 510, when the data path tag is determined, the ASN-GW 504 is determined.

The ROHC compression unit compresses the downlink packet to generate an ROHC downlink packet, and delivers it to the data path management unit.

The ROHC decompression unit restores the header of the corresponding ROHC uplink packet through the ROHC context identifier and transfers the header to the data path manager.

The method of processing the ROHC downlink packet and the ROHC uplink packet in the terminal 120 is the same as described above with reference to FIG. 1 and will be omitted.

6A and 6B are flowcharts illustrating a method of processing a ROHC packet in a wireless communication system including a base station and a terminal having a ROHC compression unit and a ROHC decompression unit according to another embodiment of the present invention.

Hereinafter, the specific ROHC packet processing method not shown in each step of FIGS. 6A and 6B may be described in detail with reference to the ROHC packet processing methods of FIGS. 4A and 4B described above.

6A illustrates a method of processing an ROHC downlink packet when a base station and a terminal have a ROHC compression unit and a ROHC decompression unit.

First, when an anchor data path function of the control station ASN-GW receives a downlink packet from a CSN (S602a), it determines a data path tag for the downlink packet and a base station to transmit the downlink packet. A classification procedure is performed (S604a).

Next, the ASN-GW transmits a downlink packet having a data path tag to the determined base station (S606a). That is, the ASN-GW anchor data path management unit transmits a packet having a data path tag such as a GRE key to the base station through the R6 / R4 data path.

Subsequently, the base station determines whether to apply the ROHC to the downlink packet by classifying the IP flow according to a packet classification rule (S608a). By the packet classification rule, the base station can determine whether the ROHC is applied to the corresponding service flow.

Next, the ROHC compression unit of the base station compresses the downlink packet classified as to which the ROHC is applied, and generates an ROHC downlink packet to which the ROHC context identifier mapped to the IP flow of the downlink packet is added (S610a).

Next, the base station performs a classification procedure for determining a connection identifier mapped to the data path tag (S612a). Here, the base station performs a classification procedure for identifying the connection identifier by the mapping table of the connection identifier (802.16e CID) and the ROHC channel ID (ROHC Channel ID).

Subsequently, the ROHC downlink packet having the connection identifier is transmitted to the terminal (S614a). Here, the terminal corresponds to the connection identifier.

Subsequently, when the terminal receives the ROHC downlink packet (S616a), a classification procedure for determining whether to apply the ROHC is performed (S618a). In this case, the UE may classify the ROHC to the ROHC downlink packet if the ROHC channel identifier mapped to the corresponding service flow exists by using the mapping information between the service flow and the ROHC channel identifier maintained.

Next, when the ROHC is classified as applying, the header is restored by decompressing the ROHC downlink packet through a previously stored ROHC context identifier in the ROHC decompressor of the terminal (S620a).

Next, the IP version of the downlink packet to which the header is restored or the ROHC is not applied is classified (S622a), and the downlink packet is transmitted to a higher layer (S624a).

6B illustrates a method of processing an ROHC uplink packet when a base station and a terminal have a ROHC compression unit and a ROHC decompression unit.

First, when the terminal acquires an uplink packet (S602b), the upper layer of the terminal transmits the uplink packet to the IP layer to classify the IP of the uplink packet (S604b).

Then, before delivering the uplink packet to the MAC layer, a classification procedure for determining whether to apply ROHC is performed (S606b). Such a classification rule may be implemented in a shim layer or ROHC layer between the IP layer and the ROHC layer.

Next, if the ROHC is classified as applying, the ROHC compression unit of the terminal compresses the uplink packet and generates an ROHC uplink packet added with an ROHC context identifier mapped to the IP flow of the uplink packet (S608b).

Next, a connection identifier is determined to transmit the ROHC uplink packet to a base station (S610b). Here, the connection identifier is determined by a mapping table of the connection identifier and the ROHC channel identifier.

Next, the ROHC uplink packet is transmitted to the base station corresponding to the connection identifier (S612b).

Next, when the base station receives the ROHC uplink packet (S614b), the base station performs a classification procedure for determining whether to apply the ROHC to the received ROHC uplink packet (S616b). In response to receiving the ROHC uplink packet from the terminal, the data path manager DPF of the base station searches for a service flow identifier (SFID) to be mapped and determines whether the SFID is mapped to the ROHC channel. The DPF of the base station determines to apply the ROHC if there is a ROHC channel mapped to the SFID.

Next, if the ROHC is classified as being applied, the ROHC decompression unit of the base station decompresses the ROHC uplink packet through the pre-stored ROHC context identifier to restore the header of the uplink packet (S618b).

Subsequently, the base station performs a classification procedure for determining the data path tag and the ASN-GW based on the SFID (S620b). Here, the base station determines a pre-stored data path tag mapped to the connection identifier. The base station also determines the ASN-GW mapped to the selected data path tag.

Subsequently, the base station transmits an uplink packet having a data path tag such as a GRE key to the anchor ASN-GW through the R6 data path (S622b).

Next, when the uplink packet is received in the ASN-GW (S624b), the uplink packet is transmitted to the CSN (S626a).

Those skilled in the art to which the present invention pertains will understand that the present invention can be implemented in other specific forms without changing the technical spirit or essential features.

Therefore, it is to be understood that the embodiments described above are exemplary in all respects and not restrictive. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. do.

1 is a block diagram of a wireless communication system including a control station and a terminal having a ROHC compression unit and a ROHC decompression unit according to an embodiment of the present invention.

2 is a diagram illustrating a mapping relationship between a service flow and a ROHC context identifier for ROHC packet processing in a wireless communication system according to an embodiment of the present invention.

3A and 3B illustrate TLV hierarchical structures of service flow information included in an ASN-GW and a base station message and a base station and terminal message according to an embodiment of the present invention, respectively.

4A and 4B are flowcharts illustrating a method of processing a ROHC packet in a wireless communication system including a control station and a terminal having a ROHC compression unit and a ROHC decompression unit according to an embodiment of the present invention.

5 is a block diagram of a wireless communication system including a base station and a terminal having a ROHC compression unit and a ROHC decompression unit according to another embodiment of the present invention.

6A and 6B are flowcharts illustrating a method of processing a ROHC packet in a wireless communication system including a base station and a terminal having a ROHC compression unit and a ROHC decompression unit according to another embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

102: CSN 104: AAA

106: PCRF 108: ASN

110: ASN-GW 112: service flow approval unit

114: data path management unit 118: base station

120: terminal 124: ROHC function

Claims (35)

In the control station, when the service flow of the downlink packet is mapped to the header compression transport channel, a header compression context identifier (Context ID) mapped to the IP flow of the downlink packet to the first packet that compresses the header of the downlink packet. Acquiring a second packet added with; Adding a data path tag mapped to a service flow of the downlink packet to the second packet; And Transmitting a second packet to which the data path tag is attached to a base station that maintains mapping information of the data path tag and a connection identifier corresponding to the terminal, so that the second packet with the data path tag is transmitted to the terminal using the header compression transmission channel. step; Header compression packet processing method in a wireless communication system comprising a. The method of claim 1, Negotiating header compression parameters with the terminal such that the header compression transport channel is generated in the terminal. The method of claim 2, And the negotiation is performed using the service flow information of the downlink packet including the header compression context identifier and a classifier indicating whether to apply header compression. The method of claim 1, The data path tag mapped to the service flow is determined according to a service flow identifier (SFID) of the service flow and a channel identifier of the header compressed transport channel. At the control station, from the base station receiving the second packet with the header compression context identifier mapped to the first flow in which the header of the uplink packet is compressed to the IP flow of the uplink packet, from the base station to the connection identifier of the uplink packet. Receiving the second packet appended with a mapped data path tag; And If the service flow corresponding to the data path tag of the second packet is mapped to a header compressed transport channel including the header compressed transport identifier, the second packet is decompressed through the header compressed transport context identifier to decompress the uplink. Restoring a header of the link packet; Header compression packet processing method in a wireless communication system comprising a. The method of claim 5, And negotiating header compression parameters with the terminal such that a header compression transport channel including the header compression context identifier is created in the terminal. The method of claim 6, And the negotiation is performed using the service flow information of the uplink packet including the header compression context identifier and a classifier indicating whether to apply header compression. The method of claim 5, The service flow mapped to the header compression transport channel including the header compression transport identifier is determined according to the service flow identifier of the service flow and the channel identifier of the header compression transport channel. Treatment method. Receiving, at a base station, the downlink packet appended with a data path tag mapped to a service flow of the downlink packet from a control station; When the service flow of the downlink packet is mapped to a header compression transport channel, a second packet including a header compression context identifier mapped to the IP flow of the downlink packet is added to the first packet that compresses the header of the downlink packet. Obtaining; And Transmitting the second packet to the terminal corresponding to the connection identifier mapped to the data path tag to be transmitted to the terminal using the header compressed transmission channel; Header compression packet processing method in a wireless communication system comprising a. The method of claim 9, Negotiating header compression parameters with the terminal such that the header compression transport channel is generated in the terminal. The method of claim 10, And the negotiation is performed using the service flow information of the downlink packet including the header compression context identifier and a classifier indicating whether to apply header compression. Receiving, at the base station, a second packet having a header compression context identifier mapped to an IP flow of the uplink packet to a first packet having a header of an uplink packet compressed from the terminal; If the service flow corresponding to the connection identifier of the second packet is mapped to a header compression transport channel including the header compression context identifier, the second packet is decompressed through the header compression context identifier to decompress the uplink packet. Restoring the header; And Adding a data path tag mapped to the connection identifier to an uplink packet whose header is restored, and transmitting the data path tag to a control station mapped to the data path tag; Header compression packet processing method in a wireless communication system comprising a. The method of claim 12, And negotiating header compression parameters with the terminal such that a header compression transport channel including the header compression context identifier is created in the terminal. The method of claim 13, And the negotiation is performed using the service flow information of the uplink packet including the header compression context identifier and a classifier indicating whether to apply header compression. The method according to any one of claims 1 to 14, And a method of generating the first packet is a robust header compression (ROHC) method. The method according to any one of claims 1 to 14, The header compression context identifier has N types, but the service flow and the header compression context identifier are mapped to 1: N. The method according to any one of claims 1 to 14, The data path tag is a header compression packet processing method in a wireless communication system, characterized in that the data path identifier (Data Path ID) included in the service flow information of the service flow. The method of claim 17, And wherein the data path identifier is a generic routing encapsulation key (GRE Key). Performing ROHC compression on the data packet such that the service flow of the data packet and the ROHC channel are one-to-one mapping; And Transmitting the ROHC compressed data packet by adding a data path identifier mapped to the service flow. The method of claim 19, And wherein said one ROHC channel comprises a plurality of ROHC contexts. The method of claim 19, And the data path identifier is a GRE key. Performing ROHC compression on the data packet such that the service flow of the data packet and the ROHC channel are one-to-one mapping; And And transmitting the ROHC compressed data packet by adding a connection identifier mapped to the service flow. The method of claim 22, The connection identifier is a header compression packet processing method in a wireless communication system, characterized in that the connection identifier defined in the IEEE 802.16e standard. A header compression unit for generating a second packet including a first header context identifier mapped to an IP flow of the downlink packet to a first packet compressed a header of a downlink packet; If a fourth packet including a second header compression context identifier mapped to the IP flow of the uplink packet is transmitted to a third packet in which a header of an uplink packet is compressed, the second packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress an uplink packet to restore a header of the uplink packet; And Add the data path tag mapped to the service flow of the downlink packet to the second packet and transmit the data path tag to the base station mapped to the data path tag, and include the second header compression context identifier in the service flow of the uplink packet A data path manager for transmitting the fourth packet to the header decompressor when a header compression transport channel is mapped; The control station in a wireless communication system comprising a. The method of claim 24, The header compressing unit and the header decompressing unit negotiate header compression parameters with the terminal through service flow information of the downlink packet including whether the downlink packet applies header compression and the first header compression context identifier. A control station in a wireless communication system. The method of claim 25, And the service flow information of the downlink packet includes a packet classification rule including the first header compression context identifier as a sub type length value (TLV). The method of claim 24, And the header compression unit uses a robust header compression method. The method of claim 24, And the first header compression context identifier has N types, wherein the service flow of the downlink packet and the first header compression context identifier are mapped to 1: N. The method of claim 24, And the data path tag is a data path identifier included in service flow information of the downlink packet. A header compression unit for generating a second packet including a first header compression context identifier mapped to an IP flow of the downlink packet, to a first packet compressed a header of a downlink packet; When a fourth packet including a second header compression context identifier mapped to an IP flow of the uplink packet is transmitted to a third packet that compresses a header of an uplink packet, the fourth packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress a packet to restore a header of the uplink packet; And The second packet is transmitted to the terminal according to a connection identifier added to the downlink packet and mapped to a data path tag transmitted from a control station, and the service header of the uplink packet includes the second header compression context identifier. A data path manager for transmitting the fourth packet to the header decompressor when a header compressed transport channel is mapped; A base station in a wireless communication system comprising a. The method of claim 30, The header compression unit is a base station in a wireless communication system, characterized in that using the robust header compression method. The method of claim 30, Wherein the first header compression context identifier has N kinds, and the service flow of the downlink packet and the first header compression context identifier are mapped to 1: N. A header compression unit for generating a second packet including a first header compressed context header of an uplink packet and a first header compression context identifier mapped to an IP flow of the uplink packet; If a fourth packet including a second header compression context identifier mapped to an IP flow of the downlink packet is transmitted to a third packet in which a header of a downlink packet is compressed, the fourth packet is transmitted through the second header compression context identifier. A header decompressor configured to decompress a packet to restore a header of the downlink packet; And The second packet is transmitted to a base station mapped to a connection identifier corresponding to a service flow of the uplink packet. When the header compression transmission channel is mapped to the connection identifier of the downlink packet, the fourth packet is sent to the header decompressor. A data path manager for transmitting; Terminal in a wireless communication system comprising a. The method of claim 33, wherein The header compression unit is a terminal in a wireless communication system, characterized in that using the robust header compression method. The method of claim 33, wherein The first header compression context identifier has N types, and the service flow of the downlink packet and the first header compression context identifier are mapped to 1: N.

Images