EP2600550B1 - Network nodes and methods - Google Patents

Network nodes and methods Download PDF

Info

Publication number
EP2600550B1
EP2600550B1 EP12188769.9A EP12188769A EP2600550B1 EP 2600550 B1 EP2600550 B1 EP 2600550B1 EP 12188769 A EP12188769 A EP 12188769A EP 2600550 B1 EP2600550 B1 EP 2600550B1
Authority
EP
European Patent Office
Prior art keywords
base stations
user equipment
base station
femto
request
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.)
Not-in-force
Application number
EP12188769.9A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2600550A1 (en
Inventor
Holger Claussen
Eric Jul
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.)
Alcatel Lucent SAS
Original Assignee
Alcatel Lucent SAS
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alcatel Lucent SAS filed Critical Alcatel Lucent SAS
Priority to EP12188769.9A priority Critical patent/EP2600550B1/en
Publication of EP2600550A1 publication Critical patent/EP2600550A1/en
Application granted granted Critical
Publication of EP2600550B1 publication Critical patent/EP2600550B1/en
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/16—Code allocation
    • H04J13/18—Allocation of orthogonal codes
    • H04J13/20—Allocation of orthogonal codes having an orthogonal variable spreading factor [OVSF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/04—Reselecting a cell layer in multi-layered cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/541—Allocation or scheduling criteria for wireless resources based on quality criteria using the level of interference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • 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 methods and network nodes of a wireless telecommunications system.
  • radio coverage is provided by areas known as cells.
  • a base station is located in each cell to provide the radio coverage area.
  • Traditional base stations provide coverage in relatively large geographical areas and these cells are often referred to as macro cells.
  • macro cells It is possible to provide smaller-sized cells, often within a macro cell.
  • Such smaller-sized cells are sometimes referred to as micro cells, pico cells or femto cells.
  • the term femto cells will be used to refer generally to all such small cells.
  • Small cells are typically established by providing a small-cell base station that provides radio coverage having a relatively limited range within the radio coverage area of a macro cell.
  • the transmission power of the small-cell base station is relatively low and, hence, each small cell provides a smaller coverage area compared to that of a macro cell and covers, for example, an office or a home.
  • a group of such small-cell base stations may together provide a wireless small-cell network.
  • Such small cells are typically provided where the communications coverage provided by the macro cell is poor or where a user wishes to use an alternative communications link provided locally, by the small-cell base station, to communicate with the core network.
  • Such a situation may arise where, for example, a user has a pre-existing communications network and the user wishes to utilise that link in preference to that provided by the macro network to communicate with the core network.
  • the group of small-cell base stations providing the wireless small-cell network can together provide extended local coverage to user equipment throughout, for example, a home or an office building by using multiple small-cell base stations distributed throughout those buildings which enables each of those base stations to transmit at a lower power than would otherwise be necessary if coverage was provided by a single small-cell base station.
  • WO 2008/088592 A1 discloses techniques for relocation in a cellular communication system.
  • a network element supports base stations with a shared pilot signal scrambling code. The network element receives a relocation request message that comprises an identification of the shared scrambling code.
  • a group processor determines a group of potential base stations.
  • a request processor transmits a request message to the target base stations that comprises a parameter indication for an uplink transmission from a remote station to the base station and requests the target base stations to measure the uplink transmission.
  • a measurement processor receives measurement reports for the uplink transmission from the target base stations and a selection processor selects a handover target base station based on the measurement reports.
  • DATABASE WPI Week 200830 Thomson Scientific, London, GB; AN 2008-E27302 XP002634799, & CN 101 052 205 A discloses a method of dividing a microcell, which belongs to the same macrocell, into multiple logical sub-districts. Microcells in the same logical sub-district have the same carrier frequency and downlink scrambling code.
  • a method of detecting a mobility event in a wireless telecommunications system comprising the steps of: detecting a set of neighbouring base stations utilising a pilot sharing a scrambling code; and periodically instructing a plurality of base stations of the set of neighbouring base stations to transmit a request to user equipment camped thereon to re-read a broadcast channel associated therewith.
  • the first aspect recognises that the number of separate carrier frequencies available for use by a wireless telecommunications network operator is limited and that carriers may need to be reused. This is particularly the case when base stations are deployed in close proximity and it is not possible to allocate each a separate carrier on a separate frequency and so as the density of deployment increases, the likelihood of interference occurring between base stations occurring increases. This is likely to particularly be the case for small-cell base stations which are deployed by private users sometimes in dense areas such as apartment complexes or commercial buildings. In such circumstances, transmissions by one base station may interfere with transmissions by another.
  • the first aspect recognises that as deployment density of base stations increases, a problem can occur, in that user equipment may not be able to detect that a mobility event has occurred when the user equipment is idle.
  • the first aspect recognises that this is because the user equipment, when idle, simply continues to monitor the scrambling code of the pilot signal it is receiving.
  • the likelihood of neighbouring base stations using the same carrier and scrambling code also increases. Accordingly, although the user equipment has moved from the cell on which it was camped to another cell, the user equipment may not detect that this has occurred because there would be no change in scrambling code.
  • the network may also be unaware that a mobility event has occurred and so is unable to take any ameliorative action. Should an incoming call then occur, the call may not be able to be connected to the user equipment because the paging message for the user equipment will be sent by the original serving base station on which the user equipment was camped, which may now be out of range of the user equipment.
  • a set of neighbouring base stations each sharing an identical scrambling code may be identified. This helps to identify the base stations where the undetected mobility event problem may occur.
  • the base station within that set may be instructed periodically to transmit a request to the user equipment to cause the user equipment to re-read the broadcast channel associated with that base station. In this way, any user equipment which is camped on a base station and which may not detect a mobility event occurring is periodically activated to cause the user equipment to re-read the broadcast channel. Causing the user equipment to re-read the broadcast channel makes the user equipment perform additional processing to that of just simply checking that the scrambling code remains constant.
  • activating the user equipment in this way causes the user equipment to verify that the cell identifier associated with the broadcast channel. Should a mobility event have occurred and the user equipment has moved from one base station to another, then the cell identifier will have changed and the user equipment will indicate to the network that a mobility event has occurred. Thereafter, the network can utilise standard mobility event procedures to transfer the user equipment onto a new serving base station. In this way, should an incoming call then occur, the correct base station is identified to enable a paging message to be sent to the user equipment to alert it to the incoming call.
  • the step of periodically instructing comprises: periodically instructing each base station of the set of neighbouring base stations to transmit the request to user equipment. Accordingly, every base station in the set of neighbouring base stations may be instructed to transmit the request to the user equipment. Should the user equipment have moved to any of the base stations within the set, the user equipment will receive the request and will then identify that a mobility event has occurred.
  • the method comprises the step of: when user equipment is detected registering with a different base station in response to the request, shortening a time between each periodic instruction to transmit the request. Accordingly, should it be determined that the user equipment has moved from one base station to another then this may indicate that the user equipment is relatively mobile and may be currently moving, in which case the time between each periodic instruction to transmit the request may be reduced in order to increase the likelihood of another mobility event being detected.
  • the method comprises the step of: when no user equipment is detected registering with a different base station in response to the request, lengthening a time between each periodic instruction to transmit the request. Accordingly, when it is detected that no re-registering of the user equipment has occurred as a result of the request, this may indicate that the user equipment is relatively static and may be unlikely to undergo a mobility event for some time. In these circumstances, the time between each periodic instruction to transmit the request may be increased in order to reduce the communications overhead and help preserve the battery life of the user equipment.
  • the neighbouring base stations comprise multi-pilot base stations utilising at least one pilot sharing a scrambling code.
  • a network node operable to detect a mobility event in a wireless telecommunications system, comprising: detection logic operable to detect a set of neighbouring base stations utilising a pilot sharing a scrambling code; and request logic operable to periodically instruct a plurality of base stations of the set of neighbouring base stations to transmit a request to user equipment camped thereon to re-read a broadcast channel associated therewith.
  • the request logic is operable to periodically instruct each base station of the set of neighbouring base stations to transmit the request to user equipment.
  • the request logic is operable, when user equipment is detected registering with a different base station in response to the request, to shorten a time between each periodic instruction to transmit the request.
  • the request logic is operable, when no user equipment is detected registering with a different base station in response to the request, to lengthen a time between each periodic instruction to transmit the request.
  • the neighbouring base stations comprise multi-pilot base stations utilising at least one pilot sharing a scrambling code.
  • a computer program product operable, when executed on a computer, to perform the method steps of the first aspect.
  • Figure 1 illustrates a wireless communication system, generally 10, according to one embodiment.
  • User equipment 44 roam through the wireless communication system 10.
  • Base stations 22 are provided which support respective macro cells 24. A number of such base stations are provided, which are distributed geographically in order to provide a wide area of coverage to the user equipment 44.
  • Each base station typically supports a number of sectors. Typically, a different antenna within a base station supports an associated sector.
  • Figure 1 illustrates a small subset of the total number of user equipment and base stations that may be present in a typical communications system.
  • the wireless communication system 10 is managed by a radio network controller 170.
  • the radio network controller 170 controls the operation of the wireless communications system 10 by communicating with the base stations 22 over a backhaul communications link 160.
  • the network controller 170 also communicates with the user equipment 44 via their respective radio links in order to efficiently manage the wireless communication system 10.
  • the radio network controller 170 maintains a neighbour list which includes information about the geographical relationship between cells supported by base stations. In addition, the radio network controller 170 maintains location information which provides information on the location of the user equipment within the wireless communications system 10.
  • the radio network controller 170 is operable to route traffic via circuit-switched and packet-switched networks.
  • a mobile switching centre 250 is provided with which the radio network controller 170 may communicate.
  • the mobile switching centre 250 then communicates with a circuit-switched network such as a public switched telephone network (PSTN) 210.
  • PSTN public switched telephone network
  • the network controller 170 communicates with service general packet radio service support nodes (SGSNs) 220 and a gateway general packet radio support node (GGSN) 180.
  • the GGSN then communicates with a packet-switch core 190 such as, for example, the Internet.
  • femto cell base stations F A to F C each of which provides a femto cell A to C in the vicinity of a building within which the associated femto cell base station is installed.
  • the femto cells A to C provide local communications coverage for a user in the vicinity of those buildings.
  • Each femto cell base station F A to Fc communicates via a femtocell controller/gateway 230.
  • a mobility event such as a handover or camping event occurs between the base station 22 and the femto cell base stations F A to F C when the femto base stations F A to F C come within range.
  • the femto cell base stations F A to Fc typically utilise the user's broadband Internet connection 240 (such as ADSL, Cable, Ethernet, etc.) as a backhaul.
  • Femto cell base stations F A to F C are lower-power, low-cost, user-deployed base stations that provide a high cellular quality of service in residential or enterprise environment.
  • the femto cell base stations F A to F C are provided locally by customers.
  • Such femto cell base stations F A to F C provide local coverage in areas of the macro network where quality of service may be low.
  • the femto cell base stations F A to F C provide for improved quality of service in areas which are difficult for network operators.
  • Femto base stations may be private access or may be public access.
  • femto base station that provides private access
  • access is registered only to registered users, for example family members or particular groups of employees.
  • femto base stations which are public access other users may use the femto base station, typically subject to certain restrictions to protect the quality of service received by preferred users.
  • the transmission power of the femto cell base station F A to F C is relatively low in order to restrict the size of the femto cell to a range of tens of metres or less.
  • the femto cell base stations F A to F C have extensive auto-configuration and self-optimisation capability to enable a simply plug-and-play deployment. As such, they are designed to automatically integrate themselves into an existing macro cellular wireless network 10.
  • the femto cells are normally grouped into clusters and each femto cell cluster behaves like a single RNC when communicating with an SGSN in an existing packet switch core network or when communication with a MSC in an existing circuit switched core network.
  • RNC functionality is geographically dispersed across a large number of network elements, it is necessary to deploy a femto gateway for each cluster of femto cells.
  • This femto gateway terminates the signalling interfaces between the traditional core network elements and the femto cell cluster, thereby creating the notion of a single virtual RNC.
  • This virtual RNC represents the femto cell cluster as a whole.
  • the femto gateway supports a number of procedures that are implemented on the femto base stations themselves.
  • Figure 3 illustrates conceptually an example arrangement showing the composition of transmission carriers and the effect of different types of codes.
  • two broadband carriers C 1 and C 2 each being transmitted on a different frequency f 1 and f 2 .
  • the carriers are split using scrambling codes to enable the carriers to support multiple transmissions.
  • a plurality of, typically orthogonal, scrambling codes are provided which provide for a plurality of bearers B 11 to B 1N and B 21 to B 2N .
  • these bearers are split using channelization codes into a plurality of channels.
  • the bearer B 21 is split into a plurality of channels, in this example a downlink channel CH D , an uplink channel CH U , a control channel CH C and a plurality of other channels (not shown).
  • Each channel utilises a spreading code to enable each channel to be decoded in the presence of interference from other channels.
  • the spreading code is used by a receiver to identify and extract the original data.
  • the effect of the spreading code is to effectively spread the transmitted data over a greater number of bits in order to reduce its susceptibility to interference and to improve the reliability of data extraction.
  • the greater the length of the spreading code (and therefore the greater the extent of duplication and associated resistance to data loss), the lower the effective data rate of the channel becomes.
  • a trade-off exists between providing high data rates and providing the certainty of being able to extract the original data reliably.
  • Figure 4 illustrates schematically an example tree arrangement of orthogonal spreading codes.
  • the length of the code increases by one every time a branch of the tree is followed in a direction away from the root. That is to say, the length of spreading code SC 12 is one greater than the length of spreading code SC 1 , and the length of spreading code SC 122 is one greater than the length of spreading code SC 12 . Accordingly, it can be seen that towards the leaves of the tree the codes are longest and therefore provide the lowest effective data rates. Similarly, towards the root of the tree the codes are shortest and therefore provide the highest effective data rates.
  • Orthogonality of the codes can be achieved by ensuring that if a given code in the tree is used, then none of the codes from that scrambling code towards the leaves can then be used. For example, if the spreading code SC 11 were selected, then all codes towards the leaves (i.e. spreading code SC 111 and SC 112 and their leaf spreading codes) would no longer be available. This means that the selection of spreading codes needs to be carefully controlled, since an inappropriate selection of a spreading code can lead to unavailability of other spreading codes. For example, if spreading codes SC 11 and SC 12 were selected, then no other spreading codes would be available.
  • FIG. 5 shows a centralised control scheme where a central controller, such as a femto gateway 230 or RNC or mobility management entity (MME), manages a number of base stations such as femto base stations F A to F C .
  • a central controller such as a femto gateway 230 or RNC or mobility management entity (MME)
  • MME mobility management entity
  • the gateway 230 maintains a neighbour list indicating each femto base station, their carrier and scrambling codes. From this information the gateway 230 is able to derive sets of neighbouring femto base stations which share the same carriers and scrambling codes.
  • FIG. 6 this shows a distributed control scheme.
  • the femto base stations themselves can act as a central controller and through information either provided from user equipment measurement reports, from sniffing by the femto base station itself and/or from information provided by the core network maintains a neighbour list indicating each femto base station, their carrier and scrambling codes. From this information each femto base station is able to derive a set of neighbouring femto base stations which share the same carriers and scrambling codes.
  • non-orthogonal codes may be selected or codes may be selected which prevent other neighbouring base stations from being able to select a non-interfering spreading code. Accordingly, a collaboration or negotiation between neighbouring base stations, each utilising the same scrambling code on the same carrier, is required to prevent unnecessary interference from occurring. In particular, careful allocation of the spreading codes is required to ensure that there are enough spreading codes for each femto cell to operate and that the channels requiring high data rates get as short a spreading code as possible.
  • the femto base station F A needing a spreading code sends a request to the gateway 230 who then either directly allocates an available spreading code or starts an allocation algorithm that reallocates the already allocated spreading codes amongst those base stations that currently need spreading codes.
  • the gateway 230 receives an indication of each base station's operating characteristics such as, for example, an indication of the traffic demand that the base station has to meet and/or any minimum quality of service requirements that a base station may need to meet which may restrict the minimum length of channelization code that may be selected for that base station. Accordingly, the gateway 230 will receive one or more of the following inputs: the number of neighbouring base stations sharing the same carrier and scrambling code, the traffic demand on each of those base stations (this may be either a fixed demand, a variable demand or an indication that there is no demand) and any quality of service requirements. The gateway 230 will also be provided with a tree of spreading codes, such as that illustrated in Figure 4 .
  • An algorithm may then use that information to achieve any one of a number of different possible desired outcomes, in accordance with specified policies. For example, the algorithm may only consider those base stations which have current traffic demand and seek to allocate the minimum length spreading code to each of those base stations. Alternatively, the algorithm may allocate only spreading code having a minimum length to take into account the quality of service restrictions on a base station. Likewise, the algorithm may pre-allocate spreading codes to base stations with no active traffic demand, in order that those codes may be rapidly utilised when required. By pre-allocating spreading codes, the need to re-execute the allocation algorithm is obviated when traffic demand occurs or when another base station within the set is activated.
  • the gateway 230 may re-request the required information from the base stations, re-run the algorithm and re-allocate the spreading codes to each base station.
  • the base stations themselves can act as a central controller for a distributed scheme.
  • femto base station F B requires spreading codes and will start negotiation with its neighbours. Accordingly, in this arrangement the femto base station F B is provided with the much of the same functionality as the gateway 230 mentioned above.
  • An advantage of such a distributed scheme is that it provides for better scalability.
  • femto base station F B may then leave the control of the negotiation to femto base station F A . If the two femto base stations initiate a negotiation simultaneously, they may run a distributed election algorithm to choose which one ought to act as the controller, who then does the work.
  • FIG. 7 illustrates in more detail an example arrangement of a femto base station, generally F, incorporating the spreading code allocation functionality.
  • the femto base station F has an antenna 300 operable to support communications with user equipment and to detect the presence of other base stations.
  • the antenna 300 is coupled with a transceiver 310, which is allocated codes by a code controller 320.
  • the code controller 320 operates a spreading code allocation algorithm using information gathered either via the antenna 300, transceiver 310, sniffer 330 and detection unit 340 route, or via the backhaul transceiver 350.
  • the code controller 320 When setting up connections with user equipment, a suitable spreading code will need to be allocated.
  • the code controller 320 either has a spreading code already available, starts negotiating for one with the femto base stations that are neighbours, or requests one from the gateway 230.
  • the division of the available spreading codes is performed in accordance with a particular predetermined policy. For example, one policy could be to allocate the codes in proportion to traffic demands so that, for example, for neighbouring base stations each requiring a high load channel will each get approximately one quarter of the available spreading codes. Another policy may be to favour the first base station's two requests, so that later requests are given longer spreading codes and thus less data bandwidth.
  • any desirable policy and implementing algorithm to allocate these spreading codes may be used.
  • Another policy may be to pre-allocate spreading codes for future allocation to base stations that in future require to support transmissions with user equipment. Another policy may be to prevent less than a minimum length spreading code being allocated to ensure that a minimum level of redundancy occurs in the transmissions to improve their robustness to interference. Another policy may be to allocate spreading codes which achieve a minimum data throughput to each base station.
  • a base station when a base station receives a new spreading code, it gives these codes to its transmission unit at a predetermined time. It is important for the base stations to implement the change in codes at the correct time, as the actual codes in use need to be orthogonal or else they will cause interference.
  • base stations within a macro cell can synchronise their transmissions using the pilot of that macro base station.
  • the base stations can run a time synchronisation protocol such as MTP to synchronise their clocks via their backhaul.
  • base stations negotiate a set of orthogonal spreading codes and then use them to avoid interference.
  • Spreading codes can be described as a tree, where the length of the code increases by one every time a branch of the tree is followed in a direction away from the root; we say down to signify this direction and say up to signify direction toward the root.
  • the codes are longest and provide the lowest data rates. Orthogonality of the codes is achieved as follows: if a given code in the tree is used, none of the codes below it can be used. There is a trade off between the number of usable codes and the maximum data rate achievable on the channels.
  • base stations that require high data rates must have short codes, but there is a limited amount of short codes.
  • To support many base stations there must be many codes in use - one for each channel. This means that this approach requires careful negotiation of the codes as to ensure that there are enough codes for each base station to operate and that the channels requiring high data rates get as short a code as possible (as to achieve as high a data rate as possible).
  • Spreading codes can be reused by other base stations as long as two base stations that use the same channelization code (or subcode) are not within range of one another.
  • a problem that can occur when the density of base stations increases is that the likelihood of neighbouring base stations sharing identical carriers and scrambling codes also increases. This causes a problem for the core network because user equipment may not be able to detect during an active call that a mobility event is occurring. This is because the user equipment will fail to detect a change in cell because the user equipment uses a change in scrambling codes to detect that a change in cell is occurring. However, because neighbouring cells may use identical scrambling codes, the user equipment is unable to identify a change in cell.
  • the core network detects that neighbouring base stations share the same carrier and scrambling code and, for those sets of neighbouring base stations, information relating to the strength of the pilot signal that shares the same scrambling code as other neighbouring pilot signals, which may otherwise have been utilised in the assessment of whether a mobility event is occurring, is ignored and not used in the assessment of whether a mobility event is occurring. Instead, the core network uses information relating to any further pilot signals also being transmitted by those base stations, and whose strengths are being reported by the user equipment in order to make that assessment.
  • Figure 8 illustrates an example arrangement of base stations.
  • this arrangement there is provided three femto base stations F A , F B , F C , each of which provides coverage within the coverage area of a macro base station 22.
  • Each of the femto base stations F A to Fc utilise dual pilot transmissions.
  • a network node such as the gateway 230, interrogates base stations under its control.
  • the gateway 230 determines neighbour lists for each of the femto base stations, as well as determining the carriers and the scrambling code used by each of the pilot transmissions.
  • pilot 1 for each of the femto base stations F A to F C shares the same carrier and scrambling codes.
  • the femto gateway will designate any measurement information relating to those pilots, designated as A-C S , as being information relating to a shared pilot and will ignore that information for the purposes of assessing whether a mobility event has occurred.
  • the femto gateway 23 will utilise the measurement information relating to pilot 2 of each of the femto base stations F A to Fc, designated as A 2 to C 2 , respectively.
  • the user equipment at time t 1 is initially located in the vicinity of femto base station F B .
  • the user equipment 44 senses the strength of pilots that it is able to receive and provides this information in measurement reports to the gateway 230.
  • the gateway 230 then assembles the list as shown.
  • the list shows that the strongest signal received by the user equipment is that of the pilot B 2 of femto base station F B .
  • the shared pilots A-Cs have the same strength.
  • the next strongest signal is from the pilot M of the macro base station 22, then the second pilot A 2 from femto base station F A . and finally the second pilot C 2 from femto base station F C . Because the other pilot from femto base stations F A and F C share the same carrier and scrambling code as that for femto base station F B , it is not possible to separately measure these signals.
  • the user equipment 44 has moved to a location in the vicinity of femto base station F C .
  • the user equipment 44 continues to provide measurement reports to the femto gateway 23 and the table is updated as indicated.
  • the strength of the signal reported for the shared pilot A-Cs has actually gone up, despite the user equipment 44 having moved away from the femto base station F B . This is due to the proximity of the user equipment 44 to the femto base station F C which is also transmitting the same pilot signal on the same carrier, with the same scrambling code.
  • the strongest pilot signal is the second pilot signal C 2 from femto base station F C , then the second pilot signal A 2 from femto base station F A , followed by the second pilot signal M from the macro base station 22 and finally the second pilot signal B 2 from femto base station F B .
  • the signal from the femto base station F B may now be insufficient to support reliable communication with the user equipment 44.
  • the strength of the shared pilot A-Cs has not dropped, the fact that the user equipment 44 is no longer supportable by the femto base station F B may not have been detected by the network, nor the user equipment 44.
  • the gateway 230 is aware that it should disregard information provided in measurement reports relating to the shared pilot A-Cs. Accordingly, instead, the gateway 230 monitors the signal strength of the secondary pilot B 2 provided by the femto base station F B and notices that the user equipment 44, when transiting between time t 1 and t 2 , reports that the signal strength associated with the pilot B 2 begins to drop.
  • the gateway 230 When the strength of this pilot B 2 drops to below a predetermined threshold, the gateway 230 will initiate a handover procedure to hand over the user equipment 44. Depending on whether the neighbouring femto base stations are open access or private access and, if private access, whether the user equipment 44 is a registered user of that femto base station, will affect whether the handover procedure will hand over the user equipment 44 to another femto base station or back to the macro base station 22. Assuming that the gateway 230 determines that a femto base station may be used as a candidate for handover, the gateway 230 will refer to the table to identify the candidate with the strongest pilot signal which, in this case at time t 2 , is femto base station F C .
  • this technique use a second pilot signal for each involved base station so that they each send out a unique identification signal.
  • User equipment 44 will pick up the secondary pilot from base stations within range and when moving from one base station to another, it will report the signal strengths of both base station's secondary signal (along with the signal strength of the primary - which the user equipment believes to come from the serving base station).
  • the network can detect the need for a handover of the user equipment from the serving base station to another base station. if the other base station is private access and the user equipment is not allowed to use that base station then the user equipment is handed over to the macro base station 22 instead.
  • a problem can occur in that as the density of deployment of base stations increases, the likelihood of neighbouring base stations using the same carrier and scrambling code also increases. Accordingly, if the user equipment 44 is camped on a base station and is in the idle mode, the use of the same scrambling code by a neighbouring base station can cause a problem in that the user equipment 44 may move from one base station to another without detecting this because it continues to receive the same scrambling code. Should an incoming call occur, the user equipment 44 may now miss the paging message sent out by the original base station.
  • the network detects that neighbouring base stations share the same carrier and scrambling code and, for those sets of neighbouring base stations cause the base stations in those sets to regularly send a request message to all user equipment camped on those base station to get them to re-read the broadcast channel.
  • Causing user equipment 44 to re-read the broadcast channel forces the user equipment to detect whether a change in cell has occurred because the user equipment will also decode the cell identifier, which will have changed if the user equipment has undergone a mobility event.
  • Figure 9 illustrates an example of deployment of femto base stations to illustrate this technique in more detail.
  • femto base stations F A to F C within the coverage area provided by a macro base station 22.
  • the user equipment 44 is in idle mode and is camped on femto base station F B .
  • the gateway 230 has been previously notified that the user equipment 44 is camped on femto base station F B in accordance with normal procedures.
  • the gateway 230 will instruct the femto base station F B to send a paging message on its paging channel.
  • the user equipment 44 which is within range of the femto base station F B , is alerted by the paging channel to the presence of an incoming call and the call is then connected.
  • a problem occurs when the user equipment transits outside of the coverage area of femto base station F B .
  • the user equipment 44 is now outside the coverage area of femto base station F B and so would fail to receive the paging message alerting it to the presence of an incoming call.
  • the user equipment 44 is unaware that it has moved outside of the coverage area of the femto base station F B because of the shared scrambling code on the pilot signals from the neighbouring femto base stations F A and F C .
  • the user equipment considers that no change in cell has occurred because the strength of the shared pilot signal A-C S is still indicated as being high.
  • this pilot signal A-C S is now being provided primarily by femto base station F C instead of femto base station F B .
  • the gateway 230 detects that neighbouring femto base stations share a common carrier and scrambling code. Should user equipment 44 camp on any of those femto base stations, then the gateway 230 will instruct the femto base station on which the user equipment 44 is camped to periodically transmit a request to the user equipment 44 to re-read the broadcast channel. To improve the likelihood of user equipment 44 receiving this request whilst it is still able to communicate with the femto base station, the gateway 230 may instruct all neighbouring femto base stations in the set to transmit this request. This request then activates a standard procedure within the user equipment 44 to cause it to re-read the broadcast channel.
  • the user equipment 44 will also automatically verify the cell identifier associated with the broadcast channel. Should the user equipment 44 still be within the coverage of the femto base station, then the user equipment 44 will take no further action. However, should the user equipment 44 detect that the cell identifier has changed, then it will initiate system procedures to relocate to the new base station.
  • the gateway 230 may extend the time between the periodic request being sent to the user equipment 44 because this may indicate that the user equipment is relatively static and reducing the occurrence of these requests will help to reduce power consumption in the user equipment.
  • the gateway 230 may detect that a relocation has occurred, then this may indicate that the user equipment 44 is currently mobile and so the time interval between sending the request messages to the user equipment 44 may be increased to help improve the probability that a mobility event is detected.
  • this technique regularly sends a request message to all user equipment registered at a base station to get them to reread the broadcast channel and thus detect that although a base station is using the same scrambling code, its broadcast data contains a different location code causing the user equipment to reregister.
  • a type of request message already exists in the UMTS standards.
  • each base station sends a broadcast message (a BCCH read message) at regular intervals causing every registered user equipment to reread all system blocks and updates the user equipment's parameters.
  • User equipment that detects it is in a different cell will then reregister with the new base station. Even user equipment that has wandered far away from the base station where it is registered will get the broadcast message as long as it hears just one of the involved base stations.
  • program storage devices e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods.
  • the program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
  • the embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
  • processors may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software.
  • the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared.
  • processor or “controller” or “logic” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage. Other hardware, conventional and/or custom, may also be included.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • ROM read only memory
  • RAM random access memory
  • any switches shown in the Figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.
  • any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the invention.
  • any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP12188769.9A 2010-11-05 2010-11-05 Network nodes and methods Not-in-force EP2600550B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12188769.9A EP2600550B1 (en) 2010-11-05 2010-11-05 Network nodes and methods

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP12188769.9A EP2600550B1 (en) 2010-11-05 2010-11-05 Network nodes and methods
EP10360041.7A EP2451104B1 (en) 2010-11-05 2010-11-05 Network nodes and methods

Related Parent Applications (3)

Application Number Title Priority Date Filing Date
EP10360041.7 Division 2010-11-05
EP10360041.7A Division-Into EP2451104B1 (en) 2010-11-05 2010-11-05 Network nodes and methods
EP10360041.7A Division EP2451104B1 (en) 2010-11-05 2010-11-05 Network nodes and methods

Publications (2)

Publication Number Publication Date
EP2600550A1 EP2600550A1 (en) 2013-06-05
EP2600550B1 true EP2600550B1 (en) 2014-09-03

Family

ID=43799668

Family Applications (2)

Application Number Title Priority Date Filing Date
EP12188769.9A Not-in-force EP2600550B1 (en) 2010-11-05 2010-11-05 Network nodes and methods
EP10360041.7A Not-in-force EP2451104B1 (en) 2010-11-05 2010-11-05 Network nodes and methods

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP10360041.7A Not-in-force EP2451104B1 (en) 2010-11-05 2010-11-05 Network nodes and methods

Country Status (7)

Country Link
US (1) US9894530B2 (zh)
EP (2) EP2600550B1 (zh)
JP (1) JP5897022B2 (zh)
KR (1) KR20130090910A (zh)
CN (1) CN103190104B (zh)
PL (1) PL2451104T3 (zh)
WO (1) WO2012059214A2 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8787262B2 (en) 2011-07-15 2014-07-22 Qualcomm Incorporated Receiving cell broadcast (CB) messages
US8838127B2 (en) * 2012-05-11 2014-09-16 Industrial Technology Research Institute Interference mitigation method in cellular wireless network, and apparatus with the same
EP2739104A1 (en) * 2012-11-28 2014-06-04 Alcatel-Lucent A cellular telecommunications base station and a method of allocating a spreading code
US10693623B2 (en) * 2014-01-31 2020-06-23 Apple Inc. Reference subframes for synchronization and cell measurements
EP3117541B1 (en) * 2014-03-14 2018-03-07 Telefonaktiebolaget LM Ericsson (publ) Automated, dynamic minimization of inter-cell site interference in cdma networks
KR20220093391A (ko) * 2014-08-07 2022-07-05 코히어런트 로직스, 인코포레이티드 멀티-파티션 라디오 프레임
BR112017002227A2 (pt) 2014-08-07 2017-11-21 One Media Llc configuração dinâmica de um quadro de dados de transporte phy de multiplexação por divisão de frequências ortogonais flexíveis
EP2991242A1 (en) * 2014-08-27 2016-03-02 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Controller for a SUDA system
CN104507092B (zh) * 2014-12-04 2017-11-17 中国联合网络通信集团有限公司 一种基于异构网络的干扰抑制方法及系统
KR102250991B1 (ko) * 2015-04-16 2021-05-12 한국전자통신연구원 이종 네트워크 환경에서 기지국을 관리하는 제어기 및 그 관리 방법, 기지국 관리 시스템
WO2018119939A1 (zh) * 2016-12-29 2018-07-05 深圳天珑无线科技有限公司 一种信道接入方法及装置
WO2018119942A1 (zh) * 2016-12-29 2018-07-05 深圳天珑无线科技有限公司 一种信道接入方法及装置
WO2018119940A1 (zh) * 2016-12-29 2018-07-05 深圳天珑无线科技有限公司 一种信道接入方法及装置
WO2018119941A1 (zh) * 2016-12-29 2018-07-05 深圳天珑无线科技有限公司 一种信道接入方法及装置
CN112105004B (zh) * 2020-09-15 2022-09-23 努比亚技术有限公司 电子价签网络检测方法、设备及计算机可读存储介质

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3058270B2 (ja) 1998-04-22 2000-07-04 日本電気株式会社 Ｃｄｍａ通信方法、スペクトラム拡散通信システム、基地局、および端末装置
JP3039525B2 (ja) * 1998-07-16 2000-05-08 日本電気株式会社 拡散符号割当装置および方法
US6233231B1 (en) 1998-12-03 2001-05-15 Motorola, Inc. Data transmission within a spread-spectrum communication system
JP3741908B2 (ja) 1999-08-16 2006-02-01 株式会社エヌ・ティ・ティ・ドコモ 周辺基地局情報更新方法、移動通信システム、移動局および基地局
KR100398784B1 (ko) 1999-06-15 2003-09-19 가부시키가이샤 엔.티.티.도코모 이동 통신 시스템에서의 셀 탐색을 위한 정보 관리 방법,이동국의 셀 탐색 방법, 이동 통신 시스템, 이동국,기지국 및 제어국
CN1387703A (zh) * 1999-09-07 2002-12-25 艾利森公司 使用智能调制代码分配的无线通信设备和方法
US6845087B1 (en) * 1999-09-20 2005-01-18 Northrop Grumman Corporation Wideband wireless communications architecture
JP2001333458A (ja) 2000-05-24 2001-11-30 Ntt Docomo Inc トラフィック監視移動体通信方法及び装置
JP2002247639A (ja) * 2001-02-15 2002-08-30 Ntt Docomo Inc 無線チャネル設定制御方法、無線ネットワーク制御装置、基地局装置及び移動通信システム
US6930470B2 (en) 2001-03-01 2005-08-16 Nortel Networks Limited System and method for code division multiple access communication in a wireless communication environment
EP1374423A2 (en) * 2001-03-01 2004-01-02 Nortel Networks Limited System and method for wireless code division multiple access communication
CN1145296C (zh) * 2001-04-30 2004-04-07 华为技术有限公司 一种码分多址系统中的码分配方法
US6999720B2 (en) * 2001-09-14 2006-02-14 Atc Technologies, Llc Spatial guardbands for terrestrial reuse of satellite frequencies
EP1483858A2 (en) * 2002-02-22 2004-12-08 Arizona Board of Regents Nonblocking ovsf codes for 3g wireless and beyond systems
US7787572B2 (en) * 2005-04-07 2010-08-31 Rambus Inc. Advanced signal processors for interference cancellation in baseband receivers
JP4182345B2 (ja) * 2003-06-26 2008-11-19 日本電気株式会社 干渉キャンセルユニット及びマルチユーザ干渉キャンセラ
JPWO2006101168A1 (ja) * 2005-03-23 2008-09-04 日本電気株式会社 呼受付制御システム及び呼受付制御方法
JP2006340051A (ja) * 2005-06-02 2006-12-14 Matsushita Electric Ind Co Ltd Ｃｄｍａ基地局
US8885628B2 (en) * 2005-08-08 2014-11-11 Qualcomm Incorporated Code division multiplexing in a single-carrier frequency division multiple access system
FR2891423B1 (fr) * 2005-09-23 2007-11-09 Alcatel Sa Dispositif et procede de traitement de donnees par modulation de jeux de pseudo-codes d'etalement fonction des cellules destinataires des donnees, pour un satellite de communication multi-faisceaux
CN100502557C (zh) * 2006-04-04 2009-06-17 中兴通讯股份有限公司 移动通信系统中的用户终端切换控制方法
US8081686B2 (en) * 2006-05-16 2011-12-20 Alcatel Lucent Scalable spectrum CDMA communication systems and methods with dynamic orthogonal code allocation
GB2445987B (en) * 2007-01-19 2011-09-28 Motorola Inc Relocation in a cellular communication system
GB2446192B (en) * 2007-01-30 2009-03-18 Motorola Inc A cellular communication system and method of operation therefor
CN101540632B (zh) * 2008-03-20 2013-03-20 华为技术有限公司 多载波系统中的信息传输方法和装置
US20090247157A1 (en) * 2008-03-28 2009-10-01 Qualcomm Incorporated Femto cell system selection
US8325783B2 (en) * 2008-09-23 2012-12-04 Sprint Communications Company L.P. Spreading code optimization based on quality factors
CN101772130A (zh) * 2009-01-07 2010-07-07 中兴通讯股份有限公司 辅助检测信令发送方法

Also Published As

Publication number Publication date
EP2451104A1 (en) 2012-05-09
EP2600550A1 (en) 2013-06-05
KR20130090910A (ko) 2013-08-14
WO2012059214A3 (en) 2012-08-16
EP2451104B1 (en) 2017-06-28
US9894530B2 (en) 2018-02-13
WO2012059214A2 (en) 2012-05-10
JP2013545390A (ja) 2013-12-19
CN103190104A (zh) 2013-07-03
JP5897022B2 (ja) 2016-03-30
US20130294364A1 (en) 2013-11-07
CN103190104B (zh) 2016-06-29
PL2451104T3 (pl) 2018-01-31

Similar Documents

Publication Publication Date Title
EP2600550B1 (en) Network nodes and methods
US10390261B2 (en) Load balancing schemes for idle mode user equipment
US8797975B2 (en) Scrambling code selection
EP2453700B1 (en) Identifying neighbouring base stations
WO2014087392A2 (en) A method for managing heterogeneous cellular networks
CN105357773A (zh) 一种无线宽带通信方法，装置和系统
JP5693612B2 (ja) マクロセルからフェムトセルへの移動局のハンドオーバーを管理するための方法および装置
EP3456119B1 (en) Anchor base station, slave cell and user equipment
EP2514110A1 (en) Interference control method and apparatus in self-organizing system
EP2724580B1 (en) Interference control
EP2496050A1 (en) Multi-operator radio cells
US9743321B2 (en) Mobility techniques
EP2846590B1 (en) Energy saving
GB2452797A (en) Handover in a mobile telecommunications network.
EP2932757B1 (en) Network elements, wireless communication system and methods therefor
EP2755430B1 (en) Soft handover techniques
WO2011079479A1 (zh) 资源调度方法及系统

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

AC Divisional application: reference to earlier application

Ref document number: 2451104

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

111Z Information provided on other rights and legal means of execution

Free format text: AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

Effective date: 20130410

17P Request for examination filed

Effective date: 20131205

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/04 20090101ALI20140328BHEP

Ipc: H04W 60/04 20090101ALI20140328BHEP

Ipc: H04W 36/00 20090101ALI20140328BHEP

Ipc: H04W 84/04 20090101ALI20140328BHEP

Ipc: H04J 13/20 20110101AFI20140328BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20140509

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

AC Divisional application: reference to earlier application

Ref document number: 2451104

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 686068

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140915

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010018820

Country of ref document: DE

Effective date: 20141016

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 686068

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140903

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: 20140903

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: 20140903

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: 20141204

Ref country code: LT

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: 20140903

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: 20140903

Ref country code: NO

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: 20141203

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20140903

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: LV

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: 20140903

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: 20140903

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: 20140903

Ref country code: HR

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: 20140903

Ref country code: RS

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: 20140903

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

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: 20140903

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

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: 20140903

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: 20140903

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: 20140903

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: 20150105

Ref country code: IS

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: 20150103

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: 20140903

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

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: 20140903

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010018820

Country of ref document: DE

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

Ref country code: BE

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

Effective date: 20141130

Ref country code: MC

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: 20140903

Ref country code: LU

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: 20141105

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

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: 20140903

Ref country code: CH

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

Effective date: 20141130

Ref country code: LI

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

Effective date: 20141130

26N No opposition filed

Effective date: 20150604

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

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

Effective date: 20140903

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: 20141105

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

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

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: 20140903

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

Ref country code: SM

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: 20140903

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: 20140903

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; INVALID AB INITIO

Effective date: 20101105

Ref country code: MT

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: 20140903

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: 20140903

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: 20140903

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

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

Ref country code: MK

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: 20140903

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

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

Ref country code: AL

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: 20140903

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

Ref country code: DE

Payment date: 20181023

Year of fee payment: 9

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

Ref country code: BE

Payment date: 20181217

Year of fee payment: 7

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

Ref country code: FR

Payment date: 20191014

Year of fee payment: 10

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602010018820

Country of ref document: DE

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

Effective date: 20191105

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

Ref country code: DE

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

Effective date: 20200603

Ref country code: GB

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

Effective date: 20191105

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

Ref country code: FR

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

Effective date: 20201130