Title of Invention

"A METHOD FOR ESTABLISHING IPOA CHANNEL-BASED DEFAULT OPERATION AND MAINTENANCE CHANNELS"

Abstract

This invention discloses a method for establishing IPOA channel-based default maintenance channels. The invention establishes an IPOA channel between a base station and a base station controller with default configuration of the base station. A BOOTP request is initiated from the base station to an operation and maintenance center, and the base station obtains an IP address assigned to it from a response sent from the operation and maintenance center, so that an operation and maintenance center is established between the base station and the base station controller. The invention can solve automatic base station launching problem, and can prevent IP address conflicts and implement parallel launching of base stations. In addition, with the method described in this invention, operation of establishing maintenance channels is simple, light in workload, and reliable. Thus, program and data auto-loading as well as configuration and maintenance of base station(s) at far end (i.e., the operation and maintenance center) can be achieved. The method described in this invention is superior in quality and low cost in maintenance, and can be applied to various networking patterns, such as star-type, chain type, and tree-type networks.

Full Text

Field of the Invention The present invention relates to data channels in wireless communication systems. In particular, it relates to a method for establishing operation and maintenance channels at lub interfaces between two base stations in UTRANs for WCDMA cellular mobile communication systems. Background of the Invention As wireless communication technology develops, communication networks become more and more sophisticated and bulky. As a result, the criteria for network maintainability become higher. However, due to default maintenance channels of base stations have not been defined in the protocols of 3G wireless communication networks for WCDMA and CDMA2000 communication systems, it is impossible for base stations to automatically complete far-end auto-configuration, which brings inconvenience to network maintenance. Presently, there are mainly two methods for establishing maintenance channels for base stations: the first one is that maintenance personnel manual configures related data at base stations (NodeB) and base station controllers, so as to configure special operation and maintenance channels to solve base station startup problem. However, due to the fact that access devices arc usually far from the network in actual applications, the fatal defect of this method is that near-end base station's O&M data configuration is in great difficulty, if the corresponding physical base station is far from the base station controller or this base station is in a remote and/or desert area, in addition, it is inconvenient for failure treatment. The second method is: At initial startup of all base stations, requests are submitted to the operation and maintenance center with preset PVCs and IP addresses, to obtain formal configuration data. For subsequent startups, the formally configured PVCs and IP addresses will be used to contact with the operation and maintenance center, and the original PVCs and IP information will be deleted. However, the fatal defect of this method is that it is difficult to implement when the operation and maintenance center is at far end. In addition, because all base stations use fixed IP addresses, they can't be launched at the same time; otherwise, the operation and maintenance center is unable to identify the base stations. Further, the operation and maintenance and network management are complex during startup of the base stations. Furthermore, operation and maintenance channels can't be established at base stations automatically, and manual intervention is necessary in case of data loss after startup of the base stations. In conclusion, the mam defect of existing methods for establishing operation and maintenance channels for base stations is that the mechanism for automatically establishing operation and maintenance channels is unavailable. Therefore, the operation of establishing operation and maintenance channels is difficult, labor-intensive, and error-prone, and thus causing increased maintenance costs and degraded quality. Summary of the Invention The purpose of the invention is to provide a method for establishing IPOA-based default operation and maintenance channels, to enable automatic establishment of operation and maintenance channels for base stations and implement maintenance functions such as program and data auto configuration, so as to enhance network maintainability, reduce operation and maintenance costs, and improve operation and maintenance quality. In order to achieve above purposes, this invention provides a method for automatically establishing LPOA channel-based default operation and maintenance channels, comprising: (1) establishing a default PVC between a base station and a base station controller; (2) initiating a BOOTP request at the base station in broadcast mode, and sending the BOOTP request to the operation and maintenance center with the default PVC; (3) the operation and maintenance center sending a response to the base station, the response containing an IP address assigned to the base station; (4) establishing an IPOA (IP over ATM) channel in accordance with the IP address and the default PVC, so as to establish an operation and maintenance channel between the base station and the base station controller. In one embodiment, the IPOA channel is established with default configuration of the base station in step (1). In one embodiment, the BOOTP request is submitted to the operation and maintenance center via a route of the base station controller in step (2). In one embodiment, the response is sent from the operation and maintenance center to the base station via the base station controller in step (3). In view of the above, this invention provides a method to establish IPOA channels between base stations and base station controllers with default PVC configurations of the base stations. BOOTP requests are submitted from the base stations to an operation and maintenance center, and the operation and maintenance center sends responses to the corresponding base stations with assigned IP addresses, and thus to establish operation and maintenance channels between the base stations and the base station controllers. Accordingly, this invention can automatically establish operation and maintenance channels when base station is powered on, which can prevent IP address conflicts and implement parallel launching of base stations. In addition, with the method described in this invention, operation of establishing operation and maintenance channels is simple, light in workload, and reliable, and thus program and data auto-loading as well as configuration and maintenance of base station at far end (i.e., the operation and maintenance center) can be achieved. The method of this invention is superior in quality and low cost in maintenance, which can be applied to various networking patterns, such as star-type, chain-type, and tree-type networks. Brief Description of Drawings Fig.l shows a flow chart of an embodiment of this invention. Fig.2 shows a format of a BOOTP request packet used in this invention. Fig.3 is a schematic diagram of establishing an operation and maintenance channel for base stations in a chain-type network according to this invention. Fig.4 is a schematic diagram of establishing an operation and maintenance channel for base stations in a tree-type network. Fig.5 shows a structural diagram of UTRAN chain-type network using WCDMA system according to one embodiment of this invention. Fig.6 shows a format of a physical address used in the embodiment shown in Fig.5. Fig. 7 is a descnption chart of the format of physical address shown in Fig.6. Embodiments of the Invention Hereunder the invention is further described with reference to the attached drawings. This invention is mainly based on the following presumptions: 1. ATM transmission technology is used between base station and base station controller: 2. physical connection between base station and base station controller is ready. Fig.l shows a flow chart of an embodiment of this invention. As shown in Fig.l, a default PVC is established between a base station and a base station controller with the default PVC configuration (step 1). Then, according to the default PVC, a BOOTP request is submitted from the base station in broadcast mode to an operation and maintenance center of a system via a route of the base station controller (step 2). Afterwards, the operation and maintenance center assigns an IP address to the base station by filling the IP address in the BOOTP response packet, and sends the BOOTP response to the base station controller, which then sends the BOOTP response to the base station (step 3). Finally, the base station obtains the IP address, and establishes an IPOA channel according to the obtained IP address and the default PVC, so that an operation and maintenance channel between the base station and the base station controller is established. Thus, an IPOA channel-based operation and maintenance channel between the base station and the base station controller is established successfully (step 4). The BOOTP request packet initiated from the base station in step 2 contains the following fields (see Fig.2 for detailed format): Packet operating code (op), designed to indicate BOOTP packet type; Hardware address type (htype), designed to indicate hardware address type; Hardware address length (hlen), designed to indicate hardware address length; Hardware operation setting (hops), designed to indicate the number of gateways passed through; Processing ID (xid), designed to match a BOOTP request and its corresponding BOOTP response: Elapsed seconds (sees), designed to indicate the time passed since startup of the client; Client EP address (cirddr), designed to indicate client IP address; Own IP address (yiaddr), designed to indicate the client IP address filled in by the server; Server IP address (siaddr), designed to indicate the server IP address filled in by the server; Gateway IP address (giaddr), designed to indicate the gateway address passed; Client hardware address (chaddr), designed to indicate hardware address of the client. In this invention, in case the base station doesn't know its own hardware address, special treatment will be carried out in this field so that the base station controller and the maintenance terminal can identify the base station that sends BOOTP request; Optional server name (sname), designed to indicate the optional server name; Boot file name (file), designed to indicate the file name to be loaded; Optional vender domain (vend), designed to indicate vendor-defined domain. In this invention, the base station controller can utilize this domain to facilitate routing. In one embodiment of this invention, in view that a physical connection (UNI-based physical connection, IMA-based physical connection, or any other physical connection) has been established between the base station and the base station controller, the base station can identify the type of connection by listening to messages on the link, so as to obtain the data of the physical link configured by the base station controller. For example, for an IMA-based physical connection, the base station can obtain the information of the physical IMA link by listening to 1CP units in IMA frames, so as to establish a default PVC. Because there is no channel between the base station and the base station controller before a default IPOA channel is created, the base station cannot interact with the base station controller. Therefore, default PVC mode is necessary. For example, VPI=1/VCI=0 may be used. After the default PVC is confirmed, the base station can initiate a BOOTP request to apply for an IP address. When the base station controller detects a BOOTP request from the base station, it would forward the BOOTP request packet to the operation and maintenance center, and ensure that the operation and maintenance center can identify the base station that sends the BOOTP request packet, in order to assign an IP address to the base station. Therefore, if the operation and maintenance center is external to the base station controller, then the base station controller needs to process the BOOTP request packet. For example, it may add PVC information in the client hardware address (chaddr) field of the BOOTP packet, to make sure thai the external operation and maintenance center can identify the base station that sends the BOOTP request packet. In addition, the base station controller should forward the BOOTP response from the operation and maintenance center to the base station, so that the base station can obtain the IP address assigned to it. In actual application, information such as file name of the program to be loaded and file path can be obtained as required. The base station will establish an IPOA channel according to the obtained IP address. After the IPOA channel between the base station and the base station controller is established, the program and data of the base station can be loaded through that channel. Fig.2 and Fig.3 show schematic diagrams of establishing operation and maintenance channels for base stations in chain-type and tree-type networking pattern, respectively. Base stations start up level by level, i.e., the base station at lower level can start up only after the base station at higher level starts up. For star-type networking pattern with respect to the base station controller, the base stations can start up in parallel. As shown in the above figures, the base station connected directly to the base station controller starts up first, so as to obtain program and configuration data to operate normally. Other base station(s) connected to the above base station also initiate BOOTP request(s) in broadcast mode through default PVC(s) with above method. The configuration data of the base station that starts up first contains configuration data of the PVC cross connection; furthermore, an IPOA channel has been established between that base station and the base station controller according to the configuration data. Therefore, the base station that starts up first is only required to perform PVC switching at the corresponding port; whereas the base station controller treats other base station(s) in the same manner as it treats with the base station that starts up first. When a base station at the lower level receives the BOOTP response and obtains the EP address, an IPOA channel between it and the base station at the higher level is established. Due to the fact that a PVC connection has been established between the base station at the higher level and the operation and maintenance center, a connection between the current level base station and the operation and maintenance center is also established. In this way. each base station can start up automatically. However, the operation and maintenance channel(s) of the base station(s) at the lower level can be established only after the base station at the higher level starts up. Fig.5 shows a structural diagram of UTRAN chain-type network using WCDMA system according to one embodiment of this invention. As shown in Fig.5, UTRAN base stations are in chain networking pattern, and the operation and maintenance center is at far end. El connection and IMA-based ATM transmission arc utilized between NodeB and RNC. First, NodeB 1 obtains IMA configuration information by listening to 1CP units in IMA frames on El link. Assuming that the default PVC is contained in the IMA group with the minimal link number, a default PVC (VP1=1; Y"CI=-0) is ready between NodeB 1 and RNC, and NodeB initiates the BOOTP request in broadcast mode. The parameters of the BOOTP packet are as follows: op = 1; htype = 1; hlen = 6; hops = 0; xid = a random number (make sure that each base station has its unique number by use of an algorithm, or by use of local time directly); sees — 0; flags = 0; ciaddr = 0: yiaddr = 0; siaddr = 0; giaddr = 0; chaddr — see Fig. 6 and Fig.7 for the format; sname = 0 (stand-by); file = 0 (stand-by); vend = 0. When the BOOTP agent of RNC (base station controller) or the BOOTP server detects the BOOTP request packet, it makes necessary treatment to the BOOT!5 request packet. For example, it adds information (e.g., PVC and socket information) in "chaddr" field to enable the far-end maintenance center to identify NodeB. If modifications have been made to the "giaddr" mfonnation at different gateways, then gateway information needs to be added. At the same time, "hops" is increased by I, and "sees" is modified. Then, RNC forwards the BOOTP packet to the far-end maintenance center. When the far-end maintenance center receives that BOOTP request, it assigns an IP address according to "chaddr", and fills IP address mfonnation with file name and path into a BOOTP response packet, and then sends out the BOOTP response packet. When RNC receives the response packet, it routes and forwards that BOOTP response packet to the default PVC of lub. Thus, NodeB 1 receives the BOOTP response packet and obtains IP address from the packet: and then it creates an IPOA device and attaches the default PVC to the IPOA device, so that an IPOA operation and maintenance channel is established. Of course, filename and path may also be included in the BOOTP response packet if necessary, so that the base station can load the program according to the filename and path. Hereunder we describe the chain-type connection. Because the far-end maintenance center has set the PVC configuration information between Nodel and RNC, after Nodel starts up and operates normally, it receives the configuration data and establishes connection with RNC according to the configuration data. The configuration data contains information of the PVC channel between NodeBl and RNC, which is used by the operation and maintenance channel for Node2. Assuming that the PVC is: VP1=1; VCI=33. After NodeB2 powers on, it also initiates a BOOTP request through a default PVC (VPI=1; VCI=0). Model receives the BOOTP request on the default PVC channel at a port and performs PVC switching according to the preset PVC cross connection. In this way, the BOOTP request is switched to the above PVC (VPI^l, VC1=33). Then, RNC makes the same treatment to the BOOTP request packet and forwards it to the far-end maintenance center to obtain IP address and file name/path. Then, the far-end maintenance center sends out a BOOTP response, which is forwarded by RNC. NodeB2 receives the BOOTP response via the PVC switching of NodeBl. In this way, an IPOA connection between NodeB2 and the far-end maintenance center is established. Above method can also be applied to hierarchical networking pattern. In addition, it can be applied to ring-type and tree-type networking patterns as well. We Claim: 1. A method for establishing an IPOA channel-based operation and maintenance channel, comprising the steps of: (1) Establishing a default PVC between a base station (1) and a base station controller (31) based on configuration information obtained by listening at the base station to messages from the base station controller (31); (2) initiating a BOOTP request at the base station (1) in broadcast mode, and sending the BOOTP request to an operation and maintenance center (51) or the base station controller host through the default PVC; (3) the operation and maintenance center (51) or the base station controller host sending a response to the base station (1), the response containing an IP address allocated to the base station (1); and (4) establishing an IPOA channel in accordance with the IP address and the default PVC after the base station (1) obtains the IP address allocated thereto, so as to establish the operation and maintenance channel between the base station (1) and the base station controller (31). 2. The method for establishing an IPOA channel-based operation and maintenance channels as claimed in claim 1, wherein in step (2), the sending of the BOOTP request to the operation and maintenance center (51) is implemented via the route of the base station controller (31). 3. The method for establishing an IPOA channel-based operation and maintenance channel as claimed in claim 1, wherein in step (2), the sending of the BOOTP request to the operation and maintenance center (51) to the base station (1) is implemented via the base station controller (31). 4. The method for establishing an IPO A channel-based operation and maintenance channel as claimed in claim 1, wherein in step (2), the BOOTP request initiated from the base station (1) includes the following fields: Packet operating code, designed to indicate BOOTP packet type; Hardware address type, designed to indicate hardware address type; hardware address length, designed to indicate hardware address length; hardware operation setting, designed to indicate number of gateways passed through; processing ID, designed to indicate whether the BOOTP request matches with its BOOTP response; elapsed seconds, designed to indicate time passed since startup from a client end; client IP address, designed to indicate client IP address; own IP address, designed to indicate client IP address filled in by a server; server IP address, designed to indicate server IP address filled in by the server; gateway IP address, designed to indicate passed gateway address; client hardware address, designed to indicate hardware address of the client end; optional server name, designed to indicate optional host name; boot file name, designed to indicate file name to be loaded; optional vendor domain, designed to indicate vendor-defined domain. 5. The method for establishing an IPO A channel-based operation and maintenance channel as claimed in claim 4, wherein it comprises the step of: in case the operation and maintenance center (51) is external to the base station controller (31), PVC information that identifies the base maintenance center (51) can identify the base station (1) that sends the BOOTP request.

Documents:

1008-delnp-2004-abstract.pdf

1008-DELNP-2004-Claims.pdf

1008-delnp-2004-complete specification (as. file).pdf

1008-delnp-2004-complete specification (granted).pdf

1008-delnp-2004-correspondence-others.pdf

1008-delnp-2004-correspondence-po.pdf

1008-DELNP-2004-Description (Complete).pdf

1008-DELNP-2004-Drawings.pdf

1008-delnp-2004-form-1.pdf

1008-delnp-2004-form-18.pdf

1008-DELNP-2004-Form-2.pdf

1008-delnp-2004-form-3.pdf

1008-delnp-2004-form-5.pdf

1008-delnp-2004-gpa.pdf

1008-delnp-2004-pct-210.pdf

1008-delnp-2004-pct-409.pdf

1008-delnp-2004-pct-416.pdf

1008-delnp-2004-petition-137.pdf