EP1867111A1 - Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises - Google Patents

Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises

Info

Publication number
EP1867111A1
EP1867111A1 EP06708700A EP06708700A EP1867111A1 EP 1867111 A1 EP1867111 A1 EP 1867111A1 EP 06708700 A EP06708700 A EP 06708700A EP 06708700 A EP06708700 A EP 06708700A EP 1867111 A1 EP1867111 A1 EP 1867111A1
Authority
EP
European Patent Office
Prior art keywords
data
control node
data stream
information
packet filter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP06708700A
Other languages
German (de)
English (en)
Inventor
Peter Braun
Friedrich Grosse-Rhode
Dorothea Lampe
Mirko Schramm
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Nokia Siemens Networks GmbH and Co KG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Siemens Networks GmbH and Co KG filed Critical Nokia Siemens Networks GmbH and Co KG
Publication of EP1867111A1 publication Critical patent/EP1867111A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/15—Flow control; Congestion control in relation to multipoint traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/765—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
    • H04L47/767—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points after changing the attachment point, e.g. after hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/788—Autonomous allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/808—User-type aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/824—Applicable to portable or mobile terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/088—Access security using filters or firewalls
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints

Definitions

  • the invention relates to a method, a control node and a system for determining the assignment of data streams to payload connections by notifying the control node of a communication network by a fürsfunk- tion and by a terminal and the evaluation of the available information in the control node and the subsequent authorization of the user connection.
  • SBLP service-based local policy
  • GPRS General Packet Radio Service
  • the GPRS payload connections are point-to-point connections and are also referred to as "Packet Data Protocol” (PDP) contexts: the setup and the modification of PDP contexts initiated by the mobile terminal, the so-called “user equipment” (UE) is authorized on the so-called “Gateway GPRS Support Node” (GGSN) via the so-called “Go” interface of the so-called “Policy Decision Function” (PDF), which knows the services currently used by the terminal. The PDF is informed about these services by one or more so-called “Application Functions” (AF), which are used with the terminal to negotiate the
  • PDP Packet Data Protocol
  • UE user equipment
  • GGSN Gateway GPRS Support Node
  • PDF Policy Decision Function
  • the PDF is informed about these services by one or more so-called “Application Functions” (AF), which are used with the terminal to negotiate the
  • IP Multimedia Core Network Subsystem IP Multimedia Core Network Subsystem
  • IETF RFC 3261 IP Multimedia Core Network Subsystem
  • QoS Quality of Service
  • the PDF knows which IP streams belong to a service.
  • a data stream is to be understood here as a sequence of data packets with the same sender and recipient address as well as the same type of user data transported therein.
  • the IP data stream should additionally be characterized by the same UDP or TCP port numbers of sender and receiver. It is possible that a terminal sets up and uses several PDP contexts for GGSN at the same time. To authorize a PDP context, the PDF must therefore know which IP data streams are transported in each case.
  • the SBLP solution standardized so far in TS 29.207, which enables the PDF to detect which IP data streams are transported in a PDP context, uses the so-called "authorization token.”
  • This token is used for a service session of the PDF on demand
  • the terminal uses the token and so-called "Flow Identifier", ie additional indices that indicate the IP data stream within the service, to assist in setting up and changing a PDP context in the service corresponding signaling for which IP data streams the PDP context should be used.
  • Authorization tokens and flow identifiers are collectively referred to as "Binding Info.”
  • the GGSN passes this information from the PDP context signaling via the Go interface to the PDF.
  • the use of the authorization token has a number of disadvantages. So must the signaling between the application function and the terminal support the transport of the token, which is currently the case only for the SIP signaling. Also, the signaling associated with the payload in the access network must support the transport of the Binding Info, which is true for the PDP contexts of the GPRS, but not for alternative access networks that are of interest in the 3GPP, such as WLAN or DSL. For GPRS, there is the restriction that the first PDP context built by the terminal does not support binding info, and therefore the terminal will receive further PDP upon receipt of a token
  • the establishment or modification of a PDP context is triggered by the terminal by means of standardized signaling in TS 29.060.
  • the terminal notifies the GGSN by means of packet filters in the so-called "Traffic Flow Template” (TFT, coding according to TS 24.008) how IP data streams received from the IP core network are to be distributed to PDP contexts for further transport to the terminal.
  • TFT Traffic Flow Template
  • the object of the invention is to propose a simple and efficient possibility for determining the assignment of data of at least one data stream to a user connection and for providing the resources.
  • a core of the invention is to be seen in that for determining the assignment of data streams to payload connections, a control node of a communication network is controlled by an application function, a network unit, for example a gateway network. GPRS support node (GGSN), a packet gateway network unit, etc., and notified by a terminal.
  • the network unit sends at least one packet filter information received from the terminal, for example a TFT packet filter, concerning the user connection to be used for the transmission of data of at least one data stream together with at least one attribute to the control node.
  • an application function sends at least one piece of information, for example a media IP flow information regarding the data of at least one data stream to be sent to the control node.
  • the control node compares the at least one packet filter information, the at least one attribute and the at least one information from the application function with each other and decides whether the user connection to be used, for example a PDP context, for the data to be sent at least one Data stream can be authorized. In a positive comparison, the control node authorizes the data of at least one data stream for the payload and, for example, sends at least one gate for installation to a network unit and determines the quality of the service for the data of the at least one data stream.
  • the terminal sends the at least one packet filter information directly to the control node.
  • the network unit would separately send the at least one attribute, for example, the PDP address, the QoS information, the MSISDN, etc., to the control node.
  • a solution is also proposed which provides a clear service Suggests identification and authorization based on minimal information of the transport layer.
  • the information according to the invention receives information such as a change in bandwidth, errors or resource problems in a transport layer network unit (eg, terminal, GGSN, etc.) This information can be used, for example, to inform the application function and to redistribute the resources, thereby allowing the user of a terminal to use a service with the maximum approved quality of the service.
  • a memory element for example a database
  • resource decision rules for the allocation of a data stream to a useful connection could be stored, which are taken into account in the assignment in the case of a positive comparison result according to the invention.
  • the at least one attribute and the at least one packet filter information could be stored for, for example, a later use.
  • An application server or an application function (for example a service server, a P-CSCF (Proxy Call State Control Function)) provides the control node with information, for example media IP flow information, in the case of a service provider.
  • the terminal must have a user connection, for example a
  • a terminal can be a mobile terminal, a mobile computer, a mobile organizer, a computer, etc.
  • a communication network a cellular mobile network, a packet-switched communication network, an IP network, a WLAN network, etc. may be used.
  • a network unit of the communication network controls and monitors the IP data traffic between the terminal and another terminal or between the terminal and an application function.
  • the gateway GPRS support node is used as the network unit.
  • the payloads in a GPRS network are generally referred to as PDP contexts. Generally, a payload is considered a logical channel with individual resources.
  • An advantageous embodiment of the invention is the dynamic reallocation and re-authorization of resources in a modification of the active service or Nutzverbin- Phyg, as well as the rebuilding of another user connection.
  • transport layer information for example, the priority of the IP packet filter, the quality of the service, etc.
  • An advantage of the invention is that the implementation effort for the individual network elements, such as the terminal, the control node, the network unit, etc., can be kept low. In particular, for the terminal no behavioral changes are needed, although a certain way of filling the TFT packet filters can optimize the allocation mechanism.
  • the invention will be explained in more detail with reference to an embodiment shown in a figure. Show
  • FIG. 1 shows the method according to the invention with reference to a simplified network architecture
  • FIG. 2 shows a table for the comparison according to the invention
  • FIG. 3 shows an example of the re-authorization
  • FIG. 4 shows two tables for the re-authorization according to the invention
  • FIG. 5 shows a device according to the invention.
  • FIG. 1 shows the method according to the invention with reference to a simplified network architecture.
  • Terminal IP address Destination terminal IP address of the terminal in downlink direction, ie from the IP core network to the terminal.
  • IP address 64 bit address prefix for IPv6 that the GGSN assigns to the PDP context and to the particular terminal.
  • Application function connection or AF connection (AF session): Set up by an application level signaling protocol offered by the application function and a prerequisite connection setup (session set-up) with explicit description of the connection before use of the service.
  • Media IP Flow Information A data stream of an application function connection described by a packet filter.
  • the flow identifier with a media component associated with the application function connection is used to identify the media IP flow information.
  • the medium described by the media component may be bi-directional or unidirectional. Therefore, a stream identifier identifies either one stream (for one unidirectional media component) or two streams (for one bi-directional media component).
  • a unique terminal identifier for example, a terminal IP address, a MSISDN, etc.
  • a unique terminal identifier for example, a terminal IP address, a MSISDN, etc.
  • Uplink and “downlink” data streams with the same data stream identifier are assigned to the same PDP context (for example, RTP and / or RTCP are associated with “uplink” and “downlink” data streams in the same PDP context)
  • PDP context attributes such as the PDP address, the TFT filters, the QoS information, the MSISDN, etc.
  • PDP context attributes are compared with the information (data stream information) of an application function AF.
  • the UE determines with a TFT packet filter in a GPRS network according to an internal decision which service should use which PDP context.
  • the TFT packet filters are not used for the assignment of the "downlink" data stream to PDP contexts by the network unit GGSN, but they are forwarded to the control node PS by the network unit GGSN, whereby received gates are received by the network unit GGSN installed for the assignment of data streams According to the already standardized
  • SBLP installs the control node so-called "gates" at the GGSN for the SBP controlled PDP contexts
  • a "gate” includes a packet filter as well as information for the GGSN to discard or hand over appropriate IP packets, ie how data is handled should. The more detail information contained in the TFT packet filters, the better authorization can be made for the QoS requirements of the service.
  • the network unit GGSN sends all available PDP context attributes, such as the PDP address, the TFT packet filters, the QoS
  • the control node PS stores these attributes for each PDP context in a storage element of the control node PS.
  • the PDP attributes can be used for the comparison according to the invention.
  • the media are matched by IP flow filters sent from the application function AF to the control node PS and the TFT packet filters plus the PDP address sent by the network unit GGSN to the control node PS compared.
  • the comparison is performed depending on the priority of the TFT packet filter. It is the highest value in terms of value TFT Packet filter started.
  • a media IP flow filter has a match with a TFT packet filter of a PDP context, if the direction is equal, the PDP address is equal to the terminal downlink destination IP address of the AF link information, the protocol IDs are the same or with a placeholder and the ports (terminal UE receive port and / or application function AF source port) are the same or have a placeholder. In the case of a port number range in a TFT packet filter, only a partial overlap is needed.
  • a comparison according to the invention is carried out: a) upon activation or modification of a PDP context (for example, the control node receives a request for authorization) and b) in connection establishment of an AF connection (for example, receipt of new connection information that the control node receives from the application function).
  • the control node analyzes the PDP context attributes (eg, PDP address, TFT, MSISDN, QoS) and, in a first step, identifies the application function connections that correspond to the PDP address such that the Terminal Identifier - Parameter received by the application function is the same as the terminal Identifier of the PDP Context.
  • the corresponding data streams from this relevant AF connection (s) are checked by the method according to the invention. Any data stream that has been identified as being transportable via the PDP context (ie there is a possibility for transport via the PDP context) is allowed or bound for this PDP context.
  • the corresponding gates are installed at the network unit GGSN depending on the priority of the corresponding TFT packet filter, and a combined quality of the service (traffic class, data rate, etc.) is determined and can be authorized.
  • a combined quality of the service (traffic class, data rate, etc.) is determined and can be authorized.
  • the control node In the event the Media IP Flow was bound to a different PDP context, the gates and the quality of the service's content in the PDP context are eliminated from the other PDP context.
  • the control node In the first PDP context (that is, without the TFT packet filter), the control node binds each payload of the relevant AF links to this PDP context.
  • the control node could be authorized either to authorize the quality of the service for that combination of payload data stream or to authorize a general quality of the service preconfigured by the network provider.
  • the quality of the service preconfigured by the network provider could depend on the QoS class or the UMTS traffic class of the PDP context.
  • the control node PS analyzes the AF connection information and, in a first step, identifies whether the AF connection corresponds to an existing PDP address. If so, the control node PS compares the payload data streams of the AF connection with the stored TFT packet filters of the existing PDP contexts. If the comparison is positive, the payload stream is bound to this PDP context and its quality of service is considered in determining the authoritative quality of service for the PDP context. The corresponding gates are installed and the combined quality of the service is authorized. The quality of the service of a PDP context is only changed when the terminal initiates a modification of the PDP context.
  • An important point of the inventive method is the search for a positive comparison between a sent from the application function AF to the control node PS media IP flow filter and a sent by the network unit GGSN to the control node TFT packet filter plus terminal IP address.
  • the TFT packet filter identifies only "downlink” IP packet filters so that a network entity is informed how to route incoming data packets into the correct PDP context. "So far, only the terminal is standardized TFT packet filter with the "downlink” packet filters sends. The connection to a PDP context thus does not work for unidirectional "uplink” payload data streams, as a result of which the control node can not know which PDP context for the "uplink” payload streams from the UE is intended. As a solution to this, the control node is to use any unidirectional "uplink"
  • both payload streams are bound to the same PDP context. Therefore, the PDP context intended for the payload stream can be used. This is derived from the TFT packet filter of the corresponding "downlink" user data stream.
  • the TFT packet filters depend on the terminal and its implementation.
  • the control node can perform only a comparison with AF connection information, if this information is also available at a certain time.
  • the AF connection information sent by the application function AF to the control node PS depends on the AF type or on the type of the application function AF.
  • a general QoS traffic class and data rate
  • general gates can be sent to the network entity GGSN or the authorization request is denied.
  • the basic payload stream binding method could also be extended by a) limiting the bound payload streams and their authorized QoS, and b) improving the PDP context signaling.
  • the control node PS attempts to limit the bound payload data streams to the AF links that ultimately use the PDP context. This happens during the construction of the PDP context.
  • Each later built PDP context will have a higher priority TFT packet filter. This priority results from the binding of the payload data stream with the PDP context.
  • the efforts in the control node could be to additionally consider the requested QoS class or UMTS traffic class of the PDP context during the binding procedure.
  • the QoS class of this payload data stream is analyzed in a third step. Only those payload streams that have a higher QoS class or the same QoS class than that requested for the PDP context will ultimately also be bound to the PDP context. This prevents binding of a user data stream with a lower authoritative QoS class.
  • SBLP provides means for reviewing media components ready to be assigned to the same PDP context. The UE is informed about these limitations by, for example, a single reservation flow indicator (IETF RFC 3524) that individual media components can not be mixed with others. If such a mixture were discovered, the authorization would be rejected.
  • the control node could behave in such a way that the current configuration of the PDP contexts and the TFT packet filter is considered non-final. Instead of rejecting the authorization, the control node could try to find and authorize the largest possible group of user data streams. This procedure may need to be repeated in a later build-up of a PDP context.
  • re-authorizing resources it is meant that a payload stream of an AF connection already allocated to a PDP context is derived from that previous PDP context (eg, First PDP Context )) and is bound to a new (later) PDP context.
  • the control node For each PDP context that loses a payload stream in this step, the control node sends an authorization decision according to the payload streams that are still bound to that resource. The control node thus defines the authorization for the remaining data streams in the PDP context.
  • the allocated resources, the quality of the service, are modified accordingly.
  • a re-authorization should also be performed in cases of modification of an active service, since this changes the comparison with the changed PDP attributes (for example service attributes, which have to be compared with the already existing TFT packet filter ) touch.
  • PDP attributes for example service attributes, which have to be compared with the already existing TFT packet filter
  • An active Service data are transmitted in at least one data stream and currently used by the terminal or the service is currently provided for example by an application function AF.
  • the rules for performing a re-authorization are configurable by the network provider.
  • a payload stream of an AF connection already assigned to a PDP context and providing a positive compare result to another PDP Context Authorization request when compared to a TFT packet filter is always disconnected from the previous PDP context if the priority of the TFT packet filter is higher.
  • FIG. 2 shows a table for the comparison according to the invention.
  • examples of positive comparison results and negative comparison results are given in the method according to the invention.
  • the filters of the first three user data streams have a positive comparison result with the two TFT packet filters because the direction is the same (TFT is always "downlink") .
  • the protocol IDs are also the same or with a placeholder and each IP address , every port and every port number range is the same, with wildcards or overlapping (for the port number range) .
  • the filters of the last three user data streams have a negative comparison result with the two TFT packet filters, since there is always an attribute which belongs to the non-wildcard attributes of the TFT packet filters are different.
  • FIG. 3 shows an example of the re-authorization.
  • a second PDP Context Authorization request with only an "uplink" data stream or without TFT is not considered because In these cases, the authorization request is rejected or authorized with general values for the PDP context.
  • the terminal UE activates a second PDP context x with a "downlink” data stream (4) and the "uplink” data streams (5) and (6) and a second PDP context y with the "downlink” data streams (1 ) and (3) and the uplink data stream (2).
  • the application function AF sends connection information according to FIG. 4 a) to the control node PS. This connection information should be available at the PDP context authorization request.
  • the PDP context address and the TFT packet filter to the second PDP contexts according to FIG. 4 b) are sent by the network unit GGSN for the identification of the user data stream to the control node PS.
  • the service identification is carried out according to the invention as follows:
  • the authorization for the quality of the service is performed for this data stream and for all (unbounded) "uplink" data streams (6) and (5) of this connection a) -d), which are unpaired.
  • Data stream (2) is present in the same media sub-component, the data stream (1) and (2) are authorized for the PDP context y.
  • FIG. 5 shows a control node PS according to the invention for carrying out the method according to FIGS. 1 to 4.
  • the control node PS has a receiving unit E, a transmitting unit S and a processing unit V.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé, un noeud de commande et un système pour déterminer l'allocation de flux de données à des liaisons utiles, par information d'un noeud de commande (PS) d'un noeud de communication, par une fonction d'application (AF) et par un terminal (UE). Selon l'invention, une unité de réseau (GGSN) envoie au moins une information paquet-filtre reçue par le terminal (UE) et concernant la liaison utile à utiliser pour la transmission de données d'au moins un flux de données et d'au moins un attribut au noeud de commande (PS). En outre, une fonction d'application (AF) envoie au moins une information concernant des données à envoyer d'au moins un flux de données, au noeud de commande (PS), ledit noeud de commande (PS) compare l'information paquet-filtre (au moins au nombre de une), l'attribut (au moins au nombre de un) et l'information (au moins au nombre de une) de la fonction d'application (AF) et décide si la liaison utile employée pour les données à envoyer d'au moins un flux de données peut être autorisée et autorise, en cas de comparaison positive, les données d'au moins un flux de données pour la liaison utile.
EP06708700A 2005-03-30 2006-03-09 Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises Withdrawn EP1867111A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102005014852A DE102005014852A1 (de) 2005-03-30 2005-03-30 Entscheidung zur Zuordnung und Ressourcenvergabe für mindestens einem Datenstrom und mindestens eine Nutzverbindung
PCT/EP2006/060597 WO2006103153A1 (fr) 2005-03-30 2006-03-09 Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises

Publications (1)

Publication Number Publication Date
EP1867111A1 true EP1867111A1 (fr) 2007-12-19

Family

ID=36463398

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06708700A Withdrawn EP1867111A1 (fr) 2005-03-30 2006-03-09 Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises

Country Status (5)

Country Link
EP (1) EP1867111A1 (fr)
BR (1) BRPI0609263A2 (fr)
DE (1) DE102005014852A1 (fr)
RU (1) RU2384001C2 (fr)
WO (1) WO2006103153A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108881014A (zh) * 2017-05-12 2018-11-23 北京猎户星空科技有限公司 一种数据发送系统及方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102957625B (zh) * 2011-08-18 2017-11-03 邳州高新区生物医药研究院有限公司 一种实现端到端层次化服务质量的系统和方法
CN104348751B (zh) * 2013-07-31 2019-03-12 中兴通讯股份有限公司 虚拟输出队列授权管理方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004030309A2 (fr) * 2002-09-24 2004-04-08 Orange Sa Telecommunications

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7826353B2 (en) * 2003-05-05 2010-11-02 Nokia Corporation Method, system and network element for authorizing a data transmission

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004030309A2 (fr) * 2002-09-24 2004-04-08 Orange Sa Telecommunications

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108881014A (zh) * 2017-05-12 2018-11-23 北京猎户星空科技有限公司 一种数据发送系统及方法

