CN1852539A - Method for obtaining information in signaling flow - Google Patents

Abstract

The invention discloses a method for obtaining information in a signaling flow, setting the messages required for signaling flow analysis and the information constituting the messages, and the method further includes: network equipment obtains all information from the interactive messages of the signaling processing flow Set the information, and then report the acquired information to the server, and the server records the received information. According to the method disclosed in the invention, call history records are provided for locating and analyzing problems occurring in the signaling flow, and the network management system can quickly locate problems and solve faults by analyzing the call history records, and can further analyze network quality and optimize the network.

Description

A method for obtaining information in signaling process

technical field

The invention relates to the technical field of network maintenance and analysis, in particular to a method for obtaining information in a signaling flow.

Background technique

The General Packet Radio Service (GPRS) system is an open system, which mainly includes three parts: Core Network (CN), UMTS Radio Access Network (UTRAN) and User Equipment (UE). Among them, the Serving GPRS Support Node (SGSN) belongs to the CN part, and there are standard interfaces between the SGSN and other network elements, such as the interface between the SGSN and the Radio Access Network (RAN) is the Iu interface, and the interface between the SGSN and the Home Location Register (HLR) The interface between SGSN and other SGSN is Gr interface, and the interface between SGSN and other SGSN is Gn interface. Figure 1 is a GPRS logical system structure diagram. It can be seen from the figure that in the GPRS system, SGSN is in a central position. On the one hand, the SGSN is connected to the RAN side through the Iu interface and the Gb interface; on the other hand, the SGSN is connected to the HLR, the GGSN and the equipment providing other services in the system. The signaling of almost all GPRS services will pass through the SGSN. In the GPRS network, the SGSN is in a general control position.

The mobile station (MS) performs signaling interaction with the SGSN through the Layer 3 (L3) message stipulated in the 3GPP24.008 specification to realize the GPRS service. The L3 signaling between MS and SGSN is mainly divided into mobile management and session management, and there are also business processes such as mobile phone location service (LCS) and short message service (SMS). At present, in the actual GPRS network, key performance item (KPI) indicators, such as typical indicators such as attachment success rate, packet data protocol (PDP) activation success rate, etc., are very important to understand the operation performance of the network and improve the quality of the network. Of course, other processes The success rate indicator is also an important indicator to measure the quality of the network. In the procedure between MS and SGSN, it is likely that mobility management or session management or other signaling procedures fail due to some reasons. Therefore, it is currently necessary to locate and analyze the cause of the failure of the signaling process, and then provide a solution to the failure.

In the routine maintenance of the existing network, the fault analysis or network quality analysis is carried out through the following methods.

1) Performance statistics method: Performance statistics measure the quality of the current network by counting key statistical items in the network, for example, counting the success/failure times of the signaling process within a specific measurement period, and feeding back the statistical value to the network management system , the network management system conducts a comprehensive analysis, and solves the expansion and existing problems of the existing network through the analysis results.

However, for the current problems that need to be solved, since performance statistics are long-term or periodic statistics, only the success rate or failure rate of the signaling process can be counted, and some key information about the failure of the signaling process cannot be given; and , Performance statistics are statistical historical data, which cannot analyze the abnormality of the faults in the signaling process, and further cannot provide a solution to the faults.

2) Network-wide signaling detection method: This method is to track the signaling in the standard protocol interface in real time through a special signaling tracking instrument, for example, to obtain standard protocols from different network elements at interfaces such as Iu, Gb, and Gr during a call messages, and send these messages to the network management center, the network management center analyzes these messages, optimizes the network and solves some problems according to the analysis results.

The above-mentioned whole-network tracking method needs to be tracked by special third-party instruments on all interfaces, which puts forward high requirements on the performance of third-party instruments and network performance; the signaling detection of whole-network tracking cannot obtain specific network Device-related information and internal processing information can only obtain information in the signaling process; this kind of tracking will generate a large amount of data, and these data are not associated with a certain signaling process of the same user. From these large amounts of data It is a very heavy workload to obtain the useful information needed to analyze a certain signaling process of a certain user; moreover, it is not easy to find the problems in the message from the above data, which requires rich experience.

