Automatic configuration of pico radio base station
Abstract
In the radio access network (24), the femto radio base station (28)f) Includes a resident receiver (54) that acquires the system information broadcast on the radio access network (24). At least some of the system information femto radio base stations (28) with adjacent data structures (59) containing information about adjacent cells.f) Is used to build. The adjacency data structure (59) is then used to build the adjacency list. Then its adjacency list is Femto Radio Base Station (28)f) To femto radio base station (28)f) Is sent to the user equipment unit (30) that receives the service. In some embodiments and embodiments, the femto radio base station (28)f) Reports the adjacent data structure to another network node (26, 100) other than its femto radio base station. Another node (26, 100) uses its adjacency data structure to build an adjacency list on those other nodes. In some embodiments and embodiments, the acquisition of system information involves scanning the macro coverage area around a femto radio base station to acquire cell identity information about the detected cell. In another embodiment and embodiment, the acquisition of the system information is a step of temporarily staying in the macro cell and at least one system information in the macro cell temporarily staying in order to acquire information about at least one adjacent cell. It may further include steps to use / browse blocks.

Term
Projected expiry 3 October 2026.
- Priority
- Filed
- Published
- Today
- Projected expiry
14 claims: 3 independent, 11 dependent
- 1無線アクセスネットワーク(24)を動作させる方法であって、 フェムト無線基地局(28 fj )において無線インタフェース(32)により、無線アクセスネットワーク(24)において同報されるシステム情報を取得する工程と、 前記フェムト無線基地局(28 fj )において、隣接セルの情報を有する隣接データ構造(59)を構築するために、前記システム情報の少なくとも一部を用いる工程と、 隣接リストを構築するために前記隣接データ構造(59)を用いる工程と、 前記フェムト無線基地局(28 fj )から前記フェムト無線基地局(28 fj )によりサービスを受けるユーザ機器ユニット(30)に前記隣接リストを送信する工程とを有することを特徴とする方法。
- 2前記フェムト無線基地局(28 fj )から前記フェムト無線基地局(28 fj )によりサービスを受けるユーザ機器ユニット(30)に前記隣接リストを送信する工程は、アイドルモードにある前記フェムト無線基地局によりサービスを受けるユーザ機器ユニットに前記隣接リストを同報する工程を有することを特徴とする請求項1に記載の方法。
- 3前記フェムト無線基地局(28 fj )から前記フェムト無線基地局(28 fj )によりサービスを受けるユーザ機器ユニット(30)に前記隣接リストを送信する工程は、アクティブモード或いは接続中モードにある前記フェムト無線基地局によりサービスを受けるユーザ機器ユニットに、モニタされたセットとして前記隣接リストを送信するために専用シグナリング接続を用いる工程を有することを特徴とする請求項1に記載の方法。
- 4前記フェムト無線基地局(28 fj )以外のネットワークノード(26,100)に前記隣接データ構造(59)を報告し、前記隣接データ構造(59)を用いて、前記他のノード(26,100)において隣接リストを構築する工程と、 前記隣接リストを前記フェムト無線基地局(28 fj )に転送する工程とをさらに有することを特徴とする請求項1に記載の方法。
- 5前記他のノードは無線ネットワーク制御局ノード(26)であることを特徴とする請求項4に記載の方法。
- 6前記システム情報を取得する工程は、前記フェムト無線基地局(28 fj )の周辺のマクロカバレッジ領域を走査し、検出されたセルについてのセルアイデンティティ情報を取得する工程を含み、 前記方法は、検出されたセル各々に関し、 前記隣接データ構造(59)に前記セルアイデンティティ情報を付加する工程と、 前記隣接データ構造(59)に付加されたセルアイデンティティを有する各セルに関し信号強度の測定を実行する工程と、 前記隣接データ構造(59)に前記信号強度の測定値を付加する工程とをさらに有することを特徴とする請求項1に記載の方法。
- 7前記システム情報を取得する工程はさらにマクロセルに一時的には留まる工程を有し、 前記方法は、 前記一時的に留まったマクロセルについてのセルアイデンティティ情報と信号強度の測定値とを前記隣接データ構造(59)に付加する工程と、 前記一時的に留まったマクロセルにおける少なくとも1つのシステム情報ブロックを用いて隣接セルについての情報を取得する工程と、 前記隣接セルについてのセルアイデンティティ情報と信号強度測定値とを前記隣接データ構造(59)に付加する工程とをさらに有することを特徴とする請求項6に記載の方法。
- 8前記フェムト無線基地局(28 fj )により構築された前記隣接データ構造(59)を前記隣接リストとして用いる工程をさらに有することを特徴とする請求項6に記載の方法。
- 9前記隣接リストを構築するために前記隣接データ構造(59)を用いる工程は、 前記隣接データ構造から少なくとも1つのセルをフィルタする工程と、 前記隣接データ構造の少なくとも1つのセルを置き換えセルで置換する工程と、 新しいセルを前記隣接データ構造(59)に追加する工程との内の少なくとも1つを有することを特徴とする請求項1に記載の方法。
- 10フェムト無線基地局(28 fj )であって、 検知されたセルについてのセルアイデンティティ情報を含むシステム情報を取得し、信号強度の測定を実行するために、前記フェムト無線基地局(28 fj )の周辺のマクロカバレッジ領域を走査するよう構成された常駐の無線受信機(54)と、 隣接セルについての情報を含む隣接データ構造(59)を構築するために、前記システム情報の少なくとも一部を使用するように構成された隣接データ構造(59)のビルダとを有し、 前記隣接データ構造(59)のビルダは、前記検知されたセルについてセルアイデンティティ情報と前記隣接データ構造(59)の各セルに関する信号強度の測定値を前記隣接データ構造(59)に含めるように構成されることを特徴とするフェムト無線基地局。
- 11前記常駐の無線受信機(54)はさらに、一時的にマクロセルに留まり、 (1)前記一時的に留まったマクロセルについてのセルアイデンティティと信号強度の測定値と、 (2)少なくとも1つの隣接セルについての情報を取得するための前記一時的に留まったマクロセルのシステム情報ブロックとを取得するように構成され、 前記隣接データ構造(59)のビルダはさらに、前記(1)と前記(2)とを用いて隣接データ構造(59)を構築するように構成されることを特徴とする請求項10に記載のフェムト無線基地局。
- 12フェムト無線基地局(28 fj )の前記隣接データ構造(59)のビルダによって構築された前記隣接データ構造(59)を、前記フェムト無線基地局(28 fj )によりサービスを受けるユーザ機器ユニット(30)への送信のために前記隣接リストとして使用するように構成されたリストマネージャ(57)をさらに有することを特徴とする請求項11に記載のフェムト無線基地局。
- 13無線アクセスネットワークであって、 フェムト無線基地局(28 fj )と、 隣接データ構造(59)を用いて隣接リストを構築するよう構成された、前記フェムト無線基地局(28 fj )からは別個のノード(26,100)とを有し、 前記フェムト無線基地局(28 fj )は、 無線アクセスネットワークにおいて同報されたシステム情報を取得するために構成された常駐の無線受信機(54)と、 前記フェムト無線基地局(28 fj )において、隣接セルについての情報を含む前記隣接データ構造(59)を構築するために前記システム情報の少なくとも一部を使用する手段を有することを特徴とする無線アクセスネットワーク。
- 14前記隣接データ構造(59)を用いて隣接リストを構築するよう構成されたノードは、無線ネットワーク制御局ノード(26)を有することを特徴とする請求項13に記載の無線アクセスネットワーク。
Independent claims14
58 paragraphs, as filed
The present invention relates to wireless communication, in particular to the operation of "femto" or "pico" radio base stations in radio access networks.
In a typical cellular radio system, a radio user equipment unit (UE) communicates with one or more core networks via a radio access network (RAN). The user equipment unit (UE) may be a mobile station such as a mobile phone (cellular phone) or a laptop with a mobile terminal, and thus at least one of the radio access network and voice and data. It may be a portable device, a pocket type, a handheld type, a computer built-in type, or an in-vehicle type mobile device that communicates with the mobile device. Alternatively, the wireless user equipment unit may be a fixed wireless device, eg, a fixed cellular device / terminal that is part of a wireless local loop or the like.
A radio access network (RAN) covers a geographic area that is divided into cell areas, each cell area being serviced by a base station. A cell is a geographic area for which radio coverage is provided by a radio base station device at a base station site. Each cell is identified by a unique identity, which is broadcast in that cell as system information. The base station communicates with the user equipment unit (UE) within the range of the base station via the air interface. In the radio access network, several base stations are typically a radio network (by landline or microwave) to a click control station (RNC) is connected. A radio network control station, sometimes referred to as a base station control station (BSC), manages and coordinates various activities of multiple base stations connected to it. Wireless network control stations are usually connected to one or more core networks. The core network has two service domains, and the RNC has interfaces with both of these domains.
One example of a radio access network is the Global Radio Access Network (UTRAN) of the Mobile Network Operator (UMTS). UMTS, in some respects, is a third-generation system built on wireless access technology developed in Europe known as GSM (Global System for Mobile communications). UTRAN is essentially a radio access network that provides a broadband code split multiple access (WCDMA) to a user equipment unit (UE). The 3rd Generation Partnership Project (3GPP) is tasked with furthering UTRAN and GSM-based radio access network technologies.
As those skilled in the art will understand, WCDMA technology allows simultaneous communication between a user equipment unit and multiple base stations due to the shared frequency band. Signals that occupy a shared frequency band are discriminated at the receiving station through diffuse spectrum CDMA waveform characteristics based on the use of fast pseudonoise (PN) codes. These high speed PN codes are used to modulate the signals transmitted from the base station and the user equipment unit (UE). A transmitting station that uses multiple PN codes (or PN codes with a time offset) produces signals that can be separated and demodulated by the receiving station. High-speed PN modulation also allows the receiving station to combine several different propagation paths of the transmitting signal to suitably generate a received signal from one transmitting station. Therefore, in CDMA, the user equipment unit (UE) does not need to switch frequencies when the connection is handed over from one cell to another. As a result, the destination cell can support the connection to its user equipment unit (UE) while the original cell continues to service the connection. Since the user equipment unit (UE) always keeps communicating through at least one cell during the handover, the call is not interrupted. For this reason there is the term "soft handover". In contrast to hard handover, soft handover is a "make-before-break" switching operation.
Other types of communication systems, including radio access networks, include: That is, Pan-European Digital Mobile Phone System (GSM), Improved Mobile Phone Service (AMPS) System, Narrow Band AMPS System (NAMPS), Total Access Communication System (TACS), Personal Digital Cellular (PDC) System, US Digital Cellular The (USDC) system and the Code Division Multiple Access (CDMA) system described in EIA / TIA IS-95.
UTRAN has several interesting interfaces. The interface between the wireless network control station (RNC) and the core network is called the "Iu" interface. The interface between the wireless network control station (RNC) and the base station (BS) is called the "Iub" interface. The interface between the user equipment unit (UE) and the base station is known as the "air interface", "wireless interface", or "Uu" interface. In some cases, the connection requires both a source and serving RNC (SRNC) and a target or drift RNC (DRNC), where the SRNC controls the connection, while one or more diversity legs of that connection. Is handled by DRNC. The transmission link between RNCs can be used to transmit control and data signals between the source RNC and the drift or target RNC, which may be a direct link or a logical link. The interface between radio network control stations (eg, between the serving RNC (SRNC) and the drift RNC (DRNC)) is called the "Iur" interface.
The Radio Network Control Station (RNC) controls UTRAN. In its role of control, RNC manages UTRAN's resources. Resources managed by the RNC include (especially) the downlink (DL) power transmitted by the base station, the uplink (UP) interference sensed by the base station, and the hardware installed at the base station.
Small radio base stations (RBS) that are referred to by some carriers as at least one of Femto RBS, Home RBS, Pico RBS, and Micro RBS in some environments. We are studying the possibility of providing home or small area WCDMA coverage for a limited number of users. According to such studies, small RBSs provide end users with normal WCDMA coverage (eg, for user equipment units (UEs)) and connect to RNCs using some sort of IP-based transmission. Will be done. The coverage area provided in this way is called a "femtocell" (to indicate that the coverage area is relatively small). Another term for femtocells includes "picocell" or "microcell", in contrast to macros, or macrocells covered by standard radio base stations (RBS).
One idea for IP-based transmission is to connect the home RBS to the RNC using fixed broadband access (such as xDSL, cable, etc.). Another option would be to use wireless broadband access (eg HSDPA and extended uplink, or WiMAX). Figure 5 shows in more detail these two different backhaul proposals. The first plan is labeled "xDSL Backhaul" and the second plan is labeled "WiMAX Backhaul".
In general, a typical WCDMA base station (Macro RBS) is installed and configured by a carrier employee, eg, an employee of a carrier that owns or maintains the Macro RBS and RNC nodes of a radio access network (RAN). .. As part of its installation, the macro RBS is manually set using operating parameters such as adjacent cell list information.
In contrast, femto RBSs are usually installed by end users rather than network operators. The end user can also move the femto RBS geographically around without the carrier having control over or attempting to control the relocation of the femto RBS. For such user-led relocation, operating parameters such as adjacent cell list information need to be processed automatically.
The adjacent cell list is a set of cells to be measured by the user equipment unit in idle mode. The adjacency list (also known as the "adjacency list") is typically included in the broadcast from a radio base station to an idle mode user equipment unit serviced by that radio base station. Adjacency lists are sent to user equipment units in active or connected mode (via a dedicated signaling connection to the user equipment units) in the form of a Monitored Set. A monitor set is a list of adjacent cells used by a user equipment unit for measurement in preparation for a possibility of handover from a cell commanded by a control node (eg, a wireless network control station node).
In other words, the base station broadcasts information about adjacent cells to be measured to determine in which cell the user equipment unit (UE) in idle mode should temporarily camp. In the case of active session, a list of cells in the monitor set is sent to the UE via a dedicated signaling connection (ie, not broadcast in this case), to which cell the measurement report should be made, and from the RNC. Gives an instruction to the UE as to which cell can be handed over at the time of the instruction.
As used herein, the terms "adjacency list" and "adjacency list" refer to both the broadcasted idle mode adjacency list and the active / connected mode adjacency list (ie, monitor set). used.
<p> Creating a list of such cells requires considerable operational and administrative (O & M) effort and support systems. The list should also be loaded into the network controller (eg at the RNC node) and associated with the correct base station. This also increases the chances of human error.</p><p> The processing of the adjacency list requires a great deal of work, so in the case of a pico (femto) base station, especially as mentioned earlier, the femto base station can be moved to a new location by the end user, so the amount of work required is It can be quite large. Traditionally, there is no automated way to automatically build adjacent cell lists for either the fixed broadband access proposal or some variants of the wireless broadband proposal.</p><p> Therefore, what is needed and the purpose here is to provide a new automatic mechanism for building adjacency lists for IP-connected femto radio base stations.</p>
<p> In a radio access network, a femto radio base station includes a resident receiver that acquires the system information broadcast in the radio access network (via a radio interface). At least a portion of that system information is used in a femto radio base station to build adjacent data structures containing information about adjacent cells. The adjacency data structure is then used to build the adjacency list. The adjacency list is then transmitted from the femto radio base station to the user equipment unit serviced by the femto radio base station.</p><p> In some embodiments and embodiments, the femto radio base station reports adjacent data structures to network nodes. The other node uses the adjacency data structure to build the adjacency list. The other node may be, for example, a radio network control station node or a back-end system node connected to the radio network control station node. The adjacency list constructed by the other node is transmitted to the femto radio base station, so that the femto radio base station then receives the adjacency list from the femto radio base station by the femto radio base station. To the unit, for example, its adjacency list is broadcast to an idle mode user equipment unit serviced by its femto radio base station, or a dedicated signaling connection to a specific user equipment unit in connected mode or active mode. It becomes possible to transmit in the sense that it is transmitted via.</p><p> In some embodiments and embodiments, the acquisition of system information involves scanning the macro coverage area around a femto radio base station to acquire cell identity information for the detected cell. For each detected cell, cell identity information is added to the adjacency data structure. In addition, the resident receiver of the femto radio base station performs a signal strength measurement for each cell with identity information added to the adjacent data structure. Signal strength measurements for each such cell are added to the adjacent data structure.</p><p> In another embodiment and embodiment, acquisition of system information further comprises staying at least temporarily in a macro cell detected during a scan of macro coverage. The cell identity information of the temporarily retained macrocell and the measured signal strength are added to the adjacent data structure. In addition, at least one system information block in the temporarily staying macro cell is browsed / used to retrieve information about at least one adjacent cell. Cell identity information and signal strength measurements for adjacent cells are also added to the adjacent data structure. By obtaining the cell identity and signal strength measurements of an adjacent cell for idle mode from the system information block of the temporarily retained macrocell, the adjacent data does not need to be scanned through the entire spectrum for possible cells. Structure candidates can be selected. Further, if desired, the adjacency data structure constructed by the femto radio base station can be used as an adjacency list to be transmitted to the user equipment unit serviced by the femto radio base station.</p><p> In some embodiments and embodiments, using an adjacency data structure to build an adjacency list involves at least one of the following: That is, (1) filtering at least one cell from the adjacent data structure, (2) replacing at least one cell in the adjacent data structure with a replacement cell, and (3) adding a new cell to the adjacent data structure. That is. At least one of cell filters, replacements, and additions may be transformed according to internal policies.</p><p> In one of its aspects, the technique relates to femto radio base stations, including resident radio receivers. The resident radio receiver should scan the macro coverage area around the femto radio base station to obtain system information, including cell identity information about the detected cell, and perform signal strength measurements. It is configured. Femto radio base stations also include a builder of adjacent data structures that is configured to use at least a portion of the system information to build an adjacent data structure that contains information about adjacent cells. The builder of the adjacent data structure is configured to include the cell identity information for the detected cell and the measured signal strength for each cell in the adjacent data structure in the adjacent data structure.</p><p> In one aspect, the technique relates to a femto radio base station configured to have a resident radio receiver. The resident radio receiver not only scans the macro coverage area around the femto radio base station to acquire system information, but also has a role of staying at least temporarily in the macro cell detected during scanning. As a result of staying in the macrocell at least temporarily, the femto radio base station also obtains (1) measurements of the cell identity and signal strength of the macrocell that stays temporarily, and (2) information about at least one adjacent cell. It is configured to get the system information block of the temporarily stayed macrocell for. Femto radio base stations also include a builder of adjacency data structures configured to use (1) and (2) to construct adjacency data structures. Optionally, the femto radio base station also uses the adjacency data structure itself constructed by the builder of the adjacency data structure of the femto radio base station as an adjacency list to send to the user equipment unit serviced by the femto radio base station. It may include a list manager configured to do so.</p><p> In that other aspect, the technique relates to a radio access network (RAN) that includes both a femto radio base station and another node. A femto radio base station is a resident radio receiver for acquiring system information broadcast in a radio access network, and system information for constructing an adjacency data structure containing information about adjacent cells in the femto radio base station. Includes means of using at least a portion of. Another node is configured to use the adjacency data structure to build its adjacency list. The other node may be, for example, a wireless network control station node or a back-end system connected to that wireless network control station node.</p><p> The aforementioned and other objectives, features, and advantages of the present invention will become apparent from the following more specific description of suitable embodiments, as shown in the accompanying drawings. In that drawing, reference characters shall refer to the same part through various figures. The drawings do not necessarily correspond to the actual size, but instead the emphasis is on illustrating the principles of the invention.</p>
In the following description, for the purpose of explanation, but not for the purpose of limitation, specific details of a specific architecture, interface, technology, etc. will be described to provide a complete understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention can be practiced in other embodiments that differ from these specific details. That is, although not explicitly explained or illustrated here, those skilled in the art will be able to implement the principles of the present invention and consider various configurations within their scope and spirit. In some examples, detailed descriptions of known devices, circuits, and methods are omitted so that the description of the present invention is not obscured by unnecessary details. All descriptions herein referring to the principles, aspects, and examples of the invention and examples thereof are intended to include both structures and functions equivalent thereto. Moreover, such equivalents may include not only currently known equivalents but also future developed equivalents, such as any developed element that performs the same function regardless of its structure. Intended.
Thus, for example, those skilled in the art will appreciate that the block diagram here can represent a conceptual diagram showing an exemplary circuit that embodies the principles of this technique. Similarly, all flowcharts, state transition diagrams, pseudo-codes, etc. are substantially represented in computer-readable media and executed by such computers or processors, whether or not they are specified. It will be recognized that it represents various processes.
The functions of various elements, including functional blocks labeled "processors" or "controllers (control stations / devices)", are not only dedicated hardware but also hardware that can execute software associated with appropriate software. May be provided by use of. When provided by a processor, the functionality may be provided by a single dedicated processor, a single shared processor, or a plurality of individual processors, some of which are shared or decentralized. Furthermore, even when the term "processor" or "controller (control station / device)" is explicitly used, it should not be construed as referring only to hardware capable of executing software, and digital signal processing devices. (DSP) hardware, read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile memory may be included, and are not limited thereto.
Although not limited to this, the present invention will be described by taking the communication system 10 shown in FIG. 1A as an example. The communication system 10 is connected to the core network 20. Communication system 10 includes a radio access network 24. The radio access network 24 includes one or more radio network control station nodes (RNCs) 26 and one or more radio base stations (BS) 28. As an example, FIG. 1A specifically shows two, ie, the first wireless network control station 26.<sub>1</sub>And the second wireless network control station 26<sub>2</sub>Also, the macro radio base station (Fig. 1A shows the macro radio base station 28).<sub>M</sub>Only one is shown) and multiple femto radio base stations 28<sub>f1</sub>、28<sub>f2</sub>、......28<sub>fx</sub>Both are shown. Macro radio base station 28<sub>M</sub>Is macrocell C<sub>M</sub>To serve. Femto radio base station 28<sub>f1</sub>、28<sub>f2</sub>、......28<sub>fx</sub>Is each femtocell C<sub>f1</sub>, C<sub>f2</sub>, ...... C<sub>fx</sub>To serve. As a person skilled in the art understands, radio base stations are usually installed inside cells (for example, in the center) served by each radio base station, but for the sake of clarity, the macro in Figure 1A Radio base stations and femto radio base stations are not so, but are indicated by double-headed arrows in association with their respective cells. Femtocell C<sub>f1</sub>, C<sub>f2</sub>, ...... C<sub>fx</sub>At least some of the geographically macrocells C<sub>M</sub>Overlaps or is included.
As used herein, "femto radio base station" also has the meaning of a pico radio base station or micro radio base station and serves a femto cell (or pico cell or micro cell). Femtocells usually overlap with one or more macrocells and serve smaller geographic areas or subscriber customer bases than macrocells. The techniques described here have special advantages for femto radio base stations, which radios have no control over installation or relocation by the owner / carrier of the radio access network. You can at least do one of the installations and relocations within the access network. In other words, a non-network carrier entity (femto operator) can acquire a femto radio base station, and the femto radio base station can be installed according to the preference of the femto operator. In this regard, Figure 1A shows such a femto radio base station 28, which may have recently been moved or activated by a femto operator.<sub>fj</sub>Is shown unintentionally. Femto radio base station 28<sub>fj</sub>Is its femtocell C<sub>fj</sub>Is macrocell C<sub>M</sub>It is geographically installed or arranged so as to overlap with.
A user equipment unit (UE), such as the user equipment unit (UE) 30 shown in FIG. 1A, communicates with one or more cells or one or more base stations (BS) 28 via radio or air interface 32. .. The user equipment unit may be a mobile station, such as a mobile phone (cellular phone) or a laptop with a mobile terminal, and thus communicates at least one of the radio access network with voice and data. For example, it may be a portable type, a pocket type, a handheld type, a built-in computer type, or an in-vehicle type mobile device.
The radio access network 24 shown in FIG. 1A may be, but is not limited to, a UMTS terrestrial radio access network (UTRAN) as an example. In UTRAN, radio access is preferably based on Broadband Code Division Multiple Access (WCDMA), where individual radio channels are assigned using CDMA spread codes. Of course, another access method may be used. Considering that nodes 26 and 28 are examples of UTRAN, they are called a radio network control station node and a radio base station node, respectively. It should be noted that the terms radio network control station and radio base station should also be understood to include nodes with similar functionality for different types of radio access networks. Other types of communication systems, including those other types of radio access networks, include: That is, Pan-European Digital Mobile Phone System (GSM), Improved Mobile Phone Service (AMPS) System, Narrow Band AMPS System (NAMPS), Total Access Communication System (TACS), Personal Digital Cellular (PDC) System, US Digital Cellular The (USDC) system and the Code Division Multiple Access (CDMA) system described in EIA / TIA IS-95.
The radio access network 24 is connected to the core network 20 via an interface that is similar to the Iu interface in UTRAN. Network 20 in Figure 1A includes, among other things, a mobile exchange center (MSC) node, a gateway MSC (GMSC) node, a gateway general line radio service (GPRS) support node (GGSN), and a serving GPRS support node (SGSN). A circuit-switched (CS) network or a packet-switched (PS) network can connect to the core network 20.
For simplicity, the radio access network 24 in Figure 1A shows only two RNC nodes 26. Multiple radio network control station nodes (RNCs) may be provided, with each RNC 26 connected to one or more base stations (BS) 28. It will be recognized that a different number of base stations than shown in Figure 1A can be serviced by the wireless network control station 26, and the RNC does not need to serve the same number of base stations. In addition, the RNC can be connected to one or more other RNCs in the radio access network 24 via the Iur interface. Radio Network Control Station Node (RNC) 26 is a Macro Radio Base Station 28 via Interface Iub<sub>M</sub>Communicate with. In addition, one of ordinary skill in the art will recognize that base stations such as macro radio base station 28 are also referred to in this art as radio base stations, node B, or node B. Each of the wireless interface 32, the Iu interface, the Iur interface, and the Iub interface is shown by the dotted line in FIG. 1A.
Figure 1A shows the femto radio base station 28.<sub>fj</sub>Radio Access Network (RAN), eg, its radio network control station node (eg, radio network control station node 26 in a specifically illustrated scenario).<sub>1</sub>) Can be seen as an illustration of general access. Femto radio base station 28 by "general access"<sub>fj</sub>It means that the access that can be performed in the above may be wideband fixed access or wideband mobile access (for example, WiMAX) as described above. After all, in Figure 1A, the femto radio base station 28<sub>fj</sub>Femto radio base station including 28<sub>f</sub>Is connected to the communication network 38. An example of such a communication network is IP network 38.
In contrast, FIG. 1B shows the femto radio base station 28.<sub>fj</sub>Shows a scenario of wideband wireless access or mobile access for. Therefore, Figure 1B shows the femto radio base station 28.<sub>fj</sub>Access to the radio access network 24 is a macro radio base station (eg, macro RBS28 in the scenario shown)<sub>M</sub>) Is used. As described above, wireless or mobile broadband access can be achieved using, for example, HSDPA and extended uplinks, or WiMAX. Unless specifically excluded in the context, aspects of the technique described herein are applicable to all types of access, including wideband fixed access and wideband mobile access (eg, wideband wireless access).
Figure 2A shows a typical femto radio base station 28, which is the first example.<sub>f</sub>The basic, selective, and representative components of. One or more femto radio base stations 28<sub>f1</sub>、28<sub>f2</sub>、......28<sub>fx</sub>Is a typical femto radio base station 28 in Figure 2A.<sub>f</sub>Can take the form of. Femto radio base station 28 in Figure 2A<sub>f</sub>Includes an IP interface unit 50, one or more radio frequency transceivers 52, a radio frequency receiver 54, a data processing system, a data processing unit, or a data processing unit 56, although there are other components not shown. .. FIG. 2A shows the data processing system 56 as including a controller or processor that includes a UE measurement list manager 57 and an adjacency data structure builder 58A. The adjacency data structure builder 58A is configured and configured to build the adjacency data structure 59A entitled "All_Cells_Found" in the description in Figure 2A. It will be appreciated that the UE Measurement List Manager 57 and the Adjacent Data Structure Builder 58A can take different forms, eg, one or more independent processors or controllers.
Figure 2B shows another example of a femto radio base station 28.<sub>f</sub>The basic, selective, and representative components of. Femto radio base station 28 in Figure 2B<sub>f</sub>Many of the elements of are, as the corresponding reference numbers indicate, the femto radio base station 28 in Figure 2A.<sub>f</sub>Same or at least similar to that of. Femto radio base station 28 in Figure 2B<sub>f</sub>Adjacent data structure builder and adjacency data structure are adjacent data structure builder 58B and adjacency data, respectively, given the fact that the adjacency data structure builder is configured to build its adjacency data structure in a somewhat different way. It is depicted as structure 59B.
Femto radio base station 28 in Figure 2A<sub>f</sub>And the femto radio base station 28 in Figure 2B<sub>f</sub>For both with and the radio frequency transceiver 52, the femto radio base station 28<sub>f</sub>Used for wireless or air interface communication with user equipment units (UEs) in femtocells serviced by. The number of radio frequency transceivers 52 depends on a variety of factors, including the capacity of the femto radio base station to handle mobile connections.
Receiver 54 is a femto radio base station 28<sub>f</sub>The system information that is resident in the radio access network 24 and is broadcast on the radio access network 24 is provided by the femto radio base station 28.<sub>f</sub>In, it has a role of acquiring via the wireless interface 32. When the radio access network (RAN) is a WCDMA network, the receiver 54 is a WCDMA receiver for both the embodiment of FIG. 2A and the embodiment of FIG. 2B. In this sense, in both embodiments, the receiver 54 may take the form of a user equipment unit (UE). That is, the femto radio base station 28 in FIG. 2A.<sub>f</sub>In, the receiver 54 may be a femto RBS-based user equipment unit (UE) capable of scanning the surrounding macro coverage.
FIG. 3A shows the basic, selective, and representative components of the wireless network control station node 26 of the first example. The wireless network control station node 26 connects the wireless network control station node 26 to the core network 20 via the Iu interface 70, and the wireless network control station node 26 to another wireless network control station via the Iur interface. Interface unit 72, wireless network control station node 26 to one or more macro radio base stations 28 via Iub interface<sub>M</sub>One or more interface units 74 connected to each, and one or more femto radio base stations 28 with wireless network control station nodes 26<sub>f1</sub>、28<sub>f2</sub>、......28<sub>fx</sub>It can include several interface units, such as one or more interface units 76 that connect to each. RNC26 and Femto Radio Base Station 28<sub>m</sub>The connection to and from is feasible via the communication network 38, for example, Internet Protocol (IP) based forwarding is available. RNC26 and macro radio base station 28<sub>M</sub>Connections to and from are available, for example, at least one of Internet Protocol (IP) -based and ATM-based transfers.
In addition to the interface unit, the wireless network control station node 26 includes a data processing system, a data processing unit, or a data processing unit 80 as well as many not shown components. As shown in FIG. 3, in an example of a non-limiting embodiment, the data processing system 80 of the wireless network control station node 26 is a control unit (eg, controller 82), a handover unit 84, (eg, connection diversity). Includes combiner and splitter unit 86 (involved in leg processing), and adjacency list builder 90.
Adjacency list builder 90 femto radio base station 28 with adjacency data structure<sub>f</sub>Received from and configured to build an adjacency list. Examples of functions drawn by the individual functional units that make up the adjacency list builder 90 include the RBS data structure receiver 92, the data structure modifier 94, and the adjacency list exporter 96. The data structure modifier 94 is shown as optionally including various additional functions or units such as filter unit 97, policy unit 98, and addition unit 99. It will be appreciated that the adjacency list builder 90 and any of its illustrated functional units may take other forms, such as one or more independent processors or controllers.
FIG. 3B illustrates another example wireless network control station node 26. Many of the elements of the wireless network control station node 26 in FIG. 3B are the same as or at least similar to those of the wireless network control station node 26 in FIG. 3A, as the corresponding reference numbers indicate. However, the wireless network control station node 26 of FIG. 3B is connected to the wireless network control station node 26 of FIG. 3B, for example, as the function of the adjacency list builder is illustrated by the adjacency list builder node 100 of FIG. 3B. It differs in the fact that it is distributed across the backend system. The radio network control station node 26 in FIG. 3B includes an adjacency list handler 102, which interfaces with the adjacency list builder node 100 and manages the transfer of adjacency lists built by the adjacency list builder node 100 to the femto radio base station. To do. Examples of functions drawn by the individual functional units that make up the Adjacency List Builder node 100 in a manner similar to the Adjacency List Builder 90 include RBS Data Structure Receiver 192, Data Structure Modifier 194, and Adjacency List Exporter 196. Including, the data structure modifier 194 optionally includes various additional functions or units such as filter unit 197, policy unit 198, and addition unit 199. It will also be appreciated that the adjacency list builder node 100 and any of its illustrated functional units may take other forms, such as one or more independent processors or controllers.
FIG. 4A shows an example of the steps and operations performed in the operation mode of the first example. The mode of operation of the first example is a common access type and can therefore include steps and operations performed for one or both of fixed and wireless broadband access. Examples of steps and operations in Figure 4A and other similar figures are, for example, femto radio base station 28.<sub>fj</sub>Occurs when is just started by a femto operator.
Step 4A-1 of FIG. 4A shows that the resident receiver 54 acquires the system information broadcast on the radio access network 24 (via the radio interface 32). In particular, step 4A-1 is the femto radio base station 28.<sub>f</sub>The receiver 54 of the is shown to scan the macro coverage area around the femto radio base station to obtain cell identity information for the detected cell. In one example of the WCDMA embodiment, receiver 54 reads the associated scrambled code, decodes the master information block (MIB) to find the PLMN-ID, and system information block 1 (SIB1) to find the LAC. Reads and decodes, and then reads and decodes System Information Block 3 (SIB3) to find the cell identity system information. As step 4A-2, the adjacency data structure builder 58 adds the detected cell (using the cell identifier) to the adjacency data structure 59. For each detected cell, cell identification information is added to the adjacent data structure 59.
Step 4 As 3A-3, Femto Radio Base Station 28<sub>f</sub>Resident receiver 54 performs a signal strength measurement for each cell with the cell identity added to the adjacent data structure 59. Step 4 As part of A-3, add signal strength measurements for each such cell to the adjacent data structure. In other words, the receiver 54 also performs a measurement of the signal strength of each cell listed in the adjacent data structure 59 (All_Cells_Found). After the completion of the adjacent data structure 59, the femto radio base station 28<sub>f</sub>Report these results to wireless network control station node 26 (in the form of adjacent data structures 59), preferably using the IP-based connection provided by IP network 38. FIG. 4A shows reporting the adjacency data structure 59 to the wireless network control station node 26 as step 4A-4.
Upon receiving the adjacency data structure 59, the radio network control station node 26 calls the adjacency list builder 90 as appropriate. The construction of the adjacency list is commonly depicted as Step 4A-5 in Figure 4A. The RBS data structure receiver 92 of the adjacency list builder 90 is essentially a femto radio base station 28.<sub>f</sub>The adjacent data structure 59 received from is received and analyzed. Adjacency list builder 90 builds an adjacency list, also known as Femto_RBS_SI_Neiboring_List. In doing so, the adjacency list builder 90 may call the data structure modifier 94. For example, filter unit 97 of data structure modifier 94 optionally or selectively applies filtering to All_Cells_Found information (eg, adjacent data structure 59) received from femto RBS based on some internal policy. You can prevent some cells from being included in the Femto_RBS_SI_Neiboring_List. When building Femto_RBS_SI_Neiboring_List, policy unit 98 could be called to replace some cells with other cells based on the internal policy. A third option would be to include an entirely new cell in the Femto_RBS_SI_Neiboring_List (eg added by addition unit 99) based on internal policy and All_Cells_Found information.
These policies realized by the data structure modifier 94 may be set by the network operator, for example, in RBS or RNC at the node that constructs the adjacent cell list according to the embodiment. These policies could also be defined on a central network node (eg RNC or O & M node) and then downloaded to the RBS to which the policy applies. One example of a policy would be not to include cells whose measured signal strength does not reach a given threshold. Another policy would be to blacklist these cells, for example, depending on which PLMN the cells belong to (indicated by the PLMN-ID). Yet another policy would be to never include certain cells that the network operator has set in the "blacklist". Yet another policy would be to have a mapping table and replace it with macrocell-Z (eg GSM cell) whenever macrocell-X (eg UMTS cell) is reported, for example. ..
Step 4 After the adjacency list construction in A-5 is complete, the adjacency list exporter 96 becomes the femto radio base station 28.<sub>f</sub>At least either format the adjacency list or prepare the list for sending to. Step 4A-6 in Figure 4A is from wireless network control station node 26 to femto radio base station 28.<sub>f</sub>Indicates that an adjacency list will be sent to. Step 4 A-7 is the wireless network control station node 26<sub>1</sub>Indicates that the adjacency list received from is stored in the UE measurement list manager 57. Step 4 A-8 then Femto Radio Base Station 28<sub>f</sub>Indicates that the adjacency list is transmitted from the user equipment unit 30 serviced by the femto radio base station. In one embodiment of Step 4A-8, the adjacency list is the femto radio base station 28.<sub>f</sub>Broadcast to all user equipment units in idle mode that are serviced by. Step 4 In another embodiment of A-8, the adjacency list is sent in the form of a monitor set to a particular user equipment unit in connected or active mode via a dedicated signaling connection.
As an aside, for example, the UE Measurement List Manager 57 may be used to store and manage notifications for lists other than adjacency lists that include monitor sets.
In the example of the femto radio base station shown in FIG. 2A, the femto radio base station 28 of FIG. 2A<sub>f</sub>The adjacency data structure 59A constructed by the adjacency data structure builder 58A is drawn to include a list of "cells to be scanned" as the receiver 54 of the is traversing the surrounding coverage area.
FIG. 4B shows an example of a step and an operation performed in the operation mode of the second example. In the mode of operation depicted in FIG. 4B, the sequence of steps including steps 4A-1 through 4A-3 of the mode of FIG. 4A is augmented by the sequence of steps including steps 4B-1 through 4B-3. ..
In step 4B-1 of FIG. 4B, the resident receiver 54 stays at least temporarily in the macrocell found during the scan of step 4A-1 and broadcasts the system information on the radio access network 24 (radio interface 32). Indicates to get (via). As step 4B-2, cell identity information and signal strength measurements for the temporarily retained macrocell are added to adjacent data structure 59B if they are no longer included in adjacent data structure 59B. In addition, as step 4B-3, at least one system information block in the temporarily staying macro cell is browsed / used to retrieve information about at least one adjacent cell. Cell identity information and signal strength measurements for at least one adjacent cell are also added to the adjacent data structure as part of Step 4B-3.
To explain the above in more detail, the femto radio base station 28<sub>f</sub>When the receiver 54 (UE) of the is successfully temporarily staying in the macro cell, if such a thing no longer exists in the adjacent data structure 59B, the measured value of the cell temporarily staying at that time. And the identity are also included in the adjacent data structure 59B (as step 4B-2). The receiver 54 (UE) can also read and decode the system information block 11 (SIB11) of the cell at that time. SIB11 contains information about adjacent cells in idle mode and can also be used to select candidates for All_Cells_Found instead of scanning the entire spectrum for possible cells.
Steps 4A through 4A-8 of the example mode of FIG. 4B are essentially the same as or similar to the corresponding steps 4A-4 through 4A-8 of the mode of FIG. 4A. These steps include reporting adjacency data structure 59B to wireless network control station node 26 as step 4A-4, building the adjacency list commonly depicted by step 4A-5, and wireless network as step 4A-6. Control station node 26 to femto radio base station 28<sub>f</sub>Send adjacency list to, step 4A-7 as wireless network control station node 26<sub>1</sub>Memory in the UE measurement list manager 57 of the adjacency list received from, and the femto radio base station 28 as step 4A-8.<sub>f</sub>Includes subsequent transmission of the adjacency list from to the user equipment unit 30 serviced by the femto radio base station.
In the embodiment of the femto radio base station shown in FIG. 2B, the femto radio base station 28 of FIG. 2B<sub>f</sub>The receiver 54 of the It is depicted as containing a list of "cells" from system information. Therefore, the adjacency data structure constructed in the mode of FIG. 4B is a concatenation of an entry as shown in adjacency data structure 59A and an entry shown in adjacency data structure 59B of FIG. 2B.
It is also necessary to scan the entire spectrum of possible cells for candidates for adjacent data structures by obtaining the cell identity of the adjacent cell in idle mode from the system information block of the macrocell that temporarily stayed in the mode manner shown in Figure 4B. Can be selected without. Signal strength measurements are then performed as a separate step for these cells.
In some of the embodiments and embodiments described above, the femto radio base station reports adjacent data structures to another network node other than the femto radio base station. Those other nodes use their adjacency data structures to build adjacency lists on those nodes. In the embodiments already shown, their other node is a wireless network control station node.
FIG. 4C shows an example of the steps and operations performed in the operation mode of the third example. In the mode shown in Figure 4C, another node that uses the adjacency data structure to build the adjacency list is the radio network control station node 26.<sub>1</sub>Instead, it is the adjacency list builder node 100 as shown in Figure 3B. The adjacency list builder node 100 may be, for example, a back-end system node connected to a wireless network control station node. The preparatory steps of FIG. 4C may be the first 4 steps of the mode of FIG. 4A or the first 7 steps of the mode of FIG. 4B. For simplicity, FIG. 4C shows that the first step is the first three steps of the mode of FIG. 4A, eg, steps 4A-1 to 4A-3. As step 4A-4, the adjacency data structure 59 is received by the wireless network control station node 26. However, in step 4C-4, the radio network control station (RNC) delegates or transmits the adjacency data structure 59 to the adjacency list builder node 100. The adjacency list builder node 100 uses the adjacency data structure 59 to build the adjacency list, as depicted in step 4C-5 of Figure 4C. When the adjacency list is complete, the adjacency list builder node 100 returns the completed adjacency list to the wireless network control station node 26 as step 4C-6, where the wireless network control station node 26 completes the adjacency list as step 4A-6. List Femto Radio Base Station 28<sub>f</sub>Tell to. Wireless network control station node 26<sub>1</sub>The storage of the adjacency list received from the UE measurement list manager 57 is performed as step 4A-7, and then the femto radio base station transmission 28<sub>f</sub>Transmission of the adjacency list from to to the user equipment unit 30 serviced by the femto radio base station is performed as step 4A-8.
In the embodiments and embodiments of FIGS. 4A-4C discussed above, an adjacency data structure 59, or any modification or modification thereof, from a femto radio base station to allow another node to build an adjacency list. Sent to the node. The other node then returns the adjacency list to the femto radio base station. An interface and an appropriate protocol are configured to transfer the adjacency data structure, and the adjacency list is transferred between the femto radio base station and at least one other node. In some embodiments, adjacency data structures and adjacency lists are transmitted via an extended Iub interface (eg, "lub +" interface). The Iub + interface is similar to the traditional Iub interface that exists between the radio base station node and the radio network control station node, but its protocol is required to achieve adjacency data structure and adjacency list transfer. It has been added or modified to include information elements or other features. Alternatively, it has been tuned or configured to facilitate the transfer of adjacency data structures and adjacency lists between a femto radio base station and another network node or entity without the use of an extended version of the Iub interface and protocol. An entirely new interface and protocol may be used.
According to at least one embodiment and embodiment of the technique, it is not always necessary to build the adjacency list with nodes other than the femto radio base station. In this regard, FIG. 4D shows an example of the steps and actions performed in the operation mode of the fourth example. The mode in Figure 4D is also the femto radio base station 28 in Figure 2C.<sub>f</sub>Also indicated by.
The first six steps of the mode of FIG. 4D are the same as those of the mode of FIG. 4B, which are steps 4A-1 to 4A-3 and steps 4B-1 to 4B-3. However, Femto Radio Base Station 28<sub>f</sub>Instead of sending the adjacency data structure 59B constructed by the other node to transform or configure the adjacency list by that other node, the femto radio base station 28, as depicted in step 4D-5 of Figure 4D.<sub>f</sub>Uses the adjacency data structure 59B it just built as an adjacency list. In this regard, FIG. 3C also shows in step 4D-5 that the adjacency data structure 59B constructed by the adjacency data structure builder 58B is used or sent to the UE measurement list manager 57. Step 4 D-8 is the femto radio base station 28<sub>f</sub>The subsequent transfer of the adjacency list (obtained from the adjacency data structure 59B) from to the user equipment unit 30 serviced by the femto radio base station is illustrated.
Therefore, as shown in the mode of FIG. 4D, if desired, the adjacency data structure constructed by the femto radio base station can be used as an adjacency list to be transferred to the user equipment unit serviced by the femto radio base station. Good. The above principles / methods are also applicable to wireless technologies other than WCDMA. WCDMA is shown as an example only, and other suitable technologies include, but are not limited to, GSM, CDMA, WiMAX, and the like. This technique has special implications for favorable systems and scenarios as described above, but may be applicable in other cases as well as in other networks.
Although various examples have been shown and described in detail, the scope of claims is not limited to any particular embodiment or example. None of the above statements should be read as suggesting that any particular element, step, scope, or function is essential. The present invention is not limited to the disclosed examples, but rather is intended to cover various improvements and equivalent configurations.
<figref num="1A">The selected femto radio base station illustrates an embodiment of a communication system including a radio access network (RAN) connected by general access transmission.</figref><figref num="1B">The selected femto radio base station illustrates an embodiment of a communication system including a radio access network (RAN) connected by mobile broadband access transmission.</figref><figref num="2A">It is the schematic of the Example of the femto radio base station using general access transmission.</figref><figref num="2B">It is the schematic of the Example of the femto radio base station using the radio broadband access transmission.</figref><figref num="2C">It is a schematic diagram of an embodiment of a femto radio base station that uses radio broadband access transmission and uses an adjacency data structure created by itself as an adjacency list.</figref><figref num="3A">It is the schematic of the radio network control station (RNC) node of the 1st Example.</figref><figref num="3B">It is the schematic of the radio network control station (RNC) node of the 2nd Example.</figref><figref num="4A">An example of a step and an operation executed in the operation mode of the first example is illustrated.</figref><figref num="4B">An example of a step and an operation executed in the operation mode of the second example is illustrated.</figref><figref num="4C">An example of a step and an operation executed in the operation mode of the third example is illustrated.</figref><figref num="4D">An example of a step and an operation executed in the operation mode of the fourth example is illustrated.</figref><figref num="5">It is a figure which shows two different backhaul proposals.</figref>
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8483719B2 | Cited by | United States of America | Applicant |
| JP2011525329A | Cited by | Japan | Examiner |
| JP2012507910A | Cited by | Japan | Search report |
| JP2013519267A | Cited by | Japan | Search report |
| JP2010529750A | Cited by | Japan | Examiner |
| US10051620B2 | Cited by | United States of America | Applicant |
| JP2014027603A | Cited by | Japan | Examiner |
| JP2014014099A | Cited by | Japan | Examiner |
| JP2013539628A | Cited by | Japan | Search report |
| JP2013176047A | Cited by | Japan | Search report |
| US9414229B2 | Cited by | United States of America | Applicant |
| US8532655B2 | Cited by | United States of America | Applicant |
| JP2014042294A | Cited by | Japan | Search report |
| US8737295B2 | Cited by | United States of America | Applicant |
| JP2011504352A | Cited by | Japan | Search report |
| JP2011504059A | Cited by | Japan | Examiner |
| JP2010529732A | Cited by | Japan | Examiner |
| JP2010109612A | Cited by | Japan | Search report |
| US9414228B2 | Cited by | United States of America | Applicant |
| US8467304B2 | Cited by | United States of America | Applicant |
| WO2011125934A1 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| JP2011504674A | Cited by | Japan | Examiner |
| JP2013066186A | Cited by | Japan | Search report |
| JP2013519267A | Cited by | Japan | Search report |
| US9014155B2 | Cited by | United States of America | Applicant |
| JP2011259425A | Cited by | Japan | Examiner |
| JP2012507910A | Cited by | Japan | Examiner |
| US8855007B2 | Cited by | United States of America | Applicant |
| US8971888B2 | Cited by | United States of America | Applicant |
| JP2001505385A | Cites | Japan | Examiner |
| JP2003333054A | Cites | Japan | Examiner |
| JP2003506960A | Cites | Japan | Examiner |
| JP2003518889A | Cites | Japan | Examiner |
54 members in 7 offices
Priority claims13
| Document | Office | Kind | Date |
|---|---|---|---|
| 60722982 | United States of America | – | |
| 60722983 | United States of America | – | |
| 60722984 | United States of America | – | |
| 72298205 | United States of America | P | |
| 72298305 | United States of America | P | |
| 72298405 | United States of America | P | |
| 60723946 | United States of America | – | |
| 72394605 | United States of America | P | |
| 60728780 | United States of America | – | |
| 72878005 | United States of America | P | |
| 60731495 | United States of America | – | |
| 73149505 | United States of America | P | |
| 2006050373 | Sweden | W |
Members54
| Document | Office | Kind | |
|---|---|---|---|
| WO2007040449A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007040450A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007040451A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007040452A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007040453A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007040454A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2007097938A1 | United States of America | A1 | |
| US2007097939A1 | United States of America | A1 | |
| US2007097983A1 | United States of America | A1 | |
| US2007105527A1 | United States of America | A1 | |
| US2007105568A1 | United States of America | A1 | |
| WO2007040453A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2007040454A3 | World Intellectual Property Organization (WIPO) | A3 | |
| TW200727712A | Taiwan Province of China | A | |
| US2007183427A1 | United States of America | A1 | |
| EP1932377A1 | European Patent Office (EPO) | A1 | |
| EP1932378A1 | European Patent Office (EPO) | A1 | |
| EP1932379A2 | European Patent Office (EPO) | A2 | |
| EP1932385A1 | European Patent Office (EPO) | A1 | |
| EP1932386A1 | European Patent Office (EPO) | A1 | |
| EP1941764A2 | European Patent Office (EPO) | A2 | |
| CN101278578A | China | A | |
| CN101278579A | China | A | |
| CN101278580A | China | A | |
| CN101278581A | China | A | |
| CN101278592A | China | A | |
| CN101310551A | China | A | |
| JP2009510969A | Japan | A | |
| JP2009510970A | Japan | A | |
| JP2009510971A | Japan | A | |
| JP2009510972A | Japan | A | |
| JP2009510973AThis record | Japan | A | |
| US7768983B2 | United States of America | B2 | |
| US7817997B2 | United States of America | B2 | |
| CN101278578B | China | B | |
| US8107964B2 | United States of America | B2 | |
| EP1932385A4 | European Patent Office (EPO) | A4 | |
| EP1932377A4 | European Patent Office (EPO) | A4 | |
| JP4891326B2 | Japan | B2 | |
| EP1932386A4 | European Patent Office (EPO) | A4 | |
| EP1932379A4 | European Patent Office (EPO) | A4 | |
| EP1941764A4 | European Patent Office (EPO) | A4 | |
| CN101278580B | China | B | |
| JP5080481B2 | Japan | B2 | |
| JP5161782B2 | Japan | B2 | |
| CN101278592B | China | B | |
| EP1932385B1 | European Patent Office (EPO) | B1 | |
| ES2421921T3 | Spain | T3 | |
| CN101278579B | China | B | |
| EP1941764B1 | European Patent Office (EPO) | B1 | |
| EP1932379B1 | European Patent Office (EPO) | B1 | |
| EP1932377B1 | European Patent Office (EPO) | B1 | |
| EP1932378A4 | European Patent Office (EPO) | A4 | |
| EP3062580A1 | European Patent Office (EPO) | A1 |
18 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2009510973
- Application
- 2008534499
Titles2
- Japanese
- 移動体システムにおける隣接リストの自動構築
- English
- Automatic construction of adjacency lists in mobile systems
Classification
- CPC, 24
- H04W68/00
- H04L63/101
- H04W8/22
- H04W8/26
- H04W12/08
- H04W16/24
- H04W16/32
- H04W24/02
- H04W24/06
- H04W36/10
- H04W48/02
- H04W48/08
- H04W48/16
- H04W80/00
- H04W80/04
- H04W84/045
- H04W88/08
- H04W88/085
- H04W92/12
- H04W92/22
- H04W76/10
- H04L2101/30
- H04L61/4511
- H04W60/00
- IPC, 13
- H04W24 02
- H04W28 12
- H04W48 08
- H04W12 08
- H04W16 24
- H04W16 32
- H04W48 16
- H04W60 00
- H04W68 00
- H04W80 04
- H04W88 08
- H04W92 12
- H04W92 22
Designated states4
- Regional, 4
- Zimbabwe
- Turkmenistan
- Türkiye
- Togo