MX2008009561A - Method and devices for installing packet filters in a data transmission - Google Patents

Abstract

A method is described for associating a data packet (DP) with a packet bearer (PB) in a user equipment (UE1 ) of a communication network. The data packet is sent in a data flow from an application function of the user equipment, the packet bearer (PB) is established with the user equipment to transmit the data packet (DP) over the communication network towards a further entity, and the user equipment is adapted to establish different packet bearers. The method comprises the steps of identifying the flow with the data packet in a control entity of the communication network, determining the packet bearer for association with said flow from the different packet bearers in a policy function of the control entity, determining a routing level identification of the further entity, instructing the user equipment to install a packet filter based on the routing level identification, wherein the packet filter associates data packets comprising the routing level identification of the further entity with the determined packet bearer, providing the routing level identification to the application function, including the routing level identification into the data packet, and forwarding the data packet (DP) on the determined packet bearer (PB). A corresponding network, control entity, monitoring entity and computer program are also described.

Description

METHOD AND DEVICES FOR INSTALLING PACKAGE FILTERS IN A DATA TRANSMISSION TECHNICAL FIELD OF THE INVENTION The present invention relates to a method for associating a data packet with a packet bearer in a user equipment of a communication network. Devices and software programs embodying the invention are also described. BACKGROUND OF THE INVENTION In many cases, data packets must be sent through a communication network between a user equipment and an additional entity. Transmissions can be made both in the downlink direction and in the uplink direction, and the additional entity is often another user equipment, for example, in the case of a telephone call. The additional entity can also be a service entity such as, for example, a server that can send different packet streams for sound and video to the user equipment, for example, in the case of a stream training session, whereas the User equipment can also send packets to the additional entity. The additional entity may be part of the communication network or may have the ability to exchange data packets with the network. The communication network can be a fixed network or a mobile network. Several networks can participate in the transmission, for example, if the user equipment is in a mobile network which is interconnected directly or through intermediate networks to a fixed network where the additional entity is located. Typical mobile networks comprise a core network with core network nodes, for example nodes that support general packet radio (GSN) services such as a general service packet radio service (SGSN) support node or a carrier support node. gateway general package radio service (GGSN). The central network nodes allow the exchange of data with external networks, such as the Internet or mobile or fixed networks of other operators. In addition, customary mobile networks comprise one or more access networks that access network nodes to control radio transmission to the user equipment, which is commonly known, for example, as base station controllers, radio network controllers (RNCs) , Node B or base transceiver stations. Other implementations of the nodes and networks are possible, for example a GSN-enhanced or enhanced RNC that perform different parts of the SGSN functionality and thus allow the omission of an SGSN. An operator can offer services to subscribers that generate different types of packet traffic, which are tones transmitted through the communication network. Depending on the type of packet traffic the requirements for transmission differ significantly, for example, a voice transmission requires a low delay and low fluctuations while a limited number of errors can be accepted. Stream formation sessions that use packet buffers typically allow for longer delays and greater disturbance and the receiver can usually also correct errors or hide them. File transfer can often be done as best effort traffic but usually requires error-free data. In addition, operators can choose to offer different qualities of service (QoS) according to the user's subscription, that is, they can choose to differentiate according to the user. Accordingly, the provision of a defined quality of service is an important concept in the control of data traffic in accordance with what is described for example in the technical specification 3GPP 23.107 V 6.3.0. of the 3rd Generation Partnership Project "Quality of Service (QoS) concept and architecture." Third-Generation Partnership Project (QoS) conception and architecture.] Different contexts define the quality of service in relation to a data transmission that includes nodes of a communication network and the user equipment. The user equipment and a central network node negotiate a PDP context (packet data protocol) that specifies parameters for the transmission of data packets to the user equipment and from the user equipment through a 3GPP bearer. Additional contexts can be established for bearers in relation to different links between the future entity and the user equipment, for example, a context for the radio bearer between an access node and the user equipment, which specifies the transcription parameters in the radio link. The packet flows between the additional entity and the user equipment are then mapped to the carriers associated with these contexts and transferred accordingly. The current 3GPP standards define a mechanism for mapping downlink data to a packet bearer. For this purpose, the bearer is associated with a PDP context. The PDP context is the granularity with which Qos can be provided, that is, different PDP context can provide different QoS. Packet mapping in DPD context is performed at an edge node of the communication network, for example, in GGSN using downlink Traffic Flo Templates (TFT). A TFT is a packet filter that defines rules that map only incoming data packets in a PDP context. The downlink TFT is part of the PDP context definition and can be configured to operate on different numbers or parameters. For example, the IP source address of a data packet or the "Type of Services" (ToS) field in the IP header can be used to map packets in a PDP context. Session Management Protocol (SM) is used to manage PDP Contexts. In the uplink, the user equipment requires information on how to map data packets from an application to a bearer with the associated context. However, this functionality is not within the scope of 3GPP standards. On the contrary, it is defined in its own way and can differ between vendors of equipment for users. In one implementation, the user equipment has several PDP context tempers, each with a different associated QoS. A connection manager offers a mapping for each application to one of the tempered PDP contexts. Mapping is a static configuration that creates a link in the connection manager and is signaled to the user equipment, for example through SMS. Typically, the user makes the configuration by visiting an operator's website and entering the phone model that he is using and the application he wants to configure, for example, WAP or MMS. When initiating a session, for example, when a call is made, the application communicates to the connection manager through an API (application programming interfaces) of its own. The Connection Manager associates the data packets coming from the application with the configured PDP context and, if required, establishes the context. Correspondingly, there is a static union between the application and PDP context tempering. The computer identifiers used in the configuration can be specific to each vendor. As a result, existing methods for associating packets and data with a bearer are inflexible and do not allow dynamic configuration changes. An additional problem is that the application development is specific to access and vendor-specific, that is, applications must be written for a specific access (eg, 3GPP) and a particular user equipment vendor since the QoS API in The aforementioned connection mechanism may differ both in terms of vendors and access. In addition, the user equipment in accordance with 3GPP specifications may consist of two entities, a terminal equipment (TE) and a mobile terminal (MT) which are logically distinct and also optionally physically different. Applications are executed in the terminal equipment and data packets are exchanged in the mobile terminal with the mobile network. In the state of the art, a TE and MT interface will be required upon which it is possible to transfer the bearer requirements of the application. Since the connection of the application and context is specific to the vendor on the current user equipment, different interfaces would be required. If the terminal equipment is, for example, a personal computer and the mobile terminal is a mobile network card, the computer may require to support different interfaces for different card vendors, which causes a significant complexity and a high cost. SUMMARY OF THE INVENTION With this context, it is an object of the present invention to propose a simple and flexible method for associating data packets with a bearer in a user equipment of a communication network. According to the following invention, the method described in claim 1 is carried out. Furthermore, the invention is incorporated into a communication network, a control entity, a monitoring entity / program and a computer program in accordance with that described in the other independent claims. Profitable modes are described in the dependent claims. The proposed method associates a data packet with a packet bearer in a user equipment of a communication network. The data packet is sent in a data stream from an application function of the user equipment. Although the stream may comprise only a single data packet, typically several data packets are sent with the stream. The packet bearer is established with the user equipment to transmit the data packet through the communication network to an additional entity, for example through user equipment or to a server. The establishment of the bearer can be activated by the user equipment or by another entity of a communication network. The establishment can be carried out at different times in relation to the other steps of the method as will be described below. The user equipment is adapted to establish different packet bearers. For example, carriers may differ in terms of the quality of service provided. Optionally, the user equipment can maintain more than one simultaneously established bearer. The method identifies the flow with the data packet in a control entity of the communication network. A policy function of the control entity determines the packet bearer for association with said flow from the different packet bearers. Preferably, the control entity is equipped with operator policy rules to determine the selection of the carriers determined among the different carriers that the user equipment is adapted to establish. In a UMTS (Universal Mobile Telecommunication System) network, the control entity can be, for example, a GSN or a PCRF (Function of Collection and Policy Rules). A routing level identification of the additional entity is determined. This determination can be made in the control entity or in another entity of the network that sends the identification of the routing level to the control entity. The identification of the routing level allows transferring the data packets to the additional entity. The identification of the routing level can be part of the identification of the flow and can be identified in said identification. The user equipment is instructed to install the packet flow based on the routing level identification. The packet filter associates data packets comprising the routing level identification of the original entity with the particular packet bearer. The routing level identification is provided to the application function, for example, to a signaling message that originates from the additional entity. Routing level identification is included in the data package. Accordingly, the data packet is transferred by the packet filter in the particular packet bearer. The proposed method allows a simple and flexible association of packets of data with packet bearers that does not require a previous configuration of the association and can be established before, at the time of, or after, a data session. The proposed method offers a controlled way for the communication network, i.e., the network operator, to map data packets in uplink carriers from the user equipment to an additional entity and consequently to provide differentiation between services and among users. The network can allow or prohibit the mapping of selected flow to carriers in the user equipment with the policy function that controls the filter installation. For this purpose, the operator can specify policy rules. In addition, the method allows access to agnostic application development, i.e., applications can be developed independently of the access network to which the user equipment is connected because only ubiquitous plug-in API functions are used. This simplifies the development of applications which allows a lower costly development. The routing level identification can be established through the application through the Plug API application. The method does not introduce new dedicated signals to install the uplink packet filter but reuses the existing procedures for this purpose and therefore can be easily implemented in existing communication networks. Communications networks typically comprise several entities. In a preferable embodiment, the control entity receives the routing level identification determined from a monitoring entity and instructs the user equipment to install the packet filter. The monitoring entity and the control entity can be implemented by the device use parts or in different devices. The monitoring entity may, for example, monitor a signaling for the session establishment between the user equipment and the additional entity or packet of data sent during a session established between the user equipment and the additional entity. As the signaling to install the filter and for session initiation has different receiving entities in the user equipment in general will be made also using different signaling protocols, often it is not appropriate to have a single entity to monitor the messages of session levels and give instructions for installing the filter. In a useful mode of the proposed method, the establishment of communication session between the user equipment and the additional entity is initiated through a start message. The start message comprises a session level identification of the additional entity, for example, in the format of a telephone number, a uniform resource locator (URL) such as the email address or any other session level identification. A monitoring entity is adapted to monitor messages sent between the user equipment and the additional entity to establish the session. The monitoring entity stores information related to the communication session. For example, the monitoring entity may be a call state control function that stores a state for initiated sessions. The monitoring entity may be associated with an entity to effect an address resolution of the session level identification by transferring the start message to the additional entity. The start message is transferred to the additional entity using the session level identification. The monitoring entity is then a response message related to the establishment of the communication session and determines the identification of the routing level of the additional entity from the response message. It is possible to receive several response messages and the 'identification of routing level can be determined from one or more response messages. The response message is transferred to the user equipment and the establishment of the session is carried out. This mode allows a simple implementation to obtain the required information and determine the identification of the flow, especially for the origin side of the session. In an alternative embodiment of the proposed method, an establishment of a communication session between the additional entity and the user equipment is initiated by a start message comprising a routing level identification of the additional entity and a session level identification. of the user equipment. A monitoring entity is adapted to receive the start message and to determine the routing level identification of the additional entity from the start message. The start message is then transferred to the user equipment using the session level identification, and the establishment of the session is effected. This mode allows a simple implementation to obtain the required information and determine the identification of the flow, especially in the case of the termination side of the session. In a further embodiment, initial data packets sent by the user equipment in a first carrier are expected, for example, in the control entity or in a monitoring entity. The first carrier can be, for example, a default carrier or it can be established in accordance with one of the embodiments described above. The flow for association is identifiable from the data of packets inspected, for example, due to information in the packet header, packet content or other parameters of the data packets. Then, a second packet bearer is determined for association with said flow. The second carrier can then be established for flow, a filter can be installed to associate the flow with a second existing carrier, or parameters of an existing carrier, for example, the first carrier, can be modified for this purpose. In a profitable embodiment, the establishment of the packet bearer is initiated by a request coming from a node in the communication network. This allows for improved control of the network operator through transmission by the user equipment. Preferably, the packet bearers differ in at least one associated member of a group comprising a quality of service, a charging fee and an access point to which the packet is transferred. Accordingly, carriers may offer a different quality of service or may be charged differently or both, and may be selected accordingly. Typically, the user equipment comprises an execution unit for executing the application function and a transmission unit for sending the data packet in the associated packet carrier. In many cases the execution unit and the transmission unit are incorporated in the same device, for example, in a mobile telephone. The units can be logically different, that is, they can have a specified interface, for example, a mobile terminal and a determining device in accordance with the 3GGP specifications. It is also possible for the user equipment to comprise physically different devices, for example, the transmission unit can be a UMTS card or a mobile phone while the execution unit is part of another device that can be connected to the transmission unit, for example. example, a computer or a television with a wired or wireless connection to the transmission unit. In a preferable embodiment, the data packet is an IP Internet protocol data packet. This allows easy implementation of the method in existing networks. A session initiation signaling can be performed using a session protocol that is based on the IP protocol. Suitable protocols are, for example, the session initiation protocol (SIP) or the real time stream formation protocol (RTSP). Both protocols can be used in combination with the session description protocol (SDP). The routing level identification of the additional entity preferably comprises a destination address and / or a destination port number, such as an IP address and an IP port number. The packet bearer can be set at different times before or during the described method. Frequently, it is appropriate to establish the carrier simultaneously with the installation of the filter. In another mode, the bearer is established before the installation of the packet filter. It is also possible to establish the bearer before the establishment of a communication session in which the data packets are sent. In these cases, the packet filter can be installed in a modification procedure of the packet bearer. This mode is advantageous if the time required for the establishment of the carrier is long compared to the time for installing the filter. In a preferable embodiment, the packet filter associates the data packet with the packet bearer based on at least one additional parameter. In this way, a finer granularity of the mapping between data packets and bearer can be achieved, for example, to transmit packets with different quality of service or different charges. For example, the packet filter can evaluate additional fields in the packet header, for example, the source address, the source port number, additional header fields, for example a differentiated services code point (DSCP), the identification of protocol, or any combination of these parameters. A profitable communication network is adapted to perform a method modality in accordance with what is described above. A preferable control entity is adapted for a communication network with a user equipment. An application function of the user equipment is adapted to send a data packet in a data stream and a packet bearer can be established with the user equipment to transmit the data packet through the communication network to an additional entity . The user equipment is adapted to establish different packet bearers. The control entity comprises an input unit adapted to receive the flow with the data packet or information related to the flow. Accordingly, the control entity can either be part of the flow path or it can receive information related to the flow, for example, source and destination, from another identity in the network. A processing unit of the control entity comprises an identification function adapted to identify the flow. A policy function is adapted to determine the packet bearer for association with said flow from the different packet bearers, for example, according to rules specified by the network operator. By way of example, the operator can specify which packages from a specific source or for a specific destination are transferred in a carrier with specific parameters. In addition, the processing unit is adapted to determine a routing level identification of the additional entity with a determination function. Typically, a processing unit determines the routing level identification from a message received from an additional entity in the network. An output unit is adapted to instruct the user equipment in the sense of installing a packet filter based on the routing level identification, the filter or packet associates data packets comprising the routing level identification of the additional entity with the particular package carrier. The input and output unit may be incorporated in a common input / output unit. It is also possible for the control entity to instruct additional nodes to carry out the signaling. A profitable monitoring entity is adapted for use in a communication network with a user equipment. An application function of the user equipment is adapted to send a data packet in a data stream. The packet bearer is established with the user equipment to transmit the data packet in a communication network to an additional entity, and the user team is adapted to establish different packet bearers. The monitoring entity comprises an input unit adapted to receive a start message comprising a session level identification of the additional entity, the start message initiating the establishment of a communication session between the user equipment and the entity additional. Preferably, the monitoring entity is also adapted to receive a response message to the start message. A processing unit of the monitoring entity is adapted to monitor the messages and determine a routing level identification of the additional entity from the start message or from the response message. An output unit adapted to send the start message to the additional entity using the session level identification and to send the response message to the user equipment. The monitoring entity is further adapted to transfer the determined routing level identification to a control entity to instruct the user equipment to install a packet filter based on the identification of the routing level, where the packet filter associates the data packets comprising the routing level identification of the additional entity with the particular packet bearer. A beneficial monitoring entity comprises a memory for storing information related to the communication session. The invention can also be incorporated into a software program comprising a code for performing the steps of the method in relation to the device in which the program is executed. It is preferably executed in a control entity. A profitable program for associating a data packet with a packet bearer in a user equipment is adapted for a communication network in which the data packet is sent in a data stream from an application function of the user equipment . The packet bearer is established with the user equipment to transmit the data packet in the communication network to an additional entity. A user equipment is adapted to establish different packet bearers, a routing level identification is provided to the application function, and the routing level identification is included in the data packet. The last steps can be carried out during and after the execution of the program. The program comprises a program code to identify the flow with the data packet in a control entity of the communication network. It determines the packet bearer for association with said flow from the different packet bearers. It also determines the routing level identification of the additional entity, optionally from the information received from another entity in the communication network. The program initiates an instruction to the user equipment to install a packet filter based on the routing level identification, wherein the packet filter associates data packets comprising the routing level identification of the additional input with the bearer of certain packages. The program according to the present invention is stored, for example, in a data carrier or can be loaded in a processing unit of a user equipment or a control device, such as for example a sequence of signals. The control entity, the monitoring entity and the software program can be adapted to any modality of the method described above. The foregoing as well as other objects, features and advantages of the present invention will be more apparent in the following detailed description of the preferred embodiments illustrated in the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS FIGURE 1 shows a architecture to provide a defined quality of service in a mobile system. FIGURE 2 shows the cooperation of nodes in a mobile system in which the invention is incorporated. FIGURE 3 shows devices that perform the method to associate data packets with carriers. FIGURE 4 shows a 'signaling diagram to implement the proposed method. FIGURE 5 shows an additional signaling diagram to implement the proposed method. FIGURE 6 shows a third signaling diagram to implement the proposed method. FIGURE 7 shows a fourth signaling diagram to implement the proposed method. FIGURE 8 shows a control device adapted to carry out the proposed method. FIGURE 9 shows a monitoring device adapted for use in the proposed method. DETAILED DESCRIPTION OF PREFERRED MODALITIES FIGURE 1 illustrates a concept of quality of service in third generation mobile systems in accordance with the specification in the 3GPP 23.107 V 6.3.0 technical specification of the Generation Partership Project. Traffic comprising data packets is sent between an additional entity (AF) and a user equipment comprising a terminal equipment (TE) and a mobile terminal (MT). The additional entity (AF) can be a server that can be found in the operator network or in an external network but can also be another user equipment. The purpose of the concept is to provide a quality of service (QoS) defined at the application level using the bearer services of the underlying levels. These bearer services are specified by contexts comprising attributes to define the QoS of the respective bearer service. Since the end-to-end service quality in the application layer depends on the specifications of the underlying levels, the contexts of bearer services must be specified in relation to the end-to-end quality of service required. The local bearer service TE / MT sends the data packets with the user equipment between the terminal equipment (TE) and the mobile terminal (MT). Accordingly, the terminal equipment (TE) and the mobile terminal (MT) can be part of a single device or they can be incorporated into different devices using communication through the local carrier service TE / MT. The data packets are received or sent through a radio link with the radio access network (RAN1) of the mobile network. The External Bearer Service is provided by another network that can also be a UMTS (Universal Mobile Telephone System) network, that is, a network in accordance with 3GGP specifications, another mobile network or a fixed network, such as a fixed communication system such as Internet. The external bearer transfers data packets between the additional entity (AF) and an edge node (CN-GW) of the central network of the mobile network. The central network also comprises a central network node (CN1) that controls the transfer of packets between the central network and a radio access network (RAN1). The edge node (CN-GW) and the core network node (CN1) can be the same node. The traffic of data packets through the mobile network is sent through a Radio Access Carrier Service between the mobile terminal (MT) and the central network node (CN1) and through a Central Network Carrier Service between a Compuerto node (CN-GW) and a central network node (CN1). These services are offered in turn by a radio bearer service on the radio link between the user equipment and the radio access network (RAN1), a RAN Access Carrier Service between the radio access network ( RAN1) and the central network node (CNl) and a Structural Carrier Service within the central network. Finally, all services depend on several different physical bearer services in the respective links, that is, typically several contexts and services are related to individual links in a transmission. FIGURE 2 shows an example of a transmission of data packets using the proposed method with contexts and nodes involved. For the transmission of the data packets, a PDP context (PDP) is negotiated between the user equipment (UE1) and a central network node, here an SGSN (SGSN1). The transmission is carried out later through the central network node and access node or at least controlled by them. The dotted line 11 indicates a possible route in which the packets are transferred in the uplink and downlink direction between the user equipment (EU) and the additional entity (AF). A control entity (PCRF) has interfaces to communicate with a GGSN (GGSN1 as an edge node and with the additional entity (AF).) The establishment of the PDP context can be initiated, for example, by a corresponding request (RQ1) of the user equipment to the SGSN. It is also possible that the network (for example, the GGSN) requests the establishment of the PDP context (PDP), for example through a message to the user equipment that then initiates the sending of a request (RQ1) to activate a PDP context. The PDP context comprises attributes that will define the quality of service for the transmission of packets. The establishment of a radio bearer (RB) is typically included in the establishment of a PDP context. For this purpose, the SGSN (SGSN1) sends a request (12) for the establishment of a radio bearer (RB) to the access node, in the example an RNC (RNC1) The transmission of the data packets in the link radio to the user equipment is effected for example through a node B (NB) controlled by the RNC using radio resource control signaling (13). It is also possible to integrate the functionality of node B and RCN into a single node. The SGSN also sends a request (14) to an edge node of the core network, here a GGSN (GGSN1), for the establishment of a central network bearer. The configuration of the different nodes can be carried out from an operation support system (OSS) in signaling links (SIG). FIGURE 3 illustrates the basic concept of the proposed method for the example of a UMTS network. In the network, a GGSN as an edge node (EN2) and a Radio Access Network (RAN) offer two carriers with different characteristics that are known as Carrier A and Carrier B. The carriers can differ in many different ways. Two examples of the characteristics would be the QoS associated with the bearers or the charging policy associated with data packets transmitted through the bearer. The GGSN comprises downlink packet filters (DL PF) that map packet flows generated by different services on the bearers. To indicate the association of packet and carrier filters, both are indicated by interrupted lines for carrier A while carrier B and associated filters are indicated in solid lines. A packet flow is a group of data packets with the same source, destination and protocol. For example, an IP stream consists of data packets with the same source address, source port, destination address, destination port, and protocol identification. In the example, a first service (Srvl) generates two application flows, and a second service (Srv2) generates a flow of applications that are mapped on the bearers by the downlink packet filters (DL PF). The data packets that come from the services require different carriers and therefore they are also indicated in interrupted and continuous lines, corresponding to the carrier to which they are transferred by the downlink filters (DL PF). Two application functions (Appl, App2) are executed in the user equipment (UE2) consisting of a personal computer as the executing unit (EU2) and a mobile telephone as a transmission unit (TU2). The first Appl application function generates two flows of data packets, each with characteristics that require different treatment in the network. This is indicated again by interrupted and continuous lines that correspond to the line of the carrier they will use. Likewise, the data packets (DP, DP ') are indicated in continuous and interrupted lines corresponding to the respective carrier. Examples of applications that generate several packet flows are multimedia applications and presence applications that combine, for example, an IP voice service with other services, for example video, chat, dashboard and file sharing. A second App2 application function generates only a single stream of data packets. The proposed method offers a mechanism for mapping between data packet flows and bearers. Even though the example describes a user equipment divided with different devices, the method is also applicable if the applications are executed in a device comprising both the execution unit and the transmission unit. The execution unit marks the data packages of the different application flows with the destination for which it is contemplated. In the example, this is achieved through the network that instructs the execution unit to mark the different application flows with the particular combination of a destination IP address and a destination port number through a signaling of application-layer using, for example, SIP / SDP. In general, the signaling functionality of a routing level identification can be part of any session level protocol. Package filters (UL PF) are established in the transmission unit and offer a packet matte in the different carriers with which the filters are associated. In the proposed solution, this is achieved by installing the filter network as part of the session management protocol procedures, for example, establishing the PDP answer or modifying. The filters use routing level identification, for example, the combination of destination IP address and port number for the packet matte on the bearers. It is possible that other parameters are reviewed in addition to the packet filters. For example, an additional filtering can be based on the source address, the source port number, a differentiated services code point (DSCP), the protocol identification, additional fields in the IP header or any combination of these parameters. This allows a finer granularity of the mapping. Using the uplink filters, the network can control the association of an uplink data packet with one of the multiple packet bearers in a user equipment of one. communication network, wherein the uplink data packet originates from an application function, and the packet bearer is established between the user equipment and the network infrastructure. The method? Identifies a flow of uplink data packets under control and determines the packet bearer to be associated with said uplink packet flow. This determination is made in the network. The routing level identification of said uplink data packet flow is also identified in the network. The association of the routing level identification with the given packet bearer is provided to the user equipment. The uplink data packet is associated with the packet bearer determined on the user equipment ^ based on the association provided from the network. The steps of identifying a flow subject to control and the determination of the packet bearer can be based on operator policy rules. A preferable routing level identification is the 5-tuple IP stream a sub-group of the 5-tuple IP stream, in particular the destination IP address and the destination port number. The uplink data packet flow identification and the related routing level identification are preferably based on the analysis of flow descriptions included in session level generalization messages sent between the application function and the receiving application entity, for example, based on protocols that use SDP, such as SIP 0 RTSP. The routing level identification may be included in a session level signaling message intended for said application function, in the form of the destination IP address and port number to be used in uplink data packets from the Application function. The provision of the routing level identification association with a packet bearer can be performed in the establishment of the packet bearer. Alternatively, provision may be made for a packet bearer that has already been established. Figures 4-6 show examples of signaling sequences for installing a packet filter in a user equipment during the establishment of a SIP-based session in a 3GPP recommissioning network. Similar sequences could also be applied to RTSP / SDP sessions. It is considered in the examples that the PDP context used to carry out the SIP signaling is already established when the session starts. The preceding signaling to establish this PDP context is therefore not shown. PDP Contexts can be established, for example, according to a request from the network, for example, an Activation PDP Context Requested by the Secondary Network (SNRPCA).

Correspondingly, a signaling, SNRPCA can be used to install the packet filters in the user equipment. In all examples, both the user equipment and the additional identity are a user equipment of a 3GPP communication system, i.e., the session is established between originating mobile user equipment and a terminating mobile user equipment, both connected to a 3GPP network. In many other cases, at least one of them will be in another type of network, for example, in a fixed network. The originating network and the terminating network can be connected by one or more intermediate networks that transfer the signaling between the networks in accordance with that indicated by a rectangle. Aspects of the signaling sequence can be changed, for example, according to future standardization of the messages. The SIP / SDP signaling is used to give instructions to user equipment, here, IMS clients (IP Multimedia Subsystem), in the sense of how to mark the data packets. With regard to the designation of information elements in the displayed messages, addresses and port numbers are designated from the perspective of the respective side, that is, the source (src) of the A side is the destination (dst) of the B side and vice versa . Both user equipment comprises a mobile terminal (MT A, T B) and a terminal equipment (TE A TE B) the signaling sequences do not require signals between the mobile terminal and the terminal equipment. Therefore, they are applicable even if there is no control interface between these two entities. An AGPRS Support Node (GSN A, GSN B,), for example, a GSN gateway, is the edge node of the mobile core network in the examples. A SIP signaling is transferred and inspected by a node designated as the IMS core A, IMS B core as a monitoring entity. In a typical 3GPP network, this may be the P-CSCF (Call-Proxy Status Control Function). Policies, for example for admission control and charge rules defined by the operator, are applied by a Policy Function Load Rules (PCRF A, PCRF B) as a control entity. In the example of Figure 4, the packet bearer to carry the data packets of the session initiated with the associated PDP context has been established before the start of the session. The corresponding signaling is therefore not shown. The following signaling messages in the diagram are described in detail. 1. The TA A terminal sends a SIP INVITE message to the IMS Core A node. The message includes SDP parameters that contain the IP address and port number to be used on the A side of the session. The IMS Core A node monitors SIP traffic. The IMS Core A node sends an AAR (Authorization Authentication Request) message to control the PCRF A entity, which contains the IP address and port number to be used on the A side of the session and a Service Identifier with which the PCRF can identify the service invoked. A control entity PCRF A sends an "Install PCC Rule" message to the edge node GSN which indicates what kind of QoS should be used for the bearer to transport packets from this service. PCRF A includes the IP address and port number to be used on the A side of the session that can be used to control the gate in the core network, and optionally a GBR (Guaranteed Bit Rates) value that can be used to carry out the admission control in the access network. A procedure is performed to modify RAB (radio access bearer) where resources are reserved for specified GBR and QoS class. If the procedure is successful, that is, the resources can be reserved in the radio access network RAN A, the establishment of the session is carried out. Sending an AAA message (Authorization Authentication Response), the IMS Core A node transfers the SIP INVITE message received in Step 1 to the IMS Core B node, optionally through one or several intermediate networks. Upon receipt of the SIP INVITE message, the IMS Core B node sends an AAR message to the control entity PCRF B, which contains the IP address and port number to be used on the A side of the session and a Service Identifier with the which the PCRF B can identify the invoked service. The control entity PCRF B sends an "Install PCC Rule" message to the edge node GSN B which indicates which QoS class should be used by the bearer to carry packets from this service. PCRF B includes the IP address and the port number to be used on the A side of the session, which are contemplated to be used by the terminal equipment TE B in the packet filter. They can also be used for control of gate and filtering in the core network, for example, GSN B. In the message a GBR (guaranteed bit rate) value can be included to carry out a transmission control in the access network. An RAB Modification procedure is performed, where resources are reserved for any specified GBR and QoS class if this procedure is successful, that is, if resources can be reserved in radio access network RAN B, the establishment of the session proceeds. A procedure for modifying the PDP Context associated with the media bearer is initiated. This procedure installs the packet filter that selects packets in accordance with the destination IP address and port number in the TE terminal equipment B. The IMS Core B node sends the SIP INVITE message to the TE terminal equipment B. The parameters SDPs contain the IP address and port number to use on the A side of the session. Correspondingly, they can be inserted into data packets that originate from an application function that is TE B. If the application function that has been initiated requires user acceptance, the IMS client TE B timbra or provides another indication of the user that a session should be established. Other sessions can be initiated without user confirmation. When the user confirms the establishment of the session, for example, taking on TE B, a SIP 200 OK message is sent from TE B to IMS Core B. This message contains the IP address and port number to be used on the B side of the session. The IMS Core B node sends an AAR message to control the PCRF B entity, which contains the IP address and port number to be used on the B side of the session. . The PCRF B sends a "Modify PCC Rule" message to the edge node GSN B containing the IP address and port number to be used on the B side of the session as well as the QoS class to be used for the session. This information can be used GSN B to carry out a gate control and filtering of incoming packets. After receiving the transferred SIP 200 OK message, the IMS Core A node monitors the message content and sends an AAR message to PCRF A, which contains the IP address and port number to be used on the B side. The PCRF control node A sends a "Modify PCC Rule" GSN A message containing the IP address and port number to be used on the B side of the session as well as the QoS class authorized for the session. This information can be used in GSN to perform gate control and filtering of incoming packets. . A procedure is initiated to modify the PDP Context associated with the media bearer. This procedure installs the packet filter containing the destination IP address and the port number in terminal equipment TE A. 17. The IMS Core A node transfers the SIP message 200 OK TE A. The SDP parameters in this message contain the IP address and port number to use on the B side of the session. Correspondingly, they can be inserted into the data packets that come from an application function found in TE A. Finally, an acknowledgment of the successful establishment of the session is sent among the teams of several involved. In summary, on the A side, an uplink packet filter is installed using the PDP context modification procedure, once the destination IP address and port are known, that is, after receiving the SIP 200 OK message includes this information from side B. On side B, the uplink filter can be installed, with the PDP context modification procedure directly, since the destination IP address and port are known from the message SIP INVITE. The RAB to RAN modification signals in steps 4 and 8 are only relevant if reservation of resources is required. If the reservation of resources in RAN is not used, the RAB modification signals can be omitted from the signaling.

Several associations are possible for the packet filter that can be used for example to map packets in carriers with different QoS characteristics. Further. Packages can be mapped to different APNs or charged differently. Combinations are also possible. The above method can also be used for other access networks apart from the 3GPP network in the example above since the application layer signaling protocol is agnostic for access. Only the signaling used for the installation of the uplink packet filter has to be adapted to the different access network. A main advantage of the method is that applications executed in the user equipment do not require to support specific procedures in API to manage the quality of service any communication with lower layers is done through a standard API plug. This means significantly the development of applications. Figure 5 shows an example in which the media carrier is established during the establishment of the session. Only selected messages are described while several messages serving the same purpose as the corresponding messages in Figure 4 are shown in Figure 5 without repeating in the text below. The following asos are carried out. . The terminal TE TE A sends a SIP INVITE message to IMS Core A. The message comprises SDP parameters containing the IP address and the port number to be used on the A side of the session. . An SNRPCA procedure is initiated on the A side to request the establishment of a PDP context or the mobile terminal MT A. In this procedure, an uplink packet filter can not be installed TE A, since the destination IP address and port number are still unknown. . As part of the PDP context activation, a RAB is established. A resource reservation procedure can also be performed in RAN A. An additional SNRPCA procedure is initiated on the B side to request the establishment of a PDP context by the mobile terminal TE B. In this procedure, an uplink packet filter TE B is installed to select conformance packets with a destination IP address and port number. . RAB is set on the B side as part of the SNRPCA procedure. . The IMS Core B node transfers the SIP INVITE message to TE B. The SDP parameters contain the IP address and port number to be used on the A side of the session.

Correspondingly, they can be inserted into the data packets that come from an application function that is TE B. 7. The SIP 200 OK message contains the IP address and port number to be used on the B side of the session. This message is transferred to the IMS Core A node on the A side. 8. Once the IP address and port number to be used on the B side of the session are received in GSN A, the Modify PDP procedure can be activated. This procedure updates the PDP context with the uplink packet filter based on the destination IP address and the port number. 9. IMS Core A transfers the SIP 200 OK message to TE A. The SDP parameters in this message contain the IP address and the port number to use on the B side of the session. Correspondingly, they can be inserted into the data packets that come from an application function that is TE A. In summary, on the A side the bearer is established using an SNRPCA procedure before the parameters required for the installation of the packet filter. uplink are available. Since the destination IP address and the port to be used on the B side are not known until after receipt of this B side information, the uplink filter is subsequently updated in the sequence using a modification procedure of PDP context. On the B side, the bearer is established and the uplink packet filter is installed during this procedure, since the IP address and port are known from the SIP INVITE message. Figure 6 shows a third signaling sequence for the installation of an uplink filter. As in the previous example, only messages selected in the sequence are described while the purpose of other messages in the figure corresponds to those in Figure 4. In this example, the uplink packet filter on the A side is installed together with the installation of the carrier. The following steps are carried out. 1. The TE A terminal sends a SIP INVITE message to the IMS Core A node. It includes SDP parameters with the IP address and port number to be used on the A side of the session. This message is transferred to IMS Core B without making a reservation of reces in the radio access network or establishing a carrier. 2. An SNRPCA procedure is initiated on the B side. In this procedure, an uplink packet filter is installed on TE B to select conformance packets with destination IP address and port number. A RAB is established on the B side as part of the SNRPCA procedure. The IMS Core B node transfers the SIP INVITE message to TE B. The SDP parameters contain the IP address and port number to be used on the A side of the session. Correspondingly, they can be inserted into the data packets that come from ^ an application function that is located in TE B. The SIP 200 OK message contains the IP address and port number to be used on the B side of the session. This message is transferred to the A side. Once the IP address and port number to be used on the B side of the session are received in GSN A, an additional SNRPCA procedure is activated to establish a PDP context on the side A. The procedure also installs an uplink packet filter to select conformance packets with destination IP address and port number. A RAB is established on the A side. If no reservation of reces is used in the RAN, it is not required a GBR value in this message. If reservation of reces is used, a GBR value can be included. The IMS Core A node transfers the SIP 200 OK message to TE A. The SDP parameters in this message contain the IP address and port number to be used on the B side of the session. Correspondingly, they can be inserted into the data packets that come from an application function found in TEA. In this example, both on the A side and on the B side, the uplink filter is installed together with the establishment of the bearer using a PDP context activation requested by network. Correspondingly, the establishment of a bearer on the A side is delayed until reception of the information on the destination IP address and port number starting on the B side. The example of Figure 7 shows a signaling sequence in which the filter of a preset carrier is modified to load content. As in the case of the preceding examples, the user equipment comprises a TE terminal equipment and a mobile terminal MT and the data transmission is effected through a GSN and controlled by a PCRF. Before the start of the illustrated sequence, a packet bearer has been established between the network and the user equipment. Initially, the user is browsing, for example, visiting sites on a WWW server. Data packets transmitted during navigation are mapped to a bearer with QoS by default. The user activates the loading of a file from a user equipment to a load server, for example, a webblog server. File loading is initiated with the default QoS but the data packets correspond to a new flow. A control entity in the network, for example, GSN or another node in the operator's network detects the new flow, for example, through identification that is directed to a specific IP address or URL. According to the user's subscription, a rule is activated in the control entity that determines that an uplink flow to the specified IP address or URL must be mapped to a higher QoS. The control entity then initiates an update of the uplink packet filter on the user equipment. In the example shown, this is done using a procedure to modify PDP. Alternatively, the modification of PDP can be replaced with a procedure for establishing an additional PDP context, for example an SNRPCA sequence. In both cases, the load preferably proceeds in parallel, using the QoS by default. When the filter in the user equipment is updated, the load continues in a carrier with a higher QoS. This ensures priority over other traffic from the user equipment and other entities in the network. A control entity in accordance with the present invention is shown in Figure 8. initiates the association of a data packet with a packet bearer in a user equipment of the communication network where the packet bearer is adapted to transmit the data package to an additional entity. The control entity comprises an input unit (IUC) for receiving information (INF) related to the flow for the data packet. A processing unit (PUC) is adapted to identify the flow in an identification (IF) function. For example, the identification (IF) function can evaluate the message (INF) for this purpose. A policy function (PF) is adapted to determine the packet bearer for association with said flow from the carriers of different packets available to the user equipment. Preferably, the control device comprises a memory with rules defined by operator (OR) as the basis for the determination. A determination function (DRI) determines a routing level identification of the additional entity. The determination function (DRI) may for example also evaluate the information message (INF) or another message comprising this information. An output unit (OUC) is adapted to instruct the user equipment to install a packet filter based on the routing level identification, the packet filter associates data packets comprising the routing level identification of the additional entity with the particular package carrier. The instruction is preferably carried out by an instruction message (IM) to the user equipment. Figure 9 shows a monitoring entity for a communication network with a user equipment. The monitoring entity comprises an input unit (IUM) adapted to receive a start message (INV) comprising a session level identification of the additional entity. The start (INV) message initiates an establishment of a communication session between the user equipment and the additional entity. The input unit (IUM) is preferably also adapted to receive a response message (REP) to the start message. It is not necessary for a response message to be sent through the monitoring entity and received by the monitoring unit if the start message comprises all the information required to perform the proposed method, such as the SIP message invite in the side B of the modality in Figure 4. A processing unit (PUM) is adapted to monitor the messages in a monitoring function (MF) and to determine a routing level identification of the additional entity from the start message (INV) or from the response message (REP). An output unit (OUM) is adapted to transfer the start message to the_, additional entity using the session level identification and, if required, to transfer the response message (REP) to the user equipment. The monitoring entity is further adapted to transfer the determined routing level identification to a control entity to instruct the user equipment to install a packet filter based on the routing level identification. For this purpose, a notification (NOT) can be sent through the output unit (OUM) to the control entity. Preferably, the monitoring entity comprises a memory (MEM) for storing information related to the communication session. The information allows especially the association of a start message (INV) and a response message (REP) between them and the session. The units and functions of the control entity and the monitoring entity can be incorporated as an electronic circuit or optical circuit or as software executed in each circuit. The input and output units of both devices can be integrated into a common Input / Output unit. The embodiments indicated above admirably achieve the objects of the invention. However, it will be appreciated that persons skilled in the art can exit them without departing from the scope of the invention limited only by the claims.

Claims (17)

1. CLAIMS 1. A method for configuring link layer entities (92, 94) for a transfer, the link layer entities (92, 94) receive service data units of a higher functional layer, convert the data units of service in protocol data units and place the protocol data units in buffer memory for transmission to a receiver (96) under the regime of an ARQ protocol having status reports, the status reports indicate receipt of one or several protocol data units in the receiver (96), the method comprises the steps of: receiving from a receiver (96) of protocol data units a supplementary status report for an existing ARQ connection (98) in relation to a imminent transfer; - determine units of service data that correspond to protocol data units placed in buffer memory taking into account the information included in the supplementary status report; and - transferring the determined service data units to a link layer entity (94) which is to establish a new ARQ connection (100) with the receiver (96); wherein the method further comprises a step of requesting the supplementary status report from the receiver (96).
2. 2. The method according to claim 1, further comprising the step of suspending the transmission of protocol data units in a close temporal relationship with the receipt of the supplementary status report. The method according to claim 1 or 2, wherein at least one of the steps of requesting and receiving the supplementary status report is carried out through one or several radio resource management messages. The method according to any of claims 1 to 3, wherein the step of requiring the supplemental status report is initiated upon receiving a notification regarding an impending transfer. The method according to any of claims 1 to 4, wherein the step of requiring the supplementary status report includes sending a link layer request message dedicated to the receiver (96). The method according to any of claims 1 to 5, wherein the step of requiring the supplementary status report is implemented in a transfer environment on the receiver side (96). The method according to any of claims 1 to 6, wherein the step of requiring the supplemental status report comprises the generation of a requirement that instructs the receiver (96) to transmit the supplemental status report. The method according to any of claims 1 to 7, wherein the step of determining the service data units excludes the service data units corresponding to protocol data units correctly received in the receiver (96) . The method according to any of claims 1 to 8, wherein the step of determining the service data units corresponding to protocol data units placed in buffer memory comprises the reconstruction of service data units from of the protocol data units placed in buffer memory. The method according to any one of claims 1 to 9, wherein the step of determining service data units that correspond to protocol data units placed in buffer memory comprises the selection of service data units from a buffer The method according to any of claims 1 to 10, wherein the step of requiring the supplementary status report comprises the generation of a requirement in which the receiver (96) is instructed to unconditionally generate the report of supplementary status. The method according to any of claims 1 to 11, further comprising the step of buffering the service data units before conversion. The method according to claim 12, further comprising the steps of: - creating a data context from all the service data units placed in buffer memory and all the service data units determined; and - transferring the data context to the link layer entity (94) which must establish the new ARQ connection (100) to the receiver (96). 14. A computer program product comprising portions of program code for performing the steps of the method according to any of claims 1 to 13, when the computer program product is used in a computing device. 15. The computer program product according to claim 14, stored in a computer readable recording medium. 16. A device (80) for configuring link layer entities (92, 94) for a transfer, the link layer entities (92, 94) receive service data units of a higher functionality, convert the units of service data in protocol data units, and buffer the protocol data units for transmission to a receiver (96) under the regime of an ARQ protocol having status reports, the status reports are an indication of the reception of one or more protocol data units in the receiver (96), the device (80) comprises: - a first interface (82) adapted to receive from a receiver (96) of protocol data units a report of supplementary status for an ARQ connection (98) existing in context with an impending transfer; - a mechanism (84) adapted to determine service data units corresponding to protocol data units placed in intermediate memory taking into account the information included in the supplementary status report; - a second interface (86) adapted to transfer the service data units determined to a link layer unit (94) that is to establish a new ARQ connection (100) to the receiver; wherein the device is further adapted to require the report of supplemental status of the receiver (96). A system (90) comprising the device (80) of claim 16 in communication with one or more link layer entities (92, 94), and a receiver (96) having a report mechanism adapted to generate reports of supplementary states. SUMMARY OF THE INVENTION A method for associating a data package is described (DP) with a packet bearer (PB) in a user equipment (UE1) of a communication network. The data packet is sent in a data stream from an application function of the user equipment, the packet bearer (PB) is established with the user equipment to transmit the data packet (DP) in the communication network to an additional entity, and the user equipment is adapted to establish different packet bearers. The method comprises the steps of identifying the flow with the data packet in a control entity of the communication network, determining the packet bearer for association with said flow from the carriers of different packets in a policy function of the control entity, determine a routing level identification of the additional entity, instruct the user equipment to install a packet filter based on the routing level identification, wherein the packet filter associates data packets comprising routing level identification of the additional entity with the given packet bearer, provide the routing level identification to the application function, including the routing level identification in the data packet, and transfer the data packet ( DP) in the given packet bearer (PB). A corresponding network, control entity, monitoring entity and computer program are also described.