3) Alarm method: the alarm system can send the reason of the alarm to the network management system in real time, for example, the cause of the alarm may be equipment failure or link failure, etc., and the network management system analyzes and eliminates the failure according to the cause of the alarm.

However, the alarm focuses on equipment failures, and cannot or seldom pays attention to the failures in the user's business process. For example, when the user fails to attach or PDP activation for some reason, the alarm system often cannot reflect it. Therefore, the alarm cannot be located and analyzed to eliminate anomalies or faults that occur in the user signaling process.

To sum up, the existing network maintenance technology cannot provide a good method for locating and analyzing the cause of the fault and solving the fault for the abnormality or fault of the signaling process.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for obtaining information in the signaling flow, which can obtain call history records for locating and analyzing problems in the signaling flow.

In order to achieve the above object, the present invention provides a method for obtaining information in the signaling flow, which is characterized in that the messages required for the analysis of the signaling flow and the information forming the message are set, and the method also includes:

The network device obtains the set information from the interaction message of the signaling processing flow, and reports the obtained information to the server.

After receiving the information reported by the network device, the server further includes: the server records the received information.

After the network device obtains the information, it further includes: the network device decides whether to report to the server according to the configuration, and if it needs to report, then reports the obtained information to the server; otherwise, discards the obtained information.

The step of the network device obtaining the set information from the interaction message of the signaling processing flow includes: the network device obtaining the set information from the message received through the interface and the message sent through the interface in the signaling processing flow, and recording into the cache.

The step of the network device reporting the obtained information to the server includes: the network device analyzes the required message carrying the obtained information through the set signaling flow and reports the obtained information to the server;

The step of the server recording the received information includes: the server obtains the value of each information from the received message, and records the value of the information.

The setting information includes: the type of setting information, existence attribute, and encoding format.

The setting information further includes: the length of the information value.

The network device is a serving general packet radio service support node.

In the method for obtaining information in the signaling process provided by the present invention, the network device obtains the signaling process related to the network device and some important information processed internally by the network device, and outputs it to a specific The server provides sufficient historical records for locating and analyzing network faults, and by analyzing the information recorded in the server, it can effectively and quickly analyze the cause of network faults and provide countermeasures to solve the faults. By analyzing the historical records provided by network devices to specific servers, the network quality can be further analyzed, which provides a reliable basis for optimizing the network. Generally, in the early stage of wireless network operation of a new standard, there will often be some unsatisfactory KPI indicators and the cause of the problem needs to be found out. In this case, the CHR records provided by the method of the present invention can be used to analyze various signaling processes. Causes of problems and solutions are given. When the operator launches a new service, the CHR record provided by the method of the invention can also be used to analyze the signaling flow, grasp the usage of the new service, and solve the existing problems.

Description of drawings

Figure 1 shows the GPRS logical architecture diagram;

FIG. 2 is a flow chart of the present invention for analyzing problems occurring in the PDP activation process.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, specific examples are given below to further describe the present invention in detail.

The present invention acquires key information of signaling flow within SGSN and reports it to a specific server. The present invention refers to the specific server as a Call History Record (CHR) server. During service operation, when the signaling process is abnormal or fails, the SGSN will report some key information to the CHR server; or, when the network management system needs to analyze the signaling process of a certain time period or a certain service, it will report the required The instructions of the signaling process are sent to the SGSN, and the SGSN decides whether to report these key information to the CHR server according to the configuration of the operation and maintenance (OM). The network management system locates and analyzes the problems in the signaling process according to the CHR recorded in the CHR server, and recovers the fault through corresponding means; the network management system can also handle customer complaints according to the call history record CHR recorded in the CHR server , business analysis, and can further analyze the quality of key networks.

In the signaling process, the SGSN obtains the key information in the message sent by the external network element through the interface and the message sent out by the SGSN through the interface, and records it in the form of a buffer. When the signaling process fails or is abnormal or complete, according to The OM configuration determines whether to report, and if it needs to be reported, it will send the corresponding key information to the CHR server through the message. After reporting the recorded information to the CHR server, the SGSN can delete the recorded information in the cache, or keep the recorded information.

The CHR server is provided for locating and analyzing the cause of signaling process failure and troubleshooting. The CHR server is generally located outside the SGSN and transmits messages with the SGSN through an external interface. After the CHR server receives the message reported by the SGSN, it obtains the value of each information unit in the message, and then stores the information in a certain form, such as a database or an XML file, in the CHR server.

