WO2005076541A1 - Optimisation de reseau fondee sur le comportement d'utilisation - Google Patents

Optimisation de reseau fondee sur le comportement d'utilisation Download PDF

Info

Publication number
WO2005076541A1
WO2005076541A1 PCT/IB2005/000226 IB2005000226W WO2005076541A1 WO 2005076541 A1 WO2005076541 A1 WO 2005076541A1 IB 2005000226 W IB2005000226 W IB 2005000226W WO 2005076541 A1 WO2005076541 A1 WO 2005076541A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
network
related data
data flow
network portion
Prior art date
Application number
PCT/IB2005/000226
Other languages
English (en)
Inventor
Sinikka Sarkkinen
Jari Isokangas
Original Assignee
Nokia Corporation
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
Priority claimed from US10/831,317 external-priority patent/US20050174965A1/en
Application filed by Nokia Corporation filed Critical Nokia Corporation
Publication of WO2005076541A1 publication Critical patent/WO2005076541A1/fr

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/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/52—Allocation or scheduling criteria for wireless resources based on load

Definitions

  • the present invention relates to a method and system for allocating resources of a network portion through which service-related data flows are routed in a transpar- ent manner, such as a radio access network.
  • Fig. 1 shows a schematic network architecture of a Universal Mobile Telecommunications System (UMTS), the European 3G mobile communication system, which comprises two parts: a UMTS terrestrial radio access network (UTRAN) and a core network (CN).
  • UTRAN provides the air interface for UMTS terminals and the CN is responsible for switching and routing of calls and data connections to external networks.
  • UTRAN comprises one or more radio network subsystems (RNS) each comprising a radio network controller (RNC), several node B and user equipment (UE).
  • RNC is responsible for the control of the radio resources of the UTRAN and plays a very important role in power control (PC), handover control (HC), admission control (AC), load control (LC) and packet scheduling (PS) procedures, which are at least partially locate at the RNC.
  • the RNC interfaces the CN via an lu interface and uses lub interfaces to control Node Bs.
  • the lur interface between RNCs allows soft handover between RNCs.
  • the Node B is the 3G equivalent to a conventional base station.
  • the Node B performs the air interface processing, which includes channel coding, interleaving, rate adaptation and spreading.
  • the connec- tion with the user equipment (UE) is made via a Uu interface, which is actually the WCDMA (Wideband Code Division Multiple Access) radio interface.
  • WCDMA Wideband Code Division
  • the CN integrates circuit and packet switched traffic. It comprises packet switched GPRS (General Packet Radio Services) nodes, i.e. a Serving GPRS Support
  • SGSN Gateway GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • PS networks e.g., IP and/or Multimedia networks
  • CS networks e.g., PSTN, PLMN, ISDN
  • Other CN nodes are an EIR (Equipment Identity Register) , a HSS (Home Subscriber Server) and an AUC (Authentication Center).
  • EIR Equipment Identity Register
  • HSS Home Subscriber Server
  • AUC Authentication Center
  • the used radio bearers can be chosen from either 2G or 3G CS or PS bearer sets. PS bearers provide more trunking gain and better resources utilization while CS bearers offer better performance for those services with stringent delay requirements. All the multimedia services are mainly characterized by the necessity from the network point of view to guarantee certain Quality of Service (QoS) requirements.
  • QoS Quality of Service
  • UMTS In UMTS, all signaling associated with service session establishment is carried out by the control plane through different QoS management functions, i.e., bearer service management, subscription, translation and admission & capability.
  • QoS management functions i.e., bearer service management, subscription, translation and admission & capability.
  • a primary PDP (Packet Data Protocol) context is activated for RTSP (Real- Time Streaming Protocol) signaling using interactive UMTS traffic class.
  • the interactive traffic class has a priority based handling instead of guarantees based handling, being the reliability requirement the target in this case.
  • the control plane functions are distributed in different layers of several network entities.
  • the QoS requirements of the application in the user equipment (UE) are mapped into 3G QoS attributes.
  • a Session Management (SM) protocol message from the UE to the SGSN of the PS domain initiates the PDP context activation procedure.
  • HLR Home Location Register
  • HLR Home Location Register
  • local admission control is performed, e.g., based on the state of the buffers, the CPU load, etc..
  • the SGSN maps the 3G QoS attributes into Radio Access Bearer (RAB) QoS attributes and triggers a RAB assignment procedure in the RAN by using the Radio Access Network Application Protocol (RANAP).
  • RAB Radio Access Bearer
  • admission control is basically based on the availability of radio resources.
  • RAB attributes are mapped into Radio Bearer (RB) parameters used in the physical and link layers (e.g. spreading codes, transmission modes, etc.).
  • RB Radio Bearer
  • a RB according to these parameters is established and it is reported to the SGSN, which employs GPRS Tunneling Protocol for Control Plane (GTP-c) to indicate the GGSN that a new PDP context has to be created.
  • GTP-c GPRS Tunneling Protocol for Control Plane
  • This object is achieved by a method of allocating resources of a network portion through which service-related data flows are routed in a transparent manner, the method comprising the steps of: - forwarding to the network portion a service behavior classification information indicating the behavior of the service-related data flow during its lifetime; and - allocating or configuring the resources of the network portion in depend- ence on the service behavior classification information.
  • a network device for controlling resource allocation in a first network portion through which a service-related data flow is routed in a transparent manner, the device comprising: - evaluating means for evaluating a service behavior classification information received from a second network portion an and indicating the behavior of the service-related data flow during its lifetime; and - allocating means for allocating the resources of the network portion in dependence on the service behavior classification information.
  • a server device for forwarding a service-related data flow through a network portion in a transparent manner, the device being configured to forward to the network portion a service behavior classification information indicating the behavior of the service-related data flow during its lifetime.
  • the service mix becomes transparent to the RNC and network operators are enabled to convert their service mix into different service behavior classes, so that RNC esti- mation can be made based on a mix of service behavior classes of different service-related data flows.
  • new services are introduced by network operators, only the percentage of certain service behavior classes is changed, kept the same or decreased, and therefore resource allocation or implementation of network de- ices may follow only the development of the service behaviors class grade, while the services behind each class can be kept unknown.
  • One service behavior class can consist of different kinds of services, which have approximately the same service profile upon their lifetime. When weight of one service is decreased the weight of another service may increase by keeping the total importance of the class the same. I.e. services can come and go and no impact is seen in the allocation of network resources. Moreover, it is much easier to handle a few service behavior classes than a huge number of different services.
  • the service behavior class principles can be implemented in an RNC, so that it should be possible to measure how much traffic or radio access bearers are belonging into each class. This information can be used for RNC optimization Thus, together with the QoS information the RNC capacity and performance can be es- timated more reliable.
  • the resource allocating may comprise optimizing at least one of system and network elements of the network portion based on the service behavior classification information.
  • the system optimization may comprise configuration of at least one of a base station, a common channel, and a cell.
  • the optimization of network element may comprise allocation of network element resources for different use.
  • the resource allocation may comprises at least one of selecting, modifying and establishing an access bearer.
  • the classification information may define at least one of a continuance, a data amount, a length of idle periods, and a number of flows of said service-related data flow.
  • the continuance may specify whether or not the service-related data flow is divided into sub-sessions
  • the number of flows may specify whether the service-related data flow consists of one flow or more than one flow
  • the data amount may specify whether the service-related data flow consists of more or less than a predetermined amount of data
  • the length of idle periods may specify predetermined ranges of time periods.
  • the network portion may be a radio access network.
  • the classification information may forwarded in a bearer setup request, or any other RANAP signaling message of the radio access network.
  • Fig. 1 shows a schematic block diagram of a network architecture in which the preferred embodiment of the present invention can be implemented
  • Fig. 2 shows a schematic functional block diagram of a bearer establishment procedure according to the preferred embodiment
  • Fig. 3 shows a table of an exemplary service behavior classification according to the preferred embodiment.
  • UTRAN resources are established and released on a demand basis.
  • demand are based on new classes which describe the behavior of the services during their lifetime. These classes could be categorized e.g. as service behavior classes.
  • the use of the service behavior classes means that each service is evaluated and categorized into a specific service behavior class which may represent, e.g., a certain type of parameter set in the RNC.
  • the used parameter set may be based on the behavior of the RNC in different situations.
  • the parameter set is known, also the load and capacity requirements for the system in the UTRAN and in the RNC can be evaluated.
  • the basic idea is to evaluate the services from the RNCs functionality point of view. By doing this, the service can be kept transparent to the RNC/UTRAN, but in the UTRAN, the service aspect also can be taken into account when the system is designed and/or dimensioned.
  • the resources needed by certain services are better known and this information can be used for system and/or RNC optimization and further implementation purpose.
  • the service behavior classes can be regarded as the UTRAN way to take services into account without getting knowledge of the service itself.
  • Fig. 2 shows a schematic functional block diagram of the bearer establishment procedure.
  • This functional block diagram describes the functionalities provided in a radio network controlling device of a RAN, such as the RNC, which is responsible for allocation, management and termination of radio bearers.
  • radio bearers are established when radio access bearer (RAB) establishment is re- quested by the CN, e.g. by an SGSN of the PS domain, as indicated by the functional step 100.
  • the corresponding RAB setup request comprises specific QoS parameters and a specific service behavior class allocated to the service for which the radio bearer is requested.
  • the service behavior class information can be fetched e.g. from the operator or it can be measured from the traffic itself.
  • a resource manager functionality 102 in the RNC which is responsible for admission control and resource allocation, first determines whether there are enough resources to service the request. If there is no capacity problem (NP), the selected radio bearer is configured and set up (functional step 108). In particular, the resource manager functionality 102 selects an appropriate radio bearer according to the QoS values of the parameters and the service behavior class specified in the RAB setup request. If there is a conditional capacity problem (YB), an existing radio access bearer with lower priority may be degraded (reconfigured) or released (functional step 106) so as to allow selection and establishment of the new radio bearer.
  • NP no capacity problem
  • YB conditional capacity problem
  • an existing radio access bearer with lower priority may be degraded (reconfigured) or released (functional step 106) so as to allow selection and establishment of the new radio bearer.
  • the setup request will be rejected with a corresponding response message including a notification of the cause (functional step 104).
  • the resource manager functionality 102 may put the setup request into a waiting queue 103, to start the establishment procedure again at a later point in time.
  • a radio bearer is specified by the type of channel it is using, the parameters describing this channel and the configuration of the radio protocols.
  • the channel is also specified by the frequency and the CDMA (Code Division Multiple Access) codes. These codes define raw data-rate on the channel.
  • error coding is used and additional redundancy may be provided at the radio link layer control function by a retransmission protocol. The choice of the error coding code and whether to use retransmissions or not depends on the level of reliability needed for the radio bearer and the delay requirements. Any mapping function can be used for allocating the QoS parameter and service behavior class given in the radio access bearer set-up to a specific radio bearer to be selected.
  • the UTRAN behavior with different service mixes can be estimated.
  • the network operator can tune the system (i.e. RNC) to work in most optimal way.
  • the system i.e. RNC
  • the operator should configure more re- sources to the common channels and define the corresponding parameters to fit data transmission on common channels. If the situation is vice versa, i.e. only dedicated channels are needed, then some resources can be taken from the common channels and this extra resource can be allocated to the dedicated channels.
  • the service behavior class or category can be taken into account dur- ing RAB allocation or establishment or when the RNC is configured, e.g. inactivity timers can be tuned to fit to majority of the services, which may decrease signaling load.
  • the possible bottlenecks - caused by different kind of service data flows - are easier to detect by the RNC, e.g. input and/or feedback can be provided for both RNC application and platform implementation. This provides increased general understanding how services are to be handled in the system including UTRAN.
  • Fig. 3 shows a table of an exemplary classification for the services based on how they are seen from radio interface/RNC behavior point of view. Important parameters which impact to the radio interface/RNC behavior are:
  • the service From the radio interface point of view the service either has assigned resources or not.
  • the release of the resources is controlled by monitoring the occupancy of the resources.
  • a service which generates idle periods between data bursts may, from air interface point of view, be seen as a non- continuous service, even if the service is active from PDP context point of view.
  • Idle periods When the resources are not used due to non-activity of the application, the resources are released from the air interface and the lub interface. Depending on how long the bearer is inactive the UE goes to one of the states RRC Connected (UE is known in UTRAN), Cell-FACH (only common resources are available, which limits how much user plane data is possible to be sent through CCH), Cell-PCH (for UE no resources have been assigned and it is not allowed to use CCH resources either. UE has to be paged from the cell), URA-PCH (for UE no resources have been assigned and it is not al- > lowed to use CCH resources either.
  • RRC Connected UE is known in UTRAN
  • Cell-FACH only common resources are available, which limits how much user plane data is possible to be sent through CCH
  • Cell-PCH for UE no resources have been assigned and it is not allowed to use CCH resources either.
  • URA-PCH for UE no resources have been assigned
  • UE has to be paged from URA (UTRAN Routing Area), RRC Idle (UE is known only in CN, but not known in UTRAN even if it may have a PDP context at CN side), and RRC Connected / Cell- DCH state (used only when radio bearer has assigned resources for data transmission).
  • URA UTRAN Routing Area
  • RRC Idle UE is known only in CN, but not known in UTRAN even if it may have a PDP context at CN side
  • RRC Connected / Cell- DCH state used only when radio bearer has assigned resources for data transmission.
  • the RNC Based on the received data amount upon RAB establishment (or wake up of the existing RAB), the RNC will select the most appropriate transport channel for the service, e.g., a common channel (services under 1 kB (today under 128 byte) are allowed to use CCH), a dedicated channel (all RT traffic and NRT traffic, which is not allowed to use CCH is transmitted by using DCHs), and HSDPA (High Speed Downlink Packet Access).
  • a common channel services under 1 kB (today under 128 byte) are allowed to use CCH
  • a dedicated channel all RT traffic and NRT traffic, which is not allowed to use CCH is transmitted by using DCHs
  • HSDPA High Speed Downlink Packet Access
  • twelve ser- vice behavior classes B1 and B12 with different parameter values for the above parameters service continuance, data amounts, idle periods, and number of flows.
  • the first service behavior classes B1 to B4 are distinguished by the amount of data and the number of flows, while only one service is provided and idle periods are not relevant.
  • the remaining service classes B5 to B12 are all re- lated to services which are divided into sub-sessions, and are divided into classes B5 to B8 and B9 to B12 by their amount of data. Further respective divisions into sub-groups of service behavior classes can be made based on the lengths of the idle periods and the number of flows. It is noted that the present invention is not restricted to the preferred embodiments described above.
  • the present invention may be implemented in any access network where resource or capacity allocation has to be performed for connection establishment or device implementation for transparent connections.
  • the service behavior classification may be based on only one or more of the above parameters or on any other parameters suitable to describe the behavior of concerned services. The embodiments may thus vary within the scope of the attached claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système permettant d'affecter des ressources d'une partie réseau par le biais desquelles les débits de données d'utilisation sont acheminés de manière transparente, l'affectation des ressources étant exécutée sur la base d'informations de classification de comportement d'utilisation indiquant le comportement du débit de données d'utilisation pendant sa durée de vie et communiquées à ladite partie réseau. Ainsi, les exigences de capacité et d'efficacité lors d'une transmission transparente peuvent être estimées plus fiables.
PCT/IB2005/000226 2004-02-06 2005-01-31 Optimisation de reseau fondee sur le comportement d'utilisation WO2005076541A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP04002687.4 2004-02-06
EP04002687 2004-02-06
US10/831,317 US20050174965A1 (en) 2004-02-06 2004-04-26 Network optimization based on service behavior
US10/831,317 2004-04-26

Publications (1)

Publication Number Publication Date
WO2005076541A1 true WO2005076541A1 (fr) 2005-08-18

Family

ID=34839783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2005/000226 WO2005076541A1 (fr) 2004-02-06 2005-01-31 Optimisation de reseau fondee sur le comportement d'utilisation

Country Status (1)

Country Link
WO (1) WO2005076541A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007143947A1 (fr) * 2006-06-05 2007-12-21 Huawei Technologies Co., Ltd. Procédé et système d'attribution de ressources et dispositif de réseau et terminal d'accès

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000070831A1 (fr) * 1999-05-17 2000-11-23 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil fournissant des services supports d'acces radio
US20020114305A1 (en) * 2001-02-09 2002-08-22 Johnson Oyama Signaling quality of service class for use in multimedia communicatations
US20030081592A1 (en) * 2001-06-01 2003-05-01 Ainkaran Krishnarajah Method and apparatus for transporting different classes of data bits in a payload over a radio interface

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000070831A1 (fr) * 1999-05-17 2000-11-23 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil fournissant des services supports d'acces radio
US20020114305A1 (en) * 2001-02-09 2002-08-22 Johnson Oyama Signaling quality of service class for use in multimedia communicatations
US20030081592A1 (en) * 2001-06-01 2003-05-01 Ainkaran Krishnarajah Method and apparatus for transporting different classes of data bits in a payload over a radio interface

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP: "3GPP TS 23.107 V6.0.0:Technical Specification Group Services and System Aspects; Quality of Service (QoS) concept and architecture (Release 6)", 3GPP, December 2003 (2003-12-01), SOPHIA ANTIPO,FR, XP002322545, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/html-info/23107.htm> [retrieved on 20050329] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007143947A1 (fr) * 2006-06-05 2007-12-21 Huawei Technologies Co., Ltd. Procédé et système d'attribution de ressources et dispositif de réseau et terminal d'accès

Similar Documents

Publication Publication Date Title
JP4852044B2 (ja) 移動体通信網で無線リソースをプリエンプティブに管理する方法
EP1787436B1 (fr) Methode et systeme pour gerer des ressources radio dans des reseaux de communication mobile, reseau associe et produit de programme informatique correspondant
US8532033B2 (en) Selective RAB assignment
CN101091359B (zh) 在移动电信网络中将分组转到载体的方法
US8223758B2 (en) System and method of load dependent rate policing
KR100994318B1 (ko) 효과적인 무선자원 관리 방법
JP5523347B2 (ja) 制御チャネルリソース上の負荷に基づいて、マルチキャリア無線通信システムにおいてキャリアに遊休状態のアクセス端末を割り当てる方法
KR101059876B1 (ko) 이동통신 시스템의 서비스 품질 보장을 위한 데이터전송량 선택 방법
KR100964684B1 (ko) 이동통신 시스템의 방송 및 멀티캐스트 서비스 제공방법
JP2007520131A (ja) Ｕｔｒａｎ無線アクセスネットワークにおける無線リソース管理方法、コアネットワークサービスノード、および無線アクセスネットワーク制御装置
US8509242B2 (en) Method and device for controlling data flows at communication terminals
KR100842644B1 (ko) 광대역 통신 시스템에서 비실시간 트래픽 송신 시스템 및 방법
CA2404523C (fr) Transmission de donnees en paquets
CN100384298C (zh) 业务优先级调度实现方法
US20070258364A1 (en) Resource control for scheduled and non-scheduled traffic
US20070053288A1 (en) Wireless communication method and apparatus for selecting a channel type for a call
US20050174965A1 (en) Network optimization based on service behavior
EP1540979B1 (fr) Procede permettant de fournir des services de telecommunications, systeme associe et produit de technique d&#39;informations
CN101111039A (zh) 用于高速下行分组接入系统中的业务量测量控制方法
US20050185655A1 (en) Process for pre-emption of resources from a mobile communications network, with a view to establishing a service according to a maximum associated pre-emption rate
Bejaoui et al. Handover and class-based Call Admission Control policy for 4G-heterogeneous mobile networks
US20060264219A1 (en) Architecture for integration of application functions within mobile systems
WO2005076541A1 (fr) Optimisation de reseau fondee sur le comportement d&#39;utilisation
GB2422749A (en) Establishing a radio connection between a terminal and a data service based on service required and terminal type.
WO2007129186A1 (fr) Contrôle de ressources pour trafic planifié et non planifié

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase