Backfilling of ticket information

Abstract

The embodiment of the invention provides a ticket information backfilling method. The method comprises the following steps: acquiring a keyword in an XDR and a learning record of an outgoing relationship; the learning record of the outgoing relationship comprises at least one outgoing relationship associated with the keyword; querying a target outgoing relationship from the learning record of the outgoing relationship according to keywords in the XDR; and backfilling the key field in the XDR according to the queried target outgoing relationship. Therefore, accurate filling of important information is realized, excessive useless information during association backfilling is avoided, and the problems of more and more deployed DPI systems due to different sources of data acquired by different DPI systems, incapability of accurate filling when ticket information is sent between different DPI systems, excessive useless information, large traffic bandwidth occupation, and high efficiency of the related technology are solved. The system load is increased, some processing errors are caused, and important information sharing among DPIs is achieved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication, in particular, to a method for backfilling of call detail record information. BACKGROUND

[0002] With the rapid development of mobile communication networks, each communication network is rapidly deployed globally, and the big data application system for monitoring data of each network is also deployed: a deep packet inspection (DPI) system supporting 4G, a DPI system supporting 5G, a DPI system supporting IMS domain, a DPI system supporting 5G message, a DPI system supporting 5G new call, a user plane DPI system, a control plane DPI system, and the like. The data collected by each DPI system comes from different sources, resulting in more and more deployed DPI systems. Important information needs to be supplemented among each DPI system, and when different DPI systems supplement important information by sending call detail record information (XDR) to each other, accurate filling becomes a big problem, and too much useless information is caused, which occupies a large flow bandwidth, increases the load of the system and causes some processing errors. SUMMARY

[0003] Embodiments of the present application provide a method for backfilling of call detail record information, to at least solve the problem that in the related art, different DPI systems collect data from different sources, resulting in more and more deployed DPI systems, different DPI systems cannot accurately fill when sending call detail record information to each other, and too much useless information is caused, which occupies a large flow bandwidth, increases the load of the system and causes some processing errors.

[0004] According to an embodiment of the present application, a method for backfilling of call detail record information is provided, comprising:

[0005] obtaining a keyword in the call detail record XDR and a learning record of external sending relationship; the learning record of external sending relationship includes an external sending relationship associated with at least one keyword;

[0006] querying a target external sending relationship from the learning record of external sending relationship according to the keyword in the XDR;

[0007] performing backfilling of a key field in the XDR according to the target external sending relationship queried.

[0008] According to another embodiment of the present application, a computer readable storage medium is also provided, and the computer readable storage medium stores a computer program, wherein the computer program is set to execute the steps in any of the above method embodiments when running.

[0009] According to still another embodiment of the present application, an electronic device is also provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor being arranged to execute the computer program to perform the steps of any of the method embodiments described above.

[0010] According to still another embodiment of the present application, a computer program product is also provided, comprising a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

[0011] In the embodiments of the present application, the keywords in the call record XDR and the learning record of the external relationship are obtained; the learning record of the external relationship includes at least one keyword associated external relationship; the target external relationship is queried from the learning record of the external relationship according to the keyword in the XDR; and the key field in the XDR is backfilled according to the queried target external relationship. The information required by the backfilling of the key field of the system based on the learned external relationship is obtained, so that the important information can be accurately filled, and the problem that too much useless information is caused during the backfilling is avoided. The problem that the data sources collected by different DPI systems are different in the related art, so that more and more DPI systems are deployed, and the important information cannot be accurately filled when the call information is transmitted between different DPI systems, and too much useless information occupies a large flow bandwidth, and the system load is increased and some processing errors are caused is solved, and the important information sharing between different DPI systems is achieved. BRIEF DESCRIPTION OF DRAWINGS

[0012] Figure 1 FIG. 1 is a hardware structure block diagram of a computer terminal of a call information backfilling method according to an embodiment of the present application;

[0013] Figure 2 FIG. 2 is a system architecture diagram of an external relationship according to an embodiment of the present application;

[0014] Figure 3 FIG. 3 is a flowchart of a call information backfilling method according to an embodiment of the present application;

[0015] Figure 4 FIG. 4 is a flowchart of external relationship learning according to an embodiment of the present application;

[0016] Figure 5 FIG. 5 is a flowchart of IPTEID-IMSI external relationship backfilling according to an embodiment of the present application;

[0017] Figure 6 FIG. 6 is a flowchart of external relationship backfilling between ternary groups of numbers according to an embodiment of the present application;

[0018] Figure 7 FIG. 7 is a flowchart of IMSI-Locaiton external relationship backfilling according to an embodiment of the present application;

[0019] Figure 8 is a sending relationship structure diagram according to an embodiment of the present application;

[0020] Figure 9 is a sending flow diagram based on IP TEID-IMSI sending relationship according to an embodiment of the present application;

[0021] Figure 10 is a sending flow diagram based on ternary relationship between numbers according to an embodiment of the present application;

[0022] Figure 11 is a sending flow diagram based on IMSI-Location sending relationship according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0025] At present, the data sources collected by various DPI systems are different, resulting in more and more deployed DPI systems. When sending call information between different DPI systems, accurate filling becomes a big problem, and because the DPI system needs to support many operation and maintenance requirements, the definition of the call field often changes, and the length of the call field is getting longer and longer. If each DPI system sends call information to each other, it will inevitably cause too much useless information, occupy a lot of traffic bandwidth, increase the load of the system and cause some processing errors.

[0026] Based on the technical problems existing in the prior art, the present application provides a call information backfilling method, and the technical concept is to backfill the information required by the system based on the learned sending relationship, so as to accurately fill in important information and avoid too much useless information when backfilling, so as to achieve important information sharing between various DPIs. The call information backfilling method of the embodiments of the present application can be applied to the construction of operator DPI systems, and provides protection for backfilling numbers and positions for each DPI system, facilitates the operator to realize important information sharing of each network system, and flexibly constructs a network.

[0027] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking the running on a computer terminal as an example, Figure 1 is a hardware structure block diagram of a computer terminal of a call information backfilling method according to an embodiment of the present application. As Figure 1 shown, the computer terminal can include one or more (Figure 1 The computer terminal shown in FIG. 1 includes one processor 102 (the processor 102 can include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. The computer terminal can also include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art can understand that, Figure 1 The structure shown is only schematic and does not limit the structure of the computer terminal. For example, the computer terminal can include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG. 1. Figure 1 The structure shown is only schematic and does not limit the structure of the computer terminal. For example, the computer terminal can include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG. 1. Figure 1 The structure shown is only schematic and does not limit the structure of the computer terminal. For example, the computer terminal can include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG. 1.

[0028] The memory 104 can be used to store computer programs, such as software programs of application software and modules, such as a computer program corresponding to the call information backfilling method in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, that is, implements the method described above. The memory 104 can include a high-speed random access memory and can also include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, and these remote memories can be connected to the mobile terminal through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0029] The transmission device 106 is used to receive or send data via a network. Specific examples of the network can include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.

[0030] Figure 2 is a system architecture diagram of an external relationship system according to the embodiments of the present application. The embodiments of the present application can run on the network architecture shown in FIG. 2, such as Figure 2 Figure 2 ​As shown, the network architecture includes a protocol decoding processor, a synthesis server, and an upper-layer application system, wherein the protocol decoding processor can generate a standard XDR and send it to the synthesis server, the synthesis server can be one or more, each synthesis server has the functions of extracting a sending relationship, learning a sending relationship, and learning a sending relationship.

[0031] As shown, Figure 2 The protocol decoding processor can be used to receive core network data processed by mirroring or splitting, and generate a standard XDR according to the core network data processed by mirroring or splitting and send it to the synthesis server.

[0032] The synthesis server can include synthesis server 1, synthesis server 2, and synthesis server 3. The synthesis server 1 can receive the standard XDR and perform a learning relationship, upload the learned relationship to the upper-layer application system; the synthesis server 1 can extract the sending relationship from the standard XDR and send it to the synthesis server 2; the synthesis server 2 can fill in the received sending relationship into its own XDR field and send the filled XDR to the upper-layer application system; the synthesis server 1 can also receive the sending relationship sent by the synthesis server 3, fill in the sending relationship sent by the synthesis server 3 into its own XDR field, and send the filled XDR to the upper-layer application system; the synthesis server 3 can also fill in the received other sending relationship and send the filled XDR to the upper-layer application system.

[0033] In this embodiment, a method for filling in call information in the above computer terminal or network architecture is provided, Figure 3 The flowchart of the method for filling in call information according to the embodiment of the present application is shown in Figure 3 The flowchart includes the following steps:

[0034] Step S301, obtaining a keyword and a learning record of a sending relationship in the call XDR; the learning record of the sending relationship includes at least one keyword associated sending relationship.

[0035] The sending relationship of the embodiment of the present application can be sent between each DPI system to supplement each other's XDR information.

[0036] As an example, the current DPI system node can receive the sending relationship sent by the previous DPI system node and learn the sending relationship to generate a learning record of the sending relationship. The learning record of the sending relationship can be saved in the memory, wherein the learning record of the sending relationship can include at least one keyword associated sending relationship, so as to query the corresponding sending relationship according to the obtained keyword.

[0037] As an example, the structure of the outgoing relationship can include, but is not limited to, a Session Initiation Protocol Data Transfer Protocol (SDTP) header, an outgoing relationship fixed field, an outgoing relationship Tag Length Value (TLV), and the like.

[0038] In an exemplary embodiment, the learning record of the outgoing relationship includes at least one of the following records: an outgoing relationship between an IP tunnel endpoint identifier (IPTEID) and an International Mobile Subscriber Identification Number (IMSI), an outgoing relationship between a three-tuple number, and an outgoing relationship between an IMSI and a location; wherein the three-tuple number includes an IMSI, an International Mobile Equipment Identity (IMEI), and a Mobile Subscriber International ISDN Number (MSISDN).

[0039] As an example, the learning record of the outgoing relationship can include, but is not limited to, an outgoing relationship between an IP tunnel endpoint identifier (IPTEID) and an International Mobile Subscriber Identification Number (IMSI), an outgoing relationship between a three-tuple number, and an outgoing relationship between an IMSI and a location. Wherein the three-tuple number includes an IMSI, an International Mobile Equipment Identity (IMEI), and a Mobile Subscriber International ISDN Number (MSISDN).

[0040] In an exemplary embodiment, the key includes at least one of the following: an IP tunnel endpoint identifier (IPTEID), an International Mobile Subscriber Identification Number (IMSI), an International Mobile Equipment Identity (IMEI), and a Mobile Subscriber International ISDN Number (MSISDN).

[0041] In an exemplary embodiment, before obtaining the learning record of the outgoing relationship, further comprising:

[0042] identifying the header field in the received XDR;

[0043] in the case where the header field value of the XDR is a preset outgoing relationship header field value, determining that the XDR is the outgoing relationship;

[0044] Learning is performed based on the field of the outgoing relationship, and a learning record of the outgoing relationship is generated.

[0045] As an example, the outgoing relationship can be an XDR, and therefore, the outgoing relationship needs to be identified before learning, so as to distinguish the standard XDR or other outgoing relationships in the system. The embodiments of the present application can send the XDR ticket and the outgoing relationship based on the SDTP protocol, define the SDTP header, and distinguish the different structures of the two types of tickets, i.e., the XDR ticket and the outgoing relationship.

[0046] As an example, the header field in the received XDR can be identified, and if the header field value of the XDR is the same as or matches the preset header field value of the outgoing relationship, it can be determined that the XDR is the outgoing relationship. Learning can be performed based on the field of the outgoing relationship, and a learning record of the outgoing relationship is generated.

[0047] For example, Figure 4 is a flowchart of outgoing relationship learning according to the embodiments of the present application, as Figure 4 shown, when multiple outgoing relationships are received, it can be determined whether it is a target outgoing relationship according to the SDTP header of the outgoing relationship. If it is a target outgoing relationship, learning of the outgoing relationship can be performed according to the preset structure of the outgoing relationship, and a learning record is generated and saved to the memory. If it is not a target outgoing relationship, it can be directly released without learning of the outgoing relationship.

[0048] In step S302, the target outgoing relationship is queried from the learning record of the outgoing relationship according to the keyword in the XDR.

[0049] In the embodiments of the present application, the DPI system can query the learning record of the outgoing relationship that meets the condition from the memory, so as to associate and backfill the outgoing relationship obtained from the learning record.

[0050] As an example, the target outgoing relationship corresponding to the keyword in the XDR can be queried from the learning record of the outgoing relationship.

[0051] As an example, the keywords in the XDR can include, but are not limited to, IPTEID, IMSI, IMEI, MSISDN, etc., so that the target external relationship can be queried from the learning record of the external relationship according to the keywords. For example, the external relationship between IPTEID and IMSI can be queried from the learning record of the external relationship according to the IPTEID; the external relationship between IMSI and the IMEI, MSISDN three tuple number can be queried from the learning record of the external relationship according to the IMSI, or the external relationship between IMEI and the IMSI, MSISDN three tuple number can be queried from the learning record of the external relationship according to the IMEI, or the external relationship between MSISDN and the IMEI, IMSI three tuple number can be queried from the learning record of the external relationship according to the MSISDN; the external relationship between IMSI and the location can be queried from the learning record of the external relationship according to the IMSI.

[0052] In step S303, the key field in the XDR is backfilled according to the queried target external relationship.

[0053] In the embodiment of the application, the key field in the XDR can be backfilled according to the queried target external relationship.

[0054] As an example, when receiving the massive XDR data, the learning record can be queried according to the keywords in the XDR data, and the external relationship in the queried learning record is backfilled to the key field.

[0055] For example, Figure 5 is a flowchart of the IPTEID-IMSI external relationship backfilling according to the embodiment of the application, as shown in Figure 5 When receiving the massive XDR data, it can be judged whether the XDR data carries valid IPTEID information, if yes, the IPTEID-IMSI external relationship can be queried from the learning record, and the IMSI can be backfilled to the IMSI field in the XDR according to the queried IPTEID-IMSI external relationship; if not, the query can not be performed.

[0056] For example, Figure 6 is a flowchart of the external relationship backfilling among the three tuple numbers according to the embodiment of the application, as shown in Figure 6 When receiving the massive XDR data, it can be judged whether the XDR data carries the IMSI information or backfills the IMSI information, if yes, the external relationship among the three tuple numbers can be queried from the learning record, and the IMEI can be backfilled to the IMEI field in the XDR and the MSISDN can be backfilled to the MSISDN field in the XDR according to the external relationship among the three tuple numbers queried based on the IMSI.

[0057] The IMSI can be backfilled into the IMSI field in the XDR and the MSISDN can be backfilled into the MSISDN field in the XDR according to the outgoing relationship between the triple numbers based on the IMEI, or the IMSI can be backfilled into the IMSI field in the XDR and the MSISDN can be backfilled into the MSISDN field in the XDR according to the outgoing relationship between the triple numbers based on the MSISDN.

[0058] Figure 7 is a flowchart of the IMSI-Location outgoing relationship backfilling according to the embodiments of the application, as shown in Figure 7 When receiving the massive XDR data, it can be judged whether the IMSI information is carried in the DR data or backfilled, if yes, the IMSI-Location outgoing relationship can be queried from the learning record, and the location can be backfilled into the field corresponding to the location information in the XDR according to the queried IMSI-Location outgoing relationship.

[0059] The call information backfilling method of the embodiments of the application can be used for the control plane DPI system to send the IPTEID-IMSI outgoing relationship and the outgoing relationship between the triple numbers to the user plane DPI system to assist the user plane DPI system to fill the number information, can be used for the DPI system of the 4G LTE network to send the location information to the DPI system of the 4G IMS network to assist the DPI system of the 4G IMS network to fill the location information, and can be used for the DPI system of the 4G LTE network and the 5G network DPI system to send the location information to the DPI system of the 5G new call to fill the location information. It should be noted that the outgoing relationship between the IMSI-IMEI-MSISDN triple numbers can be sent between the DPI systems to supplement each other.

[0060] The call information backfilling method of the embodiments of the application can be applied to the construction of the operator DPI system, can provide guarantee for the backfilling of the numbers and the locations for each DPI system, and facilitates the operator to realize the important information sharing of each network system and flexibly construct the network.

[0061] In an exemplary embodiment, further comprising:

[0062] In the case where the XDR meets the sending condition, the outgoing relationship is extracted from the XDR meeting the sending condition according to the field of the predefined outgoing relationship and is sent to the next node.

[0063] The DPI system node of the embodiments of the application can also have the functions of extracting and sending the outgoing relationship.

[0064] As an example, in the case that the XDR meets the sending condition, the external relationship can be extracted from the XDR meeting the sending condition according to the pre-defined field of the external relationship and sent to the next node.

[0065] It should be noted that the external relationship is generated based on the pre-defined field of the external relationship, and the pre-defined field of the external relationship can be various, and the external relationship can also be various, and the content of the external relationship sent to the next node can be the same as or different from the content of the external relationship described above, which is not limited by the embodiments of the present application.

[0066] In an exemplary embodiment, the pre-defined field of the external relationship includes at least one of the following fields: a session initial data transmission protocol (SDTP) header field, an external relationship fixed field, and an external relationship type length value (TLV) field.

[0067] As an example, the external relationship can be extracted from the XDR meeting the sending condition according to the pre-defined field of the external relationship.

[0068] Figure 8 The external relationship structure according to the embodiments of the present application is shown in FIG. 1. Figure 8 As shown in FIG. 1, the structure of the external relationship includes an SDTP header field, an external relationship fixed field, and an external relationship TLV field.

[0069] As an example, the embodiments of the present application can send the XDR call record and the external relationship based on the SDTP protocol, define the SDTP header, and distinguish the different structures of the two types of call records, i.e., the XDR call record and the external relationship. The external relationship fixed field is all the necessary fields to ensure that the external relationship can be associated with backfilling, and the external relationship TLV field is some fields attached to the external relationship to assist in filling some non-mandatory fields. The TLV field is sent if it exists in the call record, and the absence of the TLV field does not affect the sending of the external relationship.

[0070] The XDR call record and the external relationship can be distinguished by XDRType in the SDTP header, for example, the XDRType in the SDTP header of the standard XDR is non-100, and the XDRType of the external relationship is 100. The standard XDR and the external relationship can also be distinguished by the length of the call record in the Len field in the SDTP header, and the definition of the cmd field in the SDTP header of the standard XDR and the external relationship is also different, and the XDR call record and the external relationship can also be distinguished by the cmd field.

[0071] In an exemplary embodiment, the pre-defined outgoing relationship field includes an SDTP header field, and the SDTP header field includes at least one of the following fields: an XDR type field, an outgoing relationship length field, and an outgoing relationship unique command field; and the SDTP header field value of the pre-defined outgoing relationship is different from the header field value in the XDR.

[0072] For example, Table 1 is an IPTEID-IMSI outgoing relationship structure composition table, as shown in Table 1 below, the IPTEID-IMSI outgoing relationship can include an SDTP header, a bill interface for sending the IPTEID-IMSI outgoing relationship, a flow type, a flow state, network side IP and tunnel end point identification (TEID) information, access side IP and tunnel end point identification (TEID) information, bill start time, protocol data unit ID (PDUID), data network name (DNN) information, and the like, wherein the DNN in the relationship TLV part can or can not carry the DNN.

[0073]

[0074] Table 1

[0075] For example, Table 2 is a three-tuple number between outgoing relationship structure composition table, as shown in Table 2 below, the three-tuple number between outgoing relationship includes an SDTP header and an outgoing relationship fixed part, wherein the outgoing relationship fixed part includes an IMSI, an IMEI, and an MSISDN number three-tuple.

[0076]

[0077] Table 2

[0078] For example, Table 3 is an IMSI-Location outgoing relationship structure composition table, as shown in Table 3 below, the IMSI-Location outgoing relationship includes an SDTP header, a flow type, a flow state, an IMSI, location information, and bill start time.

[0079]

[0080] Table 3

[0081] In an exemplary embodiment, the sending condition comprises the XDR being an XDR of a target interface; wherein the XDR of the target interface comprises at least one of the following: an XDR of an N11 interface, an XDR of an N4 interface, an XDR of an S11 interface, an XDR of an N1N2 interface, an XDR of an S1 mobile management entity (MME) interface.

[0082] Figure 9 is a sending flow diagram based on IPTEID-IMSI external relationship according to an embodiment of the present application, as shown in Figure 9 When mass XDR data enters the IPTEID-IMSI sending system, it can be first judged whether the interface corresponding to the XDR is N11 or N4 or S11. If the XDR is not data of the three interfaces, the XDR data can be filtered out. If the XDR is data of the three interfaces, the data is released, and it is further judged whether the XDR data contains IMSI and contains valid IP and TEID information of the core network side and IP and TEID information of the access side. If the XDR data does not contain IMSI or valid IP and TEID information of the core network side or IP and TEID information of the access side, the XDR data is filtered out. If the XDR data contains IMSI and contains valid IP and TEID information of the core network side and IP and TEID information of the access side, the IPTEID-IMSI external relationship is generated, and the generated IPTEID-IMSI external relationship is sent to the next node, such as other DPI systems, other synthesis servers, etc.

[0083] Figure 10 is a sending flow diagram based on external relationship between three tuple numbers according to an embodiment of the present application, as shown in Figure 10 When mass XDR data enters the IPTEID-IMSI sending system, it can be first judged whether the interface corresponding to the XDR is N11 or N4 or S11. If the XDR is not data of the three interfaces, the XDR data can be filtered out. If the XDR is data of the three interfaces, the data is released, and it is further judged whether the XDR data contains IMSI and contains valid IP and TEID information of the core network side and IP and TEID information of the access side. If the XDR data does not contain IMSI or valid IP and TEID information of the core network side or IP and TEID information of the access side, the XDR data is filtered out. If the XDR data contains IMSI and contains valid IP and TEID information of the core network side and IP and TEID information of the access side, the IPTEID-IMSI external relationship is generated, and the generated IPTEID-IMSI external relationship is sent to the next node, such as other DPI systems, other synthesis servers, etc.

[0084] All XDRs can be sent as long as they contain three tuple numbers.

[0085] Figure 11 is a sending flow diagram based on IMSI-Location external relationship according to an embodiment of the present application, as shown in Figure 11As shown, when mass XDR data enters the IMSI-Location sending system, it can be first judged whether the interface corresponding to the XDR is N1N2 or S1MME interface. If the XDR is not the data of these two interfaces, the XDR data can be filtered out. If the XDR is the data of N1N2 or S1MME interface, the data is released, and the process is judged. If the process to which the XDR belongs is any one of the paging process, the chain release process, the cut-out process, and the non-successful process of the cut-in process, the XDR data can be filtered out and not exported (the location information of these four processes is not accurate, so these four processes do not export location information). Otherwise, the data is released, and it is judged whether the XDR data contains IMSI and valid location information. If yes, the IMSI-Location export relationship can be generated according to the field structure of the pre-defined IMSI-Location export relationship, and sent to the next node, such as other DPI systems, other synthesis servers, etc.

[0086] It should be noted that the N11 interface is the interface between the AMF and the SMF in the 5G network architecture, the N4 interface is the interface between the UPF and the SMF in the 5G network architecture, and the S11 interface is the interface between the MME and the SGW in the 4G network architecture. These three interfaces are interfaces that carry IPTEIDs in 4G and 5G networks. N1N2 is the interface between the base station and the AMF in the 5G network architecture, and S1MME is the interface between the base station and the MME in the 4G network architecture. The location information carried by these two interfaces is reliable, and the proportion of location information carried is high.

[0087] In the embodiments of the present application, the keywords in the call record XDR and the learning record of the export relationship are obtained; the learning record of the export relationship includes at least one keyword associated export relationship; the target export relationship is queried from the learning record of the export relationship according to the keyword in the XDR; and the key field in the XDR is backfilled according to the target export relationship. The information required by the backfilling of the key field in the system is obtained based on the learning of the export relationship, thereby accurately filling important information and avoiding too much useless information during backfilling, solving the problem that in related technologies, different DPI systems collect data from different sources, resulting in more and more deployed DPI systems, and different DPI systems cannot accurately fill in when sending call record information to each other, causing too much useless information, occupying a large flow bandwidth, increasing the load of the system and causing some processing errors, and achieving important information sharing between different DPI systems.

[0088] Those skilled in the art can clearly understand that the method according to the above-mentioned embodiments can be realized by means of software on a general hardware platform, and of course can also be realized by hardware, but in many cases the former is a better implementation. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk) and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device) to execute the methods described in the various embodiments of the present application.

[0089] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program, and the computer program is configured to execute the steps in any of the above-mentioned method embodiments when running.

[0090] In an example embodiment, the above-mentioned computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0091] The embodiments of the present application also provide an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to perform the steps in any of the above-mentioned method embodiments.

[0092] In an example embodiment, the above-mentioned electronic device can further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0093] The specific examples in the embodiments can refer to the examples described in the above-mentioned embodiments and example implementations, and the embodiments will not be described here again.

[0094] The embodiments of the present application also provide a computer program product, which includes a computer program, and the computer program is executed by a processor to perform the steps in any of the above-mentioned method embodiments.

[0095] It is apparent that those skilled in the art should understand that the modules or steps of the present application described above can be realized by using a universal computing device, which can be centralized on a single computing device or distributed on a network composed of multiple computing devices, and can be realized by using program codes executable by the computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in different order, or they can be made into individual integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

[0096] The above only describes exemplary embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for backfilling call detail record (CDR) information, characterized in that, include: Learn the key words and outbound relationships in the XDR call detail record; The learning record of the outbound relationship includes at least one outbound relationship associated with a keyword; Based on the keywords in the XDR, query the target outbound relationship from the learning records of the outbound relationship; Based on the retrieved target outbound relationships, the key fields in the XDR are backfilled.

