WO2009046681A1

WO2009046681A1 - Tracking method and device for base station

Info

Publication number: WO2009046681A1
Application number: PCT/CN2008/072620
Authority: WO
Inventors: Hua Cai; Mingjiang Xie; Shenghong Xu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-10-11
Filing date: 2008-10-08
Publication date: 2009-04-16
Also published as: CN101132648A

Abstract

A tracking method for base station is provided by the present invention. The method includes: receiving an invoke tracking message which comprises the ID of the tracking target and the content needing tracking; tracking the tracking target according to the tracking content, and obtaining corresponding tracking content. A base station and a communication system are also provided by the present invention. In the embodiment of the present invention, the relative tracking data can be collected at the base station, the tracking for the base station side information can be realized, and more comprehensive tracking information can be obtained, thereby, better failure locating and performance testing can be realized by using the obtained tracking information.

Description

Base station tracking method and device The present application claims priority to Chinese Patent Application No. 200710163884.2, entitled "Base Station Tracking Method and Apparatus", filed on October 11, 2007, the entire contents of which are incorporated by reference. In this application. Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a base station tracking method and device. Background technique

UMTS (Universal Mobile Telecommunications System) is a third-generation mobile communication system using WCDMA (Wideband Code Division Multiple Access) air interface technology. It is also called UMTS system as WCDMA. Communication Systems. The UMTS system uses a similar structure to the second generation mobile communication system, including RAN (Radio Access Network) and CN (Core Network). The RAN is used to handle all wireless related functions, and the CN handles all voice calls and data connections in the UMTS system and implements switching and routing functions with external networks. The CN is logically divided into CS (Circuit Switched Domain) and PS (Packet Switched Domain).

In the prior art, a UMTS system is shown in FIG. 1 and includes: UTRAN (UMTS Territorial Radio Access Network), CN and UE (User Equipment). The CN includes a MSC (Mobile Switching Center) / VLR (Visitor Location Register), a SGSN (Serving GPRS Support Node), and a GGSN (Gateway GPRS Support Node). ), HLR (Home Location Register) and GMSC (Gateway Mobile-services Switching Center). The UTRAN is a terrestrial radio access network, and the structure is as shown in FIG. 2, including one or several RNS (Radio Network Subsystem), and one RNS is controlled by an RNC (Radio Network Controller). One or more NodeBs (Node Base Stations). The interface between the RNC and the CN is the Iu interface, and the NodeB and the RNC are connected through the Iub interface. Within the UTRAN, the RNCs are interconnected through the Iur interface, and the Iur can be connected through a direct physical connection between the RNCs or through a transport network. The RNC is used to allocate and control the radio resources of the NodeB connected or related to it. The NodeB performs the conversion of the data stream between the Iub interface and the Uu interface, and also participates in some radio resource management.

The NodeB is a base station (i.e., a wireless transceiver) of a WCDMA system, including a wireless transceiver and baseband processing components. Through the standard Iub interface and RNC interconnection, the processing of the physical layer protocol of the Uu interface is mainly completed. The main functions include: spread spectrum, modulation, channel coding and despreading, demodulation, channel decoding, and mutual conversion of baseband and RF signals. The RNC is used to control the UTRAN's radio resources, and mainly performs connection establishment and disconnection, switching, macro diversity, and radio resource management control.

3GPP (3GPP Third Generation Partnership Project) For the purpose of fault location or performance testing, etc., the Subscriber (user) and the UE (User Equipment) are traced on the network side or the terminal side, for example, through IMSI. (International Mobile Subscriber Identification Number) identifies the tracking user and tracks the UE by IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version, IMEI Software Version). The tracked content includes: VIII, Iu-CS, Mc and MAP (Mobile Application Part) (G, B, E, F, D, C) interfaces in the MSC server; Gb, Iu-PS in the SGSN , Gn, MAP ( Gr, Gd, Gf ), CAP ( Ge ) and Gs interfaces; Gn and Gi interfaces in GGSN; Iu-CS, Iu-PS, Iur, Iub and Uu interfaces in RNC.

The tracking method is to form an Extensible Markup Language (XML) in the relevant network element (such as RNC), and then forward it to NM (Network Manager, Network) through Element Manager (Network Element Management). Network management), the tracking information is analyzed by NM.

