CN1852539A - Method for obtaining information in signaling flow - Google Patents
Method for obtaining information in signaling flow Download PDFInfo
- Publication number
- CN1852539A CN1852539A CNA2005101232558A CN200510123255A CN1852539A CN 1852539 A CN1852539 A CN 1852539A CN A2005101232558 A CNA2005101232558 A CN A2005101232558A CN 200510123255 A CN200510123255 A CN 200510123255A CN 1852539 A CN1852539 A CN 1852539A
- Authority
- CN
- China
- Prior art keywords
- information
- message
- sgsn
- tlv
- chr
- 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
Abstract
The method discloses method for obtaining information in signaling flow, sets up messages needed for analyzing signaling flow, and forms information of the said message. The method also includes steps: network equipment obtains information setup from message of interacting to signaling process flow; then, reporting the obtained information to server; server records received information. The method provides call history log for locating and analyzing problems occurred in signaling flow. Through analyzing call history log, network management system can locate problem quickly, and solve fault, and further, analyze and quality of network and optimize network.
Description
Technical field
The present invention relates to the network operation analysis technical field, be meant a kind of method of obtaining information in the signaling process especially.
Background technology
General packet radio service (GPRS) system is an open system, and this system mainly comprises core network (CN), UMTS wireless access network (UTRAN) and subscriber equipment (UE) three parts.Wherein, Serving GPRS Support Node (SGSN) belongs to the CN part, SGSN and other network element exist standard interface, such as the interface between SGSN and the wireless access network (RAN) is the Iu interface, interface between SGSN and the attaching position register (HLR) is a Gr interface, and the interface between SGSN and other SGSN is a gn interface etc.Fig. 1 is GPRS logic architecture figure, and as can be seen from the figure, in the GPRS system, SGSN is in the position at a center.On the one hand, SGSN is connected the RAN side by the Iu interface with Gb Interface; On the other hand, SGSN has connected provides other professional equipment in HLR, GGSN and the system.The signaling of nearly all gprs service all can be passed through SGSN, and in GPRS network, SGSN is in the position of a master control.
Travelling carriage (MS) carries out Signalling exchange by layer three (L3) message and the SGSN of 3GPP24.008 regulation and stipulation, realizes the GPRS service.The L3 signaling of MS and SGSN mainly is divided into mobile management and session management, in addition also just like the operation flow of the automatic positioning service of mobile phone (LCS), short message service (SMS) etc.At present, in actual GPRS network, key performance item (KPI) index, typical extremely important for the quality of the runnability raising network of awareness network as adhering to indexs such as success rate, packet data protocol (PDP) activation success rate, the success rate index of other flow process also is to weigh the important indicator of network quality certainly.In the flow process of MS and SGSN, probably for some reason, cause the failure of mobile management or session management or other signaling process.Therefore, need the location at present and analyze the reason that signaling process is failed, and then provide the method that solves fault.
In the line service of existing network, carry out accident analysis or Network Quality Analysis by the following method.
1) performance accounting method: performance statistics is a quality of weighing current network by statistical items crucial in the statistics network, for example, success/the frequency of failure of signaling process in the statistics specific measurement period, and this statistical value fed back to network management system, comprehensively analyze by network management system, solve the dilatation of existing network and the problem of existence by analysis result.
But for the present problem that needs solution,, can only count the success rate or the mortality of signaling process, can not provide some key messages that signaling process is failed because performance statistics is a kind of long-time or periodic statistics; And performance statistics is the statistical history data, can not carry out anomaly analysis to the fault that occurs in the signaling process, further can not provide the method that solves fault.
2) the whole network signaling test method: this method is by the signaling in the special signaling tracing instrument real-time tracking standard protocol interface, for example, obtain standard agreement message at interfaces such as Iu, Gb, Gr in the calling procedure from different network elements, and these message are sent to network management center, network management center is analyzed these message, network is optimized and solves subproblem according to analysis result.
The method that above-mentioned the whole network is followed the tracks of need all be followed the tracks of by special third party's instrument at all interfaces, and this proposes very high requirement to the performance of third party's instrument and the performance of network; The signaling that the whole network is followed the tracks of detects the information that can not obtain relevant information of the concrete network equipment and inter-process, can only obtain the information in the signaling process; This tracking can produce lot of data, and these data are not carried out association to same user's a certain signaling process, and obtaining from these lot of data and analyzing the required useful information of a certain signaling process of a certain user is very large workload; And also being not easy to find from above-mentioned data the problem that exists in the message needs rich experience.
3) alarm method: warning system can send the reason of alarm in real time to network management system, for example, the reason of alarm may be equipment fault or link failure etc., and network management system is according to alarm cause, and analysis is also got rid of the fault that is taken place.
But what alarm was paid close attention to is equipment fault, can not or less relevance customer service process in fault, such as, the user adheres to for a certain reason or PDP activates and waits when failing, warning system often can't embody.Therefore, the unusual or fault that occurs in the eliminating subscriber signaling flow process can not be located and analyze to alarm.
In sum, the existing network operation technology that exists can not provide good location and analyzing failure cause at the unusual or fault of signaling process and solve the method for fault.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of method of obtaining information in the signaling process, can obtain to be used for to locate and analyze the call history of the problem that signaling process occurs.
In order to achieve the above object, the invention provides a kind of method of obtaining information in the signaling process, it is characterized in that, the information that signaling process is analyzed required message and constituted described message is set, this method also comprises:
The network equipment obtains set information from the interaction message of signaling process flow process, the information of being obtained is reported server.
Server further comprises after receiving the information that the network equipment reports: the information that server record is received.
The described network equipment further comprises after obtaining information: the network equipment determines according to configuration whether needs report server, report if desired, then the information of being obtained are reported server; Otherwise, abandon the information of being obtained.
The described network equipment obtains set information from the interaction message of signaling process flow process step comprises: obtain set information in message that the network equipment receives by interface and the message by the interface transmission from the signaling process flow process, and record in the buffer memory.
The described network equipment comprises the step that the information of being obtained reports server: the network equipment is analyzed required message by the signaling process that is provided with and is carried the information of being obtained and report server;
The step of the information that described server record receives comprises: server obtains the value of each information from the message that receives, and the value of recorded information.
Described configuration information comprises: the type of configuration information, have attribute, coded format.
Described configuration information further comprises: the length of the value of information.
The described network equipment is the service universal grouping wireless serving GPRS support node.
In the method for obtaining information in the signaling process provided by the present invention, obtain some important informations of signaling process relevant and the processing of this network device internal with this network equipment at the network equipment, and export to specific server with the form of standard agreement message, for location and the fault of phase-split network provide sufficient historical record, and information by being write down in the Analysis server, can be effectively and analyze the reason of network failure apace, and provide the countermeasure that solves fault.By the historical record that phase-split network equipment provides to particular server, further the phase-split network quality provides reliable foundation for optimizing network.Generally, at the wireless network operation initial stage of new standard, tend to occur the unfavorable situation of some KPI indexs and need find out the reason that problem produces, in this case, the reason that goes wrong in the every signaling process of CHR record analysis that just can provide by the inventive method and provide the solution countermeasure.When operator released new business, the CHR record analysis signaling process that also can utilize the inventive method to provide was grasped the operating position of new business, and solves the problem that wherein exists.
Description of drawings
Figure 1 shows that GPRS logic architecture figure;
Figure 2 shows that the flow chart of analyzing the problem that occurs in the PDP activation process among the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, lift specific embodiment below, the present invention is further detailed explanation.
The present invention obtains the key message of signaling process in SGSN inside, and reports specific server.The present invention is called call history (CHR) server with described specific server.In the service operation process, during the unusual or failure of signaling process, SGSN reports the CHR server with some key messages; Perhaps, when network management system need be analyzed sometime the signaling process of section or a certain business, to report the instruction of required signaling process to be handed down to SGSN, whether SGSN reports the CHR server with these key messages according to the configuration decision of Operation and Maintenance (OM).Network management system is according to the CHR location of being write down in the CHR server and analyze the problem that occurs in the signaling process, and recovers fault by corresponding means; Network management system can also be carried out customer complaint processing, business diagnosis according to institute's ticket call historical record CHR in the CHR server, further can carry out quality analysis to the network of key.
In signaling process; key message in the message that message that SGSN sends ext nal network element by interface and SGSN send by interface obtains the back and notes with the form of buffer memory; when signaling process failure unusual or finish after; whether report according to OM configuration decision; report if desired, then carry corresponding key message and send to the CHR server by message.SGSN reports the information that is write down after the CHR server, and the information that can delete in the buffer memory to be write down also can keep the information that is write down.
The CHR server is to provide for locating and analyze the reason of signaling process failure and solving fault, and this CHR server generally is in the SGSN outside, and by external interface and SGSN pass-along message.The CHR server receives after the message that SGSN reports, and obtains the value of each information unit in this message, then with these information according to certain form, for example the form of database, extending mark language (XML) file etc. is kept in the CHR server.
When network management system is analyzed a certain signaling process, for example use user's international mobile subscriber identity (IMSI) from the CHR server, to search after the relevant record, analyze.
Be example with CHR output content in the signaling process of MS and SGSN below, at analyzing failure cause or phase-split network quality and the CHR that will provide has proposed protocol architecture, i.e. message format between SGSN and the CHR server.
The information of wanting in the CHR message comprises,
Information of mobile user (MS information): some essential informations of mobile subscriber, for example user ID, user access type etc. when this information recording events takes place;
Positional information (Location information): mobile subscriber's positional information, for example route district information, cell information, access network sign etc. when this information recording events takes place;
Procedure information (Procedure information): this information record information relevant with signaling process;
System information (System information): the essential information of system, for example system banner, system time, system's access capacity etc. when this information recording events takes place;
Extend information (Extend information): this information is that message structure is a fixed form by the extend information of system oneself definition, and content is explained by system oneself.
Definition CHR protocol of messages structure is at first classified to the CHR message that reports according to the type of the signaling process of standard protocol specifies, and the message of each class has types value; Then to each class message definition information, and the type of definition information, there are attribute, form, length etc.
Be divided into five classes for the CHR message in the signaling process of MS and SGSN, be respectively mobile management flow process CHR (MM procedure CHR); PDP context activation flow process CHR message (PDPContext Activation Procedure CHR message); Secondary PDP context activation flow process CHR message (Secondary PDP Context Activation Procedure CHR message); PDP context modification flow process CHR message (PDP Context Modification Procedures CHRmessage); PDP context deactivation flow process CHR message (PDP Context DeactivationProcedures CHR message).For the types value of decimally several respectively 1,2,3,4,5 each the class message of expression of described five class message, table one is depicted as CHR message sorting result.On this basis,, can also define the CHR message in the signaling process of more MS and SGSN according to system's needs.
| Value of message types (Message Type value) | Message (Message) |
| 1 | MM procedure CHR |
| 2 | PDP Context Activation Procedure CHR message |
| 3 | Secondary PDP Context Activation Procedure CHR message |
| 4 | PDP Context Modification Procedures CHR message |
| 5 | PDP Context Deactivation Procedures CHR message |
Table one
For above-mentioned five class message, defined the information that every class message is comprised again respectively, be described in detail as follows.
Specifying information element (Information Element) for CHR message can define information element sign (IEI), information type, have attribute (Presence), coded format (Format) etc.Wherein, IEI represents the types value of each information.M represents that this information is necessary among the Presence, if SGSN can not get Presence in signaling process when being M information, need provide default value; O represents that this information is optionally, can not carry the information that Presence is O in the CHR message of SGSN structure among the Presence; C represents that this information is with good conditionsi among the Presence, carries the information that Presence is C at SGSN under certain certain conditions in CHR message.Format represents the form of each information coding, and CHR message adopts TLV coded system coding in the 3GPP standard agreement, and each information will be encoded with T, V, TV, TLV form in the various types of messages.For the specifying information element, can also define length (Length), the length of the expression value of information.SGSN obtains after the information, and the value of filling in the information of being obtained according to defined CHR message structure constitutes CHR message.
For the information of MM procedure CHR message definition as shown in Table 2.
| IEI | Information Element | Type/Reference | Presence | Format |
| SGSN CHR type of message SGSN CHR (Message type) | Type of message (Message Type) | M | V | |
| Access service type (Access service type) | Access service type | M | V | |
| Process identification (Procedure identification) | Procedure identification | M | V | |
| Result of flow (Procedure result) | Procedure result | M | V | |
| Standby (Spare) | Spare | M | V | |
| GMM cause value (GMM cause) | GMM cause | O | TV | |
| Inner GMM cause value (Internal GMM cause) | Internal GMM cause | O | TV | |
| System time (System time) | System time | O | TV | |
| UE information unit (UE information elements) | ||||
| IMSI | IMSI | O | TV | |
| The P-TMSI (Allocated P-TMSI) that distributes | P-TMSI | O | TV | |
| The P-TMSI signature (Allocated P-TMSI signature) that distributes | P-TMSI signature (P-TMSI signature) | O | TV | |
| Old P-TMSI (Old P-TMSI) | P-TMSI | O | TV | |
| Old P-TMSI signature (Old P-TMSI signature) | P-TMSI signature | O | TV | |
| Access network type (Access System Type) | System type (System type) | O | TV | |
| Positional information unit (Location information elements) |
| Current Routing Area Identifier (Current routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | ||
| Old Routing Area Identifier (Old routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | ||
| The RNC sign (Access RNC ID) that inserts | Whole world RNC sign (Global RNC ID) | C | TV | ||
| Insert sub-district (Access cell) | Cell ID (Cell identity) | C | TV | ||
| CN identifies (CN ID) | CN ID | O | TV | ||
| Extend information unit (Externd information elements) | |||||
| Internal state (Internal status) | Internal status | O | TV | ||
| Internal physical position (Internal physical location) | Internal physical location | O | TV | ||
| Procedure information unit (PROCEDURE information elements) | |||||
| GRPS attachment flow (GPRS attach procedure) | |||||
| Type of attachment (Attach type) | Attach type | C | TV | ||
| Adhere to result (Attach result) | Attach result | C | TV | ||
| GPRS separation process (GPRS detach procedure) | |||||
| Type of separation (Detach type) | Detach type | C | TV | ||
| Routing Area Update flow process (Routing area updating procedure) | |||||
| Updating type (Update type) | Update type | C | TV | ||
| Upgrade result (Update result) | Update result | C | TV | ||
| P-TMSI allocation flow (P-TMSI reallocation procedure) | |||||
| The P-TMSI (Allocated P-TMSI) that distributes | P-TMSI | C | TV | ||
| The P-TMSI signature (Allocated P-TMSI signature) that distributes | P-TMSI signature (P-TMSI signature) | C | TV | ||
| Authentication ciphering flow process (Authentication and ciphering procedure) | |||||
| ... | |||||
| Identification flow process (Identification procedure) | ||||
| ... | ||||
| Paging flow process (Paging procedure) | ||||
| ... | ||||
| Service request flow process (Service Request Procedure) | ||||
| Request COS (Service Type) | COS (Service Type) | TV | ||
| Service request is initiated type (Service request originate type) | Initiate type (Originate type) | TV | ||
| Reorientation flow process (Relocation procedure) | ||||
| ... | ||||
| Hang up flow process (Suspend procedure) | ||||
| ... |
Table two
For the information of PDP Context Activation Procedure CHR message definition as shown in Table 3.
| IEI | Information Element | Type/Reference | Presence | Format |
| SGSN CHR type of message SGSN CHR (Message type) | Type of message (Message type) | M | V | |
| Access network type (Access System Type) | System type (System type) | M | TV | |
| System time (System Time) | System time (System time) | M | TV | |
| Result of flow (Procedure result) | Procedure result | M | V | |
| IMSI | IMSI | M | TV | |
| Current Routing Area Identifier (Current routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | |
| Old Routing Area Identifier (Old routing area identification) | Routing area identification | O | TV | |
| Insert RNC sign (Access RNC ID) | Whole world RNC sign (Global RNC ID) | C | TV | |
| Insert sub-district (Access cell) | Cell ID (Cell identity) | C | TV | |
| CN identifies (CN ID) | CN ID | O | TV | |
| Transaction Identifier (Transaction identifier, TI) | Transaction identifier | M | TV | |
| The Network Service Access point sign | Network service access | M | TV |
| (Network service access point identifier，NSAPI) | point identifier | |||
| SGSN sends to the SM cause value (SM cause sent by SGSN to MS) of MS | SM cause value (SM cause) | O | TV | |
| Inner SM cause value (Internal SM cause) | Internal SM cause | O | TV | |
| The LLC SAPI (Requested LLC SAPI) of request | LLC Service Access Point Indicator (LLC service access point identifier) | O | TV | |
| The LLC SAPI (Negotiated LLC SAPI) that consults | LLC Service Access Point Indicator (LLC service access point identifier) | O | TV | |
| The QoS (Requested QoS by MS) of MS request | Service quality (Quality of service) | O | TLV | |
| Signatory QoS (Subscribed QoS) | Quality of service | O | TLV | |
| The QoS (Negotiated QoS) that consults | Quality of service | O | TLV | |
| The pdp address (Requested PDP address by MS) of request | Pdp address (Packet data protocol address) | O | TLV | |
| The Access Point Name (Requested Access point name) of request | Access Point Name (Access point name, APN) | O | TLV | |
| Signatory Access Point Name (Subscribed Access point name) | Access point name | O | TLV | |
| The pdp address (PDP address Requested by GGSN) of GGSN request | Packet data protocol address | O | TLV | |
| The Access Point Name (Requested Access point name by GGSN) of GGSN request | Access point name | O | TLV | |
| Signatory PDP data (Subscribed PDP data) | Subscribed PDP data | O | TLV | |
| The pdp address (PDP address in use) that uses | Packet data protocol address | O | TLV | |
| The APN network identity (APNNI in use) that uses | Access point name | O | TLV | |
| The APN operator sign of using (APNOI in use) | Access point name | O | TLV | |
| APN preference pattern (APN Selection mode) | APN Selection mode | O | TV | |
| GTP tunnel version between SGSN and the GGSN (GTP tunnel version between SGSN and GGSN) | GTP version (GTP tunnel version) | O | TV | |
| SGSN gives signaling plane TEID (the Tunnel Endpoint Identifier Signalling assigned by SGSN to of GGSN | TEID (Tunnel Endpoint Identifier) | O | TLV |
| GGSN) | ||||
| Tunnel Endpoint Identifier Signalling assigned by GGSN to SGSN | Tunnel Endpoint Identifier | O | TLV | |
| SGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by SGSN to GGSN) of GGSN | Tunnel Endpoint Identifier | O | TLV | |
| SGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by SGSN to RNC) of RNC | Tunnel Endpoint Identifier | O | TLV | |
| GGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by GGSN to SGSN) of SGSN | Tunnel Endpoint Identifier | O | TLV | |
| RNC gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by RNC to SGSN) of SGSN | Tunnel Endpoint Identifier | O | TLV | |
| The GGSN address of signaling plane (GGSN Address for signalling) | Network node IP address (Network Node IP Address) | O | TLV | |
| The GGSN address (GGSN Address for user traffic) of user's transmission | Network Node IP Address | O | TLV | |
| Signaling plane SGSN address (SGSN Address for signalling) | Network Node IP Address | O | TLV | |
| The SGSN address (SGSN Address for user traffic) of user's transmission | Netwotk Node IP Address | O | TLV | |
| The RNC address (RNC Address for usertraffic) of user's transmission | Network Node IP Address | O | TLV | |
| Charging gateway address (Charging Gateway Address) | Network Node IP Address | O | TLV | |
| Charging ID (Charging ID) | Charging ID | O | TV | |
| The cause value that GGSN returns (Cause returned by GGSN) | GTP cause value (GTP Cause) | O | TV | |
| The Qos that GGSN returns (QoS returned by GGSN) | Service quality (Quality of service) | O | TLV | |
| The pdp address that GGSN returns (PDP address returned by GGSN) | Pdp address (Packet data protocol address) | O | TLV | |
| The cause value that RNC returns (Cause by RNC) | RANAP cause value (RANAP Cause) | O | TV | |
| The cause value that MS returns (Cause by MS) | SM cause value (SM Cause) | O | TV | |
| Packet traffic sign (Packet Flow Identifier) | Packet Flow Identifier PFI | O | TLV | |
| The PCO that MS sends (PCO From MS) | PCO (Protocol configuration options) | O | TLV | |
| The PCO that GGSN sends (PCO From GGSN) | Protocol configuration options | O | TLV | |
| Privately owned expansion | Private Ext | O | TLV |
| (Private Ext) |
Table three
For the information of Secondary PDP Context Activation Procedure CHR message definition as shown in Table 4.
| IEI | Information Element | Type/Reference | Presence | Format | |
| SGSN CHR type of message SGSN CHR (Message type) | Type of message (Message type) | M | V | ||
| Access network type (Access System Type) | System type (System type) | M | TV | ||
| System time (System Time) | System time | M | TV | ||
| Result of flow (Procedure result) | Procedure result | M | V | ||
| IMSI | IMSI | M | TV | ||
| Current Routing Area Identifier (Current routing area Identification) | Routing Area Identifier (Routing area identification) | O | TV | ||
| Old Routing Area Identifier (Old routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | ||
| Access RNC ID inserts the RNC sign | Global RNC ID whole world RNC sign | C | TV | ||
| Insert sub-district (Access cell) | Cell ID (Cell identity) | C | TV | ||
| CN identifies (CN ID) | CN ID | O | TV | ||
| Transaction Identifier (Transaction identifier) | Transaction identifier | M | TV | ||
| Network Service Access point sign (NSAPI) | Network Service Access point sign (Network service access point identifier) | M | TV | ||
| SGSN sends to the SM cause value (SM cause sent by SGSN to MS) of MS | SM cause value (SM cause) | O | TV | ||
| Inner SM cause value (Internal SM cause) | Internal SM cause | O | TV | ||
| The LLC SAPI (Requested LLC SAPI) of request | LLC Service Access Point Indicator (LLC service access point identifier | O | TV | ||
| The LLC SAPI (Negotiated LLC SAPI) that consults | LLC Service Access Point Indicator (LLC service access point identifier) | O | TV | ||
| The QoS (Requested QoS by MS) of MS request | Service quality (Quality of service) | O | TLV | ||
| Signatory QoS (Subscribed QoS) | Service quality (Quality of service) | O | TLV | ||
| The QoS that consults | Quality of service | O | TLV | ||
| (Negotiated QoS) | ||||
| The Transaction Identifier (Linked Transaction identifier) of link | Transaction Identifier (Transaction identifier) | O | TV | |
| The pdp address (PDP address in use) that uses | Pdp address (Packet data protocol address) | O | TLV | |
| GTP tunnel version between SGSN and the GGSN (GTP tunnel version between SGSN and GGSN) | GTP version (GTP tunnel version) | O | TV | |
| SGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by SGSN to GGSN) of GGSN | TEID (Tunnel Endpoint Identifier) | O | TLV | |
| SGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by SGSN to RNC) of RNC | TEID (Tunnel Endpoint Identifier) | O | TLV | |
| GGSN gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by GGSN to SGSN) of SGSN | TEID (Tunnel Endpoint Identifier) | O | TLV | |
| RNC gives user's face TEID I (Tunnel Endpoint Identifier Data I assigned by RNC to SGSN) of SGSN | TEID (Tunnel Endpoint Identifier) | O | TLV | |
| The GGSN address of signaling plane (GGSN Address for signalling) | Network node IP address (Network Node IP Address) | O | TLV | |
| The GGSN address (GGSN Address for user traffic) of user's transmission | Network node IP address (Network Node IP Address) | O | TLV | |
| Signaling plane SGSN address (SGSN Address for signalling) | Network Node IP Address | O | TLV | |
| The SGSN address (SGSN Address for user traffic) of user's transmission | Network Node IP Address | O | TLV | |
| The RNC address (RNC Address for user traffic) of user's transmission | Network Node IP Address | O | TLV | |
| Charging gateway address (Charging Gateway Address) | Network Node IP Address | O | TLV | |
| Charging ID (Charging ID) | Charging ID | O | TV | |
| The cause value that GGSN returns (Cause by GGSN) | GTP cause value (GTP Cause) | O | TV | |
| The QoS that QoS returned by GGSN GGSN returns | Quality of service service quality | O | TLV | |
| The pdp address that GGSN returns (PDP address returned by GGSN) | Pdp address (Packet data protocol address) | O | TLV | |
| The cause value that RNC returns (Cause by RNC) | RANAP cause value (RANAP Cause) | O | TV | |
| The packet traffic sign | PFI (Packet Flow Identifier) | O | TLV |
| (Packet Flow Identifier) | ||||
| The PCO that MS sends (PCO From MS) | PCO (Protocol configuration options) | O | TLV | |
| The PCO that GGSN sends (PCO From GGSN) | PCO (Protocol configuration options) | O | TLV | |
| Traffic Profile (TFT) | TFT (Traffic Flow Template) | O | TLV | |
| Privately owned expansion (Private Ext) | Private Ext |
Table four
For the information of PDP Context Modification Procedures CHR message definition as shown in Table 5.
| IEI | Information Element | Type/Reference | Presence | Format |
| PDP context modification process CHR message identifier (PDP Context Modification Procedures CHR message identity) | Type of message (Message type) | M | V | |
| Access network type (Access System Type) | System type (System type) | M | TV | |
| System time (System Time) | System time (System time) | M | TV | |
| Result of flow (Procedure result) | Procedure result | M | V | |
| IMSI | IMSI | M | TV | |
| Current Routing Area Identifier (Current routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | |
| Old Routing Area Identifier (Old routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | |
| Insert RNC sign (Access RNC ID) | Whole world RNC sign (Global RNC ID) | C | TV | |
| Insert sub-district (Access cell) | Cell ID (Cell identity) | C | TV | |
| CN identifies (CN ID) | CN ID | O | TV | |
| Transaction Identifier (Transaction identifier) | Transaction identifier | M | TV | |
| Network Service Access point sign (NSAPI) | Network Service Access point sign (Network service access point identifier) | M | TV | |
| Modification process type (Modification Procedure Type) | Modification process type (Modification procedure type) | M | TV |
| SGSN issues the cause value (Cause Sent by SGSN to MS) of MS | SM cause value (SM cause) | O | TV | |
| SGSN sends to the cause value (Cause Sent by SGSN to GGSN) of GGSN | GTP cause value (GTP cause) | O | TV | |
| Inner SM cause value (Internal SM cause) | Internal SM cause | O | TV | |
| The LLC SAPI (Requested LLC SAPI) of request | LLC Service Access Point Indicator (LLC service access point identifier) | O | TV | |
| The LLC SAPI (Negotiated LLC SAPI) that consults | LLC Service Access Point Indicator (LLC service access point identifier) | O | TV | |
| The QoS (Requested QoS by MS) of MS request | Service quality (Quality of service) | O | TLV | |
| The QoS (Requested QoS by GGSN) of GGSN request | Quality of service | O | TLV | |
| QoS originally (Original QoS) | Quality of service | O | TLV | |
| Signatory QoS (Subscribed QoS) | Quality of service | O | TLV | |
| The QoS (Negotiated QoS) that consults | Quality of service | O | TLV | |
| The pdp address (PDP address in use) that uses | Pdp address (Packet data protocol address) | O | TLV | |
| The pdp address (PDP address Requested by GGSN) of GGSN request | Packet data protocol address | O | TLV | |
| The cause value that GGSN returns (Cause by GGSN) | GTP cause value (GTP Cause) | O | TV | |
| The QoS that GGSN returns (QoS returned by GGSN) | Quality of service | O | TLV | |
| The pdp address that GGSN returns (PDP address returned by GGSN) | Packet data protocol address | O | TLV | |
| The cause value that RNC returns (Cause by RNC) | RANAP cause value (RANAP Cause) | O | TV | |
| The cause value that MS returns (Cause by MS) | SM cause value (SM Cause) | O | TV | |
| Packet traffic sign (Packet Flow Identifier) | PFI (Packet Flow Identifier) | O | TLV | |
| The PCO that MS sends (PCO From MS) | PCO (Protocol configuration option) | O | TLV | |
| The PCO that GGSN sends (PCO From GGSN) | Protocol configuration options | O | TLV | |
| Traffic Profile (TFT) | TFT (Traffic Flow Template) | O | TLV | |
| Privately owned expansion | Private Ext |
| (Private Ext) |
Table five
For the information of PDP Context Deactivation Procedures CHR message definition as shown in Table 6.
| IEI | Information Element | Type/Reference | Presence | Format |
| SGSN CHR type of message SGSN CHR (Message type) | Type of message (Message type) | M | V | |
| Access network type (Access System Type) | System type (System type) | M | TV | |
| System time (System Time) | System time | M | TV | |
| Result of flow (Procedure result) | Procedure result | M | V | |
| IMSI | IMSI | M | TV | |
| Current Routing Area Identifier (Current routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | |
| Old Routing Area Identifier Old (routing area identification) | Routing Area Identifier (Routing area identification) | O | TV | |
| Insert RNC sign (Access RNC ID) | Whole world RNC sign (Global RNC ID) | C | TV | |
| Insert sub-district (Access cell) | Cell ID (Cell identity) | C | TV | |
| CN identifies (CN ID) | CN ID | O | TV | |
| Transaction Identifier (Transaction identifier) | Transaction identifier | M | TV | |
| Network Service Access point sign (NSAPI) | Network Service Access point sign (Network service access point identifier) | M | TV | |
| Deexcitation type (Deactivation Procedure Type) | Deactivation procedure type | M | TV | |
| The SM cause value of MS (Cause by MS) | SM cause value (SM cause) | O | TV | |
| GGSN cause value (Cause by GGSN) | GTP cause value (GTP cause) | O | TV | |
| Inner SM cause value (Internal SM cause) | Inner SM cause value (Internal SM cause) | O | TV | |
| Remove indication (Tear down indicator) | Tear down indicator | O | TV | |
| The PCO that MS sends (PCO From MS) | PCO (Protocol configuration options) | O | TLV | |
| The PCO that GGSN sends (PCO From GGSN) | PCO | O | TLV |
| Privately owned expansion (Private Ext) | Private Ext | O | TLV |
Table six
For the definition of the IEI in the above-mentioned CHR message as shown in Table 7.
| IEI Value | Format | Information Element |
| 0 | TV | Access service type |
| 1 | TV | Procedure identification |
| 2 | TV | Procedure result |
| 3 | TV | GMM cause |
| 4 | TV | Internal GMM cause |
| 5 | TV | System time |
| 6 | TV | IMSI |
| 7 | TV | MSISDN |
| 8 | TV | Allocated P-TMSI |
| 9 | TV | Allocated P-TMSI signature |
| 10 | TV | Old P-TMSI |
| 11 | TV | Old P-TMSI signature |
| 12 | TV | Access System Type |
| 13 | TV | Current routing area identification |
| 14 | TV | Old routing area identification |
| 15 | TV | Access RNC ID |
| 16 | TV | Access cell |
| 17 | TV | CN ID |
| 18 | TV | Internal status |
| 19 | TV | Internal physical location |
| 20 | TV | Attach type |
| 21 | TV | Attach result |
| 22 | TV | Detach type |
| 23 | TV | Update type |
| 24 | TV | Update result |
| 25 | TV | Service Type |
| 26 | TV | Service request originate type |
| 27 | TV | Transaction identifier |
| 28 | TV | Linked Transaction identifier |
| 29 | TV | NSAPI |
| 30 | TV | SM cause sent by SGSN to MS |
| 31 | TV | GTP cause sent by SGSN to GGSN |
| 32 | TV | Internal SM Cause |
| 33 | TV | Requested LLC SAPI |
| 34 | TV | Negotiated LLC SAPI |
| 35 | TV | APN Selection mode |
| 36 | TV | GTP tunnel version |
| 37 | TV | Charging ID |
| 38 | TV | Cause by GGSN |
| 39 | TV | Cause by RNC |
| 40 | TV | Cause by MS |
| 41 | TV | Modification Procedure Type |
| 42 | TV | Deactivation Procedure Type |
| IEI Value | Format | Information Element |
| 43 | TV | Tear down indicator |
| 44-127 | for future study | |
| 128 | TLV | Local SGSN Address for signalling |
| 129 | TLV | Tunnel Endpoint Identifier Signalling assigned by Local SGSN to Peer SGSN |
| 130 | TLV | Peer SGSN Address for signalling |
| 131 | TLV | Tunnel Endpoint Identifier Signalling assigned by Peer SGSN to Local SGSN |
| 132 | TLV | Peer SGSN Address for user traffic |
| 133 | TLV | Requested QoS by MS |
| 134 | TLV | Requested QoS by GGSN |
| 135 | TLV | Original QoS |
| 136 | TLV | Subscribed QoS |
| 137 | TLV | Negotiated QoS |
| 138 | TLV | Requested PDP address by MS |
| 139 | TLV | Requested Access point name by MS |
| 140 | TLV | PDP address Requested by GGSN |
| 141 | TLV | Requested Access point name by GGSN |
| 142 | TLV | Subscribed PDP data |
| 143 | TLV | PDP address in use |
| 144 | TLV | APNNI in use |
| 145 | TLV | APNOI in use |
| 146 | TLV | Tunnel Endpoint Identifier Signalling assigned by SGSN to GGSN |
| 147 | TLV | Tunnel Endpoint Identifier Signalling assigned by GGSN to SGSN |
| 148 | TLV | Tunnel Endpoint Identifier Data I assigned by SGSN to GGSN |
| 149 | TLV | Tunnel Endpoint Identifier Data I assigned by SGSN to RNC |
| 150 | TLV | Tunnel Endpoint Identifier Data I assigned by GGSN to SGSN |
| 151 | TLV | Tunnel Endpoint Identifier Data I assigned by RNC to SGSN |
| 152 | TLV | GGSN Address for signalling |
| 153 | TLV | GGSN Address for user traffic |
| 154 | TLV | SGSN Address for signalling |
| 155 | TLV | SGSN Address for user traffic |
| 156 | TLV | RNC Address for user traffic |
| 157 | TLV | Charging Gateway Address |
| 158 | TLV | QoS returned by GGSN |
| 159 | TLV | PDP address returned by GGSN |
| 160 | TLV | Packet Flow Identifier |
| 161 | TLV | PCO From MS |
| 162 | TLV | PCO From GGSN |
| 163 | TLV | TFT |
| 164 | TLV | Unsuccessfully Transmitted Data Volume |
| 165 | TLV | Private Ext |
Table seven
Be example with the fault that occurs in the analysis session managing signaling flow process below, describe the process that SGSN reports CHR message in detail, and network management system be according to the process of the problem that occurs in the CHR message analysis signaling process.
The data service of having supposed certain mobile user contracted, but data service can't be used.According to this problem, can judge the reason that user mobile phone can't use data service is that PDP activates not success, so, analyzes the reason of data service failure further combined with the PDP activation process.As shown in Figure 2, the process of analysis PDP activation process failure cause may further comprise the steps:
The related signaling process of step 201:SGSN record is the key message in the PDP activation process, and concrete PDP activation is as follows:
MS sends and activates PDP Context request (Activate PDP Context Request) message to SGSN, carry in this message Network Service Access point sign (NSAPI), Transaction Identifier (TI), PDP type (PDP Type), pdp address (PDP Address), APN (Access PointName, APN), QoS (QoS Requested), the PDP config option information such as (PDP ConfigurationOptions) of request.
SGSN receives after the above-mentioned Activate PDP Context Request message, the PDPContext Activation Procedure CHR message of record MS.SGSN at first writes down network system types that MS inserts as the system type in the CHR message, and the register system time is as the system time in the CHR message, and these records are put in the buffer memory.SGSN can obtain the IMSI of MS from mobile management (MM) context that MS initiates to have set up the activation process, and with this IMSI value record in buffer memory.Simultaneously, SGSN also records NSAPI, TI, PDP Type, PDP Address, APN, QoS Requested, PDP ConfigurationOptions in the Activate PDP Context Request message in the buffer memory.
Then, SGSN will compare the PDP Address of MS request, the PDPAddress that APN and this MS contract, and parameters such as APN judge whether to refuse or continue the PDP context activation flow process of this MS.
SGSN finds that the APN of request and the APN that MS contracts do not match, the then PDP context activation request of this MS of decision refusal, and send the message that PDP activates refusal to MS, simultaneously, SGSN with the session management reason in the refuse information (SM Cause) value record in buffer memory.
If SGSN can't obtain the information in the above-mentioned CHR message, then handle accordingly respectively according to the Presence definition of item of information in the CHR message.For the necessary item of information that defines in the PDP Context ActivationProcedure CHR message, SGSN fills in default value in the PDP ContextActivation Procedure CHR message of being constructed.For example, in some cases, SGSN can not obtain the access network system type of MS, then fills in the invalid value of a regulation.For the optional item of information that defines in the PDPContext Activation Procedure CHR message, SGSN can not carry this item of information in the PDP Context Activation Procedure CHR message of being constructed.For example, if when not carrying PDPConfiguration Options information in the PDP context activation request message that MS sends, can not carry the PCO information that MS sends in the CHR message.For the item of information of the condition that defines in the PDP Context Activation Procedure CHR message, fill in this item of information according to certain conditions during SGSN structure PDP Context Activation Procedure CHR message.For example, in gsm system, do not have the RNC sign certainly, at this moment, should not carry the RNC identification information in the CHR message.
Step 202:SGSN carries the information of being obtained with PDP Context Activation Procedure CHR message, and reports the CHR server, and detailed process is as follows:
Whether SGSN reports the CHR message of this MS according to configuration determination, report CHR message if desired, SGSN is with the IMSI of this MS, and the system type in the buffer memory, system time, NSAPI, TI, PDP Type, PDP Address, APN, QoS Requested, PDP ConfigurationOptions, information such as SM Cause, and the signatory PDP Type of this MS, PDP Address, APN, information such as QoS, the current Routing Area Identifier that gets access to SGSN, old Routing Area Identifier, insert the RNC sign, information such as CN sign, PDP Context of constructing definitions Activation Procedure CHR message according to the CHR message of PDP activation process, after in this CHR message, carrying above-mentioned information, send to the CHR server.
Step 203:CHR server obtains every information from the message that receives, and accessed information is preserved, and detailed process is as described below:
The CHR server is received the PDP Context Activation Procedure CHR message that SGSN reports, from this message, resolve the value that obtains each information unit in the message, and will be kept in the CHR server with forms such as XML file or databases, so just provide CHR for accident analysis or Network Quality Analysis.
Step 204: network management system positions and analyzes the problem that is occurred according to the every information in the message of being preserved in the CHR server, thereby provides the countermeasure of dealing with problems, and detailed process is as described below:
If operator receives above-mentioned PDP and activates the user's of failure the complaint about the data service failure, then just can search this user's CHR record in the CHR server according to this user's phone number.Can judge tentatively that according to this user's complaint this user's MS signaling process occurs and causes the data service failure unusually in the PDP context activation flow process.Obtain after the IMSI of this MS according to user's phone number, in the CHR server, search the CHR record that SGSN reports according to this IMSI, lookup result obtains PDP Context Activation Procedure CHR message, and the value of each information as shown in Table 8 in this CHR message.
| Information element | The value of information |
| Message type | PDP Context Activation Procedure CHR message |
| Access System Type | GPRS |
| System Time | 2005-7-12 10:18:35 |
| IMSI | 46000×××××××××× |
| Transaction identifier | 8 |
| NSAPI | 5 |
| SM cause sent by SGSN to MS | 0x21，request service not subscribed |
| The Access Point Name (Requested Access point name) of request | NULL |
| Requested Access point name 1 | CMWAP |
| Subscribed Access point name 2 | CMNET |
Table eight
In the CHR message shown in the table eight, the request APN that this user carries in the PDP context activation request message that SGSN sends is for empty, and this user two APN that contracted are respectively CMWAP and CMNET.In this case, SGSN is owing to can not determine which APN this user uses, and the PDP that refuses this user activates request.The reason that can judge the data service failure of this user's request by above analysis is: APN and subscription data that this mobile phone carries when activating request are not inconsistent.By above analysis, the countermeasure that solves this user data service failure is: the APN parameter of notifying the user that mobile phone correctly is set.
According to the similar process of above-mentioned analysis PDP activation process, the CHR record of signaling process that can be by analyzing a certain period, certain user is estimated and the phase-split network quality, further provides the scheme of optimization network etc.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1, a kind of method of obtaining information in the signaling process is characterized in that, the information that signaling process is analyzed required message and constituted described message is set, and this method also comprises:
The network equipment obtains set information from the interaction message of signaling process flow process, the information of being obtained is reported server.
2, method according to claim 1 is characterized in that, server further comprises after receiving the information that the network equipment reports: the information that server record is received.
3, method according to claim 1 is characterized in that, the described network equipment further comprises after obtaining information: the network equipment determines according to configuration whether needs report server, report if desired, then the information of being obtained are reported server; Otherwise, abandon the information of being obtained.
4, method according to claim 1, it is characterized in that, the described network equipment obtains set information from the interaction message of signaling process flow process step comprises: obtain set information in message that the network equipment receives by interface and the message by the interface transmission from the signaling process flow process, and record in the buffer memory.
5, method according to claim 2 is characterized in that,
The described network equipment comprises the step that the information of being obtained reports server: the network equipment is analyzed required message by the signaling process that is provided with and is carried the information of being obtained and report server;
The step of the information that described server record receives comprises: server obtains the value of each information from the message that receives, and the value of recorded information.
According to the described method of claim 1, it is characterized in that 6, described configuration information comprises: the type of configuration information, have attribute, coded format.
7, method according to claim 6 is characterized in that, described configuration information further comprises: the length of the value of information.
8, method according to claim 1 is characterized in that, the described network equipment is the service universal grouping wireless serving GPRS support node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101232558A CN100401828C (en) | 2005-11-15 | 2005-11-15 | Method for obtaining information in signaling flow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101232558A CN100401828C (en) | 2005-11-15 | 2005-11-15 | Method for obtaining information in signaling flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1852539A true CN1852539A (en) | 2006-10-25 |
| CN100401828C CN100401828C (en) | 2008-07-09 |
Family
ID=37134002
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101232558A Active CN100401828C (en) | 2005-11-15 | 2005-11-15 | Method for obtaining information in signaling flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100401828C (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101541014B (en) * | 2008-03-18 | 2010-10-20 | 中国移动通信集团公司 | Method for monitoring network coverage, system for monitoring signaling and system for monitoring network coverage |
| CN101448248B (en) * | 2008-01-25 | 2011-01-05 | 中兴通讯股份有限公司 | Method for processing different user attach types by core network of evolved packet system |
| CN101431761B (en) * | 2007-11-09 | 2011-06-01 | 中国移动通信集团公司 | Network fault reporting method, equipment and system |
| CN103108345A (en) * | 2013-01-21 | 2013-05-15 | 北京拓明科技有限公司 | Automatic identification method for redundancy configuration of service GPRS supporting node (SGSN) routing area |
| CN107347016A (en) * | 2016-05-06 | 2017-11-14 | 中兴通讯股份有限公司 | A kind of signaling process method of model identification and exceptional signaling flow discrimination method |
| CN109413714A (en) * | 2018-10-12 | 2019-03-01 | Oppo广东移动通信有限公司 | Processing method, device, storage medium and the terminal of user agent's information |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1306360A (en) * | 2000-01-20 | 2001-08-01 | 上海贝尔有限公司 | Monitor method of signaling link |
| US6801940B1 (en) * | 2002-01-10 | 2004-10-05 | Networks Associates Technology, Inc. | Application performance monitoring expert |
| CN100373856C (en) * | 2002-11-19 | 2008-03-05 | 华为技术有限公司 | Analysis method of Signaling No.7 |
| CN1266863C (en) * | 2003-10-17 | 2006-07-26 | 中兴通讯股份有限公司 | Mobile communication network protocol signalling analysis system and method |
| CN100546414C (en) * | 2004-02-27 | 2009-09-30 | 诺基亚西门子通信系统技术（北京）有限公司 | In a kind of mobile communication system to operation or the test data method and apparatus handling and analyze |
| US20050276385A1 (en) * | 2004-06-01 | 2005-12-15 | Mccormick James S | Communication network event logging systems and methods |
-
2005
- 2005-11-15 CN CNB2005101232558A patent/CN100401828C/en active Active
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101431761B (en) * | 2007-11-09 | 2011-06-01 | 中国移动通信集团公司 | Network fault reporting method, equipment and system |
| CN101448248B (en) * | 2008-01-25 | 2011-01-05 | 中兴通讯股份有限公司 | Method for processing different user attach types by core network of evolved packet system |
| CN101541014B (en) * | 2008-03-18 | 2010-10-20 | 中国移动通信集团公司 | Method for monitoring network coverage, system for monitoring signaling and system for monitoring network coverage |
| CN103108345A (en) * | 2013-01-21 | 2013-05-15 | 北京拓明科技有限公司 | Automatic identification method for redundancy configuration of service GPRS supporting node (SGSN) routing area |
| CN103108345B (en) * | 2013-01-21 | 2015-09-30 | 北京拓明科技有限公司 | The automatic identifying method of a kind of SGSN Route Area redundant configuration |
| CN107347016A (en) * | 2016-05-06 | 2017-11-14 | 中兴通讯股份有限公司 | A kind of signaling process method of model identification and exceptional signaling flow discrimination method |
| CN107347016B (en) * | 2016-05-06 | 2022-03-25 | 中兴通讯股份有限公司 | Signaling flow model identification method and abnormal signaling flow identification method |
| CN109413714A (en) * | 2018-10-12 | 2019-03-01 | Oppo广东移动通信有限公司 | Processing method, device, storage medium and the terminal of user agent's information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100401828C (en) | 2008-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1852539A (en) | Method for obtaining information in signaling flow | |
| CN1159947C (en) | Location services in a packet radio network | |
| CN1253027C (en) | Method of providing non legal mobile equipment subscriber information | |
| CN102763448A (en) | Method for centralizing mdt user involvement | |
| CN107371154A (en) | It is a kind of to realize the anonymous method reported of MDT measurements | |
| CN102026234B (en) | Statistical analysis method for GSM network calling/called loss | |
| CN107147521A (en) | A kind of complaint business pre-warning monitoring method | |
| CN1859775A (en) | User's device attaching method | |
| CN103918328A (en) | Reduction of the number of cells during paging | |
| CN100499699C (en) | System and method for collecting signalling information in communication system | |
| CN1867147A (en) | Automatic equipment detection system and method | |
| CN101364901B (en) | Legal listening method, legal listening system, packet data gateway, listening center | |
| CN1516983A (en) | Method of gathering location data of terminals in communication network | |
| CN100341338C (en) | User-oriented fault detection method for wireless network controller | |
| CN1494349A (en) | Method of realizing user calling signalling tracking in mobile communication system | |
| CN101553008B (en) | A MSC/SGSN pool management method and system | |
| US8533360B2 (en) | Method and apparatus to report resource values in a mobile network | |
| CN102045182B (en) | Service fault localization method, device and system | |
| CN107180114B (en) | Maritime satellite communication ticket analysis method and system | |
| CN106454882A (en) | Method and device used for obtaining user call ticket xDR | |
| CN1901746A (en) | Method for obtaining user cut-in homing GGSN and net element device | |
| CN101553033B (en) | A pool management method and system | |
| CN1662090A (en) | Method for testing identification of intermational mobile device | |
| CN101404808B (en) | Method for detecting EDGE function of mobile phone user | |
| CN103581953A (en) | Association method for wireless drive test data and signaling monitoring data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |