BI-DIRECTIONAL PACKET DATA TRANSMISSION SYSTEM AND METHOD

Description

TECHNICAL FIELD

[0001] The present invention relates to a packet data transmission and, more particularly, to a packet data transmission method and system of a mobile communication system.

BACKGROUND ART

[0002] Recently, a mobile communication system has seen a remarkable development, but in terms of a large capacity data communication service, it is much behind the cable communication system. Countries throughout the world are developing a technique of IMT-2000 and actively cooperating for standardization of the technique.

[0003] A universal mobile telecommunications system (UMTS) is a third generation mobile communication system that has evolved from a standard known as Global System for Mobile communications (GSM). This standard is a European standard which aims to provide an improved mobile communication service based on a GSM core network and wideband code division multiple access (W-CDMA) technology.

[0004] In December, 1998, the ETSI of Europe, the ARIB/TTC of Japan, the T1 of the United States, and the TTA of Korea formed a Third Generation Partnership Project (3GPP) for the purpose of creating the specification for standardizing the UMTS.

[0005] The work toward standardizing the UMTS performed by the 3GPP has resulted in the formation of five technical specification groups (TSG), each of which is directed to forming network elements having independent operations.

[0006] More specifically, each TSG develops, approves and manages a standard specification in a related region. Among them, a radio access network (RAN) group (TSG-RAN) develops a specification for the function, items desired, and interface of a UMTS terrestrial radio access network (UTRAN), which is a new RAN for supporting a W-CDMA access technology in the UMTS.

[0007] Figure 1 illustrates an example of the construction of a general UMTS network.

[0008] As shown in Figure 1, the UMTS is roughly divided into a terminal, UTRAN 100 and a core network 200.

[0009] The UTRAN 100 includes one or more radio network sub-systems (RNS) 110 and 120. Each RNS 110 and 120 includes a radio network controller (RNC) 111 and plural Node Bs 112 and 113 managed by the RNC 111. The RNC performs functions which include assigning and managing radio resources, and operates as an access point with respect to the core network 200.

[0010] Node Bs 112 and 113 receive information sent by the physical layer of the terminal through an uplink, and transmit data to the terminal through a downlink. The Node Bs 112 and 113, thus, operate as access points of the UTRAN for the terminal.

[0011] The core network 200 includes a mobile switching center (MSC) 210 and a gateway mobile switching center (GMSC) 220 for supporting a circuit switched service, and a serving GPRS support node (SGSN) 230 and a gateway GPRS support node 240 for supporting a packet switched service.

[0012] The services provided to a specific terminal is roughly divided into the circuit switched service and the packet switched service. For example, a general voice phone call service belongs to the circuit switched service, while a Web browsing service through an Internet connection is classified as the packet switched service.

[0013] In case of supporting the circuit switched service, the RNC 111 is connected to the MSC 210 of the core network 200, and the MSC 210 is connected to the GMSC 220 managing a connection to other networks.

[0014] Meanwhile, in case of supporting the packet switched service, the RNC 111 provides a service in association with the SGSN 230 and the GGSN 240 of the core network 200. The SGSN 230 supports a packet communication going toward the RNC 111, and the GGSN 240 manages connection to other packet switched network such as the Internet network.

[0015] Various interfaces exist between network components to allow the network components to give and take information to and from each other for a mutual communication. An interface between the RNC 111 and the core network 200 is defined as an lu interface. Especially, an lu interface between packet switch-related systems of the RNC 111 and the core network 200 is defined as an lu-PS, and an lu interface between circuit switch-related systems of the RNC 111 and the core network 200 is defined as an lu-CS.

[0016] Figure 2 illustrates a structure of a radio interface protocol between the terminal and UTRAN 100 according to the 3GPP radio access network standards.

[0017] As shown in Figure 2, the radio interface protocol is vertically divided into a physical layer, a data link layer and a network layer, and is horizontally divided into a user plane (U-plane) for transmitting data signal and a control plane (C-plane) for transmitting a control signal.

[0018] The user plane is a region handling traffic information of a user such as a voice signal or an IP packet, while the control plane is a region handling control information such as an interface of a network or maintenance and management of a call.

[0019] In Figure 2, protocol layers can be divided into a first layer (L1), a second layer (L2), and a third layer (L3) based on three lower layers of an open system interconnection (OSI) standard model.

[0020] Functions of each protocol layer of Figure 2 will now be described.

[0021] The first layer (L1), that is, the physical layer, provides an information transfer service to a higher layer by using various radio transfer techniques.

[0022] The physical layer is connected to the MAC layer, a higher layer, through a transport channel, and the MAC layer and the physical layer transfer signals through the transport channel.

[0023] The second layer (L2) includes: an MAC layer, a radio link control

[0024] (RLC) layer and a packet data convergence protocol (PDCP) layer.

[0025] The MAC layer provides a re-allocation service of the MAC parameter for allocation and re-allocation of radio resources.

[0026] The MAC layer is connected to the radio link control (RLC) layer through a logical channel, and various logical channels are provided according to the kind of transmitted information.

[0027] In general, when information of the control plane is transmitted, a control channel is used. When information of the user plane is transmitted, a traffic channel is used.

[0028] The RLC layer supports a reliable data transmission and performs functions of segmentation and reassembly of an RLC service data unit (SDU) received from an upper layer.

[0029] When the RLC SDU is received from the higher layer, the RLC layer controls a size of each RLC SDU to be suitable to a process capacity, and adds header information thereto to generate a certain data unit. The thusly generated data unit is referred to as a protocol data unit (PDU) which is transferred to the MAC layer. The RLC layer includes an RLC buffer for storing the RLC SDU or the RLC PDU.

[0030] The packet data convergence protocol (PDCP) layer is a higher layer of the RLC layer. A data transmitted through a network protocol such as an IPv4(internet Protocol version 4) or an IPv6 (internet Protocol version 6) can be transmitted effectively on a radio interface with a relatively small band width by virtue of the PDCP layer.

[0031] For this purpose, the PDCP layer performs a function of reducing unnecessary control information used in the cable network, which is called a header compression, for which header compression schemes such as an RFC2507 or an RFC3095 (Robust Header Compression (ROHC)) defined by an Internet standardization group called an IETF (Internet Engineering Task Force) are used.

[0032] In these schemes, only information requisite for a header part of a data is transmitted, thereby reducing an amount of data to be transmitted. That is, unnecessary fields of the header are removed or a size of the header fields is reduced to reduce the amount of data of the header part.

[0033] An RRC (Radio Resource Control) layer is positioned at the lowest portion of the third layer. The RRC layer is defined only in the control plane and controls the transport channels and the physical channels in relation to the setup, the reconfiguration and the release of the radio bearers (RBs).

[0034] The RB service signifies a service provided by the second layer for data transmission between the terminal and UTRAN, and setting up of the RB means processes of stipulating the characteristics of a protocol layer and a channel, which are required for providing a specific service, and setting the respective detailed parameters and operation methods.

[0035] For reference, the RLC layer can be included in the user plane or in the control plane depending on which layer is connected at an upper position. If the RLC layer receives data from the RRC layer, the RLC layer belongs to the control plane, and otherwise, the RLC layer belongs to the user plane.

[0036] As shown in Figure 2, in case of the RLC layer and the PDCP layer, a plurality of entities can exist in one layer. This is because one terminal has a plurality of RBs, and generally one RLC entity (or only one PDCP entity) is used for one RB.

[0037] Figure 4 is a signal flow chart for implementing the header compression scheme in accordance with a conventional art, and Figure 5 illustrates a structure of a compressor and decompressor of the terminal and UTRAN.

[0038] An IP header compression scheme of the PDCP layer will now be described with reference to Figures 4 and 5.

[0039] First, referring to the RFC2507, different compression schemes are used depending on whether an upper protocol of the IP layer is TCP or not. That is, if an upper protocol of the IP layer is UDP, a compression scheme called 'compressed non-TCP' is used whereas if the upper protocol of the IP layer is TCP, a compression scheme called 'Compressed TCP' is used. The Compressed TCP is classified into a 'Compressed TCP' and a 'Compressed TCP nodelta' depending on a transmission method of a varied header field.

[0040] The 'Compressed TCP' scheme is a method that on the basis of the fact that variable header field values are not much different from each other among successive packets, only a difference between header fields values is transmitted, rather than transmitting the overall field value. Meanwhile, the 'Compressed TCP nodelta' scheme is a method of transmitting the overall varied field value as it is.

[0041] In the case of the 'Compressed TCP' scheme, a transmitting party first transmits an overall header packet for one packet stream to constitute a context both in the transmitting party and in a receiving party, and then uses a compression header indicating the difference from a previous packet to transmit the next packets. Meanwhile, the 'Compressed TCP nodelta' scheme is that the overall header field value as varied is transmitted.

[0042] Likewise, in the 'Compressed Non-TCP' scheme, the transmitting party first transmits an overall header packet for one packet stream to constitute a context both in the transmitting party and the receiving party, and transmits an overall header field value formed as a variable field for the next packets.

[0043] However, the 'Compressed Non-TCP' header compression scheme can be used for a uni-directional communication and adopts a compression slow-start method which transmits overall header information at exponentially increasing intervals. In the compression slow-start method, if the overall header information is changed or if a new header compression scheme is adopted, the same overall header is frequently transmitted at an initial stage and then a transmission interval is gradually widened. Figure 3 shows a concept of the compression slow-start method.

[0044] Parameters constituting the forms of the compressor and the decompressor should be defined to use the RFC2507 header compression scheme at the PDCP layer.

[0045] Defined in the RFC2507 header compression scheme are an F_MAX_PERIOD parameter indicating the number of compressed

[0046] Non-TCP header packets transmittable between full header packets transmitted exponent-repeatedly in the compression slow-start method, an F_MAX_TIME parameter indicating a compressed header packet transmission time between a time point when the latest full header packet has been transmitted and a time point when the next full header packet is to be transmitted, an MAX_HEADER parameter indicating the maximum size of a header usable for the header compression scheme, a TCP_SPACE parameter indicating the maximum number of contents usable for the 'Compressed TCP' scheme, a NON_TCP_SPACE parameter indicating the maximum number of contents used for the 'Compressed Non-TCP' scheme, and an EXPECTED-RECORDING parameter indicating whether re-sequential array is supported. The F_MAX_TIME parameter is used to inform a repetition period of the full header packet (refer to Figure 1).

[0047] The parameters are used to construct forms of the compressors 512 and 522 and the decompressors 511 and 521 of the terminal 410 and UTRAN 420 and defined in RFC2507, an IETF document of the RFC2507 header compression scheme.

[Table 1]

Information Element/Group name	Type and reference	Semantics description
>>>F_MAX_PERIOD	Integer (1..65535)	Largest number of compressed non-TCP headers that may be sent without sending a full header. Default value is 256.
>>>F_MAX_TIME	Integer (1..255) F_MAX_TIME	Compressed headers may not be sent more than seconds after sending last full header. Default value is 5.
>>>MAX_HEADER	Integer (60..65535)	The largest header size in octets that may be compressed. Default value is 168.
>>>TCP_SPACE	Integer (3.255)	Maximum CID value for TCP connections. Default value is 15.
>>>NON_TCP_SPACE	Integer (3..65535) Default	Maximum CID value for non-TCP connections. value is 15.
>>>EXPECT_REORDERING	Enumerated (reordering not expected, reordering expected)	Whether the algorithm shall reorder PDCP SDUs or not. Default value is "reordering not expected".

[0048] The header compression and decompression process adopting the RFC2507 header compression scheme will now be described.

[0049] First, the RRC layer 411 of the terminal 10 transfers capacity information to the RRC layer 421 of UTRAN 420. Then, the RRC layer 421 of UTRAN 420 allocates a memory resource required for header compression by referring to the capacity information. That is, the RRC layer 421 sets parameter values forming the compressors 512 and 522 and the decompressors 511 and 521.

[0050] For example, F_MAX_PERIOD is set to 256, F_MAX_TIME is set to 5, MAX_HEADER is set to 168, and NON_TCP_SPACE is set to 15.

[0051] When the parameter values are all set, the RRC layer 421 of UTRAN 420 transfers the set parameter values to the RRC layer 411 of the terminal 410.

[0052] As the parameter values reach the terminal 410, the RRC layer 411 of the terminal 410 and the RRC layer 421 of UTRAN 420 respectively transfer the set parameter values to respective PDCP layers 412 and 422. Then, a header compression performing layer included in the PDCP layers 412 and 422 forms the compressors 512 and 522 and the decompressors 511 and 521 on the basis of the received parameter values.

[0053] The ROHC (Robust Header Compression) scheme will now be described.

[0054] The ROHC scheme is commonly used to reduce header information of an RTP(Real-time Transport Protocol)/UDP (User Datagram Protocol)/IP(Intemet Protocol) packet. The RTP/UDP/IP packet, which means a packet with RTP, UDP and IP related headers which have been added to a user data while passing each layer, includes various header information required for transmitting data to a destination through the Internet.

[0055] The ROHC scheme is a header compression scheme based on the fact that each field value of packet headers of sequential packets belonging to one packet stream is almost the same. Thus, in the ROHC scheme, not the entire packet header field is transmitted but a variable field is transmitted.

[0056] For reference, an overall size of the header of the RTP/UDP/IP packet is 40 octet in case of IPv4 (Internet Protocol version 4) and 60 octet in case of IPv6 (internet Protocol version 6). Meanwhile, a pure data part (payload) usually has a size of 15~20 octet. That is, because the amount of control information is much greater than the amount of data to be actually transmitted, a transmission efficiency is quite low. Therefore, using the header compression schemes ensures a high transmission efficiency because the amount of control information is much reduced (in case of using the ROHC scheme, the size of the header is reduced by about 1 octet to 3 octet).

[0057] Like the RFC2507 header compression scheme, in order to use the ROHC scheme at the PDCP layer, parameters constituting the form of the compressor and the decompressor should be defined.

[0058] Parameters defined for the ROHC scheme includes a Max_CID parameter informing of the maximum number of contexts usable in the compressor, a profile parameter indicating what is the type of the IP packet used for a corresponding packet stream among RTP/UDP/IP, UDP/IP and ESP/IP, an MRRU (Maximum Reconstructed Reception Unit) parameter indicating whether an IP should be segmented and also indicating the maximum size of segments when they are reassembled after being segmented in the decompressor, a Packet_Sized_Allowed parameter informing of a size of a compression header packet supportable by the ROHC scheme, and a Reverse_Decompression_Depth parameter indicating whether a compressed packet has been re-attempted for decompression after the decompressor had failed to decompress it, and determining the number of re-attempts of decompression. These parameters are defined in the RFC3095, the IETF document of the ROHC scheme.

[0059] The header compression and decompression process adopting the ROHC scheme is the same as those of the RFC2507 header compression scheme as described above (refer to Figures 4 and 5).

[0060] For a communication to an uplink, the compressor 512 of the terminal 410 and the decompressor 521 of UTRAN 420 should have the same form, and for a communication to a downlink, the compressor 522 of UTRAN 420 and the decompressor 511 of the terminal 410 also should have the same form.

[0061] Because, the RRC layer 421 of UTRAN 420 sets the parameter values to form the compressor and the decompressor without discrimination of the uplink and the downlink, the compressors 512 and 522 and the decompressors 511 and 521 provided in the terminal 410 and UTRAN 420 have all the same forms.

[0062] In order to effectively provide a VoIP service and a streaming service and prevent consumption of radio resources, the UMTS system adopts the header compression scheme such as the RFC2507 header compression scheme or the ROHC scheme to compress a header from the original size of 40 bytes or 60 bytes to a size of 1~4 bytes and transmit it. For this purpose, the terminal 410 and UTRAN 420 should define parameters for forming the compressor and the decompressor.

[0063] Usually, the UMTS system also provides the streaming service in which the uplink and the downlink are asymmetrical as well as the VolP service in which the uplink and the downlink are symmetrical.

[0064] In this respect, however, the RRC layers 411 and 421 and the PDCP layers 412 and 422 sets a memory resource in consideration of only the transmission service in the uplink and downlink-symmetrical structure such as the VoIP (Voice over IP), so that the compressor and decompressor 512 and 521 of the uplink and the compressor and the decompressor 522 and 511 of the downlink have the same forms.

[0065] A problem of the conventional bi-directional packet data transmission system lies in that, the UMTS system allocates the same header compression-related memory resource to the uplink and the downlink even for the packet data transmission of the asymmetrical structure such as the streaming service.

[0066] The streaming service is a downlink-oriented service in which a packet data for a service requested by a user is transmitted through the downlink while reception information for the transmitted packet data is fed black through the uplink.

[0067] In terms of characteristics of the streaming service, the amount of the packet data transmitted to the downlink, is much greater than the amount of packet data transmitted to the uplink. Thus, the conventional bi-directional packet data transmission system is disadvantageous that the memory resources used for the header compression scheme are unnecessarily wasted and thus efficiency of the resources is degraded.

[0068] The above references are incorporated by reference herein where appropriate for appropriate teachings of additional or alternative details, features and/or technical background.

[0069] WO 02/25895 Al describes a method for defining a context identifier in a header filed compression when compressing header fields of data packets, a context is defined for a compressor and decompressor of data packet flow, wherein the context controls operation of said compressor and decompressor, wherein the context is identified by a context identifier, which is attached to the data packet and the length for a context identifier is defined by the data transfer between the compressor and the decompressor.

[0070] US 2002/0064164 describes a protocol header construction and/or removal for messages in wireless communications. A communication network includes a wireless core network, which is coupled to a packet data network and/or a public circuit switch network. The core network communicates over wireless links with mobile stations, which are capable of participated switch communication session in a packet switched communication sessions with another end point. To enhance spectral efficiency, protocol header associated with packet switched communications are not communicated with a bearer traffic. The protocol header are reconstructed at the receiving end based on configuration messages, which are exchanged between mobile stations and mobile wireless access systems.

DISCLOSURE OF THE INVENTION

[0071] Therefore: an object of the present invention is to provide a

[0072] bi-directional packet data transmission system and method capable of asymmetrically setting an uplink memory resource and a downlink memory resource. The object is solved by the features of the independent claims

[0073] To achieve at least the above objects in whole or in parts, there is provided a bi-directional packet data transmission system for a packet data transmission between a terminal and a radio access network, in which an uplink resource and a downlink resource are independently set.

[0074] Preferably, the resource is a memory resource.

[0075] Preferably, the memory resource is related to header compression.

[0076] Preferably, the memory resource hsa parameters required for header compression and decompression.

[0077] Preferably, an RRC layer of the radio access network sets resources to be different for uplink transmission and downlink transmission.

[0078] Preferably, a PDCP layer of the terminal forms a compressor by referring to received parameter values of the uplink and a decompressor by referring to received parameter values of downlink, and performs header compression and decompression.

[0079] Preferably, a PDCP layer of the radio access network forms a decompressor by referring to received parameter values of the uplink and a compressor by referring to received parameter values of downlink, and performs header compression and decompression.

[0080] To achieve at least these advantages in whole or in parts, there is further provided a bi-directional packet data transmission system for a packet data transmission between a terminal and a radio access network, including: setting an uplink resource and a downlink resource to be different; transferring the set resource to each PDCP layer of a terminal and a radio access network; and asymmetrically performing uplink and downlink transmission by using the received resource.

[0081] Preferably, in the resource setting step, parameters required for header compression and decompression are determined and sizes of the parameters are set.

[0082] Preferably, the asymmetrical transmission performing step includes: forming a compressor by referring to the received parameter values of uplink and a decompressor by referring to the received parameter values of downlink; and performing a packet transmission according to a header compression scheme by using the compressor and the decompressor.

[0083] Preferably, the asymmetrical transmission performing step includes: forming a decompressor by referring to the received parameter values of uplink and a compressor by referring to the received parameter values of downlink; and performing a packet transmission according to a header compression scheme by using the compressor and the decompressor.

[0084] Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objects and advantages of the invention may be realized and attained as particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0085] The invention will be described in detail with reference to the following drawings in which like reference numerals refer to like elements wherein:

Figure 1 illustrates a construction of a general UMTS network;

Figure 2 illustrates a structure of a radio interface protocol between a terminal and UTRAN on the basis of 3GPP radio access network standards;

Figure 3 illustrates a concept of a compression slow-start scheme;

Figure 4 is a signal flow chart for implementing a header compression scheme in accordance with a conventional art;

Figure 5 illustrates structures of compressors and decompressors of a terminal and UTRAN in accordance with the conventional art;

Figure 6 is a signal flow chart for implementing a header compression scheme in accordance with a preferred embodiment of the present invention; and

Figure 7 illustrates structures of compressors and decompressors of a terminal and UTRAN in accordance with the preferred embodiment of the present invention.

MODES FOR CARRYING OUT THE PREFERRED EMBODIMENTS

[0086] Figure 7 illustrates structures of compressors and decompressors of a terminal or mobile unit and UTRAN in accordance with the preferred embodiment of the present invention and shows transmission in an asymmetrical structure between an uplink and a downlink.

[0087] As shown in Figure 7, a compressor and a decompressor of the present invention have the same structures as those of the conventional art (refer to Figure 5).

[0088] The only difference of the present invention from the conventional art is that UTRAN 620 and a terminal 610 allocate a memory resource required for a header compression scheme to the uplink and the downlink in consideration of transmission that the uplink and downlink are asymmetrical as well as the transmission that uplink and downlink are symmetrical.

[0089] Figure 6 is a signal flow chart for implementing a header compression scheme in accordance with a preferred embodiment of the present invention.

[0090] As shown in Figure 6, a bi-directional packet data transmission system in accordance with a preferred embodiment of the present invention includes: UTRAN 620 for setting header compression-related parameter values required for uplink transmission and downlink transmission, and forming a compressor 722 and a decompressor 721; and a terminal 610 for transmitting the capacity information to UTRAN 620, receiving the set header compression-related parameter values from UTRAN 620 and forming a compressor 712 and a decompressor 711 by referring to the received parameter values.

[0091] UTRAN 620 includes an RRC layer 621 for setting the header compression-related parameter values required for uplink transmission and downlink transmission and transmitting the parameter values to an RRC layer 611 of the terminal and to its PDCP layer (622); and the PDCP layer 622 for forming the decompressor 721 used for uplink transmission and the compressor 722 used for downlink transmission, and performing a header compression and decompression.

[0092] The terminal 610 includes the RRC layer 611 for receiving the parameter values set by the RRC layer 621 of UTRAN 620 and transmitting the values to its PDCP layer 612; and the PDCP layer 621 for forming the compressor 712 used for uplink transmission and the decompressor 711 used for downlink transmission by referring to the received parameter values, and performing header compression and decompression; and a first and second memory spaces for the uplink and downlink data transmissions, respectively. The two memory spaces may be independent of each other.

[0093] The operation of the packet data transmission system will now be described.

[0094] To begin with, the RRC layer 611 of the terminal 610 transfers the 'capacity information' to the RRC layer 621 of UTRAN 620.

[0095] Then, the RRC layer 621 of UTRAN 620 discriminates capacity information of uplink and capacity information of downlink from the received capacity information. Subsequently, the RRC layer sets parameter values for forming the compressor 712 and the decompressor 721 of the uplink by referring the uplink capacity information and also sets parameter values for forming the compressor 722 and the decompressor 711 of downlink by referring to the downlink capacity information.