Currently, the network side only tracks the UTRAN on the RNC network element, and collects information in related interfaces. The collected interfaces include Iu, Iub, and Iur. There are two ways to initiate the trace of the RNC: based on the management, directly send the Trace activation message to the RNC in the EM, or send the deactivation to the RNC; based on the signaling, the SG informs the SGSN to do the trace, and the SGSN passes the RANAP signaling CN. The Invoke Trace is sent to the RNC to activate the Trace function of the RNC; or the CN Deactivity Trace is used to activate the Trace function of the RNC.

In the process of implementing the present invention, the inventor has found that at least the following problems exist in the prior art: Since no information is collected on the NodeB, the RNC can only obtain the information about the NodeB through the NBAP (NodeB Application Part) signaling. The RNC side cannot obtain the information that is not in the NBAP signaling. Therefore, the information of the NodeB cannot be tracked well, and the tracking effect will be affected. Especially for HSDPA (High-Speed Downlink Packet Access) and HSUPA (High-Speed Uplink Packet Access) users (referred to as Η users), NodeB has a large management capability. The defect of tracking on the RNC side is more obvious. The above only uses WCDMA as an example, but similar problems exist in other systems. Summary of the invention

The embodiment of the invention provides a base station tracking method and device, so as to collect relevant tracking information at the base station, so that the tracking is more comprehensive and effective.

The embodiment of the invention provides a base station tracking method, including:

Receiving an activation tracking message, where the activation tracking message includes an identifier of the tracking target and content that needs to be tracked;

And tracking the tracking target according to the activation tracking message to obtain corresponding tracking content.

The embodiment of the invention further provides a base station, including:

An activation module, configured to trigger a tracking module when receiving a tracking request message, where the activation is followed by The trace message includes the identifier of the tracking target and the content to be tracked;

The tracking module is connected to the activation module, and is configured to track the tracking target to obtain corresponding tracking content.

The embodiment of the invention further provides a communication system, including the foregoing base station.

Compared with the prior art, the embodiment of the present invention can collect related tracking data at the base station, implement tracking of information on the base station side, and obtain more comprehensive tracking information, so that the obtained tracking information can be utilized to better achieve fault location and performance. test. DRAWINGS

1 is a structural diagram of a UMTS system in the prior art;

2 is a structural diagram of a UTRAN in the prior art;

FIG. 3 is a flowchart of a method for performing signal tracking in a base station according to an embodiment of the present invention; FIG. 4 is a flowchart of another method for performing signal tracking at a base station according to an embodiment of the present invention; FIG. Base station structure diagram. detailed description

The main working process of the base station tracking method in the embodiment of the present invention is as shown in FIG. 3, and includes the following steps:

Step s301: The base station receives an activation tracking message.

The activation tracking message includes the identifier of the tracking target and the content that needs to be tracked. Tracking targets include: one or more of a user, a cell, an interface, a device in a base station, and an entire base station. The devices in the base station include: a DSP (Digital Signal Processing) chip, a CPU, an antenna, and the like. Correspondingly, the identifier of the tracking target includes: a user identifier, such as IMSI and IMEI, etc.; a cell identifier; an interface sequence number; a hardware identifier of the device in the base station; a base station identifier, and the like.

The base station can be applied to a universal mobile communication system UMTS, LTE (Long Term Evolution, Long Term Evolution Access Network) or HSPA+ (High Speed Package Access plus). When applied to UMTS, the base station is a NodeB. It receives an activation tracking message from the RNC through the lub interface; when applied to the CDMA system, the base station is a BTS (Base Transceiver Station), the base station controller is a BSC (Base Station Controller), and the BTS is from the BSC. Receiving the activation tracking message; when applied to LTE or HSPA+, the base station receives the activation tracking message from the upper node (for example, the core network) or the network element network management system and the network network management device, and does not need to communicate through the lub interface.

Step s302: The base station tracks the tracking target according to the activation tracking message, and acquires the tracking data.

As mentioned earlier, the activation tracking message includes the identifier of the tracking target and the content that needs to be tracked. For example, the base station learns that the tracking target is the user equipment A according to the identifier of the tracking target, and learns that the uplink channel power of the user equipment A needs to be tracked according to the content that needs to be tracked, and the base station collects the uplink channel power of the user equipment A. In this way, the tracking content that meets the tracking requirements is obtained.

