US7802011B2 - Mapping of packets to PDP contexts in multisession connection - Google Patents

Mapping of packets to PDP contexts in multisession connection Download PDF

Info

Publication number
US7802011B2
US7802011B2 US10/480,440 US48044004A US7802011B2 US 7802011 B2 US7802011 B2 US 7802011B2 US 48044004 A US48044004 A US 48044004A US 7802011 B2 US7802011 B2 US 7802011B2
Authority
US
United States
Prior art keywords
configuration information
subscriber equipment
settings
application
service
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.)
Expired - Lifetime, expires
Application number
US10/480,440
Other languages
English (en)
Other versions
US20040153551A1 (en
Inventor
Serge Haumont
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 Technologies Oy
Original Assignee
Nokia Inc
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 Inc filed Critical Nokia Inc
Assigned to NOKIA CORPORATION reassignment NOKIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HAUMONT, SERGE
Publication of US20040153551A1 publication Critical patent/US20040153551A1/en
Application granted granted Critical
Publication of US7802011B2 publication Critical patent/US7802011B2/en
Assigned to NOKIA TECHNOLOGIES OY reassignment NOKIA TECHNOLOGIES OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA CORPORATION
Adjusted expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • 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
    • 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
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • Typical networks such as an Internet network may be accessed through a variety of ways (GPRS, WLAN, ADSL modem, etc.).
  • many access technologies support multiple QoS flows (GPRS, ADSL, RSVP, etc.).
  • GPRS is the packet technology used in GSM and in UMTS (using WCDMA (Wideband Code Division Multiple Access)radio)).
  • WCDMA Wideband Code Division Multiple Access
  • each QoS flow is associated to a PDP context (logical connection from user equipment to external network).
  • PDP Packet Data Protocol
  • APN Access Point Name
  • QoS Quality of Service
  • the SGSN validates the Activate PDP Context Request optionally using PDP Type, PDP Address and APN.
  • the SGSN sends a Create PDP Context Request message comprising PDP Type, PDP Address, APN and QoS Negotiated to the affected GGSN.
  • the GGSN may use the APN to find an external network.
  • a Selection Mode indicates whether a subscribed APN was selected, or whether a non-subscribed APN sent by the MS or a non-subscribed APN chosen by the SGSN was selected. The GGSN may use the Selection Mode when deciding whether to accept or reject the PDP context activation.
  • the GGSN is configured to accept only the PDP context activation that requests a subscribed APN as indicated by the SGSN with Selection Mode.
  • the GGSN creates a new entry in its PDP context table and creates a Charging Id.
  • the new entry allows the GGSN to route PDP PDUs (Packet Data Units) between the SGSN and the external PDP network and to start charging.
  • PDP PDUs Packet Data Units
  • the GGSN returns a Create PDP Context Response message comprising PDP Address, QoS Negotiated and Charging ID to the SGSN.
  • the GGSN rejects the Create PDP Context Request message.
  • the SGSN returns an Activate PDP Context Accept message to the MS.
  • the SGSN is now able to route PDP PDUs between the GGSN and the MS and to start charging.
  • GPRS can support different QoS flows, each corresponding to a PDP context, for a unique PDP address (e.g. Ipv4 or Ipv6 address).
  • PDP Packet Datagram Protocol
  • the QoS mechanism uses a set of filters called Traffic Flow Template (TFT) and information in the IP header, such as Type of Service (ToS) field or UDP (User Datagram Protocol) port number in order to determine to which PDP context an IP packet belongs.
  • TFT Traffic Flow Template
  • ToS Type of Service
  • UDP User Datagram Protocol
  • the MS maps uplink packets to the proper PDP context, and GGSN maps downlink packets to the proper PDP context using TFT. It is to be noted that the MS configures the GGSN TFT.
  • a typical application example is an H323 call. Relying on the port number is not useful since some H323 family protocols e.g. H245 use dynamic port. Using the port number will be just impossible if encryption is used.
  • the end point of an IP connection of the user equipment is a server in an IP network, which is controlled by the operator of the IP network, for example a Call Server, or the end point is a server in the Internet or Intranet, which is not controlled by the IP network operator.
  • communication may also be established between two user equipments (e.g. VOIP call), connected through different operators' networks.
  • the general problem is how to properly configure QoS for applications which may connect through different access and to different networks, in particular, the QoS parameters used by the access technology, the filter used to select the proper QoS flow, and QoS parameters (e.g. ToS) used in the network where the connection is established.
  • QoS parameters e.g. ToS
  • An additional problem is how to set filters for applications which do not use fixed port number, or for which the port number cannot be read due to encryption.
  • ToS setting is most often proprietary.
  • a packet data network system for routing packets belonging to different quality of service flows comprises a subscriber equipment for initiating applications with associated quality of service flows in a multi-session connection.
  • the subscriber equipment may comprise a laptop or the like and a “modem” or access device (e.g. ADSL modem or mobile station) for transmitting data packets to a packet data network like an operator IP network.
  • the subscriber equipment may also integrate application and modem in the same device such as a Nokia communicator.
  • the system further comprises a configuration device like a configuration server (e.g. policy server) which may be located in the operator IP network.
  • the configuration device obtains, for each initiated application, type of service information of a network node hosting the application, such as an operator application server, media gateway, H323 gatekeeper, laptop, etc. Then, the configuration device provides the configuration information to the subscriber equipment. This information is derived from the obtained type of service information and possibly from the operator policy. This information includes QoS parameter defining QoS flow (e.g. GPRS QoS profile), filters for uplink and downlink (e.g. TFT), and parameters to be used by the application (ToS or port number).
  • QoS parameter defining QoS flow
  • filters for uplink and downlink e.g. TFT
  • parameters to be used by the application ToS or port number.
  • the system further comprises a gateway node, like a GGSN, connecting the access technology to the operator IP network, for exchanging packets between the network and the subscriber equipment.
  • This gateway should select the proper QoS flow for each application using filters using for example ToS field of incoming packets.
  • the subscriber equipment uses the obtained configuration information to set the filters and the associated quality of service flow in the gateway node.
  • the gateway node is able to route the packets into the proper QoS flow on the basis of the filter set by the user equipment and the packet header (e.g. ToS field).
  • the User equipment sets the filter in the gateway node because if dynamic configuration is not used, the application in the user equipment is the only entity capable of properly setting the filter. This is the case in GPRS where MS sets TFT. It is assumed that the same generic mechanism is kept with dynamic configuration, so that filters of the gateway node are set by the user equipment.
  • the type of service information (or other field used by the filter) marked in the packets sent by an application may be determined by an operator of the network hosting this application. In a preferred embodiment, this ToS is set by the same configuration device into the various applications. In this case the configuration device obtains these parameters directly. If the application is located in a different network connected through an edge router capable of changing the type of service information of the IP packets, the same configuration device may configure the edge router and obtain type of service used by the application in the other network. The configuration device will then know with what type of service information the packet will be marked which belongs to a certain application arriving at the gateway node.
  • the configuration device may further obtain settings, such as Type of Service (ToS) information (i.e. DiffServ codepoints), of the application(s) in the subscriber equipment and provide to the subscriber equipment the configuration information.
  • This configuration information is preferably filters based on the type of service information and appropriate QoS parameters. This is illustrated in FIG. 2 , where when knowing the settings of the application and the operator policy (here Netscape and Q931 use interactive class, Email uses background class and UDP/RTP uses conversational class), the configuration device can indicate the proper filters to the subscriber equipment (e.g. Mobile station).
  • the subscriber equipment uses the ToS field of the IP packets coming from an application and the filter to map this uplink packet into the appropriate QoS flow (e.g. PDP context).
  • the subscriber equipment transmits packets to the network for each initiated application in accordance with the associated quality of service flow mapped in the subscriber equipment.
  • the subscriber equipment may need to know the mapping for downlink.
  • This set of filters e.g. TFT
  • TFT is first sent from the configuration device to the subscriber equipment and then from the subscriber equipment to the gateway.
  • the gateway is then able to transmit every downlink packet into the right QoS flow.
  • the configuration device may further obtain setting information in a variety of ways:
  • the present invention presents a method for dynamically configuring a user equipment and an application in the user equipment, so that packet traffic of the application is sent through proper QoS flow using appropriate QoS parameters. Packets are routed in the proper QoS flow using filters. These filters use information contained in the packet header such as ToS information for mapping packets to associated QoS flows (e.g. PDP contexts). Thus, the level of QoS needed by an application is provided.
  • the present invention provides means for configuring uplink and downlink filters and their associated QoS flow for every application or protocol used by a user equipment.
  • FIG. 1 shows a PDP Context Activation Procedure.
  • FIG. 2 shows a schematic block diagram of a network system comprising a configuration server according to the present invention.
  • FIG. 3 shows a system where a policy server uses COPS to dynamically configure the user equipment.
  • FIG. 4 shows a system where a configuration server uses WAP to dynamically configure the MS.
  • FIG. 2 shows a network system according to GPRS.
  • a Mobile Station (MS) to which a laptop can be connected can initiate multiple sessions in order to use applications or protocols hosted in an operator IP network by an operator application server, a media gateway and/or an H323 gatekeeper, for example.
  • MS Mobile Station
  • For each session a PDP context with a requested QoS is activated by the MS in an SGSN (not shown) towards a GGSN in the operator IP network.
  • the GGSN then has to map downlink packets belonging to the different applications or protocols to the proper PDP contexts or QoS flows.
  • a dedicated, network-specific configuration server keeps track of the ToS settings of applications hosted within the network system.
  • the configuration server knows how the laptop sets the ToS bits for every application.
  • the configuration server obtains its knowledge from the corporate IT (Information Technology) staff, or from the software the operator provides to the user (preferably remotely).
  • the operator knows the ToS setting from the mobile type or manufacturer and provides the knowledge to the configuration server.
  • the operator may be able to configure the mobile setting, i.e. the mapping between the application and the ToS bits. This could be done by using a default standard or an agreed standard.
  • the configuration server is provided with the ToS information of the applications hosted in the operator network. For example, the configuration server knows how the application server sets the ToS bits. This is a straightforward configuration if the application server is owned by the operator or an operator partner.
  • the setting may also be known if the application server is set up by corporate staff and the operator has an agreement with the corporate.
  • a particular important application server is a Call Server which is foreseen to be managed by the operator.
  • the knowledge about the setting may also be derived from default standard or agreed standard.
  • the configuration server of this IP network provides the MS with ToS information of the application in order to inform the MS how it should configure its own TFT and the GGSN TFT.
  • the operator may use MExE (Mobile application Execution Environment) to update MS configuration, i.e. mapping of ToS to PDP context.
  • MExE Mobile application Execution Environment
  • the MS configures the TFT to be used in the GGSN for that session it is able to specify the correct ToS information and the GGSN can use the ToS information when routing packets to several simultaneous sessions of the same subscriber.
  • the ToS information may be initially delivered from the configuration server to the MS over a single-session connection from the subscriber to the application when it is self-evident to the GGSN which PDP context to use.
  • the configuration server application needs to be aware of the nature of the interference and be able to counteract this interference. In case of an operator's own edge router its behaviour can easily be known and counteracted by the configuration server.
  • FIG. 2 shows an example of ToS settings and PDP context mappings.
  • the MS maps ToS 4 to PDP context 1 (interactive), ToS 3 to PDP context 2 (background), ToS 5 to PDP context 1 (interactive) and ToS 11 to PDP context 3 (conversational).
  • the configuration server provides these settings to the MS and informs the MS how to configure the GGSN TFT, i.e. how to map the downlink ToS to PDP context.
  • the MS configures the GGSN TFT accordingly, so that the GGSN maps ToS 3 to PDP context 2 , ToS 8 to PDP context 1 , ToS 13 to PDP context 3 and ToS 7 to PDP context 1 .
  • the downlink packets are mapped by the GGSN to the same PDP context as the corresponding uplink packets.
  • FIGS. 3 and 4 A different signaling flow showing how to configure the Mobile Station is depicted in FIGS. 3 and 4 .
  • FIG. 3 shows a PDP context activation where the GGSN checks the authorization from a policy server using a COPS-pull request (communication 3 in FIG. 3 ).
  • the COPS-pull request contains user identity, user IP address, QoS requested, TFT, authorization token, an indication of intended use of the PDP context if available (e.g. signaling PDP context), MS capability and other relevant-parameters.
  • the policy server authorizes the PDP context, the policy server sends a COPS decision to the GGSN (communication 4 in FIG. 3 ) and may further send configuration information directly to the MS using COPS-push (communication 7 in FIG. 3 ).
  • This configuration information contains a list of filter(s), and associated with every filter: Diffserv marking, UMTS QoS profile, TFT and APN.
  • an application server IP address to be used by different applications may be sent.
  • APN may be-set to wild card to indicate that any APN would be acceptable.
  • This information is not limited to the configuration information needed by one application, but may cover all applications for which the MS has rights and capabilities to handle. The capabilities are deduced from a new information element “MS capability” which is an addition to existing PDP context activation procedure proposed in this application. “MS capability” covers QoS support (maximum bit rate supported by the MS; list of traffic classes supported) and list of applications installed in the MS. This information will be received by the MS.
  • the application server IP address (such as WAP Gateway address currently hard-coded) may then be dynamically set in the MS.
  • the MS behaves in the following way. If an uplink packet is received by the MS, the MS will first check it against the filter (e.g. UDP port 8080 ). The filter indicates to the MS with which Diffserv codepoints this uplink packet is to be marked and with which UMTS QoS profile it should be sent over the radio. The MS will then check whether a suitable PDP context exists (similar QoS and same PDP type, acceptable APN) to send the packet directly. If such a PDP context is found the packet is sent in this PDP context. If no suitable PDP context exists, the MS will activate a suitable PDP context. After the PDP context activation, the packet will be sent in this PDP context. The PDP context may be deleted after no traffic has been sent during a certain time.
  • the filter e.g. UDP port 8080 .
  • the filter indicates to the MS with which Diffserv codepoints this uplink packet is to be marked and with which UMTS QoS profile it should be sent over the radio.
  • the MS will
  • the MS uses the configuration information received in communication 7 in FIG. 3 to configure the application.
  • the application properly marks the IP packet based on the marking information sent in the COPS-push message. If the application needs to send a packet, it first requests a PDP context activation with appropriate QoS, appropriate APN, and appropriate TFT.
  • FIG. 4 shows a system where a configuration server uses WAP-(Wireless Application Protocol)push to dynamically configure the application in the MS.
  • WAP-Push includes in its addressing the application ID, and therefore is well suited to address an application directly.
  • the GGSN When a PDP context is created, the GGSN sends to a configuration server a RADIUS start accounting message (communication 3 in FIG. 4 ) containing user identity (e.g. IMSI, MSISDN), user IP address, QoS requested, an indication of intended use of the PDP context if available (e.g. signaling PDP context), MS capability and other relevant parameters.
  • user identity e.g. IMSI, MSISDN
  • QoS requested an indication of intended use of the PDP context if available (e.g. signaling PDP context), MS capability and other relevant parameters.
  • RADIUS stop accounting message is also sent to the configuration server. Therefore the configuration server is aware whether the MS is connected or not.
  • the configuration server sends an acknowledge message to the GGSN (communication 4 in FIG. 4 ) and further sends a WAP-push message directly to the application(s) it needs to configure (communication 7 in FIG. 4 ).
  • This message contains configuration information such as filter (mapping for uplink), Diffserv marking, UMTS QoS profile, TFT (mapping for downlink), APN and application server IP address to be used by this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
US10/480,440 2001-06-15 2001-06-15 Mapping of packets to PDP contexts in multisession connection Expired - Lifetime US7802011B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2001/006787 WO2002104046A1 (en) 2001-06-15 2001-06-15 Mapping of packets to pdp contexts in multisession connection

Publications (2)

Publication Number Publication Date
US20040153551A1 US20040153551A1 (en) 2004-08-05
US7802011B2 true US7802011B2 (en) 2010-09-21

Family

ID=8164448

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/480,440 Expired - Lifetime US7802011B2 (en) 2001-06-15 2001-06-15 Mapping of packets to PDP contexts in multisession connection

Country Status (5)

Country Link
US (1) US7802011B2 (de)
EP (1) EP1400136B1 (de)
AT (1) ATE349142T1 (de)
DE (1) DE60125422T2 (de)
WO (1) WO2002104046A1 (de)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040105452A1 (en) * 2002-11-26 2004-06-03 Ntt Docomo, Inc. Radio access network system, radio access method, and control apparatus
US20050025155A1 (en) * 2001-10-19 2005-02-03 Belhassen Jerbi Method for carrying out instant messaging with packet switched data

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1543655B1 (de) * 2002-09-24 2016-03-09 Orange Telekommunikationsnetz
GB2395090B (en) * 2002-10-01 2006-04-05 Ipwireless Inc Arrangement and method for session control in wireless communication network
US8488462B2 (en) * 2002-12-31 2013-07-16 Nokia Corporation Handling traffic flows in a mobile communications network
US7522613B2 (en) 2003-05-07 2009-04-21 Nokia Corporation Multiplexing media components of different sessions
US8108520B2 (en) * 2003-06-19 2012-01-31 Nokia Corporation Apparatus and method for providing quality of service for a network data connection
GB0319359D0 (en) * 2003-08-18 2003-09-17 Nokia Corp Activation of communication sessions in a communication system
US20060092963A1 (en) * 2004-10-28 2006-05-04 Ajay Bakre Architecture and method for efficient application of QoS in a WLAN
EP1655975B1 (de) * 2004-11-04 2007-04-18 Research In Motion Limited System und Verfahren zur Versorgung einer Mobilstation mit einem PDP-Kontext über die Luftschnittstelle
US7464169B2 (en) 2004-11-04 2008-12-09 Research In Motion Limited System and method for over the air provisioning of a single PDP context mobile communications device
US7835722B2 (en) 2004-11-04 2010-11-16 Research In Motion Limited System and method for over the air provisioning of a mobile communications device
US7433961B2 (en) * 2004-11-16 2008-10-07 Research In Motion Limited System and method for sequentially conducting independent data contexts using a mobile communications device
FI20050187A0 (fi) * 2005-02-17 2005-02-17 Nokia Corp Kuljetuspalveluun liittyvän informaation tuottaminen pakettidataverkossa
US8169953B2 (en) * 2005-05-17 2012-05-01 Qualcomm Incorporated Method and apparatus for wireless multi-carrier communications
WO2007029593A1 (ja) * 2005-09-07 2007-03-15 Matsushita Electric Industrial Co., Ltd. 携帯電話装置およびその制御方法
US20070081499A1 (en) * 2005-10-12 2007-04-12 Petter Johnsen Packet data protocol context utilization
US7474671B2 (en) 2005-11-04 2009-01-06 Research In Motion Limited System and method for resolving contention among applications requiring data connections between a mobile communications device and a wireless network
JP4838320B2 (ja) * 2005-12-12 2011-12-14 テレフオンアクチーボラゲット エル エム エリクソン（パブル） データパケットの伝送におけるサービス品質を指定する方法および装置
KR100727077B1 (ko) * 2006-02-07 2007-06-13 주식회사 케이티프리텔 멀티 피디피 환경에서의 과금 방법 및 시스템
US7876759B2 (en) * 2007-07-11 2011-01-25 Hewlett-Packard Development Company, L.P. Quality of service with control flow packet filtering
US8566453B1 (en) * 2007-11-19 2013-10-22 Juniper Networks, Inc. COPS-PR enhancements to support fast state synchronization
US8493984B2 (en) * 2008-06-13 2013-07-23 Cisco Technology, Inc. System and method for establishment of a multiprotocol label switching (MPLS) tunnel
CN101932040B (zh) * 2009-06-26 2014-01-01 华为技术有限公司 寻呼处理方法、通信装置及通信系统
US9807602B2 (en) 2010-04-07 2017-10-31 Qualcomm Incorporated Apparatus and method for connection establishment in a communications network
US9426718B2 (en) 2012-05-16 2016-08-23 Qualcomm Incorporated Systems and methods for data exchange over common communication links
US9906452B1 (en) * 2014-05-29 2018-02-27 F5 Networks, Inc. Assisting application classification using predicted subscriber behavior
US11857872B2 (en) * 2020-07-21 2024-01-02 Nvidia Corporation Content adaptive data center routing and forwarding in cloud computing environments
US11500702B1 (en) * 2021-04-26 2022-11-15 Visa International Service Association System and method for timed data transmission

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0818907A2 (de) 1996-07-12 1998-01-14 AT&T Corp. Benutzer-/Anbieterarchitektur für Internet und Netzwerke mit garantierter Dienstqualität zum Zugriff auf verteilte Mediaquellen
WO1999005828A1 (en) 1997-07-25 1999-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic quality of service reservation in a mobile communications network
WO1999016266A1 (en) 1997-09-25 1999-04-01 Telefonaktiebolaget Lm Ericsson (Publ) Selectable packet-switched and circuit-switched services in a mobile communications network
US20020036983A1 (en) * 2000-05-22 2002-03-28 Ina Widegren Application influenced policy

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0818907A2 (de) 1996-07-12 1998-01-14 AT&T Corp. Benutzer-/Anbieterarchitektur für Internet und Netzwerke mit garantierter Dienstqualität zum Zugriff auf verteilte Mediaquellen
WO1999005828A1 (en) 1997-07-25 1999-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic quality of service reservation in a mobile communications network
WO1999016266A1 (en) 1997-09-25 1999-04-01 Telefonaktiebolaget Lm Ericsson (Publ) Selectable packet-switched and circuit-switched services in a mobile communications network
US20030039237A1 (en) * 1997-09-25 2003-02-27 Jan E Forslow Common access between a mobile communications network and an external network with selectable packet-switched and circuit-switched services
US20020036983A1 (en) * 2000-05-22 2002-03-28 Ina Widegren Application influenced policy

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; QoS Concept and Architecture (3G TS 23.107 version 3.0.0 )"; 3G TS 23.107 v3.0.0 (Oct. 1999), pp. 1-32.
"Can You Build a Smart Network with Dumb NIC'S?", Data Communications on the Web, Apr. 21, 1998, pp. 1-9.
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2 (3G TS 23.060 version 3.2.0) 3G TS 23.060 DRAFT v3.2.0 (Dec. 1999), pp. 1-173.
Blake, et al., "An Architecture for Differentiated Services", Network Working Group Dec. 1998 pp. 1-36.

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050025155A1 (en) * 2001-10-19 2005-02-03 Belhassen Jerbi Method for carrying out instant messaging with packet switched data
US9306772B2 (en) * 2001-10-19 2016-04-05 Siemens Aktiengesellschaft Method for carrying out instant messaging with packet switched data
US20040105452A1 (en) * 2002-11-26 2004-06-03 Ntt Docomo, Inc. Radio access network system, radio access method, and control apparatus
US8014348B2 (en) * 2002-11-26 2011-09-06 Ntt Docomo, Inc. Radio access network system, radio access method, and control apparatus

Also Published As

Publication number Publication date
EP1400136A1 (de) 2004-03-24
DE60125422T2 (de) 2007-10-11
EP1400136B1 (de) 2006-12-20
WO2002104046A1 (en) 2002-12-27
US20040153551A1 (en) 2004-08-05
ATE349142T1 (de) 2007-01-15
DE60125422D1 (de) 2007-02-01

Similar Documents

Publication Publication Date Title
US7802011B2 (en) Mapping of packets to PDP contexts in multisession connection
US10582411B2 (en) Techniques for handling network traffic
EP2109266B1 (de) Verfahren und Einrichtungen zum installieren von Paketfiltern bei einer Datenübertragung
JP4224461B2 (ja) 機能強化されたｑｏｓ（サービスの質）制御
EP1763971B1 (de) Bindemechanismus zur dienstqualitätsverwaltung in einem kommunikationsnetz
EP1972120B1 (de) Verfahren und einrichtungen zum filtern von datenpaketen in einer übertragung
US20020062379A1 (en) Method and apparatus for coordinating quality of service requirements for media flows in a multimedia session with IP bearer services
EP1771978B1 (de) Tunneln von internet-protokoll-paketen zwischen einem gateway support node und einem mobilen endgerät
US8488462B2 (en) Handling traffic flows in a mobile communications network
KR100879164B1 (ko) 통신 네트워크에서 서비스 품질 관리를 위한 결합 메커니즘
HK1127937B (en) Method and devices for installing packet filters in a data transmission

Legal Events

Date Code Title Description
AS Assignment

Owner name: NOKIA CORPORATION, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAUMONT, SERGE;REEL/FRAME:015126/0215

Effective date: 20040115

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: NOKIA TECHNOLOGIES OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035611/0918

Effective date: 20150116

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552)

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12