Also Published As

Publication number Publication date
BRPI0609263A2 (pt) 2010-03-09
RU2007139914A (ru) 2009-05-10
WO2006103153A1 (fr) 2006-10-05
RU2384001C2 (ru) 2010-03-10
DE102005014852A1 (de) 2006-10-05

Similar Documents

Publication Publication Date Title
DE10302788B4 (de) Einrichtung und Verfahren zum Umordnen von TFTs in einem Mobilkommunikationssystem
DE60117288T2 (de) Richtlinien koordination in einem kommunikationsnetz
DE60003525T2 (de) Übertragung von dienstqualitätsabbildungsinformation in einem paketfunknetz
EP2018765B1 (fr) Controle de qualite de service et/ou taxation de service de telecommunication
DE60211881T2 (de) Bindungsinformation für ip mediendatenströmen
DE69628724T2 (de) Netzknotenvorrichtung und Verbindungsaufbauverfahren zum Aufbauen von Durchgangsverbindungen
DE60120354T2 (de) Rsvp-verarbeitung in 3g-netzwerken
DE69833111T2 (de) Bestimmung von trägerdiensten in einem funkzugriffsnetz
DE602005006095T2 (de) Bereitstellen von Informationen über die Beziehungen individueller Träger für mobile Endgeräte, die einen Multicast- oder Broadcastdienst empfangen
DE60206894T2 (de) Verfahren und vorrichtung zur herstellung eines protokoll-proxy für ein mobiles host-endgerät in einer multimediasitzung
EP1994714B1 (fr) Procédé d'attribution d'au moins une liaison de données utilisateur à au moins une connexion multiplex
WO2007025905A1 (fr) Systeme de communication, ordinateur a noeud de commutation et procede pour definir un noeud de controle
DE102005037874B4 (de) Verfahren und Anordnung zur Kontrolle und Vergebührung von Peer to Peer-Diensten in einem IP-basierten Kommunikationsnetzwerk
EP2387261B1 (fr) Préparation d'une connexion de bout en bout d'un terminal à un réseau
DE60130498T2 (de) Verfahren und vorrichtung zur trägerberechtigung in einem drahtlosen kommunikationsnetzwerk
DE102005035237A1 (de) Verfahren zur Steuerung von Ressourcen in Netzelementen eines Telekommunikationsnetzes
EP1867111A1 (fr) Decision pour allouer au moins un flux de donnees a au moins une liaison utiles et attribuer les ressources requises
EP1317820B1 (fr) Procede pour etablir des liaisons avec des qualites de service predefinies dans un reseau de communication oriente paquet, a l'aide d'un gestionnaire de ressources
EP1708434B1 (fr) Procédé et système pour imposer des directives ciblées au trafic de données dans un réseau de communication sans fil
WO2012123001A1 (fr) Procédé d'établissement d'une liaison de communication
EP1771993B1 (fr) Procede pour surveiller un echange de messages, ainsi qu'une premiere et qu'une seconde unite de reseau pour mettre ledit procede en oeuvre
EP2237600B1 (fr) Limitation de la fréquence de transmission de données pour une connexion de données dans un système mobile
DE69931132T2 (de) Funkstrecke mit dynamischer Anpassung
WO2005117340A1 (fr) Procede pour synchroniser des processus de taxation intervenant lors de l'execution d'un service sur des elements de reseau dans un reseau de communication
EP1708433B1 (fr) Procédé et système pour la facturation des applications et/ou du correspondant trafic de données dans un système de radiocommunication

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20071030

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20080131

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20100713