Step s303: The base station reports the obtained tracking data to the network element network management system or the network network management system. In this embodiment, the indication is reported to the network element network management system or the network network management system, and may be reported to other tracking processing functions. Network element.

In this step, the tracking content that can be applied to only one device can be reported to the EM (Element Manager) of the device. The tracking content applicable to the entire system can be reported to the EM of the device. It can be reported to the network management system ( NM: Network Manager ) „ where the network element network management manages a single device. The network network management device can not only directly report the tracking content to the network management system, but also report it to the network management system through the network element network management.

In this step, different reporting methods can be used. For example, real-time or timed reporting. The real-time report is specifically as follows: According to the acquired tracking data, a tracking report message is generated, and the generated tracking report message is sent to the network element network management or the network network management in real time. At the timing, "^ is specifically: obtaining tracking data, generating a tracking data file, and periodically detecting the data file. When the size of the data file exceeds a predetermined threshold, the network data management or network network management is performed on the network element. Of course, Set the reporting period (can include multiple detection cycles), if in one During the reporting period, if the size of the data file obtained by the multiple times of the detection does not exceed the predetermined threshold, the data file is reported to the network element network management system or the network network management system at the end of the reporting period.

It can be understood that, when the technical solution provided by the embodiment of the present invention is applied to the UMTS, the base station can also report the tracking content to the network element network management system or the network network management system through the radio network controller (RNC), specifically: the base station acquires the corresponding tracking. After the content, the tracking content is sent to the RNC, and the RNC generates a tracking report message according to the tracking content, or reports the data file to the network element network management or the network network management. In addition, when applied to a CDMA system, the tracking content can also be passed through the BSC.

The UMTS system is used as an example to describe the method for tracking the base station. In this embodiment, the object to be tracked is the user equipment UE. As shown in Figure 4, the method includes the following steps:

Step s401: The RNC sends an activation tracking message to the NodeB by using NBAP signaling. In the solution provided by the embodiment of the present invention, the tracking task of the base station is activated based on the signaling manner. For example, the RNC may use the existing NBAP signaling (such as public measurement information, dedicated measurement messages, etc.), or newly create a separate signaling RNC Invoke Trace through the RNC, and notify the NodeB to prepare to track Trace; or modify the existing one. NBAP signaling message body structure (such as common measurement information, dedicated measurement messages, etc.) to support activation of NodeB tracking tasks.

The RNC Invoke Trace message includes: The message includes the identifier of the tracking target and the content to be tracked. The identifier of the tracking target is mandatory. For example, when the related information of a user needs to be tracked, the IE (Information Element) of the user is the UE identifier of the tracking target. The identifier of the tracking target may be a CRNC Communication Context ID, or an identifier of the user's IMSI or IMEI.

The content of the tracking target is mandatory. The content to be tracked includes: user equipment, cell, interface, non-signaling interface information, and non-standard information tracking; for example, tracking the interface information of the user who specifies the identifier.

The RNC Invoke Trace message may further include: a tracking reference IE, configured to uniquely determine the specified tracking session, which is optional;

The RNC Invoke Trace message may further include: tracking transmission parameter IE (optional), This parameter is used to pass tracking commands to other NodeBs for signal tracking. Wherein, the tracking transmission parameter IE includes a tracking record content reference IE, which is allocated by the CN;

The RNC Invoke Trace message can also include: Tracking depth IE, which defines the level of detail of the content tracked in the RNC.

Step s402: The NodeB reads the RNC Invoke Trace signaling, and performs parameter validity check.

In this step, if the parameter validity check fails, or the NodeB does not support the RNC Invoke Trace signaling, go to step s403; if the parameter is valid, go to step s404.

Step s403, return RNC INVOKE TRACE FAILURE to the RNC.

Step s404: The NodeB reads the UE identifier of the RNC Invoke Trace signaling.

Step s405: Determine whether the user corresponding to the UE identifier is in an active state, if the user is not activated, go to step s406; if it is activated, go to step s407.

Step s406, return RNC INVOKE TRACE FAILURE to the RNC.

Step s407: The base station starts NodeB Trace to obtain tracking data.

In this step, if the tracking depth IE is included in the RNC Invoke Trace message, the NodeB Trace can be started according to the definition of the Trace Depth IE. The tracking depth determines how much content is tracked. For example, if the tracking depth is advanced, a large amount of content can be tracked. With a low tracking depth, you only need to track a small amount of content. It can be understood that when a user is activated (for example, the wireless link is removed), if the user Trace function is started, the user Trace function is stopped.

Step s408: The base station reports the obtained tracking data.

As mentioned earlier, there are many ways to do this. For example:

Method 1: Real-time reporting. The NodeB forms a tracking report message based on the acquired tracking data. Each tracking report message is reported by the NodeB to the NodeB's network element network management (NM) in real time.

Method 2: Conditional reporting.

This condition can be: A threshold value set for the data file. Of course, it is also possible to set a reporting period (which may include multiple detection periods). If the data file size obtained by multiple timing detections does not exceed a predetermined threshold in a reporting period, then the reporting is performed. The data file is reported to the NE or network management system at the end of the period.

Based on the acquired tracking data, the NodeB forms a tracking data file, such as an XML file. When the size of the data file exceeds the preset threshold, it is reported by the NodeB to the network element network management (NM) of the NodeB through the FTP (File Transfer Protocol). The NodeB is used as the FTP client and the NM is the FTP server. Further, in order to reduce the occupation of the transmission bandwidth of the NM and the NodeB by the tracking FTP data transmission, the tracking data file may be compressed first and then uploaded on the NodeB side, and there are many mature methods for file compression, such as bz2, winzip. Compression method, etc.

It can be understood that the technical solution provided by this embodiment may further include a step of deactivating:

Step s409, the RNC informs the NodeB to cancel the tracking by using the NBAP signaling mode. Similar to step s401, the RNC can use the existing signaling or notify the NodeB to deactivate by newly creating a separate signaling RNC Deactivate Trace. Similarly, the RNC Deactivate Trace signaling may also include the UE identifier, and the NodeB reads the UE identifier. If the user corresponding to the UE identifier is activated, the Trace function of the user is stopped. If the user is not activated, no action is performed. deal with.

In the above solution, information is collected at the NodeB and then sent directly to the EM or NM. In addition, the tracking data obtained by the NodeB can be sent to the RNC in the form of tracking information, and then the tracking function data is processed by the RNC Trace function entity, and then sent to the EM or NM.

The NodeB can send tracking information to the RNC through NBAP signaling. In a specific implementation manner, similar to the foregoing, the method includes using new independent signaling and utilizing existing NBAP signaling (such as common measurement information, dedicated measurement messages). The new signaling is specifically as follows: The NodeB sends the RNC to the Trace Info Report message.

With the technical solution provided by the embodiment of the present invention, related tracking data can be collected at the base station to track the information of the base station side, so that the tracking is more comprehensive and effective. For example, in the UMTS system, information on the NodeB side that the current RNC cannot track can be tracked. In particular, for HSDPA, HSUPA, etc., the management capability of the NodeB is large, and the defect that can only be tracked on the RNC side is more obvious. For example, when the RNC only allocates a range of code resources to The NodeB cell dynamically allocates code resources to the user by the NodeB. If there is a problem that the user complains that the data transmission rate is not high, for example, the quality of the air interface of the user is poor, and the allocated code resources are few. This can only be seen in the NodeB. The tracking information on the RNC side cannot reflect the cause. The solution provided in this embodiment can make up for similar defects. In the scenario where the control function of the NodeB is large, more comprehensive tracking information can be obtained, so that the obtained tracking information can be utilized to better implement fault location, performance testing, and network optimization. Wait.

The NodeB will report the acquired tracking data and send it to the EM or NM after being processed by the RNC. Compared with the previous solution, it is not necessary to cache a large amount of tracking data in the NodeB, form an XML file, and send it to the EM and NM. It only needs to send the tracking data to the RNC in time, let the RNC handle the saving and sending, and utilize the functions of the existing RNC tracking entity to further reduce the burden on the NodeB.

It can be understood that, in the first embodiment, the tracking UE is taken as an example, but the present invention is not limited thereto, and the cell, the interface, the non-signaling interface information, and the non-standard information may also be tracked. Correspondingly, the tracked content may include: UE information, cell information, interface information, and the like. For example, the NBAP dedicated measurement message can be used to report more UE information to the RNC. The cell measurement information of the cell is reported to the RNC by using the cell measurement message of the NBAP. The following is a brief list of the differences in technical solutions when tracking different objects.

1. The tracking object is UE:

If the NodeB is tracking for a certain UE or some UEs, it needs to carry the UE identifier, such as CRNC Communication Context ID, IMSI, IMEI and other identifiers. The tracked content is the base station side data associated with the UE.

2. The tracking object is a cell:

If the NodeB is tracking for a certain cell or some cells, it should carry the cell ID identifier. In addition, it can also carry information of the tracking cell, such as the number of cell users and the use of CE (Channel Element). The CE consumption can be obtained by tracking, such as the total number of uplink CE points, the total number of downlink CE points, the consumption of uplink CE points, the consumption of downlink CE points, the consumption of uplink CE points in the cell, and the consumption of downlink CE points in the cell. congestion.

3. The tracking object is the interface: If the NodeB tracks the interface message between the Iub, Iuant, or Iutma signaling, the base station baseband unit (BBU), and the radio remote unit (RRU), the corresponding interface enable information may be carried in the activation message. Similar to the CN Invoke Trace message. For example, RNC Invoke Trace may contain IE type and parameter fields as shown in Table 1: Used to indicate which interface is tracked. Among them, Iuant is the interface of NodeB to the antenna, and Iutma is the interface of NodeB to Tower Mounted Amplifier (TMA).

4. The tracking object is non-signaling interface information:

Because of the implementation, Trace is currently targeting signaling information of some standard interfaces, but not internal information of network elements. In fact, a lot of information is independent of the implementation, such as the information of the NodeB for the HSDPA user, the CQI (Channel Quality Indicator) information reported by the user, and the Ack/Nack number of the user feedback. As mentioned above, when the RNC allocates only one code resource range to the NodeB cell, the NodeB dynamically allocates the code resource to the user. If there is a problem that the HSDPA user complains that the data transmission rate is not high, it may be due to the poor quality of the user's air interface, which causes little code resources to be allocated. This can only be seen in the NodeB, but it is not reflected in the Iub interface. Therefore, non-signaling interface information can be tracked.

Specifically, the trace information of the NodeB may further include the following information: For example, for the interface between the RNC and the NodeB, the information that can be obtained through tracking is: the total number of FP packets received by the NodeB, and the total number of discontinuous FP packets received by the NodeB. The total number of FP packets discarded by the NodeB and the error rate of the physical link (E11/STM-1). You can determine if the Iub interface is normal.

The trace information of the cell may further include: a time ratio of the cell having the HSDPA user, a time ratio of the cell having the HSDPA user data, a cell HS-SCCH code utilization rate, a cell HS-PDSCH code utilization rate, and a cell HSDPA MAC-HS average throughput. Rate, cell HSDPA average power, cell HSDPA timeout data discard rate, cell Iub bandwidth usage rate, cell current HSDPA or HSUPA user number, domain type - user HSDPA information, domain length, etc., and average rate of HSDPA users, the user CQI The number of times from 0 to 5, the number of times the user CQI is 6 to 10, the number of times the user CQI is 11 to 15, the number of times the user CQI is >16, the average CQI of the HSDPA user, and the total number of ACKs of the HSDPA user The total number of NSKs for HSDPA users and so on.

5. The tracked object is non-standard information:

For non-standard information, such as which UE has a digital signal processing DSP chip, it belongs to the operator-related information. Since the information itself is not standardized, it will not be described in further detail here.

The second embodiment of the present invention uses a flat architecture HSPA+ system as an example to describe a base station tracking method. Understandably, the LTE system is similar. For the sake of simplicity, the following description is only focused on HSPA+.

In the flat architecture HSPA+ system, the flow of the base station tracking method is substantially the same as that of the first embodiment. The difference is: In the flat architecture HSPA+ system, the base station is an eNodeB (evolved NodeB), and there is no RNC connected to the base station through the Iub interface in the system, and the tracking activation message is sent by the upper node (for example, the core network CN, ) or the network element. The network management or the network management system provides the corresponding content of the Iub interface in the tracking message. The other tracking content is the same as that tracked in the first embodiment, and is not described here. In addition, the base station reports to the network network management system or the network element network management system, or reports the upper layer node to the network network management system or the network element network management system.

The content of the interface information that may not be standard includes, for example, some for the UE, some for the cell, some for the entire base station, and some may be interfaced between the LTE base stations (X2) or HSPA+. Interface between base stations (Iur + ) Up and down transmission.

The tracking information of the UL PHY (Up Link Physical Channel) includes: Received total power, which refers to the total power received by the total system bandwidth of each cell, including thermal noise; IoT (Interference power) Over thermal noise power, the ratio of the power of the noise to the thermal noise power, for each cell's system bandwidth or some frequency bandwidth; SIR

(Signal-to-Interference Ratio), the ratio of the received reference signal power to the interference power noise, for each UE, each sub-frequency bandwidth, the reference signal pair HSPA + is the SIR of the pilot channel; Received total Power on RBs for PRACH, the total power of the RB (Resource Block) received on the Physical Random Access Channel (PRACH), which is a measurement for one cell, which can be all of a cell. The average value of PRACH; Fading frequency refers to the Doppler frequency attenuation, which is for one UE.

The DL PHY (Down Link Physical Channel) tracking information includes: Transmitted carrier power, which is the ratio of the total transmit power to the maximum transmit power of the cell, used to observe the congestion level of the cell; Transmitted power Per RB, the transmit power of each resource block (RB), which can be averaged to calculate inter-cell interference, needs to be transmitted at the interface (X2) between the eNBs.

The tracking information for the UL Link (Uplink Media Access Control) includes: Usage reported per RB for UL-SCH, and the measurement of the usage of each resource block of the uplink shared channel of each cell can be used. Calculate the congestion level of the cell; UL MAC PDU throughput per logical channel, per radio bearer type or MAC PDU throughput (bits per second or bit) in the uplink direction of each cell, can be used as a key performance indicator To ensure QoS (Quality of Service) and to evaluate system efficiency; the BLER (Block Error Ratio) of the UL BLER uplink MAC PDU can take the average value of each logical channel and can be used to discover network problems; Rate of UL MAC PDU failures due to exhausing max number of

The failure rate of the HARQ retransmission UL MAC PDU can be used to discover the network problem because the number of HARQ retransmissions reaches the maximum allowable value; Num. of received RACH preambles, the RACH preamble received by the cell for a period of time to detect the load of the random access channel (RACH); Num. of logical channels whose UL throughput is smaller than the required UL, the throughput is less than the required amount Also edit the number of channels for admission control.

The DL MAC (Down Link Media Access Control) tracking message includes: Usage reported per RB for DL-SCH, and the measurement of the usage of each resource block of the downlink shared channel of each cell may be used. Calculate the congestion level of the cell; DL MAC PDU throughput, each logical channel, each radio bearer type or the MAC PDU throughput (bits/sec or bit) in the downlink direction of each cell, can be used as a key performance indicator. Used to guarantee QoS and evaluate system efficiency; BER BLER downlink MAC PDU block error rate (BLER), which can take the average of each logical channel, can be used to discover network problems; Rate of DL MAC PDU failures due to exhausing max number Of HARQ retransmission DL MAC PDU failure rate - can be used to discover network problems due to the maximum allowable number of HARQ retransmissions; Num. of discarded DL MAC PDU due to cell change DL , discarded MC PDU due to cell Change (can be divided into two cases between eNB and eNB) for observing handover performance and optimizing handover control Num. Of logical channels whose DL throughput is smaller than the required DL, is also less than a certain number of channels, Series required amount for admission control.

The tracking message for the UL RLC (Up Link Radio Link Control) includes: Residual error rate provided from UL MAC, error rate of uplink MAC: Lost PDU/(Lost + Received PDU), used In the detection of whether the UL HARQ is in the desired operating state; Num. of UL resets UL RLC, the statistics of the number of physical resets - used to determine whether the system is functioning properly during a certain measurement interval.

The DL RLC (downlink radio link control layer) tracking message includes: Amount of buffered data, the amount of buffered data held by the base station, which can be per logical channel, per cell, and each type of radio bearer. The measurement may be used to adjust the buffer size of the base station; Num. of logical channels having buffered data, the number of logical channels having buffered data, may be based on a cell, based on a period of time Measured by the interval, it can be used to observe the congestion degree of the cell; Average num. of DL retransmissions, the average number of downlink RLC layer retransmissions, measured based on the average value of each logical channel and one cell, can be used for retransmission of RLC Parameter configuration: for example, the maximum number of retransmissions, the discarding time; Num. of DL resets DL RLC, the statistics of the number of physical resets - used to determine whether the system is functioning properly during a certain measurement interval;

Average DL RTT, Average RLC DL Round Trip Time: The time from when the network sends the RLC PDU to the received acknowledgment frame, which can be used to optimize the ARQ timer parameters of the RLC; Amount of data forwarded, from the source when switching The amount of data transferred by the base station to the target base station can optimize the bandwidth of the inter-base station interface (X2 interface).

The RRC & others (Radio Resource Control or Other) tracking message is mainly used to determine the load status of the system - in units of cells or base stations, including: Num. of RRC connected users, the number of UEs currently in the RRC connection state; Num Of call arrival, number of calls allowed; Num. of admitted calls, number of allowed calls; Rate of admitted calls, rate of allowed calls; Rate of PCH transmission, transmission rate of paging channels; Num. of triggered intra-frequency HO, the number of intra-frequency handovers; Num. of completed intra-frequency HO, the number of completed frequency handovers; Num. of triggered inter-frequency HO, the number of inter-frequency handovers; Num. of completed inter-frequency HO, inter-frequency handover Number of completions; Num. of triggered inter-RAT HO, number of handovers between different radio access technologies; Num. of radio link failure, number of radio consecutive failures; Num. of triggered inter-eNB HO, handover between base stations Number; Num. of completed inter-eNB HO, the number of handovers between base stations.

The embodiment of the present invention further provides a base station, as shown in FIG. 5, including: an activation module 10, configured to trigger a tracking module 20 when receiving a tracking request message, where the activation tracking message includes an identifier of the tracking target and content that needs to be tracked; The tracking module 20 is connected to the activation module 10 for tracking the tracking target to obtain corresponding tracking content. The deactivation module 30 is connected to the tracking module 20 for receiving the deactivation request, and the instruction tracking module 20 Stop tracking of the tracking target; track content on module 40, with the tracking The module 20 is configured to report the acquired tracking content to the network element network management system, the network network management system, or the network element with the tracking processing function, where the network element with the tracking processing function is the RNC in the UMTS system and the BSC in the CDMA system. .

The tracking content specific module 40 includes: a message generation sub-module for generating a report message for the tracking content; a report message sending sub-module, when the tracking content is sent to the network element network management system or the network network management system And is connected to the report message generation submodule, and is used for reporting the report message.

The tracking content reporting module 40 may further include: a data file generating submodule, configured to generate a data file for the tracking content; a determining submodule, connected to the data file generating submodule, for determining a data file size; and a data file reporting submodule, The data file generating sub-module and the determining sub-module are respectively connected, and are used for judging that the sub-module determines that the data file size exceeds a predetermined threshold, and reports the data file; the compression sub-module, and the data file generating sub-module and the data file reporting sub-subs Module connection, used to compress data files before reporting.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

In the embodiment of the present invention, related tracking data can be collected at the base station to track the information of the base station side, so that the tracking is more comprehensive and effective. In addition, the base station may report the tracking data to the network network management or the network element network management, or may first send the network element with the tracking processing function to the network controller, and then the network element processes the network element, and then sends the data to the network element network management system or the network. The network management, without buffering a large amount of tracking data at the base station, further reduces the burden on the base station.

The above disclosure is only a few specific embodiments of the present invention, but the present invention is not limited thereto, and any changes that can be considered by those skilled in the art should fall within the protection of the present invention.

Z9Z.0/800ZN3/X3d Ϊ899 Art OOZ OAV

Claims

Rights request

A base station tracking method, comprising:

2. The base station tracking method according to claim 1, wherein the obtaining the corresponding tracking content further comprises:

Generating a tracking message according to the tracked content;

The tracking report message is reported to the network element network management system or the network network management system in real time.

The base station tracking method according to claim 1, wherein the obtaining the corresponding tracking content further comprises:

Generating the data file by the tracking content;

The data file is detected, and when the data file size exceeds a preset threshold, the data file is reported to the network element network management system or the network network management system.

