GB2501366A

GB2501366A - Authorisation of a visiting wireless communication unit by transferring personal data to an authorised wireless communication unit

Info

Publication number: GB2501366A
Application number: GB1303489.7A
Authority: GB
Inventors: Christopher Edward John Kilgour; Mark Edward Harrison
Original assignee: IP Access Ltd
Current assignee: IP Access Ltd
Priority date: 2012-02-27
Filing date: 2013-02-27
Publication date: 2013-10-23
Anticipated expiration: 2033-02-27
Also published as: GB201203316D0; GB201303489D0; GB201303487D0; GB2501366B

Abstract

When a new or visiting wireless communication unit requests authorisation to access a small cell, such as a Femto cell, then an authorised wireless communication unit (for example a master unit) receives and accepts the visiting wireless communication unit's request. It then performs a physical contact-enabled or contactless vicinity-based data transfer (this may include bumping the units together, near field communication (NFC), Bluetooth(RTM), Infra-Red (IRDA) or other short range wireless technology) of subscriber data from the visiting wireless communication unit. The master wireless device may then authorise the visiting wireless communication unit at the wireless communication unit to access the network. This removes the need for an owner of the Femto cell to manually update the whitelist or the closed subscriber group (CSG) access list to add the visiting wireless device.

Description

Title: COMMUNICATION UNIT, NETWORK ELEMENT, INTEGRATED CIRCUITS,

MANAGEMENT SYSTEM AND METHOD FOR AUTHORISING A USER

Description

Field of the invention

The field of this invention relates to a communication unit, an integrated circuit, a network element, a cellular communication system and a method therefor. The invention is applicable to, but not limited to, automatically enabling, for example authorising and adding, a new user to a restricted access small-cell whitelist.

Background of the Invention

Wireless communication systems, such as the 3 Generation (3G) of mobile telephone standards and technology, are well known. An example of such 3G standards and technology is the Universal Mobile Telecommunications System (UMTSTM), developed by the 3 Generation Partnership Project (3GPPTM) (www.3cipp.orci). The 3rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications. Such macro cells utilise high power base stations (NodeBs in 3GPPTM parlance) in order to communicate with wireless communication units within a relatively large geographical coverage area. Typically, wireless communication units, or User Equipment (UEs) as they are often referred to in 3G parlance, communicate with a Core Network (CN) of the 3G communication system via a Radio Access Network (RAN). A wireless cellular communication system typically comprises a plurality of radio network subsystems, each radio network subsystem comprising one or more (coverage) cells to which UEs may attach', and thereby connect to the network. Each macro-cellular RAN further comprises a controller, in a form of a Radio Network Controller (RNC), operably coupled to the one or more Node Bs, via a so-called lub interface.

Lower power (and therefore smaller coverage area) femto cells (or pico-cells) are a recent development within the field of wireless cellular communication systems. Femto cells or pico-cells (with the term femto cells being used hereafter to encompass pico-cells or similar) are effectively communication coverage areas supported by low power base stations (otherwise referred to as Access Points (AP5) or Home Node Bs (HNB5) or Home enhanced Node Bs (HeNB5)). These femto cells are intended to be able to co-deployed with the more widely used macro-cellular network and support communications to UEs in a restricted, for example inbuilding, environment.

Typical applications for such femto APs/HNB5 include, by way of example, residential and commercial (e.g. office) locations, communication hotspots', etc., whereby APs/HNBs can be connected to a core network via, for example, the Internet using a broadband connection or the like.

In this manner, femto cells can be provided in a simple, scalable deployment in specific in-building locations where, for example, UEs may come into close proximity to a femto AP/HNB. Thus, femto APs/HNBs are intended to enhance the coverage of a UMTSTM Radio Access Network (RAN) within residential and/or private commercial environments, and it is planned that the number of femto HNBs in a macro cell may number thousands. In the case of such deployments it can be desirable for the operator or femtocell owner to permit access to a femtocell for only a limited number of approved users or to provide certain users an enhanced service. There are two primary modes of operation whereby a UE is able to attempt to access such a femto cell, in order to communicate with other elements within the communication system. A first mode is a Closed access mode, whereby a H(e)NB provides services only to its associated Closed Subscriber Group (CSG) members. A second mode is a hybrid access mode, whereby a H(e)NB provides services to its associated CSG members as well as to non-CSG members.

Referring now to the drawings, and in particular FIG. 1, a simplified example of part of a known cellular communication system is illustrated. In FIG. 1, there is illustrated a third generation partnership project (3GPFTM) Universal Mobile Telecommunication System (UMTSTM) network that illustrates access control for in-bound mobility to a closed subscriber group (CSG) cell or hybrid cell of a femto cell 100. A CSG identifies those subscribers of an operator that are permitted to access one or more cells of the public land mobile network (PLMN). For the example femto cell embodiment illustrated in FIG. 1, a radio network sub-system comprises an access point, also known as a Home NodeB (HNB), that is arranged to perform a number of functions generally associated with a cellular communication base station, as well as a master communication unit (typically referred to as a user equipment (UE) in 3GPP parlance) 104 that is allowed to operate in the femto cell system 100, with a second (candidate) UE 102 attempting to access (sometimes referred to as handover to) the femto cell system 100.

