HK1210332B - Method for operating a mobile wireless network - Google Patents

Description

The invention is based on a method for operating a mobile network according to the type of main claim.

The German patent application, file No 1 9944 334.3, which has not yet been published, already contains a method for operating a mobile network in which data is combined by a first convergence protocol layer into at least one first unit, in particular a packet data unit, before being transferred to a second convergence protocol layer, in particular at the same protocol level, and the data is delivered from a user in a network layer to the first convergence protocol layer.

DE 198 47 679 A1 is known to be a method in which an SNDCP unit is set up using a service access point whose service access point identifier SAPI is used to identify the LLC interface on the network and subscriber side.

Err1:Expecting ',' delimiter: line 1 column 192 (char 191)

WO 96/21984 A1 describes a system whereby data packets are compressed and by means of this compression the transmission capacity can be significantly improved.

WO 99/27691 reveals a system which deals with the question of how the time lag between a party handling the negotiation and construction of a compression unit quickly and faster and the other party handling the negotiation and construction of a compression unit slowly and slower can be compensated.

Benefits of the invention

The method of the invention with the characteristics of claims 1 and 3 and the functional stations of the invention with the characteristics of claims 2 and 4 have the advantage, however, that at least one protocol instance of the first convergence protocol layer is configured, depending on a configuration request received by the second functional station, to form at least one first data unit from the data received by at least one user and to be transmitted by a carrier to a connection control layer, which can be generated in the first functional station by means of protocol instances whose settings and function correspond to the settings and function of corresponding protocol instances of the second functional station, so that a functional protocol is ensured between the two functional instances of the data transmission.

It is particularly advantageous that the configuration request specifies at least one of the alternate settings for the protocol instance supported by the second radio station, so that the first radio station can select the most favourable setting for the first radio station depending on its own capabilities or power range and/or user preference from the alternate settings.

It is also advantageous to transmit a confirmation signal from the first radio station to the second radio station, which communicates the setting of the second radio station selected and made by the first radio station, so that the second radio station can configure at least one of its protocol instances depending on the setting made for the first radio station, in order to ensure that the protocol instances function properly when transmitting the data units between the two radio stations.

It is also advantageous that a protocol instance identity is defined during configuration, which makes the protocol instance referential, allowing quick and direct access to the protocol instance for subsequent reconfigurations and for dismantling the protocol instance.

Another advantage is that the protocol instance identity is defined in such a way that it corresponds to the identity of the medium assigned to it, thus saving the transmission of an additional information element to identify the protocol instance and thus the transmission bandwidth.

It is particularly advantageous to transmit a message from the first radio station to the second radio station before receiving the configuration request indicating which settings of at least one protocol instance are supported by the first radio station, thus ensuring that the second radio station of the first radio station specifies only those settings for the configuration of at least one protocol instance which are fixed or selectable by the configuration request and which can also be implemented in the first radio station.

Another advantage is that the message is transmitted to the second radio station together with a message about the capabilities and power of the first radio station, thus saving an additional information element for the transmission of the message and thus transmission bandwidth.

Another advantage is that the configuration request is inserted into the carrier configuration message in the case where a carrier is built, reconfigured or disassembled by means of a carrier configuration message, thus saving an additional information element for the transmission of the configuration request and thus transmission bandwidth.

It is also advantageous to insert the confirmation signal into a message which the first radio station receives to confirm the construction or reconfiguration of the carrier, thus saving an additional information element for the transmission of the confirmation signal and thus the transmission bandwidth.

Drawing

An example of implementation is shown in the figure and further described in the following description: Figure 1 shows a mobile network with two radio stations, Figure 2 a protocol layer sequence for the two radio stations, Figure 3 an excerpt from the protocol layer sequence of the first of the two radio stations, Figure 4 an initial time course of a signalling exchange between the two radio stations, Figure 5 a second time course of a signalling exchange between the two radio stations, Figure 6 a message element to communicate the capabilities or power range of the first radio station, Figure 7 a carrier configuration message and Figure 8 a receipt message.

Description of the example of implementation

