Provisioning communication nodes

Prepare communication nodes {PROVISIONING COMMUNICATION NODES}

This application is a jointly owned US Provisional Patent Application Serial No. 60/978,363, filed Oct. 8, 2007, Attorney Docket No. 080042P1; U.S. Provisional Patent Application No. 61/025,686, filed February 1, 2008, Attorney Docket No. 080745P1; and U.S. Provisional Patent Application No. 61/061,537, filed June 13, 2008, Attorney Docket No. 081811P1, the invention of each of those provisional applications is incorporated herein by reference.

BACKGROUND This application relates generally to wireless communication, and more specifically to improving communication performance, but is not limited thereto.

Wireless communication systems are widely deployed to provide various types of communication (eg, voice, data, multimedia services, etc.) to multiple users. As the demand for high-rate and multimedia data services rapidly increases, the challenge is to implement efficient and robust communication systems with improved performance.

To supplement conventional mobile phone network base stations, small-coverage base stations may be deployed (eg, installed within a user's home). In some aspects, such base stations may provide more robust indoor wireless coverage to mobile units. These small-coverage base stations are generally known as access point base stations, Home NodeBs, or femto cells. Typically, these small-coverage base stations are connected to the Internet and the mobile operator's network via a DSL router or cable modem.

In some scenarios, small-coverage base stations may be deployed in an ad-hoc fashion. As a result, problems associated with accessing these base stations may exist. For example, access terminals may need to be configured to access their associated base stations. It may also be desirable to prevent unlicensed access terminals from accessing certain base stations. Accordingly, there is a need for improved access management for wireless networks.

A summary of exemplary aspects of the invention is provided. Any reference to the term aspects herein may refer to one or more aspects of the invention.

The present invention relates in some aspects to provisioning communication nodes and providing access management for wireless communication. For example, identifiers may be assigned to sets of nodes, where the identifiers may be used to control access to restricted access points that provide certain services only to a defined set of access terminals. Here, the restricted access point may provide, for example, a particular service (eg, different billing, additional services, different quality of service) for the access terminals of one or more preferential users but not for other users.

In some aspects, preparing a node may include providing a unique identifier for a set of one or more nodes. For example, a unique identifier may be assigned to one or more restricted access points. Likewise, a unique identifier may be assigned to a set of access terminals authorized to receive service from one or more restricted access points. In some aspects, an access terminal may be assigned a temporary identifier, whereby access to a node may include mapping the temporary identifier to a permanent identifier for the access terminal.

Through the use of these identifiers, a desired level of access control can be achieved, although nodes can be provisioned in an ad-hoc manner. In some aspects, access control may be provided by a restricted access point. In some aspects, access control may be provided by a network node. In some aspects, access control may be provided by cooperation of a restricted access point and a network node.

The present invention relates in some aspects to provisioning a node with a preferred roaming list. In some aspects, a node may be provisioned with a default preferred roaming list that it may use to obtain another preferred roaming list to access restricted access points. In some aspects, a node with a preferred roaming list may be provisioned through the use of a bootstrap beacon.

These and other exemplary aspects of the invention will be set forth in the following detailed description and accompanying drawings. 1 is a simplified block diagram of some illustrative aspects of a communication system. 2 is a flow diagram of some example aspects of operations that may be used to prepare network nodes and provide access control. 3 is a simplified diagram of some example network node components. 4 is a flow diagram of some example aspects of operations that may be used to prepare an access point. 5 is a flow diagram of some example aspects of operations that may be used to prepare an access terminal. 6 is a flow diagram of some example aspects of operations that may be used to prepare an access terminal. 7 is a flow diagram of some example aspects of operations that may be used to provide access control. 8 is a flow diagram of some example aspects of operations that may be used to provide access control. 9 is a flow diagram of some example aspects of operations that may be used to provide access control. 10 is a flow diagram of some example aspects of operations that may be used to provide access control. 11 is a flow diagram of some example aspects of operations that may be used to provide access control. 12 is a flow diagram of some example aspects of operations that may be used to prepare an access terminal. 13 is a flow diagram of some example aspects of operations that may be used to provide access control. 14 is a simplified diagram of a wireless communication system. 15 is a simplified diagram of a wireless communication system including femto nodes. 16 is a simplified diagram illustrating coverage areas for wireless communication. 17 is a simplified block diagram of some example aspects of communication components. 18-28 are simplified block diagrams of some illustrative aspects of an apparatus configured to provide provisioning and/or access management as described herein. In accordance with common practice, various features shown in the drawings may not be drawn to scale. Accordingly, the dimensions of various features may be arbitrarily expanded or reduced for clarity. Also, some of the drawings may be simplified for clarity. Accordingly, the drawings may not represent all of the components of a given apparatus (eg, device) or method. Finally, like reference numerals may be used to refer to like features throughout the description and drawings.

Several aspects of the invention are described below. It will be apparent that the descriptions herein may be embodied in a wide variety of forms, and that any specific structure, function, or both described herein is merely representative. Based on the descriptions herein, one skilled in the art will recognize that an aspect described herein may be implemented independently of any other aspect, and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Moreover, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects described herein. Furthermore, an aspect may include at least one element of a claim.

1 illustrates some nodes in an example communication system 100 (eg, part of a communication network). For purposes of illustration, various aspects of the present invention will be described in the context of one or more network nodes, access points, and access terminals communicating with each other. It should be understood, however, that the descriptions herein may apply to other types of devices or other similar devices that are referenced using other terminology.

Access points 102 and 104 of system 100 may be installed within an associated geographic area or one or more wireless terminals (eg, access terminals 106 and/or 108) capable of roaming throughout the geographic area. ) for one or more services (eg, network connection). Additionally, access points 102 and 104 may communicate with one or more network nodes 110 to facilitate wide area network connectivity. Such a network node may take several forms. For example, the network node may include a mobility manager or some other suitable network entity (eg, a core network entity).

Access points 102 and 104 may in some aspects, each access point provide certain services only to certain access terminals (eg, access terminals 106 and 108 ) and to other access terminals (eg, not shown). It may be limited not to provide to non-macro access terminals). For example, access points 102 and 104 may be restricted from providing at least one of registration, signaling, voice calling, data access, or any other cellular service to other access terminals. Restricted access points may be deployed in an ad-hoc manner. For example, a given homeowner may install and configure their own restricted access point.

2 provides an overview of some operations that may be performed to facilitate deployment of restricted access points and access terminals that are authorized to use such access points. In some aspects, these operations may cause a restricted access node to determine its identity, determine the identity of access terminals that are allowed to access (eg, attach to) the restricted access point, and may determine the identity of the access terminal (eg, access terminal). It can be used to verify the identity of an access terminal that is attempting to access a restricted access point. In some aspects, these operations may cause the access terminal to determine its identity, determine the identity of a restricted access point to which the access terminal is permitted to access, and set the temporary identity of the access terminal to its permanent ( permanent) identity, and to be able to verify the identity of an access point (eg, a restricted access point to which an access terminal is trying to access).

For convenience, the operations of FIG. 2 (or any other operations discussed or described herein) refer to specific components (eg, components of system 100 and/or components of system 300 as shown in FIG. 3 ). ) can be described as being performed by However, it should be understood that these operations may be performed by other types of components and may also be performed using other numbers of components. It should also be noted that one or more of the operations described herein may not be utilized in a given implementation.

3 illustrates some example components that may be included in a network node 110 (eg, a mobility manager, a mobile switching center, or a serving GPRS support node), an access point 102 , and an access terminal 106 in accordance with the descriptions herein. indicate the It should be noted that components shown for a given one of these nodes may be included in other nodes in the communication system. For example, access terminal 108 may include components similar to those described for access terminal 106 , and access point 104 may include components similar to those described for access point 102 . have.

Network node 110, access point 102, and access terminal 106 each include transceivers 302, 304, and 306 for communicating with each other and with other nodes, respectively. Transceiver 302 includes a transmitter 308 for transmitting signals (eg, messages) and a receiver 310 for receiving signals. Transceiver 304 includes a transmitter 312 for transmitting signals and a receiver 314 for receiving signals. Transceiver 306 includes a transmitter 316 for transmitting signals and a receiver 318 for receiving signals.

Network node 110 , access point 102 , and access terminal 106 also include several other components that may be used in connection with provisioning and access management of nodes as described herein. For example, network node 110 , access point 102 , and access terminal 106 manage communications with other nodes (eg, sending and receiving messages/indications) as described herein and It may include communication controllers 320, 322, and 324, respectively, to provide other related functionality. Network node 110 , access point 102 , and access terminal 106 may include provisioning controllers 326 , 328 and 330 to provision the node and provide other related functionality as described herein. . Network node 110, access point 102, and access terminal 106 may each include access controllers 332, 334, and 336 to provide access management and other related functionality described herein. . For illustrative purposes, all of the nodes are shown in Figure 3 as having functions related to provisioning and access control. However, in some implementations, one or more of these components may not be available at a given node. The description that follows describes (eg, with reference to several different figures) some different ways to provision network nodes and provide access control. For convenience, in these different manners, network node 110 , access point 102 , and access terminal 106 may be referred to as having different functionality and may be referred to as representing different types of nodes. (eg, in different implementations, network node 110 may represent SRNC, or MME, or AAA, etc.). However, it should be noted that, in a given implementation, network node 110 , access point 102 , and access terminal 106 may be configured in a particular manner.

Referring back to FIG. 2 , as shown by block 202 , each access terminal (eg, access terminal 106 ) in the system communicates with one or more access points (eg, access point 102 ). can be prepared to enable In the example of FIG. 3 , these operations may be performed, for example, by the operation of provisioning controllers 326 and 330 .

In some aspects, an operator may assign a unique identifier to the access terminal 106 . In some implementations, this identifier includes a "network access identifier (NAI)" or a "mobile station integrated services digital network (MS ISDN)" number. Alternatively, a subscriber identity such as International Mobile Subscriber Identity (IMSI) may also be derived from a subscriber identity module such as SIM, USIM or VSIM that resides in the access terminal. In some cases, this identifier is guaranteed to be unique within the operator domain (eg, the entire network provided by the cellular operator). In some implementations, this identifier may be part of the session information for the access terminal 106 . For example, the identifier may be sent by the access terminal 106 to the network node 110 (eg, a session reference network controller (SRNC)) when the access terminal 106 creates a session, or the identifier may be sent once the session is established. Once created, it can be pushed from an authentication, authorization, and accounting (AAA) entity to the network node 110. In some implementations, the identifier allows the user to provide a service to, for example, one or more access terminals of his/her restricted access. accessible to its user so as to configure the point(s).In some implementations, the access terminal can be assigned a temporary identifier.For example, the network assigns permanent and temporary identifiers for the access terminal 106. and maintains such identifiers within the network. The network may also send the temporary identifier to the access terminal 106 to enable the access terminal 106 to use the temporary identifier when accessing the access point.

Access terminal 106 may also be provisioned to have the identity of each access point (eg, access point 102 ) to which it is permitted to access. As described in more detail below, this may, for example, cause the access terminal 106 to send and/or cause the access terminal 106 to transmit access point identifiers to the access terminal 106 (eg, a push model). ) (eg, a pull model) to allow selection of access points to be accessed. Accordingly, the access terminal 106 may maintain a list of authorized access points (eg, a white list or preferred user area list) to which it may refer as it moves through various wireless coverage areas.

In some implementations, a user of an access terminal 106 may be prompted to determine whether he or she wishes to allow the access terminal 106 to access an access point. In some implementations, the access terminal 106 may be able to automatically access the access point. In some implementations, the access terminal 106 can determine whether to automatically enable access or whether a user prompt is required to enable access, based on configuration information at the access terminal 106 . have. In some implementations, a user can choose to access one or more access terminals or choose not to access them. In such a case, a list of allowed and/or denied access terminal(s) may be maintained at access terminal 106 . In this way, the access terminal 106 may prevent (eg, automatically prevent) from attempting to access an access point on its list.

As indicated by block 204 , each restricted access point (eg, access point 102 ) of the system may be prepared to enable communication with one or more access terminals (eg, access terminal 106 ). have. In the example of FIG. 3 , these operations may be performed, for example, by the operation of provisioning controllers 326 and 328 .

For example, a unique identifier may be assigned to an access point 102 or a set of access points (eg, access points 102 and 104 ). This unique identifier is different from a unique device identifier that may be assigned to identify individual access terminals in the system. As described in more detail below, such an identifier may be, for example, an identifier assigned to a group of access terminals having the same restricted association characteristics (eg, CSG) or a special type of network identifier ("NID") or subnet identifier. may include In some cases, the network may be automatically assigned a unique identifier. In some cases, one or more access points may request an identifier (by determining a suggested identifier and transmitting it to the network). In such cases, the network may determine whether the requested identifier is already in use by one or more other access points. If the requested identifier is already in use, the network may select another identifier (eg, a similar identifier) that is not being used by any other access point and may transmit this identifier to the requesting access point(s).

Access point 102 may also be provisioned to have one or more identifiers associated with each access terminal (eg, access terminal 106 ) allowed to access that access point 102 . As described in more detail below, this may include, for example, storing the access terminal identifiers in a database managed by the network and/or storing the access terminal identifiers in a local access list at the access point 102 . can

In some implementations, an access control list for a given restricted access point may be managed at that restricted access point. For example, as described below with respect to FIG. 13 , a user can connect to his or her access point using an access terminal (eg, a cellular phone) or using a password protected webpage hosted at a restricted access point. configurable.

Alternatively, in some implementations, an access control list for each restricted access point in a network is managed in that network (eg, a core network). For example, as described below with respect to FIG. 4 , the access control list may be managed in a webpage hosted by a network operator. Managing an access control list in a network may provide one or more advantages in some situations. In some aspects, such a solution may allow for greater flexibility in policy. For example, an operator may restrict access to restricted access points if necessary, and the operator may examine records (eg, for access terminals) in the same billing plan. Also, the network may be more reliable than individual access points. Accordingly, the reliability of the access control list can be improved. Also, since the access control list may not be transmitted to a restricted access point, it may not be necessary to provide a direct interface (eg, application software, USB ports, etc.) to the restricted access point. Moreover, through the use of centralized access control lists, it may be easier to manage a large number of restricted access points belonging to a common enterprise.

Once the restricted access point is ready, it can advertise its assigned identifier over-the-air. For example, the access point 102 may broadcast its identifier as part of its sector parameters or in some other suitable manner.

As indicated by block 206, once the access terminal is ready, the access terminal may monitor for signals (eg, pilot/beacon signals) broadcast by nearby access points. As detailed below, if the access terminal 106 identifies signals from the access point 102 (eg, in a scenario where the access terminal 106 is allowed to access the access point 102 ), the access Terminal 106 may request access to its access point 102 . Identification of an accessible access point by an access terminal 106 may include, for example, a trusted list 338 (eg, a white list) of authorized access points maintained by the access terminal 106 associated with the access point. It may include comparing with an identifier. In the example of FIG. 3 , these and other access-related operations may be performed, for example, by operation of access controller 336 .

As indicated by block 208 , the access terminal 102 and/or one or more network nodes (eg, network node 110 ) determine whether to allow the access terminal 106 to access the access point 102 . can be decided Such access control operations include, for example, verifying the identity of the access terminal 106 and a list of authorized access terminals maintained by the access point 102 (eg, a local access list) with an identifier of the access terminal 106 . 340) and/or a list of authorized access terminals maintained by network node 110 (eg, network database access list 342). In the example of FIG. 3 , these and other access-related operations may be performed, for example, by operation of access controller 334 and/or access controller 332 .

With the above overview in mind, additional details relating to provisioning and access control will be described with reference to FIGS. 4-13 . It should be appreciated based on the description herein that one or more of the operations described in connection with a given one of these drawings may be used in conjunction with the operations described in the other of these drawings. For convenience, these operations will be described with reference to the components of FIG. 1 . It should be noted that these operations may apply to other nodes in the network as well.

Referring first to FIG. 4 , some operations related to provisioning a restricted access point are addressed.

As indicated by block 402 , network node 110 assigns an identifier (eg, a unique identifier) for the restricted access point. In some cases, this identifier is guaranteed to be unique within the operator domain (eg, the entire network provided by the cellular operator). For example, a network entity may maintain an identifier database used to ensure the uniqueness of any assigned identifier.

The identifier can take several forms. In some implementations, this identifier includes a network identifier (eg, a femto identifier ("FNID")). In some implementations, the identifier may include a "closed subscriber group identifier (CSG ID)". As described above, a limited set of access points (eg, associated with the same administrative domain) may share a common identifier (eg, CSG ID). In some implementations, the set of FNIDs may be associated with a common CSG. For example, a CSG may be assigned to an enterprise, and different FNIDs may be assigned to different access points throughout the enterprise (eg, inside different buildings). In some implementations, additional identifiers that may be user-readable (eg, text-based) may also be used.

The unique identifier may be prepared in several ways. For example, in some cases an identifier is selected and configured when a user activates a restricted access point. Here, the identifier may be configured by the operator at the moment of purchase or may be configured in some other way.

As indicated by block 404, a list of access terminals allowed to access access point 102 (and any other access points within the defined set of access points, if applicable) is generated. Such an access list may include, for example, access terminal identifiers as described herein. Thus, such an identifier may identify an individual access terminal (eg, NAI or IMSI or MS ISDN) or a set of one or more access terminals (eg, one or more access terminals associated with a given CSG). The access list may also define permissions (eg, conditions for access) associated with a given access terminal.

In some implementations, the access list may be managed through use of the website 344 (eg, accessible by a computer, phone, or any other suitable device). In this manner, the owner or user of the access point 102 may access the website to add, delete, or edit access terminal entries in the access list. For example, in order to allow a home or guest access terminal (eg, access terminal 108 ) to access access point 102 , a user may input the access terminal's persistent NAI through a webpage to the access list. can be added to Here, several naming conventions (eg, user-readable identifiers such as "Joe's phone", etc.) may be associated with a unique access terminal identifier (eg, NAI and MS ISDN), one of these identifiers. Anomalies may be displayed on a webpage after they have been added to the webpage.

As indicated by block 406 , in some implementations, the access list is hosted by a network operator. For example, an operator may maintain a server for an access list website. In this way, the operator can approve any changes to the access list (eg, deny entries for access terminals from other operators).

As indicated by block 408 , the access list information may then be transmitted to each access point or other network nodes that perform access control associated with the given access list. For example, the server may "push" the access list information to the access point 102 , or the access point 102 may "pull" the access list information from the server. As an example of a "push" model, an access list may be sent from an operator website to a configuration server, which in turn sends the access list to the access point 102 . As another example, the access list may be transmitted from an operator website to the application software on the access point 102 via the Internet. As an example of a "pull" model, the access point 102 may query a configuration server to receive the most recent version of the access list. Such a query may be made, for example, each time the access point 102 connects to the operator network (eg, each time it establishes a new IPSec connection). Thus, if an access point 102 goes "offline" for any period of time, it can be guaranteed to receive the most recent version of the access list whenever it reconnects to the network.

By maintaining the access list at a location other than the access point 102 , the access point 102 is freed from the burden of maintaining the access list. This solution can provide improved access list management because the access list can be updated even when the access point 102 is off-line. Also, this solution may simplify the management of access lists associated with more than one access point. For example, a single access list may be defined for a set of access points (eg, associated with a given CSG). In this case, the access points may obtain the access list from a single source rather than have to cooperate with each other to manage (eg, update) the access list across all of the access points.

The use of a centralized access list may also facilitate the use of temporary identifiers. For example, the access point 102 may use the given identifier for the duration that the given IPSec tunnel is established. When a new IPSec tunnel is established, the access list may be configured to have a different set of identifiers. Here, the new set of identifiers may or may not identify the same access terminals as the previous version of the access list.

As indicated by block 410 , the access point 102 broadcasts its identifier (eg, FNID or CSG ID) over-the-air. In this way, any access terminals entering the coverage area of the access point 102 can identify the access point 102 and determine whether they are allowed to access the access point 102 .

Referring now to FIGS. 5 and 6 , some operations that may be used to prepare an access terminal are described. In particular, these figures describe techniques for providing an access terminal with the identity of one or more restricted access points to which it is permitted to access.

5 illustrates some operations that may be performed to "push" access list information to an access terminal (ie, a push model). In this example, it is assumed that a unique identifier has been assigned to the access terminal (eg, as described above).

As indicated by block 502 , at any point in time, an access terminal may be designated as being allowed to access one or more access points. For example, the owner of one or more access points may add a guest access terminal to an access list associated with the access point(s) as described above with respect to FIG. 4 .

As indicated by block 504, the operator sends a message to the access terminal indicating that the access terminal is not allowed to access the access point or set of access points. This message may include an identifier (eg, FNID or CSG ID) associated with the access point(s) as well as any applicable restrictions (eg, time restrictions for guest access). Such a message may be transmitted, for example, when the identifier of the access terminal 108 is added to an access list associated with the access point 102 . This message may also be sent in several ways. For example, the network may use an SMS message, an application protocol message (eg, Open Mobile Alliance Device Management), a wireless link to convey access point information (a query that asks the access terminal 108 whether it wants to access the access point 102 ). A message, page, or some other type of message may be sent to the access terminal.

The access terminal 108 may then inform the user of the access terminal 108 that it is entitled to access the access point(s), as indicated by block 506 . For example, the access terminal 108 may display an indication of the identity of the access point(s), or may provide some other form of indication. Such indicia may include, for example, an identifier assigned to the access point(s) or other name associated with the identifier (eg, user-readable identifiers such as "Sue's house," etc.).

The user may then determine (eg, using an input device on the access terminal 108 ) whether the requested access to the access point(s) is possible, as indicated by block 508 . Based on the user's determination, the access terminal 108 may update the list it maintains (eg, a white list) of access points to which it is permitted to access (eg, to which it can access). . As described below, the access terminal 108 can use the list to determine which access points it can access as it moves across the network. Here, the user may not need to provide any additional access grants when the access terminal enters the coverage area of an access point in the list, since the access terminal automatically "remembers" this access point. ) because you can. In some implementations, the white list may be updated only after approval is received from the network operator.

In some implementations, the access terminal 108 can send a message to the operator indicating the user's decision. In this way, the operator may choose to change the access list for the access point(s) if necessary.

By allowing the user of the access terminal to either accept or deny access to the access point, the user of the access point can prevent the access terminal (eg, a neighboring access terminal) from allowing unilateral access to the access point. Accordingly, the user of the access terminal can be assured that his/her information is not transmitted to unauthorized access points.

