US20110222430A1 - Method and device for assigning traffic to a direct tunnel, computer program product and computer-readable medium - Google Patents
Method and device for assigning traffic to a direct tunnel, computer program product and computer-readable medium Download PDFInfo
- Publication number
- US20110222430A1 US20110222430A1 US13/130,414 US200813130414A US2011222430A1 US 20110222430 A1 US20110222430 A1 US 20110222430A1 US 200813130414 A US200813130414 A US 200813130414A US 2011222430 A1 US2011222430 A1 US 2011222430A1
- Authority
- US
- United States
- Prior art keywords
- direct tunnel
- traffic
- prioritization
- tunnel
- computer
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device
Definitions
- the invention relates to a method and to a device for assigning traffic to a direct tunnel, to a computer program product and to a computer-readable medium.
- Direct tunnels are specified by 3GPP TS 23.060 (General Packet Radio Service (GPRS); Service description).
- GPRS General Packet Radio Service
- An SGSN implements this functionality to enable establishing a direct tunnel between a GGSN and a UTRAN in a UMTS network.
- Direct Tunnel is an optional function in an Iu-mode that allows the SGSN to establish a direct user plane tunnel between an RAN and a GGSN within the PS domain.
- a SGSN that is capable of processing direct tunnels shall have the capability to be configured on a per GGSN and a per RNC basis whether or not it can use a direct user plane connection.
- the SGSN handles control plane signaling and provides a decision per PDP when to establish a direct tunnel.
- the current implementation of the direct tunnel mechanism is rather ineffective in its decision whether or not to establish a direct tunnel.
- SGSN implements a direct tunnel solution to avoid user plane traffic flowing through the SGSN user plane. Due to the huge amount of data traffic expected in the (near) future, a significant demand for additional user plane capacity will arise. Direct tunnel solutions are an important tool for an operator not having to purchase more SGSN capacity. Instead, the user plane can be bypassed and traffic can be conveyed directly from the GGSN to the RNC.
- the tunnel creation process is directly proportional to RAB assignment in SGSN.
- the ratio between PDP context in view of RAB amounts to 5-10%, i.e. for every 100 PDP contexts in SGSN, there are 5 to 10 RABs. This figure is expected to increase to about 20-30% due to “Always-On” terminals and broadband type of access.
- the 3GPP standard (TR 23.809) defines a mechanism to create, to update or to delete a direct tunnel. Also, it defines cases when direct tunnel shall not be created. As mentioned, there is no provision in the standard as how to effectively utilize direct tunnels with regard to existing or upcoming traffic.
- the problem to be solved is to overcome the disadvantages mentioned above and in particular to provide an efficient utilization of direct tunnels.
- a method for assigning traffic to a direct tunnel, wherein said traffic is assigned to the direct tunnel based on a prioritization provided by a serving node and/or by a gateway node.
- At least one serving node and/or at least one gateway node may be provided at least one serving node and/or at least one gateway node.
- the serving node is a SGSN.
- the gateway node is a GGSN.
- GGSN is mentioned as an example for a gateway node and SGSN is mentioned as an example for a serving node.
- Said serving node and/or said gateway node may be any component of a network comprising a packet data switching function.
- assignment may comprise re-assignment of traffic, in particular PDP traffic (that may be organized as PDP context in a PDP session).
- the approach provided allows setting up, modifying, releasing at least one direct tunnel between a GGSN and a UTRAN (in particular a RNC) of a UMTS network.
- a GGSN and a UTRAN (in particular a RNC) of a UMTS network.
- Such handling of the direct tunnel is provided in a prioritized way, i.e. certain features and information can be utilized in order to allow for an effective prioritization.
- a throughput via the direct tunnel can be increased (e.g., maximized) thereby minimizing a need for throughput provided via the usual two tunnel approach.
- the solution presented provides a differentiation and/or priority mechanisms based on which it can be decided whether or not to establish a direct tunnel.
- direct tunnels can be crated (deleted, amended, etc.) in a selective manner to allow for an efficient utilization of user traffic in a way that, e.g., users' traffic with a high demand for bandwidth are conveyed through direct tunnel(s).
- This approach proposes using parameters and maximizing the throughput of the direct tunnels, wherein a number of direct tunnels may be limited by a license control. Hence, a two tunnel user plane throughput requirement at the SGSN is reduced. Such an optimization results in an commercial and technical economization for the operator.
- said direct tunnel is a tunnel between the gateway node and a UTRAN of a UMTS network.
- the prioritization provided comprises information regarding at least one RAB assigned to and/or created for a PDP context.
- said prioritization is based on a user profile, in particular on a user profile per access point name (APN).
- APN access point name
- an user-specific information can be utilized for prioritization purposes.
- said user profile is stored and/or associated with a database containing subscriber information.
- Such database containing subscriber information may comprise, be part of or be associated with a HLR or a HSS (in case of IMS).
- the user profile comprises a direct tunnel preference.
- Such direct tunnel preference may be, e.g., a tag or a flag, provided by or associated with the user's subscription or it may be based on an (pre-set or pre-defined) operator's preference.
- the prioritization provided comprises a cell identification.
- a local or regional information e.g., home zone and/or office zone location
- a direct tunnel e.g., a direct tunnel.
- cell identification ID
- RNC Radio Network Controller
- the prioritization provided is based on a terminal's capability or its identity.
- a terminal's identification such as an IMEI or an IMEISV could be used.
- the capability of the terminal may indicate the type of service that could be utilized by this device.
- terminal refers to any kind of mobile terminal or device that may comprise a mobile interface (e.g., computer, personal digital assistant, smartphone, mobile phone, user equipment (UE), etc.).
- a mobile interface e.g., computer, personal digital assistant, smartphone, mobile phone, user equipment (UE), etc.
- the prioritization provided is based on a load factor of at least a portion of the network.
- the load factor may be assessed, e.g., by the SGSN and/or by the GGSN.
- the prioritization provided is based on a data volume, in particular on a data volume count of the serving node.
- the serving node prioritizes traffic that is conveyed via two tunnels based on the data volume.
- highly prioritized two-tunnel traffic is assigned from the two tunnels to the direct tunnel.
- the SGSN may in particular maintain a list sorted by the amount of traffic conveyed per PDP context via said two tunnels. In case a direct tunnel resource is available, the PDP context with the highest amount of traffic can be assigned from the two tunnels to the direct tunnel.
- the event of a direct tunnel traffic being released can be indicated by a RAB inactivity timer.
- This procedure may be applied iteratively, i.e. highly prioritized traffic conveyed via said two tunnels migrates to the direct tunnel in case a direct tunnel resource becomes available. This ensures that the direct tunnel(s) are utilized in an efficient way.
- the prioritization provided is based on a data volume and/or traffic analysis monitored and/or provided by the gateway node.
- a data volume counter may be provided with the GGSN for all active PDP contexts.
- the GGSN may make a decision (based on the data volume and the direct tunnel indication supplied by the SGSN) to initiate an update PDP context procedure to switch two tunnel traffic into the direct tunnel.
- said traffic is assigned to the direct tunnel in case a direct tunnel license is available.
- a device comprising a and/or being associated with a processor unit and/or a hard-wired circuit and/or a logic device that is arranged such that the method as described herein is executable thereon.
- the device is a communication device, in particular a or being associated with a network component of a UMTS network, e.g., a SGSN or a GGSN.
- a network component of a UMTS network e.g., a SGSN or a GGSN.
- Such computer may be any device comprising and/or associated with at least one processor and/or at least one hard-wired circuit that is operable by said computer program product and/or by instructions stored on the computer-readable medium.
- Said program or instructions may be in particular used for updating purposes of a network component or node, in particular of a GGSN or a SGSN.
- FIG. 1 shows a diagram visualizing PDP traffic over time utilizing one tunnel traffic and two tunnel traffic
- FIG. 2 shows a diagram visualizing throughput over time, wherein an efficient utilization of the direct tunnel allows to reduce throughput to be provided by the conventional two tunnel approach;
- FIG. 3 shows a flow diagram comprising steps to decide whether to create two tunnels or a direct tunnel
- FIG. 4 shows a flow diagram visualizing the concept of a volume counter in order to determine whether migration to direct tunnels may proof useful
- FIG. 5A shows a flow diagram comprising an example as how to migrate two tunnels to a direct tunnel based on a GGSN volume counter
- FIG. 5B shows an example as how to migrate a direct tunnel to two tunnels based on the GGSN volume counter
- FIG. 6 shows a flow diagram comprising steps to decide whether to migrate PDP context to a direct tunnel based on a traffic analysis provided by the GGSN;
- FIG. 7 shows an arrangement of components to compare a direct tunnel and two tunnel approach.
- FIG. 1 illustrates a situation where a certain number of active PDPs (license restricted) are allowed to be carried via a direct tunnel (DT) and all remaining PDPs (exceeding the DT license limit) are conveyed conventionally via two tunnels. Regardless of the ratio between the number of two tunnels and direct tunnels, it is an objective of the approach provided herewith that high data volume is sent through the direct tunnels in order to minimize the need for two tunnel throughput.
- DT direct tunnel
- the approach suggested herein provides in particular rules to determine whether or not to use a direct tunnel, in particular for certain portions of traffic (PDP context, RAB assignment).
- an algorithm is provided that may be implemented in (or associated with) an SGSN in order to improve (e.g., maximize) a throughput capacity for the direct tunnels.
- the direct tunnels are exploited in a more efficient way thereby minimizing a throughput need for the remaining two tunnels as depicted in FIG. 2 .
- FIG. 7 shows an arrangement of components to compare a direct tunnel and two tunnel approach.
- the SGSN may decide whether to enable direct user plane tunnel between an RNC and a GGSN or if it may handle user plane data via two tunnels. Further, whenever the RAB assigned for a PDP context is released (i.e. the PDP context is preserved) the GTP-U tunnel may be established between the GGSN and SGSN in order to be able to handle the downlink packets.
- Radio Network Cell ID (Home & Office Location):
- the SGSN may start prioritizing the PDP sessions using direct tunnels, in particular by considering at least one of the following aspects:
- the GGSN maintains a data volume counter for all active PDP contexts.
- the GGSN monitors the data volume (e.g., both in uplink and in downlink direction) per session. Furthermore, the GGSN may make the decision (based on the data volume and the direct tunnel indication supplied by the SGSN) to initiate an update PDP context procedure to switch two tunnel traffic into the direct tunnel.
- the SGSN may implement a direct tunnel selection logic based on at least one of the rules mentioned herein.
- FIG. 3 shows a flow diagram comprising steps to decide whether to create two tunnels or a direct tunnel.
- the SGSN checks in a step 302 whether a direct tunnel license is available. If there is no such license available, the SGSN creates two tunnels (step 303 ). Otherwise, at least one rule may be utilized for allocating one tunnel license. Hence, if the direct tunnel (DT) license limit is not reached, it is branched from step 302 to a step 304 applying and/or processing rules during GPRS attach and/or during PDP creation. At least one of such rules may be applicable.
- DT direct tunnel
- a direct tunnel tag in an HLR user profile or a cell ID or terminal identity (e.g., IMEI, IMEISV) of the radio network may be utilized.
- rules defined by network planning and/or by the operator DT license based, network load factor, access specifics
- CAMEL Customerized Application for Mobile Network Enhanced Logic
- LI Lawful Interception
- roaming could be used as (part of) a rule.
- step 305 pursuant to step 304 it is checked whether a direct tunnel rule applies and in the affirmative, a direct tunnel is created in a step 306 . Otherwise, it is branched to step 303 and two tunnels are created.
- the SGSN may create two tunnels for all new requests.
- the SGSN may maintain a volume counter table comprising uplink and downlink data volume and session duration for all RABs having two tunnels. Based on the availability of a direct tunnel, the RAB with the highest data volume and/or with the highest session duration is moved from two tunnels to the direct tunnel. This procedure may help assigning the most active RABs (by terms of data volume and/or session time) to direct tunnel(s).
- FIG. 4 shows a flow diagram visualizing the concept of a volume counter in order to determine whether migration to direct tunnels may proof useful.
- a step 402 the SGSN volume counter for uplink (UL) and downlink (DL) traffic as well as for session duration is processed and/or maintained. For such purpose, at least one counter for each criterion may be provided.
- a step 403 it is checked whether a direct tunnel license exists, i.e. whether a direct tunnel is available. If not, it is branched to step 402 . If a direct tunnel is available, a step 404 selects a RAB based on the highest data volume and/or based on a session duration, preferably by utilizing said counter(s) maintained in step 402 .
- a PDP context update is initiated to migrate two tunnels to a direct tunnel in a step 405 .
- the GGSN may maintain a volume counter table comprising uplink and downlink data volume and/or session duration for all active PDP contexts. Since the GGSN is not aware of load factor in the SGSN as well as available direct tunnel licenses, a threshold value is defined for these counters.
- a Direct Tunnel Indicator defined in 3GPP may be used to evaluate if an allocated direct tunnel is sufficiently utilized or not.
- the GGSN may initiate
- FIG. 5A shows a flow diagram comprising an example as how to migrate two tunnels to a direct tunnel based on a GGSN volume counter and FIG. 5B shows an example as how to migrate a direct tunnel to two tunnels based on the GGSN volume counter.
- the GGSN volume counter for uplink (UL) and downlink (DL) traffic as well as for session duration is processed and/or maintained in a step 502 a .
- a step 503 a it is checked whether a counter threshold is reached. If not, it is branched to step 502 a . If the counter threshold is reached, it is checked in a step 504 a whether a DTI is available. If no DTI is available, the GGSN initiates a PDP update procedure to migrate two tunnels to a direct tunnel (step 506 a ). If, however, such DTI is available in step 504 a , it is branched to a step 505 a and data traffic is continued to be conveyed via the direct tunnel.
- the GGSN volume counter for uplink (UL) and downlink (DL) traffic as well as for session duration is processed and/or maintained in a step 502 b .
- a step 503 b it is checked whether the data traffic is below a threshold or value that may be predetermined or defined by an operator. If not, it is branched to step 502 b . If the data traffic has reached said threshold or value, it is checked in a step 504 b whether a DTI is available. If such DTI is available, the GGSN initiates a PDP update procedure to migrate a direct tunnel to two tunnels (step 505 b ). If, however, such DTI is not available in step 504 b , it is branched to a step 506 b and data traffic is continued to be conveyed via the two tunnels.
- Tunnel Creation & Deletion Rules can be Driven by GGSN Based on Traffic Analysis Rules
- Traffic analysis in the GGSN can indicate a usage of a service type. Such traffic analysis that is based on the GGSN is not utilized by the SGSN. P2P/VoIP traffic session detection provided by the GGSN may help the SGSN to establish a direct tunnel, because an average session duration for such traffic is significantly longer than other traffic and it may also indicate a high(er) data volume.
- the SGSN may send a DTI to the GGSN.
- the GGSN may utilize traffic analysis results to recommend (not) using the direct tunnel mechanism.
- the GGSN may initiate a “Network initiated PDP modification” based on L3/L4/L7 traffic optionally indicating the recommendation of not/using a direct tunnel.
- FIG. 6 shows a flow diagram comprising steps to decide whether to migrate PDP context to a direct tunnel based on a traffic analysis provided by the GGSN.
- a type of traffic it checked, e.g., point-to-point traffic (P2P). If there is no such type of traffic it is branched to step 602 . Otherwise, in a step 604 , it is checked whether DTI is available. If this is not the case, the GGSN initiates a PDP update procedure to migrate two tunnels to a direct tunnel in a step 605 . If no DTI is available in step 604 , it is branched to a step 606 and data is continued to be conveyed via the two tunnels.
- P2P point-to-point traffic
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2008/065891 WO2010057529A1 (en) | 2008-11-20 | 2008-11-20 | Method and device for assigning traffic to a direct tunnel, computer program product and computer-readable medium |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110222430A1 true US20110222430A1 (en) | 2011-09-15 |
Family
ID=40651637
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/130,414 Abandoned US20110222430A1 (en) | 2008-11-20 | 2008-11-20 | Method and device for assigning traffic to a direct tunnel, computer program product and computer-readable medium |
Country Status (7)
Country | Link |
---|---|
US (1) | US20110222430A1 (ja) |
EP (1) | EP2359541A1 (ja) |
JP (1) | JP5167417B2 (ja) |
CN (1) | CN102224712A (ja) |
AR (1) | AR074384A1 (ja) |
TW (1) | TW201038014A (ja) |
WO (1) | WO2010057529A1 (ja) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140056235A1 (en) * | 2012-02-14 | 2014-02-27 | Telefonaktiebolaget L M Ericsson (Publ) | Smart 3GDT |
US20140112151A1 (en) * | 2011-06-20 | 2014-04-24 | Telefonaktiebolaget L M Ericsson (Publ) | 3rd generation direct tunnel (3gdt) optimization |
US20150049719A1 (en) * | 2012-03-28 | 2015-02-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Establishing Direct Tunnel |
US9271313B2 (en) * | 2011-07-01 | 2016-02-23 | Telefonaktiebolaget L M Ericsson (Publ) | Service frequency based 3GDT |
JP2016192811A (ja) * | 2016-08-04 | 2016-11-10 | ▲ホア▼▲ウェイ▼技術有限公司Huawei Technologies Co.,Ltd. | ダイレクトトンネルを確立するための方法および装置 |
US10306685B2 (en) * | 2014-04-22 | 2019-05-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and nodes for handling a GTP-U direct tunnel |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6603738B1 (en) * | 1996-03-25 | 2003-08-05 | Nokia Telecommunications Oy | Prioritization of data to be transmitted in a router |
US20050237969A1 (en) * | 2004-04-24 | 2005-10-27 | Samsung Electronics Co., Ltd. | Apparatus and method for producing a tunnel in an integrated serving general packet radio service (GPRS) service node (SGSN) and gateway GPRS support node (GGSN) in a universal mobile telecommunication service (UMTS) network |
US7023820B2 (en) * | 2000-12-28 | 2006-04-04 | Nokia, Inc. | Method and apparatus for communicating data in a GPRS network based on a plurality of traffic classes |
US20070213057A1 (en) * | 2006-03-08 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting routing area update procedures in a single tunnel gprs-based wireless communication system |
US20080020775A1 (en) * | 2004-12-29 | 2008-01-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Priority Bearers In A Mobile Telecommunication Network |
US20100061386A1 (en) * | 2006-12-22 | 2010-03-11 | Telefonaktiebolaget L M Ericsson (Publ) | Method and Arrangement Relating to Communications Network Services Request Activation |
US7896393B2 (en) * | 2006-03-03 | 2011-03-01 | Takata-Petri Ag | Airbag module |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101080913A (zh) * | 2004-12-14 | 2007-11-28 | 松下电器产业株式会社 | 通信路由优化方法、相应的设备和系统 |
CN100433705C (zh) * | 2005-03-17 | 2008-11-12 | 中兴通讯股份有限公司 | 高速下行分组接入系统中映射调度优先级标志的方法 |
EP1889494B1 (en) * | 2005-06-07 | 2019-12-18 | Apple Inc. | Providing a data function in an access gateway node |
CN101207546A (zh) * | 2006-12-18 | 2008-06-25 | 华为技术有限公司 | 一种动态建立隧道的方法、隧道服务器和系统 |
-
2008
- 2008-11-20 JP JP2011536743A patent/JP5167417B2/ja not_active Expired - Fee Related
- 2008-11-20 EP EP08875345A patent/EP2359541A1/en not_active Withdrawn
- 2008-11-20 US US13/130,414 patent/US20110222430A1/en not_active Abandoned
- 2008-11-20 CN CN2008801320442A patent/CN102224712A/zh active Pending
- 2008-11-20 WO PCT/EP2008/065891 patent/WO2010057529A1/en active Application Filing
-
2009
- 2009-11-20 AR ARP090104473A patent/AR074384A1/es unknown
- 2009-11-20 TW TW098139425A patent/TW201038014A/zh unknown
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6603738B1 (en) * | 1996-03-25 | 2003-08-05 | Nokia Telecommunications Oy | Prioritization of data to be transmitted in a router |
US7023820B2 (en) * | 2000-12-28 | 2006-04-04 | Nokia, Inc. | Method and apparatus for communicating data in a GPRS network based on a plurality of traffic classes |
US20050237969A1 (en) * | 2004-04-24 | 2005-10-27 | Samsung Electronics Co., Ltd. | Apparatus and method for producing a tunnel in an integrated serving general packet radio service (GPRS) service node (SGSN) and gateway GPRS support node (GGSN) in a universal mobile telecommunication service (UMTS) network |
US20080020775A1 (en) * | 2004-12-29 | 2008-01-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Priority Bearers In A Mobile Telecommunication Network |
US7896393B2 (en) * | 2006-03-03 | 2011-03-01 | Takata-Petri Ag | Airbag module |
US20070213057A1 (en) * | 2006-03-08 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting routing area update procedures in a single tunnel gprs-based wireless communication system |
US20100061386A1 (en) * | 2006-12-22 | 2010-03-11 | Telefonaktiebolaget L M Ericsson (Publ) | Method and Arrangement Relating to Communications Network Services Request Activation |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140112151A1 (en) * | 2011-06-20 | 2014-04-24 | Telefonaktiebolaget L M Ericsson (Publ) | 3rd generation direct tunnel (3gdt) optimization |
US9998909B2 (en) * | 2011-06-20 | 2018-06-12 | Telefonaktiebolaget Lm Ericsson (Publ) | 3rd generation direct tunnel (3GDT) optimization |
US9271313B2 (en) * | 2011-07-01 | 2016-02-23 | Telefonaktiebolaget L M Ericsson (Publ) | Service frequency based 3GDT |
US20140056235A1 (en) * | 2012-02-14 | 2014-02-27 | Telefonaktiebolaget L M Ericsson (Publ) | Smart 3GDT |
US10251209B2 (en) * | 2012-02-14 | 2019-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Smart 3GDT |
US20150049719A1 (en) * | 2012-03-28 | 2015-02-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Establishing Direct Tunnel |
JP2015517248A (ja) * | 2012-03-28 | 2015-06-18 | ▲ホア▼▲ウェイ▼技術有限公司 | ダイレクトトンネルを確立するための方法および装置 |
US9706587B2 (en) * | 2012-03-28 | 2017-07-11 | Huawei Technologies Co., Ltd. | Method and apparatus for establishing direct tunnel |
US10306685B2 (en) * | 2014-04-22 | 2019-05-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and nodes for handling a GTP-U direct tunnel |
JP2016192811A (ja) * | 2016-08-04 | 2016-11-10 | ▲ホア▼▲ウェイ▼技術有限公司Huawei Technologies Co.,Ltd. | ダイレクトトンネルを確立するための方法および装置 |
Also Published As
Publication number | Publication date |
---|---|
JP5167417B2 (ja) | 2013-03-21 |
EP2359541A1 (en) | 2011-08-24 |
JP2012509628A (ja) | 2012-04-19 |
WO2010057529A1 (en) | 2010-05-27 |
TW201038014A (en) | 2010-10-16 |
AR074384A1 (es) | 2011-01-12 |
CN102224712A (zh) | 2011-10-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11438746B2 (en) | Method and equipment for determining IOT service, and method and equipment for controlling IOT service behavior | |
US10631230B2 (en) | Network controlled extended access barring for user devices | |
KR101454134B1 (ko) | 데이터 스트림을 스케줄링하기 위한 방법, 장비 및 시스템 | |
US9924406B2 (en) | Blended data transmission network for machine type communications | |
CN104412628A (zh) | 用于向应用服务平台提供对包含上下文数据的核心网络信息的访问的方法、装置和计算机程序产品 | |
KR102291766B1 (ko) | 통신 시스템에서 데이터 흐름 전송을 위한 개선된 우선권 핸들링 | |
US20110222430A1 (en) | Method and device for assigning traffic to a direct tunnel, computer program product and computer-readable medium | |
US9203766B2 (en) | Quality of service for serving node and method | |
EP2852223A1 (en) | Access to local andsf server with dedicated bearer | |
US9705793B2 (en) | Method for informing a node in a radio access network (RAN) about a type of service associated with an IP packet | |
EP2850873B1 (en) | Inter-carrier differentiation using allocation and retention priority in a wireless communication system | |
US10122634B1 (en) | Proactive response to predicted bearer loss | |
CN107809750A (zh) | 一种VoLTE业务处理方法及装置 | |
JP6500777B2 (ja) | 通信システムにおける通信装置および方法、通信パスの制御装置および方法 | |
KR102126999B1 (ko) | 데이터 서비스 제어 방법 및 그 장치 | |
EP2925074B1 (en) | Application aware communication system | |
JP5952719B2 (ja) | 通信システム、通信制御方法および通信制御装置 | |
JP6125585B2 (ja) | マルチサービスユーザデバイスのためのネットワーク制御による拡張アクセス規制 | |
KR102022613B1 (ko) | 이동통신을 위한 발신 트래픽의 부하 제어 방법 및 그 장치 | |
KR102126925B1 (ko) | 로밍 트래픽 관리장치 및 방법 | |
KR20130015894A (ko) | 가입자 우선 순위에 따른 과부하 제어 시스템, 장치 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA SIEMENS NETWORKS OY, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ANGERVUORI, JARMO SAKARI;PANDEY, RAVI SHANKAR;REEL/FRAME:031265/0450 Effective date: 20110513 |
|
AS | Assignment |
Owner name: NOKIA SOLUTIONS AND NETWORKS OY, FINLAND Free format text: CHANGE OF NAME;ASSIGNOR:NOKIA SIEMENS NETWORKS OY;REEL/FRAME:034294/0603 Effective date: 20130819 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |