EP1592275B1 - Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué - Google Patents

Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué Download PDF

Info

Publication number
EP1592275B1
EP1592275B1 EP04010204A EP04010204A EP1592275B1 EP 1592275 B1 EP1592275 B1 EP 1592275B1 EP 04010204 A EP04010204 A EP 04010204A EP 04010204 A EP04010204 A EP 04010204A EP 1592275 B1 EP1592275 B1 EP 1592275B1
Authority
EP
European Patent Office
Prior art keywords
base station
resource management
management control
control functionality
controlling
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP04010204A
Other languages
German (de)
English (en)
Other versions
EP1592275A1 (fr
Inventor
Dragan Petrovic
Eiko Seidel
Joachim Löhr
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Panasonic Holdings Corp
Original Assignee
Matsushita Electric Industrial Co Ltd
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 to EP04010204A priority Critical patent/EP1592275B1/fr
Application filed by Matsushita Electric Industrial Co Ltd filed Critical Matsushita Electric Industrial Co Ltd
Priority to DE602004001335T priority patent/DE602004001335T2/de
Priority to AT04010204T priority patent/ATE331414T1/de
Priority to US11/587,496 priority patent/US20080069088A1/en
Priority to PCT/EP2005/001308 priority patent/WO2005107303A1/fr
Priority to CN2005800221709A priority patent/CN1981553B/zh
Priority to JP2007509892A priority patent/JP2007535251A/ja
Publication of EP1592275A1 publication Critical patent/EP1592275A1/fr
Application granted granted Critical
Publication of EP1592275B1 publication Critical patent/EP1592275B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to a method and base station in a mobile communication system for relocating from a controlling base station to another base station within a mobile communication network resource management control functionality of shared channels in a plurality of cells, each cell being controlled by a base station, wherein each of the shared channels is shared by a plurality of mobile terminals within a cell. Further, the present invention relates to a mobile communication system.
  • W-CDMA Wideband Code Division Multiple Access
  • IMT-2000 International Mobile Communication
  • 3GPP 3 rd Generation Partnership Project
  • the dedicated channel (DCH) for downlink and uplink and the downlink shared channel (DSCH) have been defined in Release 99 and Release 4.
  • the developers recognized that for providing multimedia services - or data services in general - high speed asymmetric access had to be implemented.
  • the high-speed downlink packet access (HSDPA) was introduced.
  • the new high-speed downlink shared channel (HS-DSCH) provides downlink high-speed access to the user from the UMTS Radio Access Network (RAN) to the communication terminals, called user equipments in the UMTS specifications.
  • RAN UMTS Radio Access Network
  • UMTS Universal Mobile Telecommunication System
  • Fig. 1 The high level R99/4/5 architecture of Universal Mobile Telecommunication System (UMTS) is shown in Fig. 1 (see 3GPP TR 25.401: "UTRAN Overall Description", available from http://www.3gpp.org).
  • the network elements are functionally grouped into the Core Network (CN) 101, the UMTS Terrestrial Radio Access Network (UTRAN) 102 and the User Equipment (UE) 103.
  • the UTRAN 102 is responsible for handling all radio-related functionality, while the CN 101 is responsible for routing calls and data connections to external networks.
  • the interconnections of these network elements are defined by open interfaces (lu, Uu). It should be noted that UMTS system is modular and it is therefore possible to have several network elements of the same type.
  • Fig. 2 illustrates the current architecture of UTRAN.
  • a number of Radio Network Controllers (RNCs) 201, 202 are connected to the CN 101.
  • Each RNC 201, 202 controls one or several base stations (Node Bs) 203, 204, 205, 206, which in turn communicate with the user equipments.
  • An RNC controlling several base stations is called Controlling RNC (C-RNC) for these base stations.
  • C-RNC Controlling RNC
  • a set of controlled base stations accompanied by their C-RNC is referred to as Radio Network Subsystem (RNS) 207, 208.
  • RNS Radio Network Subsystem
  • S-RNS Serving RNS
  • the Drift RNS 302 (D-RNS) 302 supports the Serving RNS (S-RNS) 301 by providing radio resources as shown in Fig. 3. Respective RNCs are called Serving RNC (S-RNC) and Drift RNC (D-RNC). It is also possible and often the case that C-RNC and D-RNC are identical and therefore abbreviations S-RNC or RNC are used.
  • UP User Plane
  • CP Control Plane
  • Radio Resource Control (RRC) protocol (see 3GPP TSG RAN TS 25.331 "RRC Protocol Specification", V.6.1.0, available at http://www.3gpp.org) on the network side is terminated in the RNC. It comprises following relevant functions:
  • NBAP Node B Application Part
  • RANAP Radio Network Subsystem Application Protocol
  • RANAP Radio Access Network Application Part
  • Some of the procedures of these protocols that are used to support RRC functions from above are: Radio Link Setup common NBAP procedure, Radio Link Addition/Deletion dedicated NBAP procedure, Relocation Commit RNSAP mobility procedure, Radio Link Addition /Deletion / Setup RNSAP DCH procedures and Relocation RANAP procedure.
  • RNC User plane functions
  • RNC terminates MAC and RLC protocols on the network side according to ReI99/4 protocol architecture.
  • the User Plane protocol stack architecture of relevance to Rel5 High Speed Downlink Packet Access (HSDPA) feature will also be provided in the following passages.
  • the settings of these protocols are controlled by RRC.
  • Node B User Plane / Control Plane functions
  • the physical layer is terminated on the network side in a Node B for an ReI99/4 UMTS architecture.
  • Node B may terminate MAC layer for HS-DSCH transport channel.
  • HARQ protocol and scheduling function belong to MAC-hs sublayer that is distributed across Node B and UE. It should be noted that a selective repeat (SR) Automatic Repeat Request (ARQ) protocol based on sliding window mechanisms could be also established between RNC and UE on the level of RLC sublayer in acknowledged mode.
  • SR selective repeat
  • ARQ Automatic Repeat Request
  • RAB Radio Access Bearer
  • Each RAB is subsequently mapped to a service offered from MAC layer. This service is referred to as Logical Channel (LC).
  • LC Logical Channel
  • HS-DSCH FP High Speed Downlink Shared Channel Frame Protocol
  • RNC Radio Network Controller
  • Parameters of the protocols are configured by signaling in the Control Plane. This signaling is governed by radio Resource Control (RRC) protocol for the signaling between radio network (S-RNC and UE) and by application protocols, NBAP on the lub interface and RNSAP on the lur interface.
  • RRC radio Resource Control
  • dedicated transport channel In the Cell_DCH state of the RRC connected mode, dedicated transport channel (DCH) is located to a UE and the UE is known by its serving RNC on a cell level.
  • RRC connection mobility is managed by Active Set Update function.
  • FACH and RACH transport channels can be used for downlink and uplink transmission and cell reselection is used for managing RRC connection mobility.
  • Location of the UE on cell level is reported to the network by Cell Update function.
  • the UE may be reached only via the paging channel (PCH).
  • PCH paging channel
  • the UE may autonomously transit to Cell_FACH state and return to Cell_PCH state after completing the procedure if no other activity has been detected.
  • Radio mobility comprises RRC connection mobility functions as defined in the previous paragraphs.
  • radio mobility comprises a set of mobility management methods, based on knowledge of the UE location on the cell level, that are aimed at achieving nearly optimal utilization of available radio resources and Quality of Service (QoS) as seen by an end user.
  • QoS Quality of Service
  • An Active Set Update function modifies the active set of the communication between a UE in Cell_DCH state of the RRC connected mode and UTRAN.
  • the procedure comprises three functions: radio link addition, radio link deletion and combined radio link addition and deletion.
  • the maximum number of simultaneous radio links may be for example set to eight.
  • New radio links may be added to the Active Set once the pilot signal strengths of respective base stations (Node Bs) exceed a certain threshold relative to the pilot signal of the strongest member within Active Set.
  • a radio link may be removed from the active set once the pilot signal strength of the respective base station exceeds certain threshold relative to the strongest member of the Active Set.
  • the threshold for radio link addition may be chosen to be higher than that for the radio link deletion. Hence, addition and removal events form a hysteresis with respect to pilot signal strengths.
  • Pilot signal measurements may be reported to the network (S-RNC) from UE by means of RRC signaling.
  • S-RNC network
  • CPICH measurements in terms of RSCP or E c /N o may be used (see 3GPP TSG RAN TS 25.215 "Physical Layer Measurements - (FDD)", V.6.0.0, available from http://www.3gpp.org).
  • the S-RNC may decide to trigger the execution of one of the procedures of Active Set Update function.
  • Corresponding signaling across lub/lur interfaces is performed by NBAP/RNSAP procedures mentioned in the previous paragraphs. While executing this function, ACTIVE SET UPDATE and ACTIVE SET UPDATE COMPLETE messages of the RRC protocol may be exchanged between S-RNC and UE. Corresponding NBAP/RNSAP messages may be also exchanged across lub/lur interfaces.
  • An Active Set Update may be applicable for DCH transport channels.
  • a Hard Handover function changes the serving cell of a UE in Cell_DCH state of the RRC connected mode by first deleting the old radio link and then adding a new radio link. Decision on triggering hard handover function is made by RRC in S-RNC based on certain measurements similar as in the previous case. There are several ways to implement this function by Uu interface signaling. For example, RADIO BEARER RELEASE and RADIO BEARER SETUP procedures of the RRC protocol can be exchanged between S-RNC and Node B. Corresponding NBAP/RNSAP messages may be also exchanged across lub/lur interfaces.
  • a typical example of intra-frequency hard handover is Inter Node B serving cell change for HS-DSCH transport channel (see 3GPP TSG RAN TR 25.308 "High Speed Downlink Packet Access (HSDPA): Overall Description Stage 2", V.6.0.0, available at http://www.3gpp.org).
  • HSDPA High Speed Downlink Packet Access
  • FIG. 6 An exemplary signaling diagram for a typical Hard Handover procedure is shown in the Fig. 6.
  • the connection to the old Node B is firstly broken and then a connection to the new Node B is established. It is assumed that both old and new Node B are located in a same RNS controlled by the S-RNC.
  • the signaling will be again divided into three temporal phases: (1) measurement control, (2) Radio Bearer / Radio Link deletion and Radio Link addition and (3) Radio Bearer Setup.
  • the measurement control phase is analogous to the phase (1) from Fig. 6.
  • Radio Bearer / Radio Link deletion and Radio Link addition the Radio Bearer between the S-RNC and the UE corresponding to the connection via the old Node B is deleted first. This may be accomplished by exchanging [RRC] RADIO BEARER RELEASE and [RRC] RADIO BEARER RELEASE COMPLETE messages between the S-RNC and the UE. The corresponding Radio Link is removed by invoking [NBAP] ⁇ RL Deletion procedure> between the S-RNC and the old Node B. Finally, a new Radio Link is added between the S-RNC and the new Node B by invoking [NBAP] ⁇ RL Setup procedure>. The establishment of the user plane on the lub interface is followed by user plane synchronization during lub [DCH FP] DL/UL Synchronization procedure.
  • a new Radio Bearer is Setup between the S-RNC and the UE by exchanging [RRC] RADIO BEARER SETUP and [RRC] RADIO BEARER SETUP COMPLETE messages.
  • FIG. 10 A simplified example of a synchronized inter-Node B serving HS-DSCH cell change procedure according to current UMTS standard 3GPP TR 25.877: High Speed Downlink Packet Access: lub/lur Protocol Aspects", V.5.1.0, available at http://www.3gpp.org, is shown in Fig. 10. In this example it is assumed that the decision on triggering an active set update and cell change procedures is performed simultaneously by the S-RNC.
  • the UE transmits a MEASUREMENT REPORT message to the S-RNC via RRC signaling.
  • the S-RNC determines the need for the combined radio link addition and serving HS-DSCH cell change based on received measurement reports.
  • the SRNC initiates establishment of a new radio link for the dedicated channels to the target Node B by transmitting RADIO LINK SETUP REQUEST message via RNSAP / NBAP protocol.
  • Target Node B confirms the establishment of a radio link by transmitting RADIO LINK SETUP RESPONSE message via RNSAP/NBAP protocol.
  • RRC further transmits an ACTIVE SET UPDATE message to the UE via RRC protocol.
  • the ACTIVE SET UPDATE message comprises the necessary information for establishing dedicated physical channels for the added radio link (but not the HS-PDSCH).
  • the UE has added the new radio link it returns an ACTIVE SET UPDATE COMPLETE message via RRC protocol. This completes the addition of the new radio link for dedicated channels.
  • the S-RNC may now carry on with the next step of the procedure, which is the serving HS-DSCH cell change.
  • the serving HS-DSCH cell change both the source and target Node Bs are first prepared for execution of the handover and the cell change at the activation time.
  • the S-RNC first exchanges signaling messages with source Node B (RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION READY and RADIO LINK RECONFIGURATION COMIT via NBAP / RNSAP protocols).
  • source Node B RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION READY and RADIO LINK RECONFIGURATION COMIT via NBAP / RNSAP protocols.
  • RADIO LINK RECONFIGURATION COMMIT message comprises activation time information for source Node B.
  • the same sets of messages are subsequently exchanged with target Node B.
  • S-RNC informs source Node B to carry out the reset of MAC-hs entity by MAC-hs RELEASE REQUEST message of the NBAP / RNSAP protocol.
  • a PHYSICAL CHANNEL RECONFIGURATION message is transmitted to the UE via RRC signaling.
  • This message may comprise activation time information and request a MAC-hs reset at the UE.
  • the UE responds with PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
  • the serving Node B function is relocated for a single UE from a Source Node B to a Target Node B.
  • a serving radio resource control entity relocation method is disclosed in WO 03/017686 A. Therein a relocation specific information is transmitted from the serving network element to a desired target network element to establish an operation state between the user equipment and drift network element supporting the desired target network element such that radio resource control is relocated.
  • Micro mobility comprises SRNS relocation procedure as will be described in the following paragraphs.
  • micro mobility comprises a set of mobility management methods, based on knowledge of UE location on the RNS level, that are aimed at nearly optimal utilization of installed network infrastructure and available radio resources.
  • SRNS relocation may be defined as a method of moving the S-RNC functionality from one RNC to another RNC in the network.
  • the UE maintains a connection over a single Node B within the S-RNS in stage (i). After Active
  • the S-RNC is the 'anchor point' of the lu connection on the UTRAN side lu interface is terminated in the SGSN (Serving GPRS Supporting Node) on the CN side. Therefore, SRNS relocation always involves at least one CN node and can be classified into intra-SGSN and inter-SGSN SRNS relocation.
  • FIG. 8 An exemplary signaling diagram of a inter SGSN SRNS relocation procedure (for a ReI99/4 UMTS architecture) is shown in the Fig. 8.
  • the signaling can be divided into five phases: (1) Relocation preparation and resource allocation, (2) Relocation Commit and Relocation Detect, (3) UTRAN Mobility Information, (4) Relocation Complete and (5) lu Release.
  • the old S-RNC is referred to as the Source RNC while the new S-RNC is referred to as the Target S-RNC.
  • Each phase comprises a number of messages that, in turn, encompass several Information Elements (IEs). Relevant IEs are detailed in the explanation.
  • IEs Information Elements
  • the Source RNC decides to trigger the relocation procedure. Please note that even though the [RRC] MEASUREMENT REPORT message is shown on the figure, the Source RNC decides on relocation based primarily on other criteria, as, for example, the state of the Active Set after previously completed Active Set Update.
  • the Source RNC sends the [RANAP] RELOCATION REQUIRED message to the SGSN.
  • the message typically contains the Target RNC ID and Relocation Cause ('Resource optimization') IEs, and a set of IEs referred to as Source-to-Target RNC Container.
  • the container contains the set of data being transparent to the CN that are important for operation of the RRC protocol in the Target RNC like UE capabilities, DRNTI (Drift Radio Network Temporal Identity) RAB info and RRC info.
  • the SGSN then establishes a RAB towards the Target RNC based on already existing PDP Context / QoS attributes, by sending [RANAP] RELOCATION REQUEST message.
  • the message contains Relocation Cause IE, RAB parameters IE and already mentioned Source-to-Target RNC Container.
  • the Target RNC responds by the [RANAP] RELOCATION REQUEST ACK message containing IEs with assigned RAB parameters and a Target-to-Source RNC Container with DRNTI. A new RAB is now successfully established towards the Target RNC.
  • the SGSN then sends the [RANAP] RELOCATION COMMAND message to the Source RNC.
  • the message contains the list of assigned RAB parameters and the Target-to-Source RNC Container carrying DRNTI.
  • the Source RNC knows the Target RNC is ready to start receiving data. This means that Source RNC may start forwarding Data PDUs to the Target RNC ([DCH-FP] Data PDUs message).
  • this action of the Source-RNC is optional and standardized as an improvement of SRNS relocation for real-time services from PS domain for the ReI4 of 3GPP standardization ("seamless" relocation) - see 3GPP TSG RAN TS 25.936 "Handovers for real-time services for PS domain", V. 4.0.1, available at http://www.3gpp.org.
  • the forwarding may be applied if it is indicated in the [RANAP] RELOCATION REQUIRED that the seamless relocation is required (e.g. in the IE standing for Relocation Cause)
  • the [RNSAP] RELOCATION COMMIT message is firstly sent from the Source RNC to the Target RNC containing DRNTI, RAB ID and PDCP sequence numbers (sequence numbers are contained only if lossless relocation is required).
  • the Target RNC sends the [RANAP] RELOCATION DETECT message to the SGSN in order to report that the contact with the Source RNC has now been established over the lur interface.
  • the UE is firstly updated about the change of the SRNC by the [RRC] UTRAN MOBILITY INFO message that is sent from the SRNC.
  • the message contains IEs with RAB ID, new U-RNTI and, optionally, PDCP sequence numbers on UL (if lossless relocation is required).
  • the UE responds to the SRNC by the [RRC] UTRAN MOBILITY INFO CONFIRM message containing IEs with RAB ID and, optionally, DL PDCP sequence number if lossless relocation is required.
  • Relocation Complete only the [RANAP] Relocation Complete message is sent from the SRNC (previously Target SRNC) to the SGSN.
  • the fifth phase is aimed at releasing the old lu connection established between the SGSN and the old SRNC.
  • the connection is released by exchanging [RANAP] lu RELEASE COMMAND and [RANAP] lu RELEASE COMPLETE messages between the SGSN and the Source RNC.
  • the former message contains the IE Release Cause set to 'Successful Relocation'.
  • the SRNS relocation in the legacy architecture may be triggered rather based on knowledge of a set of radio links being configured for a particular UE than based on the measurement reporting.
  • SRNS relocation may be referred to as a network-evaluated procedure.
  • relocation procedure is performed based on a precise knowledge of UE location on the RNS level.
  • relocation procedure definitely has an immediate impact on the Core Network (CN) meaning that it directly influences lu connection between S-RNC and CN.
  • CN Core Network
  • Radio mobility Mobile- evaluated Cell level No Medium Micro mobility Network- evaluated RNS level Yes Large Serving Node B relocation comprises moving functionality of radio interface User Plane protocol stack entities from Serving to target Node B, while SRNS relocation is mainly concerned about moving RRC control plane entity (and corresponding lu connection) from Source to Target RNC. These types of relocation may be therefore referred to as User and Control Plane relocation, respectively.
  • HS-DSCH transport channel For the configuration of the HS-DSCH transport channel, basic resource parameters, total power for HS-DSCH and HS-SCCH (High Speed Shared Control Channel for signaling for HSDPA) and number of orthogonal codes for HS-PDSCH (High Speed Physical Downlink Shared Channel) may be set during cell level configuration (NBAP Cell Setup procedure). These pieces of information are signaled as information elements (IEs) of the Cell Setup message (see 3GPP TS 25.922: "Radio Resource Management Strategies", V.6.0.0, available at http://www.3gpp.org).
  • IEs information elements
  • streaming type of services guaranteed bit rate per MAC-d flow may also be signaled as an IE during NBAP Radio Link Setup procedure over lub.
  • Streaming type traffic is usually transmitted over DCH transport channels, however a HS-DSCH transport channel may be used to provide better radio resource utilization.
  • Call Admission control (CAC) for HS-DSCH is carried out in the C-RNC (Controlling RNC).
  • Scheduling functionality located in the MAC-hs, allocates transmission opportunities to the admitted users.
  • the constraint for scheduling is imposed by an amount of resources (total transmission power of HS-DSCH and HS-SCCH and number of codes for HS-PDSCH) allocated for the HSDPA .
  • CRNC may undertake certain actions to enable proper handling of users demanding fulfillment of certain guaranteed bit rate.
  • reporting mode can be immediate, common and periodic or event-triggered. It can be concluded that signaling load due to reporting messages is network implementation-specific and that it is the highest in case of periodic reporting.
  • CRNC may perform different actions. For example, it can decide to pre-empt a specific MAC-d flow and signal this to the SRNC by means of the [RNSAP] RADIO LINK PREEMPTION REQUIRED INDICATION message (see 3GPP TS 25.423: "UTRAN lur Interface RNSAP Signalling", V.6.0.0, available at http://www.3gpp.org). After the Radio Link or MAC-d flow pre-emption, SRNC may switch affected user to DCH transport channel.
  • the CRNC may use common measurement information to allocate more power or codes to the HSDPA users by means of the [NBAP] Cell Reconfiguration procedure. Therefore, it can be noticed that the signaling load in the network in this case is generated also by some actions of the controlling network element that are triggered after receiving measurement reports. Apart from signaling load, certain delay is incurred to reconfigure respective cell, in addition to CRNC processing delay that is implementation specific.
  • the RNG Radio Network Gateway
  • the RNG is used for interworking with the conventional RAN, and to act as a mobility anchor point meaning that once an RNG has been selected for the connection, it is retained for the duration of the call. This includes functions both in control plane and user plane. Further, the RNG provides connectivity to the core network of the mobile communication system.
  • Part of RNG functions is to act as a signaling gateway between the evolved RAN and the CN, and the evolved RAN and Re199/4/5 UTRAN. It has the following main functions:
  • the RNG is the user plane access point from the CN or conventional RAN to the evolved RAN. It has the following user plane functions:
  • the NodeB+ element terminates all the RAN radio protocols (L1, L2 and L3). NodeB+ functions are studied separately for control plane and user plane.
  • This category includes all the functions related to the control of the connected mode terminals within the evolved RAN.
  • Main functions are:
  • Control plane functions include also all the functions for the control and configuration of the resources of the cells of the NodeB+, and the allocation of the dedicated resources upon request from the control plane part of the serving NodeB+.
  • User plane functions include the following:
  • Radio mobility procedures are largely unchanged because they are governed by RRC protocol. Functionality of this protocol in the evolved architecture would remain the same. The only difference is that its termination on the network side would be Serving Node B+.
  • Relocation in legacy radio access network was defined as a procedure by means of which the SRNC functionality is moved from one RNC to another.
  • Serving Node B+ may be defined as the Node B+ currently performing all RRC functions for the observed UE.
  • SRNC relocation in the legacy architecture would correspond to the Serving Node B+ relocation in the radio access network with distributed architecture.
  • serving network element relocation procedure it will be referred to as serving network element relocation procedure as well. It should be noted that the latter could be used as a more generic term for the legacy SRNS relocation. Therefore, micro mobility in a radio access network with distributed architecture can be defined as serving network element (serving Node B+) relocation.
  • the controlling network element is defined as the Node B+ performing radio resource management functions as explained in the "Radio Resource Management for HSDPA" section above. These functions may affect a number of other Node B+s.
  • the set comprised of the CNode B+ and controlled Node B+s will be referred to as radio network subsystem for the evolved architecture.
  • controlling RNC functionality for HSDPA is fundamentally different from the serving RNC functionality.
  • different network elements may be allocated serving and controlling function, respectively.
  • controlling network element function for networks employing shared channel access and common measurements may be moved from one network element to another. This procedure will be referred to as controlling network element relocation. The procedure falls rather under radio resource management than under mobility management.
  • frequency of serving network element relocation dominantly depends on two factors: (1) the number of interfaces of the observed element and traffic load on observed interfaces, air interface excluding and (2) the size of coverage area controlled by observed network element.
  • the frequency of serving network element relocations increases relative to the frequency of relocations in legacy architecture.
  • the number of wired interfaces of Node B+ is tripled (2 lur interfaces and one lu/lur interface) compared to the number of wired interfaces of Node B in the legacy architecture (one lub interface).
  • the number of interfaces compared to RNC in the legacy architecture is approximately equal.
  • the traffic load on lur interfaces is expected to be substantially higher.
  • the coverage area controlled by Node B+ is much smaller than the one controlled by legacy RNC.
  • Radio Resource Management for HSDPA requires the interaction of Radio Link and Cell (Re)Configuration, Radio Link Preemption and Common Measurement reporting procedures in legacy network.
  • the architecture of the legacy network is not distributed since one controlling RNC has the responsibility for several Node Bs.
  • the object of the present invention is to enable controlling network element relocation for distributed radio access network.
  • a method for relocating from a controlling base station to another base station within a mobile communication network resource management control functionality of shared channels in a plurality of cells, each cell being controlled by a base station, wherein each of the shared channels is shared by a plurality of mobile terminals within a cell is provided.
  • the method may comprise the steps of receiving information from each reporting base station at the controlling base station, estimating at the controlling base station the signaling load between the controlling base station and each reporting base station or the processing load at each reporting base station and the controlling base station, wherein the estimation is based on said received information, and determining whether to relocate said resource management control functionality for at least a part of said plurality of cells from the controlling base station to a reporting base station, by evaluating the estimated load at the controlling base station.
  • the controlling base station may select a reporting base station to which resource management control functionality is to be relocated based on the estimated load and may relocate resource management control functionality for at least said part of said plurality of cells from the controlling base station to the selected reporting base station.
  • the resource management control functionality may comprise at least one of the following functions: initial cell and radio link configuration, call admission control and load control.
  • the resource management control functionality for the remaining cells may be maintained at the controlling base station or is relocated to another reporting base station selected by the controlling base station.
  • Another embodiment of the present invention encompasses different possibilities to provide the controlling network element with information on which its relocation decision may be based on.
  • the information received from each reporting base station may indicate the quality of service provided to each mobile terminal using a shared channel by the reporting base station.
  • the controlling base station may estimate same based on the number of mobile terminals for which measurement reports are received from a respective reporting base station.
  • the reported quality of service may indicate either one of or a combination of a provided net bit rate achieved by each mobile terminal using a shared channel within a cell, or a block error rate of data transmitted to the mobile terminals using a shared channel.
  • the information received by the controlling base station may indicate the number of mobile terminals using a shared channel under a respective reporting base station.
  • the controlling base station may estimate the signaling load based on the number of mobile terminals indicated in the received information.
  • the controlling base station may not need to extract the relevant information from the measurement reports but may extract them directly from the provided information.
  • Another embodiment encompasses an efficient reduction of the signaling load in the access network.
  • the first base station may select the reporting base station as the next controlling base station that reports the largest number of mobile terminals.
  • the method may also balance the processing and/or signaling load within a cell cluster controlled by the controlling base station.
  • the information received at the controlling base station may thus indicate the processing and/or signaling load at the respective reporting base station in order to facilitate load balancing. For example, in case the processing load at the controlling base station is above a predetermined upper processing load threshold and at least one reported processing load value is below a predetermined lower processing load threshold the controlling base station may decide to relocate resource management control functionality. This may have the advantage that frequent relocations may be prevented.
  • the relocation may be triggered only if the relation between the upper and lower threshold is maintained for a predetermined time period.
  • a reporting base station to which resource management control functionality for at least a part of said cells is to be relocated is selected to be the station having reported a processing load smaller than the predetermined lower processing load threshold is selected.
  • the method may further comprise the step of transmitting from the controlling base station to the selected reporting base station a relocation command indicating the relocation of the resource management control functionality for said shared channels of at least a part of said cells.
  • the relocation request message may further comprise cell identifiers of the cells for which resource management control functionality is relocated to the selected reporting base station and an indication whether the selected reporting base station is allowed to perform a subsequent relocation of resource management control functionality.
  • the relocation request message may further comprise cell identifiers of the cells to be controlled by other base stations than said selected reporting base stations.
  • This embodiment may facilitate splitting resource management control functionality to several designated controlling base stations (currently reporting base stations) as well as a subsequent concentration of resource management control functionality in one controlling base station again.
  • controlling base station may transmit to said selected reporting base station a container comprising information to be used in said estimation step or for load control upon transmitting the relocation request message to said selected base station in case of a lossless relocation of resource management control functionality.
  • a further embodiment allows informing the base stations not selected to become the controlling base station on the relocation in an advantageous manner. Therefore, the method may further comprise the step of transmitting from the controlling base station a setup request to base stations to which no resource management control functionality for shared channels is relocated, wherein the setup message comprises the cell identifier of the new controlling base station.
  • At least one cell identifier of other base stations to which resource management control functionality of another part of the cells is relocated may be indicated to a reporting base station to which resource management control functionality of a part of the cells is relocated in the relocation request message.
  • the reporting base station to which resource management control functionality of a part of cells is relocated may receive information used to estimate the signaling load or processing load from base stations controlling a cell for which said reporting base station has been assigned resource management control functionality from the controlling base station.
  • the reporting base station may forward said information to the base station for which the indication to perform the subsequent relocation of resource management control functionality has been received, in case said reporting base station is not allowed to perform a subsequent relocation of access control.
  • controlling base station which has been designated by the previous controlling base station to perform the next relocation procedure may be advantageously provided with information relevant for deciding upon the relocation from cells which are not controlled this controlling base station.
  • a relocation request message indicating a reporting base station to which resource management control functionality of at least a part of the cells is to be relocated from the controlling base station is signaled to another controlling base station, in case the controlling base station signaling the relocation request message does not have resource management control functionality for each of said cells.
  • the present invention provides a base station for relocating to another base station within a mobile communication network resource management control functionality to shared channels in a plurality of cells, each cell being controlled by a base station, wherein each of the shared channels is shared by a plurality of mobile terminals within a cell.
  • the base station may comprise receiving means for receiving information from each reporting base station, and processing means for estimating the signaling load between the base station and each reporting base station or the processing load at each reporting base station and the base station, wherein the estimation is based on said received information.
  • the processing means may be adapted to determine whether to relocate the resource management control functionality for at least a part of said plurality of cells from the base station to a reporting base station, by evaluating the estimated load at the base station, and to select a reporting base station to which resource management control functionality is to be relocated based on the estimated load in case it has determined to relocate resource management control functionality.
  • the base station may further comprise relocation means for relocating resource management control functionality for at least said part of said plurality of cells from the base station to the selected reporting base station in case the processing means has determined to relocate resource management control functionality.
  • the base station may further comprise means adapted to perform the relocation method according to one of the various embodiments outlined above.
  • Another embodiment of the present invention is related to a mobile communication system in which resource management control functionality to shared channels in a plurality of cells is relocated from a controlling base station to another base station, each cell being controlled by a base station, wherein each of the shared channels is shared by a plurality of mobile terminals within a cell.
  • the mobile communication system may comprise a plurality of base stations according to the present invention and a plurality of mobile terminals.
  • the present invention provides a computer-readable medium for storing instructions that, when executed on a processor, cause the processor to relocate from a controlling base station to another base station within a mobile communication network resource management control functionality to shared channels in a plurality of cells, each cell being controlled by a base station, wherein each of the shared channels is shared by a plurality of mobile terminals within a cell by receiving information from each reporting base station at the controlling base station, estimating at the controlling base station the signaling load between the controlling base station and each reporting base station or the processing load at each reporting base station, wherein the estimation is based on said received information, and determining whether to relocate the resource management control functionality for at least a part of said plurality of cells from the controlling base station to a reporting base station, by evaluating the estimated load at the controlling base station.
  • the medium may further store instructions that, when executed on a processor, cause the processor to perform the relocation by selecting at the controlling base station a reporting base station to which resource management control functionality is to be relocated based on the estimated load and relocating resource management control functionality for at least said part of said plurality of cells from the controlling base station to the selected reporting base station, in case it is determined to relocate resource management control functionality,.
  • the computer-readable medium may further store instructions that, when executed on a processor, cause the processor to perform the relocation procedure according to one of the various embodiments above.
  • the additional "+” sign appended to the protocols or network elements are intended to denote that these protocols and network elements may have an enhanced functionality compared to the corresponding legacy UMTS architecture, i.e. denote protocols that may be adapted to the Evolved UTRAN architecture.
  • the additional "+” sign should however not be understood as a limitation of the principles and ideas of this invention.
  • the principles of the present invention may be applicable to any kind of mobile communication systems employing a distributed architecture, for example to communication systems based on the beyond-IMT-2000 framework.
  • One aspect of the present invention is to enable controlling network element relocation for distributed radio access network and design corresponding procedure.
  • controlling network element relocation may be performed for several users simultaneously, which is a difference with respect to normal SRNS relocation, which is performed per single user. Hence, increase in signaling load due to controlling network element relocation will not be unacceptably high.
  • radio resource management procedures for HSDPA as described in above or another radio access technology with similar features, may be carried out for a number of users in a single network element. This may contribute to decreasing the delay of the procedures and to decreasing overall signaling load in the network.
  • Fig. 11 shows a signaling diagram for an exemplary controlling Node B+ relocation scenario.
  • CNode B+ Controlling Node B+
  • two neighboring Node B+s Serving Node B+ #2
  • These two serving Node B+s may perform serving network element functionality for users that are allocated to respective cells. They may transmit measurement reports to the CNode B+.
  • [RNSAP+] COMMON MEASUREMENT REPORT messages may be used.
  • CNode B+ may decide to trigger controlling network element relocation to the SNode B+ #1.
  • the SNode B+ #1 may be informed on this decision, for example using a [RNSAP+] C-RELOCATION REQUEST message.
  • This message may comprise a Relocation Cause IE, which may for example be set to 'controlling network element relocation', and Source-to-Target Node B+ container.
  • SNode B+ #1 may evaluate the request and may decide whether to accept relocation or not. If the decision is positive, SNode B+ #1 may inform CNode B+ its decision, for example by using a [RNSAP+] C-RELOCATION REQUEST ACK message. As a next step, the CNode B+ may send a message comprising information on the cells to be controlled by the SNode B+ #1 to same. This may for example be accomplished by sending a [RNSAP+] C-RELOCATION COMMAND message which may comprise for example cell identifiers (cell IDs) of Node B+s to be controlled by the newly selected controlling element. In addition, a container with measurement results may be transferred from the CNode B+ to the SNode B+ #1.
  • SNode B+ #2 may be informed by CNode B+ on the new controlling network element (SNode B+ #1) in order to redirect e.g. measurement reporting to that element.
  • a [RNSAP+] CNode B+ SETUP REQUEST message may for example comprise an IE with the cell ID of SNode B+ #1.
  • a confirmation from the SNode B+ #2 may be transmitted to the CNode B+, for example in a [RNSAP+] CNode B+ SETUP RESPONSE message.
  • the completion of the relocation is confirmed by using for example a [RNSAP+] C-RELOCATION COMPLETE message.
  • the Node B+ controlling cell 1405 performs resource management control functionality for all cells 1401 to 1409 (indicated by the filled cone) in Fig. 14a i.e. is the CNode B+. Further, the connection from the SNode B+s (cones) of cells 1401-1404,1406-1409 to the CNode B+ in cell 1405 are intended to indicate the measurement reports transmitted to the CNode B+ and the signaling of other information related to resource management control functionality.
  • the density of stylized mobile terminals within a cell indicates a number of terminals using a shared channel within each of the cells.
  • each stylized terminal may indicate 10 HSDPA users in the cell.
  • a scenario as shown in Fig. 14b may be the result.
  • the Node B+ in cell 1407 performs CNode B+ functions, i.e. controls resource management, while the SNode B+s of cells 1401-1407 and 1409 now provide the new CNode B+ in cell 1405 with measurement reports.
  • Fig. 15a a similar initial situation as in Fig 14a is illustrated. Again the signaling load between the CNode B+ in cell 1405 and the SNode B+ in cell 1407 is high due to a high number of users of shared channels controlled by CNode B+ in cell 1405. In this exemplary embodiment, also the SNode B+ of cell 1404 causes a fairly high signaling load. Possibly, in addition SNode B+ of cell 1407 also reported a relatively high processing load. In this exemplary scenario, the CNode B+ in cell 1405 may thus decide to split resource management control functionality for cells 1401 to 1409 to the SNode B+s of cells 1404 and 1408.
  • Fig. 12 shows a signaling diagram of a relocation procedure in which resource management control functionality is split between two SNode B+s.
  • the Controlling Node B+ may decide to split the resource management control functionality for example in a scenario outline with reference to Fig. 15a above.
  • the CNode B+ may send a request for relocation to both, Serving Node B+ #1 and Serving Node B+ #2.
  • two [RNSAP+] C-RELOCATION REQUEST messages may be transmitted by CNode B+.
  • SNode B+ #1 and SNode B+ #2 may evaluate the request and may decide whether to accept relocation or not. If the decision is positive, and may inform CNode B+ on their decision, for example by using a [RNSAP+] C-RELOCATION REQUEST ACK message.
  • the CNode B+ may send a message comprising information on the cells to be controlled by the SNode B+ #1 and SNode B+ #2 to same. This may for example be accomplished by sending a [RNSAP+] C-RELOCATION COMMAND message which may comprise for example identifiers (IDs) of Node B+s to be controlled by the newly selected controlling element.
  • a container with measurement results may be transferred from the CNode B+ to the SNode B+ #1.
  • the message transmitted by the CNode B+ may further comprise an indication which of the two SNode B+s is allowed to perform the next subsequent relocation procedure. This may be feasible in case a further split of resource management control functionality is not desired.
  • the SNode B+ designated to perform the next relocation procedure (e.g. SNode B+ #1) is also provided with all cell IDs for which control has been split, in order to have information on the "cell cluster" in which resource management control functionality is relocated amongst the Node B+s.
  • the designated new CNode B+ (e.g. SNode B+ #2) not allowed to perform a relocation of resource management control functionality may provided with information identifying the other designated CNode B+ (e.g. SNode B+ #1), for example by including the cell ID of SNode B+ #1 in the [RNSAP+] C-RELOCATION COMMAND message.
  • SNode B+ #2 may forward the measurement results or resource management control functionality related signaling received after relocation to SNode B+ #1 in order to support its decision on relocating resource management control functionality.
  • SNode B+ #3 may be informed by CNode B+ on the new controlling network element (e.g SNode B+ #1) in order to redirect e.g. measurement reporting to that element.
  • the new controlling network element e.g SNode B+ #1
  • a [RNSAP+] CNode B+ SETUP REQUEST message may for example comprises an IE with the cell ID of SNode B+ #1.
  • a confirmation from the SNode B+ #3 may be transmitted to the CNode B+, for example in a [RNSAP+] CNode B+ SETUP RESPONSE message.
  • the completion of the relocation is confirmed by using for example a [RNSAP+] C-RELOCATION COMPLETE message.
  • Controlling Node B+ may correspond to the CNode B+ in cell 1405 of Fig. 15a
  • Serving Node B+ #1 may correspond to SNode B+ in cell 1408
  • Serving Node B+ #2 may correspond to SNode B+ in cell 1404.
  • Serving Node B+ #3 in Fig. 12 may be understood as an example of any of the SNode B+s in the remaining cells.
  • Fig. 15b shows two new CNode B+s in cells 1404 and 1408 now performing resource management control functionality for their "cell cluster" comprising cells 1401, 1402, 1404, 1405 and 1407 and 1403, 1406, 1408 and 1409 respectively.
  • the new "cell clusters" are also indicated by the stylized interconnections between the new CNode B+s and their associated SNode B+.
  • the link between the CNode B+ in cell 1404 and the CNode B+ in cell 1408 may be used to forward the resource management control functionality related signaling, as for example measurement reports, from the CNode B+ of call 1404 to CNode B+ of cell 1408, which has been designated to perform the next relocation procedure.
  • Fig. 13, Fig. 16a and Fig. 16b relate to an exemplary embodiment showing a relocation procedure in a situation in which more than one controlling network element exists, i.e. in situations in which a split of resource management control functionality has occurred before.
  • the embodiments related to a split and concentration of resource management control functionality are described with respect to a split of resource management control functionality to two new CNode B+s, it should be noted that a split and concentration of resource management control functionality is also possible to/for more than two CNode B+s in an essentially similar manner as for two CNode B+s.
  • Fig. 16a essentially the same scenario as for Fig. 15b is shown.
  • Resource management control functionality has been split to two CNode B+s, the Node B+s of cells 1404 and 1408.
  • the number of HSDPA users in cells 1404 and 1408 have been reduced significantly.
  • the initially high processing load at the CNode B+ in cell 1408 is still present.
  • this CNode B+ has been designated to perform the next relocation procedure.
  • the number of HSDPA users in cell 1405 has increased again.
  • the CNode B+ in cell 1408 is assumed to be allowed to relocate resource management control functionality to the SNode B+ of cell 1405.
  • FIG. 13 An exemplary signaling diagram for this reunion of resource management control functionality according to another embodiment of the present invention is shown in Fig. 13.
  • Controlling Node B+ #1 corresponding to the CNode B+ in cell 1408
  • Serving Node B+ #1 corresponding to the SNode B+ in cell 1405
  • essentially the same relocation request, evaluation, acknowledgement and command process as outlined with reference to Fig. 11 may be performed.
  • Controlling Node B+ #1 may inform the other Controlling Node B+ #2 about the relocation, for example by means of a [RNSAP+] C-Node B+ Setup Request.
  • Controlling Node B+ #2 may forward the request to its controlled SNode B+s (represented by Serving Node B+ #2) in order to inform same on the upcoming relocation.
  • this setup message indicates for example by means of a cell ID the new selected CNode B+ (Serving Node B+ #1).
  • Controlling Node B+ #2 may forward a container with measurement results (and/or other resource management control functionality related information) to Serving Node B+ #1. Also Controlling Node B+ #1 may do so. Finally, the Serving Node B+ #1 may complete the relocation procedure, for example by sending a [RNSAP+] C-Relocation Request Complete message to Controlling Node B+ #1.
  • FIG. 17a and 17b Another possible situation illustrated in Fig. 17a and 17b may be that after a split of resource management control functionality, the CNode B+ designated to perform the next relocation (here CNode B+ in cell 1408) acquires the part of resource management control functionality which has been designated to the CNode B+ in cell 1404.
  • CNode B+ in cell 1408 an initial situation in which the processing load at the CNode B+ in cell 1408 is low and in which the number of HSDPA users in cell 1404 has been significantly reduced may be assumed for exemplary purposes. Further, the signaling load imposed by relocation resource management control functionality to another SNode B+ than the CNode B+s may be assumed to be increased, this procedure may not be feasible.
  • the CNode B+ in cell 1408 may decide to acquire the resource management control functionality for the cells currently controlled by CNode B+ of cell 1404, for example, because it is preferred to have one controlling network element within the cell cluster 1401 to 1409.
  • Controlling Node B+ #1 and Serving Node B+ #1 may be understood to correspond to each other, such that all signaling between these two entities may be omitted. Also all signaling from the remaining entities shown in Fig. 13 directed to Controlling Node B+ #1 and Serving Node B+ #1 may be understood as to be directed to Controlling Node B+ #1 only.
  • FIG. 18a and 18b A further situation of interest that may occur is illustrated in Fig. 18a and 18b.
  • a split of resource management control functionality is shown where the original CNode B+ in cell 1405 only relocates a part of the resource management control functionality to the SNode B+ of cell 1408 while it maintains the remaining part of resource management control functionality.
  • the CNode B+ may decide to relocate parts of the resource management control functionality to the SNode B+ in cell 1408 to reduce the signaling load.
  • a signaling diagram which may illustrate the signaling required for this partial relocation of resource management control functionality according to the example of Fig. 18a and Fig. 18b may correspond to the one shown in Fig. 12, except that Serving Node B+ #1 and Controlling , Node B+ #1 would be one and the same entity. Hence, all signaling between Serving Node B+#1 and Controlling Node B+ #1 in Fig. 12 may be omitted. Also all signaling directed to Serving Node B+ #1 and Controlling Node B+ #1 from the remaining entities indicated in Fig. 12 may be understood as to be transmitted to the Controlling Node B+ #1.
  • measurement results may be sent to the SNode B1+ in a separate container, which may be especially feasible if lossless relocation is desired.
  • the value of the IE Relocation Cause may for example be set to 'lossless controlling network element relocation'. If no lossless relocation is desired, the container with measurement results illustrated in the various exemplary signaling diagrams outlined above need not to be transmitted.
  • the container - if transmitted - may comprise measurement results reported to previous controlling network element separated by UE IDs (e.g. S-RNTIs) for each user and by Node B+'s cell ID for each reporting network element.
  • UE IDs e.g. S-RNTIs
  • Node B+'s cell ID for each reporting network element.
  • the results reported by SNode B+ #1 need not to be contained in the container.
  • measurement results may be sent to the SNode B+ #1 in the separate container.
  • the container size and accuracy of the transferred results can be regulated by configurable time span for which the results are sent.
  • the CNode B+ may employ different decision criteria for triggering relocation. For example, it may decide to trigger the procedure based on number of UEs for which the measurement reporting is done by respective serving network elements. In case of immediate or event-driven type of reporting this may not be so reliable. In that case, the CNode B+ may use some information possibly signaled separately by other network elements, e.g. number of UEs accessing HS-DSCH or some load measure of respective network elements.
  • the current CNode B+ may decide to divide the RNS into two parts, with each of them being controlled by Node B+es fulfilling the criterion. In this case 'split' relocation from currently controlling Node B+ to two aforementioned Node B+es may be applied.
  • the decision to trigger a further controlling network element relocation may be left to only one of the designated new CNode B+s to avoid indefinite splitting of the cell cluster or radio network subsystem.
  • the other CNode B+s may be informed of any triggered relocations.
  • Measurement results may be forwarded from the latter to the CNode B+ designated to trigger the next relocation.
  • the [RNSAP+] C-RELOCATION COMMAND message may be transmitted to both target selected SNode B+s from current CNode B+ and the message may comprise Cell IDs of newly selected controlling base stations, cell IDs of the cells to be controlled by each of the newly selected network elements as well as indication on which one of them may decide on next relocations.
  • measurement results relevant for newly selected controlling cells may always be forwarded in the container to the newly selected CNode B+s.
  • messages like [RNSAP+] CRNC SETUP REQUEST/RESPONSE may be exchanged between previous CNode B+ and all affected Node B+s apart from newly selected new CNode B+s. These messages may comprise Cell IDs of newly selected CNode B+s.
  • a further embodiment, related to criteria for triggering relocation when the processing load of certain network elements becomes too high, may depend on user mobility that in turn may cause frequent changes in user population. Also in situations in which processing load as well as signaling load should be controlled simultaneously, problems as outlined in the following may occur.
  • the two exemplary situations mentioned above may lead to relatively frequent triggering of controlling network element relocation procedure described above.
  • a CNode B+ having a high signaling load may tend to relocate resource management control functionality to a SNode B+ having a lower processing load.
  • this SNode B+ may have a low signaling load due to only few HSDPA users in the cell, while the processing load at CNode B+ may result from many HSDPA users in the respective cell.
  • the signaling load between these may increase, which may trigger a new relocation of resource management control functionality back to the original CNode B+.
  • Frequent shifts of the controlling network element role may be overcome by introducing two different thresholds: one with respect to the processing load in currently controlling network element and another with respect to the processing loads reported by other (controlled network elements). Only if a particular threshold criterion is fulfilled, for example the processing load at a reporting SNode B+ is below a predetermined threshold, and/or the signaling load is above a predetermined tolerable threshold, relocation may be triggered.
  • processing load in the CNode B+ is above an upper processing load threshold and that processing loads and/or signalling loads reported by other network elements are below predetermined lower processing threshold during a predetermined period of time.
  • a further embodiment of the present invention proposes that the controlling network element is selected by the operator before starting network operation. Further shifting of the relocation function may then be performed according to the various embodiments as set forth in the previous paragraphs.
  • Another embodiment of the present invention relates to the implementation of the above described various embodiments using hardware and software. It is recognized that the various above mentioned methods as well as the various logical blocks, modules, circuits described above may be implemented or performed using computing devices, as for example general purpose processors. The various embodiments of the present invention may also be performed or embodied by a combination of these devices.
  • the various embodiments of the present invention may also be implemented by means of software modules which are executed by a processor or directly in hardware. Also a combination of software modules and a hardware implementation may be possible.
  • the software modules may be stored on any kind of computer readable storage media, for example RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROM, DVD, etc.

Claims (24)

  1. Procédé pour déplacer d'une station de base de commande à une autre station de base à l'intérieur d'un réseau de communication mobile la fonctionnalité de commande de gestion des ressources des canaux partagés dans une pluralité de cellules, chaque cellule étant commandée par une station de base, dans lequel chacun des canaux partagés est partagé par une pluralité de terminaux mobiles à l'intérieur d'une cellule, le procédé comprenant les étapes consistant à:
    recevoir les informations provenant de chaque station de base de service à la station de base de commande,
    estimer à la station de base de commande la charge de signalisation entre la station de base de commande et
    chaque station de base de service ou la charge de traitement à chaque station de base de service et à la station de base de commande, dans lequel l'estimation est basée sur lesdites informations reçues,
    déterminer s'il faut déplacer ladite fonctionnalité de commande de gestion des ressources pour au moins une partie de ladite pluralité de cellules de la station de base de commande à une station de base de service, en évaluant la charge estimée à la station de base de commande,
    dans le cas où il est déterminé de déplacer la fonctionnalité de commande de gestion des ressources,
    sélectionner à la station de base de commande une station de base de service à laquelle la fonctionnalité de commande de gestion des ressources doit être déplacée sur la base de la charge estimée et
    déplacer la fonctionnalité de commande de gestion des ressources pour au moins ladite partie de ladite pluralité de cellules de la station de base de commande à la station de base de service sélectionnée.
  2. Procédé selon la revendication 1, dans lequel la fonctionnalité de commande de gestion des ressources comprend au moins l'une de la configuration de la première cellule et de la liaison radio, de la commande d'acceptation d'un appel et de la commande de charge.
  3. Procédé selon la revendication 1 ou 2, dans lequel la fonctionnalité de commande de gestion des ressources pour les cellules restantes est maintenue à la station de base de commande ou est déplacée à une autre station de base de service sélectionnée par la station de base de commande.
  4. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel les informations reçues de chaque station de base de service indiquent la qualité des services fournis à chaque terminal mobile utilisant un canal partagé par la station de base de service, et dans l'étape d'estimation, la station de base de commande estime la charge de signalisation sur la base du nombre de terminaux mobiles pour lesquels des rapports de mesure sont reçus provenant d'une station de base de service respective.
  5. Procédé selon la revendication 4, dans lequel la qualité de service rapportée indique soit un ou une combinaison d'un débit binaire final prévu réalisé par chaque terminal mobile utilisant un canal partagé à l'intérieur d'une cellule, soit un taux d'erreur sur les blocs des données transmises aux terminaux mobiles utilisant un canal partagé.
  6. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel les informations reçues par la station de base de commande indiquent le nombre de terminaux mobiles utilisant un canal partagé sous une station de base de service respective, et
    dans l'étape d'estimation, la station de base de commande estime la charge de signalisation à partir du nombre de terminaux mobiles indiqué dans les informations reçues.
  7. Procédé selon l'une quelconque des revendications 4 à 6, dans lequel la première station de base sélectionne la station de base de service comme étant la station de base de commande suivante qui signale le plus grand nombre de terminaux mobiles.
  8. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel les informations reçues à la station de base de commande indiquent la charge de traitement à la station de base de service respective, et
    il est déterminé de déplacer la fonctionnalité de commande de gestion des ressources dans le cas où la charge de traitement à la station de base de commande est au-dessus d'un seuil de charge de traitement supérieur prédéterminé et au moins une valeur de charge de traitement et/ou de signalisation rapportée est en dessous d'un seuil de charge inférieur prédéterminé.
  9. Procédé selon la revendication 8, dans lequel la relocalisation est déclenchée si la relation entre le seuil supérieur et inférieur est maintenue pendant une période de temps prédéterminée.
  10. Procédé selon la revendication 8 ou 9, dans lequel, dans l'étape de sélection de la station de base de service à laquelle la fonctionnalité de commande de gestion des ressources pour au moins une partie desdites cellules doit être déplacée, la station de base de service ayant signalé une charge de traitement et/ou de signalisation plus petite que le seuil de charge inférieur prédéterminé, est sélectionnée.
  11. Procédé selon l'une quelconque des revendications 1 à 10, comprenant, en outre, l'étape consistant à transmettre de la station de base de commande à la station de base de service sélectionnée une commande de relocalisation indiquant la relocalisation de la fonctionnalité de commande de gestion des ressources pour lesdits canaux partagés d'au moins une partie desdites cellules.
  12. Procédé selon la revendication 11; dans lequel le message de commande de relocalisation comprend, en outre, des identificateurs de cellule des cellules pour lesquelles la fonctionnalité de commande de gestion des ressources est déplacée jusqu'à la station de base de service sélectionnée et une indication si la station de base de service sélectionnée est autorisée à exécuter une relocalisation ultérieure de la fonctionnalité de commande de gestion des ressources.
  13. Procédé selon la revendication 12, dans lequel, dans le cas où la station de base de commande déplace la fonctionnalité de commande de gestion des ressources seulement pour une partie desdites cellules, le message de demande de relocalisation comprend, en outre, des identificateurs de cellule des cellules qui doivent être commandées par des stations de base autres que lesdites stations de base de service sélectionnées.
  14. Procédé selon l'une quelconque des revendications 11 à 13, comprenant, en outre, l'étape consistant à transmettre de la station de base de commande à ladite station de base de service sélectionnée un conteneur de données comprenant les informations qui doivent être utilisées dans ladite étape d'estimation ou une commande de charge lors la transmission du message de demande de relocalisation à ladite station de base sélectionnée dans le cas d'une relocalisation sans perte de la fonctionnalité de commande de gestion des ressources.
  15. Procédé selon l'une quelconque des revendications 11 à 14, comprenant, en outre, l'étape consistant à transmettre de la station de base de commande une demande de réinitialisation aux stations de base auxquelles aucune fonctionnalité de commande de gestion des ressources pour les canaux partagés n'est déplacée, dans lequel le message de réinitialisation comprend l'identificateur de cellule de la nouvelle station de base de commande.
  16. Procédé selon l'une quelconque des revendications 1 à 15, comprenant, en outre, l'étape consistant à indiquer à une station de base de service à laquelle la fonctionnalité de commande de gestion des ressources d'une partie des cellules est déplacée, au moins un identificateur de cellule des autres stations de base auxquelles la fonctionnalité de commande de gestion des ressources d'une autre partie des cellules est déplacée dans le message de demande de relocalisation.
  17. Procédé selon l'une quelconque des revendications 11 à 16, comprenant, en outre, l'étape consistant à recevoir à ladite station de base de service à laquelle la fonctionnalité de commande de gestion des ressources d'une partie des cellules est déplacée, les informations utilisées pour estimer la charge de signalisation ou la charge de traitement provenant des stations de base commandant une cellule pour laquelle ladite station de base de service a été affectée de la fonctionnalité de commande de gestion des ressources provenant de la station de base de commande.
  18. Procédé selon la revendication 17, comprenant, en outre, l'étape consistant à envoyer de ladite station de base de service lesdites informations à la station de base pour laquelle l'indication d'exécuter la relocalisation ultérieure de la fonctionnalité de commande de gestion des ressources a été reçue dans le cas où ladite station de base de service n'est pas autorisée à exécuter une relocalisation ultérieure d'une commande d'accès.
  19. Procédé selon l'une quelconque des revendications 1 à 18, comprenant, en outre, l'étape consistant à signaler depuis la station de base de commande un message de demande de relocalisation indiquant une station de base de service à laquelle la fonctionnalité de commande de gestion des ressources d'au moins une partie des cellules doit être déplacée à une autre station de base de commande dans le cas où la station de base de commande signalant le message de demande de relocalisation n'a pas la fonctionnalité de commande de gestion des ressources pour chacune desdites cellules.
  20. Station de base pour déplacer à une autre station de base à l'intérieur d'un réseau de communication mobile la fonctionnalité de commande de gestion des ressources des canaux partagés dans une pluralité de cellules, chaque cellule étant commandée par une station de base, dans laquelle chacun des canaux partagés est partagé par une pluralité de terminaux mobiles à l'intérieur d'une cellule, la station de base comprenant :
    un moyen de réception pour recevoir les informations de chaque station de base de service,
    un moyen de traitement pour estimer la charge de signalisation entre la station de base et chaque station de base de service ou la charge de traitement à chaque station de base de service et à la station de base, dans laquelle l'estimation est basée sur lesdites informations reçues,
    dans laquelle le moyen de traitement est adapté pour déterminer s'il faut déplacer la fonctionnalité de commande de gestion des ressources pour au moins une partie de ladite pluralité de cellules de la station de base à une station de base de service, en évaluant la charge estimée à la station de base, et
    dans laquelle le moyen de traitement est, en outre, adapté pour sélectionner une station de base de service à laquelle la fonctionnalité de commande de gestion des ressources doit être déplacée sur la base de la charge estimée dans le cas où il a déterminé de déplacer la fonctionnalité de commande de gestion des ressources, et
    un moyen de relocalisation pour déplacer la fonctionnalité de commande de gestion des ressources pour au moins ladite partie de ladite pluralité de cellules de la station de base à la station de base de service sélectionnée dans le cas où le moyen de traitement a déterminé de déplacer la fonctionnalité de commande de gestion des ressources.
  21. Station de base selon la revendication 20, comprenant, en outre, un moyen adapté pour exécuter les étapes d'un procédé de relocalisation selon l'une quelconque des revendications 2 à 19.
  22. Système de communication mobile dans lequel la fonctionnalité de commande de gestion des ressources pour des canaux partagés dans une pluralité de cellules est déplacée d'une station de base de commande à une autre station de base, chaque cellule étant commandée par une station de base, dans lequel chacun des canaux partagés est partagé par une pluralité de terminaux mobiles à l'intérieur d'une cellule, le système de communication mobile comprenant une pluralité de stations de base selon la revendication 20 ou 21 et une pluralité de terminaux mobiles.
  23. Support lisible par un ordinateur pour stocker des instructions qui, lorsqu'elles sont exécutées par un processeur, font que le processeur déplace d'une station de base de commande à une autre station de base à l'intérieur d'un réseau de communication mobile la fonctionnalité de commande de gestion des ressources pour des canaux partagés dans une pluralité de cellules, chaque cellule étant commandée par une station de base, dans lequel chacun des canaux partagés est partagé par une pluralité de terminaux mobiles à l'intérieur d'une cellule, en :
    recevant les informations de chaque station de base de service à la station de base de commande,
    estimant à la station de base de commande la charge de signalisation entre la station de base de commande et chaque station de base de service ou la charge de traitement à chaque station de base de service, dans lequel l'estimation est basée sur lesdites informations reçues,
    déterminant s'il faut déplacer ladite fonctionnalité de commande de gestion des ressources pour au moins une partie de ladite pluralité de cellules de la station de base de commande à une station de base de service, en évaluant la charge estimée à la station de base de commande,
    dans le cas où il est déterminé de déplacer la fonctionnalité de commande de gestion des ressources,
    en sélectionnant à la station de base de commande une station de base de service à laquelle la fonctionnalité de commande de gestion des ressources doit être déplacée sur la base de la charge estimée et
    en déplaçant la fonctionnalité de commande de gestion des ressources pour au moins ladite partie de ladite pluralité de cellules de la station de base de commande à la station de base de service sélectionnée.
  24. Support lisible par un ordinateur selon la revendication 23, stockant, en outre, des instructions qui, lorsqu'elles sont exécutées par un processeur, font que le processeur exécute les étapes d'un procédé selon l'une quelconque des revendications 2 à 19.
EP04010204A 2004-04-29 2004-04-29 Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué Expired - Lifetime EP1592275B1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
DE602004001335T DE602004001335T2 (de) 2004-04-29 2004-04-29 Verlagerung, auch teilweise, einer Kontrollfunktionalität einer Resourcenverwaltung von einer Basistation in eine andere in einem verteilten Funkzugangsnetz
AT04010204T ATE331414T1 (de) 2004-04-29 2004-04-29 Verlagerung, auch teilweise, einer kontrollfunktionalität einer resourcenverwaltung von einer basistation in eine andere in einem verteilten funkzugangsnetz
EP04010204A EP1592275B1 (fr) 2004-04-29 2004-04-29 Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué
PCT/EP2005/001308 WO2005107303A1 (fr) 2004-04-29 2005-02-09 Reaffectation de parties d'une fonctionnalite de controle de gestion de ressources radio d'une bts a une seconde bts dans des reseaux d'acces radio distribues
US11/587,496 US20080069088A1 (en) 2004-04-29 2005-02-09 Hierarchy Encoding Apparatus and Hierarchy Encoding Method
CN2005800221709A CN1981553B (zh) 2004-04-29 2005-02-09 分布式无线电接入网络中从第一bts到第二bts再定位部分无线电资源管理控制功能
JP2007509892A JP2007535251A (ja) 2004-04-29 2005-02-09 分散型無線アクセスネットワークにおける第１のｂｔｓから第２のｂｔｓへの無線リソース管理制御機能の一部の再配置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP04010204A EP1592275B1 (fr) 2004-04-29 2004-04-29 Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué

Publications (2)

Publication Number Publication Date
EP1592275A1 EP1592275A1 (fr) 2005-11-02
EP1592275B1 true EP1592275B1 (fr) 2006-06-21

Family

ID=34924784

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04010204A Expired - Lifetime EP1592275B1 (fr) 2004-04-29 2004-04-29 Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué

Country Status (7)

Country Link
US (1) US20080069088A1 (fr)
EP (1) EP1592275B1 (fr)
JP (1) JP2007535251A (fr)
CN (1) CN1981553B (fr)
AT (1) ATE331414T1 (fr)
DE (1) DE602004001335T2 (fr)
WO (1) WO2005107303A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI419579B (zh) * 2005-07-29 2013-12-11 Nokia Siemens Networks Gmbh 多跳無線移動通信網路中重配置方法

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060198336A1 (en) * 2005-03-03 2006-09-07 Nokia Corporation Deployment of different physical layer protocols in a radio access network
TWI410150B (zh) * 2005-08-23 2013-09-21 Nokia Corp 在ｓｒｎｃ中，具有ｄｓｃｈ／ｅ-ｄｃｈ服務胞改變狀態下，當ｒｌ增加／ｒｌ刪除狀態同時地觸發時，ｉｕｂ／ｉｕｒ ｈｓｄｐａ／ｈｓｕｐａ行動程序之改良結構
CN1992717B (zh) * 2005-12-30 2010-09-29 华为技术有限公司 无线接入网络架构及其实时业务无损迁移的实现方法
JP4867920B2 (ja) 2006-02-07 2012-02-01 日本電気株式会社 移動体通信システム、無線基地局制御装置、およびリロケーション方法
JP4692760B2 (ja) 2006-03-16 2011-06-01 日本電気株式会社 移動体通信システムおよびその移動管理制御方法
US20070254667A1 (en) * 2006-04-28 2007-11-01 Joanna Jokinen Inter-MME handover in evolved communication systems
EP2030468B1 (fr) * 2006-06-16 2023-05-17 Nokia Technologies Oy Modification d'une ancre lte spécifique par une commutation simple de tunnel
JP5023150B2 (ja) * 2006-06-20 2012-09-12 インターデイジタル テクノロジー コーポレーション Ｌｔｅ無線通信システムにおけるハンドオーバ
JP5056758B2 (ja) * 2006-08-23 2012-10-24 日本電気株式会社 移動体通信システム、無線ネットワーク制御装置、携帯電話機及びそれらに用いるセル在圏表示方法
DE102006046977A1 (de) * 2006-10-04 2008-04-10 Siemens Ag Verfahren und Vorrichtung zum Betreiben eines mobilen Kommunikationsnetzes
TWI462507B (zh) * 2006-11-01 2014-11-21 Lg Electronics Inc 在無線通訊系統中傳送及接收下鏈資料之方法
US8923236B2 (en) 2006-11-01 2014-12-30 Lg Electronics Inc. Method of transmitting and receiving paging messages in a wireless communication system
EP2081396B1 (fr) * 2006-11-03 2012-12-12 Huawei Technologies Co., Ltd. Procédé de communication mobile et entité d'accès
CN101222419B (zh) 2007-01-10 2011-07-20 华为技术有限公司 数据通信方法及系统、数据发送/接收装置
KR20140052086A (ko) 2007-02-12 2014-05-02 인터디지탈 테크날러지 코포레이션 Ｇｐｒｓ／ｇｅｒａｎ으로부터 ｌｔｅ ｅｕｔｒａｎ으로의 핸드오프를 지원하기 위한 방법 및 장치
WO2009079832A1 (fr) * 2007-12-18 2009-07-02 Zte Corporation Procédé de détection combinée multicellule de liaison montante dans un système d'accès multiple par répartition en code synchrone et répartition dans le temps
EP2076069A1 (fr) * 2007-12-27 2009-07-01 Thomson Telecom Belgium Procédé et système pour effectuer un contrôle d'admission de service
GB2458258A (en) 2008-02-04 2009-09-16 Nec Corp Method of controlling base station loading in a mobile communication system
ES2616514T3 (es) * 2008-04-01 2017-06-13 Telefonaktiebolaget L M Ericsson (Publ) Tiempo de activación para cambio de celda de servicio de alta velocidad basado en destino
JP5069666B2 (ja) 2008-11-11 2012-11-07 株式会社エヌ・ティ・ティ・ドコモ 情報収集システム、通信端末、及び情報収集方法
CN101541041A (zh) 2009-04-23 2009-09-23 华为技术有限公司 负载分担方法、装置及系统
CN102348256B (zh) * 2010-07-26 2014-10-08 华为技术有限公司 多个无线接入网聚合系统及其实现方法和接入网网元
EP2557842B1 (fr) * 2011-08-10 2018-05-23 Alcatel Lucent Resélection de cellules autonome par un équipement d'utilisateur
US8934899B2 (en) 2012-05-08 2015-01-13 Blackberry Limited Apparatus and method for high priority search on RRC state change
US20130303165A1 (en) * 2012-05-08 2013-11-14 Research In Motion Limited Apparatus And Method For Storage Of Priority-Based Reselection Parameters At Handover And Connection Establishment
EP2888894A1 (fr) * 2012-08-23 2015-07-01 Nokia Solutions and Networks Oy Découverte massive de dispositifs
CN105025541B (zh) * 2014-04-29 2019-09-03 上海诺基亚贝尔股份有限公司 用于基带池中虚拟基站迁移的方法及装置
US10244444B2 (en) 2015-03-04 2019-03-26 Qualcomm Incorporated Dual link handover
TWI562567B (en) * 2015-03-23 2016-12-11 Ind Tech Res Inst Method of automatically managing applications on digital convergence gateways, system therefor and apparatus therewith
CN109792613B (zh) 2016-09-28 2020-10-09 华为技术有限公司 无线电资源管理配置设备和方法
US10834618B1 (en) * 2019-08-05 2020-11-10 Sprint Communications Company L.P. Wireless communication network access using different functionality splits for different communication services

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5422930A (en) * 1993-05-20 1995-06-06 Motorola, Inc. Method and apparatus for sharing radio frequency spectrum in a radio frequency communication system
US5737689A (en) * 1994-06-14 1998-04-07 Telefonaktiebolaget Lm Ericsson Method for preventing calls of bad quality from being disconnected in a cellular mobile radio system
US6002678A (en) * 1997-10-31 1999-12-14 Motorola, Inc. Method of handing-off a remote unit based on overhead information start times
US7876729B1 (en) * 1998-07-20 2011-01-25 Qualcomm Incorporated Intersystem base station handover
US6807164B1 (en) * 1999-09-14 2004-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Power control in a CDMA mobile communication system
US7215958B2 (en) * 2001-08-20 2007-05-08 Nokia Corporation Relocation method, system and network element
EP1464191B1 (fr) * 2002-01-08 2010-03-10 Nokia Corporation Procede et appareil de configuration et de reconfiguration de parametres hsdpa specifiques a une cellule
CA2551852A1 (fr) * 2004-01-27 2005-08-11 Telcordia Technologies, Inc. Procedes et systemes pour une optimisation automatique dynamique des parametres d'un reseau cdma
US20050215265A1 (en) * 2004-03-23 2005-09-29 Sharma Sanjeev K Method and system for load balancing in a wireless communication system
US7257409B2 (en) * 2004-03-31 2007-08-14 Lucent Technologies Inc. Centralized cell homing and load balancing in a base station controller

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI419579B (zh) * 2005-07-29 2013-12-11 Nokia Siemens Networks Gmbh 多跳無線移動通信網路中重配置方法

Also Published As

Publication number Publication date
CN1981553A (zh) 2007-06-13
WO2005107303A1 (fr) 2005-11-10
DE602004001335D1 (de) 2006-08-03
ATE331414T1 (de) 2006-07-15
US20080069088A1 (en) 2008-03-20
DE602004001335T2 (de) 2006-11-09
JP2007535251A (ja) 2007-11-29
CN1981553B (zh) 2010-08-11
EP1592275A1 (fr) 2005-11-02

Similar Documents

Publication Publication Date Title
EP1592275B1 (fr) Déplacement aussi partiellement d'une fonctionnalité de gestion de ressources radio d'un premier station de base à un autre dans un réseau d'accès radio distribué
JP4733688B2 (ja) 分散型無線アクセスネットワークにおける遅延型基地局移転
KR101295483B1 (ko) 패킷 데이터 송수신 장치 및 방법
EP1917823B1 (fr) Amélioration des procédures de mobilité iub/iur hsdpa/hsupa
US7821996B2 (en) Mobility enhancement for real time service over high speed downlink packet access (HSDPA)
EP1532779B1 (fr) Changement de canaux ptp et ptm de mbms
US8077680B2 (en) Packet-switched handover
US20070298803A1 (en) Radio network system, radio base station and handover control method used for the same
WO2010051782A1 (fr) Procédé de notification, dispositif et système de commutation de cellules de desserte
KR20080085827A (ko) 셀룰러간 전환 개선 방법, 무선 액세스 네트워크 개체,코어 네트워크 개체 및 이동 무선 통신 시스템
WO2006018719A2 (fr) Transmission de donnees dans un reseau de communication sans fil
EP1971174A2 (fr) Procédé de synchronisation de reconfiguration de ressources dans un réseau d'accès radio UMTS
WO2006037664A2 (fr) Procede de gestion de sessions de communication et dispositifs associes
KR101014902B1 (ko) 단말의 기지국 제어기간 핸드오버를 위한 장치 및 방법
KR101421556B1 (ko) Ｗｃｄｍａ 무선망에서의 ｓｒｎｓ 재배치 방법

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20041201

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RTI1 Title (correction)

Free format text: RELOCATION, ALSO OF PARTS, OF RADIO RESOURCE MANAGEMENT CONTROL FUNCTIONALITY FROM ONE BTS TO A SECOND IN A DISTRIBUTED R

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

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

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: CH

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT;WARNING: LAPSES OF ITALIAN PATENTS WITH EFFECTIVE DATE BEFORE 2007 MAY HAVE OCCURRED AT ANY TIME BEFORE 2007. THE CORRECT EFFECTIVE DATE MAY BE DIFFERENT FROM THE ONE RECORDED.

Effective date: 20060621

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: LI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

AKX Designation fees paid

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

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602004001335

Country of ref document: DE

Date of ref document: 20060803

Kind code of ref document: P

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060921

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060921

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20061002

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20061121

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

ET Fr: translation filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20070322

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060921

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070429

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20061222

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060621

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20140612 AND 20140618

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602004001335

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

Ref country code: DE

Ref legal event code: R079

Ref document number: 602004001335

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007380000

Ipc: H04W0004000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602004001335

Country of ref document: DE

Owner name: PANASONIC INTELLECTUAL PROPERTY CORPORATION OF, US

Free format text: FORMER OWNER: PANASONIC CORPORATION, KADOMA-SHI, OSAKA, JP

Effective date: 20140711

Ref country code: DE

Ref legal event code: R082

Ref document number: 602004001335

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

Effective date: 20140711

Ref country code: DE

Ref legal event code: R079

Ref document number: 602004001335

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007380000

Ipc: H04W0004000000

Effective date: 20140711

Ref country code: DE

Ref legal event code: R082

Ref document number: 602004001335

Country of ref document: DE

Representative=s name: GRUENECKER PATENT- UND RECHTSANWAELTE PARTG MB, DE

Effective date: 20140711

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: PANASONIC INTELLECTUAL PROPERTY CORPORATION OF, US

Effective date: 20140722

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20220310

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20220308

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20220309

Year of fee payment: 19

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602004001335

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20230429

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230429

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230429

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230430

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231103