Also, this "push" model does not require the access terminal to be in the vicinity of the access point in order to add it to its white list. Also, since the access terminal can only receive "push" messages when it has been added to the access list, the likelihood of the user selecting the wrong access point (eg, an access point to which the access terminal is not allowed to access) is reduced. can

6 illustrates some operations (ie, pull model) that may be performed to "pull" access list information to an access terminal. It is also assumed that a unique identifier has been assigned to the access terminal.

As indicated by block 602 , at any point in time, a user of an access terminal (eg, access terminal 108 ) initiates a scan for nearby access points. To this end, the access terminal 108 may include a user controllable input device (eg, a menu option) for the receiver 318 to monitor one or more channels for pilot signals or other signals from the access point. .

As indicated by block 604, the access terminal 108 notifies the user of any access points detected according to the results of the scan. For example, the access terminal 108 may display an indication of the identity of the detected access point(s), or may provide some other form of indication. This indication may also include an identifier assigned to the access point(s), another name, or any other suitable information.

As indicated by block 606 , the user may select to enable access to one or more detected access points. For example, a user may control an input device on the access terminal 108 to select one or more access points displayed by the access terminal 108 .

The access terminal then attempts to access the selected access point if necessary. As described below, if the user selects the wrong access point (eg, an access point to which the access terminal is not allowed to access), the access point may deny access. The access point can then relay this information to the access terminal (eg, to prevent this from happening again later).

As indicated by block 608 , in some implementations, the access terminal 108 maintains a list (eg, a white list) of the access points to which it is allowed to access based on the user's determination. ) can be updated. In this way, the access terminal 108 can "remember" the selected access point, so that no user input will be required for future visits to this access point (eg, the access terminal 108 can be can connect to the access point without having to initiate a scan).

As indicated by block 610 , in some implementations, enabling the access terminal 108 to access the access point based on a condition (eg, pay-per-use). A "pull" model may be used for this purpose. For example, some access points (eg, access points belonging to a co-owner, such as a hotel or other enterprise) may all advertise the same unique identifier (eg, FNID or CSG ID). When an access terminal is in proximity to one of these access points and a user of the access terminal 108 initiates a scan, the user may choose to connect to one of these access points (eg, access point 102 ). . When an access terminal 108 attempts to connect to the access point 102, the access point 102 checks its local access control list to see if the access terminal 108 is authorized to access it. may not, and may instead allow the access terminal 108 to perform the initial connection. However, this initial connection may require the user to redirect to a webpage that allows the access terminal 108 to receive services from the access point 102 only if certain conditions are met (eg, payment has been made). may include Through the use of this model, any access terminal (as opposed to some designated access terminals) can gain access to a set of associated access points.

As described above, the access point and/or network node may control whether a given access terminal is allowed to access the access point. In some implementations, access control for a given restricted access point may be managed at that restricted access point. In some implementations, access control for a given restricted access point may be managed at that restricted access point with help from a centralized access control manager (eg, implemented within a network node). 7-11 illustrate some techniques that may be used to control such access.

Referring initially to FIG. 7 , some operations related to a scenario in which an access point controls access to itself are described. In some aspects, access granted by an access point may be conditional. For example, if the access point determines that access to a particular service should not be granted, the requested access may be unilaterally denied. However, if the access point determines that access to a given service should be granted, the access point may send a request to the network to ascertain whether access should be granted.

In some implementations, the access point may control (eg, unilaterally control) access to a local service. For example, an access terminal may attempt to gain access to a service provided on a local network associated with the access point. These services may include, for example, access to a local server (eg, access to audio, video, data or other content), access to a printer, and the like.

As indicated by block 702 of FIG. 7 , at some point in time, an access terminal (eg, access terminal 108 ) initiates establishing communication with a restricted access point (eg, access point 102 ). In conjunction with this operation, the access terminal 108 may attempt to open a session (or route) to the access point 102 . In addition, the associated session information may be stored in a network (eg, network node 110 ). To facilitate the access point 102 to verify the identity of the access terminal 108 , in some cases the identifier of the access terminal 108 may include session information (eg, included in context information for the access point). can be part of Such identifiers may include, for example, permanent identifiers (eg, NAIs) as described herein.

As represented by block 704 , the access point 102 may obtain information to verify the identity of the access terminal 108 . For example, in some cases, access point 102 may receive an identifier (eg, temporary identifier) or other suitable information directly (eg, over-the-air) from access terminal 108 . In some cases, the access point 102 may retrieve the above-described session information including an access terminal identifier (eg, temporary or permanent identifier) from the network (eg, from the SRNC). Advantageously, in this latter scenario, transmission of an identifier (eg permanent NAI) over-the-air may be avoided.

In cases where a temporary identifier (eg, a temporary NAI) is used, the access point 102 may cooperate with the network to ensure the validity of the identifier. For example, in some implementations, the access point 102 sends a temporary identifier to an AAA entity, which authenticates the identifier. In some implementations, the access point 102 transmits a temporary identifier to the network and in response receives an associated permanent identifier. In this case, the access point 102 may use the persistent identifier to authenticate the access terminal 108 .

As indicated by block 706 , the access point 102 adds the access terminal information (eg, temporary or permanent identifier) to its local access list (eg, represented by local access list 340 in FIG. 3 ). Compare with the information you have. As described above, the local access list may be configured to include a unique identifier (eg, NAI, CSG ID, etc.) associated with the access terminal 108 .

The access point 102 may then grant or deny the requested access based on the comparison at block 706 , as indicated by block 708 . Here, the access point 102 may send a reject message to the access terminal 108 and/or the access point 102 may redirect the access terminal 108 to another access point (eg, local macro access). by sending a redirect message identifying the point).

As described below, in some implementations, the access point 102 may cooperate with a network to authenticate the access terminal 108 . For example, if the access terminal identifier is not in the local access list, the access point 102 may be implemented such as authentication for restricted access points, etc. (eg, implemented as a standalone entity or by including functionality equivalent to a typical network AAA entity) The request may be sent to a network node, such as an AAA entity providing a femto AAA). Here, the network node may maintain an access control list for the access point 102 it uses to authenticate the access terminal 108 (eg, in a manner similar to that described above). Also, if applicable, the network node may be configured by another network node (e.g., the access terminal 108)). The access point 102 then grants the requested access based on a response indicating whether the access terminal 108 is authorized to access the access point 102 (a response that the access point 102 receives from the network). or you can refuse. In accordance with the descriptions herein, access control functions may in various implementations be an access point, or gateway, a mobile switching center ("MSC"), a serving GPRS support node ("SGSN"), a packet data serving node ("PDSN"). ), or other network entities such as MME.

Referring now to FIG. 8 , the network transmits to the access point a list of access terminal identifiers (eg, the access point's access list) to enable the access point to determine whether to grant a request for access from the access terminal. Some operations related to the scenario are described. In this example, the operations of blocks 802 and 804 may be similar to the operations of blocks 702 and 704 described above. However, in such a scenario, the access point 102 may not retrieve session information in some cases.

As indicated by block 806 , the access point 102 sends a request to the network (eg, network node 110 ) to authenticate the access terminal 108 . When the access point 102 has obtained session information (eg, including access terminal identifier information such as MS ISDN, CSG ID, or NAI), the access point 102 requests such information (eg, in a request message). included) together with the network node 110 . In some implementations, this action can include a request for a list of access terminal identifiers. In practice, the access point 102 may request such a list multiple times (eg, each time the access point powers up or joins the network, each time the access terminal attempts to access the access point, periodically, etc.).

As represented by block 808 , network node 110 obtains an identifier associated with access terminal 108 . Such an identifier may include, for example, a list of identifiers indicating one or more access groups associated with the access terminal. For example, the identifier may be a list of closed subscriber groups of which the access terminal 108 is a member, a list of access terminals allowed to access the access point 102 (eg, the access list of the access point 102 ), or an access terminal ( 108) may include a list of identifiers of access points to which it may access. Determination of the identifier by the network node 110 may include, for example, receiving the identifier from another network node (eg, HSS) or obtaining the identifier from a local database. In some implementations, determining the identifier can include determining the permanent identifier (eg, based on the received temporary identifier) as described herein. The network node 110 transmits the identifier or identifiers obtained at block 808 to the access point 810 at block 810 .

Then, as indicated by block 812 , the access point 102 may determine whether to allow or deny the requested access based on the received identifier(s). For example, the access point may compare the received identifier (eg, CSG ID) indicating the sets to which the access terminal 108 belongs to the local access list of the access point 102 indicating the sets to which the access point 102 belongs. The access point 102 may then grant or deny the requested access based on this comparison.

Referring now to FIG. 9 , some operations related to a scenario in which a network controls access to an access point are described. In this example, the operations of blocks 902 , 904 , and 906 may be similar to the operations of blocks 802 , 804 , and 806 described above. Also, the access point 102 may not retrieve session information in some cases. Also, in some cases, the access point 102 may transmit its local access list to the network for use in an authentication operation.

As indicated by block 908 , in implementations that use temporary identifiers to identify one or more nodes (eg, access terminals), network node 110 (eg, femto AAA) is an access terminal ( A permanent identifier associated with the access terminal 108 may be determined based on the temporary identifier associated with the 108 . For example, the access point 102 may have obtained the temporary identifier from the access terminal (eg, block 902 ) or may have obtained it from session information (eg, block 904 ). In this case, in block 906, in connection with the request, the access point 102 provides a temporary identifier (eg, a temporary NAI) for the access terminal 108 with the identifier (eg, FNID) of the access point 102 . together to the network node 110 . The network node 110 may then cooperate with other network nodes to derive the permanent identifier of the access terminal 108 from the temporary identifier, as described above with respect to FIG. 7 .

As indicated by block 910 , the network node 110 determines whether to allow the access terminal 108 to access the access point 102 . For example, the network node 110 may compare the identifier (eg, NAI, CSG ID, etc.) of the access terminal 108 to the access list of the access point 102 . Here, the access list may be a local list obtained from the access point 102, or it may be an access list maintained by a network (eg, based on information obtained from a web server as described above). Network node 110 may then determine whether to grant or deny the requested access based on this comparison.

As represented by block 912 , network node 110 transmits an indication of this determination to access point 102 . The access point 102 may then grant or deny the requested access based on the received indication. Advantageously, in implementations such as these, the access point 102 does not need to know the actual identity of the access terminals accessing the access point 102 . Also, an access control list for the access point 102 need not be transmitted to the access point 102 . In this implementation, access control is performed entirely at the network node transparent to the access point.

Several techniques may be used to manage access terminal identifiers in a network. As described above, the access point may store a valid identifier (eg, NAI) used by the access terminal. In some implementations, this identifier may remain valid for a defined period of time. Here, if the access terminal revisits the access point within that time period (ie, the access terminal has the same identifier during that time), the access point does not obtain an authorization from the network (eg, femto AAA) and the access terminal can accept In some implementations, an operator can choose whether to use a temporary identifier or a permanent identifier for access terminals. If a permanent identifier is used, the permanent identifiers may be stored at the access points (eg, stored in the local access list 340 ), so that the access point can independently authenticate the access terminals. If a temporary identifier is used, the operator can control the frequency at which access points check the network (eg, femto AAA) to verify identifiers stored in the local access list 340 .

10 illustrates an example of access control operations that may be performed in an implementation utilizing "long-term evolution (LTE)" or other similar technology. In this example, the network (eg, the core network as opposed to the radio access network) controls whether an access terminal is allowed to access the access point. Also, provision access terminals and access points with CSG subscription information (e.g. matching information), enforce access control (e.g., during idle or active mode), change access point or access terminal provisioning, Techniques are described for enforcing a CSG list when an access terminal performs operations such as power-up, tracking area update, and handover.

A network (eg, a home subscription server ("HSS") or CSG subscription server) may maintain CSG subscription information for access terminals and restricted access points in the network. In a manner similar to that described above, an operator may provide a web server that allows users to manage CSG subscription information for their restricted access point(s). For example, a user may use a website to change his or her subscription information (eg, MS ISDNs). The network may then approve the changes made by the user (eg, access terminal entries), and the webserver may send the subscription information to the network (eg, HSS). Here, MS ISDN may be converted to IMSI. The network may then transmit CSG information (eg, a unique CSG identifier) to the corresponding restricted access point(s). The network may also send CSG subscription information to the MME when the associated access terminal is registered with that MME.

Also as described above, the provision of an access terminal (eg, with a list of unique CSG IDs) may be authorized by the owner of the access terminal. In addition, the operator may also approve the provision of the access terminal. Here, a given CSG ID may be associated with a set of one or more access terminals that are permitted to receive at least one service from a set of at least one restricted access point. That is, both the set of access terminals and the set of access points are associated with a common CSG ID. It should also be noted that a given access terminal or access point may also be associated with multiple CSGs. In some aspects, a network (eg, HSS) may maintain information indicative of a mapping between an identifier of an access terminal and a subscribed CSG ID. Also, since the HSS can be connected to the MME, the MME can retrieve the CSG information and relay it to the restricted access point if necessary.

Also, access terminal provisioning may include a "push model" or a "pull model". For example, in the former case, the network (eg, network node) may send an SMS message to the access terminal to inform the access terminal of a new subscription (eg, identifying one or more CSG IDs) and whether the user accepts or rejects the subscription. can In the latter case, the user can initiate a manual scan and the access terminal displays a list of nearby access points (eg, user-readable CSG IDs or other types of access point identifiers), so that the user can In some cases, one or more entries may be selected from the list.

As indicated by block 1002 of FIG. 10 , at any point in time, the access terminal initiates access to the restricted access point. For example, when the access terminal 108 determines that it is in the vicinity of the access point 102 (eg, when the access point 102 advertises a CSG ID also associated with the access terminal 108 ), the access terminal 108 . ) may send a registration request or other suitable message to the access point 102 .

