CN1662089A - Method and equipment for treating and analyzing running or tested data in mobile communication system - Google Patents
Method and equipment for treating and analyzing running or tested data in mobile communication system Download PDFInfo
- Publication number
- CN1662089A CN1662089A CN 200410006351 CN200410006351A CN1662089A CN 1662089 A CN1662089 A CN 1662089A CN 200410006351 CN200410006351 CN 200410006351 CN 200410006351 A CN200410006351 A CN 200410006351A CN 1662089 A CN1662089 A CN 1662089A
- Authority
- CN
- China
- Prior art keywords
- base station
- message
- station controller
- signaling
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
A signaling analyzer adopted in the disclosed device is in use for monitoring one or more base station, and incoming and outgoing signaling between base station controller and a mobile exchange center, and storing analyzed results to local memory of the analyzer. Then, computer analyzes result (success, failure and where) of each call event (updating location, calling process, short message and switching etc.) in system automatically. Individual signaling record is separated for each single event, and visual signaling flow chart is drawn for each event to make result clear. In use for receiving signals of each base station and mobile exchange center, the base station controller controls operation of each base station.
Description
(1) technical field
The present invention relates to a kind of mobile communication system collection, processing and automatic analysis method and device to data when operation or test, more particularly, relating to a kind of mobile communication system gathers, analyzes test data when operation or test, export the result selectively, to help to judge the method and apparatus of the operation troubles that may exist.
(2) background technology
The prior art network configuration of mobile communication is formed as shown in Figure 1.
The GSM term of air interface is in the Um mouth, and the UMTS term is in the Uu mouth; Abis interface is the interface between base station and base station controller, and wherein, Abis is the GSM term, UMTS term Iub interface; The A interface is the GSM term of the interface between base station controller and mobile switching centre, and its UMTS term is the Iu interface.
For sake of convenience, the present invention is that example is illustrated the invention scheme in many places with the gsm system, therefore interface terms that adopt gsm systems more.Need to prove that in fact this when the present invention adopts other system, should change corresponding other interface name to relevant interface name just for sake of convenience.
In the development and running of mobile communication system, need do the complexity test of heavy load test, multi-user test or other types to system, with the operation conditions of checking system, comprise performance, compatibility, stability and anti-overload ability etc.When doing this class testing, need dial tens to hundreds and thousands of phones.The log file of consequent message flow (LOG file) may reach the hundreds of Mbytes.When making a mistake in the test, need find erroneous point, the reason of mistake, and wrong context.And the manual file of analyzing the hundreds of Mbytes that existing technology is adopted is both to have wasted time and energy, the work of poor efficiency again.In the actual system that puts into operation, this to the faults analysis disposal ability be difficult to gratifying.
(3) summary of the invention
At the deficiency of prior art, the invention provides a kind of analytical method of analyzing the mobile communication system working condition.This method is utilized computer technology, the correlation of the message that connects according to same call, automatically the analytic record file when finding mistake, is given all information that make mistake in analysis result, and, the file of Mbytes up to a hundred is decomposed, each is called out the related news that connect be put in the independent file, and can selectively filter out some unessential message, as: measurement report message makes further problem analysis easily simple more.In addition, can also be according to different base stations, different call events, the corresponding flow chart that draws makes more visualize of problem analysis.
In the present invention, call event refers to that in moving communicating field the incident relevant with calling comprises caller phone, called phone, position renewal, switching, short message etc.
Specifically, the invention discloses in a kind of mobile communication system the method that operation or test data are handled and analyzed, the work or the test mode of system analyzed, comprising:
Adopt at least one base station, a base station controller, a Signaling Analyzer and a mobile switching centre, Signaling Analyzer has a memory, is used for the stored record file; Described base station controller is used for receiving respectively the signal of each base station, mobile switching centre, and can control the work of each base station, Signaling Analyzer monitoring and the contact signaling between each base station and base station controller, base station controller and the mobile switching centre of decoding record monitoring result in the file of local storage (being generally local hard drive) then; The said equipment is gathered selectively, sorts out, is analyzed and export the work of system or operation or test data, comprises the following steps:
(1) to the running parameter of analytical system input system and other data that need analyze: by the log file of Signaling Analyzer record, interface link configuration information between base station and the base station controller be can also import in addition, interface up link title and down link title between base station title, base station and the base station controller comprised;
(2) needs of analyzing according to running situation, Signaling Analyzer is analyzed following parameters of operation process at least: time mark that Signaling Analyzer write down and link name, interface message between base station that all are relevant with calling out connection and the base station controller, interface message between base station controller that all are relevant with calling and the mobile switching centre;
(3) according to top analysis result, Signaling Analyzer is exported following three class files at least: call out threaded file, public message file and summary info table, use when the system works situation is analyzed.
The invention also discloses another kind of method, also be included as each calling connection based on the above method and produce an independent calling threaded file respectively, described public message file comprises broadcast channel information and call information at least, described summary info table provides delegation for each calling connects and comprises the information of calling out master data, and described information comprises information relevant with mistake when making a mistake at least.
According to another aspect of the present invention, also comprise when making a mistake in the region parameter cell of mobile switching centre's side that signalling system No.7 is connected on the interface between the region parameter cell of the side of base station controller that signalling system No.7 is connected on the interface between the down link title of interface between the up link title, base station that also comprises interface between the error message that call out to connect, base station and the base station controller in the abstract and the base station controller, base station controller and the mobile switching centre, base station controller and the mobile switching centre, the called number one or multinomial.
According to another aspect of the present invention, also comprise comprising time started of call out connecting in the abstract, calling out the concluding time, the Radio Resource that connect and connect in the release information that ID, System Frame Number, caller identities number, type of call, calling connect one or multinomial.
According to another aspect of the present invention, the analytic process of the inventive method is further comprising the steps of:
(1) finds out related message and belong to which base station;
(2) judge which message belongs to and call out connection;
(3) message is outputed in the corresponding file;
(4) select Useful Information, output to the summary info table.
According to another aspect of the present invention, the analytic process of the inventive method also comprises:
(5) according to above step gained result, signaling process figure draws;
(6) in flow chart, replenish the caller identities number of interface message between base station and the base station controller.
The invention also discloses in a kind of mobile mobile system the device that operation or test data are handled and analyzed, be used for the operation or the test data of system are gathered selectively, sort out, analyzed and export, comprising:
(1) one or more base stations link to each other with following base station controller respectively, link to each other with following Signaling Analyzer respectively simultaneously;
(2) base station controllers link to each other with above-mentioned each base station, following Signaling Analyzer and following mobile switching centre respectively, and be used for receiving respectively the signal of each base station, mobile switching centre, and can control the work of each base station,
(3) mobile switching centres link to each other with following Signaling Analyzer with described base station controller respectively,
(4) Signaling Analyzers, respectively with above-mentioned each base station, base station controller links to each other with mobile switching centre, be used for monitoring in the following manner and decoding each base station and base station controller, contact signaling between base station controller and the mobile switching centre, then monitoring result is recorded in the file of following local storage: respectively to running parameter and other data that need analyze of the analytical system input system of Signaling Analyzer, comprise log file by the Signaling Analyzer record, and interface link configuration information between base station and the base station controller, comprise the base station title, interface up link title and down link title between base station and the base station controller; According to the needs that running situation is analyzed, time mark of analyzing Signaling Analyzer at least and being write down and link name, all connect interface message between interface message between relevant base station and the base station controller, base station controller that all are relevant with calling and the mobile switching centre with calling out; And according to top analysis result, following three class files of output at least: call out threaded file, public message file and summary info table, use when the system works situation is analyzed;
(5) local storages link to each other with above-mentioned Signaling Analyzer, are used for the log file of storage system.
(4) description of drawings
The network structure of prior art in the mobile communication has been shown among Fig. 1.
Fig. 2 is the schematic network structure that has comprised the present invention program.
Fig. 3 is the schematic diagram of Signaling Analyzer configuration in apparatus of the present invention.
Fig. 4 shows an example of message flow graph model in the inventive method.
Fig. 5 shows an example of summary info table in the inventive method.
Fig. 6 is a schematic diagram of analytic process in this method method.
A concrete instance of flow chart model output in the inventive method has been shown among Fig. 7.
(5) embodiment
Specifically, the inventive method comprises two parts.
First is the generation and the record of signaling.
This method adopts a Signaling Analyzer to monitor one or more base stations, a base station controller and the wireless communication system that mobile switching centre forms.Signaling Analyzer has a local storage (for example one or more local hard drives, or the known memory of other technical staff), is used for the stored record file; Signaling Analyzer writes down each base station and base station controller, the contact signaling of base station controller and mobile switching centre, and in the file of outcome record to the Signaling Analyzer local storage.Signaling Analyzer of the present invention also comprises an analytical system at least, according to (this setting can be revised) pattern or the algorithm set relevant data is analyzed.
Fig. 2 is the schematic network structure that has comprised the present invention program.
Before beginning, need the configuration signal analyzer: on Signaling Analyzer,, provide the configuration of up link title and down link title and other Signaling Analyzer requirements respectively to the interface link between each base station and base station controller, as, protocol stack etc.For a plurality of base stations situation, the uplink downlink title of each base station must be unique, and this point is very important for later analysis.For example, for base station 1, the uplink downlink title can be taken as: BTS1-〉BSC and BSC-〉BTS1, for BTS2, can be taken as: BTS2-BSC and BSC-BTS2.
Fig. 3 is the Signaling Analyzer configuration schematic diagram.
Like this, when carrying out the Bulk Call operation or carrying out a complicated test, as, the Bulk Call test, multi-user test, switch tests etc. on the local storage of Signaling Analyzer, will produce a very big log file.This log file has write down all base stations and base station controller, the contact signaling between base station controller and mobile switching centre.These signalings may comprise hundreds and thousands of call events.Here, call event can be the calling that mobile phone is initiated, and mobile phone is done called calling, and the position is upgraded, and switches all-calls business such as short message.Down together.
For the message of each bar record, Signaling Analyzer has write down following content:
1) time mark of the transmission of this message (Time Stamp) is accurate to Millisecond
2) message is sent out the logical links title (LinkName) of the circuit at place
3) protocol information (Protocol) of this message employing, as, LAPD or signalling system No.7
4) the decoded text message of this message.
5) the not original digital information of decoding of this message, that is, and the content of message.Be generally the Serial No. that constitutes by 16 system code words.
These contents are exactly the following basis of analyzing automatically.
Second portion: the automated analysis of signaling file
This analyzes log file with Signaling Analyzer as input.Analyzing of task is:
1) from huge single log file, isolate all message of each call event oneself, then they are put in the file of oneself.
2) set up a summary info table, this summary info table has comprised the summary info of all-calls incident, and the hyperlink of arriving the file of corresponding isolated call event, like this, can pass through this summary info table, directly visit the own independent signaling file of any calling.
3) in the informative abstract table, provide those access success, those call failures, key messages such as failure cause.
4) be each call event, the visible process figure that draws independent makes the problem of watching more directly perceived, and is efficient.
When only correctly having disposed base station title and Abis mouth uplink downlink corresponding relation before beginning analysis, visual flow chart could correctly draw.
The output of analyzing:
According to top analysis result, export following content:
A) call out threaded file: this is the independent file at each call event, has comprised all exclusive message of this call event.As option, some message can be filtered, as, measurement report is so that searching of problem is easier.
B) public message file:, all be placed in this file with incoherent all message of call event.For example, system message of Abis mouth etc.It doesn't matter for searching problem or the relation little for these message, can be left in the basket.
C) summary info list file: comprised key message in this information table file to the analysis result of each call event, as, the time of calling initiation/end, the calling party's of call event identity indicates, callee's number of calling out is called out the reason that discharges, and calls out the base station at generation place etc.In addition, can also cover the hyperlink of the independent calling file of each call event.
D) visual flow chart.According to each base station electronic flow sheet that draws, this helps to search problem.And electronic flow sheet has the data screening function, can filter out any single call event, arbitrarily caller's all-calls event flow diagram.The detailed description of relevant flow chart please refer to the flow chart model of back
The process of analyzing, analytical method:
I) in order to analyze, this method has been set up following computer model:
1. call event model (Call Event Model).Model is described a call event with following parameter:
1) System Frame Number (SFN:System Frame Number).This parametric description the zero-time attribute that takes place of call event.This parameter is included in the message channel demand (Channel Required).For same call event, activate and also comprised identical parameter during channel distributes immediately at message channel.
2) switch reference sign number (HORef:Handover Reference Number).This parameter is included in the message relevant with switching controls, as: channel activates, switching command etc.
3) connection type (ConnectionType).This parameter is to describe the type of call event, and value is: caller phone (MOC) or called phone (MTC) or position are upgraded (LUP:Location Update) or are switched (HO:Handover), short message (SMS).
4). Radio Resource connects ID (RRID:Radio Connection ID), and this parameter indicates this message and belongs to which call event.This parameter be included in call out relevant Abis mouth message in except channel demands (Channel Required), channel activates (Channel Activation) and immediately in assignment commands (Immediate Assign Command) all message in addition.
5) .Abis mouth up link title (AbisUpLink).This be Signaling Analyzer give each mail to the message of base station controller from the base station, be used for indicating this message and occur on which link.
6) .Abis mouth down link title (AbisDlLink) this to be signalling analysis mail to the message of base station with each of giving from base station controller, be used for indicating this message and occur on which link.
7) local this parameter of reference number (BSClocalRef) of base station controller is used for indicating A mouth message and which belongs to calls out and connect.It is included in that mobile switching centre (MSC) mails to base station controller with " target reference number " (the Destination Reference) that calls out relevant message in.Perhaps base station controller mail to mobile switching centre (MSC) with call out relevant message " source reference is number " in (Source Reference).
8) local this parameter of reference number (MSCLocalRef:MSC Local Reference Number) of mobile switching centre is used for indicating A mouth message and which belongs to calls out and connect.It is included in that mobile switching centre (MSC) mails to base station controller with call out relevant message " source reference is number " in (Source Reference).Perhaps base station controller mail to that it is included in mobile switching centre (MSC) with " target reference number " (the Destination Reference) that calls out relevant message in.
9) Abis mouth release mark (AbisEndFlag:Abis interface End Flag) is used for indicate calling out and is connected the Abis mouth and discharges and finish
10) A mouth release mark (AintEndFlag:A interface End Flag) is used for indicate calling out and is connected the A mouth and discharges and finish
11) call event end mark (ENDFlag)
12) basic station number (BtsNO:BTS Number) also is the base station title, is used for indicating the affiliated basic station number of message.As previously mentioned, should before computer begins to analyze, be input in the computer under this parameter, and should be the Abis mouth uplink downlink title of importing this base station correspondence simultaneously.
13) carrier frequency number (TrxID:TRX Identity).This parametric representation message occurs on which carrier frequency of base station.This parameter will be represented with the TEI value of Abis mouth message.For A mouth message, this parameter need not.
14) caller ID indicates number (IMSI).This parameter is used for indicating calling party's identity, can be IMSI number, TMSI number, IMEI number.This parameter is included in 3 layers of service request information.Concrete, service request comprises following message:
User's service request (CM SERVICE REQUEST)
Position updating request (LOCATION UPDATING REQUEST)
IMSI unbind (IMSI DETACH)
Page response (PAGING RESPONSE)
Service reconnects request (CM RE-ESTABLISHMENT REQUEST)
Push-notification-answer (NOTIFICATION RESPONSE)
15) called number (CalledNO).This parameter is used for indicating callee's number, the number of calling party's dialing just.This parameter is included in the call setup message (set up).
16) call error incident (ErrorEvent).Whether this parameter is used for the register call incident and makes a mistake.This parameter will be used for storing the message name beyond the normal call that belongs to this calling connection, for example, Abis mouth message: connection failure (Connection Failure), mistake indication (Error Indication), A mouth message: service-denial (CM Service Reject) etc.
17) error reason (ErrorCause).This parameter is used for the stored calls incident and makes a mistake, or the reason during improper release.This parameter may be included in the multiple message.For example, connect release (Disconnection), connection failure (Connection Failure), mistake indication (Error Indication), service-denial (CM Service Reject) etc.
18) filename (FileName).This parameter is the filename that program is distributed each call event.Inferior filename has uniqueness, is used for uniquely determining the independent file of each call event.
19) the flow process map title (MessageFlowName)
20) message name set (Messages[]): this parameter is an array, has write down the title of each bar message of this call event in order.
21) message time mark set (MsgTimeStamps[]): this parameter is an array, has write down the time mark of each bar message of this call event in order.
22) message location sets: LineNO[]. this parameter is an array, has write down the position in the flow chart of each bar message base station under this call event of this call event in order, just line number.Because each bar message takies delegation in flow chart.In fact this parameter has write down every sequence number that message is taken place in relevant base station.
Identity about the call event link model indicates:
In order to indicate an identity of calling out connection event, distinguish mutually to call out connection event with other, need to adopt following parametric joint to express:
1) basic station number
2) carrier frequency number
3) Radio Resource connects ID
4) System Frame Number
The meaning of associating expression is: in the System Frame Number life cycle, call out connection events for any two, promptly above-mentioned four parameters can not all identical (the System Frame Number life cycle be: 3 hours 16 minutes 36 seconds).
2. message model (Message).Model is described a message with following parameter:
1) link name (LinkName) this be that every message necessarily comprises, be the additional content of every message by the signaling instrument.Show that this message occurs on that logical links.
2) time mark (TimeStamp): this is that every message necessarily comprises, and is the additional content of every message by the signaling instrument.Show that this message occurs in that constantly.
3) number of base stations (BTSNO): this parameter is not included in the middle of the message itself.This parameter is only at Abis or Iub mouth message, and when analyzing, according to link name parameter, and determine by the corresponding relation between link name and base station by computer for its value.For A mouth message or Iu mouth message, this parameter need not.
4) carrier frequency number (TrxID): this parametric representation message occur in the base station which on frequency.This parameter is included in the middle of all Abis mouths or the Iu mouth message.For GSM and TSM, this parameter is represented with the TEI parameter of LAPD signaling.
5) System Frame Number (SFN:System Frame Number): have only individual message to comprise this parameter.
6) Radio Resource connects ID (RRID:Radio Connection ID): most of Abis mouth message all comprise this parameter.For A mouth message or Iu mouth message, this parameter need not.
7) source reference number (SourceLocalReference): only be included in the middle of the part A mouth message.For Abis mouth message or Iub mouth message, this parameter need not.
8) target reference number (DestLocalReference): only be included in the middle of the part A mouth message.For Abis mouth message or Iub mouth message, this parameter need not.
9) switch reference sign number (HORef:Handover Reference Number): only be included in the middle of the part message.
The same meaning that these parameter meanings of front are central with calling out link model.Below these parameters are the exclusive parameters of message model.
10) message name (MsgName): this is that every message necessarily comprises, and is the additional content of every message by the signaling instrument.
11) message interface title (Interface).Which interface Indication message belongs to.
15) reason (CauseValue) this be that some message comprises, be used to show the reason of certain incident.As, switch indication (Handover indication), connect release (Disconnection), the reason of connection failure (Connection Failure) etc.If message does not comprise this content, so, cause value is empty.
In fact, each message does not comprise all parameters in the message model.Each message also may comprise other parameter.During analysis, adopt matching method,, just take out this parameter, be used for describing this message as long as this message comprises the parameter in the message model.
3. message flow graph model.
Its aspect of model is:
A. each base station is at the flow chart of oneself, and promptly flow chart is based on the base station.
B. comprised all message relevant that is taken place in this base station in the flow chart with calling.
C. the flow chart flow chart has row-column configuration.
D. each bar message of each calling connection event takies delegation in flow chart.
E. to each each bar message of calling out connection event, on the row at this message place, export following two parameters of this message at least: the time mark of message, message name.Each parameter takies row in flow chart.
F. the logical place of the interface under this message has been reflected in the position of the row at message name place.
G. below each message name, draw a horizontal line.This horizontal line can have direction, also can be directionless.
H. each is called out each bar message of connection event, on the row at this message place, export all parameters or some important parameters of the affiliated call event of this message.For example, following six parameters: the carrier frequency number (TrxID) of call event, Radio Resource connects ID (RRID), and caller ID indicates number (IMSI), called number (CalledNO), System Frame Number (SFN) switches reference sign number (HORef).Each parameter takies row in flow chart.
I. optional, electronic flow sheet has filtering function.Utilize computer technology, adopt filtering function, filter out the flow chart of specified conditions.For example, can filter out the all-calls incident on some carrier frequency according to carrier frequency number (TrxID); Can indicate the all-calls incident that taken place of some calling subscribers in the testing time scope that number filter out according to caller ID, can filter out the flow chart of some independent call events etc. according to System Frame Number (SFN).
Fig. 4 shows an example of message flow graph model.This example adopts electrical form software Excel to finish the picture flow chart.Adopt Excel to come the benefit of picture flow chart to be: fully adopt the strong functions of existing electrical form, realize said process easily, as, setting-out, output parameter, filtering function etc.
4. normal call event model
Whether normally normal call event model is to be used for judging call event standard.This model comprises following parameter:
1) set of the title of all message that may use of a normal call incident
2) reason of a normal call incident (Cause) set.
When certain call event had comprised message in the message name set that does not belong to the normal call event model, this call event just was considered to improper call event.Perhaps,
During reason beyond the some message of certain call event has comprised reason (Cause) set of normal call incident, this call event just is considered to improper call event.
Can set up a normal call event model to each call event.Further, can unite all call event models, set up a public normal call event model.The message name set of this public normal call event model comprises all message name of each normal call incident.The reason set comprises all normal reasons.Therefore, this public normal event model can be used to judge each call event correctness.
5. summary info table:
The summary info table has comprised all or part of parameter in the middle of the call event model.Summary info is represented tableau format.Each call event takies delegation in table.Can cover the hyperlink of the independent message file of this call event in this row.
Fig. 5 shows an example of summary info table.In Fig. 5, the StartTime presentation of events time started, the EndTime presentation of events concluding time, RRID represents that Radio Resource connects ID, SFN represents to call out the starter system frame number of generation, IMSI represents caller identities number, ConnType represents connection type, Error EventCall Release represents error event, AbisUPLink represents Abis mouth up link name, AbisDLink represents Abis mouth down link name, and Called Number represents called number, and Error Cause represents error reason.
II) in order to analyze, this method defines a message counter respectively according to each base station.
Message counter is used for writing down the message sum relevant with call event that this base station is received or sent.The purpose that this counter is set is, is each message of call event, writes down the position of this message in flow chart, i.e. line number.In order to express conveniently, definition counter name is called: BTS_Received_Message[x], which base station x represents.
III) analytic process
The analytic process of this method such as following shown in Figure 6, the key step that detailed step please be seen below is described in detail.
The detailed description of key step:
In calculating base,, set up a call event array according to the call event model.In order to express conveniently, for array is got name a: Connection[].
And use Connection[i] represent i element in the array.Here, i is a positive integer, i=1, and 2,3,4,5... sets a variable according to message model, and this variable is represented the message of a reality of describing according to the parameter of message model.Convenient for following description, here, given variable is called MSG.
According to above definition, during certain concrete call event, can use Connection[i in explanation] represent i call event in the call event array.When the model parameter of certain call event is described, using Connection[i] .xxx represents, when the parameter of certain message is described, represents with MSG.yyy.Here, xxx represents the parameter name of call event model.As Connection[i] .SFN represents the System Frame Number of i call event.Yyy represents the parameter name of message model, represents the message name attribute of this message as MSG.msgName.Describe key step below in detail.
Step 1: to program input Abis mouth configuration parameter.Corresponding relation base station number and the Abis mouth uplink downlink title of setting up basic station number and Abis mouth uplink downlink title can be the relations of one-to-many.As shown in the table:
| The base station number | The up link title | The down link title |
| ????1 | ????bts1_trx1_uplink | ????bts1_trx1_downlink |
| ????1 | ????bts1_trx2_uplink | ????bts1_trx2_downlink |
| ????1 | ????bts1_trx3_uplink | ????bts1_trx3_downlink |
| ????2 | ????bts2_trx1_uplink | ????bts2_trx1_downlink |
The computer basis is the data shown in the table as above, set up the corresponding relation database between basic station number and the link name.Like this,
According to the link name parameter of the message of Abis mouth, just can judge this message and belong to which base station.
Step 2: from log file, read the complete message of next bar (can comprise multiple line content)
In log file, message is in order, stores one by one.The task of this step is, order, from log file, read down a piece of news.For the form of different log files, there is diverse ways to realize.For form, also has accomplished in many ways with a kind of log file.
Common, in log file, each bar message all has an initial sign, or initial feature.A new information initial, just mean the end of previous message.Computer can judge whether to obtain complete message according to this feature.
Step 3: the content to this message is carried out parameter scanning, takes out corresponding message content according to the parameter of message model.
Each bar message all comprises the following content of message model definition at least: message name (MessageName), time mark (TimeStamp), link name (LinkName).For other parameters of message model definition, each bar message may comprise, and also may not comprise.If comprise, just take out this parameter.If do not comprise, this parameter is a null value just.In addition, each bar message has all comprised the protocol name that this message is used.According to the different agreement that distinct interface uses, just can judge message interface title (Interface) parameter value of this message.If distinct interface uses identical agreement, so, just need judge message interface title (Interface) parameter value of this message according to the difference of the link name of distinct interface.In this case, need before Computer Analysis begins, import the link name of each interface and the corresponding relation between the interface name, be similar to step 1 to computer.
Step 4: if this message is Abis message,, utilize the corresponding relation of basic station number and link name, find out the affiliated basic station number of this message according to the link name of this message.
Step 5: according to the parameters of this message, utilize the correlation between each message of same call event, find out message and belong to which time call event, and, determine the parameter of call event according to the parameter of message.
Between the different messages of same call event correlation is arranged.In different systems, the performance of correlation is different.Computer judges according to this correlation which call event is a certain message belong to.
Below, be example with TD-SCDMA TSM standard, this correlation is described.
1) if this message name is channel demands (Channel Required), so, this is in the call event, article one message that the base station sends to base station controller.This means that a new call event begins.Thus, computer increases a new element in the array of call event., be designated as Connection[i here], and, the following parameter of this call event is set.And, the following parameter of this call event is set:
Connection[i].SFN＝MSG.SFN
Connection[i].trxID＝Msg.trxID
Connection[i].AbisULLink＝MSG.LinkName
Connection[i].BTSNO＝MSG.BTSNO
Connection[i] .FileName=base station number .txt, here, basic station number is the parameter value of the message model parameter number of base stations (BTSNO) of this message of obtaining in step 4.
Connection[i].ENDFlag＝False
2) if being channel, this message name activates (Channel Activation), so, if this message has comprised System Frame Number (SFN:System Frame Number), so, this message is the response of base station controller to last message channel demand (Channel Required).In all call events, if certain call event satisfies following condition simultaneously:
Connection[i] System Frame Number of .SFN==MSG.SFN // call event equals the System Frame Number of this message
Connection[i] the basic station number of .BTSNO==MSG.BTSNO // call event equals the basic station number of this message
Connection[i] .trxID==msg.trxID, the carrier frequency number of // call event equals the carrier frequency number of this message
Connection[i] .ENDFlag==false so, the end mark of // call event equals false, that is, this call event does not also finish
So, this message belongs to call event Connection[i].Simultaneously, following parameter is set:
Connection[i] .RRID==MSG.RRID // this message
Parameters R RID composes to call event Connection[i]
Connection[i] .AbisdownlinkName==Msg.LinkName//the parameter link name of this message
Compose and give call event Connection[i] the down link name
If this message does not comprise System Frame Number (SFN), advocate and be, comprise and switch reference number (HOREF), so, this message is article one message of a handover event.In the call event array, increase a new element Connection[i], and, the following parameter of this call event is set:
Connection[i].HOREF＝MSG.HOREF
Connection[i].RRID＝MSG.RRID，Connection[i].trxID＝MSG.trxID
Connection[i].AbisUplinkName＝Msg.LinkName
Connection[i].ConnectionType＝”HO”Connection[i]
3) if this message name is assignment commands (Immediate Assignment CMD) or distribution refusal (Immediate Assignment Reject) immediately immediately, so in all call events, if certain call event satisfies following condition simultaneously:
Connection[i] System Frame Number of .SFN==MSG.SFN // call event equals the System Frame Number of this message
Connection[i] the basic station number of .BTSNO==MSG.BTSNO // call event equals the basic station number of this message
Connection[i] .trxID==msg.trxID, the carrier frequency number of // call event equals the carrier frequency number of this message
Connection[i] .ENDFlag==false so, the end mark of // call event equals false, that is, this call event does not also finish
So, this message belongs to i call event.
4) if this message name be Abis mouth message position updating request (Location Update) or service request (CMService Request) or page response (Paging Response) so in all call events, if certain call event satisfies following condition simultaneously:
Connection[i] .BTSNO==MSG.BTSNO // same base station
Connection[i] .trxID==msg.trxID // same carrier frequency
Connection[i] .RRID==MSG.RRID // same Radio Resource connection
Connection[i].ENDFlag＝＝false
So, this message belongs to i call event.If the parameter of person's call event:
Connection[i].IMSI＝MSG.IMSI
Divide other, can judge the type of this call event:
Connection[i]=LUP or MOC or MTC
5), so, must comprise in the middle of the following message in this message if this message name is A mouth message Complete Lay3 Information (3 layers of complete message):
User's service request (CM SERVICE REQUEST)
Position updating request (LOCATION UPDATING REQUEST)
IMSI unbind (IMSI DETACH)
Page response (PAGING RESPONSE)
Service reconnects request (CM RE-ESTABLISHMENT REQUEST)
Push-notification-answer (NOTIFICATION RESPONSE)
In all call events, if certain call event satisfies following condition simultaneously:
Connection[i].IMSI＝＝MSG.IMSI
Connection[i].EndFlag＝＝false
So, this message belongs to i call event.Give the following parameter assignment of this call event:
Connection[i].BSCLocalRef＝MSG.SourceRef??//
6) if being A mouth message position, this message name upgrades acceptance (Location Update Accept) or position renewal refusal (Location Update Reject), or (CM Service Accept) or service-denial (CM Service Reject) or identity request (Identiy Request) etc. are accepted in service, so in all call events, if certain call event satisfies following condition simultaneously:
Connection[i].BSCLocalRef＝＝MSG.DestRef
Connection[i].EndFlag＝＝false
So, this message belongs to i call event.Give the following parameter assignment of this call event
Connection[i].MSCLocalRef＝MSG.SourceRef
7) if being radio-frequency channel, this message discharges confirmation (RF Channel Release Acknowledge),, so in all call events, if certain call event satisfies following condition:
Connection[i] .BTSNO==MSG.BTSNO // same base station
Connection[i] .trxID==msg.trxID // same carrier frequency
Connection[i] .RRID==MSG.RRID // same Radio Resource connection
Connection[i] the also not end of .ENDFlag==false // this call event
So, this message belongs to i call event.Give the following parameter assignment of this call event
Connection[i] .AbisEndFlag=TRUE //the Abis mouth discharges and to finish
8) (Release Complete) finished in release if this message is A mouth message, so in all call events, if certain call event satisfies following condition:
Connection[i] .BSCLocalRef=MSG.DestRef or
One of Connection[i] .MSCLocalRef=Msg.DestRef // these two conditions
And while Connection[i] .EndFlag==false
So, this message belongs to i call event.Give the following parameter assignment of this call event
Connection[i].AintEndFlag＝TRUE
9) if this message name is other message of A mouth, so in all call events, if certain call event satisfies following condition:
Connection[i] .BSCLocalRef=MSG.DestRef or
One of Connection[i] .MSCLocalRef=Msg.DestRef // these two conditions
And while Connection[i] .EndFlag==false
So, this message belongs to i call event.
Otherwise this message does not belong to any call event.
10) if this message name is other message of Abis mouth, so, so in all call events, if certain call event satisfies following condition simultaneously:
Connection[i] .BTSNO==MSG.BTSNO//same base station
Connection[i] .trxID==msg.trxID//same carrier frequency
Connection[i] .RRID==MSG.RRID//same Radio Resource connection
Connection[i] the also not end of .ENDFlag==false//this call event
So, this message belongs to i call event.Give the following parameter assignment of this call event
Otherwise this message does not belong to any call event.
11) if this message belongs to i call event: Connection[i], so, the set of the parameter message title of this call event, the set of message time mark, the message location sets respectively increases a new element, and assignment is as follows:
Connection[i].Messages[j]＝MSG.MsgName
Connection[i].MsgTimeStamps[j]＝MSG.TimeStamp
BTS_Received_Message[x]=BTS_Received_Message[x]+1 // message counter increases 1
Connection[i] .LineNO[j]=BTS_Received_Message[x] // this message write down in flow process
Line position among the figure
12) if this message belongs to i call event: Connection[i], judge so whether this message is to belong to the central message of normal call model.Determination methods is:
The title of this message is comprised in the middle of the title set of normal call model, and, this message does not comprise cause parameter (CauseValue), that is, cause parameter is empty, perhaps, this message has comprised cause parameter (CauseValue), but this cause parameter (CauseValue) value is also contained in the middle of the reason set of normal call model, and so, this message is exactly normal messages.
If do not satisfy above-mentioned condition, then be improper message.This just means that the call event under this message is improper.So, to the following parameter assignment of this call event:
Connection[i] .ErrorEvent=MSG.MsgName//title of this message is composed call error event argument to call event.For the situation that a plurality of error events take place, should consider the new value of stack on the call error event argument.
Connection[i].ErrorCause＝MSG.CauseValue
Step 6: this message is outputed in the independent file of its call event that belongs to.
Parameter according to the call event under this message: filename (FileName) appends to corresponding end of file to this message.
Step 7: the parameters of call event is outputed in the informative abstract table.
According to the structure of summary info table, output corresponding call event argument is in table
Step 8: according to the parameter of each call event, according to the basic station number of this call event, in corresponding flow chart, flow chart draws.
According to the structure of flow chart model, the corresponding information of output in flow chart.All message name of this call event have been write down in the parameter message title of call event model set (Messages[]).The time mark of this corresponding message is recorded in the message time mark set (MsgTimeStamps[]).And the corresponding line position of this message in flow chart is recorded in the message location sets (LineNO[]).Therefore, according to line position, the corresponding line number output relevant parameters in flow chart, and below this message name, draw a horizontal line.
Following Fig. 7 is a concrete instance of flow chart model output.
Claims (9)
1. the method for in the mobile communication system operation or test data being handled and being analyzed is analyzed the work or the test mode of system, comprising:
Adopt at least one base station, a base station controller, a Signaling Analyzer and a mobile switching centre, Signaling Analyzer has a memory, is used for the stored record file; Described base station controller is used for receiving respectively the signal of each base station, mobile switching centre, and can control the work of each base station, Signaling Analyzer monitoring and the contact signaling between each base station and base station controller, base station controller and the mobile switching centre of decoding record monitoring result in the file of local storage then; The said equipment is gathered selectively, sorts out, is analyzed and export the operation or the test data of system, comprises the following steps:
(1) to running parameter and other data that need analyze of the analytical system input system of Signaling Analyzer: by the log file of Signaling Analyzer record, interface link configuration information between base station and the base station controller be can also import in addition, interface up link title and down link title between base station title, base station and the base station controller comprised;
(2) needs of analyzing according to running situation, Signaling Analyzer is analyzed following parameters of operation process at least: time mark that Signaling Analyzer write down and link name, interface message between base station that all are relevant with calling out connection and the base station controller, interface message between base station controller that all are relevant with calling and the mobile switching centre;
(3) according to top analysis result, following three class files of Signaling Analyzer output: call out threaded file, public message file and summary info table, use when the system works situation is analyzed.
2. the method for claim 1, it is characterized in that describedly producing an independent calling threaded file respectively for each call out to connect, described public message file comprises broadcast channel information and call information at least, described summary info table provides delegation for each calling connects and comprises the information of calling out master data, and described information comprises information relevant with mistake when making a mistake at least.
3. method as claimed in claim 2, it is characterized in that when making a mistake in the region parameter cell of mobile switching centre's side that signalling system No.7 is connected on the interface between the region parameter cell of the side of base station controller that signalling system No.7 is connected on the interface between the down link title of interface between the up link title, base station that also comprises interface between the error message that call out to connect, base station and the base station controller in the abstract and the base station controller, base station controller and the mobile switching centre, base station controller and the mobile switching centre, the called number one or multinomial.
4. as the described method of any claim in the claim 1 to 3, it is characterized in that comprising in the abstract and call out time started of connecting, call out the concluding time, the Radio Resource that connect and connect in the release information that ID, System Frame Number, caller identities number, type of call, calling connect one or multinomial.
5. as the described method of arbitrary claim in the claim 1 to 3, it is characterized in that may further comprise the steps in the analytic process:
(1) finds out related message and belong to which base station;
(2) judge which message belongs to and call out connection;
(3) message is outputed in the corresponding file;
(4) select Useful Information, output to the summary info table.
6. the method described in claim 4 is characterized in that may further comprise the steps in the analytic process:
(1) finds out related message and belong to which base station;
(2) judge which message belongs to and call out connection;
(3) message is outputed in the corresponding file;
(4) select Useful Information, output to the summary info table.
7. the method described in claim 5 is further comprising the steps of thereafter
(5) according to above step gained result, signaling process figure draws;
(6) in flow chart, replenish the caller identities number of interface message between base station and the base station controller.
8. the method described in claim 6, further comprising the steps of thereafter:
(5) according to above step gained result, signaling process figure draws;
(6) in flow chart, replenish the caller identities number of interface message between base station and the base station controller.
9. the device of in the mobile mobile system operation or test data being handled and being analyzed is used for the operation or the test data of system are gathered selectively, sort out, analyzed and export, and comprising:
(1) one or more base stations link to each other with following base station controller respectively, link to each other with following Signaling Analyzer respectively simultaneously;
(2) base station controllers link to each other with above-mentioned each base station, following Signaling Analyzer and following mobile switching centre respectively, and be used for receiving respectively the signal of each base station, mobile switching centre, and can control the work of each base station,
(3) mobile switching centres link to each other with following Signaling Analyzer with described base station controller respectively,
(4) Signaling Analyzers, respectively with above-mentioned each base station, base station controller links to each other with mobile switching centre, be used for monitoring in the following manner and decoding each base station and base station controller, contact signaling between base station controller and the mobile switching centre, then monitoring result is recorded in the file of following local storage: respectively to running parameter and other data that need analyze of the analytical system input system of Signaling Analyzer, comprise log file by the Signaling Analyzer record, and interface link configuration information between base station and the base station controller, comprise the base station title, interface up link title and down link title between base station and the base station controller; According to the needs that running situation is analyzed, time mark of analyzing Signaling Analyzer at least and being write down and link name, all connect interface message between interface message between relevant base station and the base station controller, base station controller that all are relevant with calling and the mobile switching centre with calling out; And according to top analysis result, following three class files of output at least: call out threaded file, public message file and summary info table, use when the system works situation is analyzed;
(5) one or more local storages link to each other with above-mentioned Signaling Analyzer, are used for the log file of storage system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200410006351XA CN100546414C (en) | 2004-02-27 | 2004-02-27 | In a kind of mobile communication system to operation or the test data method and apparatus handling and analyze |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200410006351XA CN100546414C (en) | 2004-02-27 | 2004-02-27 | In a kind of mobile communication system to operation or the test data method and apparatus handling and analyze |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1662089A true CN1662089A (en) | 2005-08-31 |
| CN100546414C CN100546414C (en) | 2009-09-30 |
Family
ID=35011114
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200410006351XA Expired - Fee Related CN100546414C (en) | 2004-02-27 | 2004-02-27 | In a kind of mobile communication system to operation or the test data method and apparatus handling and analyze |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100546414C (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100401828C (en) * | 2005-11-15 | 2008-07-09 | 华为技术有限公司 | Method for obtaining information in signaling flow |
| CN100426910C (en) * | 2006-07-05 | 2008-10-15 | 华为技术有限公司 | Method for monitoring cell code resource |
| CN100466792C (en) * | 2005-10-29 | 2009-03-04 | 华为技术有限公司 | Method for recording and output call journal information and application and system |
| CN100558181C (en) * | 2006-03-28 | 2009-11-04 | 大唐移动通信设备有限公司 | Be applicable to the data test device of interface between base station and the controller thereof |
| CN101193352B (en) * | 2006-11-28 | 2010-06-23 | 中兴通讯股份有限公司 | A processing method for base station controller in coexisted multi-type base stations |
| CN101355609B (en) * | 2008-09-08 | 2010-12-22 | 李宁 | System and method for transmitting electric visual information toward user along with telephone call |
| CN101146148B (en) * | 2007-07-03 | 2011-04-20 | 中兴通讯股份有限公司 | A monitoring system and method for non-standardized inter-network call |
| CN101150858B (en) * | 2007-10-12 | 2011-04-20 | 华为技术有限公司 | Call exception analysis method and device, call exception prevention method and device |
| CN101547457B (en) * | 2008-03-28 | 2011-05-11 | 中华电信股份有限公司 | UMTS mobile network multi-interface traffic tracking system and method thereof |
| CN101296465B (en) * | 2007-04-26 | 2011-05-11 | 中华电信股份有限公司 | Action circuit automatic monitoring analysis and problem diagnosis system and method thereof |
| WO2011134108A1 (en) * | 2010-04-27 | 2011-11-03 | Nokia Siemens Networks Oy | Method of determining a radio link failure associated with a handover of a user equipment from a source access node to a target access node, access node for determining a radio link failure associated with a handover of a user equipment from a source access node to a target access node, and user equipment |
| CN102739787A (en) * | 2012-06-25 | 2012-10-17 | 福建物联天下信息科技有限公司 | Intelligent communication method |
| WO2013060155A1 (en) * | 2011-10-27 | 2013-05-02 | 中兴通讯股份有限公司 | Radio performance data collection apparatus and method |
| CN103237026A (en) * | 2013-04-22 | 2013-08-07 | 张志涵 | System accompanying calling triggering addition information interaction and method |
| US8638764B2 (en) | 2007-11-02 | 2014-01-28 | Broadcom Corporation | Mobile telecommunications architecture |
| CN103581951A (en) * | 2013-11-22 | 2014-02-12 | 中国联合网络通信集团有限公司 | Base station detection method and device |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106336858B (en) * | 2016-08-22 | 2020-11-24 | 天津天诚拓源科技发展有限公司 | High-temperature-resistant fluid loss additive for drilling fluid and production process and application thereof |
-
2004
- 2004-02-27 CN CNB200410006351XA patent/CN100546414C/en not_active Expired - Fee Related
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100466792C (en) * | 2005-10-29 | 2009-03-04 | 华为技术有限公司 | Method for recording and output call journal information and application and system |
| CN100401828C (en) * | 2005-11-15 | 2008-07-09 | 华为技术有限公司 | Method for obtaining information in signaling flow |
| CN100558181C (en) * | 2006-03-28 | 2009-11-04 | 大唐移动通信设备有限公司 | Be applicable to the data test device of interface between base station and the controller thereof |
| CN100426910C (en) * | 2006-07-05 | 2008-10-15 | 华为技术有限公司 | Method for monitoring cell code resource |
| CN101193352B (en) * | 2006-11-28 | 2010-06-23 | 中兴通讯股份有限公司 | A processing method for base station controller in coexisted multi-type base stations |
| CN101296465B (en) * | 2007-04-26 | 2011-05-11 | 中华电信股份有限公司 | Action circuit automatic monitoring analysis and problem diagnosis system and method thereof |
| CN101146148B (en) * | 2007-07-03 | 2011-04-20 | 中兴通讯股份有限公司 | A monitoring system and method for non-standardized inter-network call |
| CN101150858B (en) * | 2007-10-12 | 2011-04-20 | 华为技术有限公司 | Call exception analysis method and device, call exception prevention method and device |
| US8638764B2 (en) | 2007-11-02 | 2014-01-28 | Broadcom Corporation | Mobile telecommunications architecture |
| CN101836404B (en) * | 2007-11-02 | 2016-06-01 | 美国博通公司 | Mobile telecommunications architecture |
| CN101547457B (en) * | 2008-03-28 | 2011-05-11 | 中华电信股份有限公司 | UMTS mobile network multi-interface traffic tracking system and method thereof |
| CN101355609B (en) * | 2008-09-08 | 2010-12-22 | 李宁 | System and method for transmitting electric visual information toward user along with telephone call |
| WO2011134108A1 (en) * | 2010-04-27 | 2011-11-03 | Nokia Siemens Networks Oy | Method of determining a radio link failure associated with a handover of a user equipment from a source access node to a target access node, access node for determining a radio link failure associated with a handover of a user equipment from a source access node to a target access node, and user equipment |
| WO2013060155A1 (en) * | 2011-10-27 | 2013-05-02 | 中兴通讯股份有限公司 | Radio performance data collection apparatus and method |
| CN102739787B (en) * | 2012-06-25 | 2015-03-11 | 福建物联天下信息科技有限公司 | Intelligent communication method |
| CN102739787A (en) * | 2012-06-25 | 2012-10-17 | 福建物联天下信息科技有限公司 | Intelligent communication method |
| CN103237026A (en) * | 2013-04-22 | 2013-08-07 | 张志涵 | System accompanying calling triggering addition information interaction and method |
| CN103237026B (en) * | 2013-04-22 | 2016-09-14 | 张志涵 | The system and method that additional information is mutual are triggered with calling |
| CN103581951A (en) * | 2013-11-22 | 2014-02-12 | 中国联合网络通信集团有限公司 | Base station detection method and device |
| CN103581951B (en) * | 2013-11-22 | 2017-02-01 | 中国联合网络通信集团有限公司 | Base station detection method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100546414C (en) | 2009-09-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1662089A (en) | Method and equipment for treating and analyzing running or tested data in mobile communication system | |
| CN1310527C (en) | Position registration control method, mobile communication network and communication terminals | |
| CN1279778C (en) | Server unit, mobile communication terminal, information sending system and information sending method | |
| CN1264327C (en) | Radio communication system, communication apparatus and portable terminal for realizing higher safety grade | |
| CN1149788C (en) | Network analysis system | |
| CN1242376C (en) | Sound recognition system, device, sound recognition method and sound recognition program | |
| CN1969585A (en) | Portable terminal, and radio quality display method, program, and system | |
| CN1716818A (en) | Mobile unit information sharing system | |
| CN1765099A (en) | Device and method for simulating communication system capable of easily controlling protocol message | |
| CN1770708A (en) | Information processing system and method, electronic appliance, and information processing method | |
| CN1628483A (en) | Integrated radio communication system, mobile communication system, switching apparatus, radio terminal, and communication method | |
| CN1316139A (en) | Apparatus and method for exchanging variable-length data according to radio link protocol in mobile communication system | |
| CN1852347A (en) | Dff-line fault information report method, device and off-line fault reason positioning system | |
| CN101068408A (en) | Self log-on method, terminal and server for multi-standby terminal | |
| CN1883138A (en) | Method of managing resources for high-speed packet data service (HSDPA) in a mobile communication system | |
| CN1794647A (en) | Method and its system upload terminal information in equipment management | |
| CN1243370A (en) | Communication system, its network juncture, radio information terminal and radio communication method | |
| CN1403986A (en) | Internet switching device terminal, internet switching device terminal user management system/program | |
| CN1894992A (en) | Location information notifying system and method, terminal location determining apparatus, and privacy check apparatus | |
| CN1472977A (en) | Network terminal set information management and data terminal device | |
| CN1747570A (en) | Wireless communication apparatus, wireless communication network and software upgrading method | |
| CN1265597C (en) | Local proxy server | |
| CN1878098A (en) | Method for testing reliability of cascade device and system therefor | |
| CN1520554A (en) | Information providing method, information providing system, and information server appts. | |
| CN1623826A (en) | Control system for data monitoring device on bus and its method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20070105 Address after: Building 14, No. 51, Jiuxianqiao Road, Beijing, Chaoyang District Applicant after: Nokia Siemens Networks GmbH & Co.KG Address before: No. 7 South Central Road, Chaoyang District, Beijing, Wangjing Applicant before: SIEMENS Ltd. CHINA |
|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: NOKIA SIEMENS NETWORKS TECHNOLOGY (BEIJING) CO., L Free format text: FORMER OWNER: NOKIA SIEMENS NETWORKS SYSTEM TECHNOLOGY (BEIJING) CO., LTD. Effective date: 20111118 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100016 CHAOYANG, BEIJING TO: 100007 DONGCHENG, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20111118 Address after: 100007 Beijing city Dongcheng District Dongzhimen South Street No. 3 7 floor Patentee after: Nokia Siemens communication technology (Beijing) Co.,Ltd. Address before: 100016 Building No. 14, Jiuxianqiao Road, Chaoyang District, Beijing, 51 Patentee before: Nokia Siemens communication system technology (Beijing) Co.,Ltd. |
|
| ASS | Succession or assignment of patent right |
Owner name: NOKIA SIEMENS NETWORKS (BEIJING) CO., LTD. Free format text: FORMER OWNER: NOKIA SIEMENS NETWORKS TECHNOLOGY (BEIJING) CO., LTD. Effective date: 20111212 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100007 DONGCHENG, BEIJING TO: 100016 CHAOYANG, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20111212 Address after: 100016 No. 14, Jiuxianqiao Road, Beijing, Chaoyang District Patentee after: NOKIA SIEMENS communications network (Beijing) Co.,Ltd. Address before: 100007 Beijing city Dongcheng District Dongzhimen South Street No. 3 7 floor Patentee before: Nokia Siemens communication technology (Beijing) Co.,Ltd. |
|
| ASS | Succession or assignment of patent right |
Owner name: NOKIA COMMUNICATION NETWORK TECHNOLOGY SERVICE CO. Free format text: FORMER OWNER: NOKIA COMMUNICATION NETWORK (BEIJING) CO., LTD. Effective date: 20141118 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| C56 | Change in the name or address of the patentee |
Owner name: NOKIA COMMUNICATION NETWORK (BEIJING) CO., LTD. Free format text: FORMER NAME: NOKIA SIEMENS NETWORKS (BEIJING) CO., LTD. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100016 CHAOYANG, BEIJING TO: 100013 DONGCHENG, BEIJING |
|
| CP01 | Change in the name or title of a patent holder |
Address after: 100016 No. 14, Jiuxianqiao Road, Beijing, Chaoyang District Patentee after: NOKIA communications network (Beijing) Co.,Ltd. Address before: 100016 No. 14, Jiuxianqiao Road, Beijing, Chaoyang District Patentee before: NOKIA SIEMENS communications network (Beijing) Co.,Ltd. |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20141118 Address after: 100013, Dongcheng District, Hepingli East Street, No. 3, building No. 11, South, 1 Ping, A section, Beijing Patentee after: NOKIA communications network technology Services Ltd. Address before: 100016 No. 14, Jiuxianqiao Road, Beijing, Chaoyang District Patentee before: NOKIA communications network (Beijing) Co.,Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090930 Termination date: 20160227 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |