WO2014169957A1 - Contrôle d'admission de connexion dans des communications - Google Patents

Contrôle d'admission de connexion dans des communications Download PDF

Info

Publication number
WO2014169957A1
WO2014169957A1 PCT/EP2013/058085 EP2013058085W WO2014169957A1 WO 2014169957 A1 WO2014169957 A1 WO 2014169957A1 EP 2013058085 W EP2013058085 W EP 2013058085W WO 2014169957 A1 WO2014169957 A1 WO 2014169957A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
lub interface
admission control
cac
network apparatus
Prior art date
Application number
PCT/EP2013/058085
Other languages
English (en)
Inventor
Heikki Juhani HAKOSALO
Yong Kang WU
Sami Antero TILANDER
Yun Ma
Heikki Matti Antero AHOLA
Marko Tapani MIKKOLA
Original Assignee
Nokia Solutions And Networks Oy
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 Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2013/058085 priority Critical patent/WO2014169957A1/fr
Publication of WO2014169957A1 publication Critical patent/WO2014169957A1/fr

Links

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]

Definitions

  • the exemplary and non-limiting embodiments of this invention relate generally to wireless communications networks, and more particularly to con- nection admission control.
  • Connection admission control involves actions and permissions in network communication that identifies where the connection is permit- ted on the basis of network ability. These actions are initiated during call setup or during reconnecting of calls.
  • CAC is based on an algorithm used to discriminate incoming and/or outgoing network traffic.
  • CAC may be used to decide which traffic is allowed or rejected in a certain network.
  • CAC may also be used for congestion control.
  • CAC may be used to decide whether there are enough system resources available before establishing a connection.
  • CAC may also be referred to as call admission control.
  • An aspect of the invention relates to a method for performing connection admission control CAC in a communications system, comprising steps of defining, in a first network apparatus, a maximum threshold value based on a transport capacity of an lub interface, wherein at least two network appara- tuses control at least one transport bearer that uses the lub interface; dividing the maximum threshold value into at least two network-apparatus-specific parts for the at least two network apparatuses; initiating connection admission control CAC regarding the lub interface; wherein, if it is found out that a first network-apparatus-specific part of the maximum threshold value is exceeded in the first network apparatus, the method comprises transmitting, from the first network apparatus to at least one second network apparatus, a share request including information on a CAC book-keeping value of the first network apparatus, in order the first network apparatus to request for
  • a further aspect of the invention relates to a method for initiating, in a first network apparatus, connection admission control CAC regarding an lub interface; periodically transmitting, from the first network apparatus to at least one second network apparatus, a share request including information on a CAC book-keeping value of the first network apparatus, in order the first network apparatus to request for or offer more transport capacity of the lub inter- face; periodically receiving, from the at least one second network apparatus, a share response including information on a CAC book-keeping value of the at least one second network apparatus.
  • a further aspect of the invention relates to a first apparatus comprising at least one processor; and at least one memory including a computer pro- gram code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first apparatus to carry out any of the method steps.
  • a still further aspect of the invention relates to a second apparatus comprising at least one processor; and at least one memory including a com- puter program code, wherein the at least one memory and the computer pro- gram code are configured to, with the at least one processor, cause the second apparatus to receive, from a first apparatus, information on initiation of centralized connection admission control in the first apparatus for transport bearers that use an lub interface; interrupt performing non-centralized connec- tion admission control for the transport bearers that use the lub interface.
  • a still further aspect of the invention relates to a computer program product comprising program code means configured to perform any of the method steps when the program is run on a computer.
  • a still further aspect of the invention relates to a computer-readable storage medium comprising program code means configured to perform any of the method steps when executed on a computer.
  • Figure 1 illustrates an architecture where two or more RNCs control and process UEs of a base station over the same lub link
  • Figure 2 shows a simplified block diagram illustrating exemplary system architecture
  • Figure 3 shows a simplified block diagram illustrating exemplary ap- paratuses
  • Figure 4 shows a messaging diagram illustrating an exemplary messaging event according to an embodiment of the invention
  • Figure 5 shows a schematic diagram of a flow chart according to an exemplary embodiment of the invention
  • Figure 6 shows a schematic diagram of a flow chart according to another exemplary embodiment of the invention.
  • Figure 7 shows a schematic diagram of a flow chart according to an exemplary embodiment of the invention.
  • connection admission control (CAC) establishes a connection when enough resources are available. If the connection is rejected in the absence of free/available resources, a notification 5 may be sent to an originator of the call or connection.
  • CAC may reject a call when there is insufficient CPU processing power, the upstream and downstream traffic load exceed a pre-defined (maximum) threshold, and/or the number of calls being i o handled exceeds a pre-defined limit.
  • WCDMA RAN there are different types of traffic which have different quality requirements. Traffic with different quality requirements may be prioritized. In order to guarantee high QoS to some connection types, bandwidth needs to be reserved for it. CAC may be used to reserve a right amount
  • one base station is connected to only one RNC through an lub interface.
  • This RNC terminates the control channels, takes care of power control and processes each UE of this base station.
  • the connection admission control (CAC) of the lub interface may be carried out within one
  • RNC may take care of the admission control for the egress direction (from RNC point of view; i.e. traffic direction out of RNC) and the base station takes care of the admission control for the ingress direction (from the RNC point view; i.e. the traffic direction into RNC).
  • connection admission control this means that the 35 CAC cannot be carried out independently within one RNC for the egress direc- tion (from the RNC point of view) as this one RNC is not aware of how much and how big transport bearers the other RNCs have admitted to the egress direction of the lub interface.
  • an exemplary embodiment provides a mechanism to take care of CAC in the egress direction when two or more RNCs control and process the UEs of a one BTS over the same lub link. Without this mechanism the capacity of the lub link is difficult to utilize fully. If the link capacity is divided to RNCs so that the sum of bandwidths equals to link capacity, it leads to bandwidth fragmentation, i.e.
  • one RNC may have used its total capacity and is not able to admit any more connections, even though there were capacity in the other RNC. If the sum of bandwidths exceeds the link capacity, it decreases the drawback of fragmentation but too many connections may be admitted which may lead to packet dropping on the lub link and even to a base station restart.
  • An exemplary embodiment enables the dynamical exchange of bandwidth budget and reservation status between the two RNCs.
  • An exemplary embodiment enables connecting two or more RNCs to control and process UEs for the one and same base station over the same lub link.
  • Another exemplary embodiment enables the base station also to take responsibility for the egress direction CAC as well, but that may mean more processing for the base station and also some more signalling between the base station and RNC which may slow down the call set-up.
  • CAC which is both accurate and fast
  • Using the centralised CAC each time for each such lub link may however cause more inter-RNC signalling, and thus call set-ups may be somewhat slower.
  • each RNC controlling UEs over the same lub may have its own CAC functionalities (de-centralised CAC), but when the load increases, individual CACs on each RNC may be shut down and CAC may run in a centralized manner on only one of the RNCs serving also the other RNCs and guaranteeing that the configured lub transport capacity is not exceeded by the CAC-protected traffic. This also guarantees that the configured lub capacity can be fully used by the CAC-protected traffic.
  • an adjustable CAC load threshold parameter which defines when to switch from the individual CACs running on each RNC, to the centralised CAC running on only one of the RNCs.
  • the centralised CAC may then initiate actions to notify this for each RNC controlling and processing UEs for this lub link.
  • the individual CACs may reply with their admission control situation and shut down. After this, the centralised CAC is running and takes care of CAC requests for this RNC CAC cluster. Book-keeping may be carried out per CAC, so that if switched back to the individual CAC mode, the individual CAC book-keeping is up-to-date and accurate.
  • a way to collaborate and share information between the de-centralised CAC running on each RNC to form a centralized view in an exemplary embodiment, in a first step 1 , during lub interface configuration, the two RNCs share configuration information and agree on the bandwidth and initial share of the total bandwidth. A threshold is defined for adjusting the bandwidth share. In a second step, when one RNC exceeds the 5 threshold, this RNC asks for more capacity from its counterpart. In a third step, when one connection attempt fails in one RNC due to exceeding the threshold, this RNC may retry after a short moment. Thus capacity may be fully utilized if the counterpart has some free capacity.
  • CAC is running in i o the de-centralised mode which provides fastest call set-ups and least amount of signalling but still never exceeding the configured lub capacity or never wasting the lub capacity.
  • CAC in de-centralised manner, there is not even a single unit in a single RNC that is overloaded.
  • RNCs may run a non-centralized- 15 CAC-only solution, or a hybrid centralized-CAC - non-centralized-CAC solution which is swapping between these modes when thresholds are exceeded or undercut.
  • an exemplary embodiment enables a fail and retry mechanism that may significantly reduce the waste of lub capacity in a user-acceptable way.
  • an exemplary embodiment enables having an accurate and fast CAC also when two or more RNCs control and process UEs of one base 30 station over the same lub link.
  • an exemplary embodiment relates to a distributed RNC architecture providing collaborated CAC.
  • CAC-book-keeping value between the RNCs, instead of (or in addition to) a threshold exceeding event being triggered, in order to request for/receive (or 35 offer) more transport capacity of the lub interface.
  • two or more in- dependent CACs may exchange reservation information with each other on a regular basis, thus enabling distributed CAC.
  • the present invention is applicable to any user terminal, network element, server, corresponding component, and/or to any communication system or any combination of different communication systems that support connection admission control.
  • the communication system may be a fixed communication system or a wireless communication system or a communication sys- tern utilizing both fixed networks and wireless networks.
  • the protocols used, the specifications of communication systems, servers and user terminals, especially in wireless communication develop rapidly. Such development may require extra changes to an embodiment. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the embodiment.
  • the radio system is based on WCDMA network elements.
  • the invention described in these examples is not limited to the WCDMA radio systems but can also be implemented in other radio systems, such as UMTS (universal mobile telecommunications system), GSM, EDGE, LTE, bluetooth network, WLAN or other fixed, mobile or wireless network.
  • the presented solution may be applied between elements belonging to different but compatible systems such as WCDMA, LTE and UMTS.
  • a general architecture of a communication system is illustrated in Figure 2.
  • the exemplary radio system of Figure 2 comprises a network node 201 , 202 of a network operator.
  • the network node 201 , 202 may include e.g. a radio network controller RNC1 , RNC2, mobile switching centre (MSC), MSC server (MSS), mobility management entity (MME), gateway GPRS support node (GGSN), serving GPRS support node (SGSN), home location register (HLR), home subscriber server (HSS), visitor location register (VLR), or any other network element, or a combination of network elements.
  • RNC1 , RNC2 mobile switching centre (MSC), MSC server (MSS), mobility management entity (MME), gateway GPRS support node (GGSN), serving GPRS support node (SGSN), home location register (HLR), home subscriber server (HSS), visitor location register (VLR), or any other network element, or a combination of network elements.
  • RNC1 , RNC2 mobile switching centre
  • MSC mobility management entity
  • MME mobility management entity
  • GGSN gateway GPRS support node
  • HLR home location register
  • HLR home subscriber server
  • the network node 201 and the base station 203 are connected to each other via a connection 204.
  • the network node 202 and the base station node 203 are connected to each other via a connection 208.
  • the interface between the network node 201 (that may also be called a radio network controller RNC1 ) and the base station 203 may be called an lub interface.
  • the interface between the network node 202 (that may also be called a radio network controller RNC2) and the base station 203 may be called an lub interface.
  • the network node 203 that may also be called a base station (BS) of the radio system hosts the functions for radio resource management in a public land mobile network.
  • BS base station
  • FIG. 2 shows one or more user equipment 205 located in the service area of the base station 203.
  • the user equipment refers to a portable computing device, and it may also be referred to as a user terminal.
  • Such computing devices include wireless mobile communication devices operating with or without a subscriber identification module (SIM) in hardware or in software, including, but not limited to, the following types of devices: mobile phone, smart-phone, personal digital assistant (PDA), handset, laptop computer.
  • SIM subscriber identification module
  • the user equipment 205 is capable of connecting to the base station 203 via a connection 206.
  • Figure 3 illustrates examples of apparatuses according to embodiments of the invention.
  • Figure 3 shows a user equipment 205 located in the area of a network node 203 such as a base station.
  • the user equipment 205 is configured to be in connection with the base station 203.
  • the user equipment or UE 205 comprises a controller 301 operationally connected to a memory 302 and a transceiver 303.
  • the controller 301 controls the operation of the user equipment 205.
  • the memory 302 is configured to store software and data.
  • the transceiver 303 is configured to set up and maintain a wireless con- 5 nection 206 to the base station 203.
  • the transceiver is operationally connected to a set of antenna ports 304 connected to an antenna arrangement 305.
  • the antenna arrangement 305 may comprise a set of antennas.
  • the number of antennas may be one to four, for example.
  • the number of antennas is not limited to any particular number.
  • the user equipment 205 may also comprise i o various other components, such as a user interface, camera, and media player. They are not displayed in the figure due to simplicity.
  • the network node 203 such as a base station (node-B, BTS, BS, eNB), comprises a controller 306 operationally connected to an interface 307, and a transceiver 308.
  • the controller 306 controls the operation of the base station 106.
  • the transceiver controls the operation of the base station 106.
  • the transceiver 308 is operationally connected to an antenna arrangement 309.
  • the antenna arrangement 309 may comprise a set of antennas.
  • the number of antennas may be two to four, for example.
  • the number of antennas is not limited to any
  • the base station 203 may be operationally connected (directly or indirectly) to another network element 201 , 202 of the communication system, such as a radio network controller (RNC).
  • the network element 201 , 202 may comprise a controller 31 0 operationally connected to an interface 31 1 , and a memory 31 2.
  • the controller 310 controls the operation of the net-
  • the memory 312 is configured to store software and data.
  • the base station 203 is operationally connected via a connection 204 to the network element 201 , such as a radio network controller RNC1 .
  • the base station 203 is operationally connected via a connection 208 to the network element 202, such as a radio
  • the interface between the base station 203 and the network node RNC1 201 may be called an lub interface 204.
  • the interface between the base station 203 and the network node RNC2 202 may be called an lub interface 208.
  • the interface between the network node RNC1 201 and the network node RNC2 202 may be called a CAC interface 207 (not shown in
  • the network node 201 , 202 may be operationally connected (directly or indirectly) to a further network element (not shown in Figure 3) of the communication system, such as a mobility management entity (MME), an MSC server (MSS), a mobile switching centre (MSC), a radio resource management (RRM) node, a gateway GPRS support node, an operations, administrations and maintenance (OAM) node, a home location register (HLR), a visitor location register (VLR), a serving GPRS support node, a gateway, and/or a server.
  • MME mobility management entity
  • MSC mobile switching centre
  • RRM radio resource management
  • gateway GPRS support node such as a gateway GPRS support node, an operations, administrations and maintenance (OAM) node, a home location register (HLR), a visitor location register (VLR), a serving GPRS support node, a gateway, and/or a server.
  • HLR home location register
  • VLR visitor location register
  • the memory may include volatile and/or non-volatile memory and typically stores content, data, or the like.
  • the memory may store computer program code such as software applications (for example for the de- tector unit and/or for the adjuster unit) or operating systems, information, data, content, or the like for the processor to perform steps associated with operation of the apparatus in accordance with embodiments.
  • the memory may be, for example, random access memory (RAM), a hard drive, or other fixed data memory or storage device. Further, the memory, or part of it, may be remov- able memory detachably connected to the apparatus.
  • an apparatus implementing one or more functions of a corresponding mobile entity described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of a corresponding apparatus described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof.
  • implementation can be through modules (e.g. procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers.
  • the data storage medium or the memory unit may be implemented within the processor/computer or external to the processor/computer, in which case it can be communicatively coupled to the processor/computer via various means as is known in the art.
  • User equipment may refer to any user communication device.
  • a term "user equipment” as used herein may refer to any device having a com- munication capability, such as a wireless mobile terminal, a PDA, tablet, a smart phone, a personal computer (PC), a laptop computer, a desktop computer, etc.
  • the wireless communication terminal may be an UMTS or GSM/EDGE smart mobile terminal having wireless modem.
  • the application capabilities of the device according to various embodiments of the invention may include native applications available in the terminal, or subsequently installed applications by the user or operator or other entity.
  • the network apparatus 201 , 202, 203 may be implemented in any network element, such as a server.
  • FIG. 3 is a block diagram of an apparatus according to an em- bodiment of the invention. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the functionality of the network apparatus 201 , 202, 203, 205 is described in more detail below with Figures 4 to 7. It should be appreciated that the apparatus 201 , 202, 203, 205 may comprise other units used in or for connection admission control. However, they are irrelevant to the actual invention and, therefore, they need not to be discussed in more detail here.
  • the apparatus may also be a user terminal which is a piece of equipment or a device that associates, or is arranged to associate, the user terminal and its user with a subscription and allows a user to interact with a communications system.
  • the user terminal presents information to the user and allows the user to input information.
  • the user terminal may be any terminal capable of receiving information from and/or transmitting information to the network, connectable to the network wirelessly or via a fixed connection. Examples of the user terminal include a personal computer, a game console, a laptop (a notebook), a personal digital assistant, a mobile station (mobile phone), and a line telephone.
  • the apparatus 201 , 202, 203, 205 may generally include a processor, controller, control unit or the like connected to a memory and to various interfaces of the apparatus.
  • the processor is a central processing unit, but the processor may be an additional operation processor.
  • the processor may comprise a computer processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), and/or other hardware components that have been programmed in such a way to carry out one or more functions of an embodiment.
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • an apparatus implementing one or more functions of a corresponding mobile entity described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of a corresponding apparatus described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof.
  • implementation may be through modules (e.g. procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers.
  • the data storage medium or the memory unit may be implemented within the processor/computer or external to the processor/computer, in which case it may be communicatively coupled to the processor/computer via various means as is known in the art.
  • a network element 201 which may comprise e.g. a radio network node such as a first radio network controller RNC1 , may perform, in item 401 , non-centralized connection admission control for at least one transport bearer that uses a lub interface controlled by the first radio network controller RNC1 and by a second radio network controller RNC2.
  • a network element 202 which may comprise e.g. at least one radio network node such as the second radio network controller 202 RNC2, may perform non-centralized connection admission control for at least one transport bearer that uses the lub interface controlled by the first radio network controller 201 RNC1 and by the second radio network controller 202 RNC2.
  • the second radio network controller RNC2 may inform the first radio network controller 201 RNC1 on the exceeding of the threshold value.
  • the first radio network controller 201 RNC1 may receive the information 404, and initiate centralized connection admission control.
  • the first radio network controller 201 RNC1 starts to perform, regarding the lub interface in question, the (centralized) connection admission control CAC for each radio network controller 201 RNC1 , 202 RNC2 controlling at least one transport bearer that uses said lub interface.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202 controlling said lub interface, on the initiation of the centralized connection admission control in the first radio network controller RNC1 , in order said other radio network controllers to interrupt performing non- centralized connection admission control regarding said lub interface.
  • the second radio network controller 202 RNC2 may receive the information 406, and interrupt non-centralized connection admission control in the second radio network controller 202 RNC2 regarding said lub interface.
  • a minimum threshold value e.g. traffic load or number of calls
  • the second radio network controller RNC2 may inform the first radio network controller 201 RNC1 on the traffic load/number of calls being below the minimum threshold value.
  • the first radio network controller 201 RNC1 may receive the information 409, and interrupt centralized connection admission control.
  • the first radio network controller 201 RNC1 ceases to perform, regarding the lub interface in question, the (centralized) connection admission control CAC for each radio network controller 201 RNC1 , 202 RNC2 controlling at least one transport bearer that uses said lub interface.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202 on the interruption of the centralized connection admission control in the first radio network controller 201 RNC1 , in order said other radio network controllers to initiate performing non-centralized connection admission control regarding said lub interface.
  • the first radio network controller 201 RNC1 may initiate non-centralized connection admission control in the first radio network controller 201 RNC1 regarding said lub interface.
  • the second radio network controller 202 RNC2 may receive the information 41 1 , and initiate non-centralized connection admission control in the second radio network controller 202 RNC2 regarding said lub interface.
  • FIG. 5 is a flow chart illustrating an exemplary embodiment.
  • the apparatus 201 which may comprise e.g. a network element (network node, e.g. a first radio network controller, RNC1 ), may perform, in item 501 , non- centralized connection admission control for at least one transport bearer that uses a lub interface controlled by the first radio network controller RNC1 and by at least one second radio network controller RNC2.
  • a maximum threshold value e.g.
  • the first radio network controller 201 RNC1 may initiate centralized connection admission control. This means that the first radio network controller 201 RNC1 starts to perform, regarding the lub interface in question, the (centralized) connection admission control CAC for each radio network controller 201 RNC1 , 202 RNC2 controlling at least one transport bearer that uses said lub interface.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202 controlling said lub interface, on the initiation of the centralized connection admission control in the first radio network controller RNC1 , in or- der said other radio network controllers to interrupt performing non-centralized connection admission control regarding said lub interface.
  • the first radio network controller 201 RNC1 may interrupt centralized connection admission control.
  • the first radio network controller 201 RNC1 ceases to perform, regarding the lub interface in question, the (centralized) connection admission control CAC for each radio network controller 201 RNC1 , 202 RNC2 controlling at least one transport bearer that uses said lub interface.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202, on the interruption of the centralized connection admission control in the first radio network controller 201 RNC1 , in order said other radio network controllers to initiate performing non-centralized connection admission control regarding said lub interface.
  • the first radio network controller 201 RNC1 may initiate non-centralized connection admission control in the first radio network controller 201 RNC1 regarding said lub interface.
  • FIG. 6 is a flow chart illustrating an exemplary embodiment.
  • the apparatus 202 which may comprise e.g. a network element (network node, e.g. a second radio network controller, RNC2), may perform, in item 601 , non- centralized connection admission control for at least one transport bearer that uses a lub interface controlled by a first radio network controller RNC1 and by at least one second radio network controller RNC2.
  • a maximum threshold value e.g. traffic load or number of calls
  • the second radio network controller RNC2 may inform the first radio network controller 201 RNC1 on the exceeding of the threshold value.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202 controlling said lub interface, on the initiation of the centralized connection admission control in the first radio network controller RNC1 , in order said other radio network controllers to inter- rupt performing non-centralized connection admission control regarding said lub interface.
  • the second radio network controller 202 RNC2 may receive the information 406, and interrupt non-centralized connection admission control in the second radio network controller 202 RNC2 regarding said lub interface.
  • the second radio network controller RNC2 may inform the first radio network controller 201 RNC1 on the traffic load/number of calls being below the minimum threshold value.
  • the first radio network controller 201 RNC1 may inform other radio network controllers RNC2 202, on the interruption of the centralized connection admission control in the first radio network controller 201 RNC1 , in order said other radio network controllers to initiate performing non-centralized connection admission control regarding said lub interface.
  • the second radio network controller 202 RNC2 may receive the information 41 1 , and initiate non-centralized connection admission control in the second radio network controller 202 RNC2 regarding said lub interface.
  • FIG. 7 is a flow chart illustrating an exemplary embodiment.
  • the apparatus 201 , 202 which may comprise e.g. a network element (network node, e.g. a second radio network controller RNC1 , RNC2), may define a maximum threshold value based on a transport capacity of an lub interface, wherein at least two radio network controllers RNC1 , RNC2 control at least one transport bearer that uses the lub interface.
  • the apparatus may divide the maximum threshold value into at least two radio-network- controller-specific parts for the at least two radio network controllers RNC1 , RNC2.
  • the apparatus may initiate connection admission control CAC regarding the lub interface.
  • the method comprises transmitting, in item 705, from the first radio network controller RNC1 to at least one second radio network controller RNC2, a share request including information on a CAC book-keeping value of the first radio network controller RNC1 , in order the first radio network controller RNC1 to request for more transport capacity of the lub interface.
  • the apparatus may receive, from at least one second radio network controller RNC2, a share response including information on a CAC book-keeping value of the at least one second radio network controller RNC2 and information on an updated first radio- network-controller-specific part of the maximum threshold value and on an up- dated second radio-network-controller-specific part of the maximum threshold value.
  • the first radio network controller may receive, from the second radio network con- trailer RNC2, a share request including information on a CAC book-keeping value of the second radio network controller RNC2, in order the second radio network controller RNC2 to request for more transport capacity of the lub interface, and transmit, to the at least one second radio network controller RNC2, a share response including information on a CAC book-keeping value of the first radio network controller RNC1 and information on an updated first radio- network-controller-specific part of the maximum threshold value and on an updated second radio-network-controller-specific part of the maximum threshold value.
  • the steps/points, signalling messages and related functions de- scribed above in Figures 1 to 7 are in no absolute chronological order, and some of the steps/points may be performed simultaneously or in an order differing from the given one. Other functions can also be executed between the steps/points or within the steps/points and other signalling messages sent between the illustrated messages. Some of the steps/points or part of the steps/points can also be left out or replaced by a corresponding step/point or part of the step/point.
  • the apparatus operations illustrate a procedure that may be implemented in one or more physical or logical entities.
  • the signalling messages are only exemplary and may even comprise several separate messages for transmitting the same information. In addition, the messages may also con- tain other information.
  • a method for performing connection admission control CAC in a communications system comprising steps of defining, in a first network apparatus, a maximum threshold value based on a transport capacity of an lub interface, wherein at least two network apparatuses control at least one transport bearer that uses the lub interface; dividing the maximum threshold value into at least two network-apparatus-specific parts for the at least two network apparatuses; initiating connection admission control CAC regarding the lub interface; wherein, if it is found out that a first network-apparatus-specific part of the maximum threshold value is exceeded in the first network apparatus, the method comprises transmitting, from the first network apparatus to at least one second network apparatus, a share request including information on a CAC bookkeeping value of the first network apparatus, in order the first network apparatus to request for more transport capacity of the lub interface; receiving, from at least one second network apparatus, a share response including information on a CAC book-keeping value of the at least one second network apparatus and information on an updated first network
  • the method comprises initiating, in the first network appara-
  • connection admission control wherein the first network apparatus performs, regarding the lub interface, the connection admission control CAC for each network apparatus controlling at least one transport bearer that uses the lub interface.
  • 25 a method for receiving, in the first network apparatus, a notification indicating that the maximum threshold value is exceeded in one or more network apparatuses controlling the lub interface.
  • a method for receiving, from other network apparatuses controlling the lub in- terface, information indicating that said other network apparatuses have interrupted performing non-centralized connection admission control regarding the lub interface is provided.
  • a method for defining a minimum threshold value based on the transport ca- pacity of the lub interface wherein, if it is found out, in the first network apparatus, that the minimum threshold value is not exceeded in at least one network apparatus controlling at least one transport bearer that uses the lub interface, the method comprises interrupting, in the first network apparatus, the centralized connection admission control, wherein the first network apparatus and the at least one radio network controller perform, regarding the lub interface, non- centralized connection admission control for respective transport bearers that use the lub interface.
  • a method for receiving, in the first network apparatus, a notification indicating that the minimum threshold value is not exceeded in one or more network apparatuses regarding the lub interface is provided.
  • a method for informing other network apparatuses regarding the lub interface that the minimum threshold value is not exceeded in said one or more network apparatuses.
  • a method for informing other network apparatuses regarding the lub interface on the interruption of centralized connection admission control in the first network apparatus, in order said other network apparatuses to initiate performing non-centralized connection admission control regarding the lub interface.
  • a method for initiating, in a first network apparatus, connection admission control CAC regarding an lub interface comprising periodically transmitting, from the first network apparatus to at least one second network apparatus, a share request including information on a CAC book-keeping value of the first network apparatus, in order the first network apparatus to request for or offer more transport capacity of the lub interface; periodically receiving, from the at least one second network apparatus, a share response including information on a CAC book-keeping value of the at least one second network apparatus.
  • the first network apparatus comprises a first radio network controller and the second network apparatus comprises a second radio network controller.
  • a first apparatus comprising at least one processor; and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first apparatus to carry out any of the method steps.
  • the first apparatus comprises a first radio network controller.
  • a second apparatus comprising at least one processor; and at least one mem- ory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to receive, from a first apparatus, information on initiation of centralized connection admission control in the first apparatus for transport bearers that use an lub interface; interrupt performing non- centralized connection admission control for the transport bearers that use the lub interface.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to transmit, to a first apparatus, a notification indicating that a maximum threshold value defined based on the transport capacity of the lub interface, is exceeded in the second apparatus controlling the lub interface, in order the first apparatus to initiate performing centralized connection admission control regarding the lub interface.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to transmit, to the first apparatus, information indicating that the first apparatus has interrupted performing non- centralized connection admission control regarding the lub interface.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to receive, from the first apparatus, information on interrupting of the centralized connection admission control in the first apparatus for transport bearers that use the lub interface; initiate performing non-centralized connection admission control regarding the lub in- terface.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to initiate performing non- centralized connection admission control regarding the lub interface if it is found out that a minimum threshold value is not exceeded in at least one network apparatus controlling at least one transport bearer that uses the lub interface.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to receive information regarding the lub interface that the minimum threshold value is not exceeded in said one or more network apparatuses.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the second apparatus to collect and maintain connection admission control CAC information regarding the lub interface when centralized connection admission control is performed in the first apparatus regarding the lub interface.
  • the second appa- ratus comprises a second radio network controller.
  • a computer program product comprising program code means configured to perform any of the method steps when the program is run on a computer.
  • a computer-readable storage medium comprising program code means configured to perform any of the method steps when executed on a computer.

Landscapes

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

Abstract

Un RNC1 (201) et un RNC2 (202) effectuent un contrôle d'admission de connexion non centralisé. Si un seuil de charge maximum est dépassé dans le RNC2, ce dernier envoie des informations (404) au RNC1 qui initie un contrôle d'admission de connexion centralisé tandis que le RNC2 interrompt le contrôle d'admission de connexion non centralisé. Si la charge redevient inférieure à un seuil minimum, le contrôle d'admission de connexion centralisé est interrompu dans le RNC1 et les deux RNC recommencent le contrôle d'admission de connexion non centralisé.
PCT/EP2013/058085 2013-04-18 2013-04-18 Contrôle d'admission de connexion dans des communications WO2014169957A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/058085 WO2014169957A1 (fr) 2013-04-18 2013-04-18 Contrôle d'admission de connexion dans des communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/058085 WO2014169957A1 (fr) 2013-04-18 2013-04-18 Contrôle d'admission de connexion dans des communications

Publications (1)

Publication Number Publication Date
WO2014169957A1 true WO2014169957A1 (fr) 2014-10-23

Family

ID=48236880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/058085 WO2014169957A1 (fr) 2013-04-18 2013-04-18 Contrôle d'admission de connexion dans des communications

Country Status (1)

Country Link
WO (1) WO2014169957A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020119784A1 (en) * 2001-02-23 2002-08-29 Evolium S.A.S. Method of managing processing resources in a mobile radio system
US20130067042A1 (en) * 2011-09-09 2013-03-14 Microsoft Corporation Dynamically allocating network resources for communication session

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020119784A1 (en) * 2001-02-23 2002-08-29 Evolium S.A.S. Method of managing processing resources in a mobile radio system
US20130067042A1 (en) * 2011-09-09 2013-03-14 Microsoft Corporation Dynamically allocating network resources for communication session

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HOSSAIN E ET AL: "Call admission control for QoS provisioning in 4G wireless networks: issues and approaches", IEEE NETWORK, IEEE SERVICE CENTER, NEW YORK, NY, US, vol. 19, no. 5, 1 September 2005 (2005-09-01), pages 5 - 11, XP011139495, ISSN: 0890-8044 *

Similar Documents

Publication Publication Date Title
JP6696580B2 (ja) データ伝送のための制御プレーンおよびユーザプレーンの選択
JP5977882B2 (ja) 高ネットワーク負荷シナリオを管理するネットワーク制御されたアダプティブ端末挙動
EP3163830B1 (fr) Noeud de commande de liaison, procédé de commande de liaison et support d'enregistrement
US10111135B2 (en) Offloading traffic of a user equipment communication session from a cellular communication network to a wireless local area network (WLAN)
US9532238B2 (en) Communication method and system, access network device, and application server
WO2018045877A1 (fr) Procédé de commande de tranchage de réseau et dispositif associé
US9060294B2 (en) System and method for throttling downlink data notifications in a network environment
RU2527728C2 (ru) Способ беспроводной связи (варианты), сетевой узел и мобильная станция
EP2645785B1 (fr) Procédé et dispositif pour l'attribution de trafic à commutation de paquets dans un réseau de communication sans fil multi-technologies
US10523589B2 (en) Traffic control method, apparatus, and system
EP2380392A1 (fr) Procédé et entité pour transmettre des unités de données
CN109819477B (zh) 一种处理请求的方法以及相应实体
KR20140024462A (ko) 코어 네트워크에서의 정체 제어를 위한 시스템 및 방법
US10149186B2 (en) Node and method for monitoring an ability of a wireless device to receive downlink data
US9510235B2 (en) Congestion control method, device, and system
CN114731568A (zh) 中继用户装备处的访问控制
EP3777461A1 (fr) Gestion de supports dédiés
EP2989822B1 (fr) Réduction d'une signalisation de mise à jour de localisation entre des n uds de réseau d'un réseau de communication mobile
WO2013120223A1 (fr) 3gdt intelligent
WO2011026525A1 (fr) Analyse d'erreurs de connexion et déclenchement de surveillance de signalisation de connexion entre un équipement utilisateur et le réseau de communication
WO2014169957A1 (fr) Contrôle d'admission de connexion dans des communications
JP2018137664A (ja) 通信システム、および、通信方法
JP6096305B2 (ja) セルラーネットワークにおけるノード、システム、および方法
WO2016176416A1 (fr) Procédé et appareil d'utilisation de contrôle d'admission d'appel pour l'équilibrage d'appels client
KR101830224B1 (ko) 패킷 트래픽 제어 방법 및 이를 위한 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13719764

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13719764

Country of ref document: EP

Kind code of ref document: A1