[0096] The parameter values are not necessarily set on the basis of capacity information of the terminal. They can be set according to a statistical calculation value previously set in UTRAN 620.

[0097] After the parameter values are completely set, the RRC layer 621 of UTRAN 620 transfers the set parameter values to the RRC layer 611 of the terminal 610. The RCC layer 621 can transfer the set parameters for either the compressor only (uplink), the decompressor only (downlink), or both.

[0098] As the set parameter values transferred to the terminal 610, the RRC layer 611 of the terminal 610 and the RRC layer of UTRAN 620 transfers the set parameter values to the PDCP layers 612 and 622. Then, each header compression performing layer included in the PDCP layers 612 and 622 forms the compressors 712 and 722 and the decompressors 711 and 721 by referring to the parameter values.

[0099] Specifically, the header compression performing layer of UTRAN 620 forms the decompressor 721 used for uplink transmission and the compressor 722 used for downlink transmission by referring to the parameter values, and the header compression performing layer of the terminal 610 forms the compressor 712 used for uplink transmission and the decompressor 711 used for downlink transmission by referring to the parameter values.

[0100] And then, the header compression performing layers of the terminal 610 and UTRAN 620 perform header compression and decompression according to a certain header compression scheme by using the compressors 712 and 722 and the decompressors 711 and 721.

[0101] As described above, in the bi-directional packet data transmission system in accordance with the preferred embodiment of the present invention, the compressor 722 and the decompressor 721 of the terminal 610 (or the form of the compressor 722 and the decompressor 721 of UTRAN 620) are constructed in a different form so that the header compression-related memory resources allocated to the uplink and the downlink are set different. The forms of the compressor and the decompressors 712, 721, 722 and 711 which have peer-to-peer relations are the same with each other.

[0102] The bi-directional packet data transmission system in accordance with the present invention performs the header compression and decompression by adopting the RFC2507 header compression scheme or the ROHC scheme.

[0103] First, in the case of adopting the RFC2507 header compression scheme for the bi-directional packet data transmission system, the compressor 712 of the terminal 610 performing the uplink communication and the decompressor 721 of UTRAN 620 are formed by an F_MAX_PERIOD parameter informing of a transmission period of an full header packet with respect to the compression slow-start scheme, an F_MAX_TIME parameter informing of packet transmission available time, a MAX_HEADER parameter informing of the maximum compressible size of a header, a TCP_SPACE parameter informing of the maximum size of a TCP packet context, and a NON_TCP_SPACE parameter informing of the maximum size of non-TCP packet context.

[0104] The compressor 722 of UTRAN performing the downlink communication and the decompressor 711 of the terminal 610 are formed by a TCP_SPACE parameter informing of the maximum size of TCP packet context, a NON_TCP SPACE parameter informing of the maximum size of the non-TCP packet context, and an EXPECTED_REORDERING parameter informing of a re-sequential array of a reception packet.

[0105] Second, in the case of adopting the ROHC scheme for the bi-directional packet data transmission system, the compressor 712 of the terminal 610 performing the uplink communication and the decompressor 721 of UTRAN 620 are formed by a Max-CID parameter informing of the maximum number of contexts used for the header compression scheme, a profile parameter informing of a kind of an IP packet supportable by the decompressor, an MRRU parameter informing whether an IP packet can be segmented in the compressor, and a Packet_Sized_Allowed parameter determining sizes of compression header packets usable in the compressor.

[0106] In addition, the compressor 722 of UTRAN 620 performing the downlink communication and the decompressor 711 of the terminal 610 are formed by a Max_CID parameter informing of the maximum number of contexts, a profile parameter informing of a kind of an IP packet supported by the decompressor, an MRRU parameter informing of the maximum size of added packets when divided segments are added in the decompressor, and a Reverse_Decompression_Depth parameter informing of the maximum storage size of a buffer which stores a decompression-failed packet.

[0107] As so far described, the packet data transmission method and system of the present invention has the following advantages.

[0108] That is, because the memory resources are set to be different for the uplink and downlink transmission, waste of the memory resource can be prevented. In addition, the memory resource can be effectively managed even in a packet data transmission service (e.g., the streaming service) with the asymmetrical structure that the packet amount of the downlink is much greater than the packet amount of the uplink, or the packet amount of the uplink is much greater than the packet amount of the downlink.

[0109] The foregoing embodiments and advantages are merely exemplary and are not to be construed as limiting the present invention. The present teaching can be readily applied to other types of apparatuses. The description of the present invention is intended to be illustrative, and not to limit the scope of the claims. Many alternatives, modifications, and variations will be apparent to those skilled in the art. In the claims, means-plus-function clauses are intended to cover the structure described herein as performing the recited function and not only structural equivalents but also equivalent structures.

Claims

1. A radio access network (20) for a data transmission system using data packets and comprising at least a terminal (10), the radio access network being configured:

to receive terminal capacity information from the terminal;

to set uplink parameter information for a header compressor (712) of the terminal;

to set downlink parameter information for a header decompressor (711) of the terminal; and

to transmit the uplink parameter information and the downlink parameter information to the terminal;

wherein the radio access network is configured to set independently the uplink parameter information for the header compressor of the terminal and the downlink parameter information for the header decompressor of the terminal based on the received terminal capacity information.

2. The radio access network according to claim 1, further configured for setting different parameter information for the header compressor of the terminal and for the header decompressor of the terminal.

3. The radio access network according to any one of claims 1 and 2, wherein the uplink parameter information and the downlink parameter information include memory space information.

4. The radio access network according to any one of claims 1 to 3, wherein the uplink parameter information and the downlink parameter information are related to a header compression scheme.

5. The radio access network according claim 4, wherein the header compression scheme is a RFC3095 compression scheme.

6. The radio access network according to claim 4, wherein the header compression scheme is a RFC2507 compression scheme.

7. The radio access network according to any one of claims 1 to 6, wherein the an amount of downlink transmission packets is greater than an amount of uplink transmission packets.

8. The radio access network according to any one of claims 1 to 6, wherein the an amount of downlink transmission packets is less than an amount of uplink transmission packets.

9. The radio access network according to any one of claims 1 to 8, wherein the downlink parameter information and the uplink parameter information are also set according to a statistical calculation previously set in the radio access network.

10. The radio access network according to any one of claims 1 to 9, wherein the uplink parameter information comprises at least one uplink parameter value and the downlink parameter information comprises at least one downlink parameter value.

11. The radio access network according to any one of claims 1 to 10, wherein the uplink parameter information comprises a parameter representing a maximum number of contexts used for the header compressor of the terminal (MAX_CID) and the downlink parameter information comprises a parameter representing a maximum number of contexts used for the header decompressor of the terminal (MAX_CID).

12. The radio access network according to any one of claims 1 to 11, wherein the downlink parameter information comprises a parameter representing a maximum storage size of a buffer which stores a decompression-failed packet (Reverse Decompression Depth).

13. The radio access network according to any one of claims 1 to 12, wherein the uplink parameter information comprises a parameter representing sizes of compression header packets usable in the header compressor (Packet_Sized_Allowed).

14. A method of communicating from a radio access network (20) to a terminal (10) in a data transmission system, comprising, carried out in the radio access network:

receiving terminal capacity information from the terminal;

setting uplink parameter information for a header compressor (712) of the terminal;

setting downlink parameter information for a header decompressor (711) of the terminal; and

transferring the uplink parameter information and the downlink parameter information to the terminal;

wherein the uplink parameter information for the header compressor of the terminal and the downlink parameter information for the header decompressor of the terminal are set independently and are based on the received terminal capacity information.

15. The method according to claim 14, wherein the uplink parameter information for the header compressor of the terminal and the downlink parameter information for the header decompressor of the terminal are different from each other.