In Figure 1, 30 denotes a mobile network in which a first radio station 15 and a second radio station 16 are located. The second radio station 16 is connected to a network unit 80 which provides services to subscribers to the mobile network 30 and operates the mobile network 30. The first radio station 15 in this example is a subscriber to the mobile network 30, for example in the form of a mobile telecommunications terminal or a mobile station, in particular in the form of a mobile phone. The first radio station 15 is to be classified as a mobile station. The second radio station 16 in this example is a base station of the mobile network 30. However, it is not relevant to the invention whether the first radio station 15 or the second radio station 16 is a subscriber to the mobile network 30 or a mobile base station. The first radio station 15 is to be classified as a mobile station, but the second radio station 16 is a base station of the mobile network 30.

For example, the mobile network 30 may be operated according to a GSM (Global System for Mobile Communications) standard or a UMTS (Universal Mobile Telecommunications System) standard or similar.

The invention relates to a packet data convergence protocol for mobile networks. In particular, the invention proposes functionalities within a convergence protocol layer 1.2 as shown in Figure 2, which can be used, for example, in a mobile telecommunications system based on the UMTS (Universal Mobile Telecommunications System) standard or also in a mobile telecommunications system based on the GSM standard. The following is intended to be an example of the assumption that the mobile network 30 is operated according to the UMTS standard.

The convergence protocol used in accordance with the UMTS standard is called PDCP (Packet Data Convergence Protocol).

The functionalities of the UMTS mobile radio system are divided into layers as in the GSM mobile radio system as shown in Figure 2 and within the layers different protocols are specified, each providing services to the higher layers and using the services offered by the lower layers. Each protocol exists at least twice within the mobile radio system, namely in at least two units, with the units each located in the same layer. The first of the two units is the mobile station 15 and the second of the two units is the base station 16. The described rail hierarchy is divided into a user level and a control plane.The protocols in which utility data is transported are assigned to the user layer. Protocols in which control data is transported and partially generated are assigned to the control layer. For this invention, the layer or protocol hierarchy of the user layer is relevant, since the convergence protocol layer is at the user level and provides services for utility data transport. Utility data generated by applications in packages and intended to be transferred in a packet-oriented manner are first passed by the respective application to a transport layer protocol in a transport layer.The transport layer protocols are used to secure the packet data for transport through the mobile network 30, which in this case serves as a packet data network, and to add the necessary routing information to it. The transport layer uses services of a network protocol in a network layer below the transport layer. The network layer is shown in Figure 2 and is denoted by reference 5 for mobile station 15 and reference 6 for base station 16. The network protocols are referred to as PDP (Packet Data Protocol) as described. The transport layer uses the services of PDPs to transmit the useful data. The PDPs of the network layer 5, 6 (Internet) and X are known.The network layer 25 is a protocol whereby both the network and transport protocols can add control data to the utility data, for example in the form of a TCP/IP header or TCP/IP header. Below the network layer 5, 6 are the UMTS-specific protocols. With each PDP, data about the data connection used by the PDP is stored in the mobile network 30 and in a terminal device of the mobile network 30 communicating with the mobile network, e.g. in the mobile station 15.Thus, an IP protocol with an IP address can be run on a terminal device once with a first parameter for the QOS service quality and once with a second parameter for the QOS service quality. PDP contexts can also be based on different network protocols.

Each of these PDP contexts is represented as a separate block in network layer 5, 6 above the convergence protocol layer 1, 2 and is designated in Figure 3 for mobile station 15 with reference numbers 21 and 22; PDP contexts 21, 22 represent users of the convergence protocol layer 1, 2 below the network layer 5, 6 as shown in Figure 3; and in Figure 2 the convergence protocol layer for mobile station 15 is designated with reference number 1 and the convergence protocol layer for base station 16 with reference number 2.

The PDCP, whose task is to prepare data to be transmitted between mobile station 15 and base station 16 for efficient UMTS transmission, adapts the payloads coming from a PDP context to the airborne transmission by optionally compressing the payloads and/or the control data or protocol control information added to the payloads and possibly aggregating or multiplexing packet data streams from 21 different PDP contexts 22 that require the same transmission quality into one packet data stream.

Below the convergence protocol layer 1, 2 for the formation of the PDCP, in the layer model of the UMTS mobile radio system, there is a radio link control layer (RLC) designated for mobile station 15 as reference 10 and for base station 16 as reference 11 in Figure 2 and which corrects the optional transmission errors of the air interface by re-receiving faulty packets on the receiver side and resending them on the transmitter side. Furthermore, the RLC layer 10, 11 optionally ensures that the order of the data packets used in the transmission is maintained and it segments the data packets in a data unit called RPDLCUs (CRLUs), the length of which is suitable for transmission.

For the transmission of each multiplexed packet data stream from different PDP contexts 21, 22 a data carrier, also called a radio bearer or RB, is then used, provided by the RLC link control layer 10, 11 below the convergence protocol layer 1, 2.

The convergence protocol layer 1.2 consists of so-called PDCP protocol instances 35 as shown in Figure 3, each of which may contain multiple compression algorithms 50, 51. Multiple PDP contexts 21, 22 may be connected to a PDCP protocol instance 35, but a PDP context 21, 22 may be connected to only one PDCP protocol instance 35. Each PDCP protocol instance 35 uses exactly one so-called carrier 45, also known as a radio bearer. A radio bearer is the connection between a PDCP protocol instance 35 and an instance of the underlying RLC link control layer 10, 11 (Radio = radio link control), through which the data from the convergence protocol layer 1, 2 to the RLC link control protocols 10, 11 are passed on.Err1:Expecting ',' delimiter: line 1 column 100 (char 99)to allow for decoding.

In order to ensure the proper functioning of the PDCP protocol instances 35, the compression algorithms 50, 51 must match their compression parameters, such as the number of codes to be stored in the compressor and decompressor in corresponding codebooks, and the multiplex information of the two convergence protocol layers 1, 2 in mobile station 15 and base station 16, indicating which PDP contexts 21, 22 to route their packet data streams of the corresponding PDCP protocol instance 35 to the multiplex. The compression algorithms 50, 51, the configuration parameters and multiplex information represent the so-called sRCCP protocol resources, which may also include additional radio resources, such as the corresponding RRC 16 radio resource controller, which is required to connect to the new PDCP protocol 15 (RRC 15), and the data controller, which may include information about the two radio resource controllers used for the transmission of the PDCP control station 15 (RRC 15), which may be used to connect to the new PDCP controller.

Err1:Expecting ',' delimiter: line 1 column 862 (char 861)

Data to be transmitted between mobile station 15 and base station 16 shall be transmitted from top to bottom in the specified sequence of layers, and data received from bottom to top in the specified sequence of layers.

Err1:Expecting ',' delimiter: line 1 column 138 (char 137)

Err1:Expecting ',' delimiter: line 1 column 81 (char 80)

Figure 3 shows an example of a section of the shift sequence for mobile station 15.

Figure 3 shows the network layer 5, the convergence protocol layer 1 and the connection control layer 10 of mobile station 15. According to Figure 3, each PDP context 21, 22 uses the services of the convergence protocol layer 1 at an access point 101, 102 assigned to it, which may also be referred to as a network layer service access point (NSAP). Each of these access points 101, 102 is assigned an identifier, such as a Network Layer Service Access Point Identifier (NSAPI), which uniquely identifies the assigned PDP context 21, 22.The connections of the connection control layer 10 are used by the convergence protocol layer 1 through service access points, also known as SAP (Service Access Point). Each connection to the SAPs is assigned an identifier RB Identity (Radio Bearer Identity). To identify the individual connections between the convergence protocol layer 5 and the connection control layer 10. Each service point provides a specific service or transmission quality QOS and, therefore, the GSM mobile access system provides a maximum of four different service points and four different connections in the connection control layer 10 with different transmission quality QOS.In order to enable the convergence protocol layer 1 to forward data packets arriving or received at one of the service access points to the correct receiver or PDP context after decompression of the utility data and/or protocol control information of these data packets, the data packets may be assigned by the sender an identifier of the receiving PDP context, i.e. the receiving user of the convergence protocol layer 1.

The described connections to the service access points are each made by a carrier, which is also referred to as the radio bearer as described. A radio bearer is, as described, the connection between a PDCP protocol instance 35 and an instance of the underlying RLC connection control layer 10, 11, through which data is passed from the convergence protocol layer 1, 2 to the RLC connection control layer 10, 11.

The PDCP protocol instance 35 of the convergence protocol layer 1 described in the example includes a data compression algorithm 51 compressing utility data received from network layer 5 as shown in Figure 3. The data compression algorithm 51 is associated with a data decompression algorithm not shown in Figure 3. The data decompression algorithm decompresses data received from connection control layer 10 and thus ultimately from base station 16. They compress data according to the associated data compression algorithm 51 The backward flow. PDCP protocol instance 35 compresses data in a data decompression protocol 50 similar to that shown in Figure 3. The data decompression algorithm is further recommended as a decompression information compression algorithm for the network and is also recommended for the data decompression protocol 50 and 50 as a decompression information compression algorithm.

A first PDP context 21 is connected via a first access point 101 to the protocol control information compression algorithm 50 and an associated protocol control information decompression algorithm via a first associated access point 101; the associated compression and decompression algorithms are considered as a unit and referenced by the corresponding compression algorithm, for the sake of simplicity, below; thus, the protocol control information compression algorithm 50 via data compression algorithm 51, hereinafter referred to as the second compression algorithm 51, is connected to carrier 45.

A second PDP context 22 is directly connected to the data compression algorithm 51 via a second access point 102 assigned to it, which is connected to carrier 45 as described.

The invention is based on procedures that allow the negotiation of PDCP protocol instance parameters and the construction of PDCP protocol instances between two mobile network 30 devices, in this example between the mobile station 15 and the base station 16 that interact with the network unit 80, such as a radio network controller (RNC), and thus are to be understood as a proxy network instance.

At the beginning of the negotiations, a procedure is used whereby base station 16 receives a message 60 from mobile station 15 as shown in Figure 4 about the settings of the PDCP protocol instance 35 of mobile station 15 to be configured that are supported by mobile station 15. This example describes, for example, the configuration of the PDCP protocol instance 35 shown in Figure 3.

Immediately prior to the initial setup of the PDCP protocol instance 35, base station 16 sends an initial configuration request 40 to mobile station 15 to initiate the initial setup of the PDCP protocol instance 35, as shown in Figure 4. This initial configuration request 40 contains the PDCP protocol instance parameters that base station 16 has selected based on the previously received message 60 according to the settings of the PDCP protocol instance 35 to be configured supported by mobile station 15.

It is now possible for mobile station 15 to build PDCP protocol instance 35 with the PDCP protocol instance parameters received by base station 16 in the first configuration request 40. After this setup, mobile station 15 discharges the setup, signaling base station 16 by means of an initial confirmation signal 55 that the PDCP protocol instance 35 is ready to receive or send data. This initial confirmation signal 55 is also referred to as PDCP Establishment Confirm.

Alternatively or additionally, the first configuration request 40 may include a selection of settings or PDCP protocol instance parameters supported by base station 16 to form the PDCP protocol instance 35, so that the mobile station 15 is given the option, upon receipt of the first configuration request 40, to select the PDCP protocol instance parameters from the pre-set selection in order to optimally match the capabilities and performance of the PDCP protocol instance 35 and, if applicable, user specifications. The first confirmation signal 55, which the mobile station 15 then sends to base station 16, allows the mobile station 16 to match the desired PDCP protocol instance with the base station 15 set.

Err1:Expecting ',' delimiter: line 1 column 299 (char 298)

For example, message 60 contains information on the compression algorithms 50, 51 supported by mobile station 15 and their compression parameters used and the multiplexing methods available in mobile station 15, i.e. the maximum number of PDP contexts 21, 22 and the possible number of carriers used by the convergence protocol layer 1 of mobile station 15.

The first configuration request 40 contains information about which PDP contexts 21, 22 access the establishing PDCP protocol instance 35 and which carrier 45 is to be used by that PDCP protocol instance 35, and the first configuration request 40 contains either firm specifications on the compression algorithm (s) to be used 51, 50 and the compression parameters to be used for it, or the first configuration request 40 contains a selection of possible compression algorithms 50, 51 and/or a selection of compression parameters from which the mobile station 15 may select one or more suitable compression algorithms 50, 51 and their compression comparator.

The first acknowledgement signal 55 then contains either only the information that the corresponding PDCP protocol instance 35 has been set up or additional information about the selected compression algorithm (s) 50, 51 and its compression parameters.

Err1:Expecting ',' delimiter: line 1 column 106 (char 105)

Err1:Expecting ',' delimiter: line 1 column 400 (char 399)

Err1:Expecting ',' delimiter: line 1 column 385 (char 384)

To modify the multiplexing function of the established PDCP protocol instance 35 described in this example, it may be useful to add to the second configuration request 41 information about one or more new PDP contexts whose packet data streams are to be multiplexed in the convergence protocol layer 1 of the mobile station 15 in addition to the packet data streams of the existing PDP contexts 21, 22 on the carriers 45 used by the PDCP protocol instance 35.

If one or more existing PDP contexts 21, 22 use a carrier with different characteristics, for example with a different transmission quality QOS, it may be useful to add to the second configuration request 41 information about the PDP context (s) whose packet data streams are to be multiplexed in the convergence protocol layer 1 of the mobile station 15 by the existing PDCP protocol instance 35 onto a carrier that has the required characteristics.

If the PDCP protocol instance 35 uses one or more other or additional compression algorithms to compress utility data or protocol control information, it may be useful to add information about this or those new compression algorithms to the second configuration request 41.

Err1:Expecting ',' delimiter: line 1 column 181 (char 180)

If, after receipt of the second configuration request 41 and as described for the first configuration request 40, mobile station 15 is given the option to select the PDCP instance parameters from a selection provided by base station 16, the PDCP instance parameters selected and set by mobile station 15 may be contained in the second confirmation signal 56 as described for the first confirmation signal 55 and as specified for the first confirmation signal 55.

Err1:Expecting ',' delimiter: line 1 column 189 (char 188)

The established PDCP protocol instance 35 can also be decommissioned. This operation is also understood in this embodiment as a configuration, as well as the construction and reconfiguration of the PDCP protocol instance 35. To do this, base station 16 sends a third configuration request 42 to mobile station 15 containing the PDCP protocol instance identifier, as shown in Figure 5, and upon receipt of the request, mobile station 15 decommissiones the PDCP protocol instance 35.

Err1:Expecting ',' delimiter: line 1 column 167 (char 166)

Err1:Expecting ',' delimiter: line 1 column 268 (char 267)

Err1:Expecting ',' delimiter: line 1 column 320 (char 319)

Err1:Expecting ',' delimiter: line 1 column 491 (char 490)

Err1:Expecting ',' delimiter: line 1 column 174 (char 173)

Err1:Expecting ',' delimiter: line 1 column 114 (char 113)

Err1:Expecting ',' delimiter: line 1 column 153 (char 152)

Err1:Expecting ',' delimiter: line 1 column 153 (char 152)

Err1:Expecting ',' delimiter: line 1 column 210 (char 209)

Err1:Expecting ',' delimiter: line 1 column 188 (char 187)

Err1:Expecting ',' delimiter: line 1 column 118 (char 117)

The PDCP protocol instance 35 configuration cases mentioned herein by building, reconfiguring and dismantling the PDCP protocol instance 35 are initiated by the base station 16 in the embodiment described herein, but may also be initiated by the mobile station 15.

The following describes in more detail the communication between mobile station 15 and base station 16, whereby mobile station 15 comprises a digital computer and a mobile unit, through which the digital computer can send and receive data to and from the mobile network 30, for example, to and from the Internet, which is connected to the mobile network 30 in this example.

Err1:Expecting ',' delimiter: line 1 column 207 (char 206)

Err1:Expecting ',' delimiter: line 1 column 47 (char 46)Err1:Expecting ',' delimiter: line 1 column 190 (char 189)

Err1:Expecting ',' delimiter: line 1 column 67 (char 66)

It is now assumed, based on the PDCP protocol instance 35 described in Figure 3, that the mobile station 15 supports both the first compression algorithm 50 and the second compression algorithm 51; the second compression algorithm 51 is capable of compressing utility data compiled by the transport layer protocols and network protocols as described; and further, in accordance with the PDCP protocol instance 35 described in Figure 3, it is assumed that the mobile station 15 also supports multiplexing of packet data streams of different PDP contexts 21, 22.

Err1:Expecting ',' delimiter: line 1 column 335 (char 334)Err1:Expecting ',' delimiter: line 1 column 252 (char 251)Err1:Expecting ',' delimiter: line 1 column 51 (char 50)

Err1:Expecting ',' delimiter: line 1 column 86 (char 85)

This means that a PDP context with identifier 22 uses the PDCP protocol instance 35 to multiplex its packet data streams to carrier 45, with the PDCP protocol instance 35 using a compression algorithm with the number 51 and code book length 16. This corresponds to a configuration of the PDCP protocol instance 35 as shown in Figure 3, where only the second PDP context 22 is connected via the second access point 102, the second compression algorithm 51 and carrier 45 to the RLC connection control layer 10 of the mobile station 15, where a multiplex is not required per se, as only the packet data stream of the second PDP protocol layer 22 is accessed via the PDP 45 RLC connection layer 15 via the 10K configuration.

Err1:Expecting ',' delimiter: line 1 column 548 (char 547)

The PDCP protocol instance 35 set up in this manner, which uses the same set-up medium 45, can be conveniently reconfigured or reconfigured in two ways.

Err1:Expecting ',' delimiter: line 1 column 318 (char 317)

Err1:Expecting ',' delimiter: line 1 column 260 (char 259)

Err1:Expecting ',' delimiter: line 1 column 177 (char 176)

The configuration of the PDCP protocol instance 35 of the mobile station 15 with the compression algorithms, compression parameters and multiplexing properties to be used shall be specified by the base station using the corresponding configuration requests 40, 41, 42 such that the compression algorithms used by the PDCP protocol instance 35 to be configured shall each correspond to a decompression algorithm in base station 16 to decompress the protocol control information or utility data compressed by the PDCP protocol instance 35 to be configured. Furthermore, for the same reason for the decompression in base station 16 the data also used by the multi-instance network protocol 35 to be configured shall be specified by the PDCP protocol 16 to be configured. The complexity of the output power used by the PDCP protocol 16 to be configured shall be measured on the basis of the PDCP 16 as the power flow rates and the utility data to be transmitted on the PDCP 16 as the power flow rates.

The following aspects result in preferred embodiments of the present invention: 1. a method for operating a mobile network (30) in which utility data is aggregated through a first convergence protocol layer (1) of a first radio station (15) before being transmitted to a second convergence protocol layer (2) of a second radio station (16), in particular at the same protocol level, into at least one first data unit, in particular a packet data unit, where the utility data is delivered from at least one user (21, 22) in a network layer (5) to the first convergence protocol layer (1), characterised by the configuration of at least one protocol instance (35) of the first convergence protocol layer (1) depending on a configuration request (40, 41, 42) received by the second radio station (16);to form at least one first data unit from the data received by at least one user (21, 22) and transmit it via a carrier (45) to a connection control layer (10).2. process in Aspect 1 characterised by at least one compression algorithm (50, 51) being specified in the configuration, by the protocol control data being compressed for the transmission of at least one first data unit or by the utility data itself to be transmitted by at least one first data unit and corresponding to a decompression algorithm in the second radio station (16) to decompress the protocol control data or utility data.3. process in Aspect 2 characterised by at least one compression algorithm being specified (50,Processes described in Aspect 1, 2 or 3 are characterised by the configuration of multiplexing characteristics which specify the users (21, 22) whose data units, composed by at least one log instance (35) from the respective received utility data, are transmitted by the carrier (45) to the connection control layer (10) after multiplexing, whereby the utility data thus generated becomes multiplexing upon reception in the second radio station (16) depending on these multiplexing characteristics.characterised by the configuration of the media (45) through which the utility data is transmitted from the protocol instance (35) to the connection control layer (10).Procedure according to one of the previous aspects, characterised by the configuration request (40, 41, 42) providing at least one of the alternative settings supported by the second radio station (16) for the protocol instance (35).Procedure according to the aspect 6, by the first radio station (15) transmitting a confirmation signal (55, 56, 57) to the second radio station (16) informing the second radio station (16) of the setting selected and made by the first radio station (15).Procedure by one of the previous aspects, characterised by the configuration request (40, 41, 42) specifying at least one setting for the protocol instance (35).Procedure by one of the previous aspects, characterised by the configuration establishing a protocol instance identity by which the protocol instance (35) is referenced.Procedure by one of the previous aspects, characterised by the protocol instance identity being established in such a way as to correspond to the identity of the carrier to which it is assigned (45).Procedure by one of the previous aspects, characterised by the transmission of a message (60) from the first radio station (15) to the second radio station (16) before receipt of the configuration request (40, 41, 42)which specifies which settings of at least one protocol instance (35) are supported by the first radio station (15).12. Process according to Aspect 11, characterized by the message (60) being transmitted to the second radio station (16), together with a message (65) about the capabilities and power of the first radio station (15),.13. Process according to one of the previous aspects, characterized by the configuration request (40) building up at least one protocol instance (35).14. Process according to one of the previous aspects, characterized by the configuration request (41) changing or reconfiguring the settings of a built-in protocol instance (35)..15. Process according to one of the previous aspects, characterized by the configuration request (42) building up a decommissioned protocol instance (35).16. procedure according to one of the preceding aspects, characterized by the insertion of the configuration request (40, 41, 42) in a message (75) where a carrier (45) is built, reconfigured or disassembled by means of a carrier configuration message (70) into which the carrier configuration message (70) is inserted.

Claims (11)

1. Method for configuring a protocol instance (35) in a convergence protocol layer (1) of a first radio station (15), so that settings and functions of the protocol instance (35) correspond to settings and functions of a corresponding protocol instance (36) in a convergence protocol layer (2) of a second radio station (16), wherein the method comprises the following steps:

   Sending a carrier configuration message to the first radio station (15),

   in order to set up by means of the carrier configuration message (70) a carrier (45), which connects the convergence protocol layer (1) with a RLC connection control layer (10), and

   wherein a configuration request (40, 41, 42) is included in the carrier configuration message (70) in order to configure at least the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15) as a function of the configuration request (40, 41, 42),

   configuring a carrier and configuring the protocol instance (36) in the convergence protocol layer (2) of the first radio station (16) by means of a radio resource control (96) of the second radio station (16).
2. Second radio station (16), which is adapted to send a carrier configuration message to the first radio station (15), to set up a carrier (45), which connects the convergence protocol layer (1) with a RLC connection control layer (10), by means of the carrier configuration message (70), wherein the second radio station (16) comprises means for including a configuration request (40, 41, 42) in the carrier configuration message in order to configure at least the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15) as a function of the configuration request (40, 41, 42), characterized in that, the second radio station (16) comprises a radio resource control (96) for configuring a carrier and for configuring the protocol instance (36) in the convergence protocol layer (2) of the first radio station (16).
3. Method for configuring a protocol instance (35) in a convergence protocol layer (1) of a first radio station (15), so that settings and functions of the protocol instance (35) correspond to settings and functions of a corresponding protocol instance (36) in a convergence protocol layer (2) of a second radio station (16), wherein the method comprises the following steps:

   receiving a carrier configuration message sent from the second radio station (16) to the first radio station (15),

   in order to set up by means of the carrier configuration message (70) a carrier (45), which connects the convergence protocol layer (1) with a RLC connection control layer (10), and

   wherein a configuration request (40, 41, 42) is included in the carrier configuration message (70) in order to configure at least the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15) as a function of the configuration request (40, 41, 42),

   configuring a carrier and configuring the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15) by means of a radio resource control (96) of the second radio station (15).
4. First radio station (15), which is adapted to receive a carrier configuration message from a second radio station (16), to set up a carrier (45), which connects the convergence protocol layer (1) with a RLC connection control layer (10), by means of the carrier configuration message (70), wherein the first radio station (15) comprises means for reading a configuration request (40, 41, 42) from the carrier configuration message in order to configure at least the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15) as a function of the configuration request (40, 41, 42), characterized in that, the first radio station (15) comprises a radio resource control (96) for configuring a carrier and for configuring the protocol instance (35) in the convergence protocol layer (1) of the first radio station (15).
5. Method according to Claim 1 or 3, characterized in that the configuration request (40, 41, 42) predetermines at least one selection, which is supported by the second radio station (16), of alternative settings for the protocol instance (35).
6. Method according to Claim 5, characterized in that a confirmation signal (55, 56, 57) is transmitted from the first radio station (15) to the second radio station (16), in which the settings chosen and set up by the first radio station (15) are indicated to the second radio station (16).
7. Method according to Claim 1, 3, 5 or 6, characterized in that the configuration request (40, 41, 42) predetermines, in a fixed manner, at least one setting for the protocol instance (35).
8. Method according to Claim 1, 3, 5, 6 or 7, characterized in that the first radio station (15) transmits a message (60) to the second radio station (16) before reception of the configuration request (40, 41, 42), which message (60) indicates what settings of the at least one protocol instance (35) are supported by the first radio station (15).
9. Method according to Claim 8, characterized in that the message (60) is transmitted to the second radio station (16) together with a message (65) about capabilities and performance of the first radio station (15).
10. Method according to Claim 1, 3, 5, 6, 7, 8, or 9, characterized in that a protocol instance identifier is determined at configuration, by means of which the protocol instance (35) can be referenced.
11. Method according to Claim 8, characterized in that the protocol instance identifier is determined in such a way that it corresponds to the identity of its associated carrier (45).