As indicated by block 1004 , the access point 102 sends a request to the network (eg, one or more network nodes 110 ) to authenticate the access terminal 108 . Here, the network node(s) 110 may include a mobility management entity ("MME") or any other suitable network entity or entities. The access point 102 may also send an identifier (eg, a CSG ID associated with the access point 102 ) to the network node 110 along with the request (eg, included in the request message). The request may also include information received from the access terminal 108 (eg, at block 1002 ).

As indicated by block 1006 , network node 110 obtains context information associated with access terminal 108 (eg, from a previous MME for access terminal 108 or from an HSS). Such contextual information may include, for example, a set of identifiers associated with the access terminal 108 . For example, the context information may include a list of all CSG IDs associated with the access terminal 108 . In some implementations, network node 110 may maintain a list of its own CSG IDs for each of its restricted access points. In this case, the network node 110 updates its list whenever an entry is changed in the web server.

As represented by block 1008 , network node 110 determines whether access terminal 108 is allowed to access access point 102 . For example, the network node 110 may indicate that the identifier of the access point 102 (indicating the CSG to which the access point 102 belongs) is a list of identifiers associated with the access terminal 108 (eg, CSGs to which the access terminal 108 belongs). indicates all).

The determination of block 1008 may be performed at various network nodes. For example, in some implementations, this determination may be made at an MME that obtains and/or maintains identifiers associated with access point 102 and access terminal 108 .

In some implementations, this determination may be made at another network node, such as an HSS. For example, the MME may send a request to the HSS to determine whether the access terminal 108 is authorized to access the access point 102 . With this request, the MME may in some cases send information (eg, identifiers such as IMSI and CSG ID) to the HSS. Also, in some cases, the HSS may obtain and maintain this information on its own. After determining whether access is allowed or not, the HSS sends a corresponding response to the MME.

As represented by block 1010 , the MME transmits a response to the access point based on the MME's determination or based on the determination of another network node (eg, HSS). Based on this response, the access point 102 may then allow or deny access by the access point 108 .

11 illustrates operations that may be used in connection with a handover operation. For example, an access terminal 108 may be initially served by an access point 104 , and at a later point in time, the access terminal 108 is handed over to the access point 102 and then served by the node. .

As indicated by block 1102 , a network (eg, HSS) may maintain context information for each access terminal in the system. As described above, this context information may include a list (eg, a white list) indicating all of the access sets (eg, CSGs) to which the access terminal 108 belongs.

As indicated by block 1104 , the network (eg, MME) fetches a context for a given access terminal and provides the context to the restricted access point when the access terminal is activated in the restricted access point. Referring to the example of FIG. 3 , when an access terminal 108 is activated (eg, turned on) at an access point 104 , the network node 110 transmits context information for the access terminal 108 to the access point. (104) can be transmitted. In this way, the access terminal 108 may be initially served by the access point 104 .

As indicated by block 1106 , at any point in time, the access terminal 108 may be handed over to the access point 102 . For example, if the access terminal 108 moves away from the access point 104, measurement reports from the access terminal 108 indicate that the signal strength of the signals being received from the access point 102 is may indicate that the signal strength of the signals received from In this case, the network may initiate a handover from the access point 104 to the access point 102 .

As indicated by blocks 1106 and 1108, in connection with this handover, the access point 104 (ie, the source access point) is a target access point (ie, access point 102), such as a CSG ID, for example. may receive an identifier associated with the . For example, such information may be received from the access terminal 108 . The access point 104 may then determine based on this identifier whether the access terminal 108 is authorized to access the access point 102 . For example, the access point 104 may create a list specifying the access points to which the access terminal 108 is allowed to access (eg, a white list such as a CSG ID list from context information for the access terminal 108) and its identifier. can be compared.

As indicated by block 1110 , if the access terminal 108 is not authorized to access the access point 102 (eg, the CSG ID of the access point 102 is added to the CSG ID list of the access terminal 108 ). Otherwise), the handover operation may not be performed. For example, the access point 102 may send a message to the network node 110 to end the handover operation. Additionally or alternatively, the access point 102 may send a reject and/or redirect message to the access point 108 (eg, as described above).

As indicated by block 1112 , if the access terminal 108 is authorized to access the access point 102 (eg, the CSG ID of the access point 102 is present in the CSG ID list of the access terminal 108 ). If yes), the handover operation can start. Accordingly, a network (eg, an MME) may transmit context information for the access terminal 108 to the access point 102 , or the access point 102 may receive such information from the access point 104 .

As indicated by block 1114 , the access point 102 may determine whether the access terminal 108 is authorized to access the access point 102 . For example, in a manner similar to that described above, the access point 102 may include a list specifying the access points to which the access terminal 108 is allowed to access (eg, a list of CSG IDs from context information for the access terminal 108 ). and its own identifier (eg, CSG ID) may be compared.

As indicated by block 1116 , in some implementations, the access point 102 makes a request (eg, with a path switch request) to the network (eg, the MME) to ascertain whether a handover should be performed. ) can be sent. For example, as described above, the access point 102 may request (eg, if necessary optionally including an identifier associated with the access terminal 108 and a CSG ID for the access point).

In situations where the access terminal needs to access the target access point without prior handover preparation (eg, during radio link failure), the target access point may fetch the access terminal context from the source access point. As described above, this context contains the CSG list for the access terminal. Accordingly, the target access point can determine whether the access terminal is allowed to access the target access point.

As indicated by block 1118 , based on block 1114 (and optionally block 1116 ), the handover is either allowed or denied. If the handover is allowed, then the access point 102 becomes the serving access point for the access terminal 108 . Conversely, if the handover is not allowed, the handover may end (eg, as described above with respect to block 1110 ).

Referring now to FIG. 12 , in some implementations, a restricted access point may be used to provision an access terminal. For illustrative purposes, the following examples describe examples in which an access terminal is prepared (eg, configured) to have a preferred roaming list ("PRL"). However, the access terminal may be prepared to have other types of information in accordance with the description herein.

As indicated by block 1202, access terminals in the network (e.g., any access terminals capable of accessing a restricted access point) are allowed to have a default PRL (e.g., the list contains or specifies a default configuration). can be originally configured. For example, an access terminal 106 may be configured by a network operator when the access terminal 106 is purchased by a user. This PRL may specify, for example, a default system identifier ("SID"), a default network identifier ("NID"), and a default frequency for initial acquisition of any restricted access points that may be deployed in the network. can Here, all of the above access terminals may be configured to have a default PRL. In this way, each access terminal can locate and access the restricted access point for preparatory operations. In some aspects, the default PRL information (eg, SID and/or NID) may correspond to one or more access points associated with the highest priority. For example, the access terminal may be configured to search (eg, search first) a specified preferred access point or specified preferred access points (eg, home access points).

In some aspects, parameters of a default PRL for restricted access point-related operations may be reserved. For example, a default SID for restricted access points may be reserved by the network operator. Through the use of such a SID, access terminals that are not configured to access restricted access points (eg, access terminals configured only for use on a macro network) may not attempt to register with the restricted access points. In addition, a default NID may be reserved for restricted access point-related initialization procedures. Also, a default frequency may be established as a common frequency to be used by restricted access points in the network to transmit beacons for preparatory procedures. In some cases, the default frequency may be the same as the operating frequency of the macro access point or the restricted access point.

The default PRL may also include information for macro system selection. For example, the default PRL may include identifiers and frequencies that may be used to access macro access points in the network.

As indicated by block 1204 , restricted access points (eg, access point 102 ) of the system are configured to transmit a bootstrap beacon. In some aspects, such a bootstrap beacon may include a temporary beacon used in connection with a provision provided by the access point 102 . Here, the bootstrap beacon may be broadcast according to the general PRL parameters described above (eg, the beacon may include or specify a default configuration). For example, a bootstrap beacon (eg, a default beacon) may be transmitted on a default frequency and may include a default SID and a default NID (eg, transmitted via an overhead message).

The bootstrap beacon may be transmitted at a very low power level that is much lower than the beacon transmit power during normal access point operations (eg, when the access point is configured in a non-initializing mode of operation, such as a normal operating mode). For example, the bootstrap beacon transmit power may occur within a coverage range (eg, radius) for the bootstrap beacon, approximately 1 meter or less.

In some implementations, the access point 102 may send bootstrap beacons when it is in a ready (eg, configure or initialize) mode. In some implementations, a user may use the input device to place the access point 102 in a configuration mode when he or she wants to initially prepare or re-arm the access terminal 106 . For example, when the access point is first installed, when the access terminal is initially purchased, or the PRL of the access terminal causes the PRL prepared by the access point to be overwritten (as described below). When updated by the macro network (eg in connection with a change in roaming list, international travel, etc.), the access terminal may be ready.

As indicated by block 1206 , when an access terminal 106 that is prepared to have a default PRL is located in proximity to a restricted access point 102 operating in a ready mode, the access terminal 106 becomes the access point 102 . It is possible to receive the bootstrap beacon transmitted by In response, the access terminal 106 may send a message to the access point 102 to initiate preparatory operations. In some implementations, this message may include a PRL currently used by the access terminal 106 . In some implementations, the user of the access terminal 106 may initiate the preparation process by selecting an appropriate feature on the access terminal (eg, calling a given number).

