CN111130855B - Problem positioning method and device - Google Patents
Problem positioning method and device Download PDFInfo
- Publication number
- CN111130855B CN111130855B CN201911236116.4A CN201911236116A CN111130855B CN 111130855 B CN111130855 B CN 111130855B CN 201911236116 A CN201911236116 A CN 201911236116A CN 111130855 B CN111130855 B CN 111130855B
- Authority
- CN
- China
- Prior art keywords
- error
- determining
- complaint information
- account
- return code
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 239000013598 vector Substances 0.000 claims abstract description 50
- 238000012545 processing Methods 0.000 claims abstract description 31
- 230000002159 abnormal effect Effects 0.000 claims abstract description 10
- 238000004891 communication Methods 0.000 claims abstract description 10
- 230000004807 localization Effects 0.000 claims 1
- 230000002776 aggregation Effects 0.000 description 36
- 238000004220 aggregation Methods 0.000 description 36
- 238000007726 management method Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 16
- 230000008859 change Effects 0.000 description 14
- 230000000875 corresponding effect Effects 0.000 description 13
- 230000008569 process Effects 0.000 description 12
- 230000001133 acceleration Effects 0.000 description 11
- 230000004044 response Effects 0.000 description 10
- 241000287828 Gallus gallus Species 0.000 description 7
- 230000006399 behavior Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000010295 mobile communication Methods 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 6
- 238000013475 authorization Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 208000030433 Epiphysiolysis of the hip Diseases 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000000194 supercritical-fluid extraction Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
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
Abstract
The invention provides a problem positioning method and a problem positioning device, relates to the technical field of communication, and solves the problem that as the data volume is increased and network element equipment nodes in a service chain are more, an operator cannot delimit a problem in time after receiving complaints of a user to a special bearing problem, so that the efficiency of fault processing is low. The method comprises the steps of obtaining complaint information; the complaint information is used for indicating that an appointed account has abnormity when using a special bearer to perform appointed service at an appointed time point; determining a problem vector according to the specified account and the specified time point; the complaint information corresponds to the problem vectors one by one; determining a problem positioning result of the complaint information according to the problem positioning judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a problem location method and apparatus.
Background
With the rapid development of mobile communication technology and services, the demands of users on high-quality service perception and differentiated and personalized services are increasing. Especially for services using special bearing such as interactive games, video live broadcast and the like, the sensitivity to time delay and bandwidth is higher.
In recent years, mobile communication networks have evolved from the second Generation mobile communication technology (2nd-Generation, 2G) era to the fourth Generation mobile communication technology (4th-Generation, 4G), and with the opening of the business era of the fifth Generation mobile communication technology (5th-Generation, 5G), the number of mobile communication users, the network size, and the number of network elements have been changed dramatically. The rapid change of the network and the rapid increase of the user bring about the tens of times or even hundreds of times of the workload of the network operation and maintenance, and the learning of new mobile communication knowledge and the accumulation of maintenance experience require a certain time, so the network operation and maintenance personnel face huge working pressure and challenges. On the other hand, the end-to-end service relates to front end, core network, bearer, wireless and other links, and the personnel handling complaints in the existing operation and maintenance system is usually non-technical personnel, and it is difficult to delimit and distribute the problems deeply to the corresponding departments, resulting in lower efficiency of fault handling.
Therefore, as the data volume increases and the number of network element equipment nodes in the service chain increases, the operator cannot delimit the problem in time after receiving the complaint of the user to the special bearing problem, so that the efficiency of fault processing is low.
Disclosure of Invention
The invention provides a problem positioning method and a problem positioning device, which solve the problem that as the data volume is increased and network element equipment nodes in a service chain are more, an operator cannot delimit the problem in time after receiving complaints of a user to a special bearing problem, so that the efficiency of fault processing is lower.
In order to achieve the purpose, the invention adopts the following technical scheme:
in a first aspect, the present invention provides a problem location method, including: complaint information is obtained; the complaint information is used for indicating that an appointed account has abnormity when using a special bearer to perform appointed service at an appointed time point; determining a problem vector according to the specified account and the specified time point; the complaint information corresponds to the problem vectors one by one; determining a problem positioning result of the complaint information according to the problem positioning judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason.
According to the scheme, the problem positioning method provided by the invention can be used for converting the complaint information of the users into the problem vector, so that the complaint information of each user can be described in a normalized mode; when the problem positioning judgment model is a model generated by an existing expert case base, even if operation and maintenance personnel have no working experience, the problem positioning result of complaint information can be determined according to the problem positioning method provided by the embodiment of the invention, so that the problem that the fault processing efficiency is low because the operator cannot delimit the problem timely after receiving complaints of the special bearing problem from the user along with the increase of data volume and more network element equipment nodes in a service chain is solved.
In a second aspect, the present invention provides a problem location apparatus for a proprietary bearer, comprising: an acquisition unit configured to acquire complaint information; the complaint information is used for indicating that an appointed account has abnormity when using a special bearer to perform appointed service at an appointed time point; the processing unit is used for determining a problem vector according to the specified account number acquired by the acquisition unit and the specified time point acquired by the acquisition unit; the complaint information corresponds to the problem vectors one by one; the processing unit is also used for determining a problem positioning result of the complaint information according to the problem positioning judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason.
In a third aspect, the present invention provides a problem location apparatus for a dedicated bearer, including: communication interface, processor, memory, bus; the memory is used for storing computer executable instructions, the processor is connected with the memory through the bus, and when the problem locating device of the proprietary bearer runs, the processor executes the computer executable instructions stored by the memory so as to enable the problem locating device of the proprietary bearer to execute the method provided by the first aspect.
In a fourth aspect, the present invention provides a computer-readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method as provided in the first aspect above.
It can be understood that any of the above-mentioned proprietary bearing problem location apparatuses is used to execute the method according to the first aspect, and therefore, the beneficial effects that can be achieved by the above-mentioned problem location apparatus refer to the beneficial effects of the method according to the first aspect and the corresponding solutions in the following detailed description, which are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a network architecture diagram of a problem location method provided by an embodiment of the present invention;
fig. 2 is a network architecture in a non-roaming state and a roaming state in the prior art;
FIG. 3 is a flow chart of a prior art acceleration service;
FIG. 4 is a flowchart illustrating a problem location method according to an embodiment of the present invention;
FIG. 5 is a second flowchart illustrating a problem location method according to an embodiment of the present invention;
FIG. 6-a is a third schematic flow chart of a problem location method according to an embodiment of the present invention;
FIG. 6-b is a fourth flowchart illustrating a problem locating method according to an embodiment of the present invention;
FIG. 7 is a fifth flowchart illustrating a problem locating method according to an embodiment of the present invention;
FIG. 8 is a sixth flowchart illustrating a problem locating method according to an embodiment of the present invention;
FIG. 9 is a seventh flowchart illustrating a problem locating method according to an embodiment of the present invention;
FIG. 10 is an eighth schematic flowchart of a problem location method according to an embodiment of the present invention;
FIG. 11 is a ninth flowchart illustrating a problem location method according to an embodiment of the present invention;
FIG. 12 is a flowchart illustrating an apparatus for problem location according to an embodiment of the present invention;
fig. 13 is a second flowchart of a problem locating apparatus according to an embodiment of the present invention.
Reference numerals are as follows:
problem location device-10;
an acquisition unit-101; a processing unit-102.
Detailed Description
Embodiments of the present invention will be described below with reference to the accompanying drawings.
For the convenience of clearly describing the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, the words "first", "second", and the like are used for distinguishing the same items or similar items with basically the same functions and actions, and those skilled in the art can understand that the words "first", "second", and the like are not limited in number or execution order.
Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the present embodiments, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
In the description of the embodiments of the present invention, the meaning of "a plurality" means two or more unless otherwise specified. For example, a plurality of networks refers to two or more networks.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. The symbol "/" herein denotes a relationship in which the associated object is or, for example, a/B denotes a or B.
The technology to which this application relates is explained below to facilitate the understanding of the reader:
with the rapid development of traffic, extensive network operations are evolving towards fine operations, general services are evolving towards differentiated services, and networks are evolving towards users. Refined, differentiated and personalized services are imperative. Under the background, operators combine the vertical industry markets such as enterprise clients, internet companies and financial enterprises by creating differentiated end-to-end services, deeply open network capacity, cooperate to carry out deep and detailed flow management and capacity opening, and comprehensively improve the inherent development requirement of network value.
The 4G network architecture provides technical support for differentiated services, and the implementation of the 4G quality of service (QoS) technology is based on a dynamic QoS management mechanism of a Policy and Charging Control (PCC) system. As shown in fig. 1, the third-party application calls a QOS service request, modification and release function of a QOS management platform (management platform of QOS, MPQ) according to a requirement. MPQ is the only link between the operator and the third party, and its functions include authentication of messages, mapping of external parameters to internal parameters, and so on. The MPQ sends the request and the related parameters to an application access control function (AAC) in a hypertext transfer protocol (HTTP) request manner. AAC as a protocol conversion node converts HTTP request into a network universal interface protocol such as Diameter protocol, and implements a dynamic QoS management mechanism by calling (PCC) system. A Policy and Charging Rule Function (PCRF) functional entity in the PCC system includes policy and charging rule function (policy and charging rule function, PCRF) functions of receiving inputs from a Policy and Charging Enforcement Function (PCEF), a Subscription Profile Repository (SPR) and an AAC, providing the PCEF with network control functions related to traffic data flow detection, gating, QoS-based and charging flow-based (except credit control), and making PCC decisions in combination with the customized information of the PCRF. The PCEF mainly contains the detection of traffic data flows, policy enforcement and flow-based charging functions. The functional entity is located in a gateway, such as a Gateway GPRS Support Node (GGSN) gateway of a General Packet Radio Service (GPRS), a public data network (public data network, PDN) gateway (PDN Gate, PGW) of an Evolved Packet Core (EPC), a Packet Data Gateway (PDG) in a Wireless Local Area Network (WLAN), and may also be deployed independently, where PGW is used for example in this document.
The dedicated bearer is established between the PGW, a Serving Gateway (SGW) and a wireless base station to ensure QOS. From the perspective of the scene, the states can be divided into roaming state and non-roaming state. In a non-roaming state, when various application services (OTT)/users initiate service guarantee requests to the users through the internet, messages are transferred to the PCRF, the PGW and the wireless device of the user's home province through the network, and a special channel is established for the users through resource allocation of the province. And in the roaming state, the service request is sent to the PCRF of the user attribution province, the PGW adopting the attribution province or the PGW adopting the visiting province is distinguished according to the attribute of the user (such as whether the user is a high-end user), and the base station equipment adopting the visiting province is used in the wireless consideration of the near access principle due to the fact that the user is in the visiting province. In fig. 2, the left side is a non-roaming state, and the right side is a roaming state. In fig. 2, the upper part of the black horizontal line is the province of the home province, and the lower part is the province of the visit province. As shown in fig. 3, the existing acceleration service process includes:
1. the user has completed the attachment and default bearer establishment in the EPC network and is able to use the data service.
2. The OTT server initiates an acceleration request based on an HTTP (hyper text transport protocol) to the PCC capability open service management platform, wherein the request carries the public network Internet Protocol (IP) and the private network IP address of User Equipment (UE), and the IP address information (the maximum supports 4 Internet protocol versions 4 (IPv 4) or 4 Internet protocol versions 6(Internet protocol versions 6, IPv 6)) of the server and the grade of the minimum uplink/downlink guaranteed rate.
3. And the PCC capability open service management platform performs an authentication (optional) process and a number taking process. The PCC capability open service management platform obtains a user mobile subscriber number (MSISDN) from the PGW through the number fetching platform according to the IP addresses of the user public network and the private network.
4. The PCC capability open service management platform sends a service acceleration request POST message based on an HTTP protocol to the AAC, wherein the request comprises a service identifier, a user public network IP address, a private network IP address, an MSISDN, a media type, a QOS attribute priority, an uplink/downlink minimum guarantee rate, a QOS duration and stream resource characteristics (including an IP quintuple, required bandwidth and the like).
5. The AAC obtains a POST acceleration request message, starts an Rx session based on a Diameter protocol, maps media information in the POST message into an Rx interface AA-request (AAR) command message, and forwards the message to a routing agent node (DRA). Wherein, a complete user IP Address is provided through a frame-IP-Address AVP (IP Address frame attribute) or a frame-IPv 6-Prefix AVP (PV6 frame Prefix attribute), and corresponding service information is provided in a Media-Component-Description AVP (Media sub-Description information attribute). The application Request message (AA-Request, AAR) message includes: the originating and destination Host, Realm, AF-Application-Identifier, AF-Charging-Identifier, Reservation-Priority, Framed-IP-Address, Framed-IPv6-Prefix and Media-Component-Description contain Media information based on Application session, including bandwidth, types of Media streams and stream quintuple.
6. And the DRA receives the AAR message and acquires the PCRF route of the user home location according to the MSISDN number of the user.
7. The DRA forwards the AAR message to the PCRF of the user home.
8. And the PCRF makes policy decision according to the media information carried in the AAR message and provides authorized QOS.
9. The PCRF sends a QOS Class Identifier (QCI), an ARP, a Guaranteed Bit Rate (GBR) and a Maximum Bit Rate (MBR) and PCC rules to the home DRA via an authentication-auth-request (RAR) message.
10. And the DRA receives the RAR message and acquires the PGW route of the user visited place/home location according to the MSISDN number of the user.
11. And the DRA forwards the RAR message to a user PGW.
12. And the PGW receives the re-authentication/authorization request message RAR and reports a re-authentication/authorization response message RAA response to the PCRF.
13. And the PCRF transmits an AAA response authorization request result message to the AAC through DRA signaling network switching according to the RAA message returned by the PGW.
14. The network acceleration capability platform (AAC) sends a POST response message based on an HTTP protocol to the network acceleration service management platform.
15. And the PCC capability open service management platform sends an acceleration response message based on the HTTP protocol to the OTT server.
16. And completing the establishment of the special load. The PGW initiates a dedicated Bearer establishment Request, and indicates a mobility management entity function (MME) to establish a dedicated Bearer through a Create Bearer Request; after receiving the Create Bearer Request message, the MME sends an active differentiated EPS Bearer context Request message to a base station (evolved node B, eNB) for requesting activation of an Evolved Packet System (EPS) Bearer context, and the eNodeB configures the EPS Bearer context through RRC Connection configuration.
17. UE sends Radio Resource Control (RRC) reconfiguration success to eNodeB, eNodeB sends activated truncated EPS bearer context accept message to MME, which is used to confirm activation of a special EPS bearer context; the PGW receives the Create Bearer Response message, and confirms that the dedicated Bearer has been established.
18. The PGW sends a credit control-request (CCR) message to the PCRF, notifying that the resource reservation is successful. And the PCRF returns a credit control answer message CCA response to the PGW.
19. And when the PCRF receives the report of the resource reservation success event of the PGW, sending a re-authentication/authorization request message RAR message to the AAC through DRA forwarding, and informing that the dedicated load establishment is successful.
20. AAC returns a re-authentication/authorization response message RAA message to PCRF.
21. The network acceleration capability platform (AAC) sends a POST response message based on an HTTP protocol to the network acceleration service management platform.
22. And the PCC capability open service management platform sends an acceleration response message based on the HTTP protocol to the OTT server.
Therefore, when the user uses the special bearer to carry out the service, the error of any network equipment can cause the failure of the service.
In order to solve the problem that the efficiency of fault handling is low because an operator cannot delimit a problem in time after receiving a complaint from a user on a proprietary bearer problem as the data volume increases and the network element devices in a service chain have more nodes, a problem positioning method provided by an embodiment of the present invention is applied to a network architecture as shown in fig. 4, and includes: the system comprises UE, eNb, a core network, a Service Capability Exposure Frame (SCEF), a service management platform, an application server and a problem positioning device; the core network includes an MME, a Home Subscriber Server (HSS), a PCRF, a system architecture evolution-gateway (SAE-GW)/a GGSN/PGW. After an operator receives complaints of users on special bearing problems, the problems are bounded in time according to the problem positioning method provided by the embodiment of the invention, so that the efficiency of fault processing is improved.
For example, the problem locating device is taken as a server for explanation, and the specific implementation process is as follows:
example one
An embodiment of the present invention provides a problem location method, as shown in fig. 5, including:
s101, complaint information is obtained; the complaint information is used for indicating that an abnormal condition exists when the specified account uses the special bearing to perform the specified service at the specified time point.
For example, in practical applications, the complaint information may come from a front-end complaint; such as: when receiving a specified account number (such as '13800000001') of the user a at a specified time point (such as '10/14/9/00 in 2019') and using a special bearer to perform a specified service (such as 'flight service'), a front-end customer service person records and inputs the problem of network blocking into the server provided by the embodiment of the invention, so that the server can acquire complaint information.
S102, determining a problem vector according to the specified account and the specified time point; the complaint information corresponds to the problem vectors one by one.
Optionally, the problem vector is determined according to the specified account and the specified time point, and as shown in fig. 6-a and fig. 7, the method includes:
s1020, according to the specified account and the specified time point, determining an error return code, account information and operation parameters of the network equipment providing the special bearer.
Specifically, the server uses a dedicated bearer to perform service flow information in an interface interaction database according to the specified account at the specified time.
Illustratively, the extracted service flow line comprises failure of resource application for Tencent in 2019, 10 and 14 days 9: 0013800000001, success of resource application for Tencent in 2019, 10 and 14 days 8.5513800000001 in 2019, 10 and 14 days 9:15, and success of service side deletion in 2019, 10 and 14 days; then, the server carries out problem positioning inquiry according to the service flow information.
Specifically, in order to more accurately locate the problem, the service flow information in a preset time period before and after the specified time point can be acquired, so that the problem of the specified account can be conveniently located; illustratively, if the specified time point is 2019, 10, 14, 9, 00 and the preset time period is 10 minutes, service data of 8:55 in 14, 10, 14, 9:10 in 10, 2019 can be acquired, and the problem location of the specified account is performed.
Specifically, the service data in the interface interaction database can be established according to the special load establishing service detail data and the network basic information data; the service interface data between the service management platform and the Application Function (AF) and the SCEF includes detailed information of a total amount of user requests, modifications and deletions. Such as: at least one of request time, service type, third party client identification, third party order identification, account balance, consumption amount, acceptance time, guarantee duration, destination IP address, user private network IP address, province score, mobile phone number, correlation identification, returned result, content description, guarantee level, AAC manufacturer, roaming identification and priority level; PGW/GGSN network service information, including at least one of message type identification, user name, port number, service type, protocol type, user IP address, target network ID, user number identification, GGSN/PGW IP address, SGSN/MME IP address, charging attribute, uplink flow statistics, downlink flow statistics, and session duration; the basic information of core network elements such as MME, PCRF, PGW/GGSN and the like comprises at least one item of province/city, MME identification, PCRF identification, PGW/GGSN identification, MME manufacturer, PCRF manufacturer, PGW/GGSN manufacturer, pool grouping identification and associated wireless identification; the basic information of the wireless equipment comprises at least one of city/district, eNodeB identification, district identification, sector number, longitude and latitude, antenna number, uplink and downlink frequency points, physical district identification code, district carrier frequency transmitting power, equipment manufacturer, duplex mode, district coverage type, district coverage range and PLMN identification.
Specifically, determining an error return code, account information, and an operation parameter of a network device providing a dedicated bearer according to a specified account and a specified time point includes:
adding, deleting, modifying, opening an account and other service data according to the specified account and the specified time point; associating PGW manufacturers and PGW identifications in a basic information table of the core network element according to the private network IP address of the specified account; the PCRF manufacturer, the PCRF identifier and the like in the basic information of the core network element can be associated according to the province to which the user account belongs; the network element device performing the specified service according to the user account may be associated with the wireless device basis information.
It should be noted that the SCEF manufacturer, the PCRF manufacturer, the number of concurrent sessions, the account opening information, the provincial-owned dimensional service aggregation level identifier, the PGW dimensional service aggregation level identifier, the PCRF session aggregation level identifier, the PGW session aggregation level identifier, the service dimensional aggregation level identifier, the user private network IP address change identifier, the callback completion identifier, the user status, and the error return code are unique values for one case; exemplary, correlated data is shown in table 1.
TABLE 1
The attribution province dimension business aggregation degree mark is used for representing the behavior that problem business (such as 'flight news') of the province attribution of the specified account number exceeds an expected amplitude or success index in a set range; the excess is 1 and the excess is 0.
For example, assuming that the setting time of province a is 1 day, the success rate of flight service is 90%, and the expected amplitude is 5%. Inquiring about the occurrence time of the problem in 2019, 10, 14 and 9:00, calculating the success rate of the flight service in the province A of 14 days where the problem is located, and comparing the success rate with the success rate of the flight service in the province in 13 days (the success rate of the flight service in the previous day is generally calculated in advance). If the success rate of the Tencent service in day 14 of the province A is less than 90%, or the difference of the success rate of the Tencent service in day 14 and day 13 is more than 5%, the setting value is 1.
The PGW dimension business aggregation degree mark is used for representing the behavior that problem business (Tencent) under a PGW providing service for a specified account number exceeds an expected amplitude or a success index in a set range; the excess is 1 and the excess is 0; the calculation mode is similar to that of the attribution province dimension business aggregation degree identification, and the difference is that the same PGW is counted.
The PCRF session aggregation degree identifier is used for representing that all services (more than problem Tencent services, which may include chicken eating, fire and shadow eating and the like) under the PCRF providing services for the specified account have behaviors exceeding expected amplitude or success indexes within a set range; the excess is 1 and the excess is 0. The calculation mode is similar to that of the aggregation degree identification of the dimension service of the province of attribution, and the difference is that the same PCRF identification granularity is counted, and only the specified service is counted; illustratively, the specified service includes an Tencent service, wherein the Tencent service is classified as eating chicken or a fire shadow.
The PGW session aggregation level identifier is used to indicate that all services (more than problem Tencent services, which may include chicken eating, fire and shadow eating, etc.) in the PGW providing services for a specific account have behaviors exceeding an expected range or success index within a set range. The calculation mode is similar to that of the attribution provincial dimension business aggregation degree identification, and the difference is that the same PGW is counted, and only the specified business is counted; illustratively, the specified service includes an Tencent service, wherein the Tencent service is classified as eating chicken or a fire shadow.
The service dimension aggregation degree identification is used for indicating that the success rate of the specified service compared with other services is lower than a set difference value. For example, the success rate of Tencent service in 2019, 10 and 14 days is 85%, and the success rate of chicken eating service in other services such as chicken eating is 92%. And calculating the difference value of the success rate of the Tencent service and the success rate of the chicken eating service as a, if a is more than 5 percent of the set value, the difference value is expressed as 1, and if not, the difference value is 0.
And S1021, determining a problem vector according to the error return code, the account number information and the operation parameters.
Specifically, in an actual application, when a problem is converted into a vector, the problem vector may be determined according to a predetermined vector conversion rule.
Illustratively, the adjacent transformation rules are as follows:
the error return codes correspond to different error return code sets by different network equipment; if the set of error return codes of the service management platform is [3000, 4000], when a problem occurs in the service management platform, the error return code at this time may be 3025.
And the account opening information takes a value of 1 when the user information is an opened account, and takes a value of 0 when the user information is not opened account.
And the user state takes a value of 1 when the network standard of the user is 3G, and takes a value of 0 when the network standard of the user is other network standards.
The SCEF manufacturer uses different numbers for representation, such as 1 for SCEF equipment of manufacturer a and 2 for SCEF equipment of manufacturer B.
The PCRF manufacturer uses different numbers for representation, for example, the number 1 represents the PCRF device of manufacturer a, and 2 represents the PCRF device of manufacturer B.
The number of concurrent sessions is expressed in terms of the actual number of session returns.
The attribution province dimension business aggregation level identifier, the PGW dimension business aggregation level identifier, the PCRF session aggregation level identifier, the PGW session aggregation level identifier, and the business dimension aggregation level identifier are expressed in the manner described in the above S1020.
The user private network IP address change identification is used for indicating whether the private network IP address of the user is changed or not, and is represented by 1 when the private network IP address of the user is changed, and is represented by 0 when the private network IP address of the user is not changed.
The callback completion flag is used to indicate the final message of the dedicated bearer establishment completion, and is indicated by 1 when the callback is completed (indicating that the callback is successful or fails) and by 0 when the callback is not completed (no callback message is returned).
Specifically, for convenience, the positions of the error return code, the account information and the operation parameters in the problem vector can be specified, so that the problem vector normalization is realized; illustratively, the error return code, the account information and the operation parameters obtained in step S1020 are shown in table 2.
TABLE 2
From the error return code, account information, and operating parameters in table 2, the problem vector may be determined to be [3025, 1, 0, 1, 1, 19, 0, 1, 1, 1, 0, 0, 0 ].
S103, determining a problem positioning result of the complaint information according to the problem positioning judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason.
Optionally, the problem location result of the complaint information is determined according to the problem location judgment model and the problem vector, as shown in fig. 6-a and 8, the problem location result includes:
s1030, determining a problem positioning result of the complaint information according to the error code set and the value of the error return code of the network equipment; wherein each network device corresponds to a set of error codes.
Specifically, in order to distinguish error return codes of different network devices, different error return codes can be set for different devices, so that problems can be located more quickly.
Illustratively, if the value of the error return code is P i (ii) a Wherein, the error code set of the service management platform is P ═ { P ═ P 1 ，P 2 .......P n Due to P i And if the error code belongs to the error code set of the service management platform, determining that the problem positioning result is that the service management platform has a problem.
If the value of the error return code is Q i (ii) a Wherein, the error code set of the interaction between the service management platform and the AF is Q ═ { Q ═ Q 1 ，Q 2. ......Q n Due to Q i And if the error code set belongs to the error code set interacted with the AF by the service management platform, determining that the problem positioning result is that the AF side (the third party application side) has a problem.
Optionally, the problem location result of the complaint information is determined according to the problem location judgment model and the problem vector, and as shown in fig. 6-a, 6-b, and 9, the problem location result includes:
s1031, determining a problem positioning result of the complaint information according to the error code set, the error return code and the operation parameters of the network equipment; wherein each network device corresponds to a set of error codes.
Specifically, in order to distinguish the error return codes of different network devices, different error return codes can be set for different devices, so that problems can be located more quickly.
Illustratively, if the value of the error return code is S i Then according to S i Determining a manufacturer of the corresponding SCFE; wherein, the error code set of the SCEF manufacturer is S ═ S 1 ，S 2. ......S n Due to S i Set of error codes belonging to SCEF manufacturer, and S i If the manufacturer of the corresponding SCFE is manufacturer A, determining a problem positioning resultThere is a problem with the SCFE equipment of manufacturer a.
If the value of the error return code is Ei, the Ei is the error return code of which the resource waiting time is overtime, and the value of the PGW dimension business aggregation degree identification is 1, determining that the problem positioning result is that the PGW has a problem; and if the value of the error return code is Ei, the Ei is the error return code of which the resource waiting time is overtime, and the value of the PGW dimension business aggregation degree identifier is 0, determining that the problem location result is that eNb has a problem.
If the value of the error return code is H i And H is i If the value of the attribution provincial dimensionality service aggregation degree identification is 1, determining that the problem positioning result is that the PCRF has a problem; if the value of the error return code is H i And H is i When the error return code fails to be established for the resource, the value of the PGW dimension business aggregation degree identification is 0, and the PCRF session aggregation degree identification is 1, determining that the problem positioning result is that the PCRF has a problem; if the value of the error return code is H i And H is i When the error return code fails to be established for the resource, the value of the PGW dimension business aggregation degree identifier is 0, the value of the PCRF session aggregation degree identifier is 0, and the value of the PGW dimension business aggregation degree identifier is 0, the problem location result is determined to be eNb or caused by other reasons; if the value of the error return code is H i And H is i And when the error return code failed to establish the resource is obtained, the value of the PGW dimension business aggregation degree identifier is 0, the PCRF session aggregation degree identifier is 0, and the value of the PGW dimension business aggregation degree identifier is 1, determining that the problem positioning result is PGW.
If the value of the error return code is 5006, the number of coexisting sessions is equal to the maximum number of sessions, and the PCRF manufacturer is a specified manufacturer, it is determined that the problem location result is caused by an unreasonable sending mechanism of an AF side (a third party application side); if the value of the error return code is 5006, the number of coexisting sessions is equal to the maximum number of sessions, and the PCRF manufacturer is not an appointed manufacturer, determining that the problem positioning result is caused by the resource overrun of the PCRF; if the value of the error return code is 5006, the number of coexisting sessions is not equal to the maximum number of sessions, and the PCRF manufacturer is a specified manufacturer, determining that the problem positioning result is caused by the resource overrun of the PCRF; and if the value of the error return code is 5006, the number of coexisting sessions is not equal to the maximum number of sessions, and the PCRF manufacturer is not the appointed manufacturer, determining that the problem positioning result is caused by the resource overrun of the PCRF.
If the value of the error return code is 5003 and the value of the callback completion identifier is 1, determining that the problem positioning result is that the PCRF resource is out of limit; if the value of the error return code is 5003 and the value of the callback completion identifier is 0, determining that the problem location result is the AF side (third-party application side).
And if the value of the error return code is other specified values, determining that the problem positioning result is PCRF.
If the value of the error return code is 5063 and the value of the service dimension aggregation degree identification is 0, determining that the problem positioning result is a service management platform; if the value of the error return code is 5063, the value of the service dimension aggregation degree identifier is 1, and the value of the attribution province dimension service aggregation degree identifier is 0, determining that the problem positioning result is PCRF; if the value of the error return code is 5063, the value of the service dimension aggregation degree identifier is 1, the value of the attribution dimension service aggregation degree identifier is 1, and the value of the user private network IP address change identifier is 1, determining that the problem positioning result is PGW; and if the value of the error return code is 5063, the value of the service dimension aggregation degree identifier is 1, the value of the attribution province dimension service aggregation degree identifier is 1, and the value of the user private network IP address change identifier is 0, determining that the problem positioning result is caused by other reasons.
Optionally, the problem location result of the complaint information is determined according to the problem location judgment model and the problem vector, and as shown in fig. 6-a, 6-b, and 10, the problem location result includes:
s1032, determining a problem positioning result of the complaint information according to the error code set of the network equipment, the value of the error return code and the account information; wherein each network device corresponds to a set of error codes.
Specifically, in order to distinguish the error return codes of different network devices, different error return codes can be set for different devices, so that problems can be located more quickly.
For example, if the value of the error return code is 5065 and the value of the user information is 0, it is determined that the problem location result is caused by a subscription, and a service needs to be registered and opened first.
Optionally, the problem location result of the complaint information is determined according to the problem location determination model and the problem vector, as shown in fig. 6-a, 6-b, and 11, including:
s1033, according to an error code set of the network equipment, a value of an error return code, account information and operation parameters, determining a problem positioning result of the complaint information; wherein each network device corresponds to a set of error codes.
Specifically, in order to distinguish the error return codes of different network devices, different error return codes can be set for different devices, so that problems can be located more quickly.
Illustratively, if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is equal to the maximum number of sessions, and the PCRF manufacturer is a designated manufacturer, it is determined that the problem location result is the AF side (third party application side).
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is a designated manufacturer, and the value of the user private network IP address change identifier is 0, determining that the problem positioning result is the user behavior.
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is not an appointed manufacturer, and the value of the user private network IP address change identifier is 0, determining that the problem positioning result is the user behavior.
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is equal to the maximum number of sessions, the PCRF manufacturer is not an appointed manufacturer, and the value of the user private network IP address change identifier is 0, determining that the problem positioning result is the user behavior.
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is a designated manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 1, determining that the problem location result is that the user falls back by 3 g.
If the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is not an appointed manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 1, determining that the problem location result is that the user falls back by 3 g;
and if the value of the error return code is 5065, the value of the user information is 1, the number of the coexisting sessions is equal to the maximum number of sessions, the PCRF manufacturer is not an appointed manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 1, determining that the problem location result is that the user falls back by 3 g.
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is a designated manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 0, determining that the problem positioning result is other reasons.
And if the value of the error return code is 5065, the value of the user information is 1, the number of coexisting sessions is not equal to the maximum number of sessions, the PCRF manufacturer is not an appointed manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 0, determining that the problem positioning result is other reasons.
And if the value of the error return code is 5065, the value of the user information is 1, the number of the coexisting sessions is equal to the maximum number of the sessions, the PCRF manufacturer is not an appointed manufacturer, the value of the user private network IP address change identifier is 1, and the value of the user state is 0, determining that the problem positioning result is other reasons.
According to the scheme, the problem positioning method provided by the embodiment of the invention can describe the complaint information of each user in a normalized manner by converting the complaint information of the user into the problem vector; when the problem positioning judgment model is a model generated by an existing expert case base, even if operation and maintenance personnel have no working experience, the problem positioning result of complaint information can be determined according to the problem positioning method provided by the embodiment of the invention, so that the problem that the fault processing efficiency is low because the operator cannot delimit the problem timely after receiving complaints of the special bearing problem from the user along with the increase of data volume and more network element equipment nodes in a service chain is solved.
Example two
An embodiment of the present invention provides a proprietary bearing problem locating device 10, as shown in fig. 12, comprising:
an obtaining unit 101, configured to obtain complaint information; the complaint information is used for indicating that an abnormal condition exists when the specified account uses the special bearer to perform the specified service at the specified time point.
The processing unit 102 is configured to determine a problem vector according to the specified account number acquired by the acquisition unit 101 and the specified time point acquired by the acquisition unit 101; the complaint information corresponds to the problem vectors one by one.
The processing unit 102 is further configured to determine a problem location result of the complaint information according to the problem location determination model and the problem vector; the problem positioning and judging model comprises a corresponding relation between a problem vector and an abnormal reason.
Optionally, the processing unit 102 is specifically configured to determine an error return code, account information, and an operation parameter of a network device providing a dedicated bearer according to the specified account obtained by the obtaining unit 101 and the specified time point obtained by the obtaining unit 101.
The processing unit 102 is specifically configured to determine a problem vector according to the error return code, the account information, and the operation parameter.
Optionally, the processing unit 102 is specifically configured to determine a problem location result of the complaint information according to the error code set and the error return code of the network device; wherein each network device corresponds to a set of error codes.
Optionally, the processing unit 102 is specifically configured to determine a problem positioning result of the complaint information according to an error code set, an error return code, and an operation parameter of the network device; wherein each network device corresponds to a set of error codes.
Optionally, the processing unit 102 is specifically configured to determine a problem positioning result of the complaint information according to the error code set, the error return code, and the account information of the network device; wherein each network device corresponds to a set of error codes.
Optionally, the processing unit 102 is specifically configured to determine a problem location result of the complaint information according to an error code set, an error return code, account information, and an operation parameter of the network device; wherein each network device corresponds to a set of error codes.
All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and the function thereof is not described herein again.
The problem locating device 10, which is exclusively carried in the case of integrated modules, comprises: the device comprises a storage unit, a processing unit and an acquisition unit. The processing unit is configured to control and manage the action of the problem locating device of the dedicated bearer, for example, the processing unit is configured to support the problem locating device of the dedicated bearer to execute the processes S101, S102, and S103 in fig. 5; the acquisition unit is used for supporting the information interaction between the problem positioning device exclusively borne and other equipment. And the storage unit is used for storing the program codes and data of the problem positioning device exclusively born.
For example, the processing unit is a processor, the storage unit is a memory, and the obtaining unit is a communication interface. The problem locating device of the proprietary bearer is shown in fig. 13 and includes a communication interface 501, a processor 502, a memory 503 and a bus 504, where the communication interface 501 and the processor 502 are connected to the memory 503 through the bus 504.
The processor 502 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application-Specific Integrated Circuit (ASIC), or one or more Integrated circuits for controlling the execution of programs according to the present disclosure.
The Memory 503 may be a Read-Only Memory (ROM) or other types of static Memory devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic Memory devices that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic Disc storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.
The memory 503 is used for storing application program codes for executing the scheme of the application, and the processor 502 controls the execution. The communication interface 501 is used for information interaction with other devices, for example, with a remote controller. The processor 502 is configured to execute application program code stored in the memory 503 to implement the methods described in the embodiments of the present application.
Additionally, a computing storage medium (or media) is also provided that includes instructions that when executed perform the method operations performed by the proprietary bearing problem location apparatus of the embodiments described above. Additionally, a computer program product is also provided, comprising the above-described computing storage medium (or media).
It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It can be understood that any of the above-mentioned proprietary bearing problem positioning apparatuses is used to execute a corresponding method of the above-mentioned embodiments, and therefore, the beneficial effects that can be achieved by the above-mentioned problem positioning apparatuses refer to the beneficial effects of the method of the above-mentioned embodiment one and the corresponding scheme in the following detailed description, which are not described herein again.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. A problem location method, comprising:
obtaining complaint information; the complaint information is used for indicating that an abnormal condition exists when the specified account uses a special bearer to perform specified service at a specified time point;
determining a problem vector according to the specified account and the specified time point; the complaint information corresponds to the problem vectors one by one;
determining a problem positioning result of the complaint information according to a problem positioning judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason;
determining a problem vector according to the specified account and the specified time point, including:
determining an error return code, account information and operation parameters of the network equipment providing the special bearer according to the specified account and the specified time point;
determining a problem vector according to the error return code, the account information and the operation parameters;
the determining a problem location result of the complaint information according to the problem location judgment model and the problem vector includes:
determining a problem positioning result of the complaint information according to the error code set of the network equipment and the value of the error return code; wherein each network device corresponds to a set of error codes.
2. The problem location method according to claim 1, wherein the determining a problem location result of the complaint information according to the problem location determination model and the problem vector further comprises:
determining a problem positioning result of the complaint information according to the error code set, the error return code and the operation parameters of the network equipment; wherein each network device corresponds to a set of error codes.
3. The problem location method according to claim 1, wherein the determining a problem location result of the complaint information according to the problem location determination model and the problem vector further comprises:
determining a problem positioning result of the complaint information according to an error code set of the network equipment, the value of the error return code and the account information; wherein each network device corresponds to a set of error codes.
4. The problem location method according to claim 1, wherein the determining a problem location result of the complaint information according to the problem location determination model and the problem vector further comprises:
determining a problem positioning result of the complaint information according to an error code set of the network equipment, a value of the error return code, the account information and the operation parameter; wherein each network device corresponds to a set of error codes.
5. A problem locating device for proprietary bearers, comprising:
an acquisition unit configured to acquire complaint information; the complaint information is used for indicating that an appointed account has abnormity when using a special bearer to perform appointed service at an appointed time point;
the processing unit is used for determining a problem vector according to the specified account number acquired by the acquisition unit and the specified time point acquired by the acquisition unit; the complaint information corresponds to the problem vectors one by one;
the processing unit is further configured to determine a problem location result of the complaint information according to a problem location judgment model and the problem vector; the problem positioning judgment model comprises a corresponding relation between a problem vector and an abnormal reason;
the processing unit is specifically configured to determine an error return code, account information, and an operation parameter of the network device providing the dedicated bearer according to the specified account acquired by the acquiring unit and the specified time point acquired by the acquiring unit;
the processing unit is specifically configured to determine a problem vector according to the error return code, the account information, and the operation parameter;
the processing unit is specifically configured to determine a problem location result of the complaint information according to the error code set and the error return code of the network device; wherein each network device corresponds to a set of error codes.
6. The problem location device of the proprietary bearer according to claim 5, wherein the processing unit is specifically configured to determine a problem location result of the complaint information according to an error code set of the network device, the error return code, and the operation parameter; wherein each network device corresponds to a set of error codes.
7. The problem location device of the proprietary bearer according to claim 5, wherein the processing unit is specifically configured to determine a problem location result of the complaint information according to an error code set of the network device, the error return code, and the account information; wherein each network device corresponds to a set of error codes.
8. The problem positioning device of the proprietary bearer according to claim 5, wherein the processing unit is specifically configured to determine a problem positioning result of the complaint information according to an error code set of the network device, the error return code, the account information, and the operation parameter; wherein each network device corresponds to a set of error codes.
9. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the problem localization method of any one of claims 1-4 above.
10. A proprietary bearing problem locating device, comprising: communication interface, processor, memory, bus; the memory is used for storing computer-executable instructions, the processor is connected with the memory through the bus, and when the problem locating device of the exclusive bearer runs, the processor executes the computer-executable instructions stored by the memory so as to enable the problem locating device of the exclusive bearer to execute the problem locating method according to any one of the claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911236116.4A CN111130855B (en) | 2019-12-05 | 2019-12-05 | Problem positioning method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911236116.4A CN111130855B (en) | 2019-12-05 | 2019-12-05 | Problem positioning method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111130855A CN111130855A (en) | 2020-05-08 |
| CN111130855B true CN111130855B (en) | 2022-08-12 |
Family
ID=70496176
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911236116.4A Active CN111130855B (en) | 2019-12-05 | 2019-12-05 | Problem positioning method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111130855B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113762978B (en) * | 2020-06-03 | 2023-08-18 | 中国移动通信集团浙江有限公司 | Complaint delimiting method and device for 5G slicing user and computing equipment |
| CN114125906B (en) * | 2020-08-10 | 2023-04-25 | 中国移动通信集团浙江有限公司 | Network abnormality diagnosis method, device, computing equipment and computer storage medium |
| CN112188014B (en) * | 2020-10-28 | 2022-04-26 | 中国联合网络通信集团有限公司 | Information processing method and device |
| CN113554485B (en) * | 2021-07-21 | 2023-11-14 | 中国农业银行股份有限公司南海分行 | Lease method and system for sharing charger baby |
| CN113596891B (en) * | 2021-07-28 | 2023-07-14 | 中国联合网络通信集团有限公司 | Fault positioning method, device, server, storage medium and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000067064A (en) * | 1998-08-20 | 2000-03-03 | Hitachi Electronics Service Co Ltd | Interaction recording system |
| CN101459925A (en) * | 2007-12-11 | 2009-06-17 | 中国移动通信集团公司 | Complaint management system and method for telecommunication network |
| CN106162714A (en) * | 2015-04-23 | 2016-11-23 | 中国移动通信集团贵州有限公司 | A kind of calling information processing method and processing device |
| CN107872353A (en) * | 2017-12-27 | 2018-04-03 | 北京奇艺世纪科技有限公司 | A kind of Fault Locating Method and device |
| CN108260150A (en) * | 2016-12-29 | 2018-07-06 | 上海大唐移动通信设备有限公司 | A kind of network communication problem determination processing method and device |
| CN108510284A (en) * | 2017-02-28 | 2018-09-07 | 中国移动通信集团广东有限公司 | A kind of the reason of data service is complained localization method and device |
| CN109996284A (en) * | 2017-12-31 | 2019-07-09 | 中国移动通信集团贵州有限公司 | Mobile communication Trouble call worksheet method, apparatus, equipment and medium |
| CN110493806A (en) * | 2018-05-15 | 2019-11-22 | 中国移动通信集团浙江有限公司 | Mobile network complains source tracing method and device |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110137772A1 (en) * | 2009-12-07 | 2011-06-09 | At&T Mobility Ii Llc | Devices, Systems and Methods for SLA-Based Billing |
| CN103703857B (en) * | 2011-07-14 | 2017-05-31 | 瑞典爱立信有限公司 | Dedicated bearer is reactivated |
| US20140074727A1 (en) * | 2012-09-10 | 2014-03-13 | Lin Miao | Platform for Resolving Complaints with Customers |
| CN104883705B (en) * | 2014-02-27 | 2018-06-26 | 中国移动通信集团上海有限公司 | A kind of the problem of data service is complained localization method and device |
| CN107888397B (en) * | 2016-09-30 | 2020-12-25 | 华为技术有限公司 | Method and device for determining fault type |
| CN106528675A (en) * | 2016-10-31 | 2017-03-22 | 杭州东方通信软件技术有限公司 | Complaint reason positioning method and device |
| CN106910075B (en) * | 2017-01-26 | 2018-07-24 | 合肥工业大学 | The intelligent processing system and method that client mobile communication is complained |
-
2019
- 2019-12-05 CN CN201911236116.4A patent/CN111130855B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000067064A (en) * | 1998-08-20 | 2000-03-03 | Hitachi Electronics Service Co Ltd | Interaction recording system |
| CN101459925A (en) * | 2007-12-11 | 2009-06-17 | 中国移动通信集团公司 | Complaint management system and method for telecommunication network |
| CN106162714A (en) * | 2015-04-23 | 2016-11-23 | 中国移动通信集团贵州有限公司 | A kind of calling information processing method and processing device |
| CN108260150A (en) * | 2016-12-29 | 2018-07-06 | 上海大唐移动通信设备有限公司 | A kind of network communication problem determination processing method and device |
| CN108510284A (en) * | 2017-02-28 | 2018-09-07 | 中国移动通信集团广东有限公司 | A kind of the reason of data service is complained localization method and device |
| CN107872353A (en) * | 2017-12-27 | 2018-04-03 | 北京奇艺世纪科技有限公司 | A kind of Fault Locating Method and device |
| CN109996284A (en) * | 2017-12-31 | 2019-07-09 | 中国移动通信集团贵州有限公司 | Mobile communication Trouble call worksheet method, apparatus, equipment and medium |
| CN110493806A (en) * | 2018-05-15 | 2019-11-22 | 中国移动通信集团浙江有限公司 | Mobile network complains source tracing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111130855A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111130855B (en) | Problem positioning method and device | |
| US9602382B2 (en) | Dynamic reaction to diameter routing failures | |
| CN102893640B (en) | For the method for transmission policy information between "Policy and Charging Rules Function and service node, system and computer-readable medium | |
| US9860390B2 (en) | Methods, systems, and computer readable media for policy event record generation | |
| KR101414921B1 (en) | Managing ip -can subscriber sessions in response to changes related to the subscriber | |
| JP5632977B2 (en) | Temporary restrictions and rollbacks | |
| US20150063130A1 (en) | Customized diameter performance metrics | |
| US20160374008A1 (en) | Service provider certified device policy management | |
| US20120081557A1 (en) | Methods, systems, and computer readable media for user activated policy enhancement | |
| JP6406259B2 (en) | COMMUNICATION DEVICE, CONTROL DEVICE, COMMUNICATION METHOD, CONTROL METHOD, AND PROGRAM | |
| US8897749B1 (en) | Policy decisions based on subscriber spending limits | |
| US20160057291A1 (en) | Enabling monitoring and reporting for dynamic policy enforcement in multi-operator wholesale networks | |
| CN102868988B (en) | Based on the method for processing business of policy and charging control and system in wireless network | |
| US8787382B2 (en) | Per-peer request delivery timeouts | |
| CN110870256B (en) | Method, system and computer readable medium for operating a telecommunication network | |
| JP2014155096A (en) | System and method for dynamically changing communication policy rule | |
| US20120142306A1 (en) | Priority Communications in a Shared Access Telecommunications Network | |
| US9094865B2 (en) | Load balancing for devices within a network | |
| CN110858957B (en) | Information pushing system, method, device, medium and equipment | |
| KR101386521B1 (en) | Method And Apparatus for Managing Fixed Charge Roaming Data | |
| US20210304215A1 (en) | Adaptive m2m billing | |
| CN110890967A (en) | Charging processing method, network element and network system | |
| CN108200606A (en) | A kind of network resource scheduling method, intelligent control center and gateway | |
| US11722717B1 (en) | Systems and methods for network-based adaptive uplink data transfer for large volume data | |
| US9247073B2 (en) | Method of pacing bulk operations based on available system resources |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |