WO2008082985A1 - Assigning code space to portable base stations - Google Patents
Assigning code space to portable base stations Download PDFInfo
- Publication number
- WO2008082985A1 WO2008082985A1 PCT/US2007/088112 US2007088112W WO2008082985A1 WO 2008082985 A1 WO2008082985 A1 WO 2008082985A1 US 2007088112 W US2007088112 W US 2007088112W WO 2008082985 A1 WO2008082985 A1 WO 2008082985A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- base station
- portable base
- code space
- offset
- assignment
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/14—Spectrum sharing arrangements between different networks
- H04W16/16—Spectrum sharing arrangements between different networks for PBS [Private Base Station] arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
Definitions
- Cellular communication systems include antenna towers erected in fixed locations to provide wireless coverage to devices such as cellular phones, personal digital assistants (PDAs) and computer systems (each of which is referred to as an Access Terminal or AT).
- PDAs personal digital assistants
- AT Access Terminal
- an AT may be located within the coverage area of multiple towers.
- each tower transmits a unique identification signal that includes information assigned to the tower. This information may be a sequence of pseudorandom numbers (PN) that are transmitted in a repetitive manner.
- PN pseudorandom numbers
- the starting elements may be identified by a number that represents the offset from the first element in the sequence to the starting element (assigned to the tower).
- RF radio frequency
- a portable base station requests assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The portable base station also transmits an identification signal using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
- the request from the portable base station may include data that represents the location of the portable base station.
- the code space may include a sequence of pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips. Requesting the assignment may be initiated by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station.
- the code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
- CDMA Code Division Multiple Access
- UMTS Universal Mobile Telecommunication System
- a system in some aspects of the invention, includes a portable base station that requests assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station.
- the portable base station is also capable of transmitting an identification signal by using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
- the portable base station may provide the functionality of a radio node, a radio node controller, an access gateway, and other similar components.
- the assignment may be based upon the distance between the portable base station and another base station.
- the remotely located control station may include a server for assigning the code space portions.
- the assignment request may include data that represents the location of the portable base station.
- the code space may include a sequence of pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips.
- Requesting the assignment may be initiated by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station.
- the code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
- CDMA Code Division Multiple Access
- UMTS Universal Mobile Telecommunication System
- a medium bears instructions to cause a portable base station to request assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The instructions also cause the portable base station to transmit an identification signal using the assigned code space portion such that the identification signal uniquely identifies the portable base station to one or more access terminals.
- the request from the portable base station may include data that represents the location of the portable base station.
- the code space may include a sequence of pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips. Requesting the assignment may be initiated by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station.
- the code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
- CDMA Code Division Multiple Access
- UMTS Universal Mobile Telecommunication System
- code space e.g., offsets of a pseudorandom number sequence, etc.
- the portable stations may be deployed and made operational in a relatively short time period and in a cost effective manner (compared to the time-consuming, deliberate and often expensive exercise of manual code space assignment).
- code space assignments may be tracked by the control station along with the location of the portable base stations.
- predefined events may initiate assignment requests, thereby, providing more controllability in allocating the code space.
- FIG. 1 is a diagram of a telecommunication core network in communication with a fixed location base station and a portable base station.
- FIG. 2 is a diagram of a control station in communication with multiple portable base stations and a fixed location base station.
- FIG. 3 is a diagram of a PN sequence.
- FIG. 4 is a flow chart of operations executed by an Offset Assigner.
- FIG. 5 is a flow chart of other operations executed by an Offset Assigner.
- a radio access network (RAN) 100 includes a conventional antenna tower 102 that is erected at a fixed location and transmits and receives electromagnetic signals that are provided to or from a fixed location base station 104.
- One or more signaling techniques and standards may be implemented by the fixed location base station 104 to establish communication links (via the antenna tower 102) with one or more ATs such as a cellular telephone 106.
- ATs such as a cellular telephone 106.
- UMTS Universal Mobile Telecommunications System
- Standards associated with spread spectrum air interface protocols such as code division multiple access (CDMA), wideband (W- CDMA), etc. may also be implemented for multiple AT access.
- Other protocols supported may include the IxEV-DO protocol, which is an
- the fixed location base station 104 transmits a signal (via the antenna 102) that uses one or more spread spectrum techniques such as being modulated with a unique pseudorandom code.
- the identification signal may appear as noise, however, the signal may be extracted with a correlation process by an appropriate receiver aware of the pseudorandom sequence.
- orthogonal or non-orthogonal coding techniques may also be used to produce unique transmission signals. For example, different PN sequences (e.g., gold sequences) referred to as scrambling codes (for W-CDMA) may be implemented. Different types of information may also be transmitted to uniquely identify the base station 104.
- the fixed location base station 104 includes a radio node (RN) 108 that supports the wireless standards and protocols (e.g., CDMA, W-CDMA, UMTS, etc.) for communicating with the ATs.
- RN radio node
- the RN 108 includes a transceiver for receiving and transmitting electromagnetic signals.
- the RN 108 may also include one or more components (e.g., a modulator/demodulator (MODEM)) for modulating a transmission carrier signal to encode digital information for transmission or demodulating a received analog signal to decode transmitted digital information.
- MODEM modulator/demodulator
- the RN 108 is connected to a radio node controller (RNC) 110 that provides commands (and transmission signals) to the RN 108 and receives incoming signals from the RN 108.
- RNC radio node controller
- An access gateway 112 such as a packet data serving node (PDSN) is connected to the RNC 110 and may be implemented as a data server to direct data packets to appropriate delivery locations. Additionally the access gateway 112 provides an interface between networking functions and service levels defined by one or more standards such as the Open Systems Interconnect (OSI) protocol standard defined by the International Standards Organization (ISO), which is herein incorporated by reference.
- OSI Open Systems Interconnect
- ISO International Standards Organization
- the access gateway 112 provides an interface between the link layer (e.g., layer 2) functionality provided by the fixed location base station 104 and the routing layer (e.g., layer 3) functionality provided by a core network 114 that is connected to the fixed location base station.
- the core network 114 exchanges data and signals with other components included in the RAN 100.
- data may be sent to other base stations, conventional landline telephone systems (e.g., Plain Old Telephone Service (POTS) systems, etc.) or other similar delivery sites and sources.
- POTS Plain Old Telephone Service
- antenna towers such as antenna tower 102 are erected to remain fixed at one location. Prior to erecting the towers, the geographical layout of the towers is planned to provide wireless coverage. Additionally each tower is assigned a portion of a code space so that the antenna (and corresponding fixed location base station 104) may uniquely identify itself to the one or more ATs within the coverage area. Since ATs such as AT 106 communicate with base stations (e.g., CDMA, W- CDMA and UMTS base stations) on the equivalent frequencies, an AT needs to differentiate one fixed location base station from another. In order to identify each fixed location base station separately, each base station repeatedly transmits an identical pseudorandom number (PN) sequence of codes that are offset in time from the PN sequences being transmitted by the other base stations.
- PN pseudorandom number
- the PN offset is assigned to each fixed location base station respectively connected to an antenna erected at a fixed location.
- these offset assignments are determined prior to the antenna tower becoming operational and are static in the sense of not being adjusted once the tower is in operation.
- such a manual offset assignment process is often time- consuming and expensive.
- Different PN-sequences may also be transmitted to uniquely identify base stations.
- signals may be transmitted on different frequencies or share a similar frequency.
- the RAN 100 also includes a portable base station 116 that is in communication with the core network 114 and provides the functionality of the fixed location base station 104.
- the portable base station 116 includes an RN 118, an RNC 120 and an access gateway 122 (e.g., a PSDN).
- the portable base station 116 is connected to a portable antenna 124 that is capable of establishing links with one or more ATs, however, antenna characteristics (e.g., beam pattern, gain, etc.) of the portable antenna are typically selected for establishing links to ATs located relatively close to the portable base station.
- the design characteristics (e.g., component size, power consumption, etc.) of the RN 118, RNC 120 and the access gateway 122 may be selected for portability.
- the portable base station 116 may provide less wireless coverage area than the fixed location base station 104 (e.g., coverage to service a single residential home, a portion of a multiple residence building or other structure or location of similar size and area).
- the portable base station 116 may interfere with the operations of the fixed base station 104 or other relatively closely located base stations (e.g., other portable base stations, fixed location base stations).
- identification signals using near-by or equivalent code space e.g., PN offset, PN sequence, etc. may interfere with the identification signals transmitted by the portable base station 116.
- a RAN 200 includes three portable base stations 202, 204, 206 that are respectively located at and provide coverage to three separate locations
- the RAN 200 also includes a fixed base station 214 that is connected to an antenna tower 216 that also provides wireless coverage (e.g., larger coverage than the portable base stations).
- Each of the portable base stations 202, 204, 206 and the fixed base station 214 are connected to a core network 218 that is in communication with a control station 220 (e.g., remotely located from the locations 208, 210 and 212) that includes a server 222 or other type of computing device (e.g., a computing system) or multiple computing devices that may provide distributed processing.
- the server 222 is in communication with a storage device 224 (e.g., magnetic, magneto-optical disks, or optical disks, etc.) that stores files, data structures, applications and instructions for execution by the server, or other types of data.
- a storage device 224 e.g., magnetic, magneto-optical disks, or optical disks, etc.
- two or more of the portable base stations 202, 204, 206 may be closely located to each other (or to the fixed tower 216) and transmit identification signals on different or equivalent frequencies.
- an AT 226 may be unable to distinguish between the pair of portable base stations (or a portable base station and the fixed tower 216).
- locations 210 and 212 may be closely located (e.g., adjacent rooms, apartments, etc.) and the AT 226 may detect identification signals from both of the portable base stations 204 and 206.
- the PN offsets or PN sequences (used by the portable base stations 210 and 212) are similar (e.g., occupy nearby code space or equivalent code space), the AT 226 may be unable to distinguish between the identification signals.
- additional portable base stations may be moved into the area (e.g., placed in adjacent rooms or the same room) and may not be distinguishable by the AT 226.
- code space may be allocated in a cost effective and timely manner (as each station is deployed).
- dynamic allocation allows distinguishable identification signals to be transmitted (using different or equivalent frequencies) from closely located portable base stations, thereby reducing potential signal collisions.
- PN offsets widely separated in a PN sequence may be assigned to closely located portable base stations (or the fixed tower base station and a portable base station).
- the PN offset assignments may be adjusted to reduce potential identification signal collision. For example, by tracking the locations (e.g., Global Positioning System (GPS) coordinates) of the portable base stations and the fixed location base stations, a code space may be segmented and assigned for minimal interference among the base stations.
- the control station 220 via communication with the core network 218, dynamically allocates code space (e.g., one or more PN sequences) and assigns portions of the code space (e.g., PN offsets, PN sequences, etc.) to each of the portable base stations 202, 204, 206 (and optionally, the fixed location base station 214).
- code space e.g., one or more PN sequences
- portions of the code space e.g., PN offsets, PN sequences, etc.
- Location tracking, PN offset assignment storage, and other functions may also be provided by the control station 220.
- the server 222 executes operations for tracking the location of the base stations (e.g., portable base stations, fixed location base stations) and assigns appropriate PN offsets to the base stations based upon the location information and potentially other information (e.g., base station capabilities, performance, time of day, etc.).
- the server 222 stores the code space assignments along with other information (e.g., base station location information, base station capabilities, assignment confirmations, etc.) in the storage device 224.
- transmissions between the control station 220 and the base stations (fixed or portable) are encrypted to reduce the probability of interception or modification.
- the encryption technique(s) may block base station users from modifying information (e.g., PN offsets) included in the transmissions.
- PN offset (or PN sequence) assignment(s) may be initiated by the occurrence of a particular event which may or may not be predefined.
- a portable base station may request a PN offset upon becoming operational (e.g., powered up) and establishing communication with the core network 218.
- the request may be provided in one or more forms such as a signal, electronic message, file, data structure, or other similar form.
- a message 228 is sent by the portable base station 204 to the control station 220 via the core network 218 upon being powered up and establishing a communication link with the core network.
- the other portable base stations 202, 206 may request a PN offset (or other type of code space portion) upon becoming operational.
- events that initiate a PN offset request may include the occurrence of predefined time (e.g., midnight each evening), resetting the portable base station, user initiated, or other type of event.
- the request 228 may contain one or more types of information such as data that identifies the portable base station 204 (e.g., a unique alphanumerical identifier assigned to the base station by a manufacturer, etc.), the location of the portable base station (e.g., GPS coordinates), base stations capabilities (e.g., coverage area, transmission power, etc.), status information (e.g., number of established ATs links) and other types of information.
- GPS coordinates may be inserted into the message 228 from a GPS receiver (not shown) that is included in the portable base station 204.
- Location information may also be provided from an external source such as an external GPS receiver or other type of location determining device in communication with the portable base station 204.
- Data that represents a previously used PN offset (or other type of code space portion) may also be included in the message 228.
- the last PN offset assigned or a list of previously assigned PN offsets (e.g., all assignments, assignments over a period of time) may be provided in the request.
- These previously assigned PN offsets may be used by the server 222 for assigning the requested offset (e.g., assign a new PN offset, assign a previously used PN offset, etc.).
- preference may factor into some assignments as described in "Configuring Preferred User Zone Lists for Private Access Points for Wireless Networking", U.S. Patent Application Serial No. 11/640,503, filed on 15 December 2006, the entire contents of which are hereby incorporated by reference.
- Information such as location information may be provided to the portable base station 204 from a user interface (e.g., a keyboard) or a data conduit (e.g., communication port) from another device (e.g., a GPS receiver).
- Other included information may be used for security (e.g., a public key, etc.), data compression, or other types of functions.
- the control station 204 initiating a request, the control station
- a polling signal may be sent from the control station 220 to each of the base stations (portable and fixed location) at predefined intervals (e.g., daily, weekly, etc.).
- requests such as the request 228 may be produced and sent from the corresponding portable base station 204 to the control station 220.
- a portion of the base stations may be polled. For example, based stations located in a particular geographical region may be polled at one time and base stations located in another region may be polled at a different time.
- the server 222 may track mobile base stations that are more frequently assigned PN offsets (e.g., due to frequent movements). These base stations may be polled more frequently than base stations that have a relatively stationary history.
- an Offset Assigner 230 is executed by the server 222. Along with request processing, the Offset Assigner 230 identifies the appropriate PN offset (if any) that should be assigned and informs the base station of the assignment. For example, upon determining a PN offset assignment for the portable base station 204, a message 232 is sent from the control station 220 to the portable base station.
- Data 234 represents the PN offset that may be retrieved from the message 232 and stored in a memory (not shown) (e.g., random access memory (RAM), read-only memory (ROM), static RAM (SRAM), etc.) or a storage device (also not shown) included in the portable base station 204.
- the control station 220 may respectively provide PN offsets 236, 238 to the other portable base stations 202, 206.
- the fixed location base station 214 is typically assigned a PN offset based upon a planning procedure that is executed prior to the tower 216 becoming operational, in some scenarios the control station 220 may assign a PN offset 240 to the fixed location base station.
- the assigned PN offset 240 may be used by a MODEM, which is included in the RN portion of the fixed location base station 214, to produce an appropriate identification signal.
- the server 222 stores data that represents the offset assignments.
- data may be stored in the storage unit 224 that uniquely represents both the assigned offset and the base station to which it is assigned.
- One or more data types, data structures, storage techniques and methodologies may be implemented so that the assigned offsets may be efficiently stored and retrievable.
- One or more techniques and methodologies may be used by the Offset Assigner 230 to determine PN offset assignments. For example, by using location information included from the request messages, the Offset Assigner 230 may use the distance between the base stations in determining the PN offset assignments. The capabilities of the base stations may also be used in the determination. For example, the range that each base station is capable of establishing an AT link may be used to determine potential signal collision ranges among the base stations. These and other techniques and methodologies, known in the art of signal collision avoidance, individually or in combination, may be implemented by the Offset Assigner 230.
- a diagram 300 represents a sequence 302 of pseudorandom numbers that form one exemplary code space that may be allocated among portable base stations (and fixed location base stations).
- the PN sequence 302 includes binary numbers (e.g., a "0" or a "1") that occur substantially at random in the sequence.
- the PN sequence 302 may be generated by implementing one or more techniques, for example, a random number generator may produce the sequence.
- Each binary number is referred to as a chip and may be considered the basic building element from which the PN sequence is produced.
- the length of the PN sequence is referred to as a frame and is predefined with a relatively large number of chips. For example, this sequence may represent 32,768 chips, however, other exemplary sequences may include more or less chips.
- each portable base station may transmit the sequence as an identification signal within its coverage distance. To provide a continuous signal, the sequence is transmitted in a repetitive manner from each base station. Each portable base station transmits a unique identification signal to differentiate itself from other base stations. For example, each portable base station may initiate transmission of the sequence 302 starting from a different chip included in the sequence. Each starting chip may be identified by dividing the frame into a predefined number of segments. For example, the frame may be divided into segments with equivalent chip lengths (e.g., sixty-four chips). As such, the frame (with a length of 32,768 chips) is divided into 512 segments that each include 64 chips. Alternatively, segments lengths may not be equivalent and some may contain different number of chips.
- the first chip of each segment is identified as an offset.
- “Offset 1" identifies the first chip of the first sixty- four chip segment
- "Offset 2" identifies the first chip of the next sixty-four chip segment
- "Offset 3" identifies the first chip of the next following segment.
- the final sixty- four chip segment starts with a chip identified by offset 512 (not shown). While a sixty- four chip segment is used in this illustration, segment length may be longer or shorter.
- Factors such as the number of portable (and fixed location) base stations may influence frame segmentation. For example, for a large amount of base stations, the frame may be segmented to provide many offset values. Alternatively, for fewer base stations, the frame may be segmented to provide fewer offsets (with wider separations). Furthermore, frame segmentation may be time dependent. For example, for certain time periods (e.g., during the day, week, etc.) the frame may be segmented to provide a particular number of offsets for base station assignments. Then, at another time period, the frame may be re-segmented to provide more or less offsets. In other scenarios, segmenting may be initiated by the occurrence of an event.
- the number of portable base stations located at a particular location may increase based on a predefined event (e.g., a sporting event).
- the frame may be divided to provide additional offsets during the event and upon the completion of the event, the frame may be re-segmented to provide less offsets since less portable bases stations may be present at the location.
- RAN level factors e.g., the number of base stations, base station separation distances, etc.
- base station specific information e.g., transmission and reception capabilities
- performance metrics e.g., collision probability
- other information may also influence offset assignment.
- two portable base stations e.g., base station 204 and 206
- offsets e.g., offset 1 and offset 512
- the probability of collision reduces as offset separation increases.
- design, performance and calibration metrics may be relaxed with increased offset separation. For example, for widely separated PN offsets, timing calibration may be relaxed.
- a base station may use a less accurate timing reference signal, e.g., from a core network (or other timing source).
- timing calibration cycles may occur less frequent for base stations using widely separated offsets. Due to this calibration relaxation, less accurate and less expensive components may be used to produce the base stations. Similarly, reducing the number of frame segmentations (e.g., from 512 to 256), increases offset separation and thereby reduces the probability of signal collision.
- Characteristics of the PN sequence may be selected to agree with one or more standards and protocols.
- the frame length and frame segmentation may be selected to conform with a standard.
- a CDMA frame has a predefined length of 32,768 chips while a UMTS frame has a length of 40,960 chips.
- Both CDMA and UMTS frames may be divided into segments (referred to as slots) that are designated for particular channels.
- a CDMA time slot may be defined to include 2048 chips while a UMTS time slot length includes 2560 chips. As such a CDMA frame has 16 slots while a UMTS frame has 15 slots.
- the frame length and slot length may vary dependent upon the standards and protocols being implemented.
- the portable base station e.g., portable base station 204
- the following chips are sequentially used to produce an identification signal.
- the portable base station Upon reaching the end of the sequence (e.g., chip 32768), the portable base station returns to the beginning of the sequence (e.g., chip 1) and repetitively uses the sequence. While this particular example uses a sequence of pseudorandom numbers to define the code space and offsets to define segments of the code space, other methodologies and techniques may be implemented to define and segment a code space.
- a flowchart 400 represents some of the operations of the Offset Assigner 230 (shown in FIG. 2).
- the Offset Assigner 230 may be executed at the control station 220.
- the server 222 a computer system of other type of computation device located at the control station 220 may execute the Offset Assigner 230.
- operation execution may be distributed among two or more sites. For example, some operations may be executed by one or more of the portable base stations and at the server located at the control station 220.
- Operations of the Offset Assigner 230 include receiving 402 a request for an offset assignment from a base station such as a portable base station (e.g., base station 204) and determining 404 if an offset may be assigned to the base station.
- a base station such as a portable base station (e.g., base station 204)
- the Offset Assigner 230 may access a list of available offsets that is stored in server memory (not shown), the storage device 224 or other type of data storage unit that is in communication with the server 222.
- Previously assigned offsets to the portable base station may also be checked for availability. If no offsets are available, operations of the Offset Assigner 230 may include denying 406 the portable base station access to the RAN.
- the Offset Assigner 230 may also send a signal or message to inform the portable base station of the lack of offset availability and possibly provide an estimated time in which availability may improve. If one or more offsets are available, operations include determining 408 if an offset had been previously assigned to the portable base station. For example, the request from the portable base station may include data that represents that one or more offsets had been previously assigned and the Offset Assigner 230 may check data stored in the server, the storage device, or other device to identify any previously assigned offsets. The server may also request additional information from the portable base station to identify the offsets. For example, the server may send a message to the portable base station that includes a request for any previous offsets assigned to the base station.
- operations include assigning 410 an available offset to the portable base station.
- the offset assignment may use one or more factors. For example, the approximate location of the portable base station along with the location of other base stations (portable and fixed location) near by (or remotely located) to the portable base station maybe used to determine the assigned offset. Operational characteristics of one or more base stations (portable and fixed location) may also be used. For example transmission power, coverage area (e.g., number of coverage sectors), antenna beam patterns, etc. may be used to identify an appropriate offset for assignment.
- operations include determining 412 if the previous assignment may be reused.
- the Offset Assigner 230 may check presently assigned offsets to determine if the previous assignment is currently being used by another base station. If the previously assigned offset is unavailable, operations include assigning 410 an available offset to the portable base station. If the previous assignment is available, the Offset Assigner 230 may re-assign the offset to the base station. Whether re-assigned or newly assigned, operations also include storing 414 the offset assignment for later retrieval and use. Typically, data that identifies the offset assignment and the portable base station are stored in memory, storage device 222, or other type of storage unit. Data structures and files along with data storage techniques and methodologies may be implemented to store the information.
- a flow chart 500 represents operations in which the Offset Assigner 230 monitors the offset assignments and dynamically adjusts the assignments, as needed.
- the probability of collisions may increase if two or more closely located bases stations can not be distinguished by one or more ATs in the general vicinity.
- the Offset Assigner 230 may update offset assignments in an efficient (and cost effective) manner, and thereby to reduce the probability of collisions.
- the portable base stations may periodically send messages to the control station 220 that include status information (e.g., location, operability, etc.), or, the control station 220 may solicit status information from portable base stations.
- the server 220 may send or broadcast a message to each portable base station.
- operations of the Offset Assigner 230 may include sending 502 a status request to each portable base station (and optionally, to each fixed location base station).
- the portable base stations may send a message to the control station 220 that includes status information.
- one or more responses may be delayed due to current activities or non-activity of the base station. For example, if currently providing service to an AT, a base station may not be able to send a response until service operations are complete or sufficient base station processing resources become available. Base stations that are not operating (e.g., powered down) typically are unable to send a response to answer the control station 220 request. In some arrangements, delayed responses and lack of responses are tracked by the control station 220 and may factor into the offset assignments. Operations also include receiving 504 one or more base station responses and determining 506 if the offset assignment(s) should be updated. Along with changes in location, changes in operability and the introduction of one or more new portable base stations, the Offset Assigner 230 determines if one or more offset assignments should be updated. For example, assignments may be deleted, added, or changed based upon the received responses.
- the Offset Assigner 230 may maintain 508 the offset assignment(s). In some implementations operations may also include recording this determination for statistical or other analysis. If assignment updates are warranted, operations include re-assigning 510 the offsets as appropriate. For example, portable base stations may be assigned offsets based upon moving to different locations, to reduce the probability of collision (e.g., separate the offset distances), etc., or, new offset assignments may be identified and sent to the corresponding base stations. The Offset Assigner 230 also stores 512 the offset re-assignments, for example, in the storage device 224 for later retrieval and use.
- the Offset Assigner 230 may also monitor other operations and events associated with the base stations. For example, PN offsets, PN sequences or other types of code space portions used in base station transmissions may be monitored. By monitoring the transmissions, the Offset Assigner 230 may compare the code space portions (used in transmissions) to the assigned portions of code space. If a match is detected, the transmissions may be allowed to continue. If a match is not detected, one or more signals or commands may be sent from the control station 220 to halt transmission from the respective base station. Accordingly, the properly assigned code space portion may then be provided to the base station for use in identification transmissions.
- PN offsets PN sequences or other types of code space portions used in base station transmissions
- the Offset Assigner 230 may compare the code space portions (used in transmissions) to the assigned portions of code space. If a match is detected, the transmissions may be allowed to continue. If a match is not detected, one or more signals or commands may be sent from the control station 220 to halt transmission from
- one or more processors may execute instructions to perform the operations of the Offset Assigner 220, e.g., respectively represented in flowchart 400 and 500.
- one or more general processors e.g., a microprocessor
- one or more specialized devices e.g., an application specific integrated circuit (ASIC), etc.
- ASIC application specific integrated circuit
- One or more of the processors may be implemented in a single integrated circuit as a monolithic structure or in a distributed structure.
- the instructions that are executed by the processors may reside in a memory (e.g., random access memory (RAM), read-only memory (ROM), static RAM (SRAM), etc.).
- RAM random access memory
- ROM read-only memory
- SRAM static RAM
- the instructions may also be stored on one or more mass storage devices (e.g., magnetic, magneto-optical disks, or optical disks, etc.).
- One or more of the operations associated with the Offset Assigner 220 may be performed by one or more programmable processors (e.g., a microprocessor, an ASIC, etc.) executing a computer program.
- the execution of one or more computer programs may include operating on input data (e.g., data provided from a source external to the RAN, etc.) and generating output (e.g., sending data to a destination external to the RAN, etc.).
- the operations may also be performed by a processor implemented as special purpose logic circuitry (e.g., an FPGA (field programmable gate array), an ASIC (application-specific integrated circuit), etc.). Operation execution may also be executed by digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
- the operations described in flowcharts 400 and 500 (along with other operations of the Offset Assigner 220) may be implemented as a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device (e.g., RAM, ROM, hard-drive, CD-ROM, etc.) or in a propagated signal.
- the computer program product may be executed by or control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program may be written in one or more forms of programming languages, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- a computer program may be deployed to be executed on one computing device (e.g., controller, computer system, etc.) or on multiple computing devices (e.g., multiple controllers) at one site or distributed across multiple sites and interconnected by a communication network.
- Other embodiments are within the scope of the following claims.
Abstract
In addition to other aspects disclosed, a portable base station requests assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The portable base station is also capable of transmitting an identification signal using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
Description
Assigning Code Space to Portable Base Stations
BACKGROUND
This description relates to assigning portions of a code space to portable base stations. Cellular communication systems include antenna towers erected in fixed locations to provide wireless coverage to devices such as cellular phones, personal digital assistants (PDAs) and computer systems (each of which is referred to as an Access Terminal or AT). In some situations an AT may be located within the coverage area of multiple towers. To distinguish one tower from another, each tower transmits a unique identification signal that includes information assigned to the tower. This information may be a sequence of pseudorandom numbers (PN) that are transmitted in a repetitive manner. To uniquely identify each tower, transmission of the PN sequence is initiated from different elements in the sequence or different sequences may be transmitted. Using one PN sequence, the starting elements may be identified by a number that represents the offset from the first element in the sequence to the starting element (assigned to the tower). Prior to becoming operational, different offsets may be assigned to the towers in a procedure known as radio frequency (RF) planning that seeks to protect against interfering identification signals being transmitted from two or more closely located towers.
SUMMARY
In general, in some aspects of the invention, a portable base station requests assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The portable base station also transmits an identification signal using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
The request from the portable base station may include data that represents the location of the portable base station. The code space may include a sequence of pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips. Requesting the assignment may be initiated
by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station. The code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
In some aspects of the invention, a system is disclosed that includes a portable base station that requests assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The portable base station is also capable of transmitting an identification signal by using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
The portable base station may provide the functionality of a radio node, a radio node controller, an access gateway, and other similar components. The assignment may be based upon the distance between the portable base station and another base station. The remotely located control station may include a server for assigning the code space portions. The assignment request may include data that represents the location of the portable base station. The code space may include a sequence of pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips. Requesting the assignment may be initiated by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station. The code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
In some aspects of the invention, a medium bears instructions to cause a portable base station to request assignment of a portion of a code space from a remotely located control station. The assignment is based upon the location of the portable base station. The instructions also cause the portable base station to transmit an identification signal using the assigned code space portion such that the identification signal uniquely identifies the portable base station to one or more access terminals.
The request from the portable base station may include data that represents the location of the portable base station. The code space may include a sequence of
pseudorandom numbers and the assigned code space portion may be defined by an offset associated with the sequence. This offset may be represented by one or more types of data such as by a number of chips. Requesting the assignment may be initiated by a predefined event such as powering up the portable base station or the remotely located control station requesting the status of the portable base station. The code space may conform to one or more standards and protocols such as a Code Division Multiple Access (CDMA) standard, a Universal Mobile Telecommunication System (UMTS) standard, or other similar standard.
Among the advantages of the techniques described here are one or more of the following.
By dynamically assigning code space (e.g., offsets of a pseudorandom number sequence, etc.) to portable base stations, the portable stations may be deployed and made operational in a relatively short time period and in a cost effective manner (compared to the time-consuming, deliberate and often expensive exercise of manual code space assignment). Additionally, by requesting the assignments from a control station, code space assignments may be tracked by the control station along with the location of the portable base stations. Furthermore, predefined events may initiate assignment requests, thereby, providing more controllability in allocating the code space. Other features and advantages will be apparent from the description and the claims.
DESCRIPTION
FIG. 1 is a diagram of a telecommunication core network in communication with a fixed location base station and a portable base station. FIG. 2 is a diagram of a control station in communication with multiple portable base stations and a fixed location base station.
FIG. 3 is a diagram of a PN sequence.
FIG. 4 is a flow chart of operations executed by an Offset Assigner.
FIG. 5 is a flow chart of other operations executed by an Offset Assigner.
Referring to FIG. 1, a radio access network (RAN) 100 includes a conventional antenna tower 102 that is erected at a fixed location and transmits and receives
electromagnetic signals that are provided to or from a fixed location base station 104. One or more signaling techniques and standards may be implemented by the fixed location base station 104 to establish communication links (via the antenna tower 102) with one or more ATs such as a cellular telephone 106. For example, techniques and standards associated with the Universal Mobile Telecommunications System (UMTS) may be implemented such that multiple ATs may establish communication links and access the fixed location base station 104. Standards associated with spread spectrum air interface protocols such as code division multiple access (CDMA), wideband (W- CDMA), etc. may also be implemented for multiple AT access. Other protocols supported may include the IxEV-DO protocol, which is an
EVolution of the IxRTT standard for high-speed data-only (DO) services and has been standardized by the Telecommunication Industry Association (TIA) as TIA/EIA/IS-856, "CDMA2000 High Rate Packet Data Air Interface Specification", 3GPP2 C.S0024-0, Version 4.0, October 25, 2002, which is incorporated herein by reference. Revision A to this specification has been published as TIA/EIA/IS-856, "CDMA2000 High Rate Packet Data Air Interface Specification", 3GPP2 C.S0024-A, Version 2.0, June 2005, which is also incorporated herein by reference. Revision B to this specification has been initiated as TIA/EIA/IS-856, "CDMA2000 High Rate Packet Data Air Interface Specification," 3GPP2 C.S0024-B, Version 1.0, March 2006 and is also incorporated herein by reference.
To identify itself, the fixed location base station 104 transmits a signal (via the antenna 102) that uses one or more spread spectrum techniques such as being modulated with a unique pseudorandom code. Thereby, the identification signal may appear as noise, however, the signal may be extracted with a correlation process by an appropriate receiver aware of the pseudorandom sequence. By implementing such spread spectrum techniques or orthogonal coding techniques, an AT may distinguish base station identities and the probability of identification signal interference may be reduced. Other types of orthogonal or non-orthogonal coding techniques may also be used to produce unique transmission signals. For example, different PN sequences (e.g., gold sequences) referred to as scrambling codes (for W-CDMA) may be implemented. Different types of information may also be transmitted to uniquely identify the base station 104. For example data (e.g., a cell identifier) uniquely assigned to the base station 104 may be transmitted.
To provide an identification signal (along with transmitting and receiving other signals), the fixed location base station 104 includes a radio node (RN) 108 that supports the wireless standards and protocols (e.g., CDMA, W-CDMA, UMTS, etc.) for communicating with the ATs. Typically the RN 108 includes a transceiver for receiving and transmitting electromagnetic signals. The RN 108 may also include one or more components (e.g., a modulator/demodulator (MODEM)) for modulating a transmission carrier signal to encode digital information for transmission or demodulating a received analog signal to decode transmitted digital information. The RN 108 is connected to a radio node controller (RNC) 110 that provides commands (and transmission signals) to the RN 108 and receives incoming signals from the RN 108. An access gateway 112 such as a packet data serving node (PDSN) is connected to the RNC 110 and may be implemented as a data server to direct data packets to appropriate delivery locations. Additionally the access gateway 112 provides an interface between networking functions and service levels defined by one or more standards such as the Open Systems Interconnect (OSI) protocol standard defined by the International Standards Organization (ISO), which is herein incorporated by reference. With reference to the seven OSI protocol layers, the access gateway 112 provides an interface between the link layer (e.g., layer 2) functionality provided by the fixed location base station 104 and the routing layer (e.g., layer 3) functionality provided by a core network 114 that is connected to the fixed location base station. Along with sending and receiving content (e.g., data packets) to and from the fixed location base station 104, the core network 114 exchanges data and signals with other components included in the RAN 100. For example, data may be sent to other base stations, conventional landline telephone systems (e.g., Plain Old Telephone Service (POTS) systems, etc.) or other similar delivery sites and sources.
As mentioned above, antenna towers such as antenna tower 102 are erected to remain fixed at one location. Prior to erecting the towers, the geographical layout of the towers is planned to provide wireless coverage. Additionally each tower is assigned a portion of a code space so that the antenna (and corresponding fixed location base station 104) may uniquely identify itself to the one or more ATs within the coverage area. Since ATs such as AT 106 communicate with base stations (e.g., CDMA, W- CDMA and UMTS base stations) on the equivalent frequencies, an AT needs to differentiate one fixed location base station from another. In order to identify each
fixed location base station separately, each base station repeatedly transmits an identical pseudorandom number (PN) sequence of codes that are offset in time from the PN sequences being transmitted by the other base stations. The PN offset is assigned to each fixed location base station respectively connected to an antenna erected at a fixed location. Typically these offset assignments are determined prior to the antenna tower becoming operational and are static in the sense of not being adjusted once the tower is in operation. However, such a manual offset assignment process is often time- consuming and expensive. Different PN-sequences may also be transmitted to uniquely identify base stations. Furthermore, signals may be transmitted on different frequencies or share a similar frequency.
The RAN 100 also includes a portable base station 116 that is in communication with the core network 114 and provides the functionality of the fixed location base station 104. For example, the portable base station 116 includes an RN 118, an RNC 120 and an access gateway 122 (e.g., a PSDN). The portable base station 116 is connected to a portable antenna 124 that is capable of establishing links with one or more ATs, however, antenna characteristics (e.g., beam pattern, gain, etc.) of the portable antenna are typically selected for establishing links to ATs located relatively close to the portable base station. Furthermore, the design characteristics (e.g., component size, power consumption, etc.) of the RN 118, RNC 120 and the access gateway 122 may be selected for portability. As such, the portable base station 116 may provide less wireless coverage area than the fixed location base station 104 (e.g., coverage to service a single residential home, a portion of a multiple residence building or other structure or location of similar size and area). However, due to its mobility, the portable base station 116 may interfere with the operations of the fixed base station 104 or other relatively closely located base stations (e.g., other portable base stations, fixed location base stations). For example, identification signals using near-by or equivalent code space (e.g., PN offset, PN sequence, etc.) may interfere with the identification signals transmitted by the portable base station 116.
Referring to FIG. 2, a RAN 200 includes three portable base stations 202, 204, 206 that are respectively located at and provide coverage to three separate locations
(e.g., residential homes) 208, 210, 212. The RAN 200 also includes a fixed base station 214 that is connected to an antenna tower 216 that also provides wireless coverage (e.g., larger coverage than the portable base stations). Each of the portable base
stations 202, 204, 206 and the fixed base station 214 are connected to a core network 218 that is in communication with a control station 220 (e.g., remotely located from the locations 208, 210 and 212) that includes a server 222 or other type of computing device (e.g., a computing system) or multiple computing devices that may provide distributed processing. The server 222 is in communication with a storage device 224 (e.g., magnetic, magneto-optical disks, or optical disks, etc.) that stores files, data structures, applications and instructions for execution by the server, or other types of data.
Due to their mobility, two or more of the portable base stations 202, 204, 206 may be closely located to each other (or to the fixed tower 216) and transmit identification signals on different or equivalent frequencies. As such, an AT 226 may be unable to distinguish between the pair of portable base stations (or a portable base station and the fixed tower 216). For example, locations 210 and 212 may be closely located (e.g., adjacent rooms, apartments, etc.) and the AT 226 may detect identification signals from both of the portable base stations 204 and 206. In particular, if the PN offsets or PN sequences (used by the portable base stations 210 and 212) are similar (e.g., occupy nearby code space or equivalent code space), the AT 226 may be unable to distinguish between the identification signals. In another scenario, additional portable base stations (using similar code space) may be moved into the area (e.g., placed in adjacent rooms or the same room) and may not be distinguishable by the AT 226. By assigning PN offsets (or different PN sequences) dynamically to each portable base station, code space may be allocated in a cost effective and timely manner (as each station is deployed). Furthermore, dynamic allocation allows distinguishable identification signals to be transmitted (using different or equivalent frequencies) from closely located portable base stations, thereby reducing potential signal collisions. For example, PN offsets widely separated in a PN sequence may be assigned to closely located portable base stations (or the fixed tower base station and a portable base station). As the portable base stations are moved (e.g., from one residence to another), the PN offset assignments may be adjusted to reduce potential identification signal collision. For example, by tracking the locations (e.g., Global Positioning System (GPS) coordinates) of the portable base stations and the fixed location base stations, a code space may be segmented and assigned for minimal interference among the base stations.
In the exemplary RAN 200, the control station 220 (via communication with the core network 218) dynamically allocates code space (e.g., one or more PN sequences) and assigns portions of the code space (e.g., PN offsets, PN sequences, etc.) to each of the portable base stations 202, 204, 206 (and optionally, the fixed location base station 214). Location tracking, PN offset assignment storage, and other functions may also be provided by the control station 220. In this arrangement, the server 222 executes operations for tracking the location of the base stations (e.g., portable base stations, fixed location base stations) and assigns appropriate PN offsets to the base stations based upon the location information and potentially other information (e.g., base station capabilities, performance, time of day, etc.). The server 222 stores the code space assignments along with other information (e.g., base station location information, base station capabilities, assignment confirmations, etc.) in the storage device 224. In some implementations transmissions between the control station 220 and the base stations (fixed or portable) are encrypted to reduce the probability of interception or modification. Furthermore, the encryption technique(s) may block base station users from modifying information (e.g., PN offsets) included in the transmissions.
PN offset (or PN sequence) assignment(s) may be initiated by the occurrence of a particular event which may or may not be predefined. For example, a portable base station may request a PN offset upon becoming operational (e.g., powered up) and establishing communication with the core network 218. The request may be provided in one or more forms such as a signal, electronic message, file, data structure, or other similar form. For illustration, a message 228 is sent by the portable base station 204 to the control station 220 via the core network 218 upon being powered up and establishing a communication link with the core network. In a similar manner the other portable base stations 202, 206 may request a PN offset (or other type of code space portion) upon becoming operational. In addition to becoming operational, events that initiate a PN offset request may include the occurrence of predefined time (e.g., midnight each evening), resetting the portable base station, user initiated, or other type of event. The request 228 may contain one or more types of information such as data that identifies the portable base station 204 (e.g., a unique alphanumerical identifier assigned to the base station by a manufacturer, etc.), the location of the portable base station (e.g., GPS coordinates), base stations capabilities (e.g., coverage area,
transmission power, etc.), status information (e.g., number of established ATs links) and other types of information. For example, GPS coordinates may be inserted into the message 228 from a GPS receiver (not shown) that is included in the portable base station 204. Location information may also be provided from an external source such as an external GPS receiver or other type of location determining device in communication with the portable base station 204. Data that represents a previously used PN offset (or other type of code space portion) may also be included in the message 228. For example, the last PN offset assigned or a list of previously assigned PN offsets (e.g., all assignments, assignments over a period of time) may be provided in the request. These previously assigned PN offsets may be used by the server 222 for assigning the requested offset (e.g., assign a new PN offset, assign a previously used PN offset, etc.). In some arrangements, preference may factor into some assignments as described in "Configuring Preferred User Zone Lists for Private Access Points for Wireless Networking", U.S. Patent Application Serial No. 11/640,503, filed on 15 December 2006, the entire contents of which are hereby incorporated by reference. Information such as location information may be provided to the portable base station 204 from a user interface (e.g., a keyboard) or a data conduit (e.g., communication port) from another device (e.g., a GPS receiver). Other included information may be used for security (e.g., a public key, etc.), data compression, or other types of functions. Rather than the portable base station 204 initiating a request, the control station
220 may trigger a request for a PN offset assignment. For example, a polling signal may be sent from the control station 220 to each of the base stations (portable and fixed location) at predefined intervals (e.g., daily, weekly, etc.). Upon receiving the polling signal, requests such as the request 228 may be produced and sent from the corresponding portable base station 204 to the control station 220. Along with polling all of the portable and fixed location base stations, in some arrangements a portion of the base stations may be polled. For example, based stations located in a particular geographical region may be polled at one time and base stations located in another region may be polled at a different time. In another scenario, the server 222 may track mobile base stations that are more frequently assigned PN offsets (e.g., due to frequent movements). These base stations may be polled more frequently than base stations that have a relatively stationary history.
To process the received requests, an Offset Assigner 230 is executed by the server 222. Along with request processing, the Offset Assigner 230 identifies the appropriate PN offset (if any) that should be assigned and informs the base station of the assignment. For example, upon determining a PN offset assignment for the portable base station 204, a message 232 is sent from the control station 220 to the portable base station. Data 234 represents the PN offset that may be retrieved from the message 232 and stored in a memory (not shown) (e.g., random access memory (RAM), read-only memory (ROM), static RAM (SRAM), etc.) or a storage device (also not shown) included in the portable base station 204. Similarly, the control station 220 may respectively provide PN offsets 236, 238 to the other portable base stations 202, 206. While the fixed location base station 214 is typically assigned a PN offset based upon a planning procedure that is executed prior to the tower 216 becoming operational, in some scenarios the control station 220 may assign a PN offset 240 to the fixed location base station. The assigned PN offset 240 may be used by a MODEM, which is included in the RN portion of the fixed location base station 214, to produce an appropriate identification signal.
As PN offsets are assigned, the server 222 stores data that represents the offset assignments. For example, data may be stored in the storage unit 224 that uniquely represents both the assigned offset and the base station to which it is assigned. One or more data types, data structures, storage techniques and methodologies may be implemented so that the assigned offsets may be efficiently stored and retrievable.
One or more techniques and methodologies may be used by the Offset Assigner 230 to determine PN offset assignments. For example, by using location information included from the request messages, the Offset Assigner 230 may use the distance between the base stations in determining the PN offset assignments. The capabilities of the base stations may also be used in the determination. For example, the range that each base station is capable of establishing an AT link may be used to determine potential signal collision ranges among the base stations. These and other techniques and methodologies, known in the art of signal collision avoidance, individually or in combination, may be implemented by the Offset Assigner 230.
Referring to FIG. 3, a diagram 300 represents a sequence 302 of pseudorandom numbers that form one exemplary code space that may be allocated among portable base stations (and fixed location base stations). In this representation the PN sequence
302 includes binary numbers (e.g., a "0" or a "1") that occur substantially at random in the sequence. The PN sequence 302 may be generated by implementing one or more techniques, for example, a random number generator may produce the sequence. Each binary number is referred to as a chip and may be considered the basic building element from which the PN sequence is produced. The length of the PN sequence is referred to as a frame and is predefined with a relatively large number of chips. For example, this sequence may represent 32,768 chips, however, other exemplary sequences may include more or less chips.
As mentioned, for identification, each portable base station may transmit the sequence as an identification signal within its coverage distance. To provide a continuous signal, the sequence is transmitted in a repetitive manner from each base station. Each portable base station transmits a unique identification signal to differentiate itself from other base stations. For example, each portable base station may initiate transmission of the sequence 302 starting from a different chip included in the sequence. Each starting chip may be identified by dividing the frame into a predefined number of segments. For example, the frame may be divided into segments with equivalent chip lengths (e.g., sixty-four chips). As such, the frame (with a length of 32,768 chips) is divided into 512 segments that each include 64 chips. Alternatively, segments lengths may not be equivalent and some may contain different number of chips.
In the figure, the first chip of each segment is identified as an offset. For example, "Offset 1" identifies the first chip of the first sixty- four chip segment, "Offset 2" identifies the first chip of the next sixty-four chip segment and "Offset 3" identifies the first chip of the next following segment. In this example, the final sixty- four chip segment starts with a chip identified by offset 512 (not shown). While a sixty- four chip segment is used in this illustration, segment length may be longer or shorter.
Factors such as the number of portable (and fixed location) base stations may influence frame segmentation. For example, for a large amount of base stations, the frame may be segmented to provide many offset values. Alternatively, for fewer base stations, the frame may be segmented to provide fewer offsets (with wider separations). Furthermore, frame segmentation may be time dependent. For example, for certain time periods (e.g., during the day, week, etc.) the frame may be segmented to provide a particular number of offsets for base station assignments. Then, at another time period,
the frame may be re-segmented to provide more or less offsets. In other scenarios, segmenting may be initiated by the occurrence of an event. For example, the number of portable base stations located at a particular location (e.g., a sporting event stadium) may increase based on a predefined event (e.g., a sporting event). The frame may be divided to provide additional offsets during the event and upon the completion of the event, the frame may be re-segmented to provide less offsets since less portable bases stations may be present at the location.
Various types of information such as RAN level factors (e.g., the number of base stations, base station separation distances, etc.), base station specific information (e.g., transmission and reception capabilities), performance metrics (e.g., collision probability) and other information may also influence offset assignment. For example, two portable base stations (e.g., base station 204 and 206) that are separated by a relatively small distance may be respectively assigned offsets (e.g., offset 1 and offset 512) separated a considerable distance in the frame. Generally, the probability of collision reduces as offset separation increases. Also, design, performance and calibration metrics may be relaxed with increased offset separation. For example, for widely separated PN offsets, timing calibration may be relaxed. So, rather than frequently monitoring a highly accurate timing signal (e.g., a timing signal from a GPS system) to calibrate one or more internal clocks, a base station may use a less accurate timing reference signal, e.g., from a core network (or other timing source).
Furthermore, timing calibration cycles may occur less frequent for base stations using widely separated offsets. Due to this calibration relaxation, less accurate and less expensive components may be used to produce the base stations. Similarly, reducing the number of frame segmentations (e.g., from 512 to 256), increases offset separation and thereby reduces the probability of signal collision.
Characteristics of the PN sequence may be selected to agree with one or more standards and protocols. For example, the frame length and frame segmentation may be selected to conform with a standard. A CDMA frame has a predefined length of 32,768 chips while a UMTS frame has a length of 40,960 chips. Both CDMA and UMTS frames may be divided into segments (referred to as slots) that are designated for particular channels. For example, a CDMA time slot may be defined to include 2048 chips while a UMTS time slot length includes 2560 chips. As such a CDMA
frame has 16 slots while a UMTS frame has 15 slots. However, the frame length and slot length may vary dependent upon the standards and protocols being implemented.
Starting with the chip identified by the offset (e.g., Offset 2) assigned to the portable base station (e.g., portable base station 204), the following chips are sequentially used to produce an identification signal. Upon reaching the end of the sequence (e.g., chip 32768), the portable base station returns to the beginning of the sequence (e.g., chip 1) and repetitively uses the sequence. While this particular example uses a sequence of pseudorandom numbers to define the code space and offsets to define segments of the code space, other methodologies and techniques may be implemented to define and segment a code space.
Referring to FIG. 4, a flowchart 400 represents some of the operations of the Offset Assigner 230 (shown in FIG. 2). As mentioned above, the Offset Assigner 230 may be executed at the control station 220. For example, the server 222, a computer system of other type of computation device located at the control station 220 may execute the Offset Assigner 230. Furthermore, along with being executed at a single site (e.g., control station 220), operation execution may be distributed among two or more sites. For example, some operations may be executed by one or more of the portable base stations and at the server located at the control station 220.
Operations of the Offset Assigner 230 include receiving 402 a request for an offset assignment from a base station such as a portable base station (e.g., base station 204) and determining 404 if an offset may be assigned to the base station. For example, the Offset Assigner 230 may access a list of available offsets that is stored in server memory (not shown), the storage device 224 or other type of data storage unit that is in communication with the server 222. Previously assigned offsets to the portable base station may also be checked for availability. If no offsets are available, operations of the Offset Assigner 230 may include denying 406 the portable base station access to the RAN. The Offset Assigner 230 may also send a signal or message to inform the portable base station of the lack of offset availability and possibly provide an estimated time in which availability may improve. If one or more offsets are available, operations include determining 408 if an offset had been previously assigned to the portable base station. For example, the request from the portable base station may include data that represents that one or more offsets had been previously assigned and the Offset Assigner 230 may check data stored
in the server, the storage device, or other device to identify any previously assigned offsets. The server may also request additional information from the portable base station to identify the offsets. For example, the server may send a message to the portable base station that includes a request for any previous offsets assigned to the base station.
If an offset had not been previously assigned, operations include assigning 410 an available offset to the portable base station. As mentioned above, the offset assignment may use one or more factors. For example, the approximate location of the portable base station along with the location of other base stations (portable and fixed location) near by (or remotely located) to the portable base station maybe used to determine the assigned offset. Operational characteristics of one or more base stations (portable and fixed location) may also be used. For example transmission power, coverage area (e.g., number of coverage sectors), antenna beam patterns, etc. may be used to identify an appropriate offset for assignment. In this implementation, if an offset had been previously assigned to the portable base station, operations include determining 412 if the previous assignment may be reused. For example, the Offset Assigner 230 may check presently assigned offsets to determine if the previous assignment is currently being used by another base station. If the previously assigned offset is unavailable, operations include assigning 410 an available offset to the portable base station. If the previous assignment is available, the Offset Assigner 230 may re-assign the offset to the base station. Whether re-assigned or newly assigned, operations also include storing 414 the offset assignment for later retrieval and use. Typically, data that identifies the offset assignment and the portable base station are stored in memory, storage device 222, or other type of storage unit. Data structures and files along with data storage techniques and methodologies may be implemented to store the information.
Referring to FIG. 5, a flow chart 500 represents operations in which the Offset Assigner 230 monitors the offset assignments and dynamically adjusts the assignments, as needed. As the portable base stations are moved (e.g., enter areas, leave areas, etc.) from location to location, the probability of collisions may increase if two or more closely located bases stations can not be distinguished by one or more ATs in the general vicinity. By monitoring the status (e.g., location, operability, etc.) of the portable base stations in communication with the server 222, the Offset Assigner 230
may update offset assignments in an efficient (and cost effective) manner, and thereby to reduce the probability of collisions. For example, as a portable base station is moved near (e.g., into the same building) to a group of other portable base stations, offsets may be adjusted to reduce conflicting assignments. In some implementations, the portable base stations may periodically send messages to the control station 220 that include status information (e.g., location, operability, etc.), or, the control station 220 may solicit status information from portable base stations. For example, the server 220 may send or broadcast a message to each portable base station. As such, operations of the Offset Assigner 230 may include sending 502 a status request to each portable base station (and optionally, to each fixed location base station). In response to receiving the status request, the portable base stations may send a message to the control station 220 that includes status information. In some scenarios, one or more responses may be delayed due to current activities or non-activity of the base station. For example, if currently providing service to an AT, a base station may not be able to send a response until service operations are complete or sufficient base station processing resources become available. Base stations that are not operating (e.g., powered down) typically are unable to send a response to answer the control station 220 request. In some arrangements, delayed responses and lack of responses are tracked by the control station 220 and may factor into the offset assignments. Operations also include receiving 504 one or more base station responses and determining 506 if the offset assignment(s) should be updated. Along with changes in location, changes in operability and the introduction of one or more new portable base stations, the Offset Assigner 230 determines if one or more offset assignments should be updated. For example, assignments may be deleted, added, or changed based upon the received responses.
If determined that the current assignments are satisfactory (e.g., due to minimal changes in deployment locations, meeting a predefined collision probability threshold, satisfying a metric, etc.), the Offset Assigner 230 may maintain 508 the offset assignment(s). In some implementations operations may also include recording this determination for statistical or other analysis. If assignment updates are warranted, operations include re-assigning 510 the offsets as appropriate. For example, portable base stations may be assigned offsets based upon moving to different locations, to reduce the probability of collision (e.g., separate the offset distances), etc., or, new
offset assignments may be identified and sent to the corresponding base stations. The Offset Assigner 230 also stores 512 the offset re-assignments, for example, in the storage device 224 for later retrieval and use.
The Offset Assigner 230 may also monitor other operations and events associated with the base stations. For example, PN offsets, PN sequences or other types of code space portions used in base station transmissions may be monitored. By monitoring the transmissions, the Offset Assigner 230 may compare the code space portions (used in transmissions) to the assigned portions of code space. If a match is detected, the transmissions may be allowed to continue. If a match is not detected, one or more signals or commands may be sent from the control station 220 to halt transmission from the respective base station. Accordingly, the properly assigned code space portion may then be provided to the base station for use in identification transmissions.
In some embodiments one or more processors may execute instructions to perform the operations of the Offset Assigner 220, e.g., respectively represented in flowchart 400 and 500. For example, one or more general processors (e.g., a microprocessor) and/or one or more specialized devices (e.g., an application specific integrated circuit (ASIC), etc.) may execute instructions. One or more of the processors may be implemented in a single integrated circuit as a monolithic structure or in a distributed structure. In some embodiments the instructions that are executed by the processors may reside in a memory (e.g., random access memory (RAM), read-only memory (ROM), static RAM (SRAM), etc.). The instructions may also be stored on one or more mass storage devices (e.g., magnetic, magneto-optical disks, or optical disks, etc.). One or more of the operations associated with the Offset Assigner 220 may be performed by one or more programmable processors (e.g., a microprocessor, an ASIC, etc.) executing a computer program. The execution of one or more computer programs may include operating on input data (e.g., data provided from a source external to the RAN, etc.) and generating output (e.g., sending data to a destination external to the RAN, etc.). The operations may also be performed by a processor implemented as special purpose logic circuitry (e.g., an FPGA (field programmable gate array), an ASIC (application-specific integrated circuit), etc.).
Operation execution may also be executed by digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The operations described in flowcharts 400 and 500 (along with other operations of the Offset Assigner 220) may be implemented as a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device (e.g., RAM, ROM, hard-drive, CD-ROM, etc.) or in a propagated signal. The computer program product may be executed by or control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program may be written in one or more forms of programming languages, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be executed on one computing device (e.g., controller, computer system, etc.) or on multiple computing devices (e.g., multiple controllers) at one site or distributed across multiple sites and interconnected by a communication network. Other embodiments are within the scope of the following claims.
Claims
1. A method comprising : a portable base station, requesting assignment of a portion of a code space from a remotely located control station, wherein the assignment is based, at least in part, upon the location of the portable base station; and transmitting an identification signal from the portable base station, using the assigned code space portion, to uniquely identify the portable base station to one or more access terminals.
2. The method of claim 1 in which the request from the portable base station includes data that represents the location of the portable base station.
3. The method of claim 1 in which the code space includes a sequence of pseudorandom numbers.
4. The method of claim 3 in which the assigned code space portion is defined by an offset associated with the sequence of pseudorandom numbers.
5. The method of claim 4 in which the offset is defined by a number of chips.
6. The method of claim 1 in which requesting the assignment is initiated by a predefined event.
7. The method of claim 6 in which the event includes powering up the portable base station.
8. The method of claim 6 in which the event includes the remotely located control station requesting the status of the portable base station.
9. The method of claim 1 in which the code space conforms to a Code Division Multiple Access (CDMA) standard.
10. The method of claim 1 in which the code space conforms to a Universal Mobile Telecommunication System (UMTS) standard.
11. A system comprising: a portable base station to request assignment of a portion of a code space from a remotely located control station, wherein the assignment is based, at least in part, upon the location of the portable base station, the portable base station is also capable of transmitting an identification signal by using the assigned code space portion to uniquely identify the portable base station to one or more access terminals.
12. The system of claim 11 in which the portable base station provides the functionality of a radio node, a radio node controller and an access gateway.
13. The system of claim 11 in which the assignment is based upon the distance between the portable base station and another base station.
14. The system of claim 11 in which the remotely located control station includes a server to assign the code space portion.
15. The system of claim 11 in which the assignment request includes data that represents the location of the portable base station.
16. The system of claim 11 in which the code space includes a sequence of pseudorandom numbers.
17. The system of claim 16 in which the assigned code space portion is defined by an offset associated with the sequence of pseudorandom numbers.
18. The system of claim 17 in which the offset is defined by a number of chips .
19. The system of claim 11 in which the assignment is requested upon the occurrence of a predefined event.
20. The system of claim 19 in which the event includes powering up the portable base station.
21. The system of claim 19 in which the event includes the remotely located control station requesting the status of the portable base station.
22. The system of claim 10 in which the code space conforms to a Code Division Multiple Access (CDMA) standard.
23. The system of claim 10 in which the code space conforms to a Universal Mobile Telecommunication System (UMTS) standard.
24. A medium bearing instructions to cause: a portable base station to request assignment of a portion of a code space from a remotely located control station, wherein the assignment is based, at least in part, upon the location of the portable base station; and transmission of an identification signal from the portable base station by using the assigned code space portion, wherein the identification signal uniquely identifies the portable base station to one or more access terminals.
25. The medium of claim 24 in which the assignment request from the portable base station includes data that represents the location of the portable base station.
26. The medium of claim 24 in which the assigned code space includes a sequence of pseudorandom numbers.
27. The medium of claim 26 in which the assigned code space portion is defined by an offset associated with the sequence of pseudorandom numbers.
28. The medium of claim 27 wherein the offset is defined by a number of chips.
29. The medium of claim 24 wherein requesting the assignment is initiated by an event.
30. The medium of claim 29 wherein the event includes powering up the portable base station.
31. The medium of claim 29 wherein the event includes the remotely located control station requesting the status of the portable base station.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/617,298 US8229498B2 (en) | 2006-12-28 | 2006-12-28 | Assigning code space to portable base stations |
US11/617,298 | 2006-12-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008082985A1 true WO2008082985A1 (en) | 2008-07-10 |
Family
ID=39387298
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/088112 WO2008082985A1 (en) | 2006-12-28 | 2007-12-19 | Assigning code space to portable base stations |
Country Status (2)
Country | Link |
---|---|
US (2) | US8229498B2 (en) |
WO (1) | WO2008082985A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8078165B2 (en) | 2006-09-07 | 2011-12-13 | Airvana, Corp. | Configuring preferred user zone lists for private access points for wireless networking |
US8160629B2 (en) | 2006-09-07 | 2012-04-17 | Airvana, Corp. | Controlling reverse link interference in private access points for wireless networking |
US8229498B2 (en) | 2006-12-28 | 2012-07-24 | Airvana, Corp. | Assigning code space to portable base stations |
US8688809B2 (en) | 2006-09-07 | 2014-04-01 | Airvana Lp | Provisioning private access points for wireless networking |
Families Citing this family (116)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8195187B2 (en) | 2001-06-25 | 2012-06-05 | Airvana Network Solutions, Inc. | Radio network control |
US8160020B2 (en) | 2001-06-25 | 2012-04-17 | Airvana Network Solutions, Inc. | Radio network control |
US7603127B2 (en) * | 2001-10-12 | 2009-10-13 | Airvana, Inc. | Boosting a signal-to-interference ratio of a mobile station |
US7843892B2 (en) * | 2004-04-28 | 2010-11-30 | Airvana Network Solutions, Inc. | Reverse link power control |
US7983708B2 (en) * | 2004-04-28 | 2011-07-19 | Airvana Network Solutions, Inc. | Reverse link power control |
WO2006010958A2 (en) | 2004-07-30 | 2006-02-02 | Andrew Richardson | Power control in a local network node (lnn) |
EP1779543B1 (en) * | 2004-07-30 | 2012-04-25 | Andrew Richardson | Signal transmission method from a local network node |
US9876670B2 (en) | 2004-07-30 | 2018-01-23 | Commscope Technologies Llc | Local network node |
US7558356B2 (en) | 2004-09-30 | 2009-07-07 | Airvana, Inc. | Providing global positioning system (GPS) timing signals to remote cellular base stations |
US7515643B2 (en) | 2004-09-30 | 2009-04-07 | Airvana, Inc. | Modulation for broadcasting from multiple transmitters |
US7626926B2 (en) * | 2004-12-09 | 2009-12-01 | Airvana, Inc. | Traffic management in a wireless data network |
US7729243B2 (en) * | 2005-01-18 | 2010-06-01 | Airvana, Inc. | Reverse link rate and stability control |
US7831257B2 (en) | 2005-04-26 | 2010-11-09 | Airvana, Inc. | Measuring interference in radio networks |
US8099504B2 (en) | 2005-06-24 | 2012-01-17 | Airvana Network Solutions, Inc. | Preserving sessions in a wireless network |
US8111253B2 (en) | 2005-07-28 | 2012-02-07 | Airvana Network Solutions, Inc. | Controlling usage capacity in a radio access network |
US8295818B2 (en) | 2005-09-15 | 2012-10-23 | Airvana Network Solutions, Inc. | Broadcasting in wireless systems |
US7751835B2 (en) | 2005-10-04 | 2010-07-06 | Airvana, Inc. | Non-circular paging areas |
US8483616B1 (en) | 2005-11-01 | 2013-07-09 | At&T Intellectual Property Ii, L.P. | Non-interference technique for spatially aware mobile ad hoc networking |
US7558588B2 (en) * | 2005-11-18 | 2009-07-07 | Airvana, Inc. | Resource allocation in a radio access network |
US8149801B2 (en) * | 2007-08-17 | 2012-04-03 | At&T Intellectual Property Ii, L.P. | System and method for geocasting in a mobile ad hoc network |
US7969914B1 (en) * | 2008-07-25 | 2011-06-28 | At&T Intellectual Property Ii, L.P. | Method for establishing and operating a mobile Ad-Hoc network |
US8355410B2 (en) | 2007-08-17 | 2013-01-15 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
US7917169B1 (en) | 2005-11-30 | 2011-03-29 | At&T Intellectual Property Ii, L.P. | System and method for mobile ad hoc network |
US7525933B1 (en) * | 2005-11-30 | 2009-04-28 | At&T Intellectual Property Ii, L.P. | System and method for mobile ad hoc network |
US8702506B2 (en) * | 2005-11-30 | 2014-04-22 | At&T Intellectual Property I, L.P. | Geogame for mobile device |
US8777752B2 (en) | 2005-11-30 | 2014-07-15 | At&T Intellectual Property I, L.P. | Geogame for mobile device |
US8145221B2 (en) | 2005-12-16 | 2012-03-27 | Airvana Network Solutions, Inc. | Radio network communication |
US20070140218A1 (en) * | 2005-12-16 | 2007-06-21 | Nair Girish R | Managing backhaul connections in radio access networks |
US8094630B2 (en) | 2005-12-16 | 2012-01-10 | Airvana Network Solutions, Inc. | Radio frequency dragging prevention |
US8619702B2 (en) | 2005-12-16 | 2013-12-31 | Ericsson Evdo Inc. | Radio network control |
US7801487B2 (en) | 2005-12-29 | 2010-09-21 | Airvana, Inc. | Detection of radio frequency interference in wireless communication systems |
US11477617B2 (en) * | 2006-03-20 | 2022-10-18 | Ericsson Evdo Inc. | Unicasting and multicasting multimedia services |
US7672682B2 (en) * | 2006-03-28 | 2010-03-02 | Airvana, Inc. | Managing page cycle periods of access terminals |
US8346220B2 (en) * | 2006-03-31 | 2013-01-01 | Airvana Network Solutions, Inc. | Signaling for push-to-talk |
US7953040B2 (en) * | 2006-04-19 | 2011-05-31 | Airvana Network Solutions, Inc. | Channel assignment in wireless communication |
US8085696B2 (en) | 2006-07-14 | 2011-12-27 | Airvana Networks Solutions, Inc. | Dynamic modification of route update protocols |
US8023439B2 (en) * | 2006-11-20 | 2011-09-20 | Airvana Network Solutions, Inc. | Multicast flow distribution |
US8130686B2 (en) * | 2006-11-20 | 2012-03-06 | Airvana Network Solutions, Inc. | Multicasting push-to-media content |
US7730189B2 (en) * | 2006-11-22 | 2010-06-01 | Airvana, Inc. | Network-initiated session recovery |
US8639247B2 (en) * | 2006-12-12 | 2014-01-28 | Ericsson Evdo Inc. | Access terminal session authentication |
US8532658B2 (en) * | 2006-12-19 | 2013-09-10 | Airvana Network Solutions, Inc. | Neighbor list provision in a communication network |
US8457084B2 (en) * | 2006-12-20 | 2013-06-04 | Airvana Llc | Communication group configuration in a network |
US8176327B2 (en) | 2006-12-27 | 2012-05-08 | Airvana, Corp. | Authentication protocol |
US7926098B2 (en) | 2006-12-29 | 2011-04-12 | Airvana, Corp. | Handoff of a secure connection among gateways |
EP2119287B1 (en) * | 2007-02-28 | 2013-11-13 | Unwired Planet, LLC | Self configuring and optimisation of cell neighbours in wireless telecommunications networks |
US8400989B2 (en) * | 2007-04-13 | 2013-03-19 | Airvana Llc | Activating private access points for wireless networking |
US8781483B2 (en) * | 2007-04-13 | 2014-07-15 | Airvana Lp | Controlling access to private access points for wireless networking |
KR100988507B1 (en) * | 2007-06-27 | 2010-10-18 | 삼성전자주식회사 | Apparatus and method for dynamic frequency assignment in wireless communication system |
US8543139B2 (en) * | 2007-08-03 | 2013-09-24 | Airvana Llc | Distributed network |
US8059614B2 (en) * | 2007-08-31 | 2011-11-15 | Samsung Electronics Co., Ltd. | Pseudorandom noise selection method for mobile communication sites |
US8594663B2 (en) * | 2007-09-24 | 2013-11-26 | Airvana Llc | Selecting embedded cells in wireless networks |
US7933619B2 (en) * | 2007-10-02 | 2011-04-26 | Airvana, Corp. | Wireless control of access points |
US8358623B2 (en) * | 2007-11-06 | 2013-01-22 | Airvana Network Solutions, Inc. | Active handoffs in a network |
US8843638B2 (en) | 2007-12-13 | 2014-09-23 | Ericsson Evdo Inc. | Handing off active connections |
US8379625B2 (en) * | 2007-12-18 | 2013-02-19 | Airvana Llc | Obtaining time information in a cellular network |
US8520659B2 (en) * | 2007-12-18 | 2013-08-27 | Airvana Llc | Absolute time recovery |
US8259671B2 (en) | 2007-12-18 | 2012-09-04 | Airvana, Corp. | Attracting access terminals |
US7983672B2 (en) | 2007-12-19 | 2011-07-19 | Airvana, Corp. | Managing communications with private access points in wireless networks |
US8355727B2 (en) | 2007-12-19 | 2013-01-15 | Airvana, Corp. | Proximity detection in a network |
US8615593B2 (en) * | 2007-12-21 | 2013-12-24 | Airvana Llc | Providing zone indications for wireless networking |
US8909278B2 (en) * | 2007-12-21 | 2014-12-09 | Airvana Lp | Adjusting wireless signal transmission power |
US8452299B2 (en) * | 2007-12-21 | 2013-05-28 | Airvana Llc | Allocating code space to base stations |
US8165528B2 (en) | 2007-12-27 | 2012-04-24 | Airvana, Corp. | Interference mitigation in wireless networks |
US8402143B2 (en) * | 2007-12-28 | 2013-03-19 | Airvana Llc | Secure proxies for flat networks |
US20090168766A1 (en) * | 2007-12-28 | 2009-07-02 | Vedat Eyuboglu | Inter-Technology Bridging Over Access Points |
US8060058B2 (en) * | 2007-12-28 | 2011-11-15 | Airvana, Corp. | Secure mobile base station connections |
US7835698B2 (en) * | 2007-12-31 | 2010-11-16 | Airvana, Corp. | Interference mitigation in wireless networks |
US8554231B2 (en) * | 2007-12-31 | 2013-10-08 | Airvana Llc | Adaptation of portable base stations into cellular networks |
US8326249B2 (en) * | 2008-03-06 | 2012-12-04 | Qualcomm Incorporated | Methods and apparatus for supporting communications using a first polarization direction electrical antenna and a second polarization direction magnetic antenna |
US8295256B2 (en) * | 2008-08-29 | 2012-10-23 | Airvana, Corp. | Private access point beacon signals in wireless networks |
US9544922B2 (en) | 2008-09-16 | 2017-01-10 | At&T Intellectual Property I, L.P. | Quality of service scheme for collision-based wireless networks |
US8229397B2 (en) | 2008-09-23 | 2012-07-24 | Airvana, Corp. | Access terminal authorization at private access points in wireless networks |
US8942136B2 (en) * | 2008-10-07 | 2015-01-27 | Airvana Lp | Allocating communication frequencies to clusters of access points |
US8774134B2 (en) * | 2008-12-23 | 2014-07-08 | Airvana Lp | Access terminal hand-off methods in wireless networks |
US7995493B2 (en) | 2008-12-23 | 2011-08-09 | Airvana, Corp. | Estimating bandwidth in communication networks |
US8953566B2 (en) * | 2008-12-29 | 2015-02-10 | Airvana Lp | Providing a cellular network with connectivity to a different network |
US20100167777A1 (en) * | 2008-12-30 | 2010-07-01 | Airvana, Inc. | Power control for reverse link |
US8160631B2 (en) * | 2008-12-30 | 2012-04-17 | Airvana, Corp. | Power control for reverse link |
US8170598B2 (en) * | 2008-12-30 | 2012-05-01 | Airvana, Corp. | Information sharing in a private access point network |
US9078284B2 (en) | 2008-12-31 | 2015-07-07 | Airvana Lp | Personal access point media server |
US9210569B2 (en) | 2008-12-31 | 2015-12-08 | Commscope Technologies Llc | Femto personal proxy application client |
US8280376B2 (en) | 2008-12-31 | 2012-10-02 | Airvana, Corp. | Geography aware peer-to-peer overlay creation |
US8693987B2 (en) * | 2008-12-31 | 2014-04-08 | Airvana Lp | Femto personal policy server |
US8805371B2 (en) * | 2009-03-17 | 2014-08-12 | Airvana Lp | Identifying hand-over targets in lightly coordinated networks |
US8428601B2 (en) | 2009-05-07 | 2013-04-23 | Airvana Network Solutions, Inc. | Wireless network inter-technology handoffs |
US8542707B2 (en) * | 2009-05-18 | 2013-09-24 | Airvana Llc | Multi-carrier system selection |
US7907571B2 (en) * | 2009-06-30 | 2011-03-15 | Airvana, Corp. | Mobile aware beacon |
US8718697B2 (en) * | 2009-10-07 | 2014-05-06 | Airvana Lp | Mitigating interference using cooperative scheduling |
US9118428B2 (en) * | 2009-11-04 | 2015-08-25 | At&T Intellectual Property I, L.P. | Geographic advertising using a scalable wireless geocast protocol |
US8340636B2 (en) * | 2009-11-30 | 2012-12-25 | Airvana Llc | Determining if an access terminal is authorized to use an access point |
US8712056B2 (en) | 2010-06-03 | 2014-04-29 | At&T Intellectual Property I, L.P. | Secure mobile ad hoc network |
US10016684B2 (en) | 2010-10-28 | 2018-07-10 | At&T Intellectual Property I, L.P. | Secure geographic based gaming |
US9161158B2 (en) | 2011-06-27 | 2015-10-13 | At&T Intellectual Property I, L.P. | Information acquisition using a scalable wireless geocast protocol |
US9319842B2 (en) | 2011-06-27 | 2016-04-19 | At&T Intellectual Property I, L.P. | Mobile device configured point and shoot type weapon |
US9538402B2 (en) * | 2011-09-30 | 2017-01-03 | Nokia Solutions And Networks Oy | Fault management traffic reduction in heterogeneous networks |
US9495870B2 (en) | 2011-10-20 | 2016-11-15 | At&T Intellectual Property I, L.P. | Vehicular communications using a scalable ad hoc geographic routing protocol |
US8744419B2 (en) | 2011-12-15 | 2014-06-03 | At&T Intellectual Property, I, L.P. | Media distribution via a scalable ad hoc geographic protocol |
US9237492B2 (en) | 2012-05-31 | 2016-01-12 | Commscope Technologies Llc | Providing circuit switched service |
US9071451B2 (en) | 2012-07-31 | 2015-06-30 | At&T Intellectual Property I, L.P. | Geocast-based situation awareness |
US9210589B2 (en) | 2012-10-09 | 2015-12-08 | At&T Intellectual Property I, L.P. | Geocast protocol for wireless sensor network |
US9660745B2 (en) | 2012-12-12 | 2017-05-23 | At&T Intellectual Property I, L.P. | Geocast-based file transfer |
US9414399B2 (en) | 2013-02-07 | 2016-08-09 | Commscope Technologies Llc | Radio access networks |
US9936470B2 (en) | 2013-02-07 | 2018-04-03 | Commscope Technologies Llc | Radio access networks |
US9380466B2 (en) | 2013-02-07 | 2016-06-28 | Commscope Technologies Llc | Radio access networks |
US9992021B1 (en) | 2013-03-14 | 2018-06-05 | GoTenna, Inc. | System and method for private and point-to-point communication between computing devices |
EP3050397B1 (en) | 2013-09-24 | 2019-04-17 | Andrew Wireless Systems GmbH | Distributed processing in a centralized radio access network |
JP6410424B2 (en) * | 2013-12-12 | 2018-10-24 | 任天堂株式会社 | Information processing program, information processing apparatus, information processing apparatus control method, and information processing system |
US10057916B2 (en) | 2014-06-09 | 2018-08-21 | Commscope Technologies Llc | Radio access networks in which mobile devices in the same communication cell can be scheduled to use the same airlink resource |
AU2015274498B2 (en) | 2014-06-11 | 2019-09-19 | Commscope Technologies Llc | Bitrate efficient transport through distributed antenna systems |
US10785791B1 (en) | 2015-12-07 | 2020-09-22 | Commscope Technologies Llc | Controlling data transmission in radio access networks |
US20180199326A1 (en) * | 2017-01-10 | 2018-07-12 | Nextivity, Inc. | Real time adaptation of a mobile repeater antenna pattern |
CN116318589A (en) | 2017-10-03 | 2023-06-23 | 康普技术有限责任公司 | Dynamic downlink reuse in C-RAN |
WO2019222415A1 (en) | 2018-05-16 | 2019-11-21 | Commscope Technologies Llc | Dynamic uplink reuse in a c-ran |
CN112005598B (en) | 2018-05-16 | 2023-06-09 | 康普技术有限责任公司 | Downlink multicast for efficient forward in C-RAN |
US10798667B2 (en) | 2018-06-08 | 2020-10-06 | Commscope Technologies Llc | Automatic transmit power control for radio points of a centralized radio access network that primarily provide wireless service to users located in an event area of a venue |
EP3847788A4 (en) | 2018-09-04 | 2022-05-11 | CommScope Technologies LLC | Front-haul rate reduction for use in a centralized radio access network |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6597677B1 (en) * | 1998-07-16 | 2003-07-22 | Nec Corporation | Spreading code allocation method and system |
US20060203746A1 (en) * | 2005-03-10 | 2006-09-14 | Mark Maggenti | Method and apparatus for automatic configuration of wireless communication networks |
Family Cites Families (97)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5953370A (en) * | 1994-09-09 | 1999-09-14 | Omnipoint Corporation | Apparatus for receiving and correlating a spread spectrum signal |
DE69427404T2 (en) * | 1994-10-26 | 2001-11-08 | Ibm | Allocation method and apparatus for reusing network resources in a wireless communication system |
US5623495A (en) * | 1995-06-15 | 1997-04-22 | Lucent Technologies Inc. | Portable base station architecture for an AD-HOC ATM lan |
US5724662A (en) * | 1996-05-17 | 1998-03-03 | Motorola, Inc. | Method an apparatus in a radio communication system for assigning and utilizing sets of transmitters |
US5848063A (en) * | 1996-05-23 | 1998-12-08 | Qualcomm Incorporated | Method and apparatus for hard handoff in a CDMA system |
DE19638111C2 (en) * | 1996-09-11 | 1998-11-26 | Siemens Ag | Method for controlling the making of emergency calls in cordless telecommunication systems, in particular DECT / GAP systems |
KR100242421B1 (en) * | 1997-04-14 | 2000-02-01 | 윤종용 | Method for assigning pilot pn offset of digital mobile communication system |
US6049564A (en) * | 1997-04-28 | 2000-04-11 | Northern Telecom Limited | Method and apparatus for configuring PN-offsets for a non-uniform CDMA cellular network |
JP2865098B1 (en) * | 1997-10-01 | 1999-03-08 | 日本電気株式会社 | Frame offset determination method in CDMA communication |
JP2878265B1 (en) * | 1998-03-16 | 1999-04-05 | 三菱電機株式会社 | Code assignment apparatus and method |
FR2784525B1 (en) * | 1998-10-12 | 2006-07-28 | Cit Alcatel | PROCESS FOR ALLOCATING ORTHOGONAL CODES IN A MOBILE RADIOCOMMUNICATIONS SYSTEM OF THE MULTIPLE ACCESS TYPE BY CODES DISTRIBUTION USING CODES OF VARIABLE LENGTH |
US6163524A (en) * | 1998-10-19 | 2000-12-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Code allocation in CDMA |
US6208873B1 (en) * | 1998-11-23 | 2001-03-27 | Qualcomm Incorporated | Method and apparatus for transmitting reverse link power control signals based on the probability that the power control command is in error |
US6233231B1 (en) * | 1998-12-03 | 2001-05-15 | Motorola, Inc. | Data transmission within a spread-spectrum communication system |
US6400755B1 (en) * | 1999-04-23 | 2002-06-04 | Motorola, Inc. | Data transmission within a spread-spectrum communication system |
JP2001008262A (en) * | 1999-06-23 | 2001-01-12 | Hitachi Ltd | Dynamic code allocation code division multiple access communication method and base station for realizing the same |
US6301484B1 (en) * | 1999-08-31 | 2001-10-09 | Qualcomm Incorporated | Method and apparatus for remote activation of wireless device features using short message services (SMS) |
EP1100215A1 (en) * | 1999-11-09 | 2001-05-16 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Method, apparatus and computer program for code allocation for variable data rates in a CDMA system |
US6615038B1 (en) * | 2000-04-28 | 2003-09-02 | Samsung Electronics Co., Ltd. | System and method for automatically creating and updating a mobile station configuration database in a wireless network |
US7487112B2 (en) * | 2000-06-29 | 2009-02-03 | Barnes Jr Melvin L | System, method, and computer program product for providing location based services and mobile e-commerce |
US6711144B1 (en) | 2000-09-15 | 2004-03-23 | Airvana, Inc. | Multi-user communication of voice and data |
US6731618B1 (en) | 2000-10-20 | 2004-05-04 | Airvana, Inc. | Coding for multi-user communication |
US7277446B1 (en) | 2000-11-02 | 2007-10-02 | Airvana, Inc. | Communication of digital data over a wireless transmission medium |
US8755473B2 (en) * | 2001-01-29 | 2014-06-17 | Ipr Licensing, Inc. | Method and apparatus for detecting rapid changes in signaling path environment |
US6741862B2 (en) | 2001-02-07 | 2004-05-25 | Airvana, Inc. | Enhanced reverse-link rate control in wireless communication |
US8199696B2 (en) * | 2001-03-29 | 2012-06-12 | Qualcomm Incorporated | Method and apparatus for power control in a wireless communication system |
US8160020B2 (en) | 2001-06-25 | 2012-04-17 | Airvana Network Solutions, Inc. | Radio network control |
US8195187B2 (en) | 2001-06-25 | 2012-06-05 | Airvana Network Solutions, Inc. | Radio network control |
US6781999B2 (en) | 2001-07-23 | 2004-08-24 | Airvana, Inc. | Broadcasting and multicasting in wireless communication |
JP3478283B2 (en) * | 2001-07-31 | 2003-12-15 | 株式会社デンソー | Mobile communication terminal |
US7603127B2 (en) | 2001-10-12 | 2009-10-13 | Airvana, Inc. | Boosting a signal-to-interference ratio of a mobile station |
US6594501B2 (en) * | 2001-12-14 | 2003-07-15 | Qualcomm Incorporated | Systems and techniques for channel gain computations |
JP3840412B2 (en) * | 2001-12-28 | 2006-11-01 | 株式会社日立製作所 | Wireless terminal device |
US7299278B2 (en) | 2002-01-16 | 2007-11-20 | Airvana, Inc. | Managing network faults |
US8611919B2 (en) | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
WO2004027628A1 (en) * | 2002-09-17 | 2004-04-01 | Broadcom Corporation | System and method for access point (ap) aggregation and resiliency in a hybrid wired/wireless local area network |
US6850511B2 (en) * | 2002-10-15 | 2005-02-01 | Intech 21, Inc. | Timely organized ad hoc network and protocol for timely organized ad hoc network |
JP3742056B2 (en) * | 2002-12-19 | 2006-02-01 | 株式会社バッファロー | Wireless network access authentication technology |
US6791968B2 (en) * | 2002-10-24 | 2004-09-14 | Motorola, Inc. | Method and apparatus for wirelessly communicating different information streams |
US7200391B2 (en) | 2002-12-06 | 2007-04-03 | Airvana, Inc. | Capacity enhancement schemes for forward and reverse links of distributed cellular base stations |
CA2516580C (en) * | 2003-02-21 | 2011-01-25 | Research In Motion Limited | System and method of multiple-level control of electronic devices |
US7933250B2 (en) * | 2003-06-23 | 2011-04-26 | Qualcomm Incorporated | Code channel management in a wireless communications system |
US20050026640A1 (en) * | 2003-07-25 | 2005-02-03 | Pan Victor Hrid | Pseudorandom number offset assignment system and method |
US20070081144A1 (en) * | 2003-12-26 | 2007-04-12 | Nhk Spring Co., Ltd. | Discrimination medium and discrimination method for discriminating the same |
US7522549B2 (en) * | 2004-04-16 | 2009-04-21 | Broadcom Corporation | Registering access device multimedia content via a broadband access gateway |
US7843892B2 (en) | 2004-04-28 | 2010-11-30 | Airvana Network Solutions, Inc. | Reverse link power control |
US7983708B2 (en) | 2004-04-28 | 2011-07-19 | Airvana Network Solutions, Inc. | Reverse link power control |
US9876670B2 (en) | 2004-07-30 | 2018-01-23 | Commscope Technologies Llc | Local network node |
EP1779543B1 (en) | 2004-07-30 | 2012-04-25 | Andrew Richardson | Signal transmission method from a local network node |
WO2006010958A2 (en) | 2004-07-30 | 2006-02-02 | Andrew Richardson | Power control in a local network node (lnn) |
US7515643B2 (en) | 2004-09-30 | 2009-04-07 | Airvana, Inc. | Modulation for broadcasting from multiple transmitters |
US7558356B2 (en) | 2004-09-30 | 2009-07-07 | Airvana, Inc. | Providing global positioning system (GPS) timing signals to remote cellular base stations |
US7626926B2 (en) | 2004-12-09 | 2009-12-01 | Airvana, Inc. | Traffic management in a wireless data network |
US7729243B2 (en) * | 2005-01-18 | 2010-06-01 | Airvana, Inc. | Reverse link rate and stability control |
US7802297B2 (en) | 2005-02-07 | 2010-09-21 | Broadcom Corporation | Keyboard with built in display for user authentication |
US8942639B2 (en) * | 2005-03-15 | 2015-01-27 | Qualcomm Incorporated | Interference control in a wireless communication system |
US7831257B2 (en) | 2005-04-26 | 2010-11-09 | Airvana, Inc. | Measuring interference in radio networks |
US8099504B2 (en) | 2005-06-24 | 2012-01-17 | Airvana Network Solutions, Inc. | Preserving sessions in a wireless network |
US20060291420A1 (en) | 2005-06-27 | 2006-12-28 | Dennis Ng | Network-initiated dormant handoffs |
US8126477B2 (en) | 2005-07-07 | 2012-02-28 | Qualcomm Incorporated | Methods and devices for interworking of wireless wide area networks and wireless local area networks or wireless personal area networks |
US8111253B2 (en) | 2005-07-28 | 2012-02-07 | Airvana Network Solutions, Inc. | Controlling usage capacity in a radio access network |
US8295818B2 (en) | 2005-09-15 | 2012-10-23 | Airvana Network Solutions, Inc. | Broadcasting in wireless systems |
US7751835B2 (en) | 2005-10-04 | 2010-07-06 | Airvana, Inc. | Non-circular paging areas |
US7558588B2 (en) | 2005-11-18 | 2009-07-07 | Airvana, Inc. | Resource allocation in a radio access network |
US8145221B2 (en) | 2005-12-16 | 2012-03-27 | Airvana Network Solutions, Inc. | Radio network communication |
US20070140218A1 (en) | 2005-12-16 | 2007-06-21 | Nair Girish R | Managing backhaul connections in radio access networks |
US8094630B2 (en) | 2005-12-16 | 2012-01-10 | Airvana Network Solutions, Inc. | Radio frequency dragging prevention |
US8619702B2 (en) | 2005-12-16 | 2013-12-31 | Ericsson Evdo Inc. | Radio network control |
US8374122B2 (en) * | 2005-12-21 | 2013-02-12 | Cisco Technology, Inc. | System and method for integrated WiFi/WiMax neighbor AP discovery and AP advertisement |
US7801487B2 (en) | 2005-12-29 | 2010-09-21 | Airvana, Inc. | Detection of radio frequency interference in wireless communication systems |
US8582498B2 (en) * | 2006-03-07 | 2013-11-12 | Sandwave Ip, Llc | Service subscription using geophysical location |
US11477617B2 (en) | 2006-03-20 | 2022-10-18 | Ericsson Evdo Inc. | Unicasting and multicasting multimedia services |
US7672682B2 (en) | 2006-03-28 | 2010-03-02 | Airvana, Inc. | Managing page cycle periods of access terminals |
US20070230419A1 (en) | 2006-03-31 | 2007-10-04 | Sundar Raman | QoS signaling to support fairness |
US20070230392A1 (en) * | 2006-03-31 | 2007-10-04 | Adams Stewart L | Minimization of in-band noise in a WLAN network |
US8346220B2 (en) | 2006-03-31 | 2013-01-01 | Airvana Network Solutions, Inc. | Signaling for push-to-talk |
US20070242648A1 (en) | 2006-04-12 | 2007-10-18 | Deepak Garg | Managing dormant handoffs in radio access networks |
US7953040B2 (en) | 2006-04-19 | 2011-05-31 | Airvana Network Solutions, Inc. | Channel assignment in wireless communication |
US7689228B2 (en) * | 2006-05-15 | 2010-03-30 | Motorola, Inc. | Method and apparatus for providing in-band wireless backhaul |
US8085696B2 (en) | 2006-07-14 | 2011-12-27 | Airvana Networks Solutions, Inc. | Dynamic modification of route update protocols |
US8160629B2 (en) | 2006-09-07 | 2012-04-17 | Airvana, Corp. | Controlling reverse link interference in private access points for wireless networking |
US8688809B2 (en) | 2006-09-07 | 2014-04-01 | Airvana Lp | Provisioning private access points for wireless networking |
US8078165B2 (en) * | 2006-09-07 | 2011-12-13 | Airvana, Corp. | Configuring preferred user zone lists for private access points for wireless networking |
CN101536587A (en) | 2006-09-07 | 2009-09-16 | 爱尔瓦纳股份有限公司 | Configuring preferred user zone lists for private access points for wireless networking |
US8130686B2 (en) | 2006-11-20 | 2012-03-06 | Airvana Network Solutions, Inc. | Multicasting push-to-media content |
US8023439B2 (en) | 2006-11-20 | 2011-09-20 | Airvana Network Solutions, Inc. | Multicast flow distribution |
US7730189B2 (en) | 2006-11-22 | 2010-06-01 | Airvana, Inc. | Network-initiated session recovery |
US8639247B2 (en) | 2006-12-12 | 2014-01-28 | Ericsson Evdo Inc. | Access terminal session authentication |
US8532658B2 (en) | 2006-12-19 | 2013-09-10 | Airvana Network Solutions, Inc. | Neighbor list provision in a communication network |
US8457084B2 (en) | 2006-12-20 | 2013-06-04 | Airvana Llc | Communication group configuration in a network |
US8176327B2 (en) | 2006-12-27 | 2012-05-08 | Airvana, Corp. | Authentication protocol |
US8229498B2 (en) | 2006-12-28 | 2012-07-24 | Airvana, Corp. | Assigning code space to portable base stations |
US7926098B2 (en) | 2006-12-29 | 2011-04-12 | Airvana, Corp. | Handoff of a secure connection among gateways |
US8400989B2 (en) | 2007-04-13 | 2013-03-19 | Airvana Llc | Activating private access points for wireless networking |
US8781483B2 (en) | 2007-04-13 | 2014-07-15 | Airvana Lp | Controlling access to private access points for wireless networking |
US8543139B2 (en) | 2007-08-03 | 2013-09-24 | Airvana Llc | Distributed network |
US8265652B2 (en) | 2007-10-02 | 2012-09-11 | Ricoh Co., Ltd. | Geographic tagging of network access points |
-
2006
- 2006-12-28 US US11/617,298 patent/US8229498B2/en active Active
-
2007
- 2007-12-19 WO PCT/US2007/088112 patent/WO2008082985A1/en active Application Filing
-
2012
- 2012-07-23 US US13/555,830 patent/US8731574B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6597677B1 (en) * | 1998-07-16 | 2003-07-22 | Nec Corporation | Spreading code allocation method and system |
US20060203746A1 (en) * | 2005-03-10 | 2006-09-14 | Mark Maggenti | Method and apparatus for automatic configuration of wireless communication networks |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8078165B2 (en) | 2006-09-07 | 2011-12-13 | Airvana, Corp. | Configuring preferred user zone lists for private access points for wireless networking |
US8160629B2 (en) | 2006-09-07 | 2012-04-17 | Airvana, Corp. | Controlling reverse link interference in private access points for wireless networking |
US8688809B2 (en) | 2006-09-07 | 2014-04-01 | Airvana Lp | Provisioning private access points for wireless networking |
US8229498B2 (en) | 2006-12-28 | 2012-07-24 | Airvana, Corp. | Assigning code space to portable base stations |
US8731574B2 (en) | 2006-12-28 | 2014-05-20 | Airvana Lp | Assigning code space to portable base stations |
Also Published As
Publication number | Publication date |
---|---|
US20120302249A1 (en) | 2012-11-29 |
US8229498B2 (en) | 2012-07-24 |
US8731574B2 (en) | 2014-05-20 |
US20080159236A1 (en) | 2008-07-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8731574B2 (en) | Assigning code space to portable base stations | |
US8452299B2 (en) | Allocating code space to base stations | |
US8078165B2 (en) | Configuring preferred user zone lists for private access points for wireless networking | |
KR101465639B1 (en) | Methods and apparatus for determining and assigning spectrum for wireless communications | |
US9888393B2 (en) | Method and apparatus for automatic configuration of wireless communication networks | |
US7733833B2 (en) | Self-configuring, self-optimizing wireless local area network system | |
EP2213132B1 (en) | Methods of paging and locating a mobile station in a femto-cell system | |
CN105530711B (en) | Management server, base station, communication system, and communication method | |
EP1962531A2 (en) | Cellular mobile radio communication system | |
CN102625232A (en) | Additional data usable in apparatus positioning | |
US20180027545A1 (en) | Radio communication terminal and base station assignment method | |
CN110447268B (en) | Indication information transmission method and device | |
US20120058794A1 (en) | Systems and Methods for Enabling Non-Cognitive Radio Devices to Function as Cognitive Radios | |
CN103098520A (en) | Method and apparatus for transmitting available radio access possibilities in a communications area | |
US10237815B2 (en) | Radio communication terminal and frequency assignment method | |
KR101004947B1 (en) | Method and apparatus for spreading channel code selection | |
CN1386387A (en) | Method of forwarding channel assignments for one or more traffic channels | |
CN111972016A (en) | Positioning method, positioning device, terminal, network side equipment and storage medium | |
US20110223920A1 (en) | Wireless communication system and method for assigning physical-layer cell identities of base stations in wireless communication system | |
JP5141267B2 (en) | Cellular mobile radio communication system | |
KR101995160B1 (en) | Wireless communication system allocating spreading coefficient to end device to accommodate massive end devices | |
Bejarano-Luque et al. | A context-aware data-driven algorithm for small cell site selection in cellular networks | |
US20210219201A1 (en) | Base station management method, base station management apparatus and program | |
US20120008618A1 (en) | Methods and apparatus for timing synchronization using multiple different timing signal sources | |
US11464026B2 (en) | Scheduling virtual preambles for data source reporting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07871708 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07871708 Country of ref document: EP Kind code of ref document: A1 |