It can be desirable to encourage communication devices to utilize a femto cell 100 owned/operated by a subscriber, and content and services available via the femto cell 100, as it can facilitate communication of information between communication devices and respective users of those communication devices and/or can generate income for the subscriber that owns/operates the femto cell 100. It also can be desirable to manage access of wireless communication devices to a femto cell and associated content and services to facilitate efficient use of bandwidth, and content and services, associated with the femto cell 100 and ensure that desired users can access the femto cell 100. The femto cell 100 comprises a means for a network element to facilitate authorizing, denying, revoking, and/or terminating access to the femto cell 100 from one or more specific UEs, comprising what is generally referred to as a White List(s)' (e.g., access control list(s)) that is an instrument that can facilitate management of access to femto cell 100 coverage.

In FIG. 1, the candidate UE 102 reads the CSG ID, access mode and optionally the Cell Global ID (CGD/Cell Identity of the target cell, which in this example is closed or hybrid femto cell 100 and compares the CSG ID of the HNB 110 of the target cell to its CSG whitelist in order to determine whether the candidate UE 102 is a member of the CSG advertised by the HNB 110 of the target cell. If the candidate UE 102 is a member of the CSG advertised by the HNB 110 of the target cell, the candidate UE 102 selects the CSG cell.

The femto cell system 100 also comprises a controller in a form of a 3G Home NodeB Gateway (HNB-GW) 132 and a security gateway 130 operably coupled to processing logic 112 in the HNB 110 via an luh interface. An HNB 110 is a communication element that supports communications within a communication cell, such as a femto cell system 100, and as such may provide access to a cellular communication network via the femto cell.

The 3G HNB-GW 132 is coupled to the core network (ON), and in particular a whitelist management Authentication, Authorization and Accounting (AAA) server 128 configured for applications such as Network access, via an lu interface or other alternative interface. The whitelist management MA server 128 provides authorization, policy enforcement and routing information to the HNB 110. In this manner, the HNB 110 is able to provide voice and data services to a cellular handset, such as UE 104. In more recent instantiations of 3GPPTM standards (3GPPTM Rel-8 and after) the access control and CSG membership checking may also be provided by a CSG list' management server in the ON that records and regulates those CSG cells that a particular UE has access to. It will be appreciated that there is a one-to-one mapping between the whitelist for a cell and the set of UEs that have that same cell as a member of their CSG lists. The two mechanisms are thus logically interchangeable.

Adding a new member to the permitted whitelist' for a cell in the femto cell system 100 has only, so far, been carried out by one of the following mechanisms. First, the cell owner (bill payer, e.g. that of the Master UE 102) and the Network Operator to approve any new addition, say via the cell owner's internet access 120, which downloads a Candidate UE's identifier, say in a form of the Mobile Station Integrated Services Digital Network (MSISDN) 122 into the Operators customer relations management (CRM) portal 124. This whitelist information is accessible by the AAA server 128 over a link to the TR-069 management system, 126. The key identity in the whitelist (for a 3GPPTM femto cell) is the International Mobile Subscriber Identity (IMSI) of the phone, stored on its SIM card, which may be determined from a Network Operator-to a Customer relations management (ORM) portal 124 of the Network Operator. Secondly, a telephone call may be made by such a responsible user to a customer support centre, which adapts the whitelist. These mechanisms have the disadvantage that they are time consuming, may decrease the customer experience, and the second option is also costly to the Network Operator.

Thus, a need exists for authorising and adding, a new user to, say, a restricted access, small-cell, whitelist or Cellular Subscriber Group (CSG) list.

Summary of the invention

Accordingly, the invention seeks to mitigate, alleviate or eliminate one or more of the above mentioned disadvantages, either singly or in any combination. Aspects of the invention provide a communication unit, a network element, an integrated circuit, a cellular communication system, a method and tangible computer product for authorising and adding, a new user to, say, a restricted access, small-cell, whitelist, as described in the appended claims.

These and other aspects of the invention will be apparent from, and elucidated with reference to, the embodiments described hereinafter.

Brief Description of the Drawings

Further details, aspects and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. Like reference numerals have been included in the respective drawings to ease understanding.

FIG. 1 illustrates a known example of part of a cellular communication system.

FIG. 2 illustrates a first example of a simplified block diagram of a communication unit and communication system adapted to authorise and add, a new user to, say, a restricted access, small-cell, whitelist.

FIG. 3 illustrates a second example of a simplified block diagram of a communication unit and communication system adapted to authorise and add, a new user to, say, a restricted access, small-cell, whitelist.

FIG. 4 illustrates an example of a simplified block diagram of a communication unit adapted to perform a contact-based or contact-less based transfer of UE data for use in authorising and adding the UE to, say, a restricted access, small-cell, whitelist.

FIG. 5 illustrates a simplified flowchart of a method for performing a contact-based or contact-less based transfer of UE data for use in authorising and adding the UE to, say, a restricted access, small-cell, whitelist.

FIG. 6 illustrates a simplified flowchart of a method for authorising and adding, a new user to, say, a restricted access, small-cell, whitelist.

FIG. 7 illustrates a typical computing system that may be employed to implement signal processing functionality in example embodiments.

Detailed Description

Examples of the invention will be described in terms of exchange of information between communication units, and in particular to use the bumpTM service or a similar physical contact or geographical vicinity communication technique (such as any form of authenticated, approvable wireless local loop) to add subscribers to a femto whitelist within a 3rd generation (3G) Radio Network Sub-system (RNS) for supporting one or more femto cells within a Universal Mobile Telecommunications System (UMTSTM) cellular communication network. However, it will be appreciated by a skilled artisan that the inventive concept herein described may be embodied in any type of communication unit that is able to exchange information within a cellular communication network. In particular, it is contemplated that the inventive concept is not limited to being implemented within a UE-based communication unit, within a UMTSTM cellular communication network, but may be equally applied within one or more communication unit(s) adapted to function in any type of communication cell, e.g. one or more macro cells, and/or adapted in accordance with alternative cellular communication technologies.

Examples of the invention may facilitate removal of the current need for manual (e.g. non-automated) identification of identification parameters for a new UE, in particular by use of proximity and presence techniques. Examples of the invention may also implicitly support authorisation by a designated femto cell owner by virtue of the message being validated by a link to, and an application on, his/her handset. In particular, in some examples of the invention, a new use in a different application of the Bump' concept, or similar technology, utilises a link to a network element in the Network Operator femto cell management infrastructure, say from the Bump servers, in order to access the approval message that enables the authorisation to be carried out automatically.

In some examples of the invention, a plurality of communication units have been adapted to authorise transfer of a femto cell whitelist simply by bumping or operationally contacting two phones together. BumpTM is a service currently supported by some smartphones, basically through applications (apps) on the phones that can access the bump service, whereby when two phones are physically knocked together with some force they transfer data via the Bump server in the cloud. In some examples of the invention, a plurality of communication units have been adapted to authorise transfer of a femto cell whitelist simply by other physical contact means, rather than applying a physical communication connection via a wired link. In some examples of the invention, a plurality of communication units have been adapted to authorise transfer of a femto cell whitelist through any means of geographical vicinity, such as a wireless local loop. In some examples of the invention, the same communication app' may be installed on a plurality of communication units. In some examples of the invention, various compatible communication apps', rather than the same app, may be installed on a plurality of communication units.

In some examples of the invention, the communication app' may be pre-installed on many or substantially all of the Network Operator's smartphones/communication units. In some examples of the invention, the app may be configured to automatically activate a contact-based data transfer when the user registers at a femto cell access point (FAR). In the context of example embodiments of the present invention, contact-based data transfer encompasses any physical contact-enabled initiation of a data transfer. In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, the master UE may transfer the candidate UE's (transferred) IMSI or mobile phone number (MSISDN) to the network, either via a wireless connection, cellular connection, or when next connected via a wired connection to the AP or HNB. In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, both the master UE and the visitor candidate) UE may transfer each other's access rights, for example the other UE's IMSI or MSISDN to the network, either via a wireless connection or when next connected via a wired connection to the AP or HNB, thereby confirming that an authorised whitelist update has taken place. Advantageously, a contact-based data transfer or contactless-based data transfer may be performed anywhere, and not just in the home. In some examples, the app may be configured to be activated by a key-code entry, or similar, in order to ensure that a contact-based data transfer or contactless-based data may not occur by accidental bumping or touching or knocking or being in the vicinity of one another.

Referring now to the drawings, and in particular FIG. 2, a simplified example of part of a cellular communication system, adapted to implement embodiments of the invention, is illustrated. In FIG. 2, there is illustrated a third generation partnership project (3GPPTM) Universal Mobile Telecommunication System (UMTSTM) network that illustrates access control for a closed subscriber group (CSG) cell or hybrid cell of a femto cell 210. For the example femto cell embodiment illustrated in FIG. 2, a radio network sub-system comprises an access point, also known as a Home NodeB (HNB), that is arranged to perform a number of functions generally associated with a cellular communication base station, as well as a master communication unit (typically referred to as a user equipment (UE) in 3GPP parlance) 204 that is allowed to operate in the femto cell 210, with a second (candidate) UE 202 wishing to access the femto cell 210.

In one example of FIG. 2, the candidate UE 202 is included on the master UEs 204 white list by physically bumping or touching 206 the candidate UE 202 with the master UE 204. In one example, the updated white list entry is then provided 203, 205 to the Network Operator's management and authorisation system, 224, 226, 228 utilising a normal cellular data connection via a cell 208. This management system, in turn, links the identity of the master UE 204 to one or more particular femto cells that the master UE 204 has control over, considers whether to authorise the candidate UE 202 from a Network Operator perspective and updates the whitelist for the cell or the CSG list for the candidate UE 202 accordingly.

Details of the Bump technique for exchanging general information between handsets, which is incorporated herein by reference, can be found described at: http://evolver.fm/201 1/01/1 4/bump-smartphone-p2p-music-sharinp/ and http://en.wikipedia.org/wiki/Bump %28application%29.

The BumpTM technology operates by having an application on each handset involved and then applying time and location correlation, as to when accelerometers in a handset measured the bump impulse'. In some examples, the bumpTM application installed on the master UE 204 and candidate UE 202 asks the UE's users what they wish to exchange. In known applications of bump', this information exchange is limited to contact details and photos, and a short while after the bump', the users receive a message saying that the data has been received and transferred. However, in examples of the invention, the bump1M application installed on the master UE 204 and candidate UE 202 automatically transfer UE identity information.

In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, the master UE may transfer the candidate UE's (transferred 203, 205) IMSI or MSISDN to the network, either via a wireless connection 203, 205, or when next connected via a wired connection, to any base station or cell that it is able to communicate with. In this context, cell A' may be a femto cell supported by HNB 208, or may be a modified open macro cell supported by a respective NodeB, modified to route access data transferred via a contact-less or contact-based operation. Indeed, in some cases, the master UE and candidate UE may be supported by different respective cells (or HNB(s) or NodeB(s)), in say, a peer-to-peer application system.

Indeed, so long as the master UE and the candidate UE are in close proximity to each other to effect a contactless data transfer, or they have been used in a contact-based transfer, using for example a bump technique, substantially any network element may be used to route the data.

If a bump' is used there is the possibility to extract information from the servers and forward the extracted information towards the management system, as well as just waiting for the information to arrive at the master UE and then the master UE initiating contact with the management system (e.g. an application located on the master UE may be configured to initiate a secure http data session).

The mobile core network 220 is operably coupled to a bump server 221, which is arranged to perform message filtering and/or message interception and/or message routing of candidate UE MSISDN and master UE identifier (e.g. MSISDN) 222 data to the Network Operator's TR-069 femto management system 226. If necessary the candidate UEs phone number (e.g. MSISDN 222) may have its corresponding IMSI linked to it.

In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, both the master UE and the visitor (candidate) UE may transfer in 203, 205 each other's access rights, for example the other UE's IMSI or MSISDN to the network, either via a wireless connection or when next connected via a wired connection to the AP or HNB, thereby confirming that an authorised whitelist update has taken place. In this manner, the candidate UE has acquired rights to use the femto cell in accordance with its acceptance on the master UE's white list.

The only known mechanism requires the cell owner (bill payer, e.g. that of the Master UE 202) and the Network Operator to approve and authorise changes to the cell's whitelist effectively off-line.

Thus, in contrast to the known mechanism, and in response to a specific request from the master UE or visiting UE, any new addition to the white list performed as described herein provide a simplified and substantially immediate, on-the-fly, whitelist change via direct access to a candidate UE's details, for example in a form of the candidate UE's phone number (MSISDN 222), or alternatively a permanent network identifier, such as the IMSI. This information arrives at the TR-069 management system 226 from the Operators customer relations management (CRM) portal 224. This whitelist information is accessible by the AM server 228. The key identity in the whitelist (for a 3GPPTM femtocell) is the IMSI of the phone, stored on its SIM card, which may be determined from a Network Operator to a Customer relations management (CRM) portal 224 of the Network Operator. In this manner, the master user (owner' of the femtocell whitelist) is able to control, and more importantly readily update, the whitelist by virtue of triggering an exchange that is authenticated by being linked to his/her own phone.

The femto cell system 200 also comprises a controller in a form of a 3G Home NodeB Gateway (HNB-GW) 232 and a security gateway 230 operably coupled via an luh interface to processing logic 212 in an access point, also known as a Home NodeB (HNB) 210. The HNB is arranged to perform a number of functions generally associated with a cellular communication base station and supports communications within a communication cell, such as a femto cell system 200. In particular, the HNB 210 may provide access to a cellular communication network via the femto cell.

The 3G HNB-GW 232 is coupled to the core network (CN), and in particular a whitelist management Authentication, Authorization and Accounting (AAA) server 228 configured for applications such as Network access, via an lu or other interface. The whitelist management AAA server 228 provides authorization, policy enforcement and routing information to the closed or hybrid HNB 210, which is the HNB that the master UE/owner controls and is allowing access to by the candidate UE 202. In this manner, the closed or hybrid HNB 210 is re-configured via updating of the whitelist to allow access by the candidate UE 202, irrespective of whether the candidate UE 202 is in the vicinity of the closed or hybrid HNB 210.

In some example embodiments, an HNB 210 may be purchased by a member of the public and installed in their home. The HNB 210 may be connected to an HNB-GW 230 via the luh interface, for example implemented over, say, the owner's broadband internet connection (not shown). Thus, the HNB 210 may be considered as encompassing a scalable, multi-channel, two-way communication device that may be provided within, say, residential and commercial (e.g. office) locations, communication hotspots' etc., to extend or improve upon network coverage within those locations. An example of a typical third generation (3G) HNB for use within a 3GFFTM system may comprise some macro cell NodeB functionality and some aspects of radio network controller (RNC) functionality.

Any identification token(s), label(s), or code(s) that can facilitate identifying a subscriber station can be employed to identify a subscriber station in a white list 220, or alternatively a black list that specifically identifies that UE as not being allowed access to the femto cell via the HNB 210, on a permanent or temporary basis.

Referring now to the drawings, and in particular FIG. 3, a simplified alternative example of part of a cellular communication system, adapted to implement embodiments of the invention, is illustrated.

In FIG. 3, there is illustrated a third generation partnership project (3GFPTM) Universal Mobile Telecommunication System (UMTSTIA) network that illustrates access control for a closed subscriber group (CSG) cell or hybrid cell of a femto cell 300. For the example femto cell embodiment illustrated in FIG. 3, a radio network sub-system comprises an access point, also known as a Home NodeB (HNB), that is arranged to perform a number of functions generally associated with a cellular communication base station, as well as a master communication unit (typically referred to as a user equipment (UE) in 3GPP parlance) 304 that is allowed to operate in the femto cell 310, with a second (candidate) UE 302 wishing to access the femto cell 310.

In one example of FIG. 3, the candidate UE 302 is included on the master UE's 304 white list by physically bumping or touching 305 the candidate UE 302 with the master UE 304. In one example, the updated white list entry is then provided 305 to the core network and thence to the operator CRM portal via a data connection utilising Cell A 308. In some examples, an application on the master UE 304 acquires the candidate UE 302 (phone) details via Bump or direct methods, and the master UE 304 creates its own registration of the details with the management system. In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, the master UE may transfer the candidate UE's IMSI or MSISDN to the network, either via a wireless connection 305, or when next connected via a wired connection, to a neighbouring AP or HNB 308.

Signal processor module 319 then transfers the updated whitelist information, obtained via the contact-based data transfer or contactless-based data transfer to the mobile core network 320. In some examples, the signal processor module 319 may be incorporated into an integrated circuit. The mobile core network 320 is operably coupled to a bump server 221, which is arranged to perform message filtering and/or message interception and/or message routing of candidate UE MSISDN 322 data to the Network Operator's TR-069 femto management system 326.

In some examples of the invention, once a contact-based data transfer or contactless-based data transfer has been performed, the master UE may transfer the candidate UE's (transferred 305) IMSI or MSISDN to the network, either via a wireless connection 305, or when next connected via a wired connection, to any base station or cell that it is able to communicate with. In this context, cell A' may be a femto cell supported by HNB 308, or may be a modified open macro cell supported by a respective NodeB, modified to route access data transferred via a contact-less or contact-based operation. Indeed, in some cases, the master UE and candidate UE may be supported by different respective cells (or HNB(s) or NodeB(s)), in say, a peer-to-peer application system. Indeed, so long as the master UE and the candidate UE are in close proximity to each other to effect a contactless data transfer, or they have been used in a contact-based transfer, using for example a bump technique, substantially any network element may be used to route the data.

In this manner, the data transfer from the master UE 304 confirms that an authorised whitelist update should take place In this manner, thereby allowing the candidate UE 302 to acquire rights to use the femto cell 310 of the master UE 304 in accordance with its acceptance on the master UE's white list.

The only known mechanism requires the cell owner (bill payer, e.g. that of the Master UE 302) and the Network Operator to approve and authorise changes to the cell's whitelist effectively off-line.

Thus, in contrast to the known mechanism, and in response to a specific request from the master UE or visiting UE, any new addition to the white list performed as described herein provide a simplified and substantially immediate, on-the-fly, whitelist change via direct access to a candidate UE's details, for example in a form of the candidate UE's phone number (MSISDN 322), or alternatively a permanent network identifier, such as the IMSI. This information arrives at the TR-069 management system 326 from the Operators customer relations management (CRM) portal 324. This whitelist information is accessible by the AM server 328. The key identity in the whitelist (for a 3GPPTM femtocell) is the IMSI of the phone, stored on its SIM card, which may be determined from a Network Operator to a Customer relations management (CRM) portal 324 of the Network Operator. In this manner, the master user (owner' of the femtocell whitelist) is able to control, and more importantly readily update, the whitelist by virtue of triggering an exchange that is authenticated by being linked to his/her own phone.

The femto cell system 300 also comprises a controller in a form of a 3G Home NodeB Gateway (HNB-GW) 332 and a security gateway 330 operably coupled via an luh interface to processing logic 312 in an access point, also known as a Home NodeB (HNB) 310. The HNB is arranged to perform a number of functions generally associated with a cellular communication base station and supports communications within a communication cell, such as a femto cell system 300. In particular, the HNB 310 may provide access to a cellular communication network via the femto cell.

The 3G HNB-GW 332 is coupled to the core network (CN), and in particular a whitelist or CSG list management Authentication, Authorization and Accounting (AM) server 328 configured for applications such as Network access, via an lu or other interface. The whitelist management AAA server 328 provides authorization, policy enforcement and routing information to the closed or hybrid HNB 310, which is the HNB that the master UE/owner controls and is allowing access to by the candidate UE 302. In this manner, the closed or hybrid HNB 310 is re-configured via updating of the whitelist to allow access by the candidate UE 302, irrespective of whether the candidate UE 302 is in the vicinity of the closed or hybrid HNB 310.

In some example embodiments, an HNB 310 may be purchased by a member of the public and installed in their home. The HNB 310 may be connected to an HNB-GW 330 via the luh interface, for example implemented over, say, the owner's broadband internet connection (not shown). Thus, the HNB 310 may be considered as encompassing a scalable, multi-channel, two-way communication device that may be provided within, say, residential and commercial (e.g. office) locations, communication hotspots' etc., to extend or improve upon network coverage within those locations. An example of a typical third generation (3G) HNB for use within a 3GFFTM system may comprise some macro cell NodeB functionality and some aspects of radio network controller (RNC) functionality.

Any identification token(s), label(s), or code(s) that can facilitate identifying a subscriber station can be employed to identify a subscriber station in a white list, or alternatively a black list that specifically identifies that UE as not being allowed access to the femto cell via the HNB 210, on a permanent or temporary basis.

As will be apparent to someone skilled in the art, a physical bump' is not needed for any particular instantiation of this invention, as any mechanism that facilitates an automatic delivery of contact details towards the network management system is envisaged. Consequently, it is envisaged that there are other ways of realising examples of the invention, such as indicated in FIG. 3. In such a scenario, a single application on the cell controller's handset may be employed, which is arranged to make use of short range wireless technologies, such as Near Field Communication (NFC), Bluetooth, Infra-Red Data Association (IRDA) and so on, in order to trigger exchange the key information -namely the mobile phone number (MSISDN) of the candidate whitelist device. This can be received in existing standard ways from mobile phones with usual features, such as support of the vCard address/contact file format -thereby obviating a need for the added phone to support custom applications.

If the operator approves the candidate UE identity then the new entry is added to the whitelist and pushed towards the access control database of the femto layer.

Referring now to FIG. 4 for completeness, an example of a simplified block diagram of a UE 202, 204, 302, 304 is shown. The example femto UE 202, 204, 302, 304 contains an antenna 402 coupled to the transceiver circuitry 455. More specifically for the illustrated example, the antenna 402 is preferably coupled to a duplex filter or antenna switch 204 that provides isolation between receive and transmit chains within the femto UE 202, 204, 302, 304.

The receiver chain, as known in the art, includes receiver front-end circuitry 406 (effectively providing reception, filtering and intermediate or base-band frequency conversion). The front-end circuitry 406 is serially coupled to the UE's signal processing module 212, 216, 312, 316. An output from the signal processing module 212, 216, 312, 316 is provided to a user interface for example a display or touch screen. A UE controller 414 is also coupled to the receiver front-end circuitry 406 and the signal processing module 212, 216, 312, 316 (typically realised by a digital signal processor (DSP)). The controller 414 and signal processing module 212, 216, 312, 316 are also coupled to at least one memory device 416 that selectively stores operating regimes, such as decoding/encoding functions, synchronisation patterns, code sequences, UE identification data and the like.

As regards the transmit chain, this essentially includes an input element, such as a keyboard or touch screen 412, operably coupled in series through transmitter/modulation circuitry 422 and a power amplifier 424 to the antenna 402. The transmitter/modulation circuitry 422 and the power amplifier 424 are operationally responsive to the controller 414, and as such are used in transmitting UE identification data to a wireless network element, such as femto HNB 208, 308.

The signal processor module 212, 216, 312, 316 in the transmit chain may be implemented as distinct from the processor function in the receive chain. Alternatively, a single processor may be used to implement processing of both transmit and receive signals, as shown in FIG. 4. Clearly, the various components within the femto UE 202, 204, 302, 304 can be realised in discrete or integrated component form, with an ultimate structure therefore being merely an application-specific or design selection. In some examples, the signal processor module 212, 216, 312, 316 and/or an associated bump sensor of the femto UE 202, 204, 302, 304 may be incorporated into an integrated circuit.

In accordance with examples of the invention, the memory device 416 stores the UE's details, for example the candidate UE's phone number (MSISDN 222 of FIG. 2) and computer-readable code thereon for programming the signal processing module 212, 216, 312, 316. In response to a user initiating a Bump process (or the like), or initiating a contactless-based connection, via user interface 410, the signal processing module 212, 216, 312, 316 and transmitter chain is able to perform a method for contact-based or contactless-based data transfer of the UE details to wireless network element, such as femto HNB 208, 308. In this manner, the UE's information transferred in this manner may be used to authorise and add the UE to, say, a restricted access, small-cell, whitelist.

Referring now to FIG. 5 there is illustrated a simplified flowchart 500 of a method for transfer a wireless communication unit's subscriber data, for example as may be implemented within the signal processing module, 212, 312, of the respective master UE 202, 302, of FIG's 2 and 3. The method of operation at the Master UE, starts at 510, and moves on to 520 with the Master UE owner/user accepts visiting UE's request to join whitelist. In 530, the Master UE owner/user and visiting UE activate a bump (or similar) or contactless vicinity-based data transfer application. In 540, if there is a contact-based data transfer, the Master UE owner/user and visiting UE perform bump operation (or similar) to transfer data. In 550, either the master UE or both the master UE and visiting UE transfer data to the femtocell management system, which may be directly in the case of the master UE making -12-direct contact, or which may be indirectly in the case of an application server filtering relevant messages. The method then ends at 560.

Referring now to FIG. 6 there is illustrated a simplified flowchart 600 of a method for transfer a wireless communication unit's subscriber data, for example as may be implemented within the signal processing module 219, 319, of the respective HNB 208, 308 of FIG's 2 and 3. The method of operation at the signal processing module 219, 319, of the respective HNB 208, 308, starts at 610, and moves on to 620 with the Operator management system receiving authorised data from either a master UE or via a bump (or similar operation) server identifying master UE and candidate UEs and, optionally closed or hybrid femtocell identity if the master UE owner controls more than one. In 630, the Operator management decides whether to authorise the candidate UE and resolves candidate UE identity to an IMSI if necessary. In 640, (if the response in 630 was yes') the Operator management system updates TR-069 management system for the identified femtocell and AAA Whitelist serve. In 650, the Master UE receives confirmation whether candidate UE has been added to the whitelist for the identified femtocell. The method then ends at 660.

Thus, in the above manner, physical touching of UEs/wireless communication units/handsets, or UEs/wireless communication units/handsets placed in close proximity is used to generate a message identifying the touched or nearby device, which is sent to the network provisioning system.

Advantageously, such a technique facilitates a literally one-touch' provisioning mechanism in order to enable a UE/wireless communication unit/handset to be added to a whitelist. Furthermore, and advantageously, such a technique facilitates better ease of use in adding devices to a communication cell's whitelist, such as femto cell, as well as better customer experience. Additionally, the technique to add the UE/wireless communication unit/handset to a whitelist provides a reduction in cost to a Network Operator.

Referring now to FIG. 7, there is illustrated a typical computing system 700 that may be employed to implement signal processing functionality in embodiments of the invention. Computing systems of this type may be used in access points (HNB5), base transceiver stations and wireless communication units. Those skilled in the relevant art will also recognize how to implement the invention using other computer systems or architectures. Computing system 700 may represent, for example, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment. Computing system 700 can include one or more processors, such as a processor 704. Processor 704 can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module. In this example, processor 704 is connected to a bus 702 or other communications medium.

Computing system 700 can also include a main memory 708, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by processor 704. Main memory 708 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Computing system 700 may likewise include a read only memory (ROM) or other static storage device coupled to bus 702 for storing static information and instructions for processor 704.

The computing system 700 may also include information storage system 710, which may include, for example, a media drive 712 and a removable storage interface 720. The media drive 712 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive.

Storage media 718 may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive 712. As these examples illustrate, the storage media 718 may include a computer-readable storage medium having particular computer software or data stored therein.

In alternative embodiments, information storage system 710 may include other similar components for allowing computer programs or other instructions or data to be loaded into computing system 700. Such components may include, for example, a removable storage unit 722 and an interface 720, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units 722 and interfaces 720 that allow software and data to be transferred from the removable storage unit 718 to computing system 700.

Computing system 700 can also include a communications interface 724. Communications interface 724 can be used to allow software and data to be transferred between computing system 700 and external devices. Examples of communications interface 724 can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via communications interface 724 are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by communications interface 724. These signals are provided to communications interface 724 via a channel 728. This channel 728 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of a channel include a phone line, a cellular phone link, an RF link, a network interface, a local or wide area network, and other communications channels.

In this document, the terms computer program product', computer-readable medium' and the like may be used generally to refer to tangible media such as, for example, memory 708, storage device 718, or storage unit 722. These and other forms of computer-readable media may store one or more instructions for use by processor 704, to cause the processor to perform specified operations.

Such instructions, generally referred to as computer program code' (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 700 to perform functions of embodiments of the present invention. Note that the code may directly cause the processor to perform specified operations, be compiled to do so, and/or be combined with other -14-software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system 700 using, for example, removable storage drive 722, drive 712 or communications interface 724. The control module (in this example, software instructions or executable computer program code), when executed by the processor 704, causes the processor 704 to perform the functions of the invention as described herein.

Furthermore, the inventive concept can be applied to any circuit for performing signal processing functionality within a network element. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP), or application-specific integrated circuit (ASIC) and/or any other sub-system element.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to a single signal processing module. However, the inventive concept may equally be implemented by way of a plurality of different functional units and processors to provide the signal processing functionality. Accordingly, it will be understood that the term signal processing module' used herein is intended to encompass one or more signal processing functional units, circuits and/or processors. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as FPGA devices. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term comprising' does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to a', an', first', second', etc. do not preclude a plurality.

Thus, an improved method and communication unit for automatically enabling, for example authorising and adding, a new user to a restricted access small-cell whitelist have been described, wherein the aforementioned disadvantages with prior art arrangements have been substantially alleviated.

Claims

Claims (GB) 1. A method for transfer of a visiting wireless communication unit's subscriber data, the method comprising, at a wireless communication unit: receiving and accepting a visiting wireless communication unit's request to be an authorised unit; performing a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; and authorising the visiting wireless communication unit at the wireless communication unit.
2. The method of Claim 1 further comprising sending the transferred data to a management system to authorise the visiting wireless communication unit at the management system.
3. The method of Claim 2 wherein sending the transferred data to a management system is performed either directly by the wireless communication unit, or indirectly via an application server filtering authorisation messages passing therethrough.
4. The method of Claim 2 or Claim 3 wherein sending the transferred data to a management system comprises sending at least one transferred Mobile Station Integrated Services Digital Network (MSISDN) to the management system.
5. The method of any of preceding Claims 2 to 4 wherein sending the transferred data to a management system is performed via at least one from a group of: a wireless connection, a cellular connection, upon accessing a wired connection to a base station.
6. The method of any preceding Claim further comprising automatically activating a physical contact-enabled data transfer when the wireless communication unit registers at a base station.
7. The method of any preceding Claim wherein the visiting wireless communication unit's request to be an authorised unit comprises a request to join the wireless communication unit's whitelist
8. The method of any preceding Claim wherein a physical contact-enabled data transfer of subscriber data from the visiting wireless communication unit comprises performing a bump operation between the wireless communication unit and the visiting wireless communication unit.
9. The method of any preceding Claim wherein performing a physical contact-enabled data transfer of subscriber data from the visiting wireless communication unit comprises applying at least one of: time correlation, location correlation, to determine whether a physical contact-enabled data transfer has occurred.
10. The method of any preceding Claim wherein performing a physical contact-enabled data transfer of subscriber data from the visiting wireless communication unit occurs when an accelerometer in the wireless communication unit identifies a physical contact-enabled impulse.
11. The method of any preceding Claim further comprising receiving and accepting a visiting wireless communication unit's request to be an authorised unit further to an activation of a security mechanism.
12. The method of Claim 11 wherein the security mechanism is a key code entry.
13. The method of any preceding Claim further comprising extracting information from a server and forwarding the extracted information to the management system.
14. The method of Claim 13 wherein the data transfer from the wireless communication unit confirms that an authorised visiting communication unit update should be effected in the management system.
15. The method of any preceding Claim wherein the management system is a femtocell management system.
16. The method of any preceding Claim wherein the contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit comprises using at least one from a group of: a short range wireless technology, near field communication (NFC), Bluetooth, Infra-red data association (IRDA).
17. A tangible computer program product having program code stored thereon for transfer of a visiting wireless communication unit's subscriber data, the program code operable for, when executed at a wireless communication unit, performing the method of any preceding Claim.
18. A wireless communication unit for receiving a transfer of a visiting wireless communication unit's subscriber data, the wireless communication unit comprising a signal processor arranged to: receive and accept a visiting wireless communication unit's request to be an authorised unit; perform a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; and authorise the visiting wireless communication unit at the wireless communication unit.
19. An integrated circuit for a wireless communication unit for receiving a transfer of a visiting wireless communication unit's subscriber data, the integrated circuit comprising a signal processor arranged to: receive and accept a visiting wireless communication unit's request to be an authorised unit; perform a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; and authorise the visiting wireless communication unit at the wireless communication unit.
20. A method for transfer of a visiting wireless communication unit's subscriber data, the method comprising, at a management system: receiving authorised subscriber data from a wireless communication unit direct or via a contact-based server, wherein the authorised subscriber data is obtained following a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; identifying a recipient wireless communication unit and a visiting wireless communication unit; and, determining a profile of the recipient wireless communication unit and in response thereto authorising the visiting wireless communication unit to be approved to communicate with the recipient wireless communication unit.
21. The method of Claim 20 further comprising linking the identity of the recipient wireless communication unit to one or more base stations that the recipient wireless communication unit has access to.
22. The method of Claim 20 or Claim 21 further comprising identifying a closed or hybrid base station identity if the recipient wireless communication unit is associated with more than one base station.
23. The method of any of preceding Claims 20 to 22 further comprising authorising the recipient wireless communication unit by updating an approved list for the base station
24. The method of any of preceding Claims 20 to 23 further comprising resolving the visiting wireless communication unit's identity to an IMSI.
25. The method of Claim 24 further comprising updating the management system for an identified base station and recipient wireless communication unit approved list in response to a positive resolution of the visiting wireless communication unit's identity.
26. The method of any of preceding Claims 20 to 25 wherein receiving the transferred data is performed via at least one from a group of: a wireless connection, a cellular connection, upon the recipient wireless communication unit accessing a wired connection to a base station.
27. The method of any of preceding Claims 20 to 26 further comprising transmitting confirmation that visiting wireless communication unit's subscriber data has been added to the recipient wireless communication unit approved list for an identified base station.
28. The method of any of preceding Claims 20 to 27 wherein receiving authorised subscriber data from a wireless communication unit via a contact-based server enables the authorisation to be carried out automatically.
29. The method of any of preceding Claims 20 to 28 wherein the recipient wireless communication unit and the visiting wireless communication unit are supported by different respective base stations.
30. A tangible computer program product having program code stored thereon for transfer of a visiting wireless communication unit's subscriber data, the program code operable for, when executed at a management system, performing the method of any of preceding Claims 20 to 29.
31. A management system for receiving a transfer of a visiting wireless communication unit's subscriber data, the wireless communication unit comprising a signal processor arranged to: receive authorised subscriber data from a wireless communication unit direct or via a contact-based server, wherein the authorised subscriber data is obtained following a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; identify a recipient wireless communication unit and a visiting wireless communication unit; and, determine a profile of the recipient wireless communication unit and in response thereto authorising the visiting wireless communication unit to be approved to communicate with the recipient wireless communication unit.
32. An integrated circuit for a management system for receiving a transfer of a visiting wireless communication unit's subscriber data, the integrated circuit comprising a signal processor arranged to: receive authorised subscriber data from a wireless communication unit direct or via a contact-based server, wherein the authorised subscriber data is obtained following a physical contact-enabled or contactless vicinity-based data transfer of subscriber data from the visiting wireless communication unit; identify a recipient wireless communication unit and a visiting wireless communication unit; and, determine a profile of the recipient wireless communication unit and in response thereto authorising the visiting wireless communication unit to be approved to communicate with the recipient wireless communication unit.