As indicated by block 1208 , access point 102 (eg, provisioning controller 328 ) may establish a new PRL for access terminal 106 (eg, during normal mobile operations). The new PRL may contain macro system information as in the default PRL, but the default PRL initialization information may be removed. Instead, new PRL information may be added (eg, the list contains or specifies a new configuration). In some aspects, the new PRL information may be specific to the access point 102 (eg, the new PRL may be different from the PRL prepared by other access points). For example, the new PRL includes the SID reserved for all restricted access points as described above, the NID unique to the access point 102 (eg, femto NID, "FNID"), and the operating frequency of the access point 102 . The indicated frequency parameter can be specified. This frequency parameter may be the same as or different from the default frequency. In some aspects, the new PRL information (eg, SID and/or NID) may correspond to one or more access points associated with the highest priority. For example, the access terminal 106 may be configured to search (eg, search first) a specified preferred access point or specified preferred access points (eg, home access points).

Access terminal 102 may obtain macro system PRL information in several ways. In some implementations, access point 102 may request such PRL information from a macro access point (eg, via network node 110 or over-the-air). In some implementations, access point 102 may receive such PRL information from an access terminal (eg, access terminal 108 ). For example, the access point 102 may include over-the-air functionality. Here, the access point 102 may send a message (eg, SSPR configuration request) to request the access terminal's current PRL (which may include current macro PRL information as described above), and the access terminal It may respond by sending its current PRL to the over-the-air access point 102 .

Once the access point 102 establishes a new PRL, it transmits (eg, pushes) the PRL to the access terminal 106 . For example, the access point 102 may transmit the PRL over-the-air (eg, via OTASP or OTAPA) to the access terminal.

Advantageously, by provisioning the access terminal 106 via the access point 102 as described above, the network operator does not need to maintain access terminal-specific information (eg, PRL information). However, it may be desirable to configure the access point 102 to perform regular updates to the access terminal's PRL. For example, the PRL may be updated every evening and transmitted over-the-air to the access terminal 106 . Further, in order to prevent one access point of the set of related access points from overwriting the preparation of PRL information by another access point in the set, each access point is configured to simply update the current PRL information of the access terminal. can be For example, the access point 102 may query the access terminal 106 for its current PRL information, so that the access point 102 may query the access terminal 106 for its current PRL information rather than overwriting the current PRL information. You will add your own PRL system information to the current PRL.

As indicated by block 1210, once an access terminal 106 is prepared to have new PRL information, the access terminal 106 will use this information to identify the access points to which it can access. For example, when the access terminal 106 determines that the access point 102 is nearby (eg, after the access point has been configured for a normal operating mode), the access terminal 106 is detected by the access terminal 106 . may prefer to be served by that access point 102 as opposed to any other access points (eg, macro access point) being

Referring now to FIG. 13 , several techniques for controlling restricted access (eg, association) at an access point are described. In this example, an access point may be configured to have a local list of access terminals that are allowed to access one or more services provided by the access point. The access point can then grant or deny access based on its local list. Advantageously, in some aspects, such a scheme may enable the owner of an access point to provide temporary service to guest access terminals without involving a network operator (eg, add such access terminals to/ by adding/deleting from ).

As represented by block 1302 , a restricted access point (eg, access point 102 ) is configured to have an access list (represented by local access list 340 in FIG. 3 ). For example, the owner of an access point 102 may construct a list of identifiers (phone numbers) of access terminals that are permitted to use one or more services provided by the access point 102 . In some implementations, control over which access terminals may access the access point 102 may thus rest with the owner of the access point 102 rather than the network operator.

The access point 102 may be provisioned in several ways. For example, the owner may use the web interface hosted by the access point 102 to configure the access point 102 .

Different access terminals may also be provided with different levels of access. For example, guest access terminals may be provided with temporary access based on several criteria. Also, in some implementations, a home access terminal may be assigned a better quality of service than a guest access terminal. Also, some access terminals (eg, guest access terminals) may be provided with access to certain services (eg, local services such as a multimedia server or some other type of information server) without involving authentication by a network operator. can Also, in some cases, the local access list 340 may be used as an initial stop gap at the access point 102, thereby being used by the network to prevent the security of the network from being compromised. Actual authentication (eg, for phone calls) may be performed.

As indicated by block 1304 , the access point 102 transfers the access terminal identifier information (eg, local access list 340 ) configured in block 1302 to a network database (eg, authentication center/home location register (") AC/HLR")) and request other identification information associated with the corresponding access terminals. For example, the access point 102 may transmit the phone number of the access terminal 106 to the network node 110 (eg, including an HLR database) and assigned from the network node 110 to the access terminal 106 . An "electronic serial number (ESN)" or an "international mobile subscriber identity (IMIS)" may be received.

As indicated by block 1306 , the access point 102 may publish its own identifying information (eg, as described herein). For example, the access point 102 may advertise SID and FNID information as described above.

As indicated by block 1308 , an access terminal that is being prepared to access the access point 102 may determine that it is in the vicinity of the access point 102 upon receiving the advertised identification information. For example, the access terminal 106 may be provisioned with a PRL by the access point 102 as described above, or the access terminal 106 may have a restricted access point SID, wildcard NID, and access point 102 . may be provisioned to have a PRL comprising one or more operating frequencies used by the Prepare to have your local list). The access terminal 106 may then attempt to register with the access point as a result of receiving a different SID (eg, which may indicate a different area than the macro area for area-based registration). Thus, in some cases, the access terminal may automatically attempt to access the access point 102 . However, in other cases, the user may control whether or not the access terminal 106 accesses the access point 102 (eg, the user may output an indication of the detected access points output by the access terminal 106 ). provides input through the input device in response to). In connection with such registration, the access terminal 106 may transmit its identifier (eg, its ESN, IMSI, etc.) to the access point 102 (eg, via an access channel).

As indicated by blocks 1310 and 1312 , the access point 102 determines whether the access terminal 106 is allowed to access the access point 102 . For example, the access point 102 can determine whether an identifier received from the access terminal 106 is listed in the local access list 340 . It should be noted that authentication information other than ESNs and IMSIs may be used in different implementations. For example, the access point 102 may receive call originating number information via idle messages (eg, compared to a caller number received from the access terminal 106 via a registration message or some other method) may use this information for authentication.

As indicated by block 1314 , if the access terminal 106 is not permitted to access (eg, the received access terminal identifier is not in the local access list 340 ), the access point 102 grants access. can be rejected For example, the access point 102 may send a registration rejection message to the access terminal 106 . Additionally or alternatively, the access point 102 may send a service redirection message to the access terminal 106 . Such a message may include, for example, information (eg, SID, NID, operating frequency) that identifies another access point (eg, a local macro network) to which the access terminal 106 may access.

As indicated by block 1316 , if the access terminal 106 is allowed to access (eg, if the received access terminal identifier is in the local access list 340 ), the access point 102 may access certain services. can grant access to For example, as described above, access point 102 may grant access to local services provided by a local network.

Additionally or alternatively, the access point 102 may communicate registration information to the network node 110 (eg, the HRL of the macro network) for authentication and registration of the access terminal 106 . The network node 110 may then respond with a registration accept or reject message. In response, the access point 102 may send a corresponding message to the access terminal 106 . Then, if granted, the access terminal 106 obtains the requested service from the access point 102 (eg, network access).

It should be noted that the above techniques may be implemented in various ways in accordance with the descriptions herein. For example, authentication information different from the information specifically mentioned above (eg, ESNs, IMSIs, CSG IDs) may be used in an apparatus or method implemented based on the descriptions herein.

In some aspects, the descriptions herein describe large-scale coverage (eg, a large area cellular network, such as a 3G network, commonly referred to as a macro cell network or WAN) and small-scale coverage (eg, a home-based or building commonly referred to as a LAN). -based network environment). As an access terminal moves through such a network, the access terminal may be served at certain locations by access points providing large coverage, while the access terminal may be served at other locations by access points providing small coverage. can be served at In some aspects, small coverage nodes may be used to provide incremental capacity growth, in-building coverage, and different services (eg, for a more robust user experience). In the description herein, a node that provides coverage over a relatively large area may be referred to as a macro node. A node that provides coverage over a relatively small area (eg, a house) may be referred to as a femto node. A node that provides coverage over an area smaller than the macro area and larger than the femto area may be referred to as a pico node (eg, providing coverage within a commercial building).

A macro node, a femto node, or a cell associated with a pico node may be referred to as a macro cell, a femto cell, or a pico cell, respectively. In some implementations, each node may be associated with (and divided into) one or more cells or sectors.

In various applications, other terms may be used to refer to a macro node, a femto node, or a pico node. For example, a macro node may be configured as or referred to as an access node, base station, access point, eNodeB, macro cell, or the like. In addition, a femto node may be configured as or referred to as a Home NodeB, Home eNodeB, access point base station, femto cell, or the like.

14 illustrates a wireless communication system 1400 configured to support multiple users, in which the descriptions herein may be implemented. System 1400 provides communication for a number of cells 1402, such as, for example, macro cells 1402A-1402G, each cell having a corresponding access point 1404 (eg, access points 1404A-1404G). ) is served by As shown in FIG. 14 , access terminals 1406 (eg, access terminals 1406A-1406L) may be distributed at various locations throughout the system over time. Each access terminal 1406 may have a forward link ("FL") and/or a reverse link (" RL") with one or more access points 1404. The wireless communication system 1400 may provide services over a large geographic area. For example, macro cells 1402A-1402G may cover a small number of blocks within a neighborhood or miles in a rural environment.

15 illustrates an example communication system 1500 in which one or more femto nodes are deployed within a network environment. In particular, system 1500 includes multiple femto nodes 1510 (eg, femto nodes 1510A and 1510B) installed in a relatively small-scale network environment (eg, one or more user homes 1530). include Each femto node 1510 may be connected to a wide area network 1540 (eg, the Internet) and a mobile operator core network 1550 via a DSL router, cable modem, wireless link, or other means of access (not shown). . As will be described below, each femto node 1510 has associated access terminals 1520 (eg, access terminal 1520A) and optionally alien access terminals 1520 (eg, access terminal). 1520B). That is, access to femto nodes 1510 may be served by a set of femto node(s) 1510 to which a given access terminal 1520 is designated (eg, home), but may be served by any non-designated femto nodes 1510 . ) (eg, the neighboring femto node 1510 ).

16 shows an example of a coverage map 1600 in which some tracking areas 1602 (or routing or location areas) are defined, each of which includes several macro coverage areas 1604 . Here, areas of coverage associated with tracking areas 1602A, 1602B, and 1602C are represented by bold lines, and macro coverage areas 1604 are represented by hexagons. Tracking areas 1602 also include femto coverage areas 1606 . In this example, each of the femto coverage areas 1606 (eg, femto coverage area 1606C) is shown within a macro coverage area 1604 (eg, macro coverage area 1604B). However, it should be noted that the femto coverage area 1606 may not exist exclusively within the macro coverage area 1604 . In practice, a very large number of femto coverage areas 1606 may be defined as a given tracking area 1602 or macro coverage area 1604 . Also, one or more pico coverage areas (not shown) may be defined within a given tracking area 1602 or macro coverage area 1604 .

Referring back to FIG. 15 , the owner of the femto node 1510 may subscribe to a mobile service, such as a 3G mobile service, provided via the mobile operator core network 1550 . Further, the access terminal 1520 may operate in both macro environments and small scale (eg, residential) network environments. That is, depending on the current location of the access terminal 1520 , the access terminal 1520 may be accessed by the macro cell access point 1560 associated with the mobile operator core network 1550 or any of the set of femto nodes 1510 . may be served by a femto cell (eg, femto nodes 1510A and 1510B residing within the corresponding user home 1530 ). For example, a subscriber is served by a standard macro access point (eg, access point 1560 ) when outside their home, and is served by a femto node (eg, node 1510A) when at home. Here, the femto node 1510 may be backward compatible with the existing access terminals 1520 .

The femto node 1510 may be deployed on a single frequency or may be deployed on multiple frequencies. Depending on the particular configuration, a single frequency or one or more of the multiple frequencies may overlap one or more frequencies used by the macro access point (eg, access point 1560 ).

In some aspects, the access terminal 1520 may be configured to connect to a preferred femto node (eg, the home femto node of the access terminal 1520 ) whenever such a connection is available. For example, when an access terminal 1520 is within a user's home 1530 , it may be desirable for the access terminal 1520 to communicate only with the home femto node 1510 .

In some aspects, if the access terminal 1520 operates within the macro cellular network 1550 but is not on its most preferred network (eg, a network defined in a preferred roaming list), the access terminal 1520 ) may continue to search for the most preferred network (eg, the preferred femto node 1510 ) using Better System Reselection (BSR), which is available to determine if better systems are currently available. It may include periodic scanning of systems and subsequent efforts to associate with such preferred systems. Acquisition entries allow access terminal 1520 to limit the search to specific bands and channels. For example, the search for the most preferred system may be repeated periodically. Upon discovery of the preferred femto node 1510 , the access terminal 1520 selects the femto node 1510 for camping within its coverage area.

A femto node may be restricted in some aspects. For example, a given femto node may only provide a specific service to specific access terminals. In deployments with so-called limited (or closed) associations, a given access terminal is connected to a macro cell mobile network and a given set of femto nodes (eg, femto nodes 1510 residing within a corresponding user interface 1530 ). can only be served by In some implementations, a node may be restricted to not providing at least one of signaling, data access, registration, paging, or service for at least one node.

In some aspects, a restricted femto node (a node that may be referred to as a Closed Subscriber Group Home NodeB) is a node that provides service to a prepared set of restricted access terminals. This set can be expanded temporarily or permanently as needed. In some aspects, a "closed subscriber group" (CSG) may be defined as a set of access points (eg, femto nodes) that share a common access control list of access terminals. A restricted access point may include a CSG that allows multiple access terminals to connect to it. A single access terminal may have the ability to connect to multiple limited access points. A channel on which all femto nodes in range (or all restricted femto nodes) operate may be referred to as a femto channel.

Accordingly, several relationships may exist between a given femto node and a given access terminal. For example, from the point of view of an access terminal, an open femto node may refer to a femto node that does not have any restricted association (eg, a femto node does not allow access to any access terminal). A restricted femto node may refer to a femto node that is restricted in some way (eg, restricted for association and/or registration). A home femto node may refer to a femto node to which an access terminal is permitted to access and also operates (eg, permanent access is provided for a given set of one or more access terminals). A guest femto node may refer to a femto node to which an access terminal is temporarily authorized to access or operate. An alien femto node may refer to a femto node to which an access terminal is not permitted to access or operate except perhaps in emergency situations (eg, 911 calls).

From the perspective of a restricted femto node, a home access terminal may refer to an access terminal that is not authorized to access the restricted femto node (eg, the access terminal has permanent access to the femto node). A guest access terminal may refer to an access terminal that has temporary access to a restricted femto node (eg, limited based on deadline, time of use, bytes, number of connections, or some other criterion or criteria). Alien access terminal refers to an access terminal that is not authorized to access a restricted femto node (e.g., an access terminal that does not have the entitlement or permission to register with a restricted femto node) except in potentially emergency situations, such as 911 calls. can do.

For convenience, the invention herein describes several functions in the context of a femto node. However, it should be noted that a pico node may provide the same or similar functionality for a larger coverage area. For example, a pico node may be restricted, a home pico node may be defined for a given access terminal, and so on.

A wireless multiple-access communication system can simultaneously support communication for multiple wireless access terminals. As noted above, each terminal may communicate with one or more base stations via transmissions on the forward and reverse links. The forward link (or downlink) refers to the communication link from the base stations to the terminals, and the reverse link (or uplink) refers to the communication link from the terminals to the base stations. Such a communication link may be established via a single-in-single-output system, a multiple-input-multiple-output ("MIMO") system, or some other type of system.

A MIMO system uses multiple (N_T) of transmit antennas and a plurality of (N_R) of the receiving antennas. N_Ttransmit antennas and N_RThe MIMO channel formed by the receive antennas is N_Scan be decomposed into N independent channels, which are also referred to as spatial channels, where N_Smin{N_T,N_R}am. N_SEach of the n independent channels corresponds to a dimension. A MIMO system may provide improved performance (eg, higher throughput and/or greater reliability) if the additional dimensions created by multiple transmit and receive antennas are utilized.

A MIMO system may support time division duplex ("TDD") and frequency division duplex ("FDD"). In a TDD system, the forward and reverse link transmissions are made on the same frequency range, so the reciprocity principle allows estimation of the forward link channel from the reverse link channel. This allows an access point to extract transmit beam-forming gain on the forward link when multiple antennas are available at the access point.

The descriptions herein may be included in a node (eg, an apparatus) that uses various components to communicate with at least one other node. 17 illustrates some example components that may be used to facilitate communication between nodes. In particular, FIG. 17 illustrates a wireless device 1710 (eg, an access point) and a wireless device 1750 (eg, an access terminal) of a MIMO system. At the apparatus 1710 , traffic data for multiple data streams is provided from a data source 1712 to a transmit ("TX") data processor 1714 .

In some aspects, each data stream is transmitted via a respective transmit antenna. TX data processor 1714 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and can be used in the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulation symbols. to be modulated (eg, symbol mapped). The data rate, coding, and modulation for each data stream may be determined by instructions performed by the processor 1730 . Data memory 1732 may store program code, data, and other information used by processor 1730 or other components of device 1710 .

The modulation symbols for all data streams are then provided to a TX MIMO processor 1720, which may further process the modulation symbols (eg, for OFDM). Then, the TX MIMO processor 1720_TN modulation symbol streams_TTransceivers ("XCVR") 1722A through 1722T. In various aspects, the TX MIMO processor 1720 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transceiver 1722 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., , amplification, filtering, and upconversion). Then, N from transceivers 1722A-1722T_TN modulated signals are_Tare transmitted from antennas 1724A through 1724T, respectively.

In device 1750, the transmitted modulated signals are_RA signal received by antennas 1752A-1752R, and received from each antenna 1752 is provided to a respective transceiver ("XCVR") 1754A-1754R. Each transceiver 1754 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and provides a corresponding "received" symbol stream. The samples are further processed for

The receive ("RX") data processor 1760 then generates N based on the particular receiver processing technique._RN from transceivers 1754_RBy receiving and processing N received symbol streams,_Tprovides "detected" symbol streams. The RX data processor 1760 may then demodulate, deinterleave, and decode each detected symbol stream, thereby recovering the traffic data for the data stream. The processing by the RX data processor 1760 is reversed to the processing performed by the TX MIMO processor 1720 and the TX data processor 1714 in the device 1710 .

Processor 1770 periodically determines which precoding matrix (described above) to use. Processor 1770 may formulate a reverse link message including a matrix index portion and a rank value portion. Data memory 1772 may store program code, data, and other information used by processor 1770 or other components of device 1750 .

The reverse link message may include various types of information regarding the communication link and/or the data stream being received. The reverse link message is then processed by a TX data processor 1738 that also receives traffic data for multiple data streams from a data source 1736, modulated by a modulator 1780, and transceivers 1754A-1754R. ) and sent back to device 1710 .

At device 1710, modulated signals from device 1750 are received by antennas 1724, conditioned by transceivers 1722, and demodulated by a demodulator ("DEMOD") 1740; Processing by the RX data processor 1742 may extract the reverse link message sent by the device 1750 . The processor 1730 may then process the extracted message by determining which precoding matrix to use to determine the beamforming weights.

17 also indicates that communication components may include one or more components that perform access control operations as described herein. For example, the access control component 1790 can communicate with the processor 1730 and/or other components of the device 1710 to transmit/receive signals to/from another device (eg, the device 1750 ) as described herein. can cooperate Similarly, access control component 1792 can cooperate with processor 1770 and/or other components of device 1750 to transmit/receive signals to/from another device (eg, device 1710 ). It should be appreciated that the functionality of two or more of the components described for each apparatus 1710 and 1750 may be provided by a single component. For example, a single processing component may provide the functionality of access control component 1790 and processor 1730 , and a single processing component may provide the functionality of access control component 1792 and processor 1770 .

The descriptions herein may be incorporated into various types of communication systems and/or system components. In some aspects, the descriptions herein are multiple-access system capable of supporting communication with multiple users by sharing available resources (eg, by specifying one or more of bandwidth, transmit power, coding, interleaving, etc.) can be used in For example, the descriptions herein may apply to any one or combination of the following techniques: code division multiple access ("CDMA") systems, multi-carrier CDMA ("MCCDMA"), wideband CDMA ( "W-CDMA"), high-rate packet access ("HSPA", "HSPA+") systems, time division multiple access ("TDMA") systems, frequency division multiple access ("FDMA") systems, single-carrier FDMA ("SC-FDMA") systems, orthogonal frequency division multiple access ("OFDMA") systems, or other multiple access technologies. A wireless communication system using the descriptions herein may be designed to implement one or more standards, such as IS-95, cdma2000, IS-856, W-CDMA, TDSCDMA, and other standards. A CDMA network may implement a radio technology such as "Universal Terrestrial Radio Access" (UTRA), cdma2000, or some other technology. UTRA includes W-CDMA and LCR ("Low Chip Rate"). The cdma2000 technology covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as "Global System for Mobile Communications" (GSM). OFDMA networks include E-UTRA ("Evolved UTRA"), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM<img file="KR20120004534A_D0001.tif" /> It is possible to implement a wireless technology such as UTRA, E-UTRA, and GSM are part of UMTS ("Universal Mobile Telecommunication System"). The descriptions herein may be implemented in a 3GPP LTE ("Long Term Evolution") system, a UMB ("Ultra-Mobile Broadband") system, and other types of systems. LTE is a release of UMTS using E-UTRA. Although certain aspects of the present invention may be described using 3GPP terminology, the descriptions herein refer to 3GPP (Rel99, Rel5, Rel6, Rel7) technology as well as 3GPP2 (IxRTT, 1xEV-DO Rel0, RevA, RevB) technology and other It should be noted that techniques can also be applied.

The descriptions herein may be included in (eg, implemented in or by) various devices (eg, nodes). In some aspects, a node (eg, a wireless node) implemented in accordance with the descriptions herein may comprise an access point or an access terminal.

For example, an access terminal includes, is embodied as, or is a user equipment, subscriber station, subscriber unit, mobile station, mobile, mobile node, remote station, remote terminal, user terminal, user agent, user device, or any other terminology. may be known as In some implementations, the access terminal is a cellular phone, cordless phone, Session Initiation Protocol ("SIP") phone, wireless local loop ("WLL") station, "personal digital assistant" (PDA), with wireless connection capability. a handheld device, or any other suitable processing device connected to a wireless modem. Accordingly, one or more aspects described herein may include a telephone (eg, a cellular phone or a smart phone), a computer (eg, a laptop), a portable communication device, a portable computing device (eg, a PDA), an entertainment device (eg, a music device, a video device). , or satellite radio), a global positioning system (GPS) device, or any other suitable device configured to communicate via a wireless modem.

An access point is a NodeB, eNodeB, Radio Network Controller ("RAN"), Base Station ("BS"), Radio Base Station ("RBS"), Base Station Controller ("BSC"), Base Transceiver Station ("BTS"), Transceiver Function may contain, be implemented as, or be known as a unit ("TF"), a wireless transceiver, a wireless router, a basic service set ("BSS"), an extended service set ("ESS"), or any other similar terminology. can

In some aspects, a node (eg, an access node) may comprise an access node for a communication system. Such an access node may provide, for example, a connection for or a connection to a network (eg, a wired or wireless communication link to a network (eg, a wide area network such as the Internet or a cellular network). Thus, an access node may enable another node (eg, an access terminal) to access the network or some other function. It should also be noted that one or both of the nodes are portable or in some cases relatively non-portable.

Additionally, a wireless node may be capable of transmitting and/or receiving information in a non-wireless manner (eg, over a wired connection). Accordingly, a receiver and transmitter as described herein may include suitable communication interface components (eg, electrical or optical interface components) for communicating a non-wireless medium.

A wireless node may communicate over one or more underlying wireless communication links, or otherwise support any suitable wireless communication technology. For example, in some aspects a wireless node may be associated with a network. In some aspects, the network may comprise a local area network or a wide area network. A wireless device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards (eg, CDMA, TDMA, OFDM OFDMA, WiMAX, Wi-Fi, etc.) such as those described herein. . Likewise, a wireless node may support or otherwise use one or more of a variety of corresponding modulation or multiplexing schemes. Accordingly, a wireless node may include suitable components (eg, air interfaces) to establish or communicate over one or more wireless communication links using the above or other wireless communication technologies. For example, a wireless node may include a wireless transceiver with associated transmitter and receiver components that may include various components (eg, signal generators and signal processors) that facilitate communication over a wireless medium.

The components described herein may be implemented in various ways. 18-28, devices 1800, 1900, 2000, 2100, 2200, 2300, 2400, 2500, 2600, 2700 and 2800 are shown as a series of interrelated functional blocks. In some aspects, the functionality of these blocks may be implemented as a processing system that includes one or more processor components. In some aspects, the functionality of these blocks may be implemented using, for example, at least a portion of one or more integrated circuits (eg, an ASIC). As described herein, an integrated circuit may include a processor, software, other related components, or any combination thereof. The functionality of these blocks may be implemented in some other manner than described herein. In some aspects, one or more of the dashed-line blocks of FIGS. 18-28 are optional.

Devices 1800 , 1900 , 2000 , 2100 , 2200 , 2300 , 2400 , 2500 , 2600 , 2700 , and 2800 include one or more modules capable of performing one or more of the functions described above with respect to the various figures. may include For example, the receive/transmit means 1802 may correspond to, for example, a communication controller as described herein. The identifier determining means 1804 may correspond to, for example, an access controller as described herein. The allowed service determining means 1806 may correspond to, for example, a communication controller as described herein. Receiving means 1902 may correspond, for example, to a communication controller as described herein. The transmitting means 1904 may correspond to, for example, an access controller as described herein. The identifier determining means 1906 may for example correspond to an access controller as described herein. The transmitting means 2002 may correspond to, for example, an access controller as described herein. Receiving means 2004 may correspond to, for example, a communication controller as described herein. The allowed service determining means 2006 may correspond to, for example, an access controller as described herein. The configuration means 2102 may for example correspond to a preparation controller as described herein. The obtaining means 2104 may correspond to, for example, an access controller as described herein. Receiving means 2106 may correspond to, for example, a communication controller as described herein. The determining means 2108 may correspond to, for example, an access controller as described herein. The identifier determining means 2202 may for example correspond to a provisioning controller as described herein. The transmitting means 2204 may correspond, for example, to a communication controller as described herein. The allocating means 2206 may correspond, for example, to a provisioning controller as described herein. Receiving means 2302 may correspond to, for example, a readiness controller as described herein. The transmitting means 2304 may correspond to, for example, a communication controller as described herein. The identifier determining means 2402 may for example correspond to a provisioning controller as described herein. Transmitting means 2404 may correspond, for example, to a communication controller as described herein. Receiving means 2502 may for example correspond to a communication controller as described herein. Accessibility determining means 2504 may correspond to, for example, an access controller as described herein. The configuration-based determining means 2506 may correspond to, for example, an access controller as described herein. List maintaining means 2508 may correspond to, for example, an access controller as described herein. The configuration means 2602 may correspond, for example, to a preparation controller as described herein. The transmitting means 2604 may correspond to, for example, a communication controller as described herein. Receiving means 2606 may correspond to, for example, a communication controller as described herein. The transmitting means 2608 may correspond to, for example, a readiness controller as described herein. The defining means 2610 may for example correspond to a preparation controller as described herein. The monitoring means 2702 may correspond to, for example, a receiver as described herein. The beacon receiving means 2704 may correspond to, for example, a receiver as described herein. The transmitting means 2706 may correspond to, for example, a communication controller as described herein. The roaming list receiving means 2708 may correspond, for example, to a provisioning controller as described herein. The configuration means 2802 may for example correspond to a preparation controller as described herein. The beacon receiving means 2804 may correspond to, for example, a receiver as described herein. The transmitting means 2806 may correspond to, for example, a communication controller as described herein. Grant receiving means 2808 may correspond to, for example, an access controller as described herein. The prompt means 2810 may correspond to, for example, an access controller as described herein. The display means 2812 may for example correspond to an access controller as described herein.

It should be understood that reference to elements herein using designations such as "first," "second," etc. generally do not limit the quantity or order of such elements. Rather, such designations may be used herein as a convenient way of distinguishing between two or more elements or instances of an element. Thus, reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in any way. Also, unless stated otherwise, a set of elements may include one or more elements.

Those of skill in the art will appreciate that information and signals may be represented using several different technologies and techniques. For example, data, instructions, instructions, information, signals, bits, symbols, and chips that may be referenced throughout the description above refer to voltages, currents, electromagnetic waves, magnetic fields or particles. fields, optical fields or particles, or any combination thereof.

Furthermore, those skilled in the art will recognize that any of the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects described herein may be implemented in electronic hardware (eg, digitally implemented, analog implementation or a combination of the two, which may be designed using source coding or some other technique), a program or design code in various forms (which may be referred to as "software" or "software module" for convenience), including instructions, , or combinations of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects described herein may be implemented in or performed by an integrated circuit ("IC"), an access terminal, or an access point. An IC is a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electronic components, optics Codes or instructions residing within the IC, external to the IC, or both, which may include components, mechanical components, or any combination thereof designed to perform the functions described herein. can run them A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

It should be noted that any specific order or hierarchy of steps in any described process is an example of an exemplary solution. Based on design preferences, it will be appreciated that the specific order or hierarchy of steps in the processes may be rearranged but within the scope of the present invention. The appended method claims present elements of the various steps in an exemplary order, but are not intended to be limited to the specific order or hierarchy in which they are presented.

The functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example only, and not limitation, such computer-readable media may be any desired in the form of RAM, ROM, EEPROM, CD-ROM or other optical disk storage medium, magnetic disk storage or other magnetic storage devices, or instructions or data structures. It may include any other medium that can be used to convey or store program code and that can be accessed by a computer. Also, any connecting means is properly termed a computer-readable medium. For example, if the Software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, such Coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks generally store data magnetically. However, the discs reproduce the data optically through a laser. Combinations of these should also be included within the scope of computer-readable media. In summary, a computer-readable medium may be embodied in any suitable computer-program product.

From the above description, in some aspects, a first method of communication comprises determining an identifier for a set of at least one access point that is configured to provide at least one service only to a set of at least one access terminal, the identifier uniquely identifies a set of said at least one access point within an operator network; and transmitting the identifier to each access point in the set of at least one access point. Further, in some aspects, at least one of the following may also apply to the first communication method: the identifier comprises a network identifier, and the network comprises a cellular operator domain; the identifier is determined in connection with activity of an access point in the set of at least one access point; the set of at least one access point includes a plurality of access points belonging to a common management domain; the set of at least one access point includes a plurality of access points associated with a common closed subscriber group; the identifier is text-based; each access point in the set of at least one access point is limited to providing, for at least one other access terminal, at least one from a group comprising: signaling, data access, registration, and service; each access point in the set of at least one access point comprises a femto node or a pico node; determining the identifier comprises receiving a request for the identifier, and determining whether the identifier is already in use by at least one access point; if the requested identifier is already in use by the at least one access point, transmitting the identifier comprises transmitting in response to the request a response comprising the identifier not being used by any other access point; each access point in the set of at least one access point provides at least one other service to at least one other access terminal; the method further comprises assigning a unique device identifier to each access point in the set of at least one access point; Each access point in the set of at least one access point provides different services to the set of at least one access terminal than for the at least one other access terminal.

From the above description, in some aspects, a second method of communication comprises receiving, at an access point in the set of at least one access point, an identifier for a set of at least one access point - the at least one access point each access point in the set of at least one access point configured to provide at least one service only to a set of at least one access terminals, the identifier uniquely identifying the at least one access point within an operator network; and transmitting the identifier by order-the-air. Further, in some aspects, at least one of the following may also apply to the second method of communication: wherein the method is an access terminal in the set of at least one access terminal in response to transmitting the identifier further comprising receiving a registration message from; the identifier comprises a network identifier, and the network comprises a cellular operator domain; the identifier is received as a result of activation of an access point receiving the identifier; the set of at least one access point includes a plurality of access points belonging to a common management domain; the set of at least one access point includes a plurality of access points associated with a common closed subscriber group; the identifier is text-based; each access point in the set of at least one access point is limited to providing, for at least one other access terminal, at least one from a group comprising: signaling, data access, registration, and service; each access point in the set of at least one access point comprises a femto node or a pico node; each access point in the set of at least one access point provides at least one other service to at least one other access terminal; each access point in the set of at least one access point provides different services to the set of at least one access terminal than for the at least one other access terminal; the identifier is received in response to a request for the identifier; The method further comprises determining a suggested identifier, wherein the request includes the proposed identifier.

Further, from the above description, in some aspects a third method of communication includes determining identifiers of access terminals in a set of access terminals; and transmitting the identifier to at least one access point that is configured to provide at least one service only to the set of access terminals. Further, in some aspects, at least one of the following may also apply to the third communication method: the identifiers include permanent identifiers for access terminals; the identifiers include temporary identifiers for access terminals; the identifiers include network address identities or mobile station integrated services digital network numbers; the identifiers are transmitted in response to a request from any of the at least one access point; the determining comprises receiving the identifiers from a network node; the determining comprises receiving identifiers from a web server enabling a user to define access terminals that are allowed to receive at least one service from at least one access point; the set of access terminals is associated with a common closed subscriber group; each access point of the at least one access point is limited not to provide at least one of the group including signaling, data access, registration and service to at least one other access terminal; each access point of the at least one access point includes a femto node or a pico node; Each access point of the at least one access point provides at least one other service to the at least one other access terminal.

Further, from the above description, in some aspects a fourth method of communication includes receiving a message relating to a request by an access terminal to access an access point, the message comprising a first identifier associated with the access terminal -; determining a second identifier associated with an access terminal based on the first identifier; and determining whether the access terminal is permitted to receive service from the access point based on the at least one identifier and the second identifier associated with the access terminal. Further, in some aspects, at least one of the following may also apply to the fourth communication method: the first identifier comprises a temporary identifier, the second identifier comprises a permanent identifier; the second identifier comprises a network address identity of the access terminal or a mobile station aggregation services digital network number of the access terminal; the second identifier identifies at least one closed subscriber group to which the access terminal can access, and the at least one identifier associated with the access point comprises a closed subscriber group identifier associated with the access point; The at least one identifier associated with the access point comprises an access list for the access point, and determining whether the access terminal is allowed to receive service from the access point comprises determining whether the second identifier is in the access list. including; The network node makes a determination as to whether the access terminal is allowed to receive service from the access point, the message comprising a request from the access point to authenticate the access terminal, the method comprising: sending a message to the access point indicating a determination as to whether it is allowed to receive the service of determining the second identifier comprises transmitting the first identifier to the network node and receiving the second identifier from the network node; the access point makes a determination as to whether the access terminal is allowed to receive service from the access point; the at least one identifier associated with the access point is received from the network node; The determination of whether the access terminal is permitted to receive service from the access point comprises: transmitting a second identifier associated with the access point and at least one identifier to a network node; receiving an indication from the network node as to whether it is allowed to receive; Determining whether the access terminal is allowed to receive service from the access point comprises transmitting a second identifier to a network node, and receiving at least one identifier associated with an access point associated with the network node; ; the access point is limited not to provide, for at least one other access terminal, at least one of a group including signaling, data access, registration and service; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects a fifth method of communication includes receiving from an access point a request to authenticate an access terminal, and at least of the access points through which the access terminal is permitted to receive at least one service. and transmitting at least one identifier identifying the one set to the access point. Further, in some aspects at least one of the following may also apply to the fifth communication method: the at least one identifier comprises a closed subscriber group identifier; the request includes the network address identity of the access terminal or the mobile station aggregation services digital network number of the access terminal; the method further comprises determining at least one identifier based on a permanent identifier associated with the access terminal, and determining a permanent identifier based on a temporary identifier associated with the access terminal; the request includes a temporary identifier; the determining of the permanent identifier includes transmitting the temporary identifier to a network node, and receiving the permanent identifier from the network node; The method further comprises receiving at least one identifier from the network node; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a sixth method of communication comprises sending, by the access point, a request to authenticate the access terminal, and in response to the request, the access terminal providing at least one service. and receiving at least one identifier identifying at least one set of access points allowed to receive. Further, in some aspects, at least one of the following may also apply to a sixth communication method: the method determines whether an access terminal is allowed to receive a service from an access point based on the at least one identifier further comprising determining whether; the at least one identifier comprises a closed subscriber group identifier; the at least one identifier identifies a closed subscriber group to which an access terminal can access; the determining comprises determining whether the at least one identifier matches a closed subscriber group identifier associated with an access point; the request is sent based on a determination that the access terminal is not listed on the access point's local access list; the request includes the network address identity of the access terminal or the mobile station aggregation services digital network number of the access terminal; the request includes a temporary identifier associated with the access terminal; the method further comprises: obtaining session information associated with an access terminal from a network node, the session information including context information for the access terminal, and the request including the context information; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a seventh method of communication comprises: transmitting, by the access point, a request comprising an identifier of a set of at least one access terminal entitled to receive service from the access point; and receiving, in response to the request, a list of at least one access terminal authorized to receive a service from the access point. Further, in some aspects, at least one of the following may also apply to the seventh communication method: the method allows the access terminal to receive a service from the access point based on at least one identifier further comprising determining whether the at least one identifier comprises at least one closed subscriber group identifier; the identifier comprises a list of at least one closed subscriber group identifier associated with the access terminal; the determining comprises determining whether a closed subscriber group identifier associated with the access point is on the list; the request is sent based on a determination that the access terminal is not listed on the access point's local access list; the request includes the network address identity of the access terminal or the mobile station aggregation services digital network number; the request includes a temporary identifier associated with the access terminal; the method includes obtaining session information associated with an access terminal from a network node, the session information including context information of the access terminal, and the request including the context information; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, an eighth communication method includes receiving from the first access point an identifier of at least one other access point to which the access terminal is entitled to access, and based on the identifier , determining whether the at least one other access point is accessible. Further, in some aspects, at least one of the following may apply to the eighth communication method: said determining comprising prompting a user to determine whether to enable access; said determining comprises displaying an indication of the identifier and receiving an input indicating whether to enable access; The method further includes determining based on the configuration information whether to automatically enable the access or to enable the access in response to the prompt; the method further comprising maintaining a list of access points to which an access terminal is allowed to access, further based on the determining list; the method further comprises maintaining a list of access points from which the user is not selected to access, wherein the determination is also based on the list; the identifier includes a network identifier; the identifier comprises a closed subscriber group identifier; the identifier is received via an SMS message, an application protocol message, a radio link message, or a pager; the identifier is received from a network node; each access point of the at least one access point is limited not to provide, for at least one other access terminal, at least one of a group including signaling, data access, registration and service; Each access point of the at least one access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a ninth communication method includes: configuring an access point to an initialization mode; transmitting a default beacon comprising a default configuration during an initialization mode; receiving a message from the access terminal in response to the default beacon; and sending the preferred roaming list to the access terminal in response to the message. Further, in some aspects, at least one of the following may also apply to the ninth communication method: a default beacon comprising the default configuration is transmitted at a first power level, the method comprising: further comprising configuring into an operational mode, whereby beacons are transmitted at a second power level that is higher than the first power level; the first power level provides a smaller coverage area than that provided by the second power level; the default configuration includes a default network identifier that is different from the network identifier used for the non-initialization mode of operation; the default configuration specifies a default system and network identifiers of at least one access point of the highest priority, and the preferred roaming list specifies network identifiers of at least one access point of the highest priority and another system; the default beacon is transmitted at a default frequency; The preferred roaming list defines another beacon frequency for the access point that is different from the default frequency; The method further comprises defining a preferred roaming list based on another preferred roaming list associated with the access terminal; The method further comprises receiving another preferred roaming list from the network node; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a tenth method of communication includes monitoring beacons at the access terminal based on a first preferred roaming list defining a default configuration; receiving a beacon including the default configuration from the access point according to a result of the monitoring; sending a message to the access point in response to the received beacon; and receiving a second roaming list from the access point in response to the message, wherein the second roaming list defines a configuration different from a default configuration. Further, in some aspects, at least one of the following may also apply to the tenth method of communication: the first preferred roaming list includes a default roaming list for initialization operations, and the second preferred roaming list includes a non - contains a roaming list for initialization operations; the default configuration includes a default network identifier; the second preferred roaming list includes another network identifier associated with the access point that is different from the default network identifier; the beacon is received at a default frequency defined by a first preferred roaming list, the second preferred roaming list defining a carrier frequency for an access point different from the default frequency; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, an eleventh communication method includes configuring an access point having a first identifier of an access terminal, obtaining a second identifier of the access terminal based on the first identifier; receiving, by the access terminal, a message requesting access, and determining at the access point whether to grant the requested access based on the second identifier. Further, in some aspects, at least one of the following may also apply to the eleventh communication method: the first identifier comprises a network address identity or a mobile station aggregation services digital network number; the second identifier comprises an electronic serial number or international mobile subscriber identity; the obtaining step includes transmitting a first identifier to a network node, and receiving a second identifier from the network node according to a result of the transmission of the first identifier; the determining comprises comparing an identifier received in the message from an access terminal with the second identifier; The determining includes transmitting a second identifier to a network node, and receiving, according to a result of the transmission of the second identifier, an indication of whether to allow the requested access, the access point via a web interface composed; the access point is limited not to provide at least one of a group including signaling, data access, registration and service to at least one other access terminal; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a twelfth method of communication includes configuring an access terminal with a preferred roaming list comprising an identifier of a set of access points that are restricted to provide service to the limited set of access terminals. , receiving a beacon from one of the access points, the beacon comprising an identifier, sending a message to the one access point in response to the beacon; and receiving permission to access the access point in response to the message. Further, in some aspects, at least one of the following may also apply to the twelfth method of communication: The set of access points includes all access points within the restricted cellular operator domain to provide service to the limited set of access terminals. do; the identifier includes a network identifier; the preferred roaming list defines a carrier frequency used by a set of access points; The method further includes prompting the user to determine whether to access the one access point; The method further comprises displaying an indication of the one access point, and receiving a user input indicating whether to access the one access point; each access point of the set of access points is constrained not to provide at least one of a group comprising signaling, data access, registration and service to at least one other access terminal; Each access point of the set of access points includes a femto node or a pico node.

Further, from the above description, in some aspects, a thirteenth method of communication comprises: receiving a request from an access point to authenticate an access terminal; an identifier of a set of at least one access terminal receiving a service from the access point; determining whether the access terminal is allowed to receive service from the access point based on Further, in some aspects, at least one of the following may also apply to the thirteenth communication method: the determining comprises determining whether identifiers are in an access list of an access point; the request compares an access list; the identifier includes a permanent identifier; the method further comprises determining a permanent identifier based on the temporary identifier of the set of at least one access terminal; the determining of the permanent identifier includes transmitting the temporary identifier to a network node, and receiving the permanent identifier from the network node; the identifier comprises a closed subscriber group identifier; the identifier comprises a list of at least one closed subscriber group identifier associated with the set of at least one access terminal, the determining comprising determining whether a closed subscriber group identifier associated with the access point is in the list; the access point is limited not to provide, for at least one other access terminal, at least one of a group including signaling, data access, registration and service; The access point includes a femto node or a pico node.

Further, from the above description, in some aspects, a fourteenth method of communication comprises: receiving, at an access point, an access request from an access terminal, the access request comprising a first identifier associated with the access terminal; determining a second identifier associated with the access terminal based on the first identifier; and allowing the access terminal to provide service from the access point based on the second identifier and the list of at least one access terminal authorized to receive service from the access point. and determining whether it is allowed to receive. Further, in some aspects, at least one of the following may also apply to the fourteenth communication method: the first identifier comprises a temporary identifier, the second identifier comprises a permanent identifier; the first identifier comprises a network address identity of the access terminal or a mobile station aggregation services digital network number of the access terminal; the list is received from the network node and includes individual access terminal identifiers; the second identifier includes a closed subscriber group identifier associated with the access terminal, and the list includes a closed subscriber group identifier associated with the access point; the determining comprises transmitting a second identifier and list to a network node, and receiving an indication from the network node as to whether the access terminal is permitted to receive service from the access point; the determining comprises sending a second identifier to a network node, and receiving the list from the network node; the access point is limited not to provide, for at least one other access terminal, at least one of a group including signaling, data access, registration and service; The access point includes a femto node or a pico node.

In some aspects, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, and fourteenth communication A function corresponding to one or more of the methods may be implemented, for example, in an apparatus using a structure as described herein. Further, a computer-program product may comprise codes configured to cause a computer to provide functionality corresponding to one or more of these communication methods.

The previous description of the described aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the invention. Accordingly, the present invention is not intended to be limited to the aspects presented herein, but is to be accorded the widest scope in accordance with the principles and novel features described herein.