CN110061866A - A kind of Fault Locating Method and system - Google Patents
A kind of Fault Locating Method and system Download PDFInfo
- Publication number
- CN110061866A CN110061866A CN201910258624.6A CN201910258624A CN110061866A CN 110061866 A CN110061866 A CN 110061866A CN 201910258624 A CN201910258624 A CN 201910258624A CN 110061866 A CN110061866 A CN 110061866A
- Authority
- CN
- China
- Prior art keywords
- verification
- judges whether
- user
- algorithm
- judges
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention relates to a kind of Fault Locating Method and systems, the described method comprises the following steps, S1, basic content verification；S2, business tine verification；S3, radio layer verification；S4, SP layers of verification.The present invention carry out respectively basic content verification, business tine verification, radio layer verification and SP layer verification, can comprehensive fault point, promotion group user product using effect.
Description
Technical field
The present invention relates to 4G industrial applications, and in particular to a kind of Fault Locating Method and system.
Background technique
With the development of mobile network, mobile 4G network is more mature, and a large amount of industrial application card is also gradually by tradition
GPRS network be transferred in 4G network, consequent is that the group customer industrial application card system in 4G network is frequent
There is extensive significant trouble, and existing system can not service for the group customer industrial application card client in LTE network,
Cannot comprehensive fault point, seriously affect group user product use.
Summary of the invention
Technical problem to be solved by the invention is to provide a kind of Fault Locating Method and systems, can comprehensively position event
Barrier point.
The technical scheme to solve the above technical problems is that a kind of Fault Locating Method, includes the following steps,
S1, basic content verification；
S2, business tine verification；
S3, radio layer verification；
S4, SP layers of verification.
The beneficial effects of the present invention are: the present invention carries out basic content verification, business tine verification, radio layer verification respectively
With SP layers verify, can comprehensive fault point, promoted group user product using effect.
Based on the above technical solution, the present invention can also be improved as follows.
Further, in the S1, the basic content, which verifies, includes,
S1.1, system layer verification；
S1.2, client layer verification；
S1.3, terminating layer verification；
S1.4, the verification of core stratum reticulare.
Further, in the S1.1, the system layer, which verifies, includes,
S1.1.1 judges whether the time started is empty；
S1.1.2 judges whether the end time is empty；
S1.1.3, judges whether the time started is more than or equal to the end time；
Whether S1.1.4 judges the end time than current time less than 6 months；
S1.1.5, judges whether the time started is less than current time；
Whether S1.1.6 opens the time that judges to begin with end time span less than 30 days；
Whether S1.1.7 judges IMSI not for sky；
S1.1.8, judges whether IMSI digit is equal to 15；
S1.1.9 judges whether IMSI input content is legal；
Whether S1.1.10 judges telephone number not for sky；
S1.1.11, judges whether telephone number digit is equal to 11；
S1.1.12 judges whether telephone number input is legal；
S1.1.13 judges whether HSS interface is abnormal.
Further, in the S1.2, the client layer, which verifies, includes,
S1.2.1 judges whether user is industrial application card client；
S1.2.2, judges whether user does not open card in query time section；
S1.2.3, judge user whether not arrearage；
S1.2.4, judges whether user opens 4G；
S1.2.5 judges the whether non-quota in user's SIM card dynamic IP addressing pond.
Further, in the S1.3, the terminating layer, which verifies, includes,
S1.3.1, judge user whether off-mode；
S1.3.2, judging user, whether SIM card exits extremely or extremely；
S1.3.3 judges whether user binds particular row card APN correct.
Further, in the S1.4, the core network layer, which verifies, includes,
S1.4.1, judges whether HSS signing opens 4G state；
S1.4.2, judges whether HSS signing binds APN；
S1.4.3, judges whether PGW core net binding APN matches with HSS signing APN；
S1.4.4, judges whether PGW core net binding SIM card static IP section matches with HSS；
S1.4.5, judges whether PGW core net binding sound state matches with HSS；
S1.4.6, judge PGW core net binding IP sections of client server end whether mistake；
S1.4.7 judges dns server exception.
Further, in the S2, the business tine verification includes whether user terminal environment is normal.
Further, in the S3, the radio layer verification includes whether user radio environment is normal.
Further, in the S4, the SP layers of verification include,
S4.1 judges whether same APN business ticket signaling data access server-side is normal；
S4.2 judges whether same APN business ticket is normal with IP sections of users' access server-sides of SIM card；
S4.3 judges whether same APN business words single-user access is normal with server-side destination IP section.
Based on a kind of above-mentioned Fault Locating Method, the present invention also provides a kind of fault location systems.
A kind of fault location system, comprises the following modules,
Basic content verification, is used to carry out basic content verification；
Business tine verification, is used to carry out business tine verification；
Radio layer verification, is used to carry out radio layer verification；
SP layers of verification are used to carry out SP layers of verification.
The beneficial effects of the present invention are: the present invention carries out basic content verification, business tine verification, radio layer verification respectively
With SP layers verify, can comprehensive fault point, promoted group user product using effect.
Detailed description of the invention
Fig. 1 is a kind of flow chart of Fault Locating Method of the present invention；
Fig. 2 is a kind of structural block diagram of fault location system of the present invention.
Specific embodiment
The principle and features of the present invention will be described below with reference to the accompanying drawings, and the given examples are served only to explain the present invention, and
It is non-to be used to limit the scope of the invention.
As shown in Figure 1, the technical scheme to solve the above technical problems is that a kind of Fault Locating Method, including
Following steps,
S1, basic content verification；
S2, business tine verification；
S3, radio layer verification；
S4, SP layers of verification.
The present invention carries out basic content verification, business tine verification, radio layer verification and SP layers of verification respectively, can be comprehensive
Fault point, promoted group user product using effect.
In this embodiment:
S1, basic content verification
S1.1, system layer verification
Whether S1.1.1, time started are not sky
[precondition] nothing；
[passing through algorithm] interface -> time started！=empty；
[check results]
Pass through: executing verification " whether the S1.1.2 end time is not sky "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.2, end time are not sky
[precondition] " whether the S1.1.1 time started is not sky " passes through verification；
[passing through algorithm] interface -> end time！=empty；
[check results]
Pass through: executing verification " whether the S1.1.3 time started is more than or equal to the end time "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.3, time started are more than or equal to the end time
[precondition]
" whether the S1.1.1 time started is not sky " passes through verification；
" whether the S1.1.2 end time is not sky " passes through verification；
[passing through algorithm] interface -> time started >=interface -> end time；
[check results]
Pass through: executing verification " the S1.1.4 end time is than current time whether less than 6 months "；
Do not pass through: verification terminates, and conclusion is shown on interface.
S1.1.4, whether the end time is than current time less than 6 months
[precondition]
" whether the S1.1.1 time started is not sky " passes through verification；
" whether the S1.1.2 end time is not sky " passes through verification；
[passing through algorithm] present system time-interface -> end time≤6 month；
[check results]
Pass through: executing verification " whether the S1.1.5 time started is less than current time "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.5, time started are less than current time
[precondition]
" whether the S1.1.1 time started is not sky " passes through verification；
" whether the S1.1.2 end time is not sky " passes through verification；
[passing through algorithm] interface -> time started > present system time；
[check results]
Pass through: executing verification " whether S1.1.6 time started and end time span are less than 7 days "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.6, time started and end time span are less than 30 days
[precondition]
" whether the S1.1.1 time started is not sky " passes through verification；
" whether the S1.1.2 end time is not sky " passes through verification；
[passing through algorithm] interface -> end time-interface -> time started > 30；
[check results]
Pass through: executing verification " whether S1.1.7 IMSI is not sky "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.7, IMSI are not sky
[precondition] selection is inquired for IMSI；
[passing through algorithm] interface -> IMSI！=empty；
[check results]
Pass through: executing verification " whether S1.1.8 IMSI digit is equal to 15 "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.8, IMSI digit are equal to 15
[precondition]
Selection is inquired for IMSI；
" whether S1.1.6 IMSI is not sky " passes through verification；
[passing through algorithm] " interface -> IMSI " length==15；
[check results]
Pass through: executing verification " S1.1.9IMSI input content is illegal "；
Do not pass through: verification terminates, and conclusion is shown on interface.
S1.1.9, IMSI input content are illegal
[precondition] selection is inquired for IMSI；
[passing through algorithm] interface -> IMSI digit==15&& content is all digital content；
[check results]
Pass through: executing verification " whether S1.1.10 telephone number is not sky "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.10, telephone number are not sky
[precondition] selection is inquired for telephone number；
[passing through algorithm] interface -> telephone number！=empty；
[check results]
Pass through: executing verification " whether S1.1.11 telephone number digit is equal to 11 "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.11, telephone number digit are equal to 11
[precondition]
Selection is inquired for telephone number；
" whether S1.1.8 telephone number is not sky " passes through verification；
[passing through algorithm] " interface -> telephone number " length==11；
[check results]
Pass through: whether the input of S1.1.12 telephone number is legal；
Do not pass through: verification terminates, and conclusion is shown on interface.
S1.1.12. whether telephone number input is legal
[precondition] selection is inquired for telephone number；
[passing through algorithm] interface -> telephone number==11&& telephone number content is all digital content；
[check results]
Pass through: executing verification " whether S1.2.1 user is industrial application card client "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Whether S1.1.13, HSS interface are abnormal
[precondition] nothing；
[passing through algorithm] HSS returned data data are normal；
[check results]
Pass through: executing verification " S1.2.2 "；
Algorithm 1 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 46002534066009718334105475
S1.2, client layer verification
Whether S1.2.1, user are industrial application card client
[precondition] nothing；
[passing through algorithm 1]
IMSI number perhaps telephone number with " industrial application card user information table -> IMSI or telephone number " carry out
Match, hit one can pass through；
[check results]
Algorithm 1 passes through: executing verification " whether S1.1.13HSS interface is abnormal "；
Algorithm 1 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,023,293,413,256 15991321770
Whether S1.2.2, user do not open card in query time section
[precondition] nothing；
[passing through algorithm]
Industrial application card IMSI and telephone number relation table -> createTime≤end time；
[check results]
Pass through: executing verification " S1.2.3 user whether not arrearage "；
Do not pass through: verification terminates, and conclusion is shown on interface.
S1.2.3, user whether not arrearage
[precondition] nothing；
[passing through algorithm 1]
！(S6a interface message table -> Procedure Type==Authentication_Information&&S6a connects
Mouth information table -> Cause==DIAMETER_AUTHORIZATION_REJECTED (5003))；
[check results]
Algorithm 1 passes through: executing verification " whether S1.2.4 user opens 4G "；
Algorithm 1 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,004,750,679,563 13564734486
Whether S1.2.4, user open 4G
[precondition] nothing；
[passing through algorithm 1]
HSS basic information table -> open 4G==is normal；
[passing through algorithm 2]
！(S1-MME interface information table -> Procedure Type==Attach&&S1-MME interface message table ->
Failure Cause Group==1&& (S1-MME interface information table -> Failure Cause Specific==EPS
Services not allowed | | S1-MME interface information table -> Failure Cause Specific==EPS
services and non-EPS services not allowed))；
[check results]
Algorithm 1&& algorithm 2 passes through: executing verification " S1.2.5 user's SIM card dynamic IP addressing pond whether quota "；
Algorithm 1 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,027,867,438,256 18798837852
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface.
Test data: 460,026,860,388,256 18275003637
S1.2.5, the whether non-quota in user's SIM card dynamic IP addressing pond
IP sections of [precondition] dynamic configuration SIM card；
[passing through algorithm]
！(S11 interface message table -> Procedure Type==Create Session&&S11 interface message table ->
Failure Cause==All dynamic addresses are occupied)；
[check results]
Pass through: executing verification " S1.3.1 user whether off-mode or offline mode "；
Algorithm does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,022,865,236,246 15085796510
S1.3, terminating layer verification
S1.3.1, user whether off-mode
For [precondition] time period without signaling data, User Status is normal；
[passing through algorithm 1]
It based on the time started, inquires three days forward, a signaling data nearest from the time started is attachment removal letter
Enable data；
[passing through algorithm 2]
Using the end time as the time started, current time is the end time, inquires to obtain one nearest from the end time backward
Data, acquisition time；
[check results]
Algorithm 1&& algorithm 2 passes through: verification terminates, and conclusion is shown on interface, and display result is as follows:
Test data: 460,027,868,476,246 18786836471
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface, and display result is as follows:
Test data: 460,027,868,476,246 18786836471
Algorithm 1 does not pass through: executing verification " whether SIM card exits S1.3.2 user extremely or extremely "
S1.3.2, whether SIM card exits user extremely or extremely
For [precondition] time period without signaling data, User Status is normal；
[passing through algorithm 1]
It based on the time started, inquires three days forward, a signaling data nearest from the time started is non-attachment removal
Signaling data, and the end time is occupied more than 1 day；
[passing through algorithm 2]
Using the end time as the time started, current time is the end time, inquires to obtain one nearest from the end time backward
Data, acquisition time；
[check results]
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface.
Test data: 460,078,860,006,246 18886011323
Algorithm 1&& algorithm 2 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,078,860,006,246 18886011323
Algorithm 1 passes through: executing verification " it is whether correct that S1.3.3 user binds particular row card APN "
S1.3.3, whether user binds particular row card APN correct
[precondition]
[passing through algorithm]
After all tickets are to " APN " duplicate removal in time range, have and be not belonging to public APN access business, with " from " HSS
Content in basic information table -> row card APN " " is matched, and hit one can pass through；
[check results]
Pass through: executing verification " whether S1.4.1HSS signing opens 4G state "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,009,408,210,996 13984013228
S1.4, the verification of core stratum reticulare
Whether S1.4.1, HSS signing open 4G state
[precondition]
[passing through algorithm]
It has checked whether to open 4G by HSS returned content；
[check results]
Pass through: executing verification " whether S1.4.2HSS signing binds APN "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,005,153,850,996 13765823682
Whether S1.4.2, HSS signing bind APN
[precondition]
[passing through algorithm]
(perhaps telephone number carries out IMSI number with " industrial application card user information table -> IMSI or telephone number "
Matching, hit one can pass through) && (by HSS interface, content and " 6.3 rows from " HSS basic information table -> row blocks APN "
Industry application card APN information table -> APN " is matched, no hit)；
[check results]
Pass through: executing verification " S1.4.3PGW core net binds whether APN matches with HSS signing APN "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,021,854,509,354 15285333952
S1.4.3, PGW core net bind whether APN matches with HSS signing APN
[precondition]
[passing through algorithm]
！(S11 interface message table -> Procedure Type==Create Session&&S11 interface message table ->
Failure Cause==Missing or unknown APN)；
[check results]
Pass through: executing verification " whether S1.4.4PGW core net binding SIM card static IP section matches with HSS "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,004,814,830,996 13985150732
Whether S1.4.4, PGW core net binding SIM card static IP section match (priority is turned down) with HSS
IP sections of [precondition] static configuration SIM card；
[passing through algorithm]
Traffic table -> USER_IPv4 belongs to that (industrial application card user information table -> SIM card distribution IPDi Zhiduan && industry is answered
With card user information table -> IP dynamic/static==static state)；
[check results]
Pass through: executing verification " whether S1.4.5PGW core net binding sound state matches with HSS "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,021,808,651,529 15186981669
Whether S1.4.5, PGW core net binding sound state match with HSS
[precondition]
[passing through algorithm]
HSS basic information table -> row card address==industrial application card user information table -> IP dynamic/static；
[check results]
Pass through: executing verification " it is whether wrong that S1.4.6PGW core net binds IP sections of client server end "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,025,585,726,529 18368550251
S1.4.6, PGW core net bind IP sections of client server end whether mistake
[precondition]
[passing through algorithm]
Traffic table -> App Server IP_IPv4 belongs to industrial application card user information table -> opposite end server ip address；
[check results]
Pass through: executing verification " S1.4.7DNS server exception "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,078,856,666,529 18886301187
S1.4.7, dns server are abnormal (a time specific APN of screening)
[precondition]
[passing through algorithm]
(S1-U interface DNS traffic table -> query result IP==is empty) is counted according to APP Server IP_Ipv4,
Statistical result is empty ratio > 95%；
[check results]
Pass through: executing verification " whether S2.1.1 user terminal environment is normal "；
Do not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,008,575,024,329 13638570226
S2, business tine verification
S2.1, terminating layer verification
Whether S2.1.1, user terminal environment are normal
Traffic table information existing for [precondition] user, and traffic table -> L4protocal==TCP；
[passing through algorithm 1] high retransmission rate
((sum (traffic table -> uplink TCP retransmits message number+traffic table -> downlink TCP and retransmits message number)/sum (business
Table ->UL IP Packet+ traffic table ->DL IP Packet)) * 100%)<10%；
[passing through algorithm 2] link setup failure rate
(sum (log-on count of (traffic table -> TCP connection state instruction==success))/sum (traffic table -> TCP link setup
Number of attempt)) * 100%) > 90%；
The high response delay of [passing through algorithm 3] link setup
(sum (traffic table ->TCP link setup response delay>50ms number)/(traffic table log-on count) * 100%)<10%；
[passing through algorithm 4] link setup height confirms time delay
(sum (traffic table ->TCP link setup confirms time delay>50ms number)/(traffic table log-on count) * 100%)<10%；
[passing through algorithm 5] service success rate
((sum (HTTP traffic table -> business completes the success of mark==business)/HTTP traffic table log-on count) *
100%) > 95%；
The high time delay of [passing through algorithm 6] business
(sum (HTTP traffic table ->service delay>50ms number)/HTTP traffic table log-on count) * 100%<10%；
[check results]
！(algorithm 1 is passed through by && algorithm 5 by && algorithm 6 by && algorithm 3 by && algorithm 4 by && algorithm 2):
Execute verification " whether S2.2.1 user radio environment is abnormal "；
Algorithm 1 is passed through by && algorithm 5 by && algorithm 6 by && algorithm 3 by && algorithm 4 by && algorithm 2: verification
Terminate, and shows conclusion on interface.
Test data: 460,022,850,559,329 15208513391
The verification of S3 radio layer
Whether S3.1, user radio environment are normal
[precondition] " whether S2.1.1 user terminal environment is normal " verification does not pass through；
[passing through algorithm 1]
S2.1.1's is counted by algorithm according to same cell, and entire cell does not pass through ratio < 5%；
[passing through algorithm 2]
Exist with cell and belong to different APN row cards, and difference APN row card does not pass through ratio < 5%；
[check results]
Algorithm 1 passes through: executing verification " whether S4.1 is normal with APN business ticket signaling data access server-side "；
Algorithm 1&& algorithm 2 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,008,539,744,329 13885300210
S4, SP layers of verification
Whether S4.1 is normal with APN business ticket signaling data access server-side
[precondition] " whether S3.1 user radio environment is normal " verification passes through；
[passing through algorithm 1]
S2.1.1's is counted by algorithm according to " traffic table ->APN " is identical, does not pass through ratio<5% entirely；
[passing through algorithm 2]
Belong to the same cell with APN row card user and generates traffic signaling ticket；
[check results]
Algorithm 1 passes through: executing verification, " whether just S4.1 accesses server-side with IP sections of users of SIM card with APN business ticket
Often "；
Algorithm 1&& algorithm 2 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,029,851,509,354 15185100593
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface.
Test data: 460,029,851,509,354 15185100593
Whether S4.2 is normal with IP sections of users' access server-sides of SIM card with APN business ticket
[precondition] " whether S4.1 is normal with APN business ticket signaling data access server end " verification does not pass through；
[passing through algorithm 1]
S2.1.1 by algorithm, according to " traffic table -> APN " Xiang Tong &&, " traffic table -> USER_Ipv4 belongs to industrial application
Card user information table -> SIM card distributes IP address section；
It " is counted, does not entirely pass through ratio < 5% with IP sections of users of SIM card with APN business ticket；
[passing through algorithm 2]
Belong to the same cell with IP sections of users of SIM card with APN row card user and generates traffic signaling ticket；
[check results]
Algorithm 1 passes through: executing verification " whether S43 is normal with server-side destination IP section with the words single-user access of APN business "；
Algorithm 1&& algorithm 2 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,021,807,112,666 15085905183
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface.
Test data: 460,021,807,112,666 15085905183
Whether S4.3 is normal with server-side destination IP section with the words single-user access of APN business
[precondition] " whether normal with IP sections of users' access server-sides of SIM card with APN business ticket " verification does not pass through；
[passing through algorithm 1]
S2.1.1 by algorithm, according to " traffic table -> APN " Xiang Tong &&, " traffic table -> USER_Ipv4 belongs to 6.2 industries
Application card user message table -> opposite end server ip address " is counted, and entirely talks about the same server-side of single-user access with APN business
Destination IP section does not pass through ratio < 5%；
[passing through algorithm 2]
Belong to the same cell with APN row card user access server-side destination IP and generates traffic signaling ticket；
[check results]
Algorithm 1 passes through: verification terminates, and conclusion is shown on interface.
Test data: 460,021,178,834,354 15285320655
Algorithm 1&& algorithm 2 does not pass through: verification terminates, and conclusion is shown on interface.
Test data: 460,028,189,754,354 15876672235
Algorithm 1 is not passed through by algorithm 2: verification terminates, and conclusion is shown on interface.
Test data: 460,028,189,754,354 15876672235
Based on a kind of above-mentioned Fault Locating Method, the present invention also provides a kind of fault location systems.
As shown in Fig. 2, a kind of fault location system, comprises the following modules,
Basic content verification, is used to carry out basic content verification；
Business tine verification, is used to carry out business tine verification；
Radio layer verification, is used to carry out radio layer verification；
SP layers of verification are used to carry out SP layers of verification.
The present invention carries out basic content verification, business tine verification, radio layer verification and SP layers of verification respectively, can be comprehensive
Fault point, promoted group user product using effect.
The foregoing is merely presently preferred embodiments of the present invention, is not intended to limit the invention, it is all in spirit of the invention and
Within principle, any modification, equivalent replacement, improvement and so on be should all be included in the protection scope of the present invention.
Claims (10)
1. a kind of Fault Locating Method, it is characterised in that: include the following steps,
S1, basic content verification；
S2, business tine verification；
S3, radio layer verification；
S4, SP layers of verification.
2. a kind of Fault Locating Method according to claim 1, it is characterised in that: in the S1, the basic content school
Test including,
S1.1, system layer verification；
S1.2, client layer verification；
S1.3, terminating layer verification；
S1.4, the verification of core stratum reticulare.
3. a kind of Fault Locating Method according to claim 2, it is characterised in that: in the S1.1, the system layer school
Test including,
S1.1.1 judges whether the time started is empty；
S1.1.2 judges whether the end time is empty；
S1.1.3, judges whether the time started is more than or equal to the end time；
Whether S1.1.4 judges the end time than current time less than 6 months；
S1.1.5, judges whether the time started is less than current time；
Whether S1.1.6 opens the time that judges to begin with end time span less than 30 days；
Whether S1.1.7 judges IMSI not for sky；
S1.1.8, judges whether IMSI digit is equal to 15；
S1.1.9 judges whether IMSI input content is legal；
Whether S1.1.10 judges telephone number not for sky；
S1.1.11, judges whether telephone number digit is equal to 11；
S1.1.12 judges whether telephone number input is legal；
S1.1.13 judges whether HSS interface is abnormal.
4. a kind of Fault Locating Method according to claim 2, it is characterised in that: in the S1.2, the client layer school
Test including,
S1.2.1 judges whether user is industrial application card client；
S1.2.2, judges whether user does not open card in query time section；
S1.2.3, judge user whether not arrearage；
S1.2.4, judges whether user opens 4G；
S1.2.5 judges the whether non-quota in user's SIM card dynamic IP addressing pond.
5. a kind of Fault Locating Method according to claim 2, it is characterised in that: in the S1.3, the terminating layer school
Test including,
S1.3.1, judge user whether off-mode；
S1.3.2, judging user, whether SIM card exits extremely or extremely；
S1.3.3 judges whether user binds particular row card APN correct.
6. a kind of Fault Locating Method according to claim 2, it is characterised in that: in the S1.4, the core network
Layer verifies,
S1.4.1, judges whether HSS signing opens 4G state；
S1.4.2, judges whether HSS signing binds APN；
S1.4.3, judges whether PGW core net binding APN matches with HSS signing APN；
S1.4.4, judges whether PGW core net binding SIM card static IP section matches with HSS；
S1.4.5, judges whether PGW core net binding sound state matches with HSS；
S1.4.6, judge PGW core net binding IP sections of client server end whether mistake；
S1.4.7 judges dns server exception.
7. a kind of Fault Locating Method according to any one of claims 1 to 6, it is characterised in that: in the S2, the industry
Business content authentication includes whether user terminal environment is normal.
8. a kind of Fault Locating Method according to any one of claims 1 to 6, it is characterised in that: in the S3, the nothing
The verification of line layer includes whether user radio environment is normal.
9. a kind of Fault Locating Method according to any one of claims 1 to 6, it is characterised in that: in the S4, the SP
Layer verifies,
S4.1 judges whether same APN business ticket signaling data access server-side is normal；
S4.2 judges whether same APN business ticket is normal with IP sections of users' access server-sides of SIM card；
S4.3 judges whether same APN business words single-user access is normal with server-side destination IP section.
10. a kind of fault location system, it is characterised in that: it comprises the following modules,
Basic content verification, is used to carry out basic content verification；
Business tine verification, is used to carry out business tine verification；
Radio layer verification, is used to carry out radio layer verification；
SP layers of verification are used to carry out SP layers of verification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910258624.6A CN110061866A (en) | 2019-04-01 | 2019-04-01 | A kind of Fault Locating Method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910258624.6A CN110061866A (en) | 2019-04-01 | 2019-04-01 | A kind of Fault Locating Method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110061866A true CN110061866A (en) | 2019-07-26 |
Family
ID=67318081
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910258624.6A Pending CN110061866A (en) | 2019-04-01 | 2019-04-01 | A kind of Fault Locating Method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110061866A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101888658A (en) * | 2010-07-16 | 2010-11-17 | 北京市万网元通信技术有限公司 | GPRS (General Packet Radio Service) core network simulation and test system |
| CN103188652A (en) * | 2011-12-31 | 2013-07-03 | 中国移动通信集团广东有限公司 | Method, device and system for processing mobile phone and SIM card fault |
| CN107809757A (en) * | 2017-10-31 | 2018-03-16 | 贵州力创科技发展有限公司 | A kind of 4G sector applications card detecting system and method |
| CN107872553A (en) * | 2017-10-31 | 2018-04-03 | 贵州力创科技发展有限公司 | A kind of 4G sector applications card detecting system and method |
-
2019
- 2019-04-01 CN CN201910258624.6A patent/CN110061866A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101888658A (en) * | 2010-07-16 | 2010-11-17 | 北京市万网元通信技术有限公司 | GPRS (General Packet Radio Service) core network simulation and test system |
| CN103188652A (en) * | 2011-12-31 | 2013-07-03 | 中国移动通信集团广东有限公司 | Method, device and system for processing mobile phone and SIM card fault |
| CN107809757A (en) * | 2017-10-31 | 2018-03-16 | 贵州力创科技发展有限公司 | A kind of 4G sector applications card detecting system and method |
| CN107872553A (en) * | 2017-10-31 | 2018-04-03 | 贵州力创科技发展有限公司 | A kind of 4G sector applications card detecting system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100473003C (en) | Technique for generating correlation number for use in lawful interception of telecommunications traffic | |
| EP1545114B1 (en) | A method and apparatus for division of revenue of communication among different proprietors | |
| EP0890239B1 (en) | Charge allocation in a multi-user network | |
| CN100574266C (en) | Packet forwarding device | |
| US7526271B2 (en) | Method for implementing prepaid multimedia messaging service | |
| CN102882853A (en) | System and method for internet user authentication | |
| EP1425899B1 (en) | Method for the provision and allocation of call numbers in a telecommunication network | |
| WO2001024122A1 (en) | Method for charging internet services via a mobile telephone | |
| ES2311821T3 (en) | AUTHENTICATION SYSTEM | |
| CN105050068B (en) | A kind of charging bill record detection bearing calibration, device and ticket processing system | |
| CN102685709A (en) | Method and device for auditing charging | |
| US7152103B1 (en) | Lawful communication interception—intercepting communication associated information | |
| CN102137450B (en) | Strategy control method and device as well as gateway | |
| CN106572454A (en) | PCRF addressing method and addressing system | |
| US7505451B2 (en) | Usage-based charging device and usage-based charging method | |
| CN110061866A (en) | A kind of Fault Locating Method and system | |
| EP1464199B1 (en) | Prepaid charging in communication network | |
| CN103812954B (en) | IPv6 address management methods and system | |
| US7310510B2 (en) | Method for ascertaining a billing tariff for billing for a data transfer | |
| CN101765069A (en) | Value added service subscribing method, device and system | |
| US8700073B2 (en) | Method and apparatus for providing mobile messaging enabled event planning, scheduling and tracking service | |
| EP1554903A2 (en) | Message transmission system and method for using sim cards via remote access for economical connections between fixed and mobile radio telephone networks | |
| AU2003221595B8 (en) | Method for separating IP packets which can be allocated to specific groups and IP packet | |
| CN107872553B (en) | 4G industry application card detection system and method | |
| CN1798041A (en) | Charging method in communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190726 |