EP2382826B1 - Procédé et agencement dans un réseau de communication - Google Patents

Procédé et agencement dans un réseau de communication Download PDF

Info

Publication number
EP2382826B1
EP2382826B1 EP09838968.7A EP09838968A EP2382826B1 EP 2382826 B1 EP2382826 B1 EP 2382826B1 EP 09838968 A EP09838968 A EP 09838968A EP 2382826 B1 EP2382826 B1 EP 2382826B1
Authority
EP
European Patent Office
Prior art keywords
subscriber group
target
cell
mobile node
control node
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
EP09838968.7A
Other languages
German (de)
English (en)
Other versions
EP2382826A4 (fr
EP2382826A1 (fr
Inventor
Johan Rune
Jari Vikberg
Tomas Nylander
Arne Norefors
Thomas Lindqvist
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP2382826A1 publication Critical patent/EP2382826A1/fr
Publication of EP2382826A4 publication Critical patent/EP2382826A4/fr
Application granted granted Critical
Publication of EP2382826B1 publication Critical patent/EP2382826B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/082—Access security using revocation of authorisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/088—Access security using filters or firewalls
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • 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 present invention relates to a method and arrangement in a network control node and to a method and arrangement in a target control node.
  • it relates to a mechanism for improving the access control of a mobile node in a handover from a source cell, into a target cell.
  • UMTS Universal Mobile Telecommunications Systems
  • SAE/LTE System Architecture Evolution/ Long Term Evolution
  • EPC/E-UTRAN Evolved Packet Core/ Evolved Universal Terrestrial Radio Access Network
  • EPS Evolved Packet System
  • GSM GSM EDGE Radio Access Network
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • a home base station In 3G radio access (UTRAN) a home base station is referred to as a Home Node B (HNB) whereas in EPC/E-UTRAN it is referred to as a Home eNodeB (HeNB).
  • HNB Home Node B
  • HeNB Home eNodeB
  • a cell served by a HNB or a HeNB is commonly referred to as a femtocell.
  • a home base station is assumed to be placed in a private home, utilizing the home owner's fixed broadband connection to access the core network. Other possible deployments are in a campus, shopping mall, company etc. It is also assumed that the home owner handles the actual physical installation of the home base station. Hence, the deployment of home base stations cannot be planned, since it is largely outside the control of the operator. Another important property of the home base station concept is the potentially large number of home base stations.
  • a HeNB/HNB provides normal service for the end users and is connected to the mobile core network using Internet Protocol (IP) based transmission, typically the HeNB/HNB owner's broadband access and the Internet.
  • IP Internet Protocol
  • the radio coverage provided may be referred to as a femtocell.
  • a femtocell covers the HeNB/HNB owner's home.
  • One of the main drivers of this concept of providing local access is to provide cheaper call or transaction rates/charges when connected via the HeNB/HNB than when connected via a eNodeB, i.e. an E-UTRAN base station; or a NodeB i.e. a UTRAN 3G WCDMA/HSPA base station.
  • Another driver is reducing the load on the operator's eNodeBs/ NodeBs and backhaul connections, thereby reducing the operator's Capital Expenditures (CAPEX) and Operational Expenditures (OPEX).
  • HN Home Node
  • a HN may connect to the operator's network via a secure tunnel, supposedly IPsec protected, to a security gateway at the border of the operator's network. Via this tunnel, said HN node connects to the core network nodes of the operator's core network, such as e.g. Mobility Management Entity (MME) and Serving Gateway (S-GW) via the S1 interface or Serving General Packet Radio Service (GPRS) Support Node (SGSN) and Mobile Switching Centre (MSC), or Media Gateway (MGW) and MSC server via the lu interface.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • GPRS General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • MSC Mobile Switching Centre
  • MSC Media Gateway
  • lu is the interface between the radio access network and the core network in 3G UMTS, i.e. between Radio Network Controller (RNC), or a HNB via a HNB Gateway, and SGSN/ MSC/ MSC server/ MGW, depending on the access technology used.
  • RNC Radio Network Controller
  • the 3rd Generation Partnership Project (3GPP) operator may also deploy a concentrator node in its network between the 3G/UTRAN Home NodeBs or, EPC/E-UTRAN Home eNodeBs and the regular core network nodes.
  • a concentrator node is commonly referred to as a HeNB Gateway, which may be an optional node in HeNB solutions.
  • the corresponding node name in 3G UMTS standardization is HNB Gateway and this node is mandatory in 3G HNB systems.
  • IPsec Internet Protocol Security
  • SEGW Security GateWay
  • a mobile node which also may be referred to as e.g. a User Equipment (UE), communicates via the HN and the core network like any other mobile node.
  • UE User Equipment
  • the Operation and Maintenance (O&M) system directs the HN to connect to a suitable core network node or pool of core network nodes, via a concentrator node, i.e. a HeNB connects to an MME pool, probably via a HeNB Gateway, and a HNB connects to an SGSN and possibly an MSC or MSC server, or pools of such nodes, via a HNB Gateway.
  • a concentrator node i.e. a HeNB connects to an MME pool, probably via a HeNB Gateway
  • a HNB connects to an SGSN and possibly an MSC or MSC server, or pools of such nodes, via a HNB Gateway.
  • the suitable core network node or pool of core network nodes that the O&M system selects is the core network node, or pool of core network nodes which serves the macro layer base stations whose cells cover the location where the HN is located.
  • core network node or pool of core network nodes
  • inter-core network node handovers e.g. inter MME pool handover or inter-SGSN/ pool handover
  • idle mode mobility i.e. when a mobile node moves in idle mode between a macro layer base station and the HN or vice versa.
  • HLR Home Location Register
  • HSS Home Subscriber Server
  • the HN concept is closely related to the concept of subscriber groups such as e.g. Closed Subscriber Group (CSG).
  • CSG Closed Subscriber Group
  • a femtocell may also be assumed to be a subscriber group cell such as e.g. a CSG cell. This means that only a selected group of subscribers are allowed to access the network through that cell.
  • a Boolean type CSG indication is included to inform mobile stations that the cell is a CSG cell.
  • the subscriber group e.g. CSG of a subscriber group cell e.g. CSG cell is identified by a subscriber group identifier e.g. CSG ID, which may also be broadcasted in the cell as a part of the system information.
  • each subscriber group cell e.g. CSG cell
  • has its own unique subscriber group identifier such as e.g. CSG ID
  • subscriber group identifier e.g. CSG ID
  • a subscriber group cell e.g. a CSG cell does not, in principle, have to be a femtocell, but may be also any other type of cell.
  • CSG data CSG definition
  • HN access list HN access list
  • ISDN numbers Integrated Services Digital Network numbers
  • MSISDN number Mobile Subscriber ISDN number
  • IMSI International Mobile Subscriber Identities
  • the CSG data, or HN access list, is reflected in the so-called Allowed CSG Lists (ACL), also known as CSG Whitelists, associated with the concerned mobile nodes.
  • ACL also known as CSG Whitelists
  • Each mobile node has an Allowed CSG List, which includes the CSG ID of each CSG the mobile node, or more precisely the subscriber using the mobile node is included in, i.e. the CSG ID of each femtocell the mobile node or actually the subscriber is allowed to access.
  • a CSG is actually associated with a group of subscribers rather than mobile nodes, but for simplicity the term mobile node may be used as the entity of which a CSG is formed.
  • a CSG Whitelist may actually be associated with a subscriber rather than with a mobile node, but for simplicity the mobile node in this context may be used as a "proxy" for the subscriber using it, such that a CSG Whitelist may be referred to as belonging to the mobile node and the mobile node may be said to be allowed or not allowed access to a CSG cell.
  • the ACL of a subscriber may be stored in a database e.g. the HSS of the subscriber's home network together with other subscriber data, but another database than the HSS may eventually be chosen for this task.
  • the data is transferred from the OMA&P system, where the CSG data resides, to the HSS, where it is distributed to appropriate subscriber records. This applies to both creation and updates, i.e. additions or exclusions of subscribers of the CSG data. It is also possible for the OMA&P system to maintain its own copies of the ACLs or to assemble them from the CSG data when needed.
  • the ACL of a subscriber may also be stored in the mobile node of the subscriber, e.g.
  • the ACL may be transferred from the network to the mobile node for example via Open Mobile Alliance Device Management (OMA DM), or Over-The-Air (OTA) USIM configuration technology, or Short Message Service (SMS) or implicitly via NAS signalling.
  • OMA DM Open Mobile Alliance Device Management
  • OTA Over-The-Air
  • SMS Short Message Service
  • NAS NAS signalling
  • the ACL of a mobile node may be downloaded from the HSS to the MME serving the mobile node, assumedly together with other subscriber data which is relevant for the serving MME, so that the MME may perform CSG based access control of mobile nodes requesting network access via a CSG cell, e.g.
  • Attach Request a Tracking Area Update (TAU) Request or a Service Request.
  • This mechanism is likely to be similar in 3G, utilizing a node corresponding to the MME, i.e. the SGSN and/or the MSC server, performing CSG based access control on the corresponding 3G procedures.
  • the search for allowed CSG cells is not governed by the network, but is left to the mobile node to handle autonomously.
  • the mobile node To identify an allowed CSG cell the mobile node must read the CSG ID from the system information broadcast in the cell and compare it with the CSG ID/s stored in ACL. When a match is found, the mobile node has discovered an allowed CSG cell.
  • the source (H)eNodeB, or source Radio Network Subsystem (RNS) or source HNB in 3G or source Base Station Subsystem (BSS) in 2G rely to a greater extent on the mobile node than during other handovers, because the neighbour relations are not maintained towards CSG cells in the same way as towards regular macrocells. Hence it is up to the mobile node to detect and report the presence of a CSG cell which may be a suitable target cell for handover.
  • all handovers into a CSG cell are signalled via the core network e.g. S1 handover in EPC/E-UTRAN.
  • CSG based access control has to be performed, just as when a mobile node performs TAU, LAU or RAU or sends a service request in a CSG cell.
  • the only CSG based access control defined in the network i.e. excluding the mobile node's own filtering of allowed and not allowed CSG cells, based on its internal ACL is the access control the serving MME or SGSN or MSC/MSC server performs when a mobile node accesses a CSG cell, e.g. Attach Request, Tracking Area Update (TAU)/ Location Area Update (LAU)/ Routing Area Update (RAU) Request or Service Request.
  • TAU Tracking Area Update
  • LAU Location Area Update
  • RAU Routing Area Update
  • the regular CSG based access control will not be triggered until the mobile node performs a location registration, i.e. TAU in EPC/E-UTRAN, RAU/LAU in 3G, after the handover is concluded.
  • TAU in EPC/E-UTRAN
  • RAU/LAU in 3G
  • a location registration e.g. TAU may not be triggered in all cases.
  • the handover is handled via a single Core Network Control Node (CNN), such as e.g. MME, and the mobile node, after moving to the target CSG cell, remains in a registration area e.g. Tracking Area or Routing Area, which does not trigger a location registration, there will be no location registration.
  • CNN Core Network Control Node
  • an illegitimate mobile node could access a non-allowed CSG cell via handover.
  • the intelligent femtocell deployment strategy aims at avoiding Inter Core Network Control Node Handovers, such as e.g. inter-MME handovers this may be a most likely case.
  • the known CSG based access control in the serving Core Network Control Node such as e.g. MME, may thus not be triggered in a handover scenario, under some circumstances.
  • a malicious mobile node aiming at getting access through a non-allowed CSG cell may simply omit the trailing location registration, even though the circumstances would normally trigger it, in order to avoid the CSG based access control.
  • 3GPP contribution R2-082238 discusses 3 options for access control of a UE entering a CSG cell upon handover.
  • 3GPP contribution S2-090129 discusses a solution for Access control for in-bound mobility to HeNBs, wherein a source eNB checks if the CSG ID of a target cell is on the Allowed CSG list for the UE.
  • This object is achieved by a method in a Mobility Management Entity, according to claim 1, a Mobility Management Entity according to claim 6, a method in a target eNB according to claim 9, and a target eNB according to claim 12. Thanks to the present methods and arrangements, it is possible to prevent illegitimate mobile nodes from accessing a target node with restricted access early in a handover process. Thus it is possible to limit the consumed network resources when the mobile node is performing a handover from a source cell to a target cell. In particular, illegitimate mobile nodes are stopped before any radio resources are allocated in the target CSG cell. Thereby the probability of inappropriate network resource allocation is reduced and also some network signalling may be omitted. Thus an improved performance within a communication network is provided.
  • the present solution is defined as a method and an arrangement in a network control node and a method and an arrangement in a target network control node which may be put into practice in the embodiments described below.
  • the present solution may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present solution. It should be understood that there is no intent to limit the present methods and/or arrangements to any of the particular forms disclosed, but on the contrary, the present methods and/or arrangements are to cover all modifications, equivalents, and alternatives falling within the scope of the present solution as defined by the claims.
  • FIG. 1 is a schematic illustration over a communication network 100.
  • a mobile node 110 is moving from a source cell 121, which source cell 121 is associated with a network control node 120, such as a source network control node, into a target subscriber group cell 152.
  • the target subscriber group cell 152 is associated with a target network control node 150.
  • the network control node 120 is connected to a network control node 130, such as a core network control node (CNN) e.g. via a wired connection.
  • the target network control node 150 is connected to a target core network control node 140, such as a core network control node (CNN) e.g. via a wired connection.
  • CNN core network control node
  • the network control node 130 and the target core network control node 140 are connected e.g. via a wired connection according to some embodiments. However, according to some embodiments, the network control node 130 and the target core network control node 140 may be collocated within the same core network control node 130. Further yet, the network control node 130 is connected to a database 160.
  • the mobile node 110 may, according to some embodiments be represented by a wireless communication device, a wireless communication terminal, a mobile cellular telephone, a Personal Communications Systems terminal, a Personal Digital Assistant (PDA), a laptop, a User Equipment (UE), computer or any other kind of device capable of managing radio resources.
  • a wireless communication device a wireless communication terminal
  • a mobile cellular telephone a personal Communications Systems terminal
  • PDA Personal Digital Assistant
  • UE User Equipment
  • the network control node 120 may according to some embodiments be referred to as a source control node, a Radio Access Network (RAN), a Radio Access Network Subsystem (RANS), or a HRANS.
  • a HRANS is a RANS where the concerned base station is a Home (e)NodeB, i.e. either Home Node B or Home eNodeB. Possibly also comprising the Home (e)NodeB Gateway via which the Home (e)NodeB may be connected to the core network.
  • the network control node 120 may be a source eNodeB or a source Home eNodeB in EPS, a source radio network subsystem i.e.
  • source network control node 120 will be used, for enhanced clarity, but it is to be considered to correspond to any of the enumerated terms such as e.g. network control node 120.
  • the source cell 121 may be a CSG cell, a femtocell, a regular macrocell, or any other arbitrary kind of cell.
  • the network control node 130 which also may be referred to as core network control node (CNN), as well as the target core network control node 140 may be a Mobility Management Entity (MME) in EPC/ E-UTRAN.
  • MME Mobility Management Entity
  • the source core network control node 130 and/or target core network control node 140 may be an SGSN or possibly a MSC/MSC server.
  • the term core network control node 130 will be used, for enhanced clarity, but it is to be considered to correspond to any of the enumerated terms such as e.g. network control node 130.
  • the target network control node 150 may according to some embodiments be referred to as a Radio Access Network (RAN), a Radio Access Network Subsystem (RANS), or a HRANS.
  • a HRANS is a RANS where the concerned base station is a Home (e)NodeB, i.e. either Home Node B or Home eNodeB. Possibly also comprising the Home (e)NodeB Gateway via which the Home (e)NodeB may be connected to the core network.
  • the target base station subsystem in 2G may comprise a base station controller and its connected radio base stations.
  • the target network control node 150 may be represented by a Gateway (GW), such as e.g. a Home eNodeB Gateway.
  • GW Gateway
  • the target subscriber group cell 152 may be a CSG cell, a femtocell, a regular macrocell with access restrictions, or any other arbitrary kind of cell with limited access. However, in the following illustrative exemplary embodiment, the target subscriber group cell 152 is embodied as a CSG cell.
  • the database 160 may be a Home Subscriber Server (HSS), or any other arbitrary database arranged to store data related to a subscriber.
  • HSS Home Subscriber Server
  • ACL network based Allowed CSG List
  • white list access control list
  • network based allowed subscriber group list may be stored at the database 160.
  • a target subscriber group identification may be comprised in the network based allowed subscriber group list associated with the mobile node 110.
  • the network based allowed subscriber group list such as e.g. an Allowed CSG List (ACL)
  • ACL Allowed CSG List
  • the network based allowed subscriber group list may comprise a list of target subscriber group identification, associated with, or identifying, target subscriber group cells 152 that the mobile node 110 may be granted access to.
  • an optional time limit associated with the certain subscriber and/or mobile node 110, having a time limited access to the subscriber group cell 152 may be comprised within the network based allowed subscriber group list.
  • the Allowed CSG List may exist in several places within the communication network 100.
  • the database 160 such as e.g. a HSS, may have a complete ACL list for one subscriber.
  • the identification of subscribers in the database 160 may be made e.g. in the form of International Mobile Subscriber Identity (IMSI) code.
  • IMSI International Mobile Subscriber Identity
  • This ACL list may comprise for each Public Land Mobile Network (PLMN) the allowed CSG IDs, which may be limited to e.g. 50 per PLMN, and their corresponding optional expiration timer.
  • PLMN Public Land Mobile Network
  • each subscriber may have one ACL for each PLMN, however it may be assumed that the CSG IDs of all PLMNs are comprised in the same ACL, i.e.
  • the database 160 may send the ACL list as part of subscription data to MSC/SGSN/MME, but it may only send the part of the data that is applicable to this PLMN. Therefore it may be that the list in MME/SGSN/MSC is a part of the full ACL list, or the full ACL list if the user only has CSG Id in one PLMN, which may be assumed to be a common case.
  • MSISDN may be one of the parameters, but the main usage in MME or SGSN may be to add the MSISDN in certain messages on certain interfaces.
  • the mobile node 110 may be assumed to get a complete ACL list from a server in the Home Public Land Mobile Network (HPLMN), and this server may in turn get the list from the database 160, according to some embodiments. However, it may be that e.g. the ACL list may be configured into the mobile node 110 such that the subscriber for example is a H(e)NB owner that only needs to access its own CSG Id.
  • HPLMN Home Public Land Mobile Network
  • the H(e)NB owner may according to some embodiments allow a friend to access its H(e)NB CSG Id, e.g. for a limited period of time.
  • the H(e)NB owner may e.g. access a portal in the HPLMN, to add identities of all mobile nodes, or rather subscribers using the mobile nodes, that may be allowed to access his/her H(e)NBs CSG Id.
  • a portal in the HPLMN
  • the portal may be configured to translate the MSISDN into an IMSI to be able to add this into the database 160 in some way.
  • the communication system 100 may be based on technologies such as e.g. System Architecture Evolution/ Long Term Evolution (SAE/LTE), Evolved Packet Core/ Evolved Universal Terrestrial Radio Access Network (EPC/E-UTRAN), Evolved Packet System (EPS), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), CDMA 2000, High Speed Downlink Packet Data Access (HSDPA), High Speed Uplink Packet Data Access (HSUPA), High Data Rate (HDR) High Speed Packet Data Access (HSPA), Universal Mobile Telecommunications System (UMTS) etc, just to mention some few arbitrary and none limiting examples.
  • SAE/LTE System Architecture Evolution/ Long Term Evolution
  • EPC/E-UTRAN Evolved Packet Core/ Evolved Universal Terrestrial Radio Access Network
  • EPS Evolved Packet System
  • Any, some or all nodes comprised within the communication system 100 may be connected together with communication links for operating and maintenance purpose.
  • the present inventive concept is to introduce access control mechanisms to be used at handover into a target subscriber group cell 152, which are based on checking that the target subscriber group identification of the target subscriber group cell 152 is comprised in the mobile node's 110 network based allowed subscriber group list.
  • the allowed subscriber group list actually pertains to a subscriber rather than the mobile node 160, but the allowed subscriber group list may also be stored in the mobile node 160 the subscriber is using and for simplicity it may be more convenient to refer to the allowed subscriber group list as pertaining to the mobile node 160, as a sort of proxy for the subscriber using the mobile node 160.
  • the network based allowed subscriber group list is provided by the database 160 to the core network control node 130.
  • the core network control node 130 may be e.g. an MME in EPC/E-UTRAN.
  • the target subscriber group identification of the target subscriber group cell 152 is provided either by the mobile node 110 or by the target network control node 150, which is adapted to control the target subscriber group cell 152.
  • the target network control node 150 may be e.g. a HeNB in EPC/E-UTRAN, according to some embodiments.
  • the actual check may be performed by the source core network control node 130.
  • the source core network control node 130 may be e.g. an MME, an MSC or an SGSN, just to mention some possible options, according to some embodiments.
  • the actual check may be performed by the source network control node 120 according to some embodiments.
  • the source network control node 120 may be e.g. an eNB or an RNC. If this access control is based on a target cell target subscriber group identification provided by the mobile node 110, then the target network control node 150 controlling the target subscriber group cell 152 may verify that the target subscriber group identification provided by the mobile node 110 actually matches the target subscriber group identification of the target subscriber group cell 152 before the mobile node 110 can be granted access to the target subscriber group cell 152, so that the handover can be concluded.
  • the mobile node 110 can prune the set of candidate target subscriber group cells 152 by checking that the target subscriber group identification of the candidate target subscriber group cell 152 is included in the mobile node 110 based allowed subscriber group list before reporting the target subscriber group cell 152 as a candidate target cell.
  • Cases that may be relevant to consider for the present solution comprises both handover from a source cell 121 to a target subscriber group cell 152 based on the same Radio Access Technology (intra-RAT handover) as well as handover between cells 121, 152 based on different Radio Access Technologies (inter-RAT handover).
  • the source cell 121 may be, according to some embodiments, a subscriber group cell such as e.g. a CSG cell.
  • the intra-RAT handover cases may comprise e.g. intra-LTE and intra-3G handovers.
  • the inter-RAT handover cases may comprise handover from 2G to 3G, e.g. from GERAN to UTRAN.
  • Another inter-RAT handover case may be from 3G to EPC/E-UTRAN, e.g. from UTRAN to E-UTRAN.
  • Yet an example of an inter-RAT handover case may be from EPC/E-UTRAN to 3G, e.g. from E-UTRAN to UTRAN.
  • the presently described methods may also be applied for e.g. a handover from 2G to EPC/E-UTRAN.
  • Figure 2 is a schematic illustration over the communication network 100 and illustrates generic signalling for inter-core network control node handover cases. If the Core Network pool concept is used, it is assumed that the source core network control node 130 and target core network control node 140 belong to different pools.
  • Figure 3 is a schematic illustration over the communication network 100 and illustrates generic signalling for intra-core network control node handover cases.
  • the mobile node 110 reports measurements and identity/identities of neighbouring candidate target subscriber group cells 152 for handover.
  • the candidate target subscriber group cell 152 may be e.g. a CSG cell. This may be a Radio Resource Control message (RRC message) such as e.g. a MeasurementReport in E-UTRAN.
  • RRC message Radio Resource Control message
  • Message 2-4 may comprise signals involving handover preparation.
  • 2 HANDOVER REQUIRED, which may be a S1 Application Protocol (S1AP) message
  • 3 Forward Relocation Request which may be a GPRS Tunnelling Protocol (GTP) message
  • 4 HANDOVER REQUEST, which may be a S1AP message.
  • S1 is the interface between the radio access network and the core network in EPS, i.e. between eNodeB and MME/ Serving Gateway.
  • Command to execute handover may be e.g. RRCConnectionReconfiguration, which may be a RRC message, in E-UTRAN.
  • Data may be transferred from the source network control node 120 to the target network control node 150 via signalling messages 2-4, e.g. in a S-to-T container according to some embodiments. This data may not be interpreted by the source core network control node 130 and/or the target core network control node 140.
  • Data may be transferred from the target network control node 150 to the source network control node 120 via signalling messages 5-7, e.g. in a T-to-S container according to some embodiments. This data may not be interpreted by the source core network control node 130 and/or the target core network control node 140.
  • the present solution may be applicable both to intra-RAT and inter-RAT cases. Furthermore, the present solution may be applied in communication network 100 wherein all involved entities support the CSG concept and/or wherein the source network control node 120 does not support the CSG concept, according to some embodiments. However, according to some embodiments core network control node 130 may not support the CSG concept.
  • step A-C the present access control mechanism at handover into a cell may comprise three steps, step A-C:
  • the mobile node 110 may report target cell 152 and target subscriber group identification, such as e.g. the CSG ID of the target cell 152 to the source network control node 120 only if the target subscriber group identification is included in the mobile node 110 based allowed subscriber group list, which may also be referred to as an Allowed CSG List (ACL), or a CSG Whitelist, or just Whitelist.
  • ACL Allowed CSG List
  • the mobile node 110 may report an empty/void target subscriber group identification parameter to the source network control node 120. If the mobile node 110 does not support the CSG concept, it may not report any target subscriber group identification parameter at all. This step is optional, e.g. as all mobile nodes 110 may support the CSG concept.
  • the database 160 may be a Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the handover may be admitted if the target subscriber group identification is comprised in the mobile node node's network based allowed subscriber group list, according to some embodiments.
  • the target network control node 150 checks that the target subscriber group identification reported by the mobile node 110 matches the subscriber group identification of the actual target cell 152, e.g. as identified by the reported cell ID. If the target subscriber group identification reported by the mobile node 110 does not match the subscriber group identification of the target cell 152, access grant may not be given and thus the handover process may be discontinued. Note that an empty/void target subscriber group identification parameter implies a non-CSG target cell 152 and may thus not match any subscriber group identification at all. Thus the check may fail if the target cell 152 is a CSG cell. This step C may be performed only if step B is based on a target subscriber group identification reported by the mobile node 110, according to some embodiments.
  • Step A may thus be optional and step C may be conditional, according to some embodiments.
  • the order of step B and step C may be reversed.
  • the mobile node 110 If the mobile node 110 supports the CSG concept, it reports a target subscriber group identification parameter, i.e. a parameter intended to comprise the subscriber group identification of a handover candidate target cell 152 to the source network control node 120 in a measurement report. If the candidate target cell 152 is a CSG cell, the target subscriber group identification parameter comprises the CSG ID of the candidate target cell 152. If the candidate target cell 152 is a non-CSG cell, the target subscriber group identification parameter is empty/void. The mobile node 110 may also perform access control as previously described under step A, i.e. selective filtering of candidate target CSG cells 152 to report.
  • a target subscriber group identification parameter i.e. a parameter intended to comprise the subscriber group identification of a handover candidate target cell 152 to the source network control node 120 in a measurement report.
  • the target subscriber group identification parameter comprises the CSG ID of the candidate target cell 152. If the candidate target cell 152 is a non-CSG cell,
  • the mobile node 110 may not report any target subscriber group identification parameter to the source network control node 120 in a measurement report and may further not perform access control step A.
  • the mobile node 110 does not report any target subscriber group identification parameter to the source network control node 120, even if the mobile node 110 does support the CSG concept.
  • the source network control node 120 may receive the network based allowed subscriber group list of a mobile node 110 from the core network control node 130 when a connection and/or context between the source network control node 120 and core network control node 130 is established for the mobile node 110, according to some embodiments.
  • the S-(H)eNB may receive the allowed subscriber group list in the S1AP INITIAL CONTEXT SETUP REQUEST message from the source MME when the S1 connection is established for the mobile node 110.
  • the source network control node 120 supports the CSG concept and receives a target subscriber group identification parameter from the mobile node 110 and the source network control node 120 has not received the mobile node's 110 network based allowed subscriber group list from the core network control node 130, then the source network control node 120 forwards the target subscriber group identification parameter in signalling message 2 to the core network control node 130 and to the target network control node 150 in the S-to-T-container. Optionally, according to some embodiments it may be forwarded to the core network control node 130.
  • the source network control node 120 may perform access control step B, provided that the target subscriber group identification parameter was non-empty/void. If the access control performed results in accepted access, the source network control node 120 forwards the target subscriber group identification parameter to the target network control node 150 in the S-to-T container. If the access control performed results in denied access, the source network control node 120 may not proceed with the handover signalling according to some embodiments.
  • the source network control node 120 may not perform access control step B and may thus not forward any target subscriber group identification parameter neither to the core network control node 130 nor to the target network control node 150, according to some embodiments.
  • the source network control node 120 may discard any target subscriber group identification parameter received from the mobile node 110. Thus according to some embodiments it may not perform access control step B and may accordingly not forward any target subscriber group identification parameter, neither to the core network control node 130 nor to the target network control node 150.
  • the described behaviour applies also when the source network control node 120 is S-HRANS i.e. the source Node B/ eNodeB is a Home Node B or Home eNodeB.
  • the core network control node 130 may forward the mobile node's 110 network based allowed subscriber group list to the source network control node 120.
  • the source- MME may forward the allowed subscriber group list to the source-(H)eNB in the S1AP INITIAL CONTEXT SETUP REQUEST message, according to some embodiments.
  • the core network control node 130 may perform access control step B, according to some embodiments.
  • the core network control node 130 may, according to some embodiments send the mobile node's 110 network based allowed subscriber group list to the target network control node 140 in signalling message 3.
  • the core network control node 130 may perform access control step B.
  • the core network control node 130 may not perform any of the above described method steps, according to some embodiments.
  • the core network control node 130 forwards the S-to-T container in signalling message 3 and the T-to-S container in signalling message 7.
  • the target network control node 140 may forward the allowed subscriber group list to the target network control node 150 in signalling message 4, according to some embodiments. However, according to other embodiments, the target network control node 140 may perform access control step B after receiving the target subscriber group identification in signalling message 5 from the target network control node 150.
  • the target network control node 140 may forward the target subscriber group identification to the core network control node 130 in signalling message 6.
  • the target subscriber group identification may be provided in message 6 in order to support CSG based charging, i.e. not only for the purpose of access control.
  • the target network control node 140 may forward the S-toT container in signalling message 4 and the T-to-S container in signalling message 6.
  • the target network control node 150 may perform access control step C, according to some embodiments.
  • the target network control node 150 may perform access control step B.
  • the target network control node 150 may send the target subscriber group identification, i.e. the actual subscriber group identification of the target cell in signalling message 5 to the target network control node 140.
  • Figure 4 is a combined signalling scheme and block diagram illustrating method embodiments in a communication network. In particular a procedure in EPC/ E-UTRAN inter-MME handover case is illustrated.
  • the mobile node 110 may establish a signalling connection with the source network control node 120, which source network control node 120 in turn may establish a signalling connection with a core network control node 130.
  • the core network control node 130 may be represented e.g. by a source Mobility Management Entity.
  • the mobile node 110 may send user plane data to the source network control node 120, which source network control node 120 may be e.g. an eNodeB, or a Home eNodeB in EPC/ E-UTRAN.
  • the source network control node 120 may forward the user plane data to a serving Gateway, which in turn sends it to a Gateway 430.
  • the Gateway 430 may according to some embodiments comprise the Serving Gateway and Packet Data Network Gateway (PDN GW). However these nodes may be separate entities.
  • a Home eNodeB Gateway may handle the user plane also between the Home eNodeB and Serving Gateway.
  • a target network control node 140 may be detected and System Information (SI) read.
  • SI System Information
  • an access control according to the previously described step A may be performed at the mobile node 110.
  • the mobile node 110 may report target cell 152 and target subscriber group identification, such as e.g. the CSG ID of the target cell 152 to the source network control node 120 only if the target subscriber group identification is included in the mobile node 110 based allowed subscriber group list.
  • target subscriber group identification such as e.g. the CSG ID of the target cell 152
  • a new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g. a target CSG cell, may be sent from the mobile node 110 to the source network control node 120. This may correspond to the previously described message 1, according to some embodiments.
  • target subscriber group identification such as e.g. CSG ID, eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g. a target CSG cell
  • TAI Tracking Area Identity
  • a handover (HO) decision may be taken in the source network control node 120, to initiate a handover process for the mobile node 110, from the source cell 121 to the target cell 152.
  • a S1 Application Protocol (S1AP) Handover required message may be sent from the source control node 120 to the core network control node 130.
  • the message in step 407 may correspond to the previously described message 2 and may comprise the new Information Element (IE) comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g. a target CSG cell.
  • An S-to-T container as previously defined, may be sent comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g. a target CSG cell, and E-UTRAN Cell Global Identity (ECGI).
  • IE Information Element
  • e.g. target subscriber group identification such as e.g. CSG ID
  • an access control according to the previously described step B may be performed at the core network control node 130.
  • the target subscriber group identification may be checked against the allowed subscriber group list i.e. the network based allowed subscriber group list obtained from the database 160 when the original session was established.
  • the database 160 may be a Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the handover can be admitted only if the target subscriber group identification is included in the mobile node 110's network based allowed subscriber group list.
  • a forward relocation request may be sent from the core network control node 130 to the target network control node 140.
  • the target network control node 140 may be represented by a target MME in EPC/ E-UTRAN.
  • the forward relocation request may among other parameters comprise an S-to-T container, as previously defined, comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g. a target CSG cell, and E-UTRAN Cell Global Identity (ECGI).
  • S-to-T container as previously defined, comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity (TAI) of target cell 152, e.g.
  • a S1 Application Protocol (S1AP) Handover request message may be sent from the target network control node 140 to the target network control node 150, possibly via a gateway 420, which gateway 420 may be a Home eNodeB gateway.
  • This step 410 may correspond to the previously described message 4.
  • an access control according to the previously described step C may be performed at the target network control node 150.
  • an access control according to the previously described step C may be performed at the gateway 420, which may be a Home eNodeB gateway.
  • the target network control node 150 or alternatively the gateway 420 may check that the target subscriber group identification reported by the mobile node 110 matches the subscriber group identification of the actual target cell 152, e.g. as identified by the reported cell ID. If the target subscriber group identification reported by the mobile node 110 does not match the subscriber group identification of the target cell 152, the handover may not be allowed and the handover procedure may be discontinued.
  • the rest of the Inter MME S1 based handover may be performed as specified in 3GPP TS 23.401, according to some embodiments.
  • Figure 5 is a combined signalling scheme and block diagram illustrating method embodiments in a communication network. In particular a procedure in EPC/ E-UTRAN inter-MME handover case, according to some embodiments is illustrated.
  • an S1 connection establishment for the mobile node 110 wherein the core network control node 130, which core network control node 130 may be an MME, transfers the mobile node's 110 allowed subscriber group list to the source network control node 120.
  • the source network control node 120 may be represented e.g. by a source Home eNodeB or an eNodeB, according to some embodiments.
  • the mobile node 110 may establish a signalling connection with the source network control node 120, which source network control node 120 in turn may establish a signalling connection with a core network control node 130.
  • the core network control node 130 may be represented e.g. by a source Mobility Management Entity.
  • the mobile node 110 may send user plane data to the source network control node 120, which source network control node 120 may be an eNodeB, or a Home eNodeB in EPC/ E-UTRAN.
  • the source network control node 120 may forward the user plane data to a serving Gateway, which in turn sends it to a Gateway 430.
  • the Gateway 430 may comprise, according to some embodiments, the Serving Gateway and Packet Data Network Gateway (PDN GW). However these nodes may be separate entities.
  • PDN GW Packet Data Network Gateway
  • a Home eNodeB Gateway may handle the user plane also between the Home eNodeB and Serving Gateway.
  • a target network control node 140 may be detected and System Information (SI) read.
  • SI System Information
  • an access control according to the previously described step A may be performed at the mobile node 110.
  • the mobile node 110 may report target cell 152 and target subscriber group identification, such as e.g. the CSG ID of the target cell 152 to the source network control node 120 only if the target subscriber group identification is included in the mobile node 110 based allowed subscriber group list, according to some embodiments.
  • target subscriber group identification such as e.g. the CSG ID of the target cell 152
  • a new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity of target cell 152, e.g. a target CSG cell, may be sent from the mobile node 110 to the source network control node 120. This may correspond to the previously described message 1, according to some embodiments.
  • a handover (HO) decision may be taken in the source network control node 120, to initiate a handover process for the mobile node 110, from the source cell 121 to the target cell 152.
  • an access control according to the previously described step B may be performed at the core network control node 130.
  • the target subscriber group identification may be checked against the allowed subscriber group list i.e. the network based allowed subscriber group list obtained from the database 160 when the original session was established.
  • the database 160 may be a Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the handover may be admitted only if the target subscriber group identification is comprised in the mobile node 110's network based allowed subscriber group list, according to some embodiments.
  • a S1 Application Protocol (S1AP) Handover required message may be sent from the source network control node 120 to the core network control node 130.
  • the message in step 407 may correspond to the previously described message 2 and may comprise the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity of target cell 152, e.g. a target CSG cell.
  • An S-to-T container as previously defined, may be sent comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity of target cell 152, e.g. a target CSG cell, and E-UTRAN Cell Global Identity (ECGI).
  • ECGI E-UTRAN Cell Global Identity
  • Step 510
  • a forward relocation request may be sent from the core network control node 130 to the target network control node 140.
  • the target network control node 140 may be represented by a target MME in EPC/ E-UTRAN.
  • the forward relocation request may among other parameters comprise an S-to-T container, as previously defined, comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity of target cell 152, e.g. a target CSG cell, and E-UTRAN Cell Global Identity (ECGI).
  • S-to-T container as previously defined, comprising e.g. the new Information Element comprising e.g. target subscriber group identification such as e.g. CSG ID, together with other Information Elements comprising e.g. eNodeB ID, Tracking Area Identity of target cell 152, e.g. a target CSG cell, and E
  • a S1 Application Protocol (S1AP) Handover request message may be sent from the target network control node 140 to the target network control node 150, possibly via a gateway 420, which gateway 420 may be a Home eNodeB gateway.
  • This step 511 may correspond to the previously described message 4.
  • an access control according to the previously described step C may be performed at the target network control node 150.
  • an access control according to the previously described step C may be performed at the gateway 420, which may be a Home eNodeB gateway.
  • the target network control node 150 or, alternatively, the gateway 420 may check that the target subscriber group identification reported by the mobile node 110 matches the subscriber group identification of the actual target cell 152, e.g. as identified by the reported cell ID. If the target subscriber group identification reported by the mobile node 110 does not match the subscriber group identification of the target cell 152, the handover may not be allowed and the handover procedure may be discontinued, according to some embodiments.
  • the rest of the Inter MME S1 based handover may, according to some embodiments be performed as specified in 3GPP TS 23.401.
  • a particular selection criterion may be that an illegitimate mobile node 110 should be stopped as early as possible, in particular before any radio resources are allocated in the target network control node 150. Therefore embodiments of the present solutions may be directed towards barring illegitimate mobile node 110 early in the handover process, preferably before the handover has been executed, in order to reduce signalling within the communication network 100 and in order not to allocate resources unnecessarily to the illegitimate mobile node 110, e.g. in the source network control node 120, or in the core network control node 130.
  • the handover may be stopped with reject messages, such as e.g. an S1AP HANDOVER FAILURE message between the target network control node 150 and the target network control node 140 and/or an S1AP HANDOVER PREPARATION FAILURE message, between the core network control node 130 and the source network control node 120 in EPS. If the access control fails after radio resources have been allocated in the target network control node 150, the handover may be aborted through other means, e.g. involving an S1AP HANDOVER CANCEL message in EPC/E-UTRAN.
  • the present methods and arrangements provide improved mechanisms for access control of mobile nodes 110 during, or before, handover into a subscriber group cell 152, such as e.g. a CSG cell.
  • the present mechanisms allow an illegitimate mobile node 110 to be barred from access early in the handover procedure; in particular before any radio resources are allocated in the target subscriber group cell 152, which minimizes the possible failure cases.
  • the present methods and arrangements may be performed without introduction of additional messages, compared to the non- subscriber group handover scenarios, thereby avoiding an increased latency for the subscriber group enabled mobile nodes 110, such as CSG-enabled mobile nodes 110.
  • the subscriber group based access control used for other, non-handover network access cases such as e.g. Attach and Service Request in EPC/E-UTRAN would have to be used also during handover into subscriber group cells 152.
  • An advantage with the present methods and arrangements is that an access control mechanism is provided early in a handover process, i.e. before resources are allocated in the target network control node 150 and released in the source network control node 120 and the mobile node 110 is already communicating via the target network control node 150. Thus unnecessary allocation of resources may be omitted or at least somewhat reduced.
  • the present methods and arrangements may improve the access control mechanism in handover scenarios when the movement to the target CSG cell does not trigger a location registration.
  • the present methods and arrangements may prevent or at least somewhat reduce the possibility for a malicious mobile node 110 to avoid access control, by omitting the location registration following the handover.
  • Figure 6 is a flow chart illustrating embodiments of method steps 601-607 performed in a network control node 120, 130.
  • the method aims at performing access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the network control node 120, 130, the source cell 121 and the target subscriber group cell 152 are comprised in a communication network 100.
  • the network control node 120, 130 may be a core network control node 130, represented by an entity comprised in the group: Mobility Management Entity (MME), Serving General Packet Radio Service Support Node (SGSN), Mobile Switching Centre (MSC), according to some embodiments.
  • MME Mobility Management Entity
  • SGSN Serving General Packet Radio Service Support Node
  • MSC Mobile Switching Centre
  • the network control node 120, 130 may be a source network control node 120, represented by a Radio Access Network.
  • the Radio Access Network may comprise any, some or a plurality of e.g. a Radio Access Network Subsystem, an eNodeB, a nodeB, a radio network subsystem, a Radio Network Controller, a base station subsystem, a Home eNodeB, a Home NodeB, a Home eNodeB Gateway and/or a Home NodeB Gateway.
  • the network control node 120, 130 may comprise, or be connected to, a time measurement unit 730.
  • the target subscriber group cell 152 may according to some embodiments be a Closed Subscriber Group cell (CSG cell). Further, the received target subscriber group identification may optionally be a Closed Subscriber Group ID (CSG ID).
  • CSG cell Closed Subscriber Group cell
  • CSG ID Closed Subscriber Group ID
  • the source cell 121 may according to some embodiments be a subscriber group cell such as e.g. a Closed Subscriber Group cell (CSG cell). However, according to some embodiments, the source cell 121 may be a cell with non restricted access.
  • CSG cell Closed Subscriber Group cell
  • the source cell 121 may be a cell with non restricted access.
  • the method may comprise a number of method steps 601-607.
  • method steps 601-607 are optional and only comprised within some embodiments. Further, it is to be noted that the method steps 601-607 may be performed in another chronological order than illustrated in this exemplary embodiment and that some method steps, e.g. step 601 and step 602, or even all steps 601-607 may be performed simultaneously or in an altered or rearranged chronological order, according to different embodiments.
  • the method may comprise the following steps:
  • a network based allowed subscriber group list, associated with the mobile node 110 is obtained.
  • the network based allowed subscriber group list may be e.g. an Allowed Closed Subscriber Group List (ACL), which also may be referred to as a Closed Subscriber Group Whitelist.
  • ACL Allowed Closed Subscriber Group List
  • the network based allowed subscriber group list associated with the mobile node 110 may be obtained from a database 160, such as a Home Subscriber Server (HSS).
  • a database 160 such as a Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • a target subscriber group identification is received.
  • the target subscriber group identification may be e.g. a Closed Subscriber Group identification (CSG ID).
  • CSG ID Closed Subscriber Group identification
  • This step is optional and may only be performed within some embodiments.
  • a check may be performed, in order to check if a time limit value associated with the mobile node 110 is exceeded.
  • the check may be performed by making a comparison with a time measurement value obtained from the time measurement unit 730.
  • This step is optional and may only be performed within some embodiments.
  • the mobile node 110 may be rejected access to the target subscriber group cell 152.
  • target subscriber group identification is comprised in the network based allowed subscriber group list
  • information from a target network control node 150 is obtained.
  • the target network control node 150 is associated with the target subscriber group cell 152, wherein the information is verifying that the received subscriber group identification corresponds to the target subscriber group cell 152.
  • the target network control node 150 may be represented by a Radio Access Network.
  • the Radio Access Network may comprise any, some or a plurality of e.g. a Radio Access Network Subsystem, an eNodeB, a nodeB, a radio network subsystem, a Radio Network Controller, a base station subsystem, a Home eNodeB, a Home NodeB, a Home eNodeB Gateway and/or a Home NodeB Gateway.
  • the Radio Access Network as referred to herein may comprise only one node 150, according to some embodiments.
  • the step of obtaining information from the target network control node 150 may optionally, according to some embodiments comprise sending a request for handover, comprising of a subscriber group identification, associated with the target subscriber group cell 152 from the network control node 120, 130 to the target network control node 150.
  • the step of obtaining information from the target network control node 150 may comprise receiving a response to the sent request for handover from the target network control node 150, which response comprises information verifying that the subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • the received response to the sent request for handover which may be received from the target network control node 150, may comprise the subscriber group identity of the target subscriber group cell 152.
  • the network control node 120, 130 may perform the further substep of comparing the received subscriber group identity of the target subscriber group cell 152 with the obtained subscriber group identification.
  • the mobile node 110 is granted access to the target subscriber group cell 152.
  • Figure 7 is a block diagram illustrating embodiments of an arrangement 700 situated in a in a network control node 120, 130.
  • the arrangement 700 is configured to perform at least some of the method steps 601-607 for performing access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the network control node 120, 130, the source cell 121 and the target subscriber group cell 152 are comprised in a communication network 100.
  • the network control node 120, 130 may be a core network control node 130, represented by an entity comprised in the group: Mobility Management Entity (MME), Serving General Packet Radio Service Support Node (SGSN), Mobile Switching Centre (MSC), according to some embodiments.
  • MME Mobility Management Entity
  • SGSN Serving General Packet Radio Service Support Node
  • MSC Mobile Switching Centre
  • the network control node 120, 130 may be a source network control node 120, represented by a Radio Access Network.
  • the Radio Access Network may comprise any, some or a plurality of e.g. a Radio Access Network Subsystem, an eNodeB, a nodeB, a radio network subsystem, a Radio Network Controller, a base station subsystem, a Home eNodeB, a Home NodeB, a Home eNodeB Gateway and/or a Home NodeB Gateway.
  • the Radio Access Network as referred to herein may comprise only one node 120, according to some embodiments.
  • the network control node 120, 130 may comprise, or be connected to, a time measurement unit 730.
  • the target subscriber group cell 152 may according to some embodiments be a Closed Subscriber Group cell (CSG cell). Further, the received target subscriber group identification may optionally be a Closed Subscriber Group ID (CSG ID).
  • CSG cell Closed Subscriber Group cell
  • CSG ID Closed Subscriber Group ID
  • the source cell 121 may according to some embodiments be a subscriber group cell such as e.g. a Closed Subscriber Group cell (CSG cell). However, according to some embodiments, the source cell 121 may be a cell with non restricted access.
  • CSG cell Closed Subscriber Group cell
  • the source cell 121 may be a cell with non restricted access.
  • the arrangement 700 comprises a first obtaining unit 710.
  • the first obtaining unit 710 is adapted to obtain a network based allowed subscriber group list associated with the mobile node 110.
  • the arrangement 700 comprises a receiving unit 720, adapted to receive a target subscriber group identification.
  • the arrangement 700 comprises a checking unit 750.
  • the checking unit 750 is adapted to check if the target subscriber group identification is comprised in the obtained network based allowed subscriber group list.
  • the arrangement 700 comprises a second obtaining unit 760.
  • the second obtaining unit 760 adapted to obtain information from a target network control node 150, which target network control node 150 is associated with the target subscriber group cell 152.
  • the arrangement 700 in further addition comprises an access granting unit 770.
  • the access granting unit 770 is adapted to grant the mobile node 110 access to the target subscriber group cell 152.
  • the arrangement 700 may according to some optional embodiments comprise, or be connected to, a time measurement unit 730.
  • the time measurement unit 730 may be adapted to measure time.
  • the arrangement 700 may optionally comprise a checking unit 750.
  • the checking unit 750 may be adapted to check if a time limit value associated with the mobile node 110 is exceeded, by performing a comparison with a time measurement value obtained from the time measurement unit 730.
  • the arrangement 700 may as a further additional option comprise a rejecting unit.
  • the rejecting unit may be adapted to reject the mobile node 110 access to the target subscriber group cell 152.
  • the arrangement 700 may according to some embodiments comprise a processing unit 790.
  • the processing unit 790 may be represented by e.g. a Central Processing Unit (CPU), a processor, a microprocessor, or other processing logic that may interpret and execute instructions.
  • the processing unit 790 may perform all data processing functions for inputting, outputting, and processing of data including data buffering and device control functions, such as call processing control, user interface control, or the like.
  • the arrangement 700 optionally may comprise a transmitting unit 780.
  • the described units 710-790 comprised within the arrangement 700 may be regarded as separate logical entities, but not with necessity as separate physical entities. Any, some or all of the units 710-790 may be comprised or co-arranged within the same physical unit. However, in order to facilitate the understanding of the functionality of the arrangement 700, the comprised units 710-790 are illustrated as separate physical units in Figure 7 . Thus e.g. the transmitting unit 780 and the receiving unit 720 may, according to some embodiments, be comprised within one physical unit, a transceiver, which may comprise a transmitter circuit and a receiver circuit.
  • the method steps 601-607 in the network control node 120, 130 may be implemented through one or more processing units 790 in the network control node 120, 130, together with computer program code for performing the functions of at least some of the present steps 601-607.
  • a computer program product comprising instructions for performing the method steps 601-607 in the network control node 120, 130 may perform access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the computer program product mentioned above may be provided for instance in the form of a data carrier carrying computer program code for performing the method steps 601-607 according to the present solution when being loaded into the processing unit 790.
  • the data carrier may be e.g. a hard disk, a CD ROM disc, a memory stick, an optical storage device, a magnetic storage device or any other appropriate medium such as a disc or tape that can hold machine readable data.
  • the computer program product may furthermore be provided as computer program code on a server and downloaded to the network control node 120, 130 remotely, e.g. over an Internet or an intranet connection.
  • the computer program product may comprise instructions for obtaining a network based allowed subscriber group list, associated with the mobile node 110. Further, the computer program product may comprise instructions for receiving a target subscriber group identification. In addition, the computer program product may comprise instructions for checking if the target subscriber group identification is comprised in the obtained network based allowed subscriber group list. The computer program product may further comprise instructions for obtaining information from a target network control node 150, which target network control node 150 is associated with the target subscriber group cell 152, wherein the information is verifying that the received subscriber group identification corresponds to the target subscriber group cell 152. Also, the computer program product may comprise instructions for granting the mobile node 110 access to the target subscriber group cell 152, when the computer program product is run on a processing unit 790 comprised within the network control node 120, 130.
  • Figure 8 is a flow chart illustrating embodiments of method steps 801-803 performed in a target network control node 150.
  • the method aims at assisting a network control node 120, 130 in performing access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the target subscriber group cell 152 is associated with the target control node 150.
  • the network control node 120, 130, the target network control node 150 and the target subscriber group cell 152 are comprised in a communication network 100.
  • the target network control node 150 may be represented by a Radio Access Network.
  • the Radio Access Network may comprise any, some or a plurality of e.g. a Radio Access Network Subsystem, an eNodeB, a nodeB, a radio network subsystem, a Radio Network Controller, a base station subsystem, a Home eNodeB, a Home NodeB, a Home eNodeB Gateway and/or a Home NodeB Gateway.
  • the Radio Access Network as referred to herein may comprise only one node 150, according to some embodiments.
  • the network control node 120, 130 may be a core network control node 130, represented by an entity comprised in the group: Mobility Management Entity (MME), Serving General Packet Radio Service Support Node (SGSN), Mobile Switching Centre (MSC), according to some embodiments.
  • MME Mobility Management Entity
  • SGSN Serving General Packet Radio Service Support Node
  • MSC Mobile Switching Centre
  • the network control node 120, 130 may be a source network control node 120, represented by a Radio Access Network.
  • the Radio Access Network may comprise any, some or a plurality of e.g. a Radio Access Network Subsystem, an eNodeB, a nodeB, a radio network subsystem, a Radio Network Controller, a base station subsystem, a Home eNodeB, a Home NodeB, a Home eNodeB Gateway and/or a Home NodeB Gateway.
  • the Radio Access Network as referred to herein may comprise only one node 120, according to some embodiments.
  • the target subscriber group cell 152 may according to some embodiments be a Closed Subscriber Group cell (CSG cell). Further, the received target subscriber group identification may optionally be a Closed Subscriber Group ID (CSG ID).
  • CSG cell Closed Subscriber Group cell
  • CSG ID Closed Subscriber Group ID
  • the method may comprise a number of method steps 801-803.
  • method steps 801-803 e.g. method step 802 is optional and only comprised within some embodiments. Further, it is to be noted that the method steps 801-803 may be performed in another chronological order than illustrated in this exemplary embodiment and that some method steps, e.g. step 801 and the optional step 802, or even all steps 801-803 may be performed simultaneously or in an altered or rearranged chronological order, according to different alternative embodiments.
  • the method may comprise the following steps:
  • a request for handover, comprising a subscriber group identification is received from the network control node 120, 130.
  • the subscriber group identification is associated with the target subscriber group cell 152.
  • This step is optional and may only be performed within some embodiments.
  • the received subscriber group identification may be compared with the subscriber group identity of the target subscriber group cell 152.
  • a response to the received request for handover is sent to the network control node 120, 130.
  • the response comprises information for assisting the network control node 120, 130 in verifying that the received subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • such response may only be sent if the subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • the response may comprise information verifying that the received subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • the response sent 803 to the network control node 120, 130 may comprise the subscriber group identity of the target subscriber group cell 152.
  • a response may instead be sent indicating that the handover is rejected, according to some embodiments.
  • Figure 9 is a block diagram illustrating embodiments of an arrangement 900 situated in a in a target network control node 150.
  • the arrangement 900 is configured to perform at least some of the method steps 801-803 in the target network control node 150, for assisting a network control node 120, 130 in performing access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the target network control node 150, the network control node 120, 130, the source cell 121 and the target subscriber group cell 152 are comprised in a communication network 100.
  • the arrangement 900 comprises a receiving unit 910.
  • the receiving unit 910 is adapted to receive a request for handover, comprising a subscriber group identification, associated with the target subscriber group cell 152, from the network control node 120, 130.
  • the arrangement 900 comprises a sending unit 930.
  • the sending unit 930 is adapted to send a response to the received request for handover to the network control node 120, 130.
  • the response comprises information verifying that the received subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • the arrangement 900 may comprise a comparison unit 920.
  • the optional comparison unit 920 may be adapted to compare the received subscriber group identification with the subscriber group identity of the target subscriber group cell 152.
  • the arrangement 900 may according to some embodiments comprise a processing unit 940.
  • the processing unit 940 may be represented by e.g. a Central Processing Unit (CPU), a processor, a microprocessor, or other processing logic that may interpret and execute instructions.
  • the processing unit 940 may perform all data processing functions for inputting, outputting, and processing of data including data buffering and device control functions, such as call processing control, user interface control, or the like.
  • the described units 910-940 comprised within the arrangement 900 may be regarded as separate logical entities, but not with necessity as separate physical entities. Any, some or all of the units 910-940 may be comprised or co-arranged within the same physical unit. However, in order to facilitate the understanding of the functionality of the arrangement 900, the comprised units 910-940 are illustrated as separate physical units in Figure 9 . Thus e.g. the sending unit 930 and the receiving unit 910 may, according to some embodiments, be comprised within one physical unit, a transceiver, which may comprise a transmitter circuit and a receiver circuit.
  • the method steps 801-803 in the target network control node 150 may be implemented through one or more processing units 940 in the target network control node 150, together with computer program code for performing the functions of at least some of the present steps 801-803.
  • a computer program product comprising instructions for performing the method steps 801-803 in the target network control node 150 may assist a network control node 120, 130 in performing access control for a mobile node 110 in a handover from a source cell 121 to a target subscriber group cell 152.
  • the source cell 121 may be a subscriber group cell or a non subscriber group cell.
  • the computer program product mentioned above may be provided for instance in the form of a data carrier carrying computer program code for performing the method steps 801-803 according to the present solution when being loaded into the processing unit 940.
  • the data carrier may be e.g. a hard disk, a CD ROM disc, a memory stick, an optical storage device, a magnetic storage device or any other appropriate medium such as a disc or tape that can hold machine readable data.
  • the computer program product may furthermore be provided as computer program code on a server and downloaded to the target network control node 150 remotely, e.g. over an Internet or an intranet connection.
  • the computer program product may comprise instructions for receiving a request for handover, comprising a subscriber group identification, from the network control node 120, 130.
  • the subscriber group identification is associated with the target subscriber group cell 152.
  • the computer program product may comprise instructions for comparing the received subscriber group identification with the subscriber group identity of the target subscriber group cell 152.
  • the computer program product may further comprise instructions for sending a response to the received request for handover, to the network control node 120, 130, if the subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152.
  • the response may comprise information verifying that the received subscriber group identification corresponds to the subscriber group identity of the target subscriber group cell 152, when the computer program product is run on a processing unit 940 comprised within the target network control node 150.

Landscapes

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

Claims (14)

  1. Procédé dans une entité de gestion de mobilité, MME, (130) pour effectuer un contrôle d'accès pour un noeud mobile (110) dans un transfert intercellulaire d'une cellule source (121) à une cellule de groupe d'abonnés cible (152), dans lequel la MME (130), la cellule source (121) et la cellule de groupe d'abonnés cible (152) sont comprises dans un réseau de communication (100), le procédé comprenant les étapes de :
    l'obtention (601) d'une liste de groupes d'abonnés autorisés sur la base du réseau, associée au noeud mobile (110),
    la réception (602) d'une identification de groupe d'abonnés cible fournie par le noeud mobile (110),
    la vérification (605) si l'identification de groupe d'abonnés cible est comprise dans la liste de groupes d'abonnés autorisés sur la base du réseau obtenue,
    l'envoi d'une demande de transfert intercellulaire, comprenant l'identification de groupe d'abonnés fournie par le noeud mobile (110) à un eNB cible (150), dans lequel l'identification de groupe d'abonnés est associée à la cellule de groupe d'abonnés cible (152),
    l'obtention (606) d'une réponse de l'eNB cible (150), ladite réponse comprenant des informations confirmant que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152) ou indiquant que le transfert intercellulaire est rejeté, et
    l'octroi (607), au noeud mobile (110), d'un accès à la cellule de groupe d'abonnés cible (152) si la réponse indique que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152).
  2. Procédé selon la revendication 1, dans lequel la réception (602) d'une identification de groupe d'abonnés cible fournie par un noeud mobile (110) comprend la réception de l'identification de groupe d'abonnés cible par l'intermédiaire d'un eNB source.
  3. Procédé selon la revendication 1 ou 2, dans lequel la cellule de groupe d'abonnés cible (152) est une cellule de groupe d'abonnés fermé, CSG, et dans lequel l'identification de groupe d'abonnés cible reçue est une identification de groupe d'abonnés fermé, ID CSG.
  4. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel la liste de groupes d'abonnés autorisés sur la base du réseau associée au noeud mobile (110) est obtenue à partir d'une base de données (160), comme un serveur d'abonné de rattachement, HSS.
  5. Procédé selon l'une quelconque des revendications 1 à 4, dans lequel une unité de mesure de temps (730) est comprise à l'intérieur de la MME (130) et le procédé comprend en outre les étapes de :
    la vérification (603) si une valeur de limite de temps associée au noeud mobile (110) est dépassée, par l'exécution d'une comparaison à une valeur de mesure de temps obtenue à partir de l'unité de mesure de temps (730), et, si tel est le cas,
    le rejet (604) de l'accès du noeud mobile (110) à la cellule de groupe d'abonnés cible (152).
  6. Entité de gestion de mobilité, MME, (130) pour effectuer un contrôle d'accès pour un noeud mobile (110) dans un transfert intercellulaire d'une cellule source (121) à une cellule de groupe d'abonnés cible (152), dans laquelle la MME (130), la cellule source (121) et la cellule de groupe d'abonnés cible (152) sont configurées pour être comprises dans un réseau de communication (100), la MME comprenant :
    une première unité d'obtention (710) apte à effectuer l'obtention d'une liste de groupes d'abonnés autorisés sur la base du réseau, associée au noeud mobile (110),
    une unité de réception (720) apte à effectuer la réception d'une identification de groupe d'abonnés cible fournie par le noeud mobile (110),
    une unité de vérification (750) apte à effectuer la vérification si l'identification de groupe d'abonnés cible est comprise dans la liste de groupes d'abonnés autorisés sur la base du réseau obtenue,
    une unité d'envoi apte à effectuer l'envoi d'une demande de transfert intercellulaire, comprenant l'identification de groupe d'abonnés fournie par le noeud mobile (110) à un eNB cible (150), dans laquelle l'identification de groupe d'abonnés est associée à la cellule de groupe d'abonnés cible (152),
    une deuxième unité d'obtention (760) apte à effectuer l'obtention d'une réponse de l'eNB cible (150), ladite réponse comprenant des informations confirmant que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152) ou indiquant que le transfert intercellulaire est rejeté, et
    une unité d'octroi d'accès (770) apte à effectuer l'octroi, au noeud mobile (110), d'un accès à la cellule de groupe d'abonnés cible (152) si la réponse indique que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152).
  7. MME selon la revendication 6, dans laquelle l'unité de réception (720), apte à effectuer la réception d'une identification de groupe d'abonnés cible fournie par le noeud mobile (110), est apte à effectuer la réception de l'identification de groupe d'abonnés cible par l'intermédiaire d'un eNB source.
  8. MME selon la revendication 6 ou 7, dans laquelle la cellule de groupe d'abonnés cible (152) est une cellule de groupe d'abonnés fermé, CSG, et dans laquelle l'identification de groupe d'abonnés cible reçue est une identification de groupe d'abonnés fermé, ID CSG.
  9. Procédé dans un eNB cible (150), pour aider une entité de gestion de mobilité, MME, (130) à effectuer un contrôle d'accès pour un noeud mobile (110) dans un transfert intercellulaire d'une cellule source (121) à une cellule de groupe d'abonnés cible (152), dans lequel la MME (130), l'eNB cible (150) et la cellule de groupe d'abonnés cible (152) sont comprises dans un réseau de communication (100), le procédé comprenant les étapes de :
    la réception (801) d'une demande de transfert intercellulaire, comprenant une identification de groupe d'abonnés, associée à la cellule de groupe d'abonnés cible (152) fournie par le noeud mobile (110) en provenance de la MME (130),
    la comparaison (802) de l'identification de groupe d'abonnés reçue à une identité de groupe d'abonnés de la cellule de groupe d'abonnés cible,
    l'envoi (803) d'une réponse à la demande reçue pour un transfert intercellulaire à la MME (130), ladite réponse comprenant des informations confirmant que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152) ou indiquant que le transfert intercellulaire est rejeté.
  10. Procédé selon la revendication 9, dans lequel la réponse envoyée (803) à la MME (130) comprend l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152).
  11. Procédé selon la revendication 9 ou 10, dans lequel la cellule de groupe d'abonnés cible (152) est une cellule de groupe d'abonnés fermé, CSG, et dans lequel l'identification de groupe d'abonnés cible reçue est une identification de groupe d'abonnés fermé, ID CSG.
  12. eNB cible (150), pour aider une entité de gestion de mobilité, MME, (130) à effectuer un contrôle d'accès pour un noeud mobile (110) dans un transfert intercellulaire d'une cellule source (121) à une cellule de groupe d'abonnés cible (152), ladite cellule de groupe d'abonnés cible (152) étant associée à l'eNB cible (150), dans lequel la MME (130), l'eNB cible (150) et la cellule de groupe d'abonnés cible (152) sont configurées pour être comprises dans un réseau de communication (100), l'agencement (900) comprenant :
    une unité de réception (910) apte à effectuer la réception d'une demande de transfert intercellulaire, comprenant une identification de groupe d'abonnés, fournie par le noeud mobile (110) en provenance de la MME (130),
    une unité de comparaison (920) apte à effectuer la comparaison de l'identification de groupe d'abonnés reçue à une identité de groupe d'abonnés de la cellule de groupe d'abonnés cible,
    une unité d'envoi (930) apte à effectuer l'envoi d'une réponse à la demande reçue pour un transfert intercellulaire à la MME (130), ladite réponse comprenant des informations confirmant que l'identification de groupe d'abonnés correspond à l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152) ou indiquant que le transfert intercellulaire est rejeté.
  13. eNB cible (150) selon la revendication 12, dans lequel la réponse envoyée à la MME (130) comprend l'identité de groupe d'abonnés de la cellule de groupe d'abonnés cible (152).
  14. eNB cible (150) selon la revendication 12 ou 13, dans lequel la cellule de groupe d'abonnés cible (152) est une cellule de groupe d'abonnés fermé, CSG, et dans lequel l'identification de groupe d'abonnés cible reçue est une identification de groupe d'abonnés fermé, ID CSG.
EP09838968.7A 2009-01-23 2009-04-07 Procédé et agencement dans un réseau de communication Active EP2382826B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14681109P 2009-01-23 2009-01-23
PCT/SE2009/050362 WO2010085191A1 (fr) 2009-01-23 2009-04-07 Procédé et agencement dans un réseau de communication

Publications (3)

Publication Number Publication Date
EP2382826A1 EP2382826A1 (fr) 2011-11-02
EP2382826A4 EP2382826A4 (fr) 2014-05-14
EP2382826B1 true EP2382826B1 (fr) 2017-11-29

Family

ID=42356099

Family Applications (1)

Application Number Title Priority Date Filing Date
EP09838968.7A Active EP2382826B1 (fr) 2009-01-23 2009-04-07 Procédé et agencement dans un réseau de communication

Country Status (12)

Country Link
US (3) US8781472B2 (fr)
EP (1) EP2382826B1 (fr)
JP (1) JP5484487B2 (fr)
CN (2) CN102326429B (fr)
BR (1) BRPI0924130B1 (fr)
DK (1) DK2382826T3 (fr)
ES (1) ES2660191T3 (fr)
MX (1) MX2011007672A (fr)
NO (1) NO2382826T3 (fr)
PT (1) PT2382826T (fr)
TW (1) TWI482506B (fr)
WO (1) WO2010085191A1 (fr)

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100584093C (zh) * 2006-08-15 2010-01-20 华为技术有限公司 一种在移动通信系统中转移用户设备的方法及系统
CN101790221B (zh) * 2009-01-22 2015-05-06 中兴通讯股份有限公司 家用基站切换时网络接入控制方法及系统
BRPI0924130B1 (pt) * 2009-01-23 2021-05-18 Telefonaktiebolaget Lm Ericsson Métodos e arranjos para executar controle de acesso para um nó móvel e para auxiliar um nó de controle de rede em executar controle de acesso a um nó móvel
US8520594B2 (en) * 2009-01-30 2013-08-27 Qualcomm Incorporated Selectively including allowed closed subscriber group list in page message
US20100197307A1 (en) * 2009-01-30 2010-08-05 Qualcomm Incorporated Access control for access terminals
US8731551B2 (en) * 2009-01-30 2014-05-20 Qualcomm Incorporated CSG membership indication
CN104768194B (zh) 2009-02-13 2020-12-08 三星电子株式会社 包括毫微微小区的无线通信系统中的切换方法和装置
PL2396939T3 (pl) 2009-02-16 2020-08-24 Nokia Solutions And Networks Oy Sposoby, urządzenia, system, powiązane programy komputerowe i struktury danych do dostarczania informacji o subskrypcji
US8369290B2 (en) * 2009-04-13 2013-02-05 Futureweil Technologies, Inc System and method for supporting handovers between different radio access technologies of a wireless communications system
GB2469645A (en) * 2009-04-20 2010-10-27 Nec Corp Providing information about a mobile device in a relocation request message
GB2471988A (en) * 2009-04-27 2011-01-26 Nec Corp Communication System comprising Home Base Station and associated Closed Subscriber Group
US9002356B2 (en) 2009-05-04 2015-04-07 Qualcomm Incorporated Access mode-based access control
CN101932049A (zh) * 2009-06-18 2010-12-29 中兴通讯股份有限公司 一种用户接入模式的通知方法及系统
JP5123274B2 (ja) * 2009-11-02 2013-01-23 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法及び無線基地局
KR101682930B1 (ko) * 2009-11-26 2016-12-07 삼성전자 주식회사 통신 시스템에서 무선 단말의 지역 기반 접속 허용 리스트 생성 방법 및 장치
CN102223691B (zh) * 2010-04-15 2015-08-12 北京三星通信技术研究有限公司 移动通信系统中的切换方法
CN102238668B (zh) * 2010-05-07 2015-08-12 北京三星通信技术研究有限公司 一种通过网关进行x2切换的方法
US20120002637A1 (en) * 2010-06-18 2012-01-05 Interdigital Patent Holdings, Inc. Method and apparatus for supporting home node-b mobility
CN102348222B (zh) * 2010-08-03 2014-12-10 中兴通讯股份有限公司 基于数字集群系统的故障弱化处理的方法及基站
KR101433541B1 (ko) * 2010-08-17 2014-08-22 닛본 덴끼 가부시끼가이샤 HeNB 인바운드 모빌리티에 대한 액세스 제어 실패 핸들링
CN102421198B (zh) * 2010-09-28 2016-03-30 中兴通讯股份有限公司 一种将更新信息通知核心网的方法及系统
US10003993B2 (en) * 2010-10-06 2018-06-19 Provenance Asset Group Llc Subscriber handling in radio telecommunication networks
EP3570589A1 (fr) 2011-02-10 2019-11-20 Mitsubishi Electric Corporation Système de communication, dispositif de terminal de communication et cellule primaire
AU2012240732B2 (en) 2011-04-05 2016-04-21 Samsung Electronics Co., Ltd. Method and apparatus for controlling inter-PLMN handover to CSG cell
US9119125B2 (en) * 2011-04-06 2015-08-25 Telefonaktiebolaget L M Ericsson (Publ) Method for managing handover of a user equipment
US8699461B2 (en) * 2011-08-19 2014-04-15 Hitachi, Ltd. Optimized home evolved NodeB (eNB) handover in an LTE network
US8934913B2 (en) * 2011-09-28 2015-01-13 Telefonaktiebolaget L M Ericsson (Publ) Enhanced mobility to home base station cells
GB2497316A (en) 2011-12-06 2013-06-12 Nec Corp Transferring internally at least one information element between first and second base station modules
US10433161B2 (en) * 2012-01-30 2019-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Call handover between cellular communication system nodes that support different security contexts
KR101625183B1 (ko) * 2012-02-10 2016-05-27 애플 인크. 아이덴티티 프로비저닝과 연관된 에러 이벤트들을 정정하기 위한 방법 및 장치
EP3541106A1 (fr) * 2012-02-14 2019-09-18 Apple Inc. Procédés et appareil de gestion de certificats euicc
US9924443B2 (en) * 2012-02-24 2018-03-20 Qualcomm Incorporated Methods and apparatus for selecting femtocell access modes and operational parameters based on the presence of nearby macrocells
JP5851585B2 (ja) * 2012-03-16 2016-02-03 京セラ株式会社 通信制御方法、ユーザ端末、基地局、及びホーム基地局
WO2014047852A1 (fr) * 2012-09-27 2014-04-03 华为技术有限公司 Procédé de détermination d'une cible, élément de réseau et système de détermination d'une cible
WO2015045296A2 (fr) * 2013-09-27 2015-04-02 Nec Corporation Système de communication, station de base, procédé de communication, et support lisible par ordinateur non éphémère stockant un programme
US20150094069A1 (en) * 2013-09-30 2015-04-02 Qualcomm Incorporated Enhanced inter-radio access technology handover procedures
CN104735679B (zh) * 2013-12-23 2018-06-26 中国移动通信集团上海有限公司 Femto网关接入核心网池的方法、网关及网络构架
US10104603B2 (en) 2014-05-30 2018-10-16 Nec Corporation Apparatus, system and method for dedicated core network
CN106304210A (zh) * 2015-05-29 2017-01-04 深圳富泰宏精密工业有限公司 网络连接控制系统及智能终端
WO2018014937A1 (fr) * 2016-07-19 2018-01-25 Telefonaktiebolaget Lm Ericsson (Publ) Noeud et procédé pour détecter qu'un dispositif sans fil a été en communication avec un dispositif non légitime
EP3524009B1 (fr) * 2016-10-07 2024-05-29 InterDigital Patent Holdings, Inc. Procédé et dispositif pour appliquer une mobilité limitée dans un réseau mobile
WO2020034106A1 (fr) * 2018-08-14 2020-02-20 Oppo广东移动通信有限公司 Procédé d'accès à un réseau, dispositif terminal et dispositif de réseau
CN111132265B (zh) * 2018-11-01 2021-06-08 华为技术有限公司 网络接入方法及装置
CN113630779B (zh) * 2021-08-17 2023-06-02 中国联合网络通信集团有限公司 网络连接管理方法及装置、终端
US11564139B1 (en) * 2021-08-19 2023-01-24 T-Mobile Innovations Llc Limiting mobility between networks based on cellID
CN114501595B (zh) * 2022-01-19 2024-04-26 陕西立博源科技有限公司 5g组网工程管理系统

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0422192D0 (en) * 2004-10-06 2004-11-03 Nokia Corp Transfer of a user equipment in a communication system
ES2421921T3 (es) 2005-10-04 2013-09-06 Ericsson Telefon Ab L M Control de acceso en una red de acceso por radio que tiene estaciones base de pico
US8072953B2 (en) * 2007-04-24 2011-12-06 Interdigital Technology Corporation Wireless communication method and apparatus for performing home Node-B identification and access restriction
US8165590B2 (en) * 2007-08-13 2012-04-24 Telefonaktiebolaget Lm Ericsson (Publ) Neighbor cell relation list initialization
CN105472572B (zh) * 2007-09-10 2020-01-07 蜂窝通信设备有限责任公司 封闭订户组的访问控制
CN101136826B (zh) * 2007-09-30 2011-01-05 中兴通讯股份有限公司 一种通过核心网控制终端接入家庭基站覆盖区域的方法
DK2198647T3 (en) * 2007-10-01 2019-02-18 Nokia Technologies Oy MEASUREMENT REPORT FOR CLOSED subscriber groups
US9167505B2 (en) * 2007-10-08 2015-10-20 Qualcomm Incorporated Access management for wireless communication
US9313769B2 (en) * 2008-01-14 2016-04-12 Qualcomm Incorporated Wireless communication paging and registration utilizing multiple types of node identifiers
US8942204B2 (en) * 2008-12-23 2015-01-27 Qualcomm Incorporated Access point handover control based on closed subscriber group subscription information
US8924535B2 (en) * 2008-12-23 2014-12-30 Qualcomm Incorporated Maintaining closed subscriber group information for access control
KR101471676B1 (ko) * 2008-12-30 2014-12-10 에릭슨 엘지 주식회사 셀 관리 방법 및 그를 위한 이동통신 시스템
KR101571730B1 (ko) 2009-01-09 2015-11-25 엘지전자 주식회사 무선 통신 시스템에서 ｃｓｇ 아이디 전송 방법
CA2749046A1 (fr) 2009-01-13 2010-07-22 Telefonaktiebolaget L M Ericsson (Publ) Abonnes nomades d'un reseau radio peripherique
BRPI0924130B1 (pt) * 2009-01-23 2021-05-18 Telefonaktiebolaget Lm Ericsson Métodos e arranjos para executar controle de acesso para um nó móvel e para auxiliar um nó de controle de rede em executar controle de acesso a um nó móvel

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
JP5484487B2 (ja) 2014-05-07
WO2010085191A1 (fr) 2010-07-29
US9258751B2 (en) 2016-02-09
CN102326429B (zh) 2015-11-25
US20140162654A1 (en) 2014-06-12
US8781472B2 (en) 2014-07-15
EP2382826A4 (fr) 2014-05-14
US20110281584A1 (en) 2011-11-17
BRPI0924130B1 (pt) 2021-05-18
JP2012516105A (ja) 2012-07-12
NO2382826T3 (fr) 2018-04-28
CN102326429A (zh) 2012-01-18
PT2382826T (pt) 2018-01-15
TWI482506B (zh) 2015-04-21
BRPI0924130A2 (pt) 2020-10-20
US20160165502A1 (en) 2016-06-09
CN105142147B (zh) 2019-02-12
TW201101867A (en) 2011-01-01
CN105142147A (zh) 2015-12-09
DK2382826T3 (en) 2018-01-08
MX2011007672A (es) 2011-08-08
EP2382826A1 (fr) 2011-11-02
US9661537B2 (en) 2017-05-23
ES2660191T3 (es) 2018-03-21

Similar Documents

Publication Publication Date Title
US9661537B2 (en) Method and arrangement in a communication network
EP2947903B1 (fr) Système et procédé d'identification d'un abonné dans un environnement de réseau
US8437743B2 (en) Access network discovery and selection function, ANDSF, node distributing closed subscriber group, CSG, information
KR101489882B1 (ko) 사용자 장비에 허용된 액세스 권리들에 관하여 셀 및 셀을 서빙하는 라디오 기지국을 사용자 장비에 알림
KR102198740B1 (ko) 로컬 ｉｐ 액세스 - ｌｉｐａ - 모빌리티를 지원하기 위한 방법 및 장치
US9807652B2 (en) System and method for providing handover to an ambiguous small cell access point in a network environment
US9167487B2 (en) Communication system including a gateway device and method thereof
US9479975B2 (en) Communication system
KR20120111905A (ko) 이동통신 네트워크 내에서 제어 평면을 담당하는 서버 및 액세스 제어 방법
US9699696B2 (en) System and method for providing handover to an ambiguous small cell access point in a network environment
US8428597B2 (en) RAN node and method thereof
US8452283B2 (en) Femtocell base station and method thereof

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

AK Designated contracting states

Kind code of ref document: A1

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

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602009049669

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0048180000

Ipc: H04W0012080000

A4 Supplementary search report drawn up and despatched

Effective date: 20140416

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 12/08 20090101AFI20140410BHEP

Ipc: H04W 48/02 20090101ALI20140410BHEP

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

Owner name: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL)

17Q First examination report despatched

Effective date: 20151029

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170120

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

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20170619

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 951404

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171215

Ref country code: CH

Ref legal event code: NV

Representative=s name: ISLER AND PEDRAZZINI AG, CH

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

Country of ref document: DE

REG Reference to a national code

Ref country code: DK

Ref legal event code: T3

Effective date: 20180105

REG Reference to a national code

Ref country code: PT

Ref legal event code: SC4A

Ref document number: 2382826

Country of ref document: PT

Date of ref document: 20180115

Kind code of ref document: T

Free format text: AVAILABILITY OF NATIONAL TRANSLATION

Effective date: 20180109

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: NO

Ref legal event code: T2

Effective date: 20171129

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2660191

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20180321

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602009049669

Country of ref document: DE

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

Ref country code: RO

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

Effective date: 20171129

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

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

26N No opposition filed

Effective date: 20180830

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

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

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180430

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

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

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

Ref country code: MT

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

Effective date: 20180407

REG Reference to a national code

Ref country code: AT

Ref legal event code: UEP

Ref document number: 951404

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171129

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

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 NON-PAYMENT OF DUE FEES

Effective date: 20171129

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

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230523

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

Ref country code: PT

Payment date: 20240325

Year of fee payment: 16

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

Ref country code: NL

Payment date: 20240426

Year of fee payment: 16

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

Ref country code: TR

Payment date: 20240320

Year of fee payment: 16

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

Ref country code: IE

Payment date: 20240429

Year of fee payment: 16

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

Ref country code: GB

Payment date: 20240429

Year of fee payment: 16

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

Ref country code: DE

Payment date: 20240429

Year of fee payment: 16

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

Ref country code: DK

Payment date: 20240425

Year of fee payment: 16

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

Ref country code: CH

Payment date: 20240501

Year of fee payment: 16

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

Ref country code: ES

Payment date: 20240503

Year of fee payment: 16

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

Ref country code: AT

Payment date: 20240320

Year of fee payment: 16

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

Ref country code: NO

Payment date: 20240429

Year of fee payment: 16

Ref country code: IT

Payment date: 20240422

Year of fee payment: 16

Ref country code: FR

Payment date: 20240425

Year of fee payment: 16