EP2810470B1 - Attribution d'identificateurs aux home node bs - Google Patents

Attribution d'identificateurs aux home node bs Download PDF

Info

Publication number
EP2810470B1
EP2810470B1 EP13701443.7A EP13701443A EP2810470B1 EP 2810470 B1 EP2810470 B1 EP 2810470B1 EP 13701443 A EP13701443 A EP 13701443A EP 2810470 B1 EP2810470 B1 EP 2810470B1
Authority
EP
European Patent Office
Prior art keywords
cell
hnb
cells
gateway entity
neighbouring
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.)
Active
Application number
EP13701443.7A
Other languages
German (de)
English (en)
Other versions
EP2810470A1 (fr
Inventor
Hanns Juergen Schwarzbauer
Srinivasan Selvaganapathy
Alexander Vesely
Dario Serafino TONESI
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.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of EP2810470A1 publication Critical patent/EP2810470A1/fr
Application granted granted Critical
Publication of EP2810470B1 publication Critical patent/EP2810470B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the application concerns the allocation of identifiers for home node Bs in cellular communication systems.
  • the operation of a cellular access network typically involves a communication device moving from one cell to another cell.
  • the cell change procedure makes use of a temporary identifier for the communication device based on a combination of (i) a radio network controller identifier (RNC-ID) by which the serving radio network controller (SRNC) is identified to the core network (CN) and (ii) a temporary identifier by which the communication device is uniquely identified to the SRNC.
  • RNC-ID radio network controller identifier
  • SRNC serving radio network controller
  • CN core network
  • a temporary identifier by which the communication device is uniquely identified to the SRNC.
  • One example of such sharing of RNC-ID is the use of a common RNC-ID by all Home NodeBs (HNBs) that are connected to the core network via the same Home NodeB Gateway (HNB-GW). This is due to the fact that the core network uses the RNC-ID to identify the radio network controllers and from core network perspective the HNB-GW is considered to be a radio network controller.
  • GB2482071A relates to techniques for selecting a scrambling code.
  • the invention relates to methods, apparatuses and computer program products as set forth in the claims.
  • a cell change procedure makes use of a radio network temporary identifier (RNTI) for the communication device based on a combination of (i) an RNC-ID and (ii) a RNTI allocated to the communication device; and (b) a common RNC-ID is used for a plurality of network entities allocating RNTIs to communication devices.
  • RNTI radio network temporary identifier
  • FIG. 1 illustrates an example of a mobile telecommunication network (MTN) involving macro cells 4 with transceivers at respective macro base stations called NodeBs (NBs) 2 and HNB cells with transceivers at respective HNBs 6.
  • MTN mobile telecommunication network
  • NBs NodeBs
  • HNB cells with transceivers at respective HNBs 6.
  • HNB cells are useful, for example, for providing good service to indoor users in homes or small offices or shopping malls.
  • the plurality of macro NBs 2 are connected to a common RNC 10.
  • the RNC 10 performs radio resource management and some of the mobility management functions for the UEs 8 served by the macro NBs 2 (base stations) connected to the RNC 10.
  • RNC radio network controller
  • the macro RNC 10 is connected to the core network (CN) 12 including a packet-switched part including GPRS support nodes.
  • the HNBs 6 are connected to the same core network via the internet 16 and a Home NodeB Gateway (HNB-GW) 14.
  • HNB-GW 14 acts as a concentrator of HNBs and presents itself to the CN 12 as a single RNC; and all the HNBs 6 connected to CN 12 via the same HNB-GW 14 share a common RNC-ID.
  • FIG 2 shows a schematic partially sectioned view of an example of user equipment 8 that may be used for communicating with the macro NBs 2 and HNBs 6 of Figure 1 via a wireless interface.
  • the user equipment (UE) 8 may be used for various tasks such as making and receiving phone calls, for receiving and sending data from and to a data network and for experiencing, for example, multimedia or other content.
  • the UE 8 may be any device capable of at least sending or receiving radio signals to or from the macro NBs 2 and small cell HNBs 6.
  • Non-limiting examples include a mobile station (MS), a portable computer provided with a wireless interface card or other wireless interface facility, personal data assistant (PDA) provided with wireless communication capabilities, or any combinations of these or the like.
  • the UE 8 may communicate via an appropriate radio interface arrangement of the UE 8.
  • the interface arrangement may be provided for example by means of a radio part and associated antenna arrangement.
  • the antenna arrangement may be arranged internally or externally to the UE 8.
  • the UE 8 may be provided with at least one data processing entity 203 and at least one memory or data storage entity 217 for use in tasks it is designed to perform.
  • the data processor 213 and memory 217 may be provided on an appropriate circuit board 219 and/or in chipsets.
  • the user may control the operation of the UE 8 by means of a suitable user interface such as key pad 201, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • a display 215, a speaker and a microphone may also be provided.
  • the UE 8 may comprise appropriate connectors (either wired or wireless) (not shown) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • FIG. 3 shows an example of apparatus for use at the small cell HNBs 6 and macro NBs 2.
  • the apparatus comprises a radio frequency antenna 301 configured to receive and transmit radio frequency signals; radio frequency interface circuitry 303 configured to interface the radio frequency signals received and transmitted by the antenna 301 and the data processor 306.
  • the radio frequency interface circuitry 303 may also be known as a transceiver.
  • the apparatus also comprises an interface 309 via which it can send and receive information to and from one or more other network nodes e.g. MSC/SGSN/MME or O&M entity.
  • the data processor 306 is configured to process signals from the radio frequency interface circuitry 303, control the radio frequency interface circuitry 303 to generate suitable RF signals to communicate information to the UE 8 via the wireless communications link, and also to exchange information with other network nodes via the interface 309.
  • the memory 307 is used for storing data, parameters and instructions for use by the data processor 306.
  • FIG. 4 shows an example of apparatus for use at the macro RNC 10 and the HNB-GW 14.
  • the apparatus 400 includes a memory 402 for receiving and storing data of the kind mentioned below in the description of an embodiment of the present invention, and a data processor 404 for processing data stored in memory 402 and making computations and determinations of the kind mentioned below in the description of an embodiment of the present invention.
  • the apparatus also comprises an interface 406 via which it can send and receive information to and from other network nodes.
  • UE 8 can be in a special connected state in which it is not allocated a dedicated physical channel.
  • a connected state is e.g. the CELL_FACH state described at 3GPP 25.331 Section 7.2.2.2.
  • the CELL_FACH state is characterised by a lower power consumption rate (e.g. about 50%) at UE 8 compared to the CELL_DCH state described at 3GPP 25.331 Section 7.2.2.3, in which UE 8 is allocated a dedicated physical channel.
  • a dedicated physical channel is a channel by which data can be sent to and from UE 8 without requiring prior reservation of resources.
  • a cell change procedure begins with UE 8 sending a cell update message to the new NodeB (e.g. macro NB or HNB) that has been identified as a target cell (e.g. by the measurement at UE 8 of reference signals transmitted by the new NodeB); and is followed by the new NodeB forwarding the cell update message to the source NodeB (e.g. HNB). It is therefore required that the source NodeB can be identified by information included in the cell update message.
  • the new NodeB e.g. macro NB or HNB
  • UE 8 is identified in cell change procedures by a radio network temporary identifier (u-RNTI) comprising a combination of (i) the RNC ID for the RNC serving UE 8 (SNRC) and (ii) the radio network temporary identifier (s-RNTI) that the SRNC uses to uniquely identify UE 8 from all the other UEs served by the same RNC.
  • u-RNTI radio network temporary identifier
  • the RNC-ID is a 12-bit number
  • the s-RNTI is a 20-bit number.
  • HNBs 6 connected to the same HNB-GW 14 share the same RNC-ID.
  • s-RNTIs temporary identifiers assigned to UE 8 by the serving HNB 6
  • s-RNTIs temporary identifiers assigned to other UEs by other HNBs 6 connected to the same HNB-GW 14.
  • Figure 5 illustrates an example of a HNB Registration procedure according to an embodiment of the present invention.
  • HNB-GW 14 When a HNB 6 is powered up, it sends to HNB-GW 14 a HNB Registration Request message according to the HNBAP (Home NodeB Application) protocol, which message includes additional information identifying one or more macro cells as neighbouring cells (STEP 502).
  • the neighbouring macro cells could be determined from measurements made by HNB of the power at which it detects macro cell reference signals.
  • the information in the Registration Request message could identify up to e.g. 4 macro cells whose reference signal is detected at HNB 6 at the highest received power (RSRP) and exceeds a predetermined RSRP threshold.
  • the HNB Registration Request message also includes information identifying neighbouring HNBs, which as discussed later, is useful for cell changes from HNB 6 to a neighbouring HNB.
  • HNB-GW Based on the information about neighbouring macro cells in the HNB Registration Request message, HNB-GW selects for HNB 6 a s-RNTI prefix that distinguishes HNB 6 from any other HNB that is connected to HNB-GW 14 and has specified one or more neighbouring cells (macro cells or HNB cells) in common with HNB 6 (STEP 504).
  • HNB-GW 14 creates a mapping table 702 in which s-RNTI prefixes are mapped to HNB identities for each cell that has been specified as a neighbouring cell by any one of the HNBs registered with HNB-GW14. For the simple example of Figure 7 , four HNBs A, B, C and D are registered with HNB-GW.
  • HNB A specifies macro cell MC 1 only as a neighbouring cell
  • HNBs B and C both specify both macro cells MC1 and MC2 as neighbouring cells
  • HNB D specifies macro cell MC 2 only as a neighbouring cell.
  • HNB-GW creates a mapping table 702, in which s-RNTI prefixes are mapped to HNB identities for each of macro cells MC1 and MC2.
  • s-RNTI prefixes X, Y and Z are respectively allocated to HNBs A, B and C.
  • One characteristic of the method as described subsequently is assigning s-RNTI prefixes uniquely for HNBs commonly located in the coverage area of a reported macro NB and also uniquely within the radio coverage of a neighbouring HNB.
  • HNBs are grouped according to the identities of the macro NBs that they report as neighbouring cells.
  • HNBs A, B, C have unique s-RNTIs assigned thereto to allow retrieval of the UE context in case a UE performs the cell update procedure with the macro NB MC1.
  • HNBs B, C and D are located in the coverage area of macro NB MC2 and have unique s-RNTI values assigned thereto.
  • HNB A is reporting only macro NB MC1 but not macro NB MC2 allows that the s-RNTI prefix X can also be used for HNB D, because D does not specify macro cell MC1 as a neighbouring cell i.e., more generally, does not share any neighbouring cells with HNB A, to which s-RNTI prefix X is also allocated.
  • s-RNTI values could be re-used of nodes not sharing one or more common neighbouring nodes, which could comprise both macro NBs and HNBs. Furthermore these nodes are not necessarily direct neighbours that a UE would be able to address in a CELL-UPDATE procedure.
  • HNB-GW ends the HNB registration procedure by sending a HNB-Registration-Accept message to HNB 6 (STEP 506), which message specifies the s-RNTI prefix that has been allocated to HNB 6.
  • the HNB-GW also provides HNB 6 with information about the neighbouring cells of HNB, which neighbouring cells may include cells of other HNBs or macro cells.
  • the HNB-GW may provide an indication which allows HNB 6 to identify and communicate with the HNB node for the neighbouring HNB cells, eg., a Transport Network Layer Address of the HNB which may be an address according to the Internet Protocol RFC791, or according to the Asynchronous Transmission Mode ATM protocols, a Radio Network Layer identification of the HNB which may be a s-RNTI prefix of the neighbouring HNBs within the same HNB-GW.
  • the HNB may determine if a neighbouring cell relates to a neighbouring HNB by evaluating the RNC-ID and the s-RNTI of the neighbouring cell.
  • RNC-ID of neighbouring cell is equal to its own RNC-ID, both are connected to the same common node HNB-GW and the s-RNTI prefix value distinguishes both HNBs within the common node HNB-GW.
  • HNB may determine the neighbouring HNB and the related communication address by matching the s-RNTI prefix value with previously received neighbour cell information from HNB-GW and may send a message to the HNB using the related Transport Network Layer Address of the HNB.
  • HNB allocates a u-RNTI to UE 8.
  • this u-RNTI is a 32-bit number, which comprises: (a) a 10-bit RNC-ID for the HNB 6 which is also the RNC-ID for all other HNBs connected to the CN via the same HNB-GW 14; and (b) a 20-bit s-RNTI, which itself comprises (i) the s-RNTI prefix allocated to HNB 6 by HNB-GW and (ii) a 10-bit number allocated to the UE 8 by HNB 6 which distinguishes UE 8 from any other UE served by the same HNB 6.
  • the lengths of the s-RNTI prefix in bits may be different to 10bits as in this example.
  • the actually used s-RNTI prefix length may be assigned by HNB-GW 14 as well as the s-RNTI prefix value and shared with HNB 6.
  • a different s-RNTI prefix length allows a different maximum number of identifiable HNBs to be registered at the HNB-GW 14.
  • the s-RNTI prefix reserves a certain part of the 20-bit s-RNTI values, less numbers are available to HNB 6 to distinguish and identify a UE 8 from all other UEs served by the HNB 6.
  • the lengths i.e.
  • the number of bits) of the s-RNTI prefix may be assigned dynamically upon registration of a HNB 6 at the HNB-GW 14 and communicated to the HNB 6, which may allow the adjustment of network resources according to HNB performance or the number of UEs attaching to the HNB 6 and remaining attached for some time period.
  • Figure 6 illustrates an example of a HNB ⁇ macroNB cell change procedure according to an embodiment of the present invention.
  • Figure 6 illustrates a cell change procedure after UE 8 in a CELLFACH state of connection with HNB (Source HNB) has identified a macro cell 4 as a target cell.
  • UE 8 transmits eg., via the NodeB 2 for the target macro cell 4, to the macro RNC 10 for the target macro cell 4 a cell update message indicating the u-RNTI assigned to UE 8 by the source HNB (STEP 602).
  • Macro RNC 10 sends the cell update message to the HNB-GW 14 identified by the RNC-ID included in the cell update message, together with a macro cell ID for the target macro cell (STEP 604).
  • HNB-GW 14 determines the identity of source HNB from (a) the s-RNTI prefix forming part of the u-RNTI included in the cell update message and (b) the macro cell ID (STEP 606). In more detail, the HNB-GW consults the mapping table 702 it has created including mapping of s-RNTI to HNB identity for each macro cell ID. For the simple example illustrated in Figure 7 : if the macro cell ID received at HNB-GW from macro RNC 10 is MC 1, and the s-RNTI prefix forming part of the u-RNTI specified in the cell update message is X, HNB-GW can determine that the source HNB is HNB A.
  • HNB-GW next forwards the cell update message to the HNB identified from the combination of the s-RNTI prefix and the macro cell ID (STEP 608).
  • a conventional SRNS (Serving Radio Network Subsystem) Relocation procedure is then performed between Source HNB 6 and the macro RNC 10 for the target macro cell (STEP 610), by which procedure the PDP (Packet Data Protocol) context is transferred to macro RNC 10 from source HNB 6.
  • PDP Packet Data Protocol
  • the PDP context is referred to as UE context as well and may include UE authorisation information, UE configuration information, UE state information and avoids re-synchronisation between UE and network upon cell changes.
  • macro RNC 10 sends a cell-update-confirm message to UE 8, which message includes a new u-RNTI for UE 8, as allocated to it by macro RNC 10.
  • UE 8 in a CELL_FACH connection state with Source HNB 6 identifies a neighbouring HNB cell as a target cell, it transmits to the target HNB 6 a cell-update message including the u-RNTI allocated to UE 8 by Source HNB.
  • target HNB will have been one of the HNBs identified as a neighbouring HNB in the HNB Registration Request message sent from source HNB 6 to HNB-GW 14 at the time of registration of Source HNB with HNB-GW 14.
  • HNB-GW 14 will have already informed all HNBs 6 identified as neighbouring HNBs by Source HNB of the s-RNTI prefix and Transport Network Layer address (IP address) for Source HNB.
  • IP address Transport Network Layer address
  • neighbouring HNB 6 when neighbouring HNB 6 receives a cell update message from UE 8, it can determine the IP address for the source HNB from the s-RNTI prefix included in the received cell update message, and can thereby communicate directly with Source HNB for the PDP context transfer from Source HNB to Target HNB.
  • the s-RNTI prefixes are allocated by HNB-GW 14 such that the s-RNTI prefix also distinguishes between HNBs specifying one or more neighbouring HNB cells in common.
  • target HNB transmits a Cell-Update-Confirm message to UE 8, which message includes a new u-RNTI for UE 8, as allocated to it by Target HNB 6.
  • the new u-RNTI will include the same RNC-ID as the old u-RNTI (because both Source and Target HNBs are connected to the same HNB-GW 14), but it will include a different s-RNTI comprising a different s-RNTI prefix (as allocated to the Target HNB by HNB-GW 14) and a 10-bit number allocated to UE 8 by Target HNB and distinguishing UE 8 from any other UE served by Target HNB.
  • FIG. 8 illustrates the procedure for a cell change to a Target HNB from a Source HNB with which UE 8 has set up a RRC Connection (STEP 802) by which UE has received from Source HNB a u-RNTI including the s-RNTI prefix for Source HNB.
  • UE sends to Target HNB a Cell-Update message including the u-RNTI assigned to it by Source HNB (STEP 804).
  • Target HNB Based on the information Target HNB has for the neighbouring HNBs of Target HNB and from the s-RNTI Prefix included in the Cell-Update message, Target HNB can determine the identity of Source HNB (STEP 806).
  • Target HNB then initiates the context-transfer procedure to transfer the UE context from Source HNB to Target HNB (STEP 808).
  • Target HNB assigns a new u-RNTI to UE, which includes the s-RNTI prefix for Target HNB; and includes the new u-RNTI for UE in a Cell-Update-Confirm message to UE.
  • the HNB ⁇ Macro cell change procedure described above is further illustrated in Figure 9.
  • Figure 9 illustrates the procedure for a cell change to a Target Macro NB from a Source HNB with which UE 8 has set up a RRC Connection (STEP 902) by which UE has received from Source HNB a u-RNTI including the s-RNTI prefix for Source HNB.
  • UE When UE moves to macro-coverage, UE sends a cell-update message to the RNC for the Target Macro NB, which cell-update message includes the u-RNTI assigned to UE by Source HNB (STEP 904).
  • Macro RNC routes the Cell-Update message via the lur interface to the HNB-GW identified by the RNC-ID forming part of the u-RNTI included in the cell-update message (STEP 908).
  • Macro RNC also sends to HNB-GW an indication of the identity of the macro cell that is the target cell.
  • HNB-GW determines the identity of the Source HNB by referring to the part of the mapping table it maintains including mapping of s-RNTI prefixes to HNB identities for the macro cell identified as the target cell in the information received from Macro RNC (STEP 910).
  • HNB-GW 14 forwards the cell-update message to the Source HNB (STEP 912). This triggers a SRNS Relocation procedure by which the PDP context is transferred from Source HNB to the macro-RNC for the target cell (STEP 914).
  • Macro-RNC sends a cell-update-confirm message to UE including the new u-RNTI assigned to it by macro-RNC (STEP 916).
  • the above-described operations may require data processing in the various entities.
  • the data processing may be provided by means of one or more data processors.
  • various entities described in the above embodiments may be implemented within a single or a plurality of data processing entities and/or data processors.
  • Appropriately adapted computer program code product may be used for implementing the embodiments, when loaded to a computer.
  • the program code product for providing the operation may be stored on and provided by means of a carrier medium such as a carrier disc, card or tape. A possibility is to download the program code product via a data network. Implementation may be provided with appropriate software in a server.
  • the embodiments of the invention may be implemented as a chipset, in other words a series of integrated circuits communicating among each other.
  • the chipset may comprise microprocessors arranged to run code, application specific integrated circuits (ASICs), or programmable digital signal processors for performing the operations described above.
  • ASICs application specific integrated circuits
  • programmable digital signal processors for performing the operations described above.
  • Embodiments of the invention may be practiced in various components such as integrated circuit modules.
  • the design of integrated circuits is by and large a highly automated process.

Landscapes

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

Claims (11)

  1. Procédé comprenant :
    la réception, au niveau d'une entité passerelle (14), d'informations de cellules voisines spécifiant une ou plusieurs cellules comme cellules voisines pour une première cellule (6) d'une pluralité de cellules (6) associées à l'entité passerelle (14); et
    la sélection, au niveau de l'entité passerelle (14), sur la base desdites informations de cellules voisines, d'un identifiant pour ladite première cellule (6) qui distingue ladite première cellule (6) de toute autre cellule (6) de ladite pluralité de cellules (6) associées à ladite entité passerelle (14) qui spécifie une ou plusieurs cellules (6) voisines en commun avec ladite première cellule (6).
  2. Procédé selon la revendication 1 comprenant :
    la réception, au niveau de l'entité passerelle (14), en relation avec un changement de cellule vers une cellule cible (6) à partir de la première cellule (6), d'un message comportant (i) un identifiant pour ladite cellule cible (6), et (ii) l'identifiant sélectionné pour ladite première cellule (6) ; et
    la détermination, au niveau de l'entité passerelle (14), de l'identité de ladite première cellule (6) à partir dudit identifiant pour ladite cellule cible (6) et dudit identifiant pour ladite première cellule (6).
  3. Procédé selon la revendication 2, dans lequel ladite détermination comprend :
    la référence, au niveau de l'entité passerelle (14), à une table de mappage qui mappe (a) les identités respectives de cellules (6) associées à ladite entité passerelle à (b) des identifiants attribués à des cellules (6) associées à ladite entité passerelle (14), pour chacune d'une pluralité de cellules (6) spécifiées comme cellules (6) voisines par des cellules (6) associées à ladite entité passerelle (14).
  4. Procédé comprenant :
    l'envoi, par une première cellule (6) à une entité passerelle (14), d'une demande d'enregistrement de la première cellule, dans lequel ladite demande comporte des informations de cellules voisines pour ladite première cellule (6) ; et
    la réception, par la première cellule (6) de ladite entité passerelle (14), d'un identifiant pour ladite première cellule (6) sur la base desdites informations de cellules voisines qui distingue ladite première cellule (6) de toute autre cellule (6) d'une pluralité de cellules (6) associées à ladite entité passerelle (14) qui spécifie une ou plusieurs cellules (6) voisines en commun avec ladite première cellule (6).
  5. Procédé selon la revendication 4, comprenant en outre :
    la communication, par la première cellule (6) à un dispositif de communication (8) demandant une connexion à ladite première cellule (6), d'un identifiant pour ledit dispositif de communication (8) ; lequel identifiant comporte : (i) ledit identifiant pour ladite première cellule (6), et (ii) un identifiant sélectionné par ladite première cellule (6) pour ledit dispositif de communication (8) et qui distingue ledit dispositif de communication (8) de tout autre dispositif de communication (8) desservi par ladite première cellule (6).
  6. Appareil comprenant : un processeur et une mémoire comportant un code de programme informatique, dans lequel la mémoire et le code de programme informatique sont configurés pour, avec le processeur, amener l'appareil à :
    recevoir, au niveau d'une entité passerelle (14), des informations de cellules voisines spécifiant une ou plusieurs cellules (6) comme cellules (6) voisines pour une première cellule (6) d'une pluralité de cellules (6) associées à l'entité passerelle (14) ; et
    sélectionner, au niveau de l'entité passerelle (14), sur la base desdites informations de cellules voisines, un identifiant pour ladite première cellule (6) qui distingue ladite première cellule (6) de toute autre cellule (6) de ladite pluralité de cellules (6) associées à ladite entité passerelle (14) qui spécifie une ou plusieurs cellules (6) voisines en commun avec ladite première cellule (6).
  7. Appareil selon la revendication 6, comprenant : un processeur et une mémoire comportant un code de programme informatique, dans lequel la mémoire et le code de programme informatique sont configurés pour, avec le processeur, amener l'appareil à :
    recevoir, au niveau de l'entité passerelle (14), en relation avec un changement de cellule vers une cellule cible (6) à partir de la première cellule (6), un message comportant (i) un identifiant pour ladite cellule cible (6), et (ii) un identifiant sélectionné pour ladite première cellule (6) ; et
    déterminer, au niveau de l'entité passerelle (14), l'identité de ladite première cellule (6) à partir dudit identifiant pour ladite cellule cible (6) et dudit identifiant pour ladite première cellule (6).
  8. Appareil selon la revendication 7, dans lequel la mémoire et le code de programme informatique sont en outre configurés pour, avec le processeur, amener l'appareil à :
    se référer, au niveau de l'entité passerelle (14), à une table de mappage qui mappe (a) les identités respectives de cellules (6) associées à ladite entité passerelle (14) à (b) des identifiants attribués à des cellules (6) associées à ladite entité passerelle (14), pour chacune d'une pluralité de cellules (6) spécifiées comme cellules (6) voisines par des cellules (6) associées à ladite entité passerelle (14).
  9. Réseau comprenant une première cellule (6) et une entité passerelle (14), la première cellule (6) comprenant : un processeur et une mémoire comportant un code de programme informatique, dans lequel la mémoire et le code de programme informatique sont configurés pour, avec le processeur, amener la première cellule (6) à :
    envoyer à l'entité passerelle (14) une demande d'enregistrement de la première cellule (6), dans lequel ladite demande comporte des informations de cellules voisines pour ladite première cellule (6) ; et
    recevoir de ladite entité passerelle (14) un identifiant pour ladite première cellule (6) sur la base desdites informations de cellules voisines qui distingue ladite première cellule (6) de toute autre cellule (6) d'une pluralité de cellules (6) associées à ladite entité passerelle (14) qui spécifie une ou plusieurs cellules (6) voisines en commun avec ladite première cellule (6).
  10. Réseau selon la revendication 9, dans lequel la mémoire et le code de programme informatique sont en outre configurés pour, avec le processeur, amener la première cellule (6) à :
    communiquer à un dispositif de communication (8) demandant une connexion à ladite première cellule (6), un identifiant pour ledit dispositif de communication (8) ; lequel identifiant comporte : (i) ledit identifiant pour ladite première cellule (6), et (ii) un identifiant sélectionné par ladite première cellule (6) pour ledit dispositif de communication (8) et qui distingue ledit dispositif de communication (8) de tout autre dispositif de communication (8) desservi par ladite première cellule (6).
  11. Produit de programme informatique comprenant des moyens de code de programme qui, lorsqu'ils sont chargés dans un ordinateur, commandent l'ordinateur pour réaliser un procédé selon l'une des revendications 1 à 5.
EP13701443.7A 2012-01-30 2013-01-25 Attribution d'identificateurs aux home node bs Active EP2810470B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN349CH2012 2012-01-30
PCT/EP2013/051421 WO2013113623A1 (fr) 2012-01-30 2013-01-25 Attribution d'identificateurs pour des nœuds b domestiques

Publications (2)

Publication Number Publication Date
EP2810470A1 EP2810470A1 (fr) 2014-12-10
EP2810470B1 true EP2810470B1 (fr) 2023-10-18

Family

ID=47605535

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13701443.7A Active EP2810470B1 (fr) 2012-01-30 2013-01-25 Attribution d'identificateurs aux home node bs

Country Status (3)

Country Link
US (1) US9467874B2 (fr)
EP (1) EP2810470B1 (fr)
WO (1) WO2013113623A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10057838B2 (en) * 2013-04-26 2018-08-21 Qualcomm Incorporated X2 setup and routing at an X2-gateway
GB2514806A (en) * 2013-06-04 2014-12-10 Nec Corp Communications system
US20150201411A1 (en) * 2014-01-10 2015-07-16 Qualcomm Incorporated Handling invalid configurations for enhanced uplink in cell_fach state
JP6347289B2 (ja) * 2014-10-02 2018-06-27 富士通株式会社 中継装置および基地局システム
CN107453998B (zh) * 2016-05-31 2020-02-14 华为技术有限公司 传输报文的方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2135473B1 (fr) * 2007-04-11 2020-12-23 Optis Wireless Technology, LLC Informations sur une structure de signaux de référence pour l'obtention de mesures relatives à des cellules voisines
EP2079258B1 (fr) 2008-01-11 2015-09-02 Alcatel-Lucent USA Inc. Affectation automatique de codes régionaux pour le déploiement femtocell
JPWO2010098035A1 (ja) * 2009-02-24 2012-08-30 パナソニック株式会社 端末装置、ホーム基地局およびホーム基地局交換装置
GB2482071B (en) 2009-08-11 2012-07-04 Ubiquisys Ltd Scrambling code selection
WO2011023234A1 (fr) 2009-08-27 2011-03-03 Nokia Siemens Networks Oy Procédé et appareil pour exploitation d'un réseau de communication