16. The method according to any one of claims 14 and 15, wherein the uplink parameter information and the downlink parameter information include memory space information.

17. The method according to any one of claims 14 to 16, wherein the uplink parameter information and the downlink parameter information are related to a header compression scheme.

18. The method according to claim 17, wherein the header compression scheme is a RFC3095 compression scheme.

19. The method according to claim 17, wherein the header compression scheme is a RFC2507 compression scheme.

20. The method according to any one of claims 14 to 19, wherein an amount of downlink transmission packets is greater than an amount of uplink transmission packets.

21. The method according to any one of claims 14 to 19, wherein an amount of downlink transmission packets is less than an amount of uplink transmission packets.

22. The method according to any one of claim 14 to 21, wherein the downlink parameter information and the uplink parameter information are also set according to a statistical calculation previously set in the radio access network.

23. The method according to any one of claims 14 to 22, wherein the uplink parameter information comprises at least one uplink parameter value and the downlink parameter information comprises at least one downlink parameter value.

24. The method according to any one of claims 14 to 23, wherein the uplink parameter information comprises a parameter representing a maximum number of contexts used for the header compressor of the terminal (MAX_CID) and the downlink parameter information comprises a parameter representing a maximum number of contexts used for the header decompressor of the terminal (MAX_CID).

25. The method according to any one of claims 14 to 24, wherein the downlink parameter information comprises a parameter representing a maximum storage size of a buffer which stores a decompression-failed packet (Reverse Decompression Depth).

26. The method according to any one of claims 14 to 25, wherein the downlink parameter information comprises a parameter representing sizes of compression header packets usable in the header compressor (Packet_Sized_Allowed).

27. A terminal (10) to be used in a data transmission system using data packets, the terminal comprising a header compressor (712) and a header decompressor (711) and being configured
for transmitting to a radio access network (20) terminal capacity information; for receiving, from the radio access network, uplink parameter information and downlink parameter information; and
for using the uplink parameter information for the header compressor (712) and the downlink parameter information for the header decompressor (711),
wherein the uplink parameter information for the header compressor and the downlink parameter information for the header decompressor are independent one from another and are based on the terminal capacity information.

28. The terminal according to claim 27, wherein the uplink parameter information for the header compressor and the downlink parameter information for the header decompressor are different from each other.

29. The terminal to any one of claims 27 and 28, wherein the uplink parameter information and the downlink parameter information include memory space information.

30. The terminal according to any one of claims 27 to 29, wherein the uplink parameter information and the downlink parameter information are related to a header compression scheme.

31. The terminal according claim 30, wherein the header compression scheme is a RFC3095 compression scheme.

32. The terminal according claim 30, wherein the header compression scheme is a RFC2507 compression scheme.

33. The terminal according to any one of claims 27 to 32, wherein an amount of downlink transmission packets is greater than an amount of uplink transmission packets.

34. The terminal according to any one of claims 27 to 32, wherein an amount of downlink transmission packets is less than an amount of uplink transmission packets.

35. The terminal according to any one of claims 27 to 34, wherein the downlink parameter information and the uplink parameter information are also set according to a statistical calculation previously set in the radio access network.

36. The terminal according to any one of claims 27 to 35, wherein the uplink parameter information comprises at least one uplink parameter value and the downlink parameter information comprises at least one downlink parameter value.

37. The terminal according to any one of claims 27 to 36, wherein the uplink parameter information comprises a parameter representing a maximum number of contexts used for the header compressor (MAX_CID) and the downlink parameter information comprises a parameter representing a maximum number of contexts used for the header decompressor (MAX_CID).

38. The terminal according to any one of claims 27 to 37, wherein the downlink parameter information comprises a parameter representing a maximum storage size of a buffer which stores a decompression-failed packet (Reverse Decompression Depth).

39. The terminal according to any one of claims 27 to 38, wherein the uplink parameter information comprises a parameter representing sizes of compression header packets usable in the header compressor (Packet_Sized_Allowed).

40. A method for communicating between a terminal (10) and a radio access network (20) of a data transmission system, comprising:

transmitting terminal capacity information to the radio access network;

receiving uplink parameter information and downlink parameter information from the radio access network;

forming a header compressor (712) according to the received uplink parameter information; and

forming a header decompressor (711) according to the received downlink parameter information,

wherein the uplink parameter information for the header compressor and the downlink parameter information for the header decompressor are independent one from another and are based on the terminal capacity information.

41. The method of claim 40, wherein the uplink parameter information for the header compressor and the downlink parameter information for the header decompressor are different from each other.

42. The method according to any one of claims 40 and 41, wherein the uplink parameter information and the downlink parameter information include memory space information.

43. The method according to any one of claims 40 to 41, wherein the uplink parameter information and the downlink parameter information are related to a header compression scheme.

44. The method according to claim 43, wherein the header compression scheme is a RFC3095 compression scheme.

45. The method according to claim 43, wherein the header compression scheme is a RFC2507 compression scheme.

46. The method according to any one of claims 40 to 45, wherein an amount of downlink transmission packets is greater than the an amount of uplink transmission packets.

47. The method according to any one of claims 40 to 45, wherein an amount of downlink transmission packets is less than an amount of uplink transmission packets.

48. The method according to any one of claims 40 to 47, wherein the downlink parameter information and the uplink parameter information are also set according to a statistical calculation previously set in the radio access network.

49. The method according to any one of claims 40 to 48, wherein the uplink parameter information comprises at least one uplink parameter value and the downlink parameter information comprises at least one downlink parameter value.

50. The method according to any one of claims 40 to 49, wherein the uplink parameter information comprises a parameter representing a maximum number of contexts used for the header compressor (MAX_CID) and the downlink parameter information comprises a parameter representing a maximum number of contexts used for the header decompressor (MAX_CID.

51. The method according to any one of claims 40 to 50, wherein the downlink parameter information comprises a parameter representing a maximum storage size of a buffer which stores a decompression-failed packet (Reverse Decompression Depth).

52. The method according to any one of claims 40 to 51, wherein the uplink parameter information comprises a parameter representing sizes of compression header packets usable in the header compressor (Packet_Sized_Allowed).

Ansprüche

1. Funkzugangsnetz (20) für ein Datenübertragungssystem, das Datenpakete verwendet und mindestens ein Endgerät (10) umfasst, wobei das Funkzugangsnetz dazu ausgestaltet ist:

eine Endgerät-Kapazitätsinformation vom Endgerät zu empfangen;

eine Uplink-Parameterinformation für einen Header-Komprimierer (712) des Endgeräts festzusetzen;

eine Downlink-Parameterinformation für einen Header-Dekomprimierer (711) des Endgeräts festzusetzen; und

die Uplink-Parameterinformation und die Downlink-Parameterinformation an das Endgerät zu übertragen;

wobei das Funkzugangsnetz dazu eingerichtet ist, unabhängig die Uplink-Parameterinformation für den Header-Komprimierer des Endgeräts und die Downlink-Parameterinformation für den Header-Dekomprimierer des Endgeräts basierend auf der empfangenen Endgerät-Kapazitätsinformation festzusetzen.

2. Funkzugangsnetz nach Anspruch 1, ferner dazu eingerichtet, unterschiedliche Parameterinformation für den Header-Komprimierer des Endgeräts und für den Header-Dekomprimierer des Endgeräts festzusetzen.

3. Funkzugangsnetz nach einem der Ansprüche 1 und 2, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation eine Speicherplatz-Information enthalten.

4. Funkzugangsnetz nach einem der Ansprüche 1 bis 3, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation einem Header-Komprimierschema entsprechen.

5. Funkzugangsnetz nach Anspruch 4, wobei das Header-Komprimierschema ein RFC3095 Komprimierschema ist.

6. Funkzugangsnetz nach Anspruch 4, wobei das Header-Komprimierschema ein RFC2507 Komprimierschema ist.

7. Funkzugangsnetz nach einem der Ansprüche 1 bis 6, wobei eine Downlink-Übertragungspaketmenge größer ist als eine Uplink-Übertragungspaketmenge.

8. Funkzugangsnetz nach einem der Ansprüche 1 bis 6, wobei eine Downlink-Übertragungspaketmenge geringer ist als eine Uplink-Übertragungspaketmenge.

9. Funkzugangsnetz nach einem der Ansprüche 1 bis 8, wobei die Downlink-Parameterinformation und die Uplink-Parameterinformation auch entsprechend einer statistischen Berechnung festgesetzt sind, die zuvor im Funkzugangsnetz festgesetzt worden ist.

10. Funkzugangsnetz nach einem der Ansprüche 1 bis 9, wobei die Uplink-Parameterinformation mindestens einen Uplink-Parameterwert umfasst und die Downlink-Parameterinformation mindestens einen Downlink-Parameterwert umfasst.

11. Funkzugangsnetz nach einem der Ansprüche 1 bis 10, wobei die Uplink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Komprimierer des Endgeräts verwendet werden, und wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten darstellt (MAX_CID), die für den Header-Dekomprimierer des Endgeräts verwendet werden.

12. Funkzugangsnetz nach einem der Ansprüche 1 bis 11, wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Speichergröße eines Zwischenspeichers darstellt, der ein Paket mit fehlgeschlagener Dekomprimierung speichert (umgekehrte Dekomprimiertiefe).

13. Funkzugangsnetz nach einem der Ansprüche 1 bis 12, wobei die Uplink-Parameterinformation einen Parameter umfasst, der Größen von Kompressionsheader-Paketen darstellt, die im Header-Komprimierer verwendbar sind (erlaubte Paketgröße).

14. Verfahren zum Herstellen einer Verbindung von einem Funkzugangsnetz (20) zu einem Endgerät (10) in einem Datenübertragungssystem, umfassend die im Funkzugangsnetz ausgeführten Schritte:

Empfangen einer Endgerät-Kapazitätsinformation vom Endgerät;

Festsetzen einer Uplink-Parameterinformation für einen Header-Komprimierer (712) des Endgeräts;

Festsetzen einer Downlink-Parameterinformation für einen Header-Dekomprimierer (711) des Endgeräts; und

Übertragen der Uplink-Parameterinformation und der Downlink-Parameterinformation zum Endgerät;

wobei die Uplink-Parameterinformation für den Header-Komprimierer des Endgeräts und die Downlink-Parameterinformation für den Header-Dekomprimierer des Endgeräts unabhängig festgesetzt sind und auf der empfangenen Endgerät-Kapazitätsinformation basieren.

15. Verfahren nach Anspruch 14, wobei die Uplink-Parameterinformation für den Header-Komprimierer des Endgeräts und die Downlink-Parameterinformation für den Header-Dekomprimierer des Endgeräts voneinander verschieden sind.

16. Verfahren nach einem der Ansprüche 14 und 15, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation eine Speicherplatz-Information enthalten.

17. Verfahren nach einem der Ansprüche 14 bis 16, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation einem Header-Komprimierschema entsprechen.

18. Verfahren nach Anspruch 17, wobei das Header-Komprimierschema ein RFC3095 Komprimierschema ist.

19. Verfahren nach Anspruch 17, wobei das Header-Komprimierschema ein RFC2507 Komprimierschema ist.

20. Verfahren nach einem der Ansprüche 14 bis 19, wobei eine Downlink-Übertragungspaketmenge größer ist als eine Uplink-Übertragungspaketmenge.

21. Verfahren nach einem der Ansprüche 14 bis 19, wobei eine Downlink-Übertragungspaketmenge geringer ist als eine Uplink-Übertragungspaketmenge.

22. Verfahren nach einem der Ansprüche 14 bis 21, wobei die Downlink-Parameterinformation und die Uplink-Parameterinformation auch entsprechend einer statistischen Berechnung festgesetzt werden, die zuvor im Funkzugangsnetz festgesetzt wird.

23. Verfahren nach einem der Ansprüche 14 bis 22, wobei die Uplink-Parameterinformation mindestens einen Uplink-Parameterwert umfasst und die Downlink-Parameterinformation mindestens einen Downlink-Parameterwert umfasst.

24. Verfahren nach einem der Ansprüche 14 bis 23, wobei die Uplink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Komprimierer des Endgeräts verwendet werden, und die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Dekomprimierer des Endgeräts verwendet werden.

25. Verfahren nach einem der Ansprüche 14 bis 24, wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Speichergröße eines Zwischenspeichers darstellt, der ein Paket mit fehlgeschlagener Dekomprimierung speichert (umgekehrte Dekomprimiertiefe).

26. Verfahren nach einem der Ansprüche 14 bis 25, wobei die Downlink-Parameterinformation einen Parameter umfasst, der Größen von Kompressionsheader-Paketen darstellt, die im Header-Komprimierer verwendbar sind (erlaubte Paketgröße).

27. Endgerät (10) zur Verwendung in einem Datenübertragungssystem, das Datenpakete verwendet, wobei das Endgerät einen Header-Komprimierer (712) und einen Header-Dekomprimierer (711) umfasst und dazu eingerichtet ist:

eine Endgerät-Kapazitätsinformation an ein Funkzugangsnetz (20) zu übertragen;

eine Uplink-Parameterinformation und eine Downlink-Parameterinformation vom Funkzugangsnetz zu empfangen; und

die Uplink-Parameterinformation für den Header-Komprimierer (712) und die Downlink-Parameterinformation für den Header-Dekomprimierer (711) zu verwenden,

wobei die Uplink-Parameterinformation für den Header-Komprimierer und die Downlink-Parameterinformation für den Header-Dekomprimierer voneinander unabhängig sind und auf der Endgerät-Kapazitätsinformation basieren.

28. Endgerät nach Anspruch 27, wobei die Uplink-Parameterinformation für den Header-Komprimierer und die Downlink-Parameterinformation für den Header-Dekomprimierer voneinander verschieden sind.

29. Endgerät nach einem der Ansprüche 27 und 28, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation eine Speicherplatz-Information enthalten.

30. Endgerät nach einem der Ansprüche 27 bis 29, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation einem Header-Komprimierschema entsprechen.

31. Endgerät nach Anspruch 30, wobei das Header-Komprimierschema ein RFC3095 Komprimierschema ist.

32. Endgerät nach Anspruch 30, wobei das Header-Komprimierschema ein RFC2507 Komprimierschema ist.

33. Endgerät nach einem der Ansprüche 27 bis 32, wobei eine Downlink-Übertragungspaketmenge größer ist als eine Uplink-Übertragungspaketmenge.

34. Endgerät nach einem der Ansprüche 27 bis 32, wobei eine Downlink-Übertragungspaketmenge geringer ist als eine Uplink-Übertragungspaketmenge.

35. Endgerät nach einem der Ansprüche 27 bis 34, wobei die Downlink-Parameterinformation und die Uplink-Parameterinformation auch entsprechend einer statistischen Berechnung festgesetzt sind, die zuvor im Funkzugangsnetz festgesetzt worden ist.

36. Endgerät nach einem der Ansprüche 27 bis 35, wobei die Uplink-Parameterinformation mindestens einen Uplink-Parameterwert umfasst und die Downlink-Parameterinformation mindestens einen Downlink-Parameterwert umfasst.

37. Endgerät nach einem der Ansprüche 27 bis 36, wobei die Uplink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Komprimierer verwendet werden, und wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Dekomprimierer verwendet werden.

38. Endgerät nach einem der Ansprüche 27 bis 37, wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Speichergröße eines Zwischenspeichers darstellt, der ein Paket mit fehlgeschlagener Dekomprimierung speichert (umgekehrte Dekomprimiertiefe).

39. Endgerät nach einem der Ansprüche 27 bis 38, wobei die Uplink-Parameterinformation einen Parameter umfasst, der Größen von Kompressionsheader-Paketen darstellt, die im Header-Komprimierer verwendbar sind (erlaubte Paketgröße).

40. Verfahren zum Herstellen einer Verbindung zwischen einem Endgerät (10) und einem Funkzugangsnetz (20) eines Datenübertragungssystems, umfassend:

Übertragen einer Endgerät-Kapazitätsinformation an das Funkzugangsnetz;

Empfangen einer Uplink-Parameterinformation und einer Downlink-Parameterinformation vom Funkzugangsnetz;

Bilden eines Header-Komprimierers (712) entsprechend der empfangenen Uplink-Parameterinformation; und

Bilden eines Header-Dekomprimierers (711) entsprechend der empfangenen Downlink-Parameterinformation;

wobei die Uplink-Parameterinformation für den Header-Komprimierer und die Downlink-Parameterinformation für den Header-Dekomprimierer unabhängig voneinander sind und auf der Endgerät-Kapazitätsinformation basieren.

41. Verfahren nach Anspruch 40, wobei die Uplink-Parameterinformation für den Header-Komprimierer und die Downlink-Parameterinformation für den Header-Dekomprimierer voneinander verschieden sind.

42. Verfahren nach einem der Ansprüche 40 und 41, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation eine Speicherplatz-Information enthalten.

43. Verfahren nach einem der Ansprüche 40 bis 41, wobei die Uplink-Parameterinformation und die Downlink-Parameterinformation einem Header-Komprimierschema entsprechen.

44. Verfahren nach Anspruch 43, wobei das Header-Komprimierschema ein RFC3095 Komprimierschema ist.

45. Verfahren nach Anspruch 43, wobei das Header-Komprimierschema ein RFC2507 Komprimierschema ist.

46. Verfahren nach einem der Ansprüche 40 bis 45, wobei eine Downlink-Übertragungspaketmenge größer ist als eine Uplink-Übertragungspaketmenge.

47. Verfahren nach einem der Ansprüche 40 bis 45, wobei eine Downlink-Übertragungspaketmenge geringer ist als eine Uplink-Übertragungspaketmenge.

48. Verfahren nach einem der Ansprüche 40 bis 47, wobei die Downlink-Parameterinformation und die Uplink-Parameterinformation auch entsprechend einer statistischen Berechnung festgesetzt werden, die zuvor im Funkzugangsnetz festgesetzt wird.

49. Verfahren nach einem der Ansprüche 40 bis 48, wobei die Uplink-Parameterinformation mindestens einen Uplink-Parameterwert umfasst und die Downlink-Parameterinformation mindestens einen Downlink-Parameterwert umfasst.

50. Verfahren nach einem der Ansprüche 40 bis 49, wobei die Uplink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Komprimierer verwendet werden, und die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Anzahl von Kontexten (MAX_CID) darstellt, die für den Header-Dekomprimierer verwendet werden.

51. Verfahren nach einem der Ansprüche 40 bis 50, wobei die Downlink-Parameterinformation einen Parameter umfasst, der eine maximale Speichergröße eines Zwischenspeichers darstellt, der ein Paket mit fehlgeschlagener Dekomprimierung speichert (umgekehrte Dekomprimiertiefe).

52. Verfahren nach einem der Ansprüche 40 bis 51, wobei die Uplink-Parameterinformation einen Parameter umfasst, der Größen von Kompressionsheader-Paketen darstellt, die im Header-Komprimierer verwendbar sind (erlaubte Paketgröße).

Revendications

1. Réseau d'accès radio (20) pour un système de transmission de données utilisant des paquets de données et comprenant au moins un terminal (10), le réseau d'accès radio étant configuré :

pour recevoir des informations de capacité de terminal depuis le terminal ;

pour fixer des informations de paramètres montants pour un compresseur d'en-tête (712) du terminal ;

pour fixer des informations de paramètres descendants pour un décompresseur d'en-tête (711) du terminal ; et

pour transmettre les informations de paramètres montants et les informations de paramètres descendants au terminal ;

dans lequel le réseau d'accès radio est configuré pour fixer indépendamment les informations de paramètres montants pour le compresseur d'en-tête du terminal et les information de paramètres descendants pour le décompresseur d'en-tête du terminal en se basant sur les informations de capacité de terminal reçues.

2. Réseau d'accès radio selon la revendication 1, configuré en outre pour fixer différentes informations de paramètres pour le compresseur d'en-tête du terminal et pour le décompresseur d'en-tête du terminal.

3. Réseau d'accès radio selon l'une quelconque des revendications 1 et 2, dans lequel les informations de paramètres montants et les informations de paramètres descendants incluent des informations concernant l'espace mémoire.

4. Réseau d'accès radio selon l'une quelconque des revendications 1 à 3, dans lequel les informations de paramètres montants et les informations de paramètres descendants sont en relation avec un schéma de compression d'en-tête.

5. Réseau d'accès radio selon la revendication 4, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC3095.

6. Réseau d'accès radio selon la revendication 4, dans lequel le schéma de compression d'en-tête est un schéma de compression RSC2507.

7. Réseau d'accès radio selon l'une quelconque des revendications 1 à 6, dans lequel une quantité de paquets de transmission descendants est supérieure à une quantité de paquets de transmission montants.

8. Réseau d'accès radio selon l'une quelconque des revendications 1 à 6, dans lequel une quantité de paquets de transmission descendants est inférieure à une quantité de paquets de transmission montants.

9. Réseau d'accès radio selon l'une quelconque des revendications 1 à 8, dans lequel les informations de paramètres descendants et les informations de paramètres montants sont également fixées en accord avec un calcul statistique auparavant fixé dans le réseau d'accès radio.

10. Réseau d'accès radio selon l'une quelconque des revendications 1 à 9, dans lequel les informations de paramètres montants comprennent au moins une valeur de paramètre montant et les informations de paramètres descendants comprennent au moins une valeur de paramètre descendant.

11. Réseau d'accès radio selon l'une quelconque des revendications 1 à 10, dans lequel les informations de paramètres montants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le compresseur d'en-tête du terminal (MAX_CID) et les informations de paramètres descendants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le décompresseur d'en-tête du terminal (MAX_CID).

12. Réseau d'accès radio selon l'une quelconque des revendications 1 à 11, dans lequel les informations de paramètres descendants comprennent un paramètre représentant une taille de stockage maximum d'un tampon qui stocke un paquet de défauts de décompression (Reverse Decompression Depth).

13. Réseau d'accès radio selon l'une quelconque des revendications 1 à 12, dans lequel les informations de paramètres montants comprennent un paramètre représentant des tailles de paquets d'en-tête de compression utilisables dans le compresseur d'en-tête (Packet_Sized_Allowed).

14. Procédé de communication depuis un réseau d'accès radio (20) vers un terminal (10) dans un système de transmission de données, comprenant, mis en oeuvre dans le réseau d'accès radio :

la réception d'informations de capacité de terminal depuis le terminal ;

la fixation d'informations de paramètres montants pour un compresseur d'en-tête (712) du terminal ;

la fixation d'informations de paramètres descendants pour un décompresseur d'en-tête (711) du terminal ; et

le transfert des informations de paramètres montants et des informations de paramètres descendants au terminal ;

dans lequel les informations de paramètres montants pour le compresseur d'en-tête du terminal et les informations de paramètres descendants pour le décompresseur d'en-tête du terminal sont fixées indépendamment et sont basées sur les informations de capacité de terminal reçues.

15. Procédé selon la revendication 14, dans lequel les informations de paramètres montants pour le compresseur d'en-tête du terminal et les informations de paramètres descendants pour le décompresseur d'entête du terminal sont différentes les unes des autres.

16. Procédé selon l'une quelconque des revendications 14 et 15, dans lequel les informations de paramètres montants et les informations de paramètres descendants incluent des informations concernant l'espace mémoire.

17. Procédé selon l'une quelconque des revendications 14 à 16, dans lequel les informations de paramètres montants et les informations de paramètres descendants sont en relation avec un schéma de compression d'en-tête.

18. Procédé selon la revendication 17, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC3095.

19. Procédé selon la revendication 17, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC2507.

20. Procédé selon l'une quelconque des revendications 14 à 19, dans lequel une quantité de paquets de transmission descendants est supérieure à une quantité de paquets de transmission montants.

21. Procédé selon l'une quelconque des revendications 14 à 19, dans lesquelles une quantité de paquets de transmission descendants est inférieure à une quantité de paquets de transmission montants.

22. Procédé selon l'une quelconque des revendications 14 à 21, dans lequel les informations de paramètres descendants et les informations de paramètres montants sont également fixées en accord avec un calcul statistique auparavant fixé dans le réseau d'accès radio.

23. Procédé selon l'une quelconque des revendications 14 à 22, dans lequel les informations de paramètres montants comprennent au moins une valeur de paramètre montant et les informations de paramètres descendant comprennent au moins une valeur de paramètre descendant.

24. Procédé selon l'une quelconque des revendications 14 à 23, dans lequel les informations de paramètres montants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le compresseur d'en-tête du terminal (MAX_CID) et les informations de paramètres descendants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le décompresseur d'en-tête du terminal (MAX_CID).

25. Procédé selon l'une quelconque des revendications 14 à 24, dans lequel les informations de paramètres descendants comprennent un paramètre représentant une taille de stockage maximum d'un tampon qui stocke un paquet de défauts de décompression (Reverse Decompression Depth).

26. Procédé selon l'une quelconque des revendications 14 à 25, dans lesquels les informations de paramètres descendants comprennent un paramètre représentant des tailles de paquets d'en-tête de compression utilisables dans le compresseur d'en-tête (Packet_Sized_Allowed).

27. Terminal (10) à utiliser dans un système de transmission de données utilisant des paquets de données, le terminal comprenant un compresseur d'en-tête (712) et un décompresseur d'en-tête (711) et étant configuré
pour transmettre à un réseau d'accès radio (20) des informations de capacité de terminal ;
pour recevoir, depuis le réseau d'accès radio, des informations de paramètres montants et des informations de paramètres descendants ; et pour utiliser les informations de paramètres montants pour le compresseur d'en-tête (712) et les informations de paramètres descendants pour le décompresseur d'en-tête (711),
dans lequel les informations de paramètres montants pour le compresseur d'en-tête et les informations de paramètres descendants pour le décompresseur d'en-tête sont indépendantes les unes des autres et sont basées sur les informations de capacité de terminal.

28. Terminal selon la revendication 27, dans lequel les informations de paramètres montants pour le compresseur d'en-tête et les informations de paramètres descendants pour le décompresseur d'en-tête sont différentes les unes des autres.

29. Terminal selon l'une quelconque des revendications 27 et 28, dans lequel les informations de paramètres montants et les informations de paramètres descendants incluent des informations concernant l'espace mémoire.

30. Terminal selon l'une quelconque des revendications 27 à 29, dans lequel les informations de paramètres montants et les informations de paramètres descendants sont en relation avec un schéma de compression d'en-tête.

31. Terminal selon la revendication 30, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC3095.

32. Terminal selon la revendication 30, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC2507.

33. Terminal selon l'une quelconque des revendications 27 à 32, dans lequel une quantité de paquets de transmission descendants est supérieure à une quantité de paquets de transmission montants.

34. Terminal selon l'une quelconque des revendications 27 à 32, dans lequel une quantité de paquets de transmission descendants est inférieure à une quantité de paquets de transmission montants.

35. Terminal selon l'une quelconque des revendications 27 à 34, dans lequel les informations de paramètres descendants et les informations de paramètres montants sont également fixées en accord avec un calcul statistique préalablement fixé dans le réseau d'accès radio.

36. Terminal selon l'une quelconque des revendications 27 à 35, dans lequel les informations de paramètres montants comprennent au moins une valeur de paramètre montant et les informations de paramètres descendants comprennent au moins une valeur de paramètre descendant.

37. Terminal selon l'une des revendications 27 à 36, dans lequel les informations de paramètres montants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le compresseur d'en-tête (MAX_CID) et les informations de paramètres descendants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le décompresseur d'en-tête (MAX_CID).

38. Terminal selon l'une quelconque des revendications 27 à 37, dans lequel les informations de paramètres descendants comprennent un paramètre représentant une taille de stockage maximum d'un tampon qui stocke un paquet de défauts de décompression (Reverse Decompression Depth).

39. Terminal selon l'une quelconque des revendications 27 à 38, dans lequel les informations de paramètres montants comprennent un paramètre représentant des tailles de paquets d'en-tête de compression utilisables dans le compresseur d'en-tête (Packet_Sized_Allowed).

40. Procédé pour communiquer entre un terminal (10) et un réseau d'accès radio (20) d'un système de transmission de données, comprenant :

la transmission d'informations de capacité de terminal au réseau d'accès radio ;

la réception d'informations de paramètres montants et d'informations de paramètres descendants depuis le réseau d'accès radio ;

la formation d'un compresseur d'en-tête (712) en accord avec les informations de paramètres montants reçues ; et

la formation d'un décompresseur d'en-tête (711) en accord avec les informations de paramètres descendants reçues ;

dans lequel les informations de paramètres montants pour le compresseur d'en-tête et les informations de paramètres descendants pour le décompresseur d'en-tête sont indépendantes les unes des autres et sont basées sur les informations de capacité de terminal.

41. Procédé selon la revendication 40, dans lequel les informations de paramètres montants pour le compresseur d'en-tête et les informations de paramètres descendants pour le décompresseur d'en-tête sont différentes les unes des autres.

42. Procédé selon l'une quelconque des revendications 40 et 41, dans lequel les informations de paramètres montants et les informations de paramètres descendants incluent des informations concernant l'espace mémoire.

43. Procédé selon l'une quelconque des revendications 40 à 41, dans lequel les informations de paramètres montants et les informations de paramètres descendants sont en relation avec un schéma de compression d'en-tête.

44. Procédé selon la revendication 43, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC3095.

45. Procédé selon la revendication 43, dans lequel le schéma de compression d'en-tête est un schéma de compression RFC2507.

46. Procédé selon l'une quelconque des revendications de 40 à 45, dans lequel une quantité de paquets de transmission descendants est supérieure à une quantité de paquets de transmission montants.

47. Procédé selon l'une quelconque des revendications 40 à 45, dans lequel une quantité de paquets de transmission descendants est inférieure à une quantité de paquets de transmission montants.

48. Procédé selon l'une quelconque des revendications 40 à 47, dans lequel les informations de paramètres descendants et les informations de paramètres montants sont également fixées en accord avec un calcul statistique préalablement fixé dans le réseau d'accès radio.

49. Procédé selon l'une quelconque des revendications 40 à 48, dans lequel les informations de paramètres montants comprennent au moins une valeur de paramètre montant et les informations de paramètres descendants comprennent au moins une valeur de paramètre descendant.

50. Procédé selon l'une quelconque des revendications 40 à 49, dans lequel les informations de paramètres montants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le compresseur d'en-tête (MAX_CID) et les informations de paramètres descendants comprennent un paramètre représentant un nombre maximum de contextes utilisés pour le décompresseur d'en-tête (MAX_CID).

51. Procédé selon l'une quelconque des revendications 40 à 50, dans lequel les informations de paramètres descendants comprennent un paramètre représentant une taille de stockage maximum pour un tampon qui stocke un paquet de défauts de décompression (Reverse Decompression Depth).

52. Procédé selon l'une quelconque des revendications 40 à 51, dans lequel les informations de paramètres montants comprennent un paramètre représentant des tailles de paquets d'en-tête de compression utilisables dans le compresseur d'en-tête (Packet_Sized_Allowed).

Drawing