2. The method according to claim 1, characterized in that, The learning record of the outgoing relationship includes at least one of the following: the outgoing relationship between IP Tunnel Endpoint Identifier (IPTEID) and International Mobile Subscriber Identity (IMSI), the outgoing relationship between triple numbers, and the outgoing relationship between IMSI and location; wherein the triple number includes IMSI, IMEI, and MSISDN.

3. The method according to claim 1, characterized in that, The keywords include at least one of the following: IP Tunnel Endpoint Identifier (IPTEID), International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), and International Mobile Subscriber Identity (MSISDN).

4. The method according to claim 1, characterized in that, Before acquiring learning records of outbound relationships, the following is also included: Identify the header fields in the received XDR; If the header field value of the XDR is a preset outbound relationship header field value, then the XDR is determined to be the outbound relationship; Learning is performed based on the fields of the outgoing relationship to generate learning records for the outgoing relationship.

5. The method according to claim 1, characterized in that, Also includes: If the XDR meets the sending conditions, the outgoing relationship is extracted from the XDR that meets the sending conditions according to the predefined outgoing relationship fields and sent to the next node.

6. The method according to claim 5, characterized in that, The predefined outbound relationship fields include at least one of the following fields: Session Initiation Data Transfer Protocol (SDTP) header field, outbound relationship fixed field, and outbound relationship type length value (TLV) field.

7. The method according to claim 5, characterized in that, The predefined outbound relationship fields include SDTP header fields, which include at least one of the following fields: XDR type field, outbound relationship length field, and outbound relationship unique command field; the values ​​of the predefined outbound relationship SDTP header fields are different from the values ​​of the header fields in the XDR.

8. The method according to claim 5, characterized in that, The transmission conditions include the XDR being the XDR of the target interface; wherein the XDR of the target interface includes at least one of the following: the XDR of the N11 interface, the XDR of the N4 interface, the XDR of the S11 interface, the XDR of the N1N2 interface, and the XDR of the S1 Mobility Management Entity (MME) interface.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 8.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 8.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 8.

Images