Also Published As

Publication number Publication date
EP2810470A1 (fr) 2014-12-10
US20150017925A1 (en) 2015-01-15
US9467874B2 (en) 2016-10-11
WO2013113623A1 (fr) 2013-08-08

Similar Documents

Publication Publication Date Title
RU2425466C2 (ru) Обнаружение соседних сот
EP2375807B1 (fr) Procédé de traitement de transfert, passerelle pour station de base locale et système de réseau
TWI495290B (zh) 無線電涵蓋蜂巢式單元識別符的碰撞偵測
US8265028B2 (en) Distributed allocation of physical cell identifiers
CN107432047B (zh) 在基站之间建立连接的方法、存储介质、基站和cpe
US8768364B2 (en) Femto cell system and method of achieving mobility with macro/micro cell in femto cell system
US9001789B2 (en) Communication system, identifier assignment device, base station, identifier assignment method, and non-transitory computer readable medium embodying instructions for controlling a device
EP2244503A1 (fr) Contrôle de transfert
US20130225168A1 (en) Method and apparatus for base station identification discovery in wireless communications
KR20130065902A (ko) 이동 통신 시스템 및 그 이동 통신 시스템에서 기지국 식별자 관리 방법
EP2810470B1 (fr) Attribution d'identificateurs aux home node bs
JP4678030B2 (ja) 通信システム及び情報管理方法
EP2625885A1 (fr) N uds relais
US10623948B2 (en) Communication system
US8655360B2 (en) Method and system of allocating network temporary identities
CN101572876B (zh) 标识信息的分配、获取方法及装置
CN106358270A (zh) 专用核心网的选择方法和装置
US8364152B2 (en) Macrocell to Femtocell and Femtocell to Femtocell handoff
CN107925923B (zh) 服务小区管理
US9813902B2 (en) Method of management in a communications network
KR101845914B1 (ko) 위치 측위 방법과 그를 위한 시스템 및 장치
US10028273B2 (en) Method for interference coordination, network server and communication system using the same
WO2013045698A1 (fr) Cellules localisées
KR101524600B1 (ko) 중첩 네트워크에서 셀 결정 방법 및 그를 수행하는 시스템
CN105873104B (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

17P Request for examination filed

Effective date: 20140901

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

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20181130

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

Owner name: NOKIA SOLUTIONS AND NETWORKS OY

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20221115

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTC Intention to grant announced (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230508

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

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

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20231018

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1623570

Country of ref document: AT

Kind code of ref document: T

Effective date: 20231018

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013084807

Country of ref document: DE

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

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

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

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

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

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

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

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

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

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

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

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231018

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Ref country code: LU

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

Effective date: 20240125

26N No opposition filed

Effective date: 20240719

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

Ref country code: LU

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

Effective date: 20240125

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

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

Ref country code: CH

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

Effective date: 20240131

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

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

Ref country code: CH

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

Effective date: 20240131

Ref country code: BE

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

Effective date: 20240131

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20240131

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

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

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

Effective date: 20130125

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

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

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

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

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

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

Ref country code: GB

Payment date: 20251204

Year of fee payment: 14

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

Ref country code: FR

Payment date: 20251208

Year of fee payment: 14

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

Ref country code: DE

Payment date: 20251203

Year of fee payment: 14