Automatic configuration of pico radio base station
10 claims: 7 independent, 3 dependent
- 1無線アクセスネットワーク(24)を動作させる方法であって、 フェムト無線基地局(28 f )の常駐無線受信器(54)を用いて、エアインタフェース(32)により無線アクセスネットワーク(24)において同報されるシステム情報を受信する工程と、 前記システム情報の少なくとも一部を用いて 完全修飾ドメイン名(FQDN)を構築する工程と、 前記構築された完全修飾ドメイン名(FQDN)を用いて前記フェムト無線基地局がノードアドレス問合せを汎用リダイレクタノード(100)に送信する工程と、 前記汎用リダイレクタノード(100)がドメインネームシステム(DNS)データベースに前記ノードアドレス問合せを転送する工程と、 前記フェムト無線基地局(28 f )は前記ノードアドレス問合せに対する前記ドメインネームシステム(DNS)データベースからの応答を前記汎用リダイレクトノード(100)を介して受信し、 前記フェムト無線基地局(28 f ) への接続 に適切な無線ネットワーク制御局ノード(26 2 )のインターネットプロトコル(IP)アドレスを取得する工程とを有することを特徴とする方法。
- 2前 記インターネットプロトコル(IP)アドレスを使用して、前記フェムト無線基地局(28 f )に対するアクティブ無線ネットワーク制御局ノードとして、前記フェムト無線基地局(28 f )を前記適切な無線ネットワーク制御局ノード(26 2 )に接続する工程 を さらに有することを特徴とする請求項1に記載の方法。
- 3前記フェムト無線基地局(28 f )の識別子を前記ノードアドレス問合せに含める工程をさらに有し、 前記フェムト無線基地局(28 f )の識別子は、前記フェムト無線基地局(28 f )のハードウェア識別子と、前記フェムト無線基地局(28 f )のシリアル番号と、前記フェムト無線基地局(28 f )の所有者/運用者の番号との内の少なくとも1つを含むことを特徴とする請求項2に記載の方法。
- 4前記システム情報は、(1)PLMN-IDと、(2)ロケーションエリアコード(LAC)と、(3)セルアイデンティティ(CI)との内の少なくとも1つを含むことを特徴とする請求項1に記載の方法。
- 5前記 完全修飾ドメイン名(FQDN)は、(1)PLMN-IDと、(2)ロケーションエリアコード(LAC)と、(3)セルアイデンティティ(CI)との内の2つ以上の部分の組み合わせ或いは連結を含むことを特徴とする請求項 1 に記載の方法。
- 6前記完全修飾ドメイン名(FQDN)を構築するために前記システム情報と事前構成情報との少なくとも一部を用いる工程をさらに有することを特徴とする請求項 1 に記載の方法。
- 7フェムト無線基地局(28 f )であって、 エアインタフェース(32)により無線アクセスネットワーク(24)で同報されるシステム情報を受信する常駐無線受信器(54)と、 前記システム情報の少なくとも一部を用いて完全修飾ドメイン名(FQDN)を構築するFQDN形成ユニット(58)と、 前記構築された完全修飾ドメイン名(FQDN)を用いてドメインネームシステム(DNS)データベースに対するノードアドレス問合せを汎用リダイレクタノード(100)に送信する手段と、 前記ノードアドレス問合せに対する前記ドメインネームシステム(DNS)データベースからの応答を前記汎用リダイレクトノード(100)を介して受信し、 前記フェムト無線基地局(28 f )に対する適切な無線ネットワーク制御局ノード(26 2 )のインターネットプロトコル(IP)アドレスを取得する手段とを有することを特徴とするフェムト無線基地局。
- 8前記完全修飾ドメイン名(FQDN)を構築するために前記システム情報と事前構成情報との内の少なくとも一部を使用する完全修飾ドメイン名(FQDN)構築手段をさらに有することを特徴とする請求項 7 に記載のフェムト無線基地局。
- 9複数の無線ネットワーク制御局ノード(26)と、少なくとも1つのフェムト無線基地局(28 f )とを有する無線アクセスネットワークであって、 ドメインネームシステム(DNS) データベース(42) と、 汎用リダイレクタノード(100)と を有し、 前記少なくとも1つのフェムト無線基地局(28 f )は、 エアインタフェース(32)により前記無線アクセスネットワーク(24)で同報されるシステム情報を受信する常駐無線受信器(54)と、 前記システム情報 の少なくとも一部を用いて完全修飾ドメイン名(FQDN)を構築するFQDN形成ユニット(58)と、 前記構築された完全修飾ドメイン名を用いて前記ドメインネームシステム(DNS)データベースに対するノードアドレス問合せを前記汎用リダイレクタノード(100)に送信する 手段と、 前 記ノードアドレス問合せに対する前記ドメインネームシステム(DNS)からの応答 を前記汎用リダイレクトノード(100)を介して受信し、 前記複数の無線ネットワーク制御局ノードの内の適切な無線ネットワーク制御局ノードのインターネットプロトコル(IP)アドレスを 取得する手段と、 前 記適切な無線ネットワーク制御局ノードの前記アドレスを使用して前記少なくとも1つのフェムト無線基地局のアクティブ無線ネットワーク制御局ノードとして、前記適切な無線ネットワーク制御局ノードに前記フェムト無線基地局を接続する手段とを有することを特徴とする無線アクセスネットワーク。
- 10前記少なくとも1つのフェムト無線基地局(28 f )はさらに、 前記完全修飾ドメイン名(FQDN)を構築するために前記システム情報と事前構成情報との内の少なくとも一部を使用する完全修飾ドメイン名(FQDN)構築手段を 有 することを特徴とする請求項 9 に記載の無線アクセスネットワーク。
Independent claims10
70 paragraphs, as filed
The present invention relates to wireless communication, in particular to the operation of a "femto" or "pico" radio base station in a radio access network (RAN).
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. 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 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. The base station communicates with the user equipment unit (UE) within the range of the base station via the air interface. In a radio access network, several base stations are typically connected to a radio network control station (RNC) (via terrestrial communication lines or microwaves). 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 Mobile Communication (UMTS) Terrestrial Radio Access Network (UTRAN). 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 spectral 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.
Those skilled in the art will recognize that the RNC may have a serving RNC (SRNC) role or a drift RNC (DRNC) role for certain RAN-UE connections. .. When the RNC is a serving RNC (SRNC), the RNC is responsible for the connection with the user equipment unit (UE) and, for example, has full control over the connection within the radio access network (RAN). The serving RNC (SNRC) is connected to the core network. On the other hand, if the RNC is a drift RNC (DRNC), it serves the serving RNC by supplying the radio resources (in the cell controlled by the drift RNC (DRNC)) needed to connect to the user equipment unit (UE). Supports (SRNC). A system having a drift radio network control station (DRNC) and a base station controlled by the drift radio network control station (DRNC) by the Iub interface is referred to herein as the DRNC subsystem or DRNS. The RNC is called the control RNC (CRNC) of the base station connected to the RNC by the Iub interface. The role of this CRNC is not limited to UE. The CRNC is, among other things, responsible for handling radio resource management for base station cells connected to the CRNC via the Iub interface.
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, ordinary WCDMA base stations (macro RBS) can be connected to an RNC using IP-based transmission. Carrier employees, such as employees of operating companies that own or maintain macro RBS nodes and RNC nodes in radio access networks (RANs), typically install macro RBS nodes. As part of its installation, the macro RBS is manually configured using the IP addressing information (DNS name, fully qualified domain name (FQDN), or IP address) of the RNC to which the macro RNC connects.
In contrast, femto RBSs are usually installed by end users rather than network carriers. 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 a user-driven relocation, it is necessary to connect the femto RBS to the correct RNC no matter where the femto RBS is installed or deployed. The correct RNC or favorable RNC or appropriate RNC in this sense would be the same RNC that controls the overlaying macrocells in the radio access network (RAN).
Connecting to the correct RNC is important because it also improves, for example, the creation of a list of adjacent cells required for roaming and handover between femto RBS cells and macro RBS cells. In addition, it also minimizes network signaling between control nodes.
<p> Therefore, current techniques for manually configuring RBS with RNC IP addressing information do not work for femto RBS, for example, because femto RBS is installed by the end user.</p><p> Therefore, what is needed and the purpose here is to provide methods, techniques, equipment and systems for connecting to the correct RNC servicing the femto RBS, for example the IP connection femto RBS.</p>
<p> The methods and devices of the present application make it possible to connect a femto radio base station to an appropriate radio network control station node of a radio access network to be used as the active radio network control station node of the femto radio base station. The femto radio base station prepares a node address query used to obtain the Internet Protocol (IP) address of the appropriate radio network control station node. Upon receiving a response to that node address query, the femto radio base station also connects the Internet Protocol (IP) address of the appropriate radio network control station node to the appropriate radio network control station node as the active radio network control station node. use.</p><p> In some embodiments, the connection is achieved using radio access network system information (eg, location display information) obtained from the resident receiver of a femto radio base station. The femto radio base station uses at least a portion of the system information to prepare a node address query and uses the node address query to obtain the appropriate wireless network control station node's Internet Protocol (IP) address. Upon receiving a response to its node address query, the femto radio base station connects the Internet Protocol (IP) address of the appropriate radio network control station node to the radio network control station node suitable as its active radio network control station node. Used for.</p><p> From one aspect, this technology concerns how to operate a radio access network. The method includes an example of the following basic steps. That is, the process of preparing and transmitting a node address query, the process of using a node address query to obtain an appropriate wireless network control station node's Internet Protocol (IP) address, and using the Internet Protocol (IP) address, This is a step of connecting an appropriate wireless network control station node and the femto radio base station as an active radio network control station node of the femto radio base station. In some embodiments, the method uses a node to obtain system information broadcast to a radio access network through a radio interface at a femto radio base station and at least a portion of that system information. It further has a step of preparing and transmitting an address query.</p><p> Another aspect of this technique relates to an embodiment of a femto radio base station comprising a resident radio receiver that receives system information broadcast on a radio access network through an air interface. In addition to the Internet Protocol (IP) interface, femto radio base stations also include means of using at least some of the system information to prepare node address queries. The IP interface sends a node address request query containing at least a portion of the system information to the database, receives the appropriate wireless network control station node's Internet Protocol (IP) address in response to the query, and receives the appropriate wireless network. The address of the control station node is used to help connect the femto radio base station to a radio network control station node that is suitable as the active radio network control node for at least one femto radio base station.</p><p> Yet another aspect of the technique relates to a radio access network having a database, multiple radio network control station nodes, and at least one femto radio base station as summarized above.</p><p> In a different embodiment, the system information broadcast by the macro radio base station of the macro cell that overlays the femto cell and received by the femto cell is (1) PLMN-ID, (2) location area code (LAC) and (3) Include at least one of the cell identities (CI).</p><p> In some embodiments, the femto radio base station uses at least a portion of the system information to build or prepare a node address query in the form of a Fully Qualified Domain Name (FQDN). .. The fully qualified domain name (FQDN) then queries the Domain Name System (DNS) database to obtain the Internet Protocol (IP) address of the appropriate wireless network control station node for connection to the femto radio base station. Used for. A fully qualified domain name (FQDN) is formed at least in part using at least part of the system information that is broadcast, and in some cases the combination is (1) PLMN-ID and (2) location. (1) PLMN-ID and (2) Location Area Code (LAC) and (3) such as the concatenation of two or more parts of Area Code (LAC) and (3) Cell Identity (CI). It may include a combination of two or more parts of the cell identity (CI).</p><p> In some embodiments, the femto radio base station has a fully qualified domain name (FQDN) in the Domain Name System (DNS) database to obtain the Internet Protocol (IP) address of the appropriate radio network control station node. ) Is included in the query directly. In another example embodiment, the femto radio base station sends a query, including a fully qualified domain name (FQDN), to the radio network control station node. The wireless network control station node transfers the fully qualified domain name (FQDN) to the Domain Name System (DNS) database in order to obtain the Internet Protocol (IP) address of the appropriate wireless network control station node. When receiving the Internet Protocol (IP) address of the appropriate radio network control station node, the radio network control station node forwards the same to the femto radio base station. In yet another example embodiment, the femto radio base station queries with a fully qualified domain name (FQDN) as a Generic Redirector. Sending to Node), the generic redirector node forwards the fully qualified domain name (FQDN) to the Domain Name System (DNS) database in order to obtain the Internet Protocol (IP) address of the appropriate wireless network control station node. When receiving the Internet Protocol (IP) address of the appropriate radio network control station node, the general purpose redirector node forwards the same to the femto radio base station.</p><p> In some embodiments, the femto radio base station uses system information and at least part of one or both of the identifiers for the femto radio base station to construct or prepare a node address query in the form of a node address request message. Used for. The femto radio base station sends a node address request message to the radio network control station node or the general-purpose redirector node. The wireless network control station node or general-purpose redirector node may transfer at least one or both of the system information and femto wireless base station identifiers contained in the node address request message to the database for proper wireless network control. Obtain the Internet Protocol (IP) address of the station node. The database may be co-located with the wireless network control station node and the general purpose redirector node, or it may be separate. When receiving the Internet Protocol (IP) address of the appropriate wireless network control station node, the wireless network control station node (or general purpose redirector node) forwards the same to the femto radio base station. In some embodiments, the femto radio base station provides system information and femto radio to obtain the Internet Protocol (IP) address of the appropriate radio network control station node from the database for connection to the femto radio base station. At least part of the base station identifier may be used. The identifier for the femto radio base station may include at least one of the hardware identifier of the femto radio base station, the serial number of the femto radio base station, and the owner / operator number of the femto radio base station.</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, one of ordinary skill in the art will appreciate, for example, that the block diagram herein 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. It may include, but is not limited to, (DSP) hardware, read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile memory.
Although not limited to this, the present invention will be described by taking the communication system 10 shown in FIG. 1A as an example. Communication system 10 is connected to 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 them are geographically macrocell 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 typically overlap 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 or end user) can acquire a femto radio base station and install the femto radio base station according to the preference of the femto operator. In this regard, Figure 1A shows such a femto radio base station 28 recently launched by a femto operator.<sub>f-new</sub>Is shown unintentionally. Femto radio base station 28<sub>f-new</sub>Is its femtocell C<sub>f-new</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. The core network 20 of 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 those 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.
In Figure 1A, the femto radio base station 28<sub>f</sub>Is connected to the communication network 38. An example of such a communication network is IP network 38.
Figure 1A also shows that the radio access network also has a Domain Name System (DNS) database 42. The Domain Name System (DNS) database 42 is connected to IP network 38. The Domain Name System (DNS) database 42 of the remote unit may be provided as a separate node of the radio access network 24 as shown, or may be an adjunct to another node (eg, one or more radio network control stations). It may be included in node (RNC) 26). Alternatively, in some cases, access to the Domain Name System (DNS) database 42 may even be provided through core network 20.
When the Domain Name System (DNS) database 42 receives a query by FQDN, the Domain Name System (DNS) database 42 should return the Internet Protocol (IP) address of the appropriate wireless network control station node corresponding to the FQDN of the query. It is composed of.
As shown in the format example depicted in Figure 4, the Domain Name System (DNS) database 42 stores information that associates one or more sets of fully qualified domain names (FQDNs) with a particular wireless network control station node. , When a query is received, the IP network address of a specific wireless network control station node that matches the FQDN included in the query can be returned in response to the query. In such a query and response process, the Domain Name System (DNS) database 42 should be used as the active radio network control station node to which the femto radio base station connects, as described below. For example, it returns the address of the (optimal or preferred) radio network control station node to the queryed femto radio base station.
Figure 1A shows the femto radio base station 28.<sub>f-new</sub>Radio Access Network (RAN), eg, its radio network control station node (eg, radio network control station node 26 in a specific scenario)<sub>1</sub>) Can be considered as an illustration of typical access. Typical access means femto radio base station 28<sub>f-new</sub>The access given to is a broadband fixed access as described above, or a broadband wireless (mobile) access (for example, WiMAX). For broadband radio (mobile) access, femto radio base station 28<sub>f-new</sub>Access to the radio access network 24 is through a macro radio base station and may be made using, for example, High Speed Downlink Packet Access (HSDPA) and Enhanced Uplink, WiMAX, or the like. To comprehensively respond to access types, in Figure 1, the femto radio base station 28<sub>f-new</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. Unless specifically excluded in that context, aspects of the techniques described herein are applicable to all types of access, including broadband fixed access and broadband mobile access (eg, broadband wireless access).
Figure 2 shows a typical femto radio base station 28<sub>f</sub>The basic representative components selected in the example of are shown. One or more femto radio base stations 28<sub>f1</sub>、28<sub>f2</sub>、...、28<sub>fx</sub>However, the general femto radio base station 28 shown in Fig. 2<sub>f</sub>May take the form of. As shown in Figure 2, the femto radio base station 28<sub>f</sub>Has an IP interface unit 50, one or more radio frequency transceivers 52, a radio frequency receiver 54, and a data processing system / part / unit 56, with other not shown components.
Radio frequency transceiver 52 is a femto radio base station 28<sub>f</sub>It is for communicating with the user equipment unit (UE) in the femtocell to be serviced by wirelessly or via an air interface. The number of radio frequency transceivers 52 depends on a variety of factors, including the capacity of the femto radio base station that handles mobile connections.
In the illustrated embodiment, receiver 54 is a femto radio base station 28.<sub>f</sub>It is resident in the Femto radio base station and is useful for acquiring the system information broadcast on the radio access network 24 through the radio interface. For example, in one embodiment, the femto radio base station 28<sub>f</sub>Provides or equips a WCDMA receiver (UE) as its radio frequency receiver 54, thereby receiving signals from cells (including both WCDMA macrocells and femtocells) that the femto radio base station can receive. Temporarily camp on to allow reading of relevant system or network information broadcast in those cells. In one embodiment, the system information that is broadcast from the macro radio base station of the macro cell that overlays the femto cell and is received by the femto radio base station is (1) PLMN-ID and (2) location area code (LAC). (3) Includes at least one of the cell identity (CI).
Therefore, as described above, the femto radio base station may be equipped with, for example, a WCDMA receiver or UE and USIM as the radio frequency receiver 54 in one embodiment. As will be described later, this UE / USIM may be used to connect to a macro cell, which in turn provides mobile broadband access to connect to the RNC.
Use of resident receiver 54 is for femto radio base station 28<sub>f</sub>Is just one example of a method by which can obtain system information or location display information (system information or location display information is used to form at least a part of the FQDN). Techniques described herein, including the formation / use of an FQDN in a femto radio base station, particularly for queries to the Domain Name System (DNS) database, are such that the femto radio base station does not have a resident receiver, eg, femto. It is also applicable to other embodiments in which system information or location display information must be acquired from the outside, such as a user equipment unit serviced by a radio base station.
The RBS data processing system 56 has an FQDN formation unit 58. As described herein, the FQDN formation unit 58 uses at least a portion of system information (eg, obtained by radio frequency receiver 54, etc.) to form a fully qualified domain name (FQDN). To do. The FQDN formation unit 58 may be included as part of the RBS data processing system 56 as shown, or may be provided as a separate controller or processor in the broader sense of those terms as described above.
FIG. 3 shows selected basic representative components of the example of wireless network control station node 26. The wireless network control station node 26 connects the wireless network control station node 26 to the core network 20 through the Iu interface to the interface unit 70, and the wireless network control station node 26 to another wireless network control station (not shown) through the Iur interface. One or more macro radio base stations 28 to connect to the interface unit 72 and the wireless network control station node 26 through the Iub interface<sub>M</sub>One or more interface units 74, each connected to, 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 may have several interface units, such as one or more interface units 76, each connected to. RNC26 and Femto Radio Base Station 28<sub>m</sub>The connection to and from may be made through the communication network 38, for example, Internet Protocol (IP) based transmission may be utilized. RNC26 and macro radio base station 28<sub>M</sub>For the connection with, for example, at least one of Internet Protocol (IP) -based transmission and ATM-based transmission may be used.
In addition to the interface unit, the wireless network control station node 26 includes not only the data processing system / unit / unit 80, but also a number of components (not shown). In the non-limiting embodiment shown in FIG. 3, the data processing system 80 of the wireless network control station node 26 is the control unit (eg, controller 82), the handover unit 84, and (eg, the diversity leg of the connection). It has a combiner and a splitter unit 86 (which is involved in handling etc.).
At the time shown in Figure 1A, the femto radio base station 28<sub>f-new</sub>Has just been launched by the femto operator. Immediately after startup, femto radio base station 28<sub>f-new</sub>Does not yet know its specific location in the environment of the radio access network 24 (as shown in the event or step S-1A) and therefore the femto radio base station 28.<sub>f-new</sub>Does not know which radio network control station node 26 is optimally located (geographically or otherwise) to serve as the active radio network control station of. In the situation shown in Figure 1A, the femto radio base station 28<sub>f-new</sub>Is macrocell C<sub>M</sub>Located in Macrocell C<sub>M</sub>Is a radio base station 26<sub>M</sub>And the second wireless network control station node 26<sub>2</sub>Received service from. Therefore, judging from the topology of the radio access network 24, the femto radio base station 28<sub>f-new</sub>The correct / preferred wireless network control node for is the first wireless network control station node 26.<sub>1</sub>Not the second wireless network control station node 26<sub>2</sub>Is.
Femto radio base station 28 in that it does not know about its location on the radio access network 24<sub>f-new</sub>Activates the radio frequency receiver 54 and uses the radio frequency receiver 54 to confirm or obtain system information broadcast to the radio access network 24 through the radio interface. In this regard, FIG. 1B shows the acquisition of system information as an event or step S-1B.
The system information (also known as location information) is one of the following: (1) PLMN-ID, (2) Location Area Code (LAC) and (3) Cell Identity (CI): The above can be included. The PLMN-ID can be decoded from the master information block (MIB). The location area code (LAC) is decoded from the decoding system information block 1 (SIB1). The cell identity (CI) is decoded from system information block 3 (SIB3). UTRAN cell identities consist of 28 bits, of which 12 bits are typically used to contain RNC identifiers. This means that in this case the cell identity (CI) can be used to identify the RNC of a single PLMN.
Figure 1C shows the femto radio base station 28 as an event or step S-1C.<sub>f-new</sub>Indicates that it will use at least some of the system information to create the fully qualified domain name (FQDN). Creating a fully qualified domain name (FQDN) is a femto radio base station 28<sub>f-new</sub>FQDN formation unit 58 of.
Therefore, which PLMN is allowed after the radio frequency receiver 54 searches the surrounding macro coverage and temporarily camps on the best UTRAN cell allowed for the UE with the radio frequency receiver 54. USIM information is used to find out. The UE, eg, the radio frequency receiver 54, reads the relevant system information and transmits it to the FQDN formation unit 58. The FQDN formation unit 58 then creates a fully qualified domain name (FQDN), at least in part, based on system information.
Once the fully qualified domain name (FQDN) is formed (eg, as described below), the femto radio base station will use the fully qualified domain name (FQDN) in the Domain Name System (as shown in Figure 1D). DNS) Used to query database 42. Femto radio base station 28<sub>f-new</sub>In one embodiment, the fully qualified domain name (FQDN) is propagated to the IP interface unit 50 as a node address query, as depicted in step 1D or event S-1D. IP interface unit 50 helps send node address queries, including fully qualified domain names (FQDNs), to Domain Name System (DNS) database 42. Femto radio base station 28 to access Domain Name System (DNS) database 42<sub>f-new</sub>Knows in advance the network address of the Domain Name System (DNS) database 42. For example, the network address of the Domain Name System (DNS) database 42 is pre-stored or pre-downloaded to the IP interface unit 50 using, for example, a Dynamic Host Configuration Protocol (DHCP) server. As an example, FIG. 2 shows a femto radio base station 28 having memory 94 (preferably non-volatile) for storing the IP address of the Domain Name System (DNS) database 42.<sub>f</sub>Is shown.
Figure 1E shows the Domain Name System (DNS) database 42 femto radio base station 28 as a step or event S-1E.<sub>f-new</sub>It depicts receiving a node address query (query) from and performing a search to match the IP address of the appropriate or correct wireless network control station node with the FQDN of the query. As shown in Figure 4, in one configuration example of the Domain Name System (DNS) database 42, the IP address of the wireless network control station node is probably in some queries, for example, some fully qualified domain names (FQDNs). Be associated.
Figure 1E shows the femto radio base station 28 in the form of the IP address of the appropriate or correct radio network control station node where the Domain Name System (DNS) database 42 matches the FQDN of the query or responds appropriately.<sub>f-new</sub>I also draw a place to return a response to. Femto radio base station 28<sub>f-new</sub>IP interface unit 50 serves to receive a response to an inquiry (the Internet Protocol (IP) address of the appropriate / correct wireless network control station node). The Internet Protocol (IP) address of the appropriate / correct wireless network control station node is stored in memory or registers such as memory 96 shown in Figure 2.
Figure 1F shows the femto radio base station 28 as the subsequent operation stage.<sub>f-new</sub>In particular, the IP interface unit 50 uses the Internet Protocol (IP) address of the appropriate / correct wireless network control station node (obtained by the above method with reference to FIGS. 1A-1E) of the femto radio base station. It depicts connecting to the appropriate / correct radio network control station node used by the femto radio base station as an active radio network control node. In the specific situation shown in FIG. 1F, the IP interface unit 50 is connected to the second wireless network control station node 26 through the IP network 38.<sub>2</sub>Connect to. Second wireless network control station node 26 in terms of network topology<sub>2</sub>Is a femto radio base station 28<sub>f-new</sub>The correct / preferred wireless network control node. Wireless network control station node 26 through IP network 38<sub>2</sub>The connection to is depicted in step 1F or event S-1F in Figure 1.
Therefore, in the above illustrated method example, the FQDN created by the FQDN formation unit 58 is used to query the Domain Name System (DNS) database 42 to find the correct RNC IP address. As a result, the femto radio base station 28<sub>f-new</sub>Will be able to initiate an IP connection with a wireless network control station node with the address selected by the Domain Name System (DNS) database 42.
In the embodiments of FIGS. 1A-1F, the FQDN created by the FQDN formation unit 58 is used to directly query the Domain Name System (DNS) database 42 to find the correct RNC IP address. In another embodiment shown in FIG. 6, the FQDN created by the FQDN formation unit 58 is sent to the wireless network control station node as a node address query, and then the wireless network control station node is the domain name server (DNS) database 42. Query the database such as (6). In the embodiment of FIG. 6, the femto radio base station 28<sub>f</sub>Interface 50 connects to the communication network 38 through an interface known as the extended Iub interface (Iub + interface). The extended Iub + interface is preferably formed by an Internet Protocol (IP) connection through IP network 38. In some embodiments, the Iub + interface is similar to the Iub interface, but modified to convey additional information. The operation of the embodiment of FIG. 6 begins in essentially the same manner as that depicted in FIGS. 1A-1C of the embodiments of FIGS. 1A-1F. However, in contrast to the previous embodiment, for the embodiment of FIG. 6, step S-6D (1) is a femto radio base station 28.<sub>f</sub>IP interface unit 50 queries the wireless network control station node 26, including the fully qualified domain name (FQDN).<sub>1</sub>Indicates where to send to. Wireless network control station node 26<sub>1</sub>Is a femto radio base station 28<sub>f</sub>May be the default RNC with a pre-known (eg, preconfigured) network address. Step S-6D (2) is the wireless network control station node 26<sub>1</sub>But the femto radio base station 28<sub>f</sub>Shows a query containing the fully qualified domain name (FQDN) created by the domain name server (DNS) database 42 (6). In the particular embodiment shown in FIG. 6, the domain name server (DNS) database 42 (6) is the wireless network control station node 26.<sub>1</sub>It is located on a different node than the node in. However, in other embodiments, the Domain Name Server (DNS) database 42 (6) is the default wireless network control station node 26.<sub>1</sub>May be located in the same place as.
Figure 6 further depicts the step or event S-6E (1) in which the Domain Name System (DNS) database 42 is the wireless network control station node 26.<sub>1</sub>It is about to receive a query from and perform a search to match the IP address of the appropriate or correct wireless network control station node with the FQDN of the query. Figure 6 also depicts as step or event S-6E (2) for a suitable or correct wireless network control station node where the Domain Name System (DNS) database 42 matches or responds appropriately to the FQDN of the query. Wireless network control station node 26 in the form of an IP address<sub>1</sub>I am about to reply to. Radio network control station node 26 as step or event S-6E (3)<sub>1</sub>The response from the domain name server (DNS) database 42 (6), femto radio base station 28<sub>f-new</sub>Transfer to the IP interface unit 50 of. Therefore, the femto radio base station 28<sub>f-new</sub>IP interface unit 50 serves to receive a response to an inquiry (the Internet Protocol (IP) address of the appropriate / correct wireless network control station node). The Internet Protocol (IP) address of the proper / correct radio network control station node is the femto radio base station 28, as explained earlier.<sub>f</sub>It is stored in the memory or register of. In the example of the embodiment of FIG. 6, the wireless network control station node 26<sub>1</sub>Not the wireless network control station node 26<sub>2</sub>But the femto radio base station 28<sub>f</sub>Is the proper / correct wireless network control station node.
Then, as a step or subsequent stage of operation depicted in event S-6F, the femto radio base station 28<sub>f-new</sub>In particular, the IP interface unit 50 is suitable for use by the femto radio base station as the active radio network control node of the femto radio base station, using the appropriate / correct radio network control station node's Internet Protocol (IP) address. / Connect to the correct wireless network control station node. In the specific situation shown in FIG. 1F, the IP interface unit 50 is connected to the second wireless network control station node 26 through the IP network 38.<sub>2</sub>Connect to. From the network topology, the second wireless network control station node 26<sub>2</sub>Is a femto radio base station 28<sub>f-new</sub>The correct / preferred wireless network control node. Wireless network control station node 26 through IP network 38<sub>2</sub>The connection with is depicted in step 6 or event S-6F in Figure 6.
Therefore, in the embodiment of FIG. 6, the femto radio base station 28<sub>f</sub>And the default wireless network control station node 26<sub>1</sub>The Iub + interface between and is similar to the Iub interface, but has been modified to convey additional information, such as the query in step S-6C and the response in step S-6D (3).
The embodiment of FIG. 7 is similar to the embodiment of FIG. 6, but has a general purpose redirector node 100. The general-purpose redirector node 100 is the wireless network control station node 26 in FIG.<sub>1</sub>Performs the same steps and functions as, but uses the new protocol or "redirected" protocol through the "redirected" interface instead of the Iub extended protocol or Iub + protocol. The "redirect" protocol may be, for example, any new protocol configured to carry query information and responses to general nodes. Thus, FIG. 7 forwards the query to the domain name server (DNS) database 42 (7) as step or event S-7D (2) and the domain name server (DNS) database as step or event S-7E (2). Femto radio base station 28 receives a response from 42 (7) and receives a response from domain name server (DNS) database 42 (7) as step or event S-7E (3)<sub>f</sub>Shows the general-purpose redirector node 100 to forward to. Therefore, as a step or subsequent stage of operation depicted by Event S-7F, Femto Radio Base Station 28<sub>f-new</sub>In particular, the IP interface unit 50 is a suitable / correct wireless network control station node (eg, wireless network control station node 26 in the embodiment of FIG. 7).<sub>2</sub>) Internet Protocol (IP) address to connect to the appropriate / correct radio network control station node used by the femto radio base station as the active radio network control node for the femto radio base station.
In each of the embodiments of FIGS. 6 and 7, the default wireless network control station node 26<sub>1</sub>And the generic redirector node 100 can contact the domain name server (DNS) database located on different nodes in the situations depicted in FIGS. 6 and 7, respectively. Alternatively, the default wireless network control station node 26<sub>1</sub>And the general-purpose redirector node 100 may execute the function of the domain name server (DNS) database by its own device in each embodiment.
It should also be recognized that the database queried in any of the examples described herein is not necessarily referred to as a domain name server (DNS) database, nor does it have to provide its services alone. Any other database that has sufficient information to locate or determine the correct or appropriate radio network control station node address for the femto radio base station can be used instead.
As mentioned earlier, the FQDN formation unit 58 creates a fully qualified domain name (FQDN), at least in part, based on system information. It can be said that the fully qualified domain name (FQDN) is at least partly based on system information in the sense that it may also be based on, for example, the preconfigured information of the femto radio base station to identify the operator. The preconfigured information could be, for example, a string such as "operator.com". This specific identifier is described as "pre-conf-operator-id" in the following FQDN example. In other cases, the femto radio base station could use the string .pub.3gppnetwork.org instead as the preconfigured identifier.
As described below, a fully qualified domain name (FQDN) is formed or generated in a variety of different ways, with at least a portion formed using at least a portion of the system information broadcast. In one embodiment, one technique for creating a fully qualified domain name (FQDN) is to use all three identifiers, PLMN-ID, LAC, and cell identity. As another example, a fully qualified domain name (FQDN) probably contains two or more parts of (1) PLMN-ID and (2) location area code (LAC) and (3) cell identity (CI). It may have a combination of two or more parts, such as a concatenated combination of (1) PLMN-ID, (2) location area code (LAC), and (3) cell identity (CI). ..
Therefore, essentially any combination of PLMN-ID, LAC and CI is used to create the FQDN. An example of the combination is given below (remember that the pre-configuration information is represented by pre-conf-operator-id). That is, PLMN-ID, LAC and Cell Identity (CI) PLMN-ID and LAC PLMN-ID and cell identity · Only pre-conf-operator-id and LAC (in some cases) · Only pre-conf-operator-id and cell identity (in some cases).
For example scenarios, consider the situation where the UTRAN environment is described with the following information. That is, -Set the pre-configuration information about the femto radio base station, that is, the pre-conf-operator-id to "operator.com". -PLMN-ID is 012-123 (that is, mobile country code MCC is 012, mobile network code MNC is 123). -The LAC has a value of 34567. CI is a hexadecimal value of 1234567 (this is because the RNC identifier part of the CI is 123 in hexadecimal (ie, 291 in decimal) and the 3G cell identifier part is 4567 in hexadecimal (ie, decimal). Means that it is 17767)).
For the scenario described immediately before, the following is a non-limiting example of the fully qualified domain name (FQDN) formed or generated by the FQDN formation unit 58 for that scenario. That is, -Only the pre-conf-operator-id and the RNC part of the cell identity, for example, rnc291.operator.com. · Only pre-conf-operator-id and LAC (in some cases), for example lac34567.operator.com. -PLMN-ID and LAC, for example, "lac34567.mnc123.mcc012.pub.3gppnetwork.org".
In one aspect of the behavior, the femto operator may choose one or more different alternatives to create the FQDN. Domain Name System (DNS) Database 42 is programmed or updated to reflect relevant information (IP address and FQDN matching or pairing for all wireless network control station nodes that Domain Name System (DNS) Database 42 is responsible for). It should be.
If the femto radio base station is not within WCDMA coverage, in one embodiment the femto radio base station could connect to the Domain Name System (DNS) database 42 using only the pre-conf-operator-id. Good. Such a femto base station could be connected to any radio network control station node, for example, the default RNC or the central RNC. This is because in such cases, handover or roaming to macrocells is not possible without loss of coverage, so there is no need to provide a list of adjacent cells.
Also, in some embodiments, the node address query may take a different form than the fully qualified domain name (FQDN). For example, in the example embodiments of FIGS. 8 and 9, the node address query is for the wireless network control station node 26.<sub>1</sub>Takes the form of a node address request message sent to (Figure 8) or sent to a generic redirector node (Figure 9). The example step or event in Figure 8 is similar to the example in Figure 6. It is also understood in Figure 8 that the node address query takes the form of a node address message rather than a fully qualified domain name (FQDN), and database 42 (8) does not necessarily have to be a domain name server (DNS) database. Ru. Similarly, the example step or event in Figure 9 is similar to the example in Figure 7. It is also understood in Figure 9 that the node address query takes the form of a node address message rather than a fully qualified domain name (FQDN), and database 42 (9) does not necessarily have to be a domain name server (DNS) database. Will be done.
The node address request message can include at least part of the system information and one or both of the identifiers for the femto radio base station in order to obtain the Internet Protocol (IP) address of the appropriate wireless network control station node from the database. .. In a different embodiment, the identifiers for the femto radio base station used in the node address request message are the femto radio base station hardware identifier, the femto radio base station serial number, and the femto radio base station owner / operator. It can contain at least one of the numbers. A database (eg, database 42 (8) or database 42 (9)) of system information and identifiers is used to determine the appropriate radio network control station node for a femto radio base station that has an identifier and provides system information. One or both may be used.
Femto radio base station 28, regardless of the form of the node address query (eg, FQDN or node address request message)<sub>f-new</sub>Whatever the wireless network control station node that becomes the active wireless network control station node, it should also be able to redirect the femto RBS to another RNC if the situation requires it. Such redirection may include further queries to database 42. This decision is based on the amount and type of traffic produced via (eg) femto radio base stations.
As pointed out above, at startup and startup, femto radio base station 28<sub>f-new</sub>Essentially does not remember its location within the radio access network. Therefore, Femto Radio Base Station 28<sub>f-new</sub>The purpose of creating a node address query (for example, a fully qualified domain name (FQDN) or node address request message) and querying the appropriate database 42 is for the femto radio base station 28.<sub>f-new</sub>However, it is possible to determine the address of the appropriate or correct radio network control station node that the femto radio base station can connect to for use as the active radio network control station node.
Thus, as described above, the femto radio base station may be moved by the end user, and the femto radio base station still connects to the correct RNC using the techniques described above.
As mentioned above, such principles / methods may also be applied to wireless technologies other than WCDMA. WCDMA is illustrated only as an example. Other suitable technologies include, but are not limited to, GSM, CDMA, WiMAX, and the like. This technique is particularly relevant to the systems and scenarios described above for convenience, but could be applicable to other cases and 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">、</figref><figref num="1B">、</figref><figref num="1C">、</figref><figref num="1D">、</figref><figref num="1E">、</figref><figref num="1F">FIG. 5 is a schematic diagram of an embodiment of a communication system including a radio access network, showing sequential stages of operation of connecting a femto radio base station and an appropriate radio network control node.</figref><figref num="2">It is the schematic of the Example of the femto radio base station.</figref><figref num="3">It is a schematic diagram of an example of a wireless network control (RNC) node.</figref><figref num="4">It is a schematic diagram of the structural example of the Domain Name System (DNS) database.</figref><figref num="5">It is a figure which shows two different backhaul proposals.</figref><figref num="6">It is a schematic of another embodiment of a communication system including a radio access network, showing selected sequential steps of operation connecting a femto radio base station and a suitable radio network control node according to an example of another mode of operation. It is a figure which shows.</figref><figref num="7">It is a schematic of still another embodiment of a communication system including a radio access network, and a selected sequential operation of connecting a femto radio base station to a suitable radio network control node according to an example of yet another mode of operation. It is a figure which shows the stage.</figref><figref num="8">It is a schematic of still another embodiment of a communication system including a radio access network, and a selected sequential operation of connecting a femto radio base station to a suitable radio network control node according to an example of yet another mode of operation. It is a figure which shows the stage.</figref><figref num="9">It is a schematic of still another embodiment of a communication system including a radio access network, and a selected sequential operation of connecting a femto radio base station to a suitable radio network control node according to an example of yet another mode of operation. It is a figure which shows the stage.</figref>
14 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 Sheet 14
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2002501333A | Cites | Japan |
| WO2005079087A1 | Cites | World Intellectual Property Organization (WIPO) |
| JP2001309421A | Cites | Japan |
54 members in 7 offices
Priority claims13
| Document | Office | Kind | Date |
|---|---|---|---|
| 60722984 | United States of America | – | |
| 60722983 | United States of America | – | |
| 60722982 | United States of America | – | |
| 72298405 | United States of America | P | |
| 72298305 | United States of America | P | |
| 72298205 | 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 | |
| 2006050370 | 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 | |
| JP2009510973A | 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 | |
| JP5080481B2This record | 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 |
20 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 | |
| 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 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 5080481
- Application
- 2008534497
Titles2
- Japanese
- IP接続の無線基地局に対する無線ネットワーク制御局の選択
- English
- Selection of wireless network control station for IP-connected wireless base station
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, 14
- H04W8 26
- H04W84 10
- H04W92 12
- H04W12 08
- H04W16 24
- H04W16 32
- H04W24 02
- H04W48 08
- H04W48 16
- H04W60 00
- H04W68 00
- H04W80 04
- H04W88 08
- H04W92 22