The base station tracking method according to claim 1, wherein after receiving the activation tracking message, the method further comprises:

Receive a deactivation message to stop tracking the tracking target.

The base station tracking method according to claim 1, wherein before the tracking the tracking target, the method further comprises:

A parameter validity check is performed, and if it is passed, it is judged whether the tracking target is activated, and if so, the tracking of the tracking target is started.

The base station tracking method according to any one of claims 1 to 5, wherein the activation tracking message further includes: one or more of a tracking reference IE, a tracking transmission parameter IE, and a tracking depth IE. .

The base station tracking method according to any one of claims 1 to 5, wherein the tracking target comprises: one or more of a user, a cell, an interface, a device in a base station, and an entire base station.

8. The base station tracking method according to claim 7, wherein when applied to a universal mobile communication system UMTS or a code division multiple access CDMA system, an activation tracking message is received by the network controller to obtain corresponding tracking content. The method further includes: sending the tracking content to the network controller, where the network controller generates a tracking report message according to the tracking content, or reports the data file to the network element network management or the network network management;

When applied to the Long Term Evolution Access Network (LTE) or High Speed Packet Access Enhanced HSPA+, the activation tracking message is received by the upper node or the network element network management or the network network management.

The base station tracking method according to claim 8, wherein when applied to UMTS,

The content of the cell tracking includes: the number of cell users, the total number of uplink channel units, the total number of downlink channel units, the consumption of uplink channel unit points, the consumption of downlink channel unit points, the consumption of uplink channel unit points of the current cell, and the downlink channel unit of the current cell. One or several of the points consumed;

The content of the interface tracking specifically includes: Iub interface signaling received and sent by the base station, Iuant interface message of the base station and the antenna, Iutma interface message between the base station and the tower amplifier, the base station baseband unit and the radio remote unit One or several of the inter-interface messages;

The content of the non-signaling interface specifically includes: one or more of the information of the base station for the high-speed downlink packet access HSDPA, the channel quality indication CQI information reported by the user, the number of ACK/NACKs fed back by the user, and the Iub interface information;

The content of the non-standard information specifically includes: a digital signal processing DSP chip of the service of the user equipment.

The base station tracking method according to claim 8, wherein when applied to the long-term evolution access network LTE or the high-speed packet access evolution network HSPA+,

The content of the cell tracking includes: number of cell users: total number of uplink channel units, total number of downlink channel units, consumption of uplink channel unit points, consumption of downlink channel unit points, consumption of uplink channel unit points of the current cell, and downlink channel unit of the current cell One or several of the points consumed; The content tracked by the interface specifically includes: one or more of an interface message between the base station and the antenna, an interface message between the base station and the tower amplifier, and an interface message between the base station baseband unit and the radio remote unit;

The content of the non-signaling interface includes: one or more of the information of the base station for HSDPA, the CQI information reported by the user, and the number of ACK/NACKs fed back by the user; the content of the non-standard interface includes: uplink physical channel information, One or more of downlink physical channel information, uplink medium access control layer information, downlink medium access control layer information, uplink radio link control layer information, downlink radio link control layer information, and radio resource control information.

A base station, comprising:

The activation module is configured to trigger a tracking module when receiving the tracking request message, where the activation tracking message includes an identifier of the tracking target and content that needs to be tracked;

The base station according to claim 11, further comprising:

Deactivating the module, connecting with the tracking module, and after receiving the deactivation request, instructing the tracking module to stop tracking the tracking target.

The base station according to claim 11, further comprising:

The tracking content reporting module is connected to the tracking module, and is configured to send the obtained tracking content to the network element network management system, the network network management system, or the network element with the tracking processing function.

The base station according to claim 13, wherein the tracking content reporting module specifically includes:

The report message generating sub-module is configured to generate the report message by using the tracking content, and the report message sending sub-module is connected to the report message generating sub-module for reporting the report message.

a data file generating submodule, configured to generate a data file by using the tracking content, and a determining submodule, connected to the data file generating submodule, for determining the number According to the file size;

The data file reporting sub-module is respectively connected to the data file generating sub-module and the determining sub-module, and is configured to report the data file when the determining sub-module determines that the data file size exceeds a predetermined threshold.

A communication system, comprising the base station according to any one of claims 11 to 15.