Resolving node identifier confusion

[0001] The present application relates generally to communication, and more specifically, but not exclusively, to conflict resolution related to communication nodes.

Introduction [0002] Wireless communication systems are widely used to provide various types of communication (e.g., voice, data, multimedia services, etc.) to many users. As the demand for high-bandwidth services and multimedia data is growing rapidly, there is a challenge to implement efficient and reliable communication systems with better performance.

[0003] To complement traditional base stations of cell phone networks (e.g. macrocells), base stations with a small coverage area can be deployed (e.g. installed in the user's home) to provide better wireless coverage for indoor mobile units. Such base stations with a small coverage area are generally known as access point base stations, home NodeB nodes or femtocells. Usually, such base stations with a small coverage area are connected to the Internet and the mobile operator's network via a DSL router or cable modem.

[0004] In practice, there may be a relatively large number of base stations (e.g., femtocells) used in a given area (e.g., within the coverage area of ​​a given macrocell). In this case, there is a need for effective techniques for

And identifying these base stations so that other nodes in the network can communicate with these base stations.

SUMMARY OF THE INVENTION [0005] The invention is independent 1, 6 and 7. exemplary aspects of any reference defined by the claims

The following is a summary of the invention. It is to be understood that by the term aspects herein may refer to one or more aspects of the invention.

[0006] The invention relates, in some aspect, to resolving a conflict associated with node identifiers. For example, a limited number of node identifiers can be defined within a network such that more than one node (e.g., access point) in the network can be assigned the same identifier. Therefore, when the access terminal is switched from the source node to the destination node, there may be a conflict regarding the identification of the destination node. This document describes various techniques for resolving such conflict.

[0007] In some aspects, the access terminal to be switched to the destination node may resolve the conflict regarding the destination node by acquiring a unique identifier associated with the destination node. In some implementations, the access terminal sends this unique identifier to the source node that initiates operations. In other implementations, the access terminal has a unique identifier to initiate handover operations.

[0008] The access terminal may be configured to detect conflict. In some cases, the access terminal independently detects conflict. For example, the access terminal may monitor identifiers associated with the received handovers.

uses

53 / 59P31502EN00 signals and generate measurement reports that indicate that multiple nodes use the same identifier.

[0009] As another example, a signal threshold may be assigned to a set of identifiers that have been identified as possibly conflicting. This threshold value can then be used to trigger the acquisition of a more unique identifier or to trigger a conflict determination operation on the source node. [0010] In some cases, the access terminal detects a conflict in response to a request. For example, the source node may periodically send a message to the access terminal requesting that the access terminal send conflict information via a measurement report.

[0011] The access point may be configured to detect conflict. For example, the access point may detect a conflict based on the detection of neighborhoods, the destination node identified in the switch request, or the received configuration information. Once a conflict is detected, the access point may send a message to the access terminal requesting that the access terminal acquire a unique identifier to resolve the conflict. In some cases, this message may instruct the access terminal to use a unique identifier to initiate handover operations.

[0012] Conflict resolution can also be used when the access terminal directly gains access to the destination node. For example, in the event that the access terminal establishes communication with the destination node before the destination node obtains resources for the access terminal, the access terminal may send a unique identifier for the source node to the destination node. In this way, the destination node can obtain the appropriate resources from the source node even when the node identifier used by the source node is potentially misleading.

[0013] "Ericsson: Automatic neighbor cell configuration; 3GPP TSG-SA5 "refers to automatic relations between neighboring cells (ANRL). The measuring cell identifier (MCI) is a level 1 identifier for a cell, which may not be unique in the network and therefore may be reused. CIPL is another identifier (level 3) that is usually unique. The proposed ANRL method must be able to automatically identify and identify new neighbors. To this end, the eNodeB instructs the UE to make measurements and report with the new MCI identifier. If it is new, the eNodeB requests a new CIPL identifier from the new eNodeB and reports it. Then, the list of neighborhood relations is updated and the X2 interface can be configured.

[0014] The document "Huawei: Detection of conflicting cell identities; 3GPP TSG RAN WG3 Meeting # 57bis ”. is for detecting conflicting cell identifiers. Global cell identifiers (GCI) and cell physical layer identifiers (PLCI) can be used for this purpose. UE equipment could detect PLCI conflict during cell search. It could then decode the GCI value to assess if there is a conflict.

[0015] Document "Qualcomm Europe: Inter-RAT / frequency

Automatic Neighbor Relation Function; 3GPP TSG RAN2 # 60 "refers to sending a message from cell A to the mobile terminal and contains the Phy-CID. Then, a message containing the Global-CID is sent from the mobile terminal to cell A.

[0016] T-Mobile: Automatic Neighbor Cell List Configuration - required Measurement and signaling support; 3GPP TSG-RAN WG3 Meeting # 57bis "refers to measuring signal strength in UE equipment and reporting it to LTE.

53 / 59P31502PL00

BRIEF DESCRIPTION OF THE DRAWINGS [0017] These and other examples of aspects of the invention will be described in the detailed description and the appended claims, which are found below, and in the accompanying drawings, in which:

[0018] FIG. 1 is a simplified block diagram of several sample aspects of a communication system configured for conflict resolution;

[0019] FIG. 2 is a simplified diagram illustrating coverage areas for wireless communication;

[0020] FIG. 3 is a flowchart of several sample aspects of operations that may be performed to specify the use of the second type of identifier; [0021] FIG. 4 is a simplified block diagram of several sample aspects of components that can be used in communication nodes;

[0022] FIG. 5 is a flowchart of several sample aspects of operations that may be performed to determine whether to use the second type of identifier to communicate with a node;

[0023] FIG. 6 is a flowchart of several sample aspects of operations that can be performed to determine if a second type of identifier should be used to communicate with a node based on a list of identifiers;

[0024] FIG. 7 depicts a flowchart of several sample aspects of operations that can be performed to resolve conflicts for a source node;

[0025] FIG. 8 is a flowchart of several sample aspects of operations that can be performed to determine whether to request a second type of identifier; [0026] FIG. 9A and 9B show a flowchart of several sample aspects of operations that can be performed

To cause the terminal to obtain the second type of identifier above;

[0027] FIG. 10A and 10B are a flowchart of several sample aspects of operations that may be performed to cause the terminal to obtain the second type of identifier above;

[0028] FIG. 11 is a flowchart of several sample aspects of operations that can be performed in conjunction with a conflict detection access terminal;

[0029] FIG. 12 is a flowchart of several sample aspects of operations that may be performed in conjunction with a conflict detection access terminal;

[0030] FIG. 13 is a flowchart of several sample aspects of operations that may be performed in conjunction with an access terminal providing a conflict report on demand;

[0031] FIG. 14 is a simplified diagram of a wireless communication system;

[0032] FIG. 15 is a simplified diagram of a wireless communication system comprising femto nodes;

[0033] FIG. 16 is a simplified block diagram of several sample aspects of communication components; and [0034] FIG. 17-21 are simplified block diagrams of several sample aspects of devices configured for conflict resolution, as already explained.

[0035] As a general practice, the various features illustrated in the drawings may not be made to scale. Therefore, for the sake of clarity, the dimensions of the various features can be arbitrarily increased or decreased. In addition, some simplified for transparency. Thus, drawings may not show all components of the instrument (e.g. device) or method. Finally, the same reference designations can be used to designate the same features in the description and figures.

53 / 59P31502PL00

DETAILED DESCRIPTION [0036] FIG. 1 illustrates several nodes in an example communication system 100 (e.g., parts of a communication network). For illustrative purposes, various aspects of the invention will be described in the context of one or more access terminals, access points and network nodes that communicate with each other. It should be noted, however, that the information contained herein may be used for other types of devices or other similar devices referenced using different terminology (e.g. base stations, user equipment and the like).

[0037] Access points in the system 100 provide one or more services (e.g., network connectivity) for one or more wireless terminals (e.g., access terminal 102) that can be installed inside or that may travel through a related geographical area. For example, at various times, access terminal 102 may connect to access point 104, any of a set of 1-N access points (represented by access points 106 and 108 and associated ellipses), or access point 110. Each of access points 102 - 110 it may communicate with one or more network nodes (represented, for convenience, by network node 112) to facilitate wide area network connectivity. Such network nodes may take various forms such as, for example, one or more core and / or radio network units (e.g. configuration manager, mobility management unit, or other suitable network unit).

[0038] Each access point in the system 100 is associated with a first type of identifier, referred to herein as the node identifier. In various implementations, such

The identifier may include, for example, a physical cell identifier ("PCID"), a pseudo-random number shift ("PN") or acquisition pilot. Usually, a fixed number (e.g. 504) of node identifiers is defined in a given system. In this case, there may be a conflict when the number of access points exceeds the number of node identifiers. FIG. 1 illustrates a simple example of this, where both "access point 106" and "access point 110" have been assigned the "identifier 1."

[0039] As the access terminal 102 moves in the system 100, the access terminal 102 may be switched from one access point (e.g., access point 104) to another access point (e.g., access point 110). The decision to switch the access terminal 102 to the access point 110 can be made based on whether the access terminal 102 receives particularly strong signals from the access point 110. Here, the access terminal identifies signals from the access point identifier of the node associated with (e.g. inside) these signals. To perform the handover, various information maintained by the source access point 104 (access point to which the access terminal is currently connected) is transmitted to the destination access point 110. In the absence of a conflict, this can be done by using the node identifier ("identifier 1") associated with the first access point 110. When a conflict occurs, however, as in the example of FIG. 1, access point 104 may not be able to determine whether information should be sent to access point 106 or access point 110.

[0040] For conflict resolution such as this, access terminal 102 and / or access point 104 are configured to detect conflict and determine the second type of identifier associated with access point 110. In some aspects,

102

110 using placed

53 / 59P31502EN00 the second type of identifier includes a unique identifier. For example, the second identifier type may be unique within a larger area than the first identifier type. In some implementations, the second type of identifier may be unique in the operator's network. In various implementations, such a unique identifier may include, for example, a global cell identifier ("GCI"), node identifier sector identifier, Protocol address some other identifier that access 110 inside access terminal 102 that can detect access ("ANID")

Internet, or uniquely identifies a network point.

[0041] In some implementations, it includes a conflict detector 114, an actual or potential conflict between nodes in the system 100. Upon detecting a conflict, the access terminal 102 (e.g., unique identifier controller 116) may obtain a unique identifier. For example, access terminal 102 may monitor a signal containing a unique identifier that is broadcast by access point 110. After detecting a conflict, the access terminal 102 may also inform the access point 104 about the conflict and / or the unique identifier.

[0042] In some implementations, the access point 104 includes a conflict controller 118 that can detect actual or potential conflict between nodes in the system 100. For example, conflict controller 118 can independently detect a conflict or, upon receiving a conflict indication from the access terminal 102, conflict controller 118 may perform additional steps to determine if there is a conflict. If a conflict is detected, the access point 104 may request the access terminal 102 to acquire a unique identifier.

[0043] After resolving the conflict earlier, access point 104 as discussed (e.g., controller 120

53 / 59P31502EN00) can initiate switching operations based on a unique identifier. In this way, access terminal 102 can be efficiently switched to the desired target access point. As will be described below, in some implementations, access terminal 102 (e.g., using a switch controller operation, not shown) can initiate switch operations based on a unique identifier (e.g., when it resolves a conflict).

[0044] The conflict described above may occur in the network 200 as shown in FIG. 2, where some access points provide macro coverage, while other access points provide less coverage. In this case, macro coverage areas 204 may be provided by, for example, macro access points of a large area cellular network, such as a 3G network, usually called a macro cell network or a wide area network ("WAN"). In addition, smaller coverage areas 206 can be provided by, for example, network environment access points in an apartment or building, usually referred to as a local area network ("LAN"). Because the access terminal ("AT") moves in such a network, the access terminal can be operated at specific locations by means of access points that provide macro coverage, while the access terminal can be operated at other locations by access points that provide a smaller area coverage. In some aspects, access points for smaller coverage areas can be used to provide incremental increase in capacity, coverage in a building, and various services, all of which lead to better user experience.

[0045] In the present specification, a node (e.g. access point) that provides coverage over a relatively large area can be referred to as a macro node, while a node that provides coverage over a relatively small area (e.g. apartment) may

53 / 59P31502EN00 be referred to as the femto node. Note that the information contained herein can be applied to nodes associated with other types of coverage areas. For example, a pico node may provide coverage in an area that is smaller than the macro area and larger than the femto area (e.g., coverage within a commercial building). In various applications, different terminology may be used to specify the macro of the node, femto node, or other access point nodes. For example, a macro node may be configured or referred to as an access node, base station, access point, eNodeB node, cell macro, and so on. Also, the femto node may be configured or referred to as Home NodeB, Home eNodeB, access point base station, femto cell, and the like. In some implementations, a node may be associated with (e.g., divided into) one or more cells or sectors. A cell or sector associated with a macro node, femto node, or pico node may be called a macro cell, femto cell, or pico cell, respectively.

[0046] In the example of FIG. 2, several tracking areas 202 (or alignment areas or location areas) are defined, each of which includes several macro coverage areas 204. Here, the coverage areas associated with the tracking areas 202A, 202B, and 202C are indicated by broad lines, and the macro coverage areas 204 are represented by hexagons. As mentioned above, tracking areas 202 may also include femto coverage areas 206. In this example, each of the femto coverage areas 206 (e.g., the femto coverage area 206C) is represented within one or more macro coverage areas 204 (e.g., macro coverage area 204B). It should be noted, however, that the femto coverage area 206 may not lie entirely within the macro coverage area 204. One or more pico or femto coverage areas (not shown) may also be defined within a given tracking area 202 or macro coverage area 204.

[0047] In deployment (e.g. dense urban deployment), when a large number of access points, such as femto and pico nodes, are located within a given area, two or more of these access points may be assigned the same identifier. For example, in macro coverage area 204A, femto coverage areas 206A and 206D may be assigned the same identifier. In this case, the node identifier conflict (e.g. PCID conflict) may occur because many adjacent nodes that are near the serving access point of the access terminal announce the same node identifier. For example, in FIG. 1 access points 106 and 110 may include femto nodes or pico nodes that advertise "identifier 1" by means of corresponding broadcast pilot signals. Furthermore, both of these access points may be close to access point 104 (e.g. access point macro) that currently supports access terminal 102. In this case, access point 104 may be aware of both access points 106 and 110 and, as a result, conflict may arise when switching to an access point identified by "identifier 1 is desirable. ".

techniques for solving any type of node.

[0048] In general, the conflicts described herein can be used to. However, in many embodiments, macro access points in a given area will be planned so that there will be no conflict associated with switching to the macro access point. In such cases, the conflict resolution techniques discussed here can be applied to any non-macro nodes on the network. Such nodes other than macro nodes may include, for example, nodes that are unplanned. As mentioned above, such non-macro nodes may contain femto nodes (e.g., arranged by individual persons) as well as low power pico nodes arranged by the operator. Also as will be

Discussed in more detail, the node may be limited in some way (e.g., limited in terms of access). Thus, the conflict resolution techniques discussed here can be applied to restricted nodes (e.g., nodes associated with a closed subscriber group).

[0049] In view of the above, various techniques that may be used to resolve the conflict according to the information contained herein will be described with reference to FIG. 3-13. In short, FIG. 3 illustrates several components that can be used in an access point or access terminal, and the flowchart of FIG. 4 - 13 relate to various conflict resolution techniques.

[0050] For illustrative purposes, the operations of FIG. 4-13 (or any other operations discussed or discussed herein) may be described as being carried out by specific components (e.g., system components 100 and / or components shown in FIG. 3). However, it should be noted that these operations can be performed by other types of components and can be performed using a different number of components. It should also be noted that one or more operations described herein may not be used in a given implementation.

[0051] FIG. 3 illustrates several sample components that may be embedded in nodes such as access terminal 102 and access point 104 to perform conflict resolution operations, as already explained herein. The described components can also be embedded in other nodes in the communication system. For example, other nodes in the system may include components similar to those described for access terminal 102 and access point 104 to provide similar functionality. A given node may contain one or more components described. For example, the access terminal may include a plurality of transceiver transceiver components that enable the access terminal

Operating at multiple frequencies and / or communication by other technology.

[0052] As shown in FIG. 3, access terminal 102 and access point 104 may include transceivers 302 and 304, for communication with other nodes, respectively. The transceiver 302 includes a transmitter 306 for sending signals (e.g., messages a receiver 308 for receiving signals e.g.

the connection is explained.

conflict detectors 318 and containing performed pilot signal searches). Transceiver 304 includes a transmitter 310 for sending signals and a receiver 312 for receiving signals.

[0053] The access terminal above 102 and the access point 104 also include other components that can be used in conflict resolution operations, as already here For example, the access terminal above 102 and the access point may include communication controllers 314 and 316, respectively, to manage communication with other nodes (e.g., send and receive messages / indications) and to provide other related functionalities, as already explained here. Access terminal 102 and / or access point 104 may include and 320 conflicts, respectively, for detecting to provide other related functionalities, as already explained herein. Access terminal 102 and / or access point 104 may include identifier controllers 322 and 324, respectively, for managing (e.g., selecting, acquiring, requesting, and so on) node identifiers to provide other related functionality, as already explained herein. Exemplary operations of the other components of FIG. 3.

[0054] For ease of use, access point 102 access 104 is shown in FIG. 3 as components that can be used in the various examples described below in conjunction with FIG. 4 - 13. In practice, one or more of the components shown may not be used in this example. As an example, in and terminal containing

In some implementations, access terminal 102 may not include a conflict detector 318, and in some implementations, access point 104 may not include a conflict detector 320. [0055] Referring now to FIG. 4 and 5, in some aspects the conflict associated with the first type of identifier (e.g. PN offset, PCID, etc.) can be resolved by specifying the use of the second type of identifier (e.g. ANID, GCI etc.) in combination with switching or other operation.

[0056] This scheme can be used, for example, when an access terminal that is connected to a macro access point activates searches for nearby femto nodes (e.g., a home femto node). When the access terminal detects a signal from the femto node, the access terminal may obtain a first type identifier (e.g., pilot ID, sector ID, PCID, etc.) from the signal. If the received signal strength is above the threshold value and / or the access terminal is authorized to access the discovered femto node (e.g. the access point is placed on the access terminal's preferred roaming list), the access terminal may add this access point to the active set for the access terminal .

[0057] The first access terminal to perform route opening for this femto node from the access point macro will establish a mapping between the first type identifier and the second type identifier (e.g. ANID, GCI, etc.) at the macro access point. Here, after receiving the second identifier type from the access terminal, the macro access point may start neighborhood detection using this femto node.

[0058] The presence of successive femto nodes with the same identifier of the first type in the macro coverage will result in the macro access point determining that there are multiple access points using common

A first type identifier (i.e., conflict detection with respect to that identifier). In this case, the macro access point may recognize the presence of these other femto nodes by, for example, neighborhood detection or by receiving messages from the access terminal that has recognized the conflict. The access point macro can then always request a second type of identifier whenever it receives a message (e.g. on route opening) containing the conflicting identifier. After receiving the second type of identifier from the access terminal, the macro access point may start detecting neighborhood with this femto node.

[0059] Additionally, as optimization in some implementations, the access terminal may send messages with the second identifier type by default. For example, the access terminal may always use the second type of identifier when sending a route open message or other message to its home femto node.

[0060] Referring initially to FIG. 4, as represented by block 402, the access point (e.g., access point 104) receives a message from the access terminal, wherein the message is directed to a node (e.g., a destination node such as access point 110) identified by the first node identifier. For example, as discussed earlier, the access terminal may receive a route open request containing a PN offset or some other type of message containing some other type of identifier. It should be noted that this message can have different forms. For example, in various implementations, the message may include a resource setting message for a handover, a handover request, an active set add request, a interference management signaling, a signal strength measurement report, or a message for reserving at least one resource.

[0061] As represented by block 404, the access point determines whether another node is identified by

53 / 59P31502EN00 first node identifier. The access point can detect such conflict in various ways. For example, as discussed earlier, an access point may receive messages from one or more access terminals that indicate identifiers used by neighboring nodes. In some cases, the access point may perform neighborhood detection and determine that two or more adjacent nodes use an identical identifier. In some cases, the access point may receive information from the configuration manager represented in FIG. 1) that indicate which access point identifiers used by the neighbors (e.g., node 112 are access identifiers. In some cases, operation at block 404 may include determining whether the identifiers maintained identifier is a list by the access point. As discussed herein, this list of identifiers may include, for example, identifiers that are not guaranteed to be free of conflict, identifiers that are potentially conflicted, or identifiers that have been identified as conflicting. In some aspects, the identifier list may include a range of identifier values.

[0062] As represented by block 406 and 408, if no conflict is detected, the access point may perform the appropriate operation (e.g., handover operation) based on the first node identifier.

[0063] As represented by block 410, if a conflict is detected, the access point sends a message to the access terminal which specifies that the access terminal should use a second node identifier (e.g. ANID) to establish communication with the node. This message can take many forms. For example, the message may contain a rejection message (e.g., rejection of route opening) that instructs the access terminal to use different identifiers.

[0064] As represented by block 412, the access point may then receive a message from the access terminal that includes the second node identifier. The access point may perform the appropriate operation (e.g., handover) based on the second node identifier. In some implementations this may involve tunneling of the message containing the second node identifier to the destination node.

[0065] In some aspects, the operations of FIG. 4 relate to reserving resources using a backhaul connection for switching operations (e.g. in connection with the operation of adding an active set). In addition, because conflicted nodes may be restricted in some aspects (e.g., binding constraints or in some other way as discussed below), these operations may also involve reserving resources for restricted nodes.

[0066] FIG. 5 relates in some aspects to specifying the use of a non-conflicting identifier to establish communication with a node. In some aspects, these operations may be complementary to some of the operations of FIG. 4.

[0067] As represented by block 502, the access terminal (e.g., access terminal 102) selects for transmission a message to the destination node identified by the first node identifier. As mentioned above in block 402, this message may be sent using an associated access point (e.g., access point 104).

[0068] As represented by block 504, the access terminal determines whether another node can be identified by the first node identifier. This determination can be performed in various ways. As discussed earlier, the access terminal could send a message to access point 104 using the first node identifier and receive a message from the access point 104 that indicates that it is occurring

Conflict (and which specifies the use of the second node identifier). In some cases, this determination may involve attempting to communicate with the destination node and receiving messages from the destination node that indicates that communication is not authorized. Such a rejection message may be received because the context for the access terminal was sent to a node other than the intended destination node due to node identifier conflict. Also, the access terminal may identify the conflict based on the signals it receives from neighboring access points that indicate the identifiers used by these access points.

[0069] As represented by blocks 506 and 508, if no conflict is detected, the access terminal may use the first node identifier to establish communication with the destination node.

[0070] As represented by block 510, if a conflict is detected, the access terminal may use the second node identifier to establish communication with the destination node.

[0071] Furthermore, as represented by block 512, the access terminal may be configured to use the second node identifier to establish communication with the destination node. For example, the access terminal may be configured in this way after the access terminal detects a conflict. Alternatively, as discussed herein, the access terminal may send the second node identifier by default.

[0072] FIG. 6 relates in some aspects to reserving a subset of a node identifier space (e.g., PCID spaces) for non-macro nodes to simplify conflict resolution. In this way, the node that receives the identifier from the subset can easily determine that a conflict is possible or probable.

some

In implementations, the subset includes a set of designated values ​​that is associated with access points that are designated as not being conflict free. In some implementations, the subset includes a set of designated values ​​that is associated with a closed subscriber group (e.g., as discussed below). In some implementations, the subset includes a set of designated values ​​that is associated with access points of at least one designated type (e.g. node type). Such a designated type may relate, for example, to one or more of: transmission power, coverage area, or relay performance.

[0073] As represented by block 602, the access terminal (e.g., access terminal 102) receives the list of node identifiers . This list may include, for example, the subset of node identifiers discussed above. In some implementations, this list may be received from a serving access point (e.g., access point 104) that announces the list. In some implementations, the target access point or some other access points (e.g. by means of information on the list of neighbors) may announce an indication that the second type of identifier (e.g. GCI) is to be used when accessing the target access point. In some implementations, this list may be received from a configuration manager (e.g., network node 112), which tracks the reserved set of nodes to which an identifier from the list is assigned.

[0074] As represented by block 604, the access terminal determines the first identifier to communicate with the target access point. For example, as discussed herein, such an identifier may be received using a pilot signal or some other suitable signal.

[0075] As represented by block 606, the access terminal may determine (e.g., independently) whether to use a second identifier (e.g., GCI) to establish communication with

53 / 59P31502EN00 access point. In some aspects, this determination may be based on the first identifier (e.g., by determining the type of the first identifier). For example, if the identifier received in block 604 is on the list received in block 602, the access terminal may obtain a second identifier. Here, obtaining the second identifier may include monitoring other signals (from the target access point) that contain the second identifier. As an example, the destination access point may broadcast the second identifier at intervals that are less frequent than the intervals for which the destination access point broadcasts the first identifier.

[0076] As represented by block 608, the access terminal may transmit a message including the second identifier to establish communication with the target access point. This message can take different forms in different scenarios. For example, the message may include a signal for measuring the signal strength, a radio resource report or a switching request. In a typical implementation, an access terminal (e.g. access terminal 102) contains the associated PCID and GCI values ​​in the measurement report that the access terminal sends to its serving access point (e.g., access point 104). In addition, as described below in connection with FIG. 7, under certain circumstances, the access terminal may send this information to the destination access point.

[0077] As represented by block 610, after receiving this information, the serving access point may initiate a handover procedure using the GCI value. Thus, the serving access point will set the resources in the target cell and send a switch command to the access terminal.

[0078] FIG. 7 relates in some aspects to selecting an identifier to be provided to a destination access point, wherein the identifier is associated with

53 / 59P31502EN00 source access point. For example, the access terminal may use the GCI of the source access point in cases where the access terminal accesses the target access point directly without prior switching preparation. In this case, the access terminal may include the GCI of the source access point while accessing the target access point. This enables the target access point to resolve any conflict regarding the identification of the source access point. Destination access points can then download the context for the access terminal from the appropriate source access point, and complete the switch. These operations are described in blocks 702 - 706 in FIG. 7.

[0079] As represented by block 702, the access terminal selects identifiers (e.g., identifier e.g.

GCI) set the first identifier such as PCID with the target In some second identifier such as GCI) associated with the access point (e.g. access point 110 aspects, selection of the second identifier may be based on whether the first identifier is on the received list of identifiers (e.g. designated as conflict-free, based on the access point node type, etc.) in a similar manner as discussed previously in connection with FIGURE 6. As mentioned above, in some aspects the selection of the second identifier may be based on loss of communication with the source access point (e.g., access point 104).

[0080] As represented by block 704, the access terminal transmits the selected access point identifier during establishment to the target communication with the target access point. For example, the access terminal may include a GCI source access point in the connection request message.

[0081] As represented by block 706, the source access point may then use the selected identifier to establish communication with and / or receive configuration information from the source access point. In this way, the source access point may receive context information for the access terminal to complete handover.

[0082] FIG. 8 relates, in some aspects, to operations that an access point and / or an access terminal may perform in conjunction with detecting and resolving conflicts of node identifiers. In some aspects, these operations are complementary to the operations described above in conjunction with FIG. 5.

[0083] As represented by block 802, the access point (e.g., access point 104) determines whether multiple nodes use the same identifier when the identifier is of the first type (e.g., PCID). As mentioned above, the access point can detect such conflict based on measurement reports, neighborhood detection and received messages.

[0084] As represented by blocks 804 and 806, if no conflict is detected, the access point may continue normal operations. For example, the access point may determine whether to perform switching based on the first type identifier received by the measurement report.

[0085] As represented by block 808, if a conflict is detected, the access point may issue a request to obtain a second type identifier that is associated with the first type identifier subject to the conflict. For example, if the conflicting PCID was received via a measurement report from an access terminal (e.g., access terminal 102), the access point may send a request to the access terminal to obtain the GCI associated with the PCID. The access terminal may then acquire GCI, for example, as discussed herein.

[0086] As represented by block 810, the access point may then receive a response from the access terminal that contains the GCI. Because the conflict will now be resolved (e.g., at the access point), at block 812, a handover operation may be initiated (e.g., using the access point) using the received GCI.

[0087] FIG. 9A and 9B relate in some aspects to the use of a threshold to induce the acquisition of a unique identifier (e.g. GCI). In some cases, the access terminal may independently determine when to obtain the unique identifier; that is, without being instructed to do so by another node (e.g. access point).

[0088] As represented by block 902, the access terminal may receive a defined set of identifiers of the first type (e.g., the list of node identifiers described above). In some implementations, this information may be defined by and / or provided by a serving access point (e.g., by identifier controller 324) or some other node. For example, the serving access point may identify all of the PCIDs that are or may be in conflict, and provide a list of those IDs to the access terminal.

[0089] As represented by block 904, the access terminal may also receive a threshold value associated with the defined set of identifiers. For example, this threshold value may determine a signal strength threshold for the received signal that triggers GCI acquisition by the access terminal. In some implementations, this threshold value may be defined by and / or provided by a serving access point (e.g. by threshold controller 334) or some other node. For example, this threshold value may be defined to be lower (e.g., by a few dB) than the threshold value of the received signal strength u that triggers the switching operation. In some

In implementations, the threshold value may be specified as a relative offset relative to the signal strength of the target access point, or as an absolute threshold value for the carrier to interference ratio ("C / I") value from the target access point.

[0090] As represented by block 906, at some point in time, the access terminal will receive a signal that is associated with an identifier of the first type. As represented by block 908, the access terminal (e.g., comparator 330) may determine if the received identifier is in the list of identifiers. In addition, an access terminal (e.g. a signal processor 332 that may be implemented in or operate in conjunction with the receiver 308) determines whether the received signal strength for the signal received by block 906 is greater than equal to the threshold value.

[0091] As represented by blocks 910 and 912, if the criteria of block 908 are not met, the access terminal may continue to monitor signals from neighboring access points.

[0092] As represented by block 914, if the criteria of block 908 are met, the access terminal acquires a second type identifier (e.g., GCI) which is associated with the identifier received in block 906. As discussed earlier, this may involve monitoring the broadcast signal. with specific periodicity.

[0093] As represented by block 916, the access terminal (e.g., report generator 328) sends a message to the access point containing the identifier of blocks 906 and 910 and the strength of the received related signal (e.g., the signal received at block 906). This message can be sent as soon as a unique identifier has been obtained in block 910 or at another time. In some implementations, this information is sent in a measurement report. For example, this report can be obtained in a signal for

It is sent when the received signal strength for the received signal (e.g. from the target access point) exceeds the switching threshold.

[0094] As represented by block 918, since any conflict will now be resolved, the access point (e.g., switching controller 326) determines whether to initiate the switching operation based on the identifier and received signal strength provided in this message. As discussed herein, if a switching operation is indicated, the access point will use the unique identifier to prepare the target access point and send the switch command to the access terminal.

[0095] In some aspects, the diagram of FIG. 9 may be beneficial in highly mobile environments. For example, this scheme may provide faster handover because the GCI can be read before the signal strength of the target access point becomes strong enough for the handoff request.

[0096] FIG. 10A and 10B relate in some aspects to the scheme in which the access terminal reports the receipt of a signal that has exceeded a threshold (e.g., GCI threshold) to the access point. In this case, the access point may determine if conflict is possible and, if so, instruct the access terminal to obtain a unique identifier (e.g., GCI). Here, the operations of blocks 1002-1012 may be similar to the operations of blocks 902-912, respectively.

[0097] However, if the criteria are met at block 1010, at block 1014, the access terminal sends a message to the access point that includes the identifier acquired at block 1006 and the received signal strength for the associated signal. This message can be sent as soon as the identifier is obtained in block 1006 or at some other time. In some implementations, this information is sent in a measurement report.

[0098] As represented by block 1016, the access point determines if a conflict is likely based on the information received. For example, this determination may be based on whether multiple nodes use the same identifier. In addition, this determination may optionally be based on the received signal strength of any detected signals that include this identifier.

[0099] As represented by blocks 1018 and 1020, if no conflict is detected, the access point may continue normal operations. For example, the access point may determine whether to perform switching based on the first type identifier received by the measurement report.

[0100] As represented by block 1022, if a conflict is detected, the access point sends a message to the access terminal that requested the access terminal to acquire a unique identifier (e.g., CGI) associated with the conflicting identifier. As represented by block 1024, the access terminal may then acquire an identifier as discussed herein and send the identifier to an access point (e.g., using a measurement report).

[0101] As represented by blocks 1026 and 1028, the access point thus resolves the conflict and determines whether switching should be initiated based on the unique identifier and received signal strength (e.g., as discussed herein).

[0102] FIG. 11 relates in some aspects to collision detection (e.g., independent detection) by an access terminal. In particular, this scheme applies to an access terminal that provides a measurement report with collision information.

[0103] As represented by block 1102, the access terminal detects collision for a given identifier of the first type. For example, based on monitored pilot signals or other appropriate signals, the access terminal may determine that

Many access points use the same PCID as discussed herein.

[0104] As represented by block 1104, the access terminal may optionally acquire a second type identifier (e.g., GCI) associated with the identifier for which the collision was indicated. Again, this operation can be performed as discussed earlier.

[0105] As represented by block 1106, the access terminal sends a measurement report that includes a plurality of entries for the identifier for which a collision was indicated. For example, if two access terminals use a PCID value of 12, the measurement report may contain two separate entries corresponding to a PCID value of 12. In addition, the measurement report may optionally contain a unique identifier (e.g., GCI) associated with each of these entries.

[0106] FIG. 12 relates in some aspects to independent collision detection by an access terminal. In particular, this scheme applies to an access terminal that sends a measurement report if it detects a collision.

[0107] As represented by block 1202, the access terminal detects collision for a given identifier of the first type. As above, the access terminal may determine that multiple access points use the same PCID based on monitored pilot signals or other appropriate signals as discussed herein.

[0108] In some aspects, collision detection may be indicated based on whether at least two nodes are currently using the same identifier or have recently used the same identifier. For example, a collision may be indicated if the access terminal is currently receiving synchronization or pilot signals from multiple access points that use the same PCID. In addition, a collision may be indicated if the access terminal has received synchronization or pilot signals from multiple access points at a specific

53 / 59P31502EN00 a period of time (e.g. last 10 seconds). Under certain conditions, this period of time can be set to zero (e.g. for a fast-moving access terminal). Also, a collision may be indicated if the access terminal has received synchronization or pilot signals from multiple access points over a period of time associated with a defined number of handoffs (e.g., the last four handoffs). This second scheme may advantageously allow slow moving terminals to send reports to cover the desired geographical area. In other words, this scheme allows the detection of duplicate node identifiers in a wider geographical area.

[0109] As represented by block 1204, the access terminal may optionally acquire a second type identifier (e.g., GCI) associated with the identifier for which a collision was indicated. Again, this operation can be performed as discussed earlier.

[0110] As represented by block 1206, the access terminal sends a measurement report if a collision is detected in block 1202. In addition, the measurement report may optionally contain a unique identifier (e.g., GCI) associated with each of these entries.

[0111] FIG. 13 relates in some aspects to an access terminal that provides an on-demand collision report. As represented by block 1302, the access terminal receives a request for a collision report. For example, the network may periodically request the access terminal to send a measurement report with collision information. This request may specify one or more identifiers (e.g. PCID) for which collision information is requested. This identifier may be the identifier of the requesting node (e.g., serving access point). Alternatively, this request may include a wildcard identifier, wherein the access terminal is requested to report all detected collisions. How

With no response, the number of operations from is represented by block 1304, the access terminal monitors signals from neighboring access points and detects collisions, if applicable (block 1306). As represented by block 1308, the access terminal sends a collision report if a collision is detected in block 1306. In the event that the access terminal does not have any collision information, the access terminal may respond by "no event" message or may not deliver. It should be noted that one or more of FIG. 11-13 can be combined in various ways in different implementations.

[0112] As mentioned above, the information contained herein can be implemented in a network that uses macro access points and femto nodes. FIG. 14 and 15 illustrate examples of how access points can be used in such a network. FIG. 14 illustrates, in a simplified manner, how cells 1402 (e.g., macro cells 1402A-1402G) of the wireless communication system 1400 can be served by their corresponding access points 1404 (e.g., access points 1404A-1404G). Here, the macro cells 1402 may correspond to the macro coverage areas 204 of FIG. 2. As shown in FIG. 14, access terminals 1406 (e.g., access terminals 1406A 1406L) may be dispersed at various locations in the system over time. Each access terminal 1406 may communicate with one or more access points 1404 on the forward link ("FL") and / or reverse link ("RL) at any given time, depending on, for example, whether the terminal Access 1406 is active and is soft-switching. By using this cellular scheme, the 1400 wireless communication system can provide a service in a large geographical area. For example, each of the 1402A - 1402G macro cells may cover several blocks in neighborhood or several square miles in a rural environment.

[0113] FIG. 15 illustrates an example of how one or more femto nodes may be deployed within a network environment (e.g., a 1400 system). In system 1500 of FIG. 15, many femto nodes 1510 (e.g., femto nodes 1510A and 1510B) are installed in a network environment with a relatively small coverage area (e.g., in one or more user apartments 1530). Each femto node 1510 can be coupled to wide area network 1540 (e.g. Internet) and a 1550 mobile operator core network using a DSL router, cable modem, wireless connection, or other means of communication (not shown).

[0114] The femto owner of the node 1510 may subscribe to a mobile service, such as, for example, a 3G mobile service offered by the mobile operator's core network 1550. In addition, the access terminal 1520 may be capable of operating in both macro environments and network environments with a smaller coverage area (e.g., apartment). In other words, depending on the current location of the access terminal 1520, the access terminal 1520 may be served by an access point 1560 macro cell associated with the mobile operator's core network 1550 or by any of the set of femto nodes 1510 (e.g. femto nodes 1510A and 1510B, which are are placed inside the respective user's 1530 apartment). For example, when the subscriber is out of his home, the subscriber may be served by a standard macro access point (e.g. access point 1560), and when the subscriber is near or inside his home, the subscriber may be served by a femto node (e.g., node 1510A). In this case, the femto node 1510 may be backward compatible with legacy access terminals 1520.

[0115] Femto node 1510 may be operating on a single frequency, or in an alternative embodiment, on multiple frequencies. Depending on the particular configuration, a single frequency or one or more of many

The frequency may overlap one or more frequencies used by the macro access point (e.g., access point 1560).

[0116] In some aspects, the access terminal above 1520 may be configured to connect to a preferred femto node (e.g., home femto access terminal node 1520) as long as such connectivity is possible. For example, whenever the access terminal 1520A is located inside the user's apartment 1530, it may be desirable for the access terminal 1520A to communicate only with the home femto node 1510A or 1510B.

[0117] In some aspects, if the access terminal 1520 operates within the macro cellular network 1550 but is not in the most favorable network (e.g. as specified in the preferred roaming list), the access terminal 1520 may continue to search for the most preferred network (e.g. preferred femto node 1510) using the Better System Reselection ("BSR") system, which may include periodic scanning of available systems to determine if better systems are currently available, and subsequent attempts to establish association with such preferred systems. By using the acquisition entry, the access terminal 1520 may limit the search to a specific band and channel. For example, the search for the most preferred system may be repeated periodically. After detecting the preferred femto node 1510, access terminal 1520 selects the femto node 1510 to be located within its coverage area.

[0118] Femto knot may be limited in some aspects. For example, a given femto node can only provide specific services to specific access terminals. In implementations with so-called restricted (or closed) binding, a given access terminal can only be served by a mobile macro cellular network and a defined set of femto nodes (e.g. femto nodes 1510 that are located

53 / 59P31502EN00 inside the respective user apartment 1530). In some implementations, a node may be restricted such that it does not provide, for at least one node, at least one of: signaling, data access, registration, paging or service.

[0119] In some aspects, a restricted Femto node (which may also be referred to as a Closed Subscriber Home NodeB) is the one that provides services to the restricted secure set of access terminals. This set can be temporarily or permanently extended if necessary. In some aspects, a closed subscriber group ("CSG") can be defined as a set of access points (e.g. femto nodes) that share a common access terminal access control list. The channel on which all femto nodes (or all restricted femto nodes) operate in a region may be referred to as a femto channel.

[0120] Different dependencies may therefore exist between a given femto node and a given access terminal. For example, from the perspective of an access terminal, an open femto node may refer to a femto node with unlimited association (e.g., a femto node allows access to any access terminal). A restricted femto node may refer to a femto node that is limited in some way (e.g., limited in terms of binding and / or registration). A home femto node may refer to a femto node in which the access terminal is authorized to access or operate on it (e.g., permanent access is provided for a defined set of one or more access terminals). A guest femto node may refer to a femto node that the access terminal is temporarily authorized to access or operate on. A foreign femto node may refer to a femto node that the access terminal is not authorized to

53 / 59P31502EN00 access or operation on it, except in the event of an emergency (e.g. call 911).

[0121] From the perspective of the restricted femto node, the home access terminal may refer to an access terminal that is authorized to access the restricted femto node (e.g., the access terminal has permanent access to the femto node). A guest access terminal may refer to an access terminal with temporary access to a restricted femto node (e.g., limitation based on time limit, usage time, bytes, connection counter or any other criterion or criteria). A foreign access terminal may relate to an access terminal that does not have permission to access a restricted femto node, except for possible emergencies, such as a 911 connection (e.g., an access terminal that has no credentials or registration permits) in a restricted femto node).

[0122] For convenience, the present invention describes various functionalities in the context of a femto node. Note, however, that a pico node may provide the same or similar functionality for a larger coverage area. For example, a pico node may be limited, a home pico node may be defined for a given access terminal, and so on.

[0123] The information contained herein may be implemented in various types of communication devices. In some aspects, the information contained herein can be implemented in wireless devices that can be arranged with multi-access communication that can support communication for multiple wireless access terminals. In this case, each terminal may communicate with one or more access points by means of forward and reverse link transmission. The forward link (or downlink) refers to the communication link from access points to the terminals, and the reverse link (or uplink) applies to the link in the system simultaneously

53 / 59P31502EN00 from terminals to access points. This communication link can be established by means of one input system - one output, multiple input system - multiple outputs ("MIMO"), or other type of system.

[0124] For illustrative purposes, FIG. 16 describes examples of communication components that can be used in a wireless device in the context of a MIMO-based system 800. The 1600 system uses multiple (NT) transmit antennas and multiple (NR) receive antennas for data transmission. The MIMO channel formed by NT transmission antennas and NR receiving antennas can be spread over NS independent channels, which also refer to spatial channels, where N_S <min {NT, NR}. Each of these NS independent channels corresponds to a dimension. The MIMO system can provide increased performance (e.g., greater throughput and / or better reliability) if additional dimensions created by multiple transmission and receiving antennas are used.

[0125] System 1600 may support time division duplex ("TDD") and frequency division duplex ("FDD"). In the TDD system, transmissions on the forward and reverse links occur in the same frequency region so that reciprocity allows the uplink channel to be estimated from the reverse link channel. This allows the access point to extract the beam-shaping gain on the forward link when multiple antennas are available at the access point.

[0126] System 1600 includes a wireless device 1610 (e.g., access point) and wireless device 1650 (e.g., access terminal). In device 1610, traffic data for a number of data streams are provided from a data source 1612 to a transmission data processor 1614 ("TX").

[0127] In some aspects, each data stream is transmitted via respective transmission antennas. TX data processor 1614 formats, encodes and interleaves data related to

53 / 59P31502EN00 traffic for each data stream based on a specific coding scheme selected for that data stream to provide coded data.

[0128] The encoded data for each data stream can be multiplexed using pilot data using OFDM techniques. Pilot data is usually a known data pattern that is processed in a known manner and can be used in the receiver system to estimate the u channel response. Multiplexed pilot data and encoded data for each data stream are then modulated (i.e. mapped to symbols) based on a specific modulation scheme (e.g. BPSK, QSPK, M-PSK or M-QAM) selected for the data stream to provide modulation symbols. Bit rate, coding and modulation for each data stream can be determined by instructions executed by the 1630 processor. The data memory 1632 can store program code, data and other information used by the 1630 processor or other components of the 1610 device.

[0129] Modulation symbols for all data streams are then provided to the TX MIMO 1620 processor, which can then process modulation symbols (e.g., OFDM). The TX MIMO 1620 processor then provides NT modulation symbol streams to NT transceivers ("XCVR") from 1622A to 1622T. In some aspects, the TX MIMO 1620 processor applies beam-forming weights relative to data stream symbols and relative to the antenna from which the symbol is transmitted.

[0130] Each transceiver 1622 receives and processes a corresponding symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters and converts the frequency to a higher frequency) analog signals to provide a modulated signal suitable for transmission via using the MIMO channel. NT modulated signals from transceivers from 1622A to

53 / 59P31502PL00

The 1622T is then transmitted from NT antennas from 1624A to 1624T, respectively.

[0131] In the device 1650, the transmitted modulation symbols are received by NR antennas from 1652A to 1652R, and the received signals from each antenna 1652 are provided to the respective transceiver ("XCVR") from 1654A to 1654R. Each 1654 transceiver is conditioned (e.g. filters, amplifies, and converts the frequency to a lower) corresponding received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide the appropriate "received" symbol stream.

[0132] The received data processor ("RX") 1660 then receives and processes the NR received symbol streams from the NR transceivers 1654 based on the appropriate processing technique of the specific receiver to provide NT "detected" symbol streams. The RX data processor 1660 then demodulates, deinterlaces and decodes each detected symbol stream to recover traffic data for the data stream. The processing of the RX data processor 1660 is complementary to the processing performed by the TX MIMO processor 1620 and the TX data processor 1614 in the device 1610.

[0133] The processor 1670 periodically determines which precoding matrix to use (discussed below). The processor 1670 formulates a uplink message containing a part with a matrix index and a part with a degree value. The 1672 data memory can store program code, data, and other information used by the 1670 processor or other 1650 device components.

[0134] The reverse link message may include various types of information regarding the communication link and / or the received data stream. The uplink message is then processed by TX data processor 1638, which also receives traffic data for a number

The data streams from the data source 1636, modulated by the 1680 modulator, conditioned by the transceivers 1654A to 1654R and transmitted back to the device 1610.

[0135] In device 1610, modulated signals from device 1650 are received by antennas 1624, conditioned by transceivers 1622, demodulated by a demodulator ("DEMOD") 1640 and processed by RX data processor 1642 to extract the uplink message transmitted by the device 1650. The 1630 processor then determines which precoding matrix to use to determine the beam-forming weights, and then processes the extracted message.

[0136] FIG. 16 also shows that communication components may include one or more components that perform conflict control operations, as already explained. For example, the conflict control component 1690 may cooperate with the processor 1630 and / or other component of the device 1610 to send / receive signals from / to another device (e.g. device 1650) as already explained herein. Similarly, the conflict control component 1692 may cooperate with the 1670 processor and / or other components of the device 1650 to send / receive signals from / to another device (e.g., device 1610). It should be noted that for each device 1610 and 1650, the functionality of two or more of the components described may be provided by a single component. For example, a single processing component may provide functionality of the conflict control component 1690 and processor 1630, and a single processing component may provide functionality of the conflict control component 1692 and processor 1670.

[0137] The information contained herein may be incorporated into many different types of communication systems and / or system components. In some aspects, the information contained herein may be

53 / 59P31502EN00 used in a communication support system sharing available with multiple access with many use of system resources

<td>capable</td><td>down</td>

<td>kami</td><td>by</td>

<td>(Eg.</td><td>by</td>

<td>band,</td><td>power</td>

<td>further)</td><td>. On</td>

transmitting, coding, interleaving and this example, the information contained herein can be used in any technology or combination of technologies: systems <a href="http://megaslownik.pl/slownik/polsko_angielski/,wielodost%C4%99p+z+dzieleniem+kod%C3%B3w">multiple access</a><a href="http://megaslownik.pl/slownik/polsko_angielski/,wielodost%C4%99p+z+dzieleniem+kod%C3%B3w">with code breakdown </a>("CDMA"), multi-carrier CDMA ("MCCDMA"), broadband CDMA ("W-CDMA"), HighSpeed ​​Packet Access systems ("HSPA", "HSPA +"), time division multiple access systems ("TDMA" ), pu multi frequency access systems ("FDMA"), single carrier FDMA systems ("SC-FDMA"), orthogonal frequency division multiple access systems ("OFDMA"), or other multi-access techniques. A wireless communication system using the information provided herein may be designed to implement one or more standards such as IS-95, cdma2000, IS856, W-CDMA, TDSCDMA and other standards. The CDMA network may implement radio technology such as Universal Terrestrial Radio Access ("UTRA)", cdma2000, or any other technology. UTRA includes W-CDMA and Low Chip Rate ("LCR"). Cdma2000 technology includes IS-2000, IS-95 and IS856 standards. The TDMA network can implement radio technology such as

Global Mobile Communication System ("GSM"). The OFDMA network can implement radio technology such as enhanced UTRA ("EUTRA"

IEEE

02.11, IEEE 802.16, IEEE 802.20, Flash-OFDM®, etc. UTRA, E-UTRA, and GSM Mobile Telephony ("UMTS") implemented in the ("LTE") system are part of the Global System

The information contained herein may be 3GPP Long Term Evolution 3GPP Ultra-Mobile Broadband ("UMB") and other types of systems. LTE is an UMTS edition that uses EUTRA. Although specific aspects of the invention may be described using 3GPP terminology, it will be understood that the information herein may be used for terminology

53 / 59P31502PL00 3GPP technology (Re199, Re15, Re16, Re17) as well as 3GPP2 technology (IxRTT, 1xEV-DO RelO, RevA, RevB) and other technologies.

[0138] Solutions contained herein may be implemented in (e.g., implemented internally or implemented by) various devices (e.g., nodes). In some aspects, a node (e.g., wireless node) implemented in accordance with the information contained herein may include an access point or access terminal.

[0139] For example, the access terminal may include, be implemented as or known as user equipment, subscriber station, subscriber unit, mobile station, mobile phone, mobile node, remote station, remote terminal, user terminal, user agent or any other implementations mobile access terminal, cordless telephone, session initiation ("SIP"), local station ("WLL"), personal digital assistant ("PDA"), a portable device capable of being wirelessly connected, or some other appropriate processing device connected to the wireless modem. Accordingly, one or more aspects discussed herein may be implemented in a telephone (e.g., mobile phone or smartphone), computer (e.g., communication device, e.g., personal digital assistant) for entertainment (e.g. device or satellite radio), positioning system, or any other that is configured to communicate using a wireless medium.

[0140] The access point may include, be implemented as or known as a NodeB node, eNodeB, user radio network controller, terminology device. In some it may contain a telephone with a telephone with a wireless loop (portable device (music device, laptop device), portable computing, dedicated video device, global device,

53 / 59P31502EN00 ("RNC"), base station ("BS"), radio base station ("RBS"), base station controller ("BSC"), base transceiver station ("BTS"), transceiver function (" TF "), radio transceiver, radio router, basic service set (" BSS "), extended service set (" ESS ") or other similar terminology.

[0141] In some aspects, the node (e.g., access point) may include an access node for a communication system. Such an access node may provide, for example, connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) over a wired or wireless communication link to the network. In this regard, the access node may allow another node (e.g., access terminal) to access the network or other functionality. In addition, it should be noted that one or both nodes may be portable or, in some cases, relatively non-portable.

[0142] Also, it should be noted that a wireless node may be capable of transmitting and / or receiving information in a non-wireless manner (e.g., via a wired connection). Thus, the receiver and transmitter as discussed herein may include appropriate communication interface components (e.g., electrical or optical interface components) for communication via a non-wireless medium.

[0143] A wireless node may communicate via one or more wireless communication links that are based on or otherwise support any suitable wireless communication technology. For example, in some aspects a wireless node may bind to a network. In some aspects, the network may include a local area network or wide area network. A wireless device may support or otherwise use one or more of many different wireless communication technologies, protocols, or

Standards such as those discussed here (e.g., CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, and so on). Similarly, a wireless node may support or otherwise utilize one or more different suitable modulation or multiplexing schemes. The wireless node may therefore contain appropriate components (e.g. radio interface) for establishing and communicating via 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, which may include various components (e.g., signal generators and signal processors) that facilitate communication via a wireless medium.

[0144] The components described herein can be implemented in various ways. Referring to FIG. 17-21, devices 1700, 1800, 1900, 2000, and 2100 are represented as a series of interdependent functional blocks. In some aspects, the functionality of these blocks can be implemented as a processing system comprising one or more processor components. In some aspects, the functionality of these blocks can be implemented using, for example, at least a portion of one or more integrated circuits (e.g., ASICs). As discussed herein, an integrated circuit may include a processor, software, other related components, or any combination thereof. The functionality of these blocks can also be implemented in any other way, as already explained. In some aspects, one or more of the dashed block lines indicated in FIG. 17 - 21 is optional.

[0145] The devices 1700, 1800, 1900, 2000, and 2100 may include one or more modules that can perform one or more of the functions described above with respect to the various figures. For example, measures

53 / 59P31502PL00

1702 for receiving, means 1806 for receiving a message, means 1906 for receiving a request, means 2012 for receiving a signal, or receiving means 2108 may correspond, for example, to a receiver and / or a communication controller as discussed herein. Means 1704 for determining identification or means 1902 for determining an identical identifier may correspond, for example, to a conflict detector as discussed herein. Means 1706 for sending the message, means 1802 for sending the identifier, means 1808 defining the identifier, means 1908 for determining the identifier, means 2004 for determining the type, means 2006 for determining the second identifier, means 2104 for selecting the identifier may correspond, for example, to the identifier controller, as discussed in this description. Means 1706 for sending or means 2008 for transmission may correspond, for example, to a transmitter and / or a communication controller, as discussed herein. Means 1804 for sending the threshold or means 1810 defining the threshold 1810 may correspond, for example, to the threshold controller as discussed herein. Means 1904 for sending a report may correspond, for example, to a report generator as discussed herein. Means 2002 for determining the first identifier, means 2010 for using the identifier, communication means 2102, or transmission means 2106 may correspond, for example, to a communication controller as discussed herein. The means 2014 for determining the signal strength may correspond, for example, to the signal processor and / or the receiver as discussed herein.

[0146] Skilled artisans will understand that information and signals can be utilized by any of a variety of techniques. For example, data, instructions, commands, information, signals, bits, symbols and chips that

The designed electronic implementation may be referred to in its entirety in the above description, it may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0147] Skilled artisans will further note that any of various exemplary logic blocks, modules, processors, means, circuits and algorithm steps described in connection with the aspects disclosed herein may be implemented as hardware (e.g. digital implementation, analogue or a combination thereof, which may be using source coding or any other technique), various program forms or project code including instructions (which may be referred to herein as, for convenience, as "software" or "software module") or their combination. To clearly illustrate this interchangeability of hardware and software, various examples of components, blocks, modules, circuits and steps have been described above essentially in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design restrictions imposed on the entire system. Skilled artisans may implement desired functionality in a variety of ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

[0148] Various exemplary logic blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented internally or implemented by an integrated circuit ("IC"), integrated circuit IC, access terminal or access point.

may include a general purpose processor, digital signal processor (DSP), special purpose integrated circuit (ASIC), directly programmable gate matrix (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete

53 / 59P31502EN00 hardware components, electrical components, optical components, mechanical components or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that are contained within an IC, outside an IC, or both. The general purpose processor may be a microprocessor, but alternatively the processor may be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented as a combination of computing devices, e.g., a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration.

The functions described in this document may be by means of hardware, software, firmware or a combination thereof. If software is implemented, software implemented functions may be stored in or transmitted as one or more instructions or code on a computer readable medium. The computer readable medium includes both a computer storage medium and communication media including any medium that facilitates the transfer of a computer program from one place to another. The storage media may be any available media that a computer can access. For example, but without limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical memory disk, magnetic memory disk or other magnetic memory devices, or any other suitable medium that may be used for carrying and store program code in the form of instructions or data structures, and which the computer can access. Also, any connection is properly referred to as a computer readable medium. For example, if the software is transmitted from a website

53 / 59P31502EN00 internet, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio waves and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio waves and microwaves are included in the definition of medium. The disc and disc, as used herein, include a compact disc (CD), laser disc, optical disc, universal video disc (DVD), floppy disk and blu-ray disc, with the discs typically playing magnetic data and the discs playing optically using laser data. Combinations of the above examples should also be included within the scope of the computer readable medium. In summary, it should be noted that the computer readable medium can be implemented in any suitable product in the form of a computer program.

QUALCOMM Incorporated Proxy:

53 / 59P31502PL00