When the network management system analyzes a certain signaling process, for example, the user's International Mobile Subscriber Identity (IMSI) is used to search for relevant records from the CHR server, and then the analysis is performed.

Taking the output content of CHR in the signaling process between MS and SGSN as an example, a protocol structure is proposed for the CHR to be provided for analyzing the cause of the fault or analyzing the network quality, that is, the message format between the SGSN and the CHR server.

The desired information in the CHR message includes,

Mobile user information (MS information): This information records some basic information of the mobile user when the event occurs, such as user ID, user access type, etc.;

Location information: This information records the location information of the mobile user when the event occurs, such as routing area information, cell information, access network identification, etc.;

Procedure information: This information records information related to signaling procedures;

System information: This information records the basic information of the system when the event occurs, such as system identification, system time, system access capacity, etc.;

Extended information: This information is extended information defined by the system itself, the information structure is in a fixed form, and the content is interpreted by the system itself.

Define the protocol structure of CHR messages. First, classify the reported CHR messages according to the type of signaling process specified in the standard protocol. Each type of message has a type value; then define information for each type of message, and define the type of information, There are attributes, formats, lengths, etc.

The CHR messages in the signaling process between MS and SGSN are divided into five categories, namely, mobile management process CHR (MM procedure CHR); PDP context activation process CHR message (PDPContext Activation Procedure CHR message); secondary PDP context activation process CHR Message (Secondary PDP Context Activation Procedure CHR message); PDP Context Modification Procedures CHR message (PDP Context Modification Procedures CHR message); PDP Context Deactivation Procedures CHR message (PDP Context Deactivation Procedures CHR message). For the five types of messages, the decimal numbers 1, 2, 3, 4, and 5 are used to represent the type value of each type of message, and Table 1 shows the results of CHR message classification. On this basis, according to the needs of the system, more CHR messages in the signaling process between the MS and the SGSN can be defined. MessageType value 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 I

For the above five types of messages, the information contained in each type of message is defined separately, and the detailed description is as follows.

For the specific information element (Information Element) of the CHR message, the information element identifier (IEI), information type, presence attribute (Presence), encoding format (Format), etc. can be defined. Wherein, IEI represents the type value of each piece of information. M in Presence indicates that this information is necessary. If the SGSN cannot obtain the information that Presence is M in the signaling process, it needs to give a default value; O in Presence indicates that this information is optional. In the CHR message constructed by SGSN The information that the Presence is 0 may not be carried; the C in the Presence indicates that the information is conditional, and under certain conditions, the SGSN carries the information that the Presence is C in the CHR message. Format indicates the encoding format of each information. The CHR message is encoded using the TLV encoding method in the 3GPP standard protocol, and each information in each message will be encoded in the T, V, TV, and TLV formats. For a specific information element, a length (Length) can also be defined, indicating the length of the information value. After the SGSN obtains the information, it fills in the value of the obtained information according to the defined CHR message structure to form a CHR message.

The information defined for the MM procedure CHR message is shown in Table 2. IEI Information Element Type/Reference Presence Format SGSN CHR message type SGSN CHR(Message type) Message Type m V Access service type Access service type m V Procedure identification Procedure identification m V Procedure result Procedure result m V Spare Spare m V GMM cause value (GMM cause) GMM cause o TV Internal GMM cause value (Internal GMM cause) Internal GMM cause o TV System time System time o TV UE information elements IMSI IMSI o TV Allocated P-TMSI (Allocated P-TMSI) P-TMSI o TV Allocated P-TMSI signature (Allocated P-TMSI signature) 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 o TV Location information elements Current routing area identification Routing area identification o TV Old routing area identification Routing area identification o TV Access RNC ID (Access RNC ID) Global RNC ID (Global RNC ID) C TV Access cell Cell identity C TV CN ID (CN ID) CN ID o TV Extended information elements Internal status Internal status o TV Internal physical location Internal physical location o TV Process information elements (PROCEDURE informationelements) GPRS attach procedure Attach type Attach type C TV Attach result Attach result C TV GPRS detach procedure Detach type Detach type C TV Routing area updating procedure Update type Update type C TV Update result Update result C TV P-TMSI reallocation procedure Allocated P-TMSI (Allocated P-TMSI) P-TMSI C TV Allocated P-TMSI signature (Allocated P-TMSI signature) P-TMSI signature (P-TMSI signature) C TV Authentication and ciphering procedure ... Identification procedure ... Paging procedure ... Service Request Procedure Request Service Type (Service Type) Service Type TV Service request originate type Originate type TV Relocation procedure ... Suspend procedure ...

Table II

The information defined for the PDP Context Activation Procedure CHR message is shown in Table 3. IEI Information Element Type/Reference Presence Format SGSN CHR message type SGSN CHR(Message type) Message type m V Access Network Type (Access System Type) System type m TV System Time System time m TV Procedure result Procedure result m V IMSI IMSI m TV Current routing area identification Routing area identification o TV Old routing area identification Routing area identification o TV Access RNC ID (Access RNC ID) Global RNC ID (Global RNC ID) C TV Access cell Cell identity C TV CN ID (CN ID) CN ID o TV Transaction identifier (TI) Transaction identifier m TV Network service access point identification Network service access m TV (Network service access point identifier, NSAPI) point identifier SM cause value sent by SGSN to MS (SM cause sent by SGSN to MS) SM cause value (SM cause) o TV Internal SM cause value (Internal SM cause) Internal SM cause o TV Requested LLC SAPI (Requested LLC SAPI) LLC service access point identifier (LLC service access point identifier) o TV Negotiated LLC SAPI (Negotiated LLC SAPI) LLC service access point identifier (LLC service access point identifier) o TV QoS requested by MS (Requested QoS by MS) Quality of service o TLVs Subscribed QoS (Subscribed QoS) Quality of service o TLVs Negotiated QoS (Negotiated QoS) Quality of service o TLVs Requested PDP address (Requested PDP address by MS) PDP address (Packet data protocol address) o TLVs Requested Access point name Access point name (APN) o TLVs Subscribed Access point name Access point name o TLVs PDP address requested by GGSN (PDP address Requested by GGSN) Packet data protocol address o TLVs Requested Access point name by GGSN Access point name o TLVs Subscribed PDP data (Subscribed PDP data) Subscribed PDP data o TLVs PDP address in use (PDP address in use) Packet data protocol address o TLVs The APN network identifier used (APNNI in use) Access point name o TLVs The APN operator identifier used (APNOI in use) Access point name o TLVs APN Selection mode APN Selection mode o TV GTP tunnel version between SGSN and GGSN (GTP tunnel version between SGSNand GGSN) GTP version (GTP tunnel version) o TV Signaling plane TEID (Tunnel Endpoint IdentifierSignalling assigned by SGSN to GGSN from SGSN to TEID (Tunnel Endpoint Identifier) o TLVs GGSN) Tunnel Endpoint Identifier Signaling assigned by GGSN to SGSN Tunnel Endpoint Identifier o TLVs SGSN to GGSN user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by SGSN to GGSN) Tunnel Endpoint Identifier o TLVs SGSN to RNC user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by SGSN to RNC) Tunnel Endpoint Identifier o TLVs User plane TEID I (Tunnel Endpoint Identifier Data Iassigned by GGSN to SGSN) from GGSN to SGSN Tunnel Endpoint Identifier o TLVs RNC to SGSN user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by RNC to SGSN) Tunnel Endpoint Identifier o TLVs The GGSN address of the signaling plane (GGSN Address for signaling) Network Node IP Address (Network Node IPAddress) o TLVs GGSN address for user traffic (GGSN Address for user traffic) Network Node IPAddress o TLVs Signaling plane SGSN address (SGSN Address for signaling) Network Node IPAddress o TLVs SGSN address for user traffic (SGSN Address for user traffic) Netwotk Node IPAddress o TLVs RNC address for user traffic (RNC Address for usertraffic) Network Node IPAddress o TLVs Charging Gateway Address Network Node IPAddress o TLVs Charging ID Charging ID o TV Cause value returned by GGSN (Cause returned by GGSN) GTP cause value (GTP Cause) o TV Qos returned by GGSN (QoS returned by GGSN) Quality of service o TLVs PDP address returned by GGSN (PDP address returned by GGSN) PDP address (Packet data protocol address) o TLVs Cause value returned by RNC (Cause by RNC) RANAP cause value (RANAP Cause) o TV Cause value returned by MS (Cause by MS) SM cause value (SM Cause) o TV Packet Flow Identifier Packet Flow IdentifierPFI o TLVs PCO from MS (PCO From MS) PCO (Protocol configuration options) o TLVs PCO from GGSN (PCO From GGSN) Protocol configuration options o TLVs private extension Private Ext o TLVs (Private Ext)

Table 3

The information defined for the Secondary PDP Context Activation Procedure CHR message is shown in Table 4. IEI Information Element Type/Reference Presence Format SGSN CHR message type SGSN CHR(Message type) Message type m V Access Network Type (Access System Type) System type m TV System Time System time m TV Procedure result Procedure result m V IMSI IMSI m TV Current routing area identification (Current routing area Identification) Routing area identification o TV Old routing area identification Routing area identification o TV Access RNC ID Access RNC ID Global RNC ID Global RNC identification C TV Access cell Cell identity C TV CN ID (CN ID) CN ID o TV Transaction identifier Transaction identifier m TV Network Services Access Point Identifier (NSAPI) Network service access point identifier m TV SM cause value sent by SGSN to MS (SM cause sent by SGSN to MS) SM cause value (SM cause) o TV Internal SM cause value (Internal SM cause) Internal SM cause o TV Requested LLC SAPI (Requested LLC SAPI) LLC service access point identifier (LLC service access point identifier o TV Negotiated LLC SAPI (Negotiated LLC SAPI) LLC service access point identifier (LLC service access point identifier) o TV QoS requested by MS (Requested QoS by MS) Quality of service o TLVs Subscribed QoS (Subscribed QoS) Quality of service o TLVs Negotiated QoS Quality of service o TLVs (Negotiated QoS) Linked Transaction identifier Transaction identifier o TV PDP address in use (PDP address in use) PDP address (Packet data protocol address) o TLVs GTP tunnel version between SGSN and GGSN (GTP tunnel version between SGSNand GGSN) GTP version (GTP tunnel version) o TV SGSN to GGSN user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by SGSN to GGSN) TEID (Tunnel Endpoint Identifier) o TLVs SGSN to RNC user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by SGSN to RNC) TEID (Tunnel Endpoint Identifier) o TLVs User plane TEID I (Tunnel Endpoint Identifier Data Iassigned by GGSN to SGSN) from GGSN to SGSN TEID (Tunnel Endpoint Identifier) o TLVs RNC to SGSN user plane TEID I (Tunnel Endpoint Identifier Data Iassigned by RNC to SGSN) TEID (Tunnel Endpoint Identifier) o TLVs The GGSN address of the signaling plane (GGSN Address for signaling) Network Node IP Address (Network Node IPAddress) o TLVs GGSN address for user traffic (GGSN Address for user traffic) Network Node IP Address (Network Node IPAddress) o TLVs Signaling plane SGSN address (SGSN Address for signaling) Network Node IPAddress o TLVs SGSN address for user traffic (SGSN Address for user traffic) Network Node IPAddress o TLVs RNC address for user traffic (RNC Address for user traffic) Network Node IPAddress o TLVs Charging Gateway Address Network Node IPAddress o TLVs Charging ID Charging ID o TV Cause value returned by GGSN (Cause by GGSN) GTP cause value (GTP Cause) o TV QoS returned by GGSNGGSN Returned QoS Quality of serviceQuality of service o TLVs PDP address returned by GGSN (PDP address returned by GGSN) PDP address (Packet data protocol address) o TLVs Cause value returned by RNC (Cause by RNC) RANAP cause value (RANAP Cause) o TV packet flow identification PFI (Packet Flow Identifier) o TLVs (Packet Flow Identifier) PCO from MS (PCO From MS) PCO (Protocol configuration options) o TLVs PCO from GGSN (PCO From GGSN) PCO (Protocol configuration options) o TLVs Traffic Template (TFT) TFT (Traffic Flow Template) o TLVs Private Ext Private Ext

Table 4

The information defined for the PDP Context Modification Procedures CHR message is shown in Table 5. IEI Information Element Type/Reference Presence Format PDP context modification procedure CHR message identity (PDP Context Modification Procedures CHR message identity) Message type m V Access Network Type (Access System Type) System type m TV System Time System time m TV Procedure result Procedure result m V IMSI IMSI m TV Current routing area identification Routing area identification o TV Old routing area identification Routing area identification o TV Access RNC ID (Access RNC ID) Global RNC ID (Global RNC ID) C TV Access cell Cell identity C TV CN ID (CN ID) CN ID o TV Transaction identifier Transaction identifier m TV Network Services Access Point Identifier (NSAPI) Network service access point identifier m TV Modification Procedure Type Modification procedure type m TV Cause value sent by SGSN to MS (Cause Sent by SGSN to MS) SM cause value (SM cause) o TV Cause value sent by SGSN to GGSN (Cause Sent by SGSN to GGSN) GTP cause value (GTP cause) o TV Internal SM cause value (Internal SM cause) Internal SM cause o TV Requested LLC SAPI (Requested LLC SAPI) LLC service access point identifier (LLC service access point identifier) o TV Negotiated LLC SAPI (Negotiated LLC SAPI) LLC service access point identifier (LLC service access point identifier) o TV QoS requested by MS (Requested QoS by MS) Quality of service o TLVs QoS requested by GGSN (Requested QoS by GGSN) Quality of service o TLVs Original QoS (Original QoS) Quality of service o TLVs Subscribed QoS (Subscribed QoS) Quality of service o TLVs Negotiated QoS (Negotiated QoS) Quality of service o TLVs PDP address in use (PDP address in use) PDP address (Packet data protocol address) o TLVs PDP address requested by GGSN (PDP address Requested by GGSN) Packet data protocol address o TLVs Cause value returned by GGSN (Cause by GGSN) GTP cause value (GTP Cause) o TV QoS returned by GGSN (QoS returned by GGSN) Quality of service o TLVs PDP address returned by GGSN (PDP address returned by GGSN) Packet data protocol address o TLVs Cause value returned by RNC (Cause by RNC) RANAP cause value (RANAP Cause) o TV Cause value returned by MS (Cause by MS) SM cause value (SM Cause) o TV Packet Flow Identifier PFI (Packet Flow Identifier) o TLVs PCO from MS (PCO From MS) PCO (Protocol configuration option) o TLVs PCO from GGSN (PCO From GGSN) Protocol configuration options o TLVs Traffic Template (TFT) TFT (Traffic Flow Template) o TLVs private extension Private Ext (Private Ext)

Table 5

The information defined for the PDP Context Deactivation Procedures CHR message is shown in Table 6. IEI Information Element Type/Reference Presence Format SGSN CHR message type SGSN CHR(Message type) Message type m V Access Network Type (Access System Type) System type m TV System Time System time m TV Procedure result Procedure result m V IMSI IMSI m TV Current routing area identification Routing area identification o TV Old (routing area identification) Routing area identification o TV Access RNC ID (Access RNC ID) Global RNC ID (Global RNC ID) C TV Access cell Cell identity C TV CN ID (CN ID) CN ID o TV Transaction identifier Transaction identifier m TV Network Services Access Point Identifier (NSAPI) Network service access point identifier m TV Deactivation Procedure Type Deactivation procedure type m TV 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 Internal SM cause value (Internal SM cause) Internal SM cause value (Internal SM cause) o TV Tear down indicator tear down indicator o TV PCO from MS (PCO From MS) PCO (Protocol configuration options) o TLVs PCO from GGSN (PCO From GGSN) PCO o TLVs Private Ext Private Ext o TLVs

Table 6

The definition of the IEI in the above CHR message is 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 twenty one TV Attach result twenty two TV Detach type twenty three TV Update type twenty four 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 TLVs Local SGSN Address for signaling 129 TLVs Tunnel Endpoint Identifier Signaling assigned by Local SGSN to Peer SGSN 130 TLVs Peer SGSN Address for signaling 131 TLVs Tunnel Endpoint Identifier Signaling assigned by Peer SGSN to Local SGSN 132 TLVs Peer SGSN Address for user traffic 133 TLVs Requested QoS by MS 134 TLVs Requested QoS by GGSN 135 TLVs Original QoS 136 TLVs Subscribed QoS 137 TLVs Negotiated QoS 138 TLVs Requested PDP address by MS 139 TLVs Requested Access point name by MS 140 TLVs PDP address Requested by GGSN 141 TLVs Requested Access point name by GGSN 142 TLVs Subscribed PDP data 143 TLVs PDP address in use 144 TLVs APNNI in use 145 TLVs APNOI in use 146 TLVs Tunnel Endpoint Identifier Signalingassigned by SGSN to GGSN 147 TLVs Tunnel Endpoint Identifier Signaling assigned by GGSN to SGSN 148 TLVs Tunnel Endpoint Identifier Data I assigned by SGSN to GGSN 149 TLVs Tunnel Endpoint Identifier Data I assigned by SGSN to RNC 150 TLVs Tunnel Endpoint Identifier Data I assigned by GGSN to SGSN 151 TLVs Tunnel Endpoint Identifier Data I assigned by RNC to SGSN 152 TLVs GGSN Address for signaling 153 TLVs GGSN Address for user traffic 154 TLVs SGSN Address for signaling 155 TLVs SGSN Address for user traffic 156 TLVs RNC Address for user traffic 157 TLVs Charging Gateway Address 158 TLVs QoS returned by GGSN 159 TLVs PDP address returned by GGSN 160 TLVs Packet Flow Identifier 161 TLVs PCO From MS 162 TLVs PCO From GGSN 163 TLVs TFT 164 TLVs Unsuccessfully Transmitted Data Volume 165 TLVs Private Ext

Table 7

Taking the analysis of faults in the signaling process of session management as an example, the process of reporting the CHR message by the SGSN and the process of analyzing the problems in the signaling process by the network management system according to the CHR message are described in detail below.

Assume that a mobile user subscribes to a data service, but cannot use the data service. According to this problem, it can be judged that the reason why the user's mobile phone cannot use the data service is that the PDP activation is not successful. Then, the reason for the failure of the data service is further analyzed in combination with the PDP activation process. As shown in Figure 2, the process of analyzing the cause of the failure of the PDP activation process includes the following steps:

Step 201: The signaling process involved in the SGSN record is the key information in the PDP activation process. The specific PDP activation process is as follows:

The MS sends an Activate PDP Context Request (Activate PDP Context Request) message to the SGSN, which contains the network service access point identifier (NSAPI), transaction identifier (TI), PDP type (PDP Type), and PDP address (PDP Address) , Access Point Name (Access PointName, APN), requested QoS (QoS Requested), PDP Configuration Options (PDP Configuration Options) and other information.

After receiving the above Activate PDP Context Request message, the SGSN records the PDPContext Activation Procedure CHR message of the MS. The SGSN first records the network system type that the MS accesses as the system type in the CHR message, records the system time as the system time in the CHR message, and puts these records into a cache. The SGSN can obtain the IMSI of the MS from the established Mobility Management (MM) context in the activation process initiated by the MS, and record the IMSI value in the cache. At the same time, the SGSN also records NSAPI, TI, PDP Type, PDP Address, APN, QoS Requested, and PDP ConfigurationOptions in the Activate PDP Context Request message into the cache.

Then, the SGSN will compare the PDP Address requested by the MS, the APN and the PDPAddress, APN and other parameters signed by the MS, and judge whether to reject or continue the PDP context activation process of the MS.

When the SGSN finds that the requested APN does not match the APN signed by the MS, it decides to reject the PDP context activation request of the MS, and sends a PDP activation rejection message to the MS. At the same time, the SGSN will reject the session management reason (SM Cause) value in the message recorded in the cache.

If the SGSN cannot obtain the information in the CHR message, corresponding processing is performed according to the Presence definition of the information item in the CHR message. For the necessary information items defined in the PDP Context Activation Procedure CHR message, the SGSN fills in default values in the constructed PDP Context Activation Procedure CHR message. For example, in some cases, the SGSN cannot obtain the access network system type of the MS, and fill in a specified invalid value. For the optional information item defined in the PDPContext Activation Procedure CHR message, the SGSN may not carry this information item in the constructed PDP Context Activation Procedure CHR message. For example, if the PDP Context Activation Request message sent by the MS does not carry PDPConfiguration Options information, the CHR message may not carry the PCO information sent by the MS. For the information item of the condition defined in the PDP Context Activation Procedure CHR message, the SGSN fills in the information item according to the specific condition when constructing the PDP Context Activation Procedure CHR message. For example, there is definitely no RNC identity in the GSM system. At this time, the CHR message should not carry RNC identity information.

Step 202: The SGSN uses the PDP Context Activation Procedure CHR message to carry the obtained information and reports it to the CHR server. The specific process is as follows:

The SGSN judges whether to report the CHR message of the MS according to the configuration. If it needs to report the CHR message, the SGSN will send the IMSI of the MS, as well as the system type, system time, NSAPI, TI, PDP Type, PDP Address, APN, QoS Requested, PDP Configuration Options, SM Cause and other information, as well as the PDP Type, PDP Address, APN, QoS and other information signed by the MS, and the current routing area ID, old routing area ID, access RNC ID, CN ID and other information obtained by the SGSN Construct a PDP Context Activation Procedure CHR message according to the definition of the CHR message of the PDP activation process, and send it to the CHR server after carrying the above information in the CHR message.

Step 203: The CHR server obtains various information from the received message, and saves the obtained information. The specific process is as follows:

The CHR server receives the PDP Context Activation Procedure CHR message reported by the SGSN, parses the message to obtain the value of each information unit in the message, and saves it in the CHR server in the form of an XML file or database, so as to facilitate fault analysis or network Mass analysis provided CHR.

Step 204: The network management system locates and analyzes the problems that occur according to the information in the messages stored in the CHR server, so as to provide countermeasures to solve the problems. The specific process is as follows:

If the operator receives a complaint about the failure of the data service from the user whose PDP activation failed, the operator can search the CHR record of the user in the CHR server according to the mobile phone number of the user. According to the user's complaint, it can be preliminarily judged that the MS of the user has an abnormal signaling process during the PDP context activation process, resulting in data service failure. After obtaining the IMSI of the MS according to the user's mobile phone number, search the CHR record reported by the SGSN in the CHR server according to the IMSI, and obtain the PDP Context Activation Procedure CHR message as a result of the search. The values of each information in the CHR message are shown in Table 8. information element 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 Requested Access point name NULL Requested Access point name 1 CMWAP Subscribed Access point name 2 CMNET

Table 8

In the CHR message shown in Table 8, the request APN carried in the PDP context activation request message sent by the user to the SGSN is empty, and the user subscribes to two APNs, namely CMWAP and CMNET. In this case, the SGSN rejects the user's PDP activation request because it cannot determine which APN the user uses. Through the above analysis, it can be judged that the reason why the data service requested by the user fails is that the APN carried in the activation request of the mobile phone does not match the subscription data. Through the above analysis, the countermeasure to solve the failure of the user's data service is: notify the user to correctly set the APN parameters of the mobile phone.

According to the process similar to the above analysis of the PDP activation process, the network quality can be evaluated and analyzed by analyzing the CHR records of the signaling process of some users in a certain period of time, and further solutions for optimizing the network can be given.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (8)

1. A method for obtaining information in the signaling process, characterized in that, the message required for signaling process analysis and the information forming the message are set, the method also includes: The network device obtains the set information from the interaction message of the signaling processing flow, and reports the obtained information to the server. 2. The method according to claim 1, characterized in that after the server receives the information reported by the network device, it further comprises: the server records the received information. 3. The method according to claim 1, wherein after the network device obtains the information, it further comprises: the network device decides whether to report to the server according to the configuration, and if it needs to report, then reports the obtained information to the server; Otherwise, the acquired information is discarded. 4. The method according to claim 1, wherein the step of the network device obtaining the set information from the interactive message of the signaling processing flow comprises: the network device receives the message from the signaling processing flow through an interface Get the set information from the message sent through the interface, and record it in the cache. 5. The method of claim 2, wherein: The step of the network device reporting the obtained information to the server includes: the network device analyzes the required message carrying the obtained information through the set signaling flow and reports the obtained information to the server; The step of the server recording the received information includes: the server obtains the value of each information from the received message, and records the value of the information. 6. The method according to claim 1, wherein the setting information includes: setting information type, existence attribute, and encoding format. 7. The method according to claim 6, wherein the setting information further includes: the length of the information value. 8. The method of claim 1, wherein the network device is a Serving General Packet Radio Service Support Node.

Images