Data processing method, device, electronic device and storage medium

Abstract

The embodiment of the present invention discloses a data processing method, device, electronic device and storage medium. The method includes: determining the key to be verified corresponding to each received data acquisition request according to a pre-established key mapping relationship table; determining the target key verification method according to the verification type corresponding to the data acquisition request; verifying the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result; if the target verification result is consistent with the preset verification result, backfilling the identity identifier corresponding to the data acquisition request to obtain a target backfill result. The method solves the problem in the prior art that the backfill number is obtained based on the mapping relationship between the query GUTI and the number (IMSI), resulting in a high error rate of number backfill, thereby improving the accuracy of number determination and achieving the effect of improving the accuracy of number backfill.

Description

Technical Field

[0001] The present invention relates to computer processing technology, and more particularly to a data processing method, device, electronic device, and storage medium. Background Art

[0002] With the continuous development of mobile communication technology, backfill number technology has also become an effective means for mobile communication systems to determine user identities. Among them, mobile communication systems usually use user private information such as IMSI (International Mobile Subscriber Identification Number) and mobile phone number to represent user identity, and number backfill is achieved by obtaining this information. However, in the network, in order to ensure the security of user private information, IMSI is usually obtained based on the mapping relationship between IMSI and GUTI (Globally Unique Temporary UE Identity). Among them, GUTI is allocated by the network to UE (User Equipment). During the attachment or tracking area update process, MME (Mobility Management Entity) may re-allocate GUTI to UE due to relocation and other reasons. When the number is subsequently backfilled, the GUTI will be obtained first. Since the NAS (Non-Access Stratum) message that allocates the GUTI is often encrypted, the real-time allocated GUTI cannot be obtained when decryption fails, and the GUTI-IMSI mapping relationship cannot be correctly maintained, resulting in number backfill errors and the inability to accurately determine the user identity. Summary of the Invention

[0003] The embodiments of the present invention provide a data processing method, device, electronic device and storage medium to improve the accuracy of number determination and achieve the technical effect of improving the accuracy of number backfilling.

[0004] In a first aspect, an embodiment of the present invention provides a data processing method, the method comprising:

[0005] Determine the key to be verified corresponding to each received data acquisition request according to a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key to be selected;

[0006] Determine the target key verification method based on the identity identifier corresponding to the data acquisition request;

[0007] Verify the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result;

[0008] If the target verification result is consistent with the preset verification result, backfill processing is performed on the identity identifier corresponding to the data acquisition request to obtain a target backfill result.

[0009] In a second aspect, an embodiment of the present invention further provides a data processing device, the device comprising:

[0010] A key determination module for verification, configured to determine the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key to be selected;

[0011] A target key verification mode determination module is used to determine a target key verification mode according to an identity identifier corresponding to a data acquisition request;

[0012] A target verification result acquisition module is used to verify the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result;

[0013] The target backfill result acquisition module is used to perform backfill processing on the identity identifier corresponding to the data acquisition request if the target verification result is consistent with the preset verification result to obtain the target backfill result.

[0014] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising:

[0015] one or more processors;

[0016] a storage device for storing one or more programs,

[0017] When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method as described in any one of the embodiments of the present invention.

[0018] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data processing method as described in any one of the embodiments of the present invention.

[0019] The technical solution of the embodiment of the present invention determines the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table, determines the target key verification method based on the verification type corresponding to the data acquisition request, and verifies the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result. If the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request is backfilled to obtain a target backfill result. This solves the problem in the prior art of obtaining a backfill number based on querying the mapping relationship between the GUTI and the number (IMSI), which leads to a high error rate in number backfilling. When the identity identifier is obtained, the integrity of the key to be verified and the data acquisition request is checked based on the target key verification method corresponding to the identity identifier to obtain the target verification result, thereby achieving the effect of verifying the initially obtained identity identifier. When the target verification result is consistent with the preset verification result, the obtained identity identifier is used as the target backfill result to implement number backfilling, greatly improving the accuracy of the backfill result determination and achieving the technical effect of improving the accuracy of number backfilling. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] To more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings introduced here only illustrate some of the embodiments to be described by the present invention, and are not exhaustive. A person skilled in the art can derive other drawings based on these drawings without inventive effort.

[0021] Figure 1 A flowchart of a data processing method provided in Example 1 of the present invention;

[0022] Figure 2 This is a structural block diagram of a data processing device provided in Embodiment 3 of the present invention;

[0023] Figure 3 This is a structural diagram of an electronic device provided in Example 4 of the present invention. DETAILED DESCRIPTION

[0024] The present invention will be further described in detail below with reference to the accompanying drawings and examples. It will be understood that the specific embodiments described herein are intended only to illustrate the present invention and are not intended to limit the present invention. It should also be noted that, for ease of description, the accompanying drawings only illustrate portions relevant to the present invention, not all structures.

[0025] Example 1

[0026] Figure 1This is a flow chart of a data processing method provided in Embodiment 1 of the present invention. This embodiment is applicable to number verification. This method can be executed by a data processing device in an embodiment of the present invention. The device can be implemented using software and / or hardware. Optionally, it can be implemented by an electronic device, such as a mobile terminal, a PC, or a server. The device can be configured in a computing device. The data processing method provided in this embodiment specifically includes the following steps:

[0027] S110 : Determine the key to be verified corresponding to each received data acquisition request according to a pre-established key mapping relationship table.

[0028] It should be noted that a corresponding number verification system can be developed based on this technical solution, and then the corresponding tasks can be processed based on the system to verify the number. Optionally, the number can be a mobile phone number or an IMSI (International Mobile Subscriber Identification Number). For example, in the field of number backfilling, in order to ensure the accuracy of the backfilled number, the number and the corresponding key can be processed to determine the verification result corresponding to the number, so that it can be determined based on the verification result whether the number is to be backfilled. It should also be noted that this technical solution can be applied to the situation of number verification in the field of number backfilling, and can also be applied to any situation where number verification is required.

[0029] The key mapping table includes an identity and the corresponding key to be selected. The identity can be understood as identifying information used to represent a user's identity. For example, in 4G and / or 5G networks, a mobile phone number or IMSI can be used as an identity. The key to be verified can be used to verify whether the NAS message has been tampered with or to verify the accuracy of the IMSI backfilled in the NAS message.

[0030] In this embodiment, when a data acquisition request is received from a communication device, an interface can be used to retrieve the identity corresponding to the data acquisition request. For example, in 4G mobile communications, when an Extended-Service-Request is received, the IMSI (i.e., the identity) can be obtained by querying the mapping relationship between the GUTI and the IMSI. To verify the correctness of the IMSI, an interface can be used to retrieve the key corresponding to the IMSI from a pre-established key mapping relationship table. For example, in a 4G network, the key can be obtained through the s6a interface; in a 5G network, the key can be obtained through the N12 interface and used as a key to be verified to verify the correctness of the IMSI based on the key to be verified. It should be noted that in actual mobile communication scenarios, when a user uses an input device to initiate a connection between a mobile communication device and a mobile network, the identity corresponding to the mobile communication device can be obtained, such as the IMSI or mobile phone number corresponding to the SIM (Subscriber Identity Module) card built into the mobile communication device. As the user completes a series of operations, the network can use the distribution algorithm to generate a key for integrity verification of the NAS message, that is, the key to be verified. Then, the network can use the mapping technology to map the identity (IMSI or mobile phone number) and the key, and establish a key mapping relationship table so that the key mapped to the identity can be directly retrieved from the key mapping relationship table.

[0031] It should also be noted that in 4G / 5G networks, each data acquisition request includes at least one method of obtaining an identity identifier. For example, in a 4G network, the Initial-Context-Setup-Request (initial context setup request) can obtain the IMSI by associating the S6a interface with KeNB, or by associating the S11 interface with GTP-U (GPRS Tunneling Protocol for the user plane); in a 5G network, the Initial-Context-Setup-Request can obtain the IMSI by associating the N12 interface with KgNB, or by associating the N11 interface with GTP-U tunnel. After receiving the data acquisition request, the IMSI can be obtained based on the method of obtaining the identity identifier corresponding to the request, and then the key to be verified corresponding to the IMSI can be retrieved from the key mapping relationship table.

[0032] Optionally, based on a pre-established key mapping relationship table, determining the key to be verified corresponding to each received data acquisition request, including: receiving at least one data acquisition request sent by the target communication device, and determining the identity identification acquisition method corresponding to each data acquisition request; based on the identity identification acquisition method, obtaining the identity identification corresponding to each data acquisition request; based on the identity identification, retrieving and obtaining the corresponding key to be verified from the key mapping relationship table.

[0033] The target communication device may be a mobile terminal device.

[0034] In actual applications, when a data acquisition request is received from a target communication device, an identity acquisition process can be performed based on the identity acquisition method corresponding to the data acquisition request to obtain the corresponding identity. For example, when the communication path of the mobile terminal is switched from base station A to base station B, a Path-Switch-Request (path switching request) is sent to base station B, and then base station B forwards this request to the server. At this time, it can be considered that the Path-Switch-Request has been received, and the previous session (old session) corresponding to the current session can be associated with the src-mme-ue-s1ap-id, and the IMSI in the previous session is obtained as the IMSI of the current session. The process of obtaining the IMSI based on the Path-Switch-Request is an identity acquisition method. Accordingly, the identity can be obtained based on the identity acquisition method corresponding to each data acquisition request, and then the key to be verified corresponding to the identity can be retrieved from the key mapping relationship table.

[0035] S120: Determine a target key verification method according to the identity identifier corresponding to the data acquisition request.

[0036] The target key verification method refers to a method for verifying the correctness of the identity.

[0037] In practical applications, after the system processes a data retrieval request, it can obtain the identity corresponding to the data retrieval request. Based on the verification method corresponding to the identity, it can verify whether the identity is correct. For example, the verification method can be an integrity check on the NAS message that returns the identity. Optionally, the verification method can be used as a target key verification method.

[0038] It should be noted that after the system processes a data acquisition request and obtains an identity corresponding to the data acquisition request, it can also preliminarily determine whether the identity is correct or uncertain based on the method used to obtain the identity. For example, if the Handover-Request obtains the identity through the S11 interface associated with the GTP-U tunnel, the identity may be preliminarily determined to be uncertain. In this case, further verification of the identity is required. Accordingly, the target key verification method corresponding to the uncertain identity can be used to verify it, thereby improving backfill accuracy.

[0039] Optionally, the target key verification method is determined based on the identity identifier corresponding to the data acquisition request, including: determining the identification type of the identity identifier corresponding to the data acquisition request based on the identity identifier acquisition method corresponding to each data acquisition request; if the identification type is a definite identification, determining the target key verification method based on the authentication feedback data corresponding to the data acquisition request; or, if the identification type is an indefinite identification, determining the target key verification method based on the data acquisition request and the key to be verified.

[0040] The identification type includes a definite identification and an indeterminate identification, and the identification type can represent the accuracy of the identity identification. The identification acquisition method can be understood as the execution means of obtaining the identity identification.

[0041] In this embodiment, the identification type of the obtained identity corresponding to the data acquisition request can be determined based on the identification acquisition method used when processing the data acquisition request, i.e., the identification acquisition method. For example, a Handover-Request that obtains an identity through the Transparent-Container associated S10 / N26 interface can be considered as identification acquisition method 1, and the obtained identity can be marked as a definite identity, i.e., the identification type of the identity is a definite identifier. A Handover-Request that obtains an identity through the GTP-U tunnel associated S11 interface can be considered as identification acquisition method 2, and the obtained identity can be marked as an indeterminate identity, i.e., the identification type of the identity is a definite identifier. Furthermore, the corresponding target key verification method can be determined based on the identification type of the identity. Optionally, if the identification type is a definite identifier, the identity is temporarily confirmed to be correct. However, the backend may also perform further verification of the user's identity, such as authentication verification. If the authentication verification passes, a signaling message indicating authentication success is fed back; if the authentication verification fails, a signaling message indicating authentication failure is fed back. If authentication fails, the obtained identity identifier is considered uncertain and will not be subsequently backfilled. When the identifier type is determined to be a definite identifier, the authentication result in the authentication feedback data corresponding to the data acquisition request can be used as a target key verification method to determine whether the identity identifier is truly accurate. If the identifier type is uncertain, the obtained identity identifier may not be a real-time maintained identifier. For example, in practical applications, the maintenance of the GUTI-IMSI mapping table is affected by factors such as NAS encryption, which can easily lead to mapping errors. Directly backfilling the IMSI (identity identifier) ​​obtained based on the GUTI-IMSI mapping table can lead to IMSI backfill errors. The IMSI-key mapping table is obtained from the s6a and n12 interfaces. During the acquisition process, signaling messages are not encrypted, and the IMSI-key mapping can be maintained persistently. The key to be verified in the key mapping relationship table can be used as a verification condition for verifying the IMSI to verify the correctness of the IMSI. The NAS message in the data acquisition request can be verified against the key to be verified to determine the correctness of the identity identifier, as a target key verification method.

[0042] It should be noted that the identity acquisition methods corresponding to each data acquisition request can be pre-classified based on experience. For example, each identity acquisition method can be divided into a definite identity acquisition method and an indeterminate identity acquisition method. The definite identity acquisition method can be understood as a method for obtaining a definite correct identity, and the indeterminate identity acquisition method can be understood as a method for obtaining an indeterminate correct identity. When obtaining an identity based on an identity acquisition method, it is determined whether the identity is definite correct or indeterminate correct. The correctness of the identity is verified using the corresponding target key verification method to prevent inaccurate identity backfilling and improve the accuracy of number backfilling.

[0043] Optionally, according to the identity identification acquisition method corresponding to each data acquisition request, the identification type of the identity identification corresponding to the data acquisition request is determined, including: dividing the identity identification acquisition method corresponding to each data acquisition request to obtain a definite identity identification acquisition method and an indefinite identity identification acquisition method; if the identity identification acquisition method is a definite identity identification acquisition method, the identification type of the identity identification is a definite identification; or, if the identity identification acquisition method is an indefinite identity identification acquisition method, the identification type of the identity identification is an indefinite identification.

[0044] In practical applications, it is possible to preliminarily determine based on experience whether an identity obtained using a certain identity acquisition method is a definite or indeterminate one, and then categorize the identity acquisition methods corresponding to each data acquisition request. For example, if an indeterminate identity a is obtained based on identity acquisition method A, A can be marked as an indeterminate identity acquisition method. This allows subsequent attempts to obtain an identity using identity acquisition method A to directly mark the identity as an indeterminate identity and verify its correctness. For example, if an Initial-Context-Setup-Request obtains an IMSI through the KgNB-associated N12 interface, it can be preliminarily determined that the IMSI is a definite identity. Accordingly, the Initial-Context-Setup-Request's acquisition method through the KgNB-associated N12 interface can be categorized as a definite identity acquisition method. If a Handover-Request obtains an IMSI through the GTP-U tunnel-associated N11 interface, it can be preliminarily determined that the IMSI is an indeterminate identity. Accordingly, the Handover-Request's acquisition method through the GTP-U tunnel-associated N11 interface can be categorized as an indeterminate identity acquisition method. This allows the identification type of the identity to be determined when determining the identity acquisition method.For example, in a 4G network, the identity identifier cannot be obtained directly from the S1MME interface, and needs to be associated with interfaces such as S6a / S10 / S11 / N26. The identity identifier obtained in the current session can be preliminarily used as the determined identifier. The method for obtaining the determined identity identifier may include but is not limited to: Path-Switch-Request (path switching request) is associated with the previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Definite-IMSI; Handover-Request (handover request) is associated with the previous session through Transparent-Container, and the Definite-IMSI of the previous session; Initial-Context-Setup-Request (initial context setup request) is associated with the IMSI obtained through KeNB through S6a interface; Handover-Request is associated with the IMSI obtained through Transparent-Container S10 / N26; Authentication-Response (authentication response) is associated with the IMSI obtained through the S6a interface through the authentication vector; Attach (attachment) process is through NAS (Network Attached The TAU (Tracking Area User) process associates the IMSI obtained by S10 / N26 through a NAS message. In the 5G network, the identity identifier cannot be obtained directly from the N1N2 interface, and needs to be associated with other interfaces. The identity identifier obtained in the current session can be preliminarily used as the definite identifier. The definite identity identifier acquisition method may include but is not limited to: Path-Switch-Request associates the old session through src-mme-ue-s1ap-id, and the Definite-IMSI of the old session; Handover-Request associates the old session through Transparent-Container, and the IMSI of the old session is Definite-IMSI; Initial-Context-Setup-Request associates the IMSI obtained by the N12 interface through KgNB; Handover-Request associates the IMSI obtained by N14 / N26 through Transparent-Container; Authentication-Response associates the IMSI obtained by the N12 interface through the authentication vector; the registration process associates the IMSI obtained by N14 through GUTI; the registration process associates the IMSI obtained by N26 through NAS message.Furthermore, in the 4G network, the identity obtained in the current session can be initially used as an uncertain identity. The uncertain identity obtaining method may include but is not limited to: Path-Switch-Request associates the previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Not-Sure-IMSI; Handover-Request associates the previous session through Transparent-Container, and the Not-Sure-IMSI of the previous session; Initial-Context-Setup-Request associates the IMSI obtained by the S11 interface through the GTP-U tunnel; Handover-Request associates the IMSI obtained by the S11 interface through the GTP-U tunnel; Initial-UE-Message (initial UE message) obtains the IMSI by querying GUTI (Globally Unique Temporary UE IMSI obtained by querying GUTI through Attach-Request; IMSI carried in Detach-Request; IMSI obtained by querying GUTI through Detach-Request; IMSI carried in TAU-Request; IMSI obtained by querying GUTI through TAU-Request; IMSI obtained by querying GUTI through Extended-Service-Request; IMSI carried in Identity-Response.In the 5G network, the identity obtained in the current session can be initially used as an uncertain identity. The uncertain identity acquisition method may include but is not limited to: Path-Switch-Request associates the previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Not-Sure-IMSI; Handover-Request associates the previous session through Transparent-Container, and the IMSI of the previous session is Not-Sure-IMSI; Initial-Context-Setup-Request associates the IMSI obtained by the N11 interface through the GTP-U tunnel; Handover-Request associates the IMSI obtained by the N11 interface through the GTP-U tunnel; Initial-UE-Message obtains the IMSI by querying the GUTI; IMSI carried in Registration-Request; IMSI obtained by Registration-Request by querying the GUTI; IMSI carried in Identity-Response. Based on the above solution, if the identity acquisition method is a determinate identity acquisition method, the obtained identity can be considered to be of a determinate type. If the identity acquisition method is an indeterminate identity acquisition method, the obtained identity can be considered to be of an indeterminate type. Furthermore, the target key verification method can be determined based on the data acquisition request and the key to be verified. Verifying the correctness of the identity based on the target key verification method improves the accuracy of identity backfilling.

[0045] S130 , performing verification processing on the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result.

[0046] The target verification result may include verification success and verification failure.

[0047] In practical applications, after determining the target key verification method, the accuracy of the identity identifier (IMSI) can be verified based on the target key verification method. This can be done by verifying the authentication feedback data corresponding to the data acquisition request, or by verifying the key to be verified and the NAS message in the data acquisition request. Accordingly, a target verification result is obtained. It should be noted that the specific verification method depends on whether the identity identifier type is definite or indefinite.

[0048] It should also be noted that if the identifier type is a confirmed identifier, the identity identifier can be verified based on the target key verification method corresponding to the authentication feedback data corresponding to the data acquisition request to obtain the target verification result. For example, in actual applications, after the Authentication-Response obtains the IMSI through the S6a interface associated with the authentication vector, the system can initiate an operation to authenticate the IMSI. If the feedback data of the authentication failure is received, the IMSI can be considered as an uncertain identity identifier and not be backfilled. Otherwise, the IMSI is backfilled as the final confirmed identity identifier.

[0049] Optionally, the identification type is a confirmed identification, and the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request are verified based on each target key verification method to obtain a target verification result, including: receiving the authentication feedback data corresponding to the data acquisition request; if the feedback result in the authentication feedback data is consistent with the preset feedback result, the verification success is used as the target verification result.

[0050] The preset feedback result can be understood as successful authentication.

[0051] In actual applications, the authentication feedback data corresponding to the data acquisition request fed back by the authentication system can be received, and then the authentication feedback data can be parsed to obtain the corresponding authentication feedback result. If the authentication feedback result is consistent with the preset feedback result corresponding to the successful authentication, the successful verification can be used as the target verification result, and the identity identifier can be backfilled.

[0052] It should be noted that if the identifier type is an uncertain identifier, the identity identifier can be verified based on the target key verification method corresponding to the data acquisition request and the key to be verified, obtaining a target verification result. When verifying based on the key to be verified, to ensure the security of the key and prevent its disclosure, the key to be verified can be converted to obtain converted data. This converted data can then be verified against the field data in the NAS message in the data acquisition request to determine whether the verification is successful. The verification result can be used as the target verification result.

[0053] Optionally, the identification type is an uncertain identification, and the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request are verified based on each target key verification method to obtain a target verification result, including: converting the key to be verified to obtain the data to be verified; determining the target verification result based on the data to be verified and the command message in the data acquisition request.

[0054] In actual applications, after obtaining the identity identifier corresponding to the data acquisition request, if the identifier type of the identity identifier is an uncertain identifier, the key to be verified can be converted based on the preset field to obtain the processed key to be verified as the data to be verified. The command message in the data acquisition request can be parsed to obtain a NAS message, and then the data to be verified can be compared with the field at the preset position in the NAS message. If the two are consistent, the verification can be considered successful, that is, the verification success can be used as the target verification result; if the two are inconsistent, the verification can be considered failed, that is, the verification failure can be used as the target verification result.

[0055] S140: If the target verification result is consistent with the preset verification result, backfill processing is performed on the identity identifier corresponding to the data acquisition request to obtain a target backfill result.

[0056] The preset verification result may be verification success.

[0057] In this embodiment, if the target verification result is successful, it can be considered consistent with the preset verification result, that is, the identity identifier at this time is the finalized identity identifier. Accordingly, the identity identifier corresponding to the data acquisition request can be used as the target backfill result and backfilled.

[0058] It should be noted that when comparing the target verification result with the preset verification result, the determination can be made based on the comparison of the feedback result in the authentication feedback data with the preset feedback result, or the comparison of the data to be verified with the field at a preset position in the command message. For example, if the comparison results are consistent, the verification can be considered successful, and the identity obtained at this time can be considered the final identity and can be backfilled.

[0059] Optionally, if the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request is backfilled to obtain a target backfill result, including: if the feedback result in the authentication feedback data is consistent with the preset feedback result, the target verification result is the preset verification result; or, if the data to be verified is consistent with the field data at the preset position in the command message, the target verification result is the preset verification result; and the identity identifier corresponding to the data acquisition request is used as the target backfill result.

[0060] Specifically, if the feedback result in the authentication feedback data is consistent with the preset feedback result corresponding to successful authentication, the verification can be considered successful, that is, the successful verification is the target verification result, which is consistent with the preset verification result. If the data to be verified is consistent with the field data at the preset position in the command message, the verification can be considered successful, that is, the successful verification is the target verification result, which is consistent with the preset verification result. When the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request can be used as the target backfill result.

[0061] It should be noted that in the current session, when the identity type obtained is a definite-IMSI, the mapping relationship between the GUTI and the IMSI can be maintained in real time. When processing the Security-Mode-Command message, the identity with the definite-IMSI type is used first. When performing NAS message decryption and integrity verification, the identity with the definite-IMSI type is used first. When outputting call records, only the identity with the definite-IMSI type is used for output, thereby improving the number backfill accuracy of the S1MME / N1N2 interface.

[0062] The technical solution of this embodiment determines the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table, determines the target key verification method based on the verification type corresponding to the data acquisition request, and verifies the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result. If the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request is backfilled to obtain a target backfill result. This solves the problem in the prior art of obtaining a backfill number based on querying the mapping relationship between the GUTI and the number (IMSI), which leads to a high error rate in number backfilling. When the identity identifier is obtained, the integrity of the key to be verified and the data acquisition request is checked based on the target key verification method corresponding to the identity identifier to obtain the target verification result, thereby achieving the effect of verifying the initially obtained identity identifier. When the target verification result is consistent with the preset verification result, the obtained identity identifier is used as the target backfill result to implement number backfilling, greatly improving the accuracy of the backfill result determination and achieving the technical effect of improving the accuracy of number backfilling.

[0063] Example 2

[0064] As an alternative embodiment to the above embodiment, in order to make those skilled in the art further understand the technical solution of the embodiment of the present invention, a specific application scenario example is given. For details, please refer to the following specific content.

[0065] In actual applications, for the 4G core network, user location information is generally obtained from the S1MME interface; for the 5G core network, user location information is generally obtained from the N1N2 interface. For the S1MME and N1N2 interfaces, location information can be obtained directly from the signaling message, but the user identity (IMSI and mobile phone number) and other information need to be obtained by associating with other interfaces. For example, the S1MME interface and the N1N2 interface can be associated with the identity obtained by other interfaces and divided into two categories according to the actual working situation. Among them, one is the definite identification acquisition method, and the identity obtained by this acquisition method (Definite-IMSI) is initially determined to be correct, and the other is the uncertain identification acquisition method, and the identity obtained by this acquisition method (Not-Sure-IMSI) is initially determined to be incorrect. Optionally, in the 4G core network, determining the identification acquisition method may include Path-Switch-Request (path switching request) associating a previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Definite-IMSI; Handover-Request (handover request) associating a previous session through Transparent-Container, and the Definite-IMSI of the previous session; Initial-Context-Setup-Request (initial context setup request) associating the IMSI obtained by S6a interface through KeNB; Handover-Request associating the IMSI obtained by S10 / N26 through Transparent-Container; Authentication-Response (authentication response) associating the IMSI obtained by S6a interface through authentication vector; Attach (attachment) process associating the IMSI obtained by S10 / N26 through NAS (Network Attached Storage) message; TAU (Tracking Area User) process associating the IMSI obtained by S10 / N26 through NAS message.The uncertain identification acquisition methods can be: Path-Switch-Request associates the previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Not-Sure-IMSI; Handover-Request associates the previous session through Transparent-Container, and the Not-Sure-IMSI of the previous session; Initial-Context-Setup-Request associates the IMSI obtained by the S11 interface through the GTP-U tunnel; Handover-Request associates the IMSI obtained by the S11 interface through the GTP-U tunnel; Initial-UE-Message (initial UE message) obtains the IMSI by querying GUTI (Globally Unique Temporary UE IMSI obtained by querying GUTI through Attach-Request; IMSI carried in Detach-Request; IMSI obtained by querying GUTI through Detach-Request; IMSI carried in TAU-Request; IMSI obtained by querying GUTI through TAU-Request; IMSI obtained by querying GUTI through Extended-Service-Request; IMSI carried in Identity-Response.In the 5G network, the identity cannot be obtained directly from the N1N2 interface, and it needs to be associated with other interfaces. Accordingly, the obtained IMSI is used as the identity of the current session (Definite-IMSI). The identification acquisition method may include: Path-Switch-Request associates the old session through src-mme-ue-s1ap-id, and the Definite-IMSI of the old session; Handover-Request associates the old session through Transparent-Container, and the IMSI of the old session is Definite-IMSI; Initial-Context-Setup-Request associates the IMSI obtained by KgNB with the N12 interface; Handover-Request associates the IMSI obtained by N14 / N26 through Transparent-Container; Authentication-Response associates the IMSI obtained by N12 interface through authentication vector; The registration process associates the IMSI obtained by N14 through GUTI; The registration process associates the IMSI obtained by N26 through NAS message The obtained IMSI; the uncertain identification acquisition method of using the obtained IMSI as the Not-Sure-IMSI of the current session may include: Path-Switch-Request associates the previous session through src-mme-ue-s1ap-id, and the IMSI of the previous session is Not-Sure-IMSI; Handover-Request associates the previous session through Transparent-Container, and the IMSI of the previous session is Not-Sure-IMSI; Initial-Context-Setup-Request associates the IMSI obtained by the N11 interface through the GTP-U tunnel; Handover-Request associates the IMSI obtained by the N11 interface through the GTP-U tunnel; Initial-UE-Message obtains the IMSI by querying the GUTI; IMSI carried in Registration-Request; IMSI obtained by querying the GUTI in Registration-Request; IMSI carried in Identity-Response.It should be noted that when executing a data acquisition request to obtain an identity identifier, if the identity identifier is obtained based on an uncertain identifier acquisition method, the identifier type of the identity identifier can be marked as an uncertain identifier (Not-Sure-IMSI). At this time, it is necessary to retrieve the key to be verified corresponding to the identity identifier from the key mapping relationship table, and then perform integrity verification on the key to be verified and the NAS message in the data acquisition request. If the verification is successful, the identifier type of the identity identifier can be converted to a definite identifier, and the identity identifier can be backfilled as the target backfill result. If the identity identifier is obtained based on a definite identifier acquisition method, the identifier type of the identity identifier can be marked as a definite identifier (Definite-IMSI). If the authentication result corresponding to the received authentication feedback data is a feedback result of successful authentication, the identity identifier can be backfilled as the target backfill result. If the authentication result corresponding to the received authentication feedback data is a feedback result of failed authentication, the identifier type of the identity identifier is converted to an uncertain identifier and no backfill is performed.

[0066] It should also be noted that in the current session, when the identity type obtained is a definite-IMSI, the mapping relationship between the GUTI and the IMSI can be maintained in real time. When processing the Security-Mode-Command message, the identity with the definite-IMSI type is used first. When performing NAS message decryption and integrity verification, the identity with the definite-IMSI type is used first. When outputting call records, only the identity with the definite-IMSI type is used for output, thereby improving the number backfill accuracy of the S1MME / N1N2 interface.

[0067] The technical solution of this embodiment determines the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table, determines the target key verification method based on the verification type corresponding to the data acquisition request, and verifies the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result. If the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request is backfilled to obtain a target backfill result. This solves the problem in the prior art of obtaining a backfill number based on querying the mapping relationship between the GUTI and the number (IMSI), which leads to a high error rate in number backfilling. When the identity identifier is obtained, the integrity of the key to be verified and the data acquisition request is checked based on the target key verification method corresponding to the identity identifier to obtain the target verification result, thereby achieving the effect of verifying the initially obtained identity identifier. When the target verification result is consistent with the preset verification result, the obtained identity identifier is used as the target backfill result to implement number backfilling, greatly improving the accuracy of the backfill result determination and achieving the technical effect of improving the accuracy of number backfilling.

[0068] Example 3

[0069] Figure 2 This is a structural block diagram of a data processing device provided by the third embodiment of the present invention. The device includes: a to-be-verified key determination module 210 , a target key verification mode determination module 220 , a target verification result acquisition module 230 , and a target backfill result acquisition module 240 .

[0070] Among them, the key to be verified determination module 210 is used to determine the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key to be selected; the target key verification method determination module 220 is used to determine the target key verification method based on the identity identifier corresponding to the data acquisition request; the target verification result acquisition module 230 is used to verify the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result; the target backfill result acquisition module 240 is used to backfill the identity identifier corresponding to the data acquisition request if the target verification result is consistent with the preset verification result to obtain a target backfill result.

[0071] The technical solution of this embodiment determines the key to be verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table, determines the target key verification method based on the verification type corresponding to the data acquisition request, and verifies the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result. If the target verification result is consistent with the preset verification result, the identity identifier corresponding to the data acquisition request is backfilled to obtain a target backfill result. This solves the problem in the prior art of obtaining a backfill number based on querying the mapping relationship between the GUTI and the number (IMSI), which leads to a high error rate in number backfilling. When the identity identifier is obtained, the integrity of the key to be verified and the data acquisition request is checked based on the target key verification method corresponding to the identity identifier to obtain the target verification result, thereby achieving the effect of verifying the initially obtained identity identifier. When the target verification result is consistent with the preset verification result, the obtained identity identifier is used as the target backfill result to implement number backfilling, greatly improving the accuracy of the backfill result determination and achieving the technical effect of improving the accuracy of number backfilling.

[0072] On the basis of the above device, optionally, the to-be-verified key determination module 210 includes an identity identification acquisition method determination unit, an identity identification determination unit and a to-be-verified key determination unit.

[0073] an identity identification acquisition mode determination unit, configured to receive at least one data acquisition request sent by a target communication device and determine an identity identification acquisition mode corresponding to each data acquisition request;

[0074] An identity identification determination unit, configured to obtain an identity identification corresponding to each data acquisition request based on the identity identification acquisition method;

[0075] The key-to-be-verified determining unit is configured to retrieve and obtain the corresponding key to be verified from the key mapping relationship table based on the identity identifier.

[0076] Based on the above device, optionally, the target key verification mode determination module 220 includes an identification type determination unit and a target key verification mode determination unit.

[0077] An identification type determining unit, configured to determine the identification type of the identity corresponding to each data acquisition request according to the identification acquisition method corresponding to each data acquisition request; wherein the identification type includes a definite identification and an indefinite identification;

[0078] The target key verification mode determination unit is used to determine the target key verification mode based on the authentication feedback data corresponding to the data acquisition request if the identification type is a definite identification; or to determine the target key verification mode based on the data acquisition request and the key to be verified if the identification type is an uncertain identification.

[0079] On the basis of the above device, optionally, the identification type determination unit includes an identity identification acquisition mode division subunit and an identification type determination subunit.

[0080] The identity identification acquisition method classification subunit is used to classify the identity identification acquisition methods corresponding to each data acquisition request into a determined identity identification acquisition method and an uncertain identity identification acquisition method;

[0081] The identification type determination subunit is used to determine that the identification type of the identity is a definite identification if the identity identification acquisition method is a definite identity identification acquisition method; or to determine that the identification type of the identity is an indefinite identification if the identity identification acquisition method is an indefinite identity identification acquisition method.

[0082] On the basis of the above device, optionally, the identification type is a determination identification, and the target verification result acquisition module 230 includes an authentication feedback data receiving unit and a target verification result determination unit.

[0083] An authentication feedback data receiving unit, configured to receive authentication feedback data corresponding to a data acquisition request;

[0084] The target verification result determining unit is configured to determine whether verification success is a target verification result if the feedback result in the authentication feedback data is consistent with a preset feedback result.

[0085] On the basis of the above device, optionally, the identification type is an uncertain identification, and the target verification result acquisition module 230 includes a to-be-verified data determination unit and a target verification result determination unit.

[0086] a data to be verified determining unit, configured to convert the key to be verified to obtain data to be verified;

[0087] The target verification result determining unit is used to determine the target verification result based on the data to be verified and the command message in the data acquisition request.

[0088] Optionally, the target backfill result acquisition module 240 includes a preset verification result determination unit and a target backfill result determination unit.

[0089] A preset verification result determining unit, configured to determine, if the feedback result in the authentication feedback data is consistent with the preset feedback result, that the target verification result is the preset verification result; or, if the data to be verified is consistent with the field data at a preset position in the command message, that the target verification result is the preset verification result;

[0090] The target backfill result determining unit is configured to use the identity identifier corresponding to the data acquisition request as the target backfill result.

[0091] The data processing device provided by the embodiment of the present invention can execute the data processing method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0092] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the embodiments of the present invention.

[0093] Example 4

[0094] Figure 3 This is a structural diagram of an electronic device provided in Example 4 of the present invention. Figure 3 A block diagram of an exemplary electronic device 30 suitable for implementing exemplary embodiments of the present invention is shown. Figure 3 The electronic device 30 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0095] like Figure 3 As shown, electronic device 30 is a general-purpose computing device. Components of electronic device 30 may include, but are not limited to, one or more processors or processing units 301, system memory 302, and a bus 303 connecting various system components (including system memory 302 and processing unit 301).

[0096] Bus 303 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0097] The electronic device 30 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 30, including volatile and non-volatile media, removable and non-removable media.

[0098] System memory 302 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 304 and / or cache memory 305. Electronic device 30 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 306 may be used to read and write non-removable, non-volatile magnetic media ( Figure 3 Not shown, often called a "hard drive"). Although Figure 3 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 303 via one or more data medium interfaces. Memory 302 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of various embodiments of the present invention.

[0099] A program / utility 308 having a set (at least one) of program modules 307 may be stored, for example, in memory 302. Such program modules 307 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may include an implementation of a network environment. Program modules 307 generally implement the functions and / or methods of the embodiments described herein.

[0100] The electronic device 30 may also communicate with one or more external devices 309 (e.g., keyboard, pointing device, display 310, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 30, and / or any device that enables the electronic device 30 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 311. Furthermore, the electronic device 30 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 312. As shown, the network adapter 312 communicates with other modules of the electronic device 30 via the bus 303. It should be understood that although Figure 3Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 30, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0101] The processing unit 301 executes various functional applications and data processing by running programs stored in the system memory 302, such as implementing the data processing method provided by the embodiment of the present invention.

[0102] Example 5

[0103] A fifth embodiment of the present invention further provides a storage medium containing computer-executable instructions, wherein the computer-executable instructions, when executed by a computer processor, are used to perform a data processing method. The method includes:

[0104] Determine the key to be verified corresponding to each received data acquisition request according to a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key to be selected;

[0105] Determine the target key authentication method based on the authentication type corresponding to the data acquisition request;

[0106] Verify the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result;

[0107] If the target verification result is consistent with the preset verification result, backfill processing is performed on the identity identifier corresponding to the data acquisition request to obtain a target backfill result.

[0108] The computer storage medium of the embodiment of the present invention may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device.

[0109] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0110] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0111] The computer program code for performing the operations of the embodiments of the present invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0112] Note that the above are only preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments and may include many other equivalent embodiments without departing from the concept of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data processing method, characterized in that: include: Determine the key to be verified corresponding to each received data acquisition request according to a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key to be verified; Determining a target key verification method based on an identity identifier corresponding to a data acquisition request includes: determining an identification type of an identity identifier corresponding to the data acquisition request based on an identity identifier acquisition method corresponding to each data acquisition request; wherein the identification type includes a definite identification and an indefinite identification; Based on each target key verification method, the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request are verified to obtain a target verification result, including: The identification type is a confirmed identification, and authentication feedback data corresponding to the data acquisition request is received; if the feedback result in the authentication feedback data is consistent with the preset feedback result, the verification success is taken as the target verification result; wherein the authentication feedback data is the authentication result after the identity identifier is authenticated; The identifier type is an uncertain identifier, the key to be verified is converted to obtain data to be verified; based on the data to be verified and the command message in the data acquisition request, a target verification result is determined; wherein the target verification result is a result obtained by comparing the data to be verified with a field at a preset position in the non-access stratum message in the command message; If the target verification result is consistent with the preset verification result, backfill processing is performed on the identity identifier corresponding to the data acquisition request to obtain a target backfill result.

2. The method according to claim 1, characterized in that The step of determining the key to be verified corresponding to each received data acquisition request according to the pre-established key mapping relationship table includes: receiving at least one data acquisition request sent by a target communication device, and determining an identity acquisition method corresponding to each data acquisition request; Based on the identity identification acquisition method, obtain the identity identification corresponding to each data acquisition request; Based on the identity identifier, the corresponding key to be verified is retrieved from the key mapping relationship table.

3. The method according to claim 1, characterized in that The determining of the target key verification method according to the identity identifier corresponding to the data acquisition request includes: If the identification type is a confirmation identification, then determining the target key verification method based on the authentication feedback data corresponding to the data acquisition request; or, If the identification type is an uncertain identification, a target key verification method is determined based on the data acquisition request and the key to be verified.

4. The method according to claim 3, characterized in that The determining of the identification type of the identity corresponding to each data acquisition request according to the identification acquisition method corresponding to each data acquisition request includes: The identity identification acquisition method corresponding to each data acquisition request is divided into a determined identity identification acquisition method and an uncertain identity identification acquisition method; If the identity identification acquisition method is a confirmed identity identification acquisition method, the identification type of the identity identification is a confirmed identification; or, If the identity identification acquisition method is an uncertain identity identification acquisition method, the identification type of the identity identification is an uncertain identification.

5. The method according to claim 1, wherein If the target verification result is consistent with the preset verification result, backfill processing is performed on the identity identifier corresponding to the data acquisition request to obtain a target backfill result, including: If the feedback result in the authentication feedback data is consistent with the preset feedback result, the target verification result is the preset verification result; or, If the data to be verified is consistent with the field data at the preset position in the command message, the target verification result is the preset verification result; The identity identifier corresponding to the data acquisition request is used as the target backfill result.

6. A data processing device, characterized in that: include: A key-to-be-verified determination module, configured to determine the key-to-be-verified corresponding to each received data acquisition request based on a pre-established key mapping relationship table; wherein the key mapping relationship table includes an identity identifier and a corresponding key-to-be-verified; a target key verification mode determination module, configured to determine a target key verification mode according to a verification type corresponding to a data acquisition request; The target key verification mode determination module includes: An identification type determining unit, configured to determine the identification type of the identity corresponding to each data acquisition request according to the identification acquisition method corresponding to each data acquisition request; wherein the identification type includes a definite identification and an indefinite identification; A target verification result acquisition module is used to verify the corresponding data acquisition request, the key to be verified, and the authentication feedback data corresponding to the data acquisition request based on each target key verification method to obtain a target verification result; The identification type is a confirmation identification, and the target verification result acquisition module includes: An authentication feedback data receiving unit, configured to receive authentication feedback data corresponding to a data acquisition request; a target verification result determining unit, configured to determine a successful verification as a target verification result if the feedback result in the authentication feedback data is consistent with a preset feedback result; wherein the authentication feedback data is an authentication result after authenticating the identity identifier; The identification type is an uncertain identification, and the target verification result acquisition module includes: a data to be verified determining unit, configured to convert the key to be verified to obtain data to be verified; a target verification result determining unit, configured to determine a target verification result based on the data to be verified and the command message in the data acquisition request; wherein the target verification result is a result obtained by comparing the data to be verified with a field at a preset position in the non-access stratum message in the command message; The target backfill result acquisition module is used to perform backfill processing on the identity identifier corresponding to the data acquisition request if the target verification result is consistent with the preset verification result to obtain the target backfill result.

7. An electronic device, characterized in that: The device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the data processing method according to any one of claims 1 to 5 is implemented.

Images