CN115988438A

CN115988438A - Call service data processing method, device, equipment and storage medium

Info

Publication number: CN115988438A
Application number: CN202211608606.4A
Authority: CN
Inventors: 杨朝鹏; 黄荣濂; 严锋雲
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-12-14
Filing date: 2022-12-14
Publication date: 2023-04-18

Abstract

The application provides a call service data processing method, a device, equipment and a storage medium. The method comprises the following steps: obtaining an external data representation XDR of a first core network domain of a first communication system, an XDR of a second core network domain, an XDR of a third core network domain of a second communication system, and an XDR of a wireless domain. The voice service includes a call service. And generating an XDR call record of at least one call service of at least one terminal device according to the XDR of each domain. And determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and the problem tree matrix corresponding to the call service of the target service type. The method improves the efficiency and accuracy of identifying and processing the call service fault.

Description

Call service data processing method, device, equipment and storage medium

Technical Field

The present application relates to communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing call service data.

Background

With the development of the fifth Generation Mobile Communication technology (5 g) network service, in order to obtain higher quality Voice call and video call experience, the call service is gradually changed from a Voice over Long-Term Evolution (VoLTE) mode to a Voice over New air (Voice New Radio, voNR) mode. However, since the coverage of the VoNR is not comprehensive, in order to ensure the continuity of the call service, the call service is currently switched from the VoNR to the VoLTE through an Evolved Packet System voice Fallback (EPSFB). In this scenario, the call service involves two communication systems, 5G and 4G, which may each include a core network domain and a wireless domain.

At present, the identification and processing of the call service fault are carried out manually on each domain, and the problems of low efficiency and accuracy of identification and processing exist.

Disclosure of Invention

The application provides a call service data processing method, a device, equipment and a storage medium, which are used for solving the problems that the identification and processing of the current call service fault are carried out manually on each domain, and the identification and processing efficiency and accuracy are low.

In a first aspect, the present application provides a method for processing call service data, including:

acquiring an external data representation XDR of a first core network domain of the first communication system, an XDR of a second core network domain, an XDR of a third core network domain of the second communication system, and an XDR of a wireless domain; the first core network domain and the third core network domain are used for providing voice services and/or data services, and the second core network domain is used for providing multimedia services; the wireless domain comprises a wireless domain of a first communication system and/or a wireless domain of a second communication system; the voice service comprises a call service;

generating an XDR call record of at least one call service of at least one terminal device according to the XDR of each domain;

determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and a problem tree matrix corresponding to the call service of the target service type; the problem tree matrix is used for representing the mapping relation among the XDR call records, the fault delimiting network elements, the fault delimiting domains, the fault delimiting results, the problem reasons and the processing suggestions.

In a second aspect, the present application provides a data processing apparatus for a call service, where a first communication system and a second communication system provide a call service in a voice fallback manner, and the apparatus includes:

an obtaining module, configured to obtain an external data representation XDR of a first core network domain of the first communication system, an XDR of a second core network domain, an XDR of a third core network domain of the second communication system, and an XDR of a wireless domain; the first core network domain and the third core network domain are used for providing voice services and/or data services, and the second core network domain is used for providing multimedia services; the wireless domain comprises a wireless domain of a first communication system and/or a wireless domain of a second communication system; the voice service comprises a call service;

a processing module, configured to generate an XDR call record of at least one call service of at least one terminal device according to the XDR of each domain; determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and a problem tree matrix corresponding to the call service of the target service type; the problem tree matrix is used for representing the mapping relation among the XDR call records, the fault delimiting network elements, the fault delimiting domains, the fault delimiting results, the problem reasons and the processing suggestions.

In a third aspect, the present application provides an electronic device, comprising: a processor, a communication interface, and a memory; the processor is respectively in communication connection with the communication interface and the memory;

the memory stores computer-executable instructions;

the communication interface is in communication interaction with external equipment;

the processor executes computer-executable instructions stored by the memory to implement the method as described in the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for implementing the method as set forth in the first aspect when executed by a processor.

By acquiring the XDRs of the terminal device in the multiple domains included in the multiple communication systems, the XDRs corresponding to the terminal device are synthesized, and the XDR call records of the same call service of the same terminal device are acquired, where the XDR call records can represent data of the call service in the multiple domains, and the failure of the call service in the multiple domains can be jointly analyzed by only identifying the XDR call records. And determining the fault information of the call service of the terminal equipment through the synthesized XDR call records and the problem tree matrix with the mapping relation with the synthesized XDR call records, thereby improving the efficiency and the accuracy of identifying and processing the faults of the call service under the condition of realizing the functions of automatically associating and identifying the faults of the call service on the core network domain and the wireless domain of a plurality of communication systems and automatically processing the faults.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic diagram of a communication system architecture of an existing ESPFB scenario;

fig. 2 is a schematic flowchart of a call service data processing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of another call service data processing method according to an embodiment of the present application;

fig. 4 is a schematic flowchart of another call service data processing method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a problem tree matrix corresponding to a target service type of a possible call service according to an embodiment of the present application;

fig. 6 is a schematic diagram of a problem tree matrix corresponding to a target service type of another possible call service provided in the embodiment of the present application;

fig. 7 is a schematic flowchart of a fault definition analysis result of an output call service according to an embodiment of the present application;

fig. 8 is a schematic diagram of a network element dimension fault definition analysis result provided in the embodiment of the present application;

fig. 9 is a schematic diagram of another network element dimension fault definition analysis result provided in the embodiment of the present application;

fig. 10 is a schematic diagram of a result of a dimension fault definition analysis of another network element according to an embodiment of the present application;

fig. 11 is a schematic diagram of a cell dimension fault definition analysis result provided in the embodiment of the present application;

fig. 12 is a schematic diagram of another cell dimension fault definition analysis result provided in the embodiment of the present application;

fig. 13 is a schematic diagram of a further cell dimension fault definition analysis result provided in the embodiment of the present application;

fig. 14 is a schematic flowchart of another fault definition analysis result of an output call service according to an embodiment of the present application;

fig. 15 is a schematic diagram of a result of analyzing a fault definition of a call service of a target terminal according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a call service data processing apparatus according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The method for processing call service data provided by the present application may be applied to the communication system architecture diagram of the ESPFB scenario shown in fig. 1. As shown in fig. 1, the architecture includes: the first core network domain, the second core network domain and the wireless domain of the first communication system, the third core network domain and the wireless domain of the second communication system and the terminal equipment.

The first core network domain of the first communication system and the third core network domain of the second communication system are used for providing voice services and/or data services, and the second core network domain of the first communication system is used for providing multimedia services.

It should be understood that the first communication System and the second communication System shown in fig. 1 may be any network System, for example, may be suitable for Global System for Mobile communication (GSM), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), time Division-Synchronous Code Division Multiple Access (TD-SCDMA), long Term Evolution (Long Term Evolution, LTE), 5G New air interface (New Radio, NR), future 6G, and other network systems.

Illustratively, the network standard of the first Communication system is 5G, and the network standard of the second Communication system is a fourth Generation Mobile Communication technology (4 th Generation Mobile Communication technology, 4G).

The access Network device may be a Base Station (BTS) and/or a Base Station Controller in GSM or CDMA, a Base Station (NodeB, NB) and/or a Radio Network Controller (Radio Network Controller, RNC) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, or a relay Station or an access point, or a Base Station (gNB) in a 5G Network, and the like, which is not limited herein.

The terminal device may be a device that provides voice and/or other traffic data connectivity to a user, a handheld device with wireless connection capability, or other processing device connected to a wireless modem. A terminal device may communicate with one or more core Network devices via a Radio Access Network (RAN), and a wireless terminal may be a mobile terminal, such as a mobile phone (or called "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket, hand-held, computer-included or vehicle-mounted mobile device, which exchanges languages and/or data with the RAN. For another example, the Wireless terminal may be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), and the like. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Device or User Equipment (User Equipment), which are not limited herein. Optionally, the terminal device may also be a smart watch, a tablet computer, or the like.

The present application will be described below by taking an example in which the first communication system is an NR system and the second communication system is an LTE system.

When the first communication system is an NR system, the first core network domain is a 5G core network (5gcore, 5gc) domain, and the 5GC domain may include network elements of the NR system core network, such as Access and Mobility Management Function (AMF) network elements, session Management Function (SMF) network elements, policy Control Function (PCF) network elements, unified Data Management Function (UDM) network elements, and the like.

The second core network domain may be, for example, an IP Multimedia System (IMS) domain. The second core network domain may include network elements of an IMS core network, for example, a Proxy Call Session Control Function (P-CSCF) network element, an inquiry Call Session Control Function (I-CSCF) network element, a serving Call Session Control Function (SIP-CSCF, S-CSCF), a Home Subscriber Server (HSS), and the like.

When the second communication system is an LTE system, the third Core network domain is an Evolved Packet Core (EPC) domain, and the EPC domain may include network elements of the LTE system Core network, for example, a Mobility Management Entity (MME) network element, an HSS, and the like.

The wireless domain is a part of the first communication system and/or the second communication system which is connected with the user terminal equipment in a wireless mode. For example, the information may be provided by an access network device in a first communication system, and/or provided by an access network device in a second communication system, where the access network device is a gNB when the first communication system is an NR system, and the access network device is an eNB when the second communication system is an LTE system. The wireless domain described later in this application may be determined as the wireless domain of the first communication system, or the wireless domain of the second communication system, or the wireless domain of the first communication system and the wireless domain of the second communication system according to actual conditions.

In the present application, the service coverage on the access network device (e.g. base station) of the first communication system is not complete, for example, some access network devices temporarily do not cover the call service, so that the call service cannot be provided for the terminal device within the wireless signal coverage area. The access network device of the second communication system overlays the call service, i.e. is able to provide the call service.

At present, in this scenario, when a terminal device is simultaneously located in a wireless signal coverage area of an access network device of a first communication system that does not cover a call service and in a wireless signal coverage area of an access network device of a second communication system, and the terminal device is currently accessed in the first communication system, if the terminal device needs to use the call service, the call service may be dropped back to the second communication system in an ESPFB manner, so as to perform the call service through the access network device and a core network of the second communication system, thereby ensuring the continuity of the call service. The call service may be, for example, a voice announcement, an incoming voice call, an outgoing voice call, a video call, etc.

Therefore, the call service in the ESPFB mode may involve a plurality of domains, such as the first core network domain, the second core network domain, and the wireless domain of the first communication system, the third core network domain, and the wireless domain of the second communication system. Currently, the identification and processing of call service failures are performed by manually analyzing, judging, and processing call service data in each domain. Identifying and handling call service failures in the manual manner described above presents the following problems.

Problem 1: manual identification and handling of call traffic failures is inefficient. When the call traffic is large, the manual work cannot identify and process the call traffic fault in time.

Problem 2: the accuracy rate of manually identifying and processing the call service fault is low. If the experience of the staff is insufficient or the staff needs to handle a large number of call service failures in a short time, the accuracy of identifying and handling the call service failures may be reduced.

Problem 3: it is difficult for a person to quickly associate call traffic data in a plurality of domains included in a plurality of communication systems for fault identification and handling.

In view of this, the present application provides a method for processing call service Data, which obtains External Data Representation (XDR) of a terminal device in multiple domains included in multiple communication systems, synthesizes the XDRs corresponding to the terminal device, and obtains XDR call records of the same call service of the same terminal device, where the XDR call records can represent Data of the call service in the multiple domains, and can jointly analyze faults of the call service in the multiple domains only by identifying the XDR call records. And determining the fault information of the call service of the terminal equipment through the synthesized XDR call records and the problem tree matrix with the mapping relation with the synthesized XDR call records, thereby improving the efficiency and the accuracy of identifying and processing the faults of the call service under the condition of realizing the functions of automatically associating and identifying the faults of the call service on the core network domain and the wireless domain of a plurality of communication systems and automatically processing the faults.

The execution main body of the application can be a call service identification processing system, and the call service identification processing system can be a driving program, program code software, or a medium storing related execution codes, such as a U disk; alternatively, the call service identification processing system may also be an entity device integrated or installed with relevant executable codes, for example, an electronic device such as a chip, a micro controller Unit (MCU for short), a computer, or a computer.

The functions of the call service identification processing system may be integrated on a physical device; or after being constructed by other devices, the call service identification processing system can be stored in a storage medium, and the entity device realizes the functions of the call service identification processing system by operating the relevant execution codes in the storage medium; the call service recognition and processing function can be provided for the entity device by being deployed on the cloud platform.

In the following, taking the function of the call service identification processing system integrated on the target device as an example, the technical solution of the present application and how to solve the above technical problem in the technical solution of the present application will be described in detail with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a schematic flowchart of a call service data processing method according to an embodiment of the present application.

As shown in fig. 2, the method may include:

s201, obtaining an XDR (external data representation) of a first core network domain of a first communication system, an XDR of a second core network domain, an XDR of a third core network domain of a second communication system and an XDR of a wireless domain; .

Wherein the first core network domain and the third core network domain are used for providing a voice service and/or a data service, and the second core network domain is used for providing a multimedia service. The voice service includes a call service, which may be, for example, an audio call service, a video call service, etc.; the data service mainly adopts data transmission and information interaction and is used for accessing remote information, interactive entertainment, electronic commerce and the like; the multimedia service is used for transmitting multimedia data such as pictures, audio, video, menus, expressions, positions, actions, augmented Reality (AR)/Virtual Reality (VR), and the like. The XDR data may include the identifier of the terminal device, the call service data of the terminal device, and other contents.

Illustratively, under the 5GC domain, the XDR includes the fields shown in Table 1 below:

TABLE 1

Illustratively, under the IMS domain, the XDR includes fields as shown in table 2 below:

TABLE 2

/>

Illustratively, under the EPC domain, the XDR includes the fields shown in table 3 below:

TABLE 3

Illustratively, under a 5G wireless domain, the XDR includes fields as shown in table 4 below:

TABLE 4

/>

Illustratively, under a 5G wireless domain, the XDR includes fields as shown in table 5 below:

TABLE 5

/>

/>

In one possible implementation, the XDR in each domain may be obtained through a DPI interface of a network element included in each domain. For example, in the 5GC domain, the DPI interfaces between network elements may include, for example, N1, N2, N4, N7, and other interfaces; in the IMS domain, DPI interfaces between network elements may include, for example, SIP, diameter, gxRx, nc, sv interfaces, etc.; in the EPC domain, the DPI interfaces between network elements may include, for example, S1MEE, S6a interfaces, and the like; the MR interface of the corresponding communication system may be included in the wireless domain. The XDR in each domain acquired through the DPI interface may be acquired through Kafka, enterprise Service Bus (ESB), file Transfer Protocol (FTP), and the like, for example.

In another possible implementation manner, the network elements included in each domain actively report their XDRs.

S202, according to the XDR of each domain, generating an XDR call record of at least one call service of at least one terminal device.

According to the XDR of each domain, the time of the terminal equipment for carrying out the call service and the data of the call service are obtained, and whether the XDR of each domain belongs to the same call service of the same terminal equipment or not is determined according to the identifier of the terminal equipment and the time of the call service. And synthesizing the XDRs of the same call service belonging to the same terminal equipment into an XDR call record of the call service of the terminal equipment. The XDR call record includes data contents included in the XDR of the terminal device in each domain. When the XDR is used to synthesize an XDR call record, duplicate content in the XDR of each domain may be deleted, or only part of the XDR of each domain may be selected for synthesis.

In one possible implementation manner, the range of the XDRs of each domain to be synthesized may be selected according to the actual requirement, that is, a portion of the XDRs corresponding to the actual requirement is selected from the XDRs of each domain for synthesis.

In another possible implementation, all currently obtained XDRs for each domain are synthesized as described above.

S203, determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and the problem tree matrix corresponding to the call service of the target service type.

The problem tree matrix is used for representing mapping relations among XDR call records, fault delimitation network elements, fault delimitation domains, fault delimitation results, problem reasons and processing suggestions. The problem tree matrix can be obtained after statistical analysis according to historical XDR data, or can be obtained after model training is carried out by utilizing the historical XDR data and historical calling service fault recognition and processing results, wherein the historical calling service fault recognition and processing results are related to the historical XDR data. The fault delimitation domain can be divided according to actual conditions, for example, the fault delimitation domain can be divided into the following fault delimitation domains: an unknown domain, an EPC domain, an IMS domain, a CS domain, a wireless domain, a digital domain, a user domain, a terminal domain, a transmission domain, a content source domain, an account opening data domain, a 5GC domain and the like. The application does not limit the division of the fault definition domain.

The problem tree matrix provided by the embodiment of the application can be as shown in the following table 6:

TABLE 6

/>

/>

The service condition is obtained when obtaining the XDR of each domain, and the service type, the call type, the connection state, and the service result corresponding to the service condition all include corresponding values in the XDR of each domain. The service type may be, for example, registration, calling, connection, etc. The call type is used to indicate the type of the call service, and may be, for example, voNR, ESPFB, voLTE, or the like. The connection status is used to indicate whether the used network of the call service was successfully connected, which may be, for example, successful or failed. The service result is used to indicate the result of the call service, which may be, for example, successful connection, failed connection, dropped call, etc. In each domain, each domain includes a plurality of fields, the fields are used for indicating contents related to a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem cause, a processing proposal and the like in the XDR call record, and the fields may be determined according to actual requirements, which is not limited by the application.

The problem tree matrix may be different for call services of different service types. And determining a problem tree matrix for processing the XDR call record according to the target service type. In addition, the problem tree matrix may be the same or different for different call types in the present application. When the problem tree matrices are not the same for different call types, the problem tree matrix handling the XDR call records may be further determined according to the call type.

A possible implementation mode is that according to values corresponding to all fields in an XDR call record and a mapping relation between a problem tree matrix and the values of the fields, a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem reason and a processing suggestion are determined.

According to the corresponding values of some fields in the XDR call record and the mapping relation between the problem tree matrix and the corresponding values of the fields, the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem reason and the processing suggestion are determined. The part of the field may be selected according to actual requirements, which is not limited in the present application.

The method for processing the call service data obtains the XDR of the terminal equipment using the call service in each domain, synthesizes the XDR in each domain according to the terminal equipment and the call service, and obtains the XDR call record used for indicating each call service of each terminal equipment, wherein the XDR call record can represent the data of the call service in a plurality of domains, and the fault of the call service in the plurality of domains can be jointly analyzed only by identifying the XDR call record. And then according to the XDR call record and the mapping relation of the problem tree matrix corresponding to the call service of the target service type, obtaining the fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type, thereby improving the efficiency and the accuracy of identifying and processing the fault of the call service under the conditions of realizing the functions of automatically associating and identifying the faults of the call service on the core network domain and the wireless domain of a plurality of communication systems and automatically processing the faults.

Next, how to generate an XDR call record of at least one call service of at least one terminal device according to the XDRs of each domain in step S202 will be described in detail.

Since the acquisition modes and acquisition devices of the XDRs of the respective domains may be different, even if XDRs generated at the same time are acquired in different domains, the acquisition times of the XDRs may not be synchronized. Therefore, when the XDRs of each domain are collected, there may be a problem that the collection time is not synchronous, so that when an XDR call record is synthesized, the XDRs of each domain synthesizing the XDR call record are missing due to the existing collection time difference, thereby affecting the accuracy of judging the fault of the call service data.

Fig. 3 is a flowchart illustrating another call service data processing method according to an embodiment of the present application. As shown in fig. 3, step S202 may include:

s301, asynchronously importing each domain XDR into the stack of each domain according to the time of receiving each domain XDR.

The stacks of the domains are used to store XDRs obtained from the domains, and the XDRs stored in the stacks of the domains are used for subsequent synthesis of XDR call records. The stack stores the XDRs in the corresponding domain according to their acquisition time order. The stack of each domain may continue to store XDRs in that domain without deleting any stored XDRs; it is also possible that a holding time period for storing the XDR is set, and when the XDR is stored in the stack for a time exceeding the holding time period, the XDR is deleted from the stack.

The XDR of each domain is stored in an asynchronous import stack mode, so that even if time difference exists in the time for collecting the XDR, the corresponding XDR of the XDR call record to be synthesized can be stored in the stack, and the condition that partial XDR is lost in the synthesis process due to the time difference for collecting the XDR is prevented.

S302, according to the XDR holding maximum time, extracting the XDR of the same call service belonging to the same terminal equipment from the stack of each domain, and generating the XDR call record of the call service of the terminal equipment by using the extracted XDR.

Wherein the same call service of the same terminal device is determined according to the time included in the XDR and the identifier of the terminal device. The time included in the XDR is the time corresponding to the call service of the terminal device, and may be, for example, the start time of the call service. The Identity of the terminal equipment included in the XDR is used to uniquely indicate the terminal equipment, and may be, for example, an International Mobile Subscriber Identity (ims), and/or a Mobile station International ISDN number (MSISDN), which is specifically related to the manner in which the terminal equipment is uniquely identified in the first communication system and the second communication system. The XDRs having the same terminal device identifier in the preset time period can be determined as the XDRs of the same call service of the same terminal device by setting the preset time period. The preset time period is used for limiting the time included in the XDR within the same time period interval, and the preset time period may be determined according to actual requirements, which is not limited in the present application.

One possible implementation is to consider XDRs of the same terminal identifier as XDRs generated by a call service of the same terminal device. After confirming the XDR of the same terminal equipment, judging the XDR time of the same terminal equipment, and if the XDR time with different times belongs to the same preset time period, judging the XDRs as the XDR of the same call service of the same terminal equipment.

Another possible implementation manner is to divide all XDRs in the stack according to a preset time period, and then divide all XDRs in each preset time period according to the terminal identifier, so as to determine the XDRs of the same call service of the same terminal device.

The XDR maximum holding duration is a maximum duration that can be held in a stack without being deleted when an XDR is stored in a stack of each domain and has not been used for synthesizing an XDR call record, and when an XDR is not used for synthesizing an XDR call record and the time stored in the stack exceeds the XDR maximum holding duration, the XDR is deleted (or popped) from the stack of the domain.

In one possible implementation, the XDR maximum hold time is constant.

That is, the storage time of the XDRs stored in the stacks of the domains is smaller than the XDR maximum holding time. And according to the judging mode of the same call service of the same terminal equipment, extracting all XDRs of the same call service belonging to the same terminal equipment in each domain, deleting the same data in the XDRs, and merging the rest XDR data so as to obtain the XDR call record of the one call service of the terminal equipment.

In another possible implementation, the XDR maximum holding time varies according to the matching schedules of multiple domains.

S3021, for the same terminal device, if the XDR of the terminal device in the first core network domain and the XDR of the second core network domain are matched from the stack of the first core network domain and the stack of the second core network domain, detecting whether the XDR of the terminal device exists in the stack of the third core network domain according to the first maximum duration of retention.

Wherein, the XDR of the first core network domain and the XDR of the second core network domain determine whether the XDR of the first core network domain and the XDR of the second core network domain belong to the XDR of the same call service of the same terminal device within the maximum holding time according to the matching mode in the previous implementation mode, if not, the characteristic cannot be matched, and currently, no XDR capable of being matched exists in each domain stack, so that it is necessary to continuously wait for the subsequent acquisition of XDRs to be stored in each domain stack to try matching again, and if the XDR in the stack cannot be matched after reaching the first holding maximum time, the characteristic that no other XDR capable of being matched exists in the XDR, so that the XDR is popped out from the corresponding stack, and the storage space of the stack is saved to store the newly acquired XDR; if the XDR belongs to the first core network domain, the characteristics can be matched, and the XDR of the terminal equipment exists in the stack of the third core network domain.

S3022, when the XDR of the first core network domain and the XDR of the second core network domain can be matched, if it is detected that the XDR of the terminal device exists in the stack of the third core network domain, it is indicated that the XDR that can be matched also exists in the stack of the third core network domain, and the XDR of the third core network domain is matched with the result of matching the XDR of the first core network domain and the XDR of the second core network domain. At this time, only the XDRs in the stack of the wireless domain remain without matching, and at this time, the total number of the remaining unmatched XDRs is small, and the matching time is short, so that it is possible to detect whether the XDR of the terminal device exists in the stack of the wireless domain according to a second maximum holding duration that is smaller than the first maximum holding duration, and further match the XDRs in the stack of the wireless domain within the second maximum holding duration.

S3023, if the XDR of the terminal device exists in the stack of the wireless domain, merging the XDR of the terminal device in the first core network domain, the XDR of the second core network domain, the XDR of the third core network domain, and the XDR of the wireless domain, to obtain the XDR of the call service of the terminal device. The merging method may be, for example, merging non-overlapping contents included in the XDRs in the domain to obtain the XDR of the call service of the terminal device; or combining the non-overlapping contents included in the XDRs in the domain, and deleting part of the contents according to actual requirements to obtain the XDR of the call service of the terminal device.

S3024, if the XDR of the terminal device does not exist in the stack of the wireless domain, and/or the XDR of the terminal device does not exist in the stack of the third core network domain, merging the other matched XDRs of the terminal device to obtain the XDR of the call service of the terminal device. For example, if the XDR of the terminal device does not exist in the stack of the wireless domain but the XDR of the terminal device exists in the stack of the third core network domain, the XDR of the first core network domain, the XDR of the second core network domain, and the XDR of the third core network domain are merged; if the XDR of the terminal device does not exist in the stack of the wireless domain and the XDR of the terminal device does not exist in the stack of the third core network domain, merging the XDR of the first core network domain and the XDR of the second core network domain; and if the XDR of the terminal device exists in the stack of the wireless domain and the XDR of the terminal device does not exist in the stack of the third core network domain, merging the XDR of the first core network domain, the XDR of the second core network domain and the XDR of the wireless domain.

According to the method provided by the embodiment of the application, even if time difference exists in the time for collecting the XDR, the stack can store the corresponding XDR to be synthesized in the XDR call record, and the problem that part of the XDR is lost in the synthesis process due to the time difference for collecting the XDR is solved. In addition, by judging whether the collected XDR of each domain belongs to the same calling service of the same terminal equipment or not, the XDR of each domain is merged according to the same calling service of the same terminal equipment to obtain the XDR calling record of the calling service of the terminal equipment, so that repeated content in XDR data of each domain is reduced, the same calling service of the same terminal equipment on a plurality of domains is only expressed in the mode of one XDR, the subsequent fault identification and processing efficiency of the calling service data of the terminal equipment is improved, and the function of analyzing faults of the calling service by combining a plurality of domains is realized.

In the following, how to obtain the fault definition analysis result of the call service of the target service type according to the problem tree matrix is explained in detail.

The problem tree matrix shown in step S203 includes a mapping relationship among a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain, a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem cause, and a processing suggestion in the XDR call record.

And according to at least two target fields in a first target field of a first core network domain, a second target field of a second core network domain and a third target field of a third core network domain in the XDR call record, a mapping relation exists between the at least two target fields and at least one of a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem reason and a processing proposal. For example, the result of at least one of the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem cause, and the processing suggestion may be determined through the first target field of the first core network domain, the second target field of the second core network domain, and the mapping relationship; or determining the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem reason and the result of the processing suggestion through the three target fields and the mapping relation.

Under this implementation manner, fig. 4 is a schematic flowchart of another call service data processing method provided in this embodiment of the present application. As shown in fig. 4, step S203 may include:

s401, aiming at each XDR call record of each terminal device, according to a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain and a problem tree matrix corresponding to a target service type of a call service in the XDR call record, determining a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem reason and a processing suggestion corresponding to the call record.

Firstly, a corresponding problem tree matrix is determined according to the target service type of the call service. And filling corresponding values into the content included in each XDR call record of each terminal device according to a first target field of a first core network domain, a second target field of a second core network domain and a third target field of a third core network domain included in the problem tree matrix. According to the first target field of the first core network domain, the second target field of the second core network domain and the corresponding value of the third target field of the third core network domain, the first target field of the first core network domain, the second target field of the second core network domain, the third target field of the third core network domain, the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem reason and the processing suggestion result are determined.

Illustratively, when the service type is "registration" and the call type is "VoNR/EPSFB", a problem tree matrix corresponding to a target service type of a possible call service is shown in fig. 5. For specific contents of the first target field of the first core network domain, the second target field of the second core network domain, the third target field of the third core network domain, the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem cause, and the processing suggestion, reference may be made to fig. 5, which is not repeated here.

Illustratively, when the service type is "caller" and the call type is "EPSFB", a problem tree matrix corresponding to a target service type of a possible call service is shown in fig. 6.

It should be understood that the mapping relationships between the first target field and the second target field and the fault delimiting network element, the fault delimiting field, the fault delimiting result, the problem cause, and the processing proposal may be preset according to actual needs, which is not limited in the present application.

When the method is actually used, the number of fields included in the first target field, the second target field, and the third target field, and which fields are specifically included in the first target field, the second target field, and the third target field may be set according to actual requirements, and fields may be added or deleted according to actual requirements, which is not limited in the present application.

S402, obtaining the fault definition analysis result of the XDR call record aiming at the call service of the target service type according to the fault definition network element, the fault definition domain, the fault definition result, the problem reason and the processing suggestion corresponding to the call record.

Implementation mode 1: and directly taking the fault delimitation network element, the fault delimitation domain, the fault delimitation result, the problem reason and the processing suggestion corresponding to the call record as the fault delimitation analysis result of the XDR call record aiming at the call service of the target service type no matter whether the delimitation domain result is a wireless domain or not.

Implementation mode 2: and determining a fault delimitation analysis result of the call service of the target service type according to whether the delimitation domain result is a wireless domain.

If the delimited domain corresponding to the call record is a non-wireless domain, the fault delimited network element, the fault delimited domain, the fault delimited result, the problem reason and the processing suggestion corresponding to the call record are used as the fault delimited analysis result of the XDR call record aiming at the call service of the target service type. Namely, the fault definition analysis result comprises a fault definition network element, a fault definition domain, a fault definition result, a problem reason and a processing suggestion, and each result obtains a corresponding value according to the first target field, the second target field and the third target field.

In another possible implementation manner, if the delimited domain corresponding to the call record is a wireless domain, the specific reason of the XDR call record in the wireless domain is further analyzed, and the specific reason in the wireless domain is used as a result of analyzing the fault delimited of the XDR call record for the call service of the target service type. Therefore, a more detailed fault definition analysis result is provided for the fault of the call service corresponding to the XDR call record. The fault definition analysis result may only include the specific reason in the aspect of radio, and may also include the contents of the fault definition network element, the fault definition domain, the fault definition result, the problem reason, the processing suggestion, and the like, which are output by the problem tree matrix.

S4021, obtaining the reason for the problem in the wireless domain corresponding to the XDR call record according to the fourth target field in the wireless domain in the XDR call record and the mapping relationship among the preset field, the fourth target field and the reason for the problem in the wireless domain. Wherein the fourth target field comprises a preset field.

The fourth target field may be a field corresponding to data capable of characterizing actual situations of call services in the wireless domain, and may include, for example, fields such as Reference Signal Receiving Power (RSRP) of a cell covered by the wireless domain where the terminal device is located, RSRP of cells adjacent to the cell, a distance from the terminal device to the base station, and an average received interference Power of the base station. The preset field may be an INTRAT field and an INTNCRAT field included in a Radio Access Technology (RAT).

And determining a mapping relation between a fourth target field of a wireless domain and a problem reason of the wireless domain in the XDR call record according to the preset field, and then determining the problem reason of the wireless domain according to the mapping relation and the fourth target field. The cause of the problem in the wireless domain may be set according to actual requirements, and may include at least one of the following: coverage holes, pseudo weak coverage, fast fading, over coverage, overlay coverage, uplink interference, modulo three interference, etc.

Optionally, when the INTRAT field and the INTNCRAT field in the XDR call record have no value, the cause of the problem in the wireless domain is determined only by a mapping relationship between the content of the fourth target field of the wireless domain, except for the preset field, and the cause of the problem in the wireless domain. For example, the mapping relationship between the fourth target field and the cause of the radio domain problem may be as shown in table 7 below.

TABLE 7

The reason for the wireless domain problem and the mapping relationship between the fourth target field and the reason for the wireless domain problem may be determined according to actual requirements, table 2 in the present application only provides a reference example, and the reason for the wireless domain problem and the mapping relationship between the fourth target field and the reason for the wireless domain problem are not limited to this.

Optionally, when the INTRAT field and the INTNCRAT field in the XDR call record have values, the cause of the problem in the wireless domain may also be determined by a mapping relationship between a fourth target field, a preset field, and the cause of the problem in the wireless domain. For example, the mapping relationship between the fourth target field of the radio domain, the preset field and the cause of the radio domain problem may be as shown in table 8 below.

TABLE 8

/>

/>

The reason for the wireless domain problem, and the mapping relationship between the fourth target field, the preset field, and the reason for the wireless domain problem may be determined according to actual requirements, table 3 in the present application merely provides a reference example, and the reason for the wireless domain problem, and the fourth target field, the preset field, and the reason for the wireless domain problem in the wireless domain are not limited to this.

S4022, using the radio domain problem reason corresponding to the XDR call record, and the fault delimitation network element, the fault delimitation domain, the fault delimitation result, the problem reason and the processing suggestion corresponding to the call record as the fault delimitation analysis result of the XDR call record for the call service of the target service type.

After step S402 is completed, the method may further include storing the result of the fault-definition analysis of the XDR call record for the call service of the target service type.

Optionally, the XDR call record may further include a field for storing a Result of analyzing the fault definition of the call service of the target service type, for example, the field may be an LTE _ Radio _ Result field. In this implementation manner, the method may further include filling the fault definition analysis result of the call service of the target service type into the field for storing the fault definition analysis result of the call service of the target service type, so as to be conveniently matched with the call service of the terminal device corresponding to the XDR call record, thereby implementing a function of feeding back the fault definition analysis result to the fault request of the call service of the corresponding terminal device.

Optionally, the fault definition analysis result is stored in a preset position except for the XDR call record, and when a fault request of a call service of the corresponding terminal device is received, the fault definition analysis result is matched.

According to the method provided by the embodiment of the application, the fault definition analysis result of the call service of the target service type is determined through the mapping relation among the corresponding target fields in the first core network domain, the second core network domain and the third core network domain in the XDR call record, the fault definition network element, the fault definition domain, the fault definition result, the problem reason and the processing suggestion. In addition, when the fault definition domain is a wireless domain, the problem cause of the wireless domain included in the wireless domain can be further determined, so that a more accurate fault definition analysis result is obtained.

After the fault definition analysis result of the call service of the target service type is obtained, the call service data processing method further comprises the step of outputting the fault definition analysis result of the call service aiming at the target service type.

The implementation mode A is as follows: and outputting a fault delimitation analysis result of the call service according to the target service type.

Fig. 7 is a schematic flowchart of a fault definition analysis result of an output call service according to an embodiment of the present application. As shown in fig. 7, the method may include:

s701, receiving a fault delimitation analysis request aiming at the call service of the target service type.

The fault definition analysis request is used for obtaining a fault definition analysis result of the call service of the target service type. The target service type may be, for example, the aforementioned registration, calling, connection, and the like, and may further include call service fall-back condition, call service delay, call drop indicator, and the like. The fault definition analysis request for the call service of the target service type may be reported by a terminal device of a communication system operator.

S702, acquiring a fault definition analysis result of the call service aiming at the target service type according to the fault definition analysis result of each XDR call record aiming at the target service type of each terminal device.

And acquiring a fault definition analysis result aiming at the call service of the target service type by acquiring XDR call records of the call services of all the terminal equipment belonging to the target service type within preset time. And analyzing the fault definition analysis result from multiple dimensions according to the fault definition analysis result of the call service aiming at the target service type, so as to obtain the fault definition analysis result of the call service aiming at the target service type under multiple dimensions. The multiple dimensions may include, for example: area dimension, network element dimension, cell dimension, terminal type dimension, and the like.

The region dimension limits the geographic positions of the call services of all the terminal devices belonging to the target service type within a preset time; the network element dimension limits the network elements used by the call services of all the terminal equipment belonging to the target service type within the preset time; the cell dimension limits the cell in which the call services of all the terminal devices belonging to the target service type are located within the preset time; the terminal type dimension belongs to the category of the terminal device corresponding to the target service type within a preset time.

A possible implementation manner may be to generate a fault definition analysis result for the call service of the target service type according to the fault definition analysis result for the call service of the target service type recorded by each XDR call of all the terminal devices, that is, without further division from the above dimensions.

Another possible implementation manner may further obtain, according to any one of the dimensions, a fault definition analysis result of each XDR call record of all terminal devices for the call service of the target service type in the dimension, and generate and output a fault definition analysis result of the call service of the target service type in the dimension.

Under this implementation manner, fig. 8 is a schematic diagram of a network element dimension fault definition analysis result provided in the embodiment of the present application. The fault definition analysis item is SIP first-break ratio analysis. Wherein, the SIP first-break ratio is the ratio of different values in the name field of the SIP first-break message in table 6 above.

Fig. 9 is a schematic diagram of another network element dimension fault definition analysis result provided in the embodiment of the present application. The fault definition analysis item is definition domain proportion analysis. Wherein the bounding volume is a proportion of the different outcomes in the fault bounding volume in table 6 above.

Fig. 10 is a schematic diagram of a further network element dimension fault definition analysis result provided in the embodiment of the present application. The fault definition analysis item is definition result proportion analysis. Wherein, the delimiting result is the proportion of different results in the fault delimiting result in table 6 above.

Fig. 11 is a schematic diagram of a cell dimension fault definition analysis result provided in an embodiment of the present application. The fault definition analysis item is SIP first-break ratio analysis. Wherein, the SIP first-break ratio is the ratio of different values in the name field of the SIP first-break message in table 6 above.

Fig. 12 is a schematic diagram of another cell dimension fault definition analysis result provided in the embodiment of the present application. The fault definition analysis item is definition domain proportion analysis. Wherein the bounding volume is a proportion of the different outcomes in the fault bounding volume in table 6 above.

Fig. 13 is a schematic diagram of a further cell dimension fault definition analysis result provided in the embodiment of the present application. The fault definition analysis item is definition result proportion analysis. Wherein the delimiting result is a ratio of different results in the fault delimiting result in table 6 above.

And S703, outputting a fault delimitation analysis result aiming at the call service of the target service type.

For example, the fault delimitation analysis result of the call service of the target terminal can be output to the terminal device of the worker in any reminding mode such as an application program, a short message, an applet and the like.

The implementation mode B is as follows: and outputting a fault definition analysis result of the call service according to the target terminal.

Fig. 14 is a schematic flow chart of another fault definition analysis result of an output call service according to the embodiment of the present application. As shown in fig. 7, the method may include:

s801, receiving a fault delimitation analysis request aiming at the call service of the target terminal.

The fault definition analysis request is used to obtain a fault definition analysis result of the call service of the target terminal, for example, the fault definition analysis request may be a fault definition analysis request of a call service of the target terminal, or may be a fault definition analysis request of a call service of the target terminal for multiple times within a certain time period. The fault definition analysis request for the call service of the target terminal may be reported by the target terminal, or may be a fault definition analysis request including the target terminal identifier and the call service identifier, which is reported by other terminal devices.

S802, extracting fault delimitation analysis results of each XDR call record of the target terminal aiming at the call service of each service type, and obtaining the fault delimitation analysis results of the call service of the target terminal.

And extracting each XDR call record of the target terminal according to the target terminal identifier and the call service identifier, acquiring a fault definition analysis result aiming at the call service of each service type according to each XDR call record of the target terminal, and determining the fault definition analysis result of the call service of the target terminal to be selected according to the service type corresponding to the fault definition analysis request.

And S803, outputting the fault delimitation analysis result of the call service of the target terminal.

For example, the fault definition analysis result of the call service of the target terminal may be output to the target terminal device or the terminal device reporting the fault definition analysis request in the form of an application program, a short message, an applet, or the like.

Exemplarily, fig. 15 is a schematic diagram of a result of analyzing a fault definition of a call service of a target terminal according to an embodiment of the present application. As shown in fig. 15, the result of analyzing the fault definition of the call service of the target terminal includes: delimitation network element, delimitation domain, delimitation department, delimitation result, problem reason and processing suggestion. The delimiting network element is the fault delimiting network element in fig. 5, the delimiting domain is the fault delimiting domain in fig. 5, the delimiting result, the cause of the problem and the processing suggestion can be as shown in fig. 5, and the delimiting department can be determined according to actual conditions or according to an actual technical department having a mapping relationship with the delimiting network element.

According to the method for outputting the fault definition analysis result of the call service, the fault definition analysis result of the terminal equipment used by the user is analyzed, so that the user can receive the fault definition analysis result corresponding to the fault definition analysis request more quickly after the user provides the fault definition analysis request. In addition, statistical data related to the fault delimitation analysis result is pushed to terminal equipment of workers, so that the fault condition of the call service under the current multiple communication systems is displayed more intuitively, and the fault of the call service is found in advance conveniently.

It should be understood that, in the embodiment of the present application, the call service data processing method is described by taking 5G and 4G communication systems as examples. However, when the method is applied to other communication systems, the content in the method can be adaptively adjusted according to the characteristics and actual conditions of the communication system.

Fig. 16 is a schematic structural diagram of a call service data processing apparatus according to an embodiment of the present application. As shown in fig. 16, the call service data processing apparatus includes: the device comprises an acquisition module 11 and a processing module 12. In one possible embodiment, the method further comprises: and a receiving module 13.

An obtaining module 11, configured to obtain an external data representation XDR of a first core network domain of the first communication system, an XDR of a second core network domain, an XDR of a third core network domain of the second communication system, and an XDR of a wireless domain. The first core network domain and the third core network domain are used for providing voice services and/or data services, and the second core network domain is used for providing multimedia services. The wireless domain includes a wireless domain of a first communication system and a wireless domain of a second communication system. The voice service includes a call service.

A processing module 12, configured to generate an XDR call record of at least one call service of at least one terminal device according to the XDRs of each domain. Determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and a problem tree matrix corresponding to the call service of the target service type; the problem tree matrix is used for representing the mapping relation among XDR call records, fault delimiting network elements, fault delimiting domains, fault delimiting results, problem reasons and processing suggestions.

In one possible implementation, the processing module 12 is specifically configured to asynchronously import each domain XDR into the stack of each domain according to the time at which each domain XDR is received. And according to the maximum duration of the XDR maintenance, extracting the XDR of the same call service belonging to the same terminal equipment from the stack of each domain, and generating an XDR call record of the call service of the terminal equipment by using the extracted XDR.

In this implementation, the processing module 12 is specifically configured to, for the same terminal device, if the XDR of the terminal device in the first core network domain and the XDR of the second core network domain are matched from the stack of the first core network domain and the stack of the second core network domain, detect whether the XDR of the terminal device exists in the stack of the third core network domain according to the first maximum duration of retention. And if the XDR of the terminal equipment exists in the stack of the third core network domain, detecting whether the XDR of the terminal equipment exists in the stack of the wireless domain according to a second maximum holding duration, wherein the second maximum holding duration is smaller than the first maximum holding duration. If the XDR of the terminal equipment exists in the stack of the wireless domain, the XDR of the terminal equipment in the first core network domain, the XDR of the second core network domain, the XDR of the third core network domain and the XDR of the wireless domain are merged to obtain the XDR of the call service of the terminal equipment. If the XDR of the terminal device does not exist in the stack of the wireless domain, and/or the XDR of the terminal device does not exist in the stack of the third core network domain, merging the other matched XDRs of the terminal device to obtain the XDR of the call service of the terminal device.

In any of the above implementation manners, the problem tree matrix includes a mapping relationship among a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain, a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem cause, and a processing suggestion in the XDR call record. The processing module 12 is specifically configured to determine, for each XDR call record of each terminal device, a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem cause, and a processing suggestion that correspond to the call record according to a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain, and a problem tree matrix corresponding to a target service type of the call service in the XDR call record. And acquiring a fault definition analysis result of the XDR call record aiming at the call service of the target service type according to the fault definition network element, the fault definition domain, the fault definition result, the problem reason and the processing suggestion corresponding to the call record.

In this implementation manner, the processing module 12 is specifically configured to, if the delimited domain corresponding to the call record is a non-wireless domain, use the fault delimited network element, the fault delimited domain, the fault delimited result, the problem cause, and the processing suggestion corresponding to the call record as a fault delimited analysis result of the XDR call record for the call service of the target service type. If the delimited domain corresponding to the call record is a wireless domain, acquiring the reason of the problem of the wireless domain corresponding to the XDR call record according to a fourth target field of the wireless domain in the XDR call record and a mapping relation among a preset field, the fourth target field and the reason of the problem of the wireless domain; the fourth target field includes the preset field. And taking the wireless domain problem reason corresponding to the XDR call record, and the fault delimitation network element, the fault delimitation domain, the fault delimitation result, the problem reason and the processing suggestion corresponding to the call record as a fault delimitation analysis result of the XDR call record aiming at the call service of the target service type.

Optionally, the receiving module 13 is configured to receive a fault definition analysis request for the call service of the target service type before the processing module 12 determines the fault definition analysis result for the call service of the target service type in each XDR call record of each terminal device. The processing module 12 is further configured to obtain a fault definition analysis result of the call service for the target service type according to the fault definition analysis result of each XDR call record of each terminal device for the call service of the target service type after determining the fault definition analysis result of each XDR call record of each terminal device for the call service of the target service type. And outputting a fault definition analysis result aiming at the call service of the target service type.

Optionally, the receiving module 13 is configured to receive a fault definition analysis request for the call service of the target terminal before the processing module 12 determines that each XDR call record of each terminal device is a fault definition analysis result for the call service of the target service type. The processing module 12 is further configured to extract a fault definition analysis result of each XDR call record of the target terminal for the call service of each service type after determining the fault definition analysis result of each XDR call record of each terminal device for the call service of the target service type, and obtain the fault definition analysis result of the call service of the target terminal. And outputting the fault delimitation analysis result of the call service of the target terminal.

The call service data processing apparatus provided in the embodiment of the present application may execute the call service data processing method in the foregoing method embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

Fig. 17 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Wherein, the electronic device is used for executing the call service data processing method. The electronic device may be, for example, the aforementioned device with a call service data processing system deployed. As shown in fig. 17, the access control apparatus 1700 may include: at least one processor 1701, memory 1702, and a communication interface 1703.

The memory 1702 is used for storing programs. In particular, the program may include program code including computer operating instructions.

The memory 1702 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor 1701 is configured to execute computer executable instructions stored in the memory 1702 to implement the methods described in the foregoing method embodiments. The processor 1701 may be a CPU, or an Application Specific Integrated Circuit (ASIC) or one or more Integrated circuits configured to implement the embodiments of the present Application.

The processor 1701 may communicatively interact with external devices via the communication interface 1703. When the access control device is an SDP controller, the external device referred to herein may be, for example, a terminal device of a user or a terminal device of a staff member.

In a specific implementation, if the communication interface 1703, the memory 1702 and the processor 1701 are implemented independently, the communication interface 1703, the memory 1702 and the processor 1701 may be connected to each other through a bus and communicate with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. Buses may be classified as address buses, data buses, control buses, etc., but do not represent only one bus or type of bus.

Alternatively, in a specific implementation, if the communication interface 1703, the memory 1702 and the processor 1701 are integrated on one chip, the communication interface 1703, the memory 1702 and the processor 1701 may perform communication through an internal interface.

The present application also provides a computer-readable storage medium, which may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and in particular, the computer-readable storage medium stores program instructions, and the program instructions are used in the method in the foregoing embodiments.

The present application also provides a program product comprising execution instructions stored in a readable storage medium. The at least one processor of the access control device may read the execution instruction from the readable storage medium, and the execution of the execution instruction by the at least one processor causes the access control device to implement the call service data processing method provided in the various embodiments described above.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A call service data processing method is characterized in that a first communication system and a second communication system provide call service in a voice fallback mode, and the method comprises the following steps:

determining a fault delimitation analysis result of each XDR call record of each terminal device aiming at the call service of the target service type according to the XDR call record of at least one call service of at least one terminal device and a problem tree matrix corresponding to the call service of the target service type; the problem tree matrix is used for representing the mapping relation among the XDR call record, the fault delimiting network element, the fault delimiting domain, the fault delimiting result, the problem reason and the processing suggestion.

2. The method according to claim 1, wherein the generating an XDR call record for at least one call service of at least one terminal device according to the XDRs of each domain comprises:

asynchronously importing each domain XDR into a stack of each domain according to the time of receiving each domain XDR;

and according to the maximum XDR keeping time, extracting the XDR of the same call service belonging to the same terminal equipment from the stack of each domain, and generating an XDR call record of the call service of the terminal equipment by using the extracted XDR.

3. The method of claim 2, wherein the extracting XDRs of the same call service belonging to the same terminal device from stacks of domains according to the XDR holding maximum duration comprises:

for the same terminal device, if the XDR of the terminal device in the first core network domain and the XDR of the second core network domain are matched from the stack of the first core network domain and the stack of the second core network domain, detecting whether the XDR of the terminal device exists in the stack of the third core network domain according to the first maximum duration of retention;

if the XDR of the terminal equipment exists in the stack of the third core network domain, detecting whether the XDR of the terminal equipment exists in the stack of the wireless domain according to a second maximum holding duration, wherein the second maximum holding duration is smaller than the first maximum holding duration;

if the XDR of the terminal equipment exists in the stack of the wireless domain, merging the XDR of the terminal equipment in the first core network domain, the XDR of the second core network domain, the XDR of the third core network domain and the XDR of the wireless domain to obtain the XDR of the call service of the terminal equipment;

if the XDR of the terminal device does not exist in the stack of the wireless domain, and/or the XDR of the terminal device does not exist in the stack of the third core network domain, merging the other matched XDRs of the terminal device to obtain the XDR of the call service of the terminal device.

4. The method of claim 3, wherein the problem tree matrix comprises mapping relationships among a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain, a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem cause, and a processing proposal in the XDR call record;

the determining, according to the XDR call record of at least one call service of at least one terminal device and the problem tree matrix corresponding to the call service of the target service type, a fault definition analysis result of each XDR call record of each terminal device for the call service of the target service type includes:

for each XDR call record of each terminal device, determining a fault delimiting network element, a fault delimiting domain, a fault delimiting result, a problem reason and a processing suggestion corresponding to the call record according to a first target field of a first core network domain, a second target field of a second core network domain, a third target field of a third core network domain in the XDR call record and a problem tree matrix corresponding to a target service type of a call service;

and acquiring a fault definition analysis result of the XDR call record aiming at the call service of the target service type according to the fault definition network element, the fault definition domain, the fault definition result, the problem reason and the processing suggestion corresponding to the call record.

5. The method of claim 4, wherein obtaining the fault definition analysis result of the XDR call record for the call service of the target service type according to the fault definition network element, the fault definition domain, the fault definition result, the problem cause, and the processing suggestion corresponding to the call record comprises:

if the delimited domain corresponding to the call record is a non-wireless domain, taking a fault delimited network element, a fault delimited domain, a fault delimited result, a problem reason and a processing suggestion corresponding to the call record as a fault delimited analysis result of the XDR call record aiming at the call service of the target service type;

if the delimited domain corresponding to the call record is a wireless domain, acquiring the reason of the problem of the wireless domain corresponding to the XDR call record according to a fourth target field of the wireless domain in the XDR call record and a mapping relation among a preset field, the fourth target field and the reason of the problem of the wireless domain; the fourth target field comprises the preset field;

and taking the wireless domain problem reason corresponding to the XDR call record, and the fault delimitation network element, the fault delimitation domain, the fault delimitation result, the problem reason and the processing suggestion corresponding to the call record as a fault delimitation analysis result of the XDR call record aiming at the call service of the target service type.

6. The method according to any of claims 1-5, wherein before determining the result of fault-delimiting analysis of each XDR call record of each terminal device for the call service of the target service type, the method further comprises:

receiving a fault delimitation analysis request aiming at a call service of a target service type;

after determining the fault definition analysis result of each XDR call record of each terminal device for the call service of the target service type, the method further includes:

acquiring a fault delimitation analysis result of the call service aiming at the target service type according to each XDR call record of each terminal device;

and outputting a fault definition analysis result aiming at the call service of the target service type.

7. The method according to any of claims 1-5, wherein before determining the result of fault-bound analysis of each XDR call record of each terminal device for the call service of the target service type, the method further comprises:

receiving a fault delimitation analysis request aiming at a call service of a target terminal;

extracting fault delimitation analysis results of each XDR call record of the target terminal aiming at the call service of each service type, and acquiring the fault delimitation analysis results of the call service of the target terminal;

and outputting a fault delimitation analysis result of the call service of the target terminal.

8. A call service data processing device, wherein a call service is provided between a first communication system and a second communication system by a voice fallback mode, comprising:

9. An electronic device, comprising: a processor, a communication interface, and a memory; the processor is respectively in communication connection with the communication interface and the memory;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory to implement the method of any of claims 1 to 7.

10. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the method of any one of claims 1 to 7.