Mobile phone number batch updating method, device, equipment, medium and product

Abstract

The invention discloses a mobile phone number batch updating method, device and equipment, a medium and a product, and relates to the technical field of financial science and technology. The mobile phone number batch updating method comprises the following steps: collecting target association relationship data of mobile phone numbers and financial service systems according to an RPA technology; verifying the corresponding new and old mobile phone numbers according to the target association relationship data and the client identity; and after the new and old mobile phone numbers pass the verification, automatically updating the client mobile phone number in each financial service system based on manual verification or an authorized mobile phone number automatic updating service. According to the technical scheme provided by the embodiment of the invention, the mobile phone numbers of clients under various financial service systems can be automatically updated in batches, the labor cost is greatly reduced, and the situation that the mobile phone numbers are not updated can be effectively avoided.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a method, device, equipment, medium and product for batch updating of mobile phone numbers. Background Art

[0002] There are hundreds of business processing information systems (hereinafter referred to as business systems) in continuous operation in the data centers of large financial enterprises, providing customers with various financial business service functions. Among them, mobile phone numbers, as key customer information, are widely used in business scenarios related to financial services, such as customer online login, account change notifications, business processing process and result notifications, business system upgrades or shutdown announcements, and promotional event notifications. It is necessary to communicate with customers through mobile phone numbers.

[0003] However, due to historical reasons, customer mobile phone numbers are not stored as the main data source in each business system, but are stored in different business systems. When a customer's mobile phone number changes, how to synchronize and update the mobile phone numbers in multiple business systems in a timely, automatic and efficient manner has become a current problem. Summary of the invention

[0004] The present invention provides a method, device, equipment, medium and product for batch updating of mobile phone numbers to solve the current problem that mobile phone numbers in multiple financial services cannot be updated synchronously and efficiently.

[0005] According to one aspect of the present invention, a method for updating mobile phone numbers in batches is provided, comprising:

[0006] Based on RPA technology, collect data on the target association between mobile phone numbers and various financial business systems;

[0007] Verify the corresponding new and old mobile phone numbers based on the target association data and customer identity;

[0008] After the new and old mobile phone numbers are verified, the customer's mobile phone numbers in various financial business systems are automatically updated based on manual verification or automatic update services for authorized mobile phone numbers.

[0009] According to another aspect of the present invention, there is provided a device for updating mobile phone numbers in batches, comprising:

[0010] The data collection module is used to collect the target association relationship data between mobile phone numbers and various financial business systems based on RPA technology;

[0011] The mobile phone number verification module is used to verify the corresponding new and old mobile phone numbers based on the target association relationship data and customer identity;

[0012] The mobile phone number automatic update module is used to automatically update the customer's mobile phone number in each financial business system based on manual verification or authorized mobile phone number automatic update service after the new and old mobile phone numbers are verified.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] at least one processor; and

[0015] a memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for batch updating of mobile phone numbers described in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for batch updating of mobile phone numbers described in any embodiment of the present invention when executed.

[0018] According to another aspect of the present invention, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the method for batch updating of mobile phone numbers described in any embodiment of the present invention is implemented.

[0019] The technical solution of the embodiment of the present invention collects the target association relationship data between the mobile phone number and each financial business system based on the RPA technology, thereby verifying the corresponding old and new mobile phone numbers based on the target association relationship data and the customer identity, and then automatically updating the customer's mobile phone number in each financial business system based on manual verification or the automatic update service of the authorized mobile phone number after the new and old mobile phone numbers are verified. In this solution, RPA technology is used to replace manual processing of a large number of repetitive, fixed-rule, complex and cumbersome process tasks, automatically collect target association relationship data, reduce the labor cost of collecting target association relationship data, provide a reliable data basis for the verification of the new and old mobile phone numbers of customers, and finally automatically update the customer's mobile phone number in multiple financial business systems, solving the current problem of being unable to efficiently and synchronously update mobile phone numbers in multiple financial services, and can enable automatic batch updates of customer mobile phone numbers under various financial business systems, greatly reducing labor costs, and effectively avoiding the situation where mobile phone numbers are missed from being updated.

[0020] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 A flowchart of a method for updating mobile phone numbers in batches provided in Embodiment 1 of the present invention;

[0023] Figure 2 A flowchart of a method for updating mobile phone numbers in batches provided in Embodiment 2 of the present invention;

[0024] Figure 3 A schematic diagram of the structure of a mobile phone number batch update system provided in Embodiment 3 of the present invention;

[0025] Figure 4 A schematic diagram of the structure of a batch update server provided in Embodiment 3 of the present invention;

[0026] Figure 5 A schematic diagram of a batch update server execution process provided in Embodiment 3 of the present invention;

[0027] Figure 6 A schematic diagram of the structure of a business system management unit provided in Embodiment 3 of the present invention;

[0028] Figure 7 A schematic diagram of a processing flow of a business system management unit provided in Embodiment 3 of the present invention;

[0029] Figure 8 A schematic diagram of the structure of a mobile phone number scanning and marking unit provided in Embodiment 3 of the present invention;

[0030] Fig. 9 A schematic diagram of a processing flow of a mobile phone number scanning and marking unit provided in Embodiment 3 of the present invention;

[0031] Fig.10 A schematic diagram of the structure of a mobile phone number verification unit provided in Embodiment 3 of the present invention;

[0032] Fig.11 A schematic diagram of a processing flow of a mobile phone number verification unit provided in Embodiment 3 of the present invention;

[0033] Fig.12 A schematic diagram of the structure of a batch change unit provided in Embodiment 3 of the present invention;

[0034] Fig.13 A structural diagram of a report unit provided in Embodiment 3 of the present invention;

[0035] Fig.14 A schematic diagram of the structure of a mobile phone number batch updating device provided in Embodiment 4 of the present invention;

[0036] Fig.15 A schematic diagram of the structure of an electronic device that can be used to implement an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0038] It should be noted that the term "target" and the like in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0039] Embodiment 1

[0040] Figure 1 This is a flowchart of a method for batch updating of mobile phone numbers provided in the first embodiment of the present invention. This embodiment can be applied to the case of efficiently batch updating the mobile phone numbers of customers in a financial service system. The method can be executed by a batch updating device for mobile phone numbers. The batch updating device for mobile phone numbers can be implemented in the form of hardware and / or software. The batch updating device for mobile phone numbers can be configured in an electronic device. Figure 1 As shown, the method includes:

[0041] Step 110: Based on RPA technology, collect target association relationship data between mobile phone numbers and various financial business systems.

[0042] Among them, RPA (Robotic Process Automation) is a business processing automation technology based on software robots and artificial intelligence, which simulates manual operations. The target association data can be data describing the association between financial services and customer mobile phone numbers.

[0043] In an embodiment of the present invention, based on RPA technology, business-related content including customer mobile phone numbers in a financial business system can be scanned, and by analyzing the business-related content including customer mobile phone numbers, target association relationship data between mobile phone numbers and various financial business systems can be determined.

[0044] Step 120: Verify the corresponding new and old mobile phone numbers according to the target association relationship data and the customer identity.

[0045] In an embodiment of the present invention, after receiving a mobile phone number update application submitted by at least one customer, the customer identity of the customer who sent the mobile phone number update application and the old and new mobile phone numbers under the customer's name are determined, so as to verify the corresponding old and new mobile phone numbers in each financial business system using the target association relationship data and the determined customer identity.

[0046] Step 130: After the old and new mobile phone numbers are verified, the customer's mobile phone number is automatically updated in each financial service system based on manual verification or the authorized mobile phone number automatic update service.

[0047] Among them, the authorized mobile phone number automatic update service can be a financial service authorized by the customer to automatically update the new mobile phone number under the customer's name.

[0048] Specifically, after the customer's identity is successfully verified through the old and new mobile phone numbers, the managers of each financial business system can log in to the financial business systems under their jurisdiction to review and approve the customer's mobile phone number update, and automatically update the customer's mobile phone number in each financial business system that has passed the approval. Alternatively, based on the authorized mobile phone number automatic update service, the customer's mobile phone number in each financial business system can be automatically updated, that is, the customer's new number can be updated and registered.

[0049] The technical solution of the embodiment of the present invention collects the target association relationship data between the mobile phone number and each financial business system based on the RPA technology, thereby verifying the corresponding old and new mobile phone numbers based on the target association relationship data and the customer identity, and then automatically updating the customer's mobile phone number in each financial business system based on manual verification or the automatic update service of the authorized mobile phone number after the new and old mobile phone numbers are verified. In this solution, RPA technology is used to replace manual processing of a large number of repetitive, fixed-rule, complex and cumbersome process tasks, automatically collect target association relationship data, reduce the labor cost of collecting target association relationship data, provide a reliable data basis for the verification of the new and old mobile phone numbers of customers, and finally automatically update the customer's mobile phone number in multiple financial business systems, solving the current problem of being unable to efficiently and synchronously update mobile phone numbers in multiple financial services, and can enable automatic batch updates of customer mobile phone numbers under various financial business systems, greatly reducing labor costs, and effectively avoiding the situation where mobile phone numbers are missed from being updated.

[0050] Embodiment 2

[0051] Figure 2 This is a flowchart of a method for batch updating of mobile phone numbers provided in Example 2 of the present invention. This example is specific based on the above example and provides a specific optional implementation method for collecting target association relationship data between mobile phone numbers and various financial business systems based on RPA technology. Figure 2 As shown, the method includes:

[0052] Step 210: Based on RPA technology, log in to each financial business system in turn and scan the customer mobile phone numbers stored in each financial business system.

[0053] In an embodiment of the present invention, based on RPA technology, each financial service system can be logged in in turn, and the financial service related content of the registered mobile phone number can be scanned to obtain the customer mobile phone number stored in each financial service system.

[0054] Step 220: Obtain target association relationship data based on the association relationship between the customer mobile phone numbers stored in each financial business system and the corresponding financial business system.

[0055] In an embodiment of the present invention, the customer mobile phone numbers stored in various financial business systems and the correspondence between the customer mobile phone numbers and the stored financial business systems, that is, the association relationship between the customer mobile phone numbers stored in each financial business system and the corresponding financial business system, can be collected using RPA technology to generate target association relationship data.

[0056] Step 230: Verify the corresponding new and old mobile phone numbers according to the target association relationship data and the customer identity.

[0057] In an optional embodiment of the present invention, verifying the corresponding new and old mobile phone numbers based on the target association relationship data and the customer identity may include: matching and verifying the target association relationship data based on the mobile phone number information recorded in the database of each financial business system and / or the mobile phone number information in the transaction log to obtain verified association relationship data; verifying the corresponding new and old mobile phone numbers based on the verified association relationship data and the customer identity.

[0058] The transaction log may be a way of recording detailed transaction information. The verified association relationship data may be association relationship data in the target association relationship data that has passed matching verification.

[0059] In an embodiment of the present invention, the mobile phone number information recorded in the database of each financial business system can be queried through a general database query interface based on RPA technology, and the mobile phone number information in the transaction log of each financial business system can be collected through a transaction log query interface based on RPA technology, so as to match and verify the target association relationship data according to the mobile phone number information recorded in the database of each financial business system, and / or, match and verify the target association relationship data according to the mobile phone number information in the transaction log of each financial business system, and further use the verified data in the target association relationship data as the verified association relationship data, so as to verify the corresponding new and old mobile phone numbers using the verified association relationship data and the customer identity. By verifying the target association relationship data, the accuracy of the association relationship between the mobile phone number in the verified association relationship data and each financial business system is guaranteed, and a reliable data basis is provided for the verification of new and old mobile phone numbers.

[0060] In an optional embodiment of the present invention, the corresponding old and new mobile phone numbers are verified based on the verified association relationship data and the customer identity, which can include: initial verification of the old mobile phone number based on the old mobile phone number and the customer identity of the customer in the pending customer application list, and initial verification of the new mobile phone number based on the new mobile phone number and the customer identity of the customer in the pending customer application list; based on the verified association relationship data, the association relationship between the old mobile phone number of the customer in the pending customer application list and the business system is verified.

[0061] The pending customer application list may be a list of customers who have submitted applications for updating their mobile phone numbers.

[0062] In an embodiment of the present invention, the customer in the list of pending customer applications can be identified, so as to determine the old mobile phone number and customer identity of the customer in the list, and use the customer identity to perform an initial verification of the old mobile phone number under the name of the corresponding customer (i.e., confirm whether the old mobile phone number under the name of the customer is consistent with the mobile phone number of the corresponding customer under the financial business system), and then use the customer identity in the list to perform an initial verification of the new mobile phone number of the corresponding customer (i.e., confirm whether the new mobile phone number under the name of the customer actually exists), and further verify the association relationship between the old mobile phone number of the customer in the list of pending customer applications and the business system based on the verified association relationship data, that is, determine whether the binding relationship between the old mobile phone number of the customer recorded under the financial business and the financial business exists. By verifying the customer's new mobile phone number, old mobile phone number, and the association relationship between the customer's old mobile phone number and the business system, the accuracy of subsequent mobile phone number updates can be effectively guaranteed.

[0063] Exemplarily, the list of pending customer applications is read, and each customer in the list is authenticated to ensure that the operation is performed by the customer himself. The telecommunications operator is used to feedback whether the current customer's old mobile phone number belongs to the customer himself, and whether the new mobile phone number belongs to the customer himself. When it is determined that the old and new mobile phone numbers are the real mobile phone numbers under the name of the current customer, the old and new mobile phone numbers are detected to be present in the verified association relationship data, and it is determined whether all customers in the pending customer application list have been processed. If not, the above process is performed on the next customer. After the verification of the new and old mobile phone numbers of all customers in the pending customer application list is completed, the new and old mobile phone number verification process is terminated. The new and old mobile phone number verification process can call the RPA robot, enable multi-threaded parallel working mode, and verify the new and old mobile phone numbers of a customer by one thread.

[0064] In an optional embodiment of the present invention, before performing the initial verification of the old mobile phone number based on the old mobile phone number and customer identity of the customer in the pending customer application list, it may also include: verifying the customer identity of the customer in the pending customer application list; and eliminating customer applications in the pending customer application list whose customer identity authentication failed.

[0065] In the embodiment of the present invention, each customer who has submitted a mobile phone number update application in the pending customer application list can be determined, and the customer identity of each of the aforementioned customers can be further verified, and customers who have failed the identity verification can be removed from the pending customer application list. That is, by verifying the identity of the customer in the pending customer application list, the validity of the subsequent mobile phone number update can be ensured.

[0066] Step 240: After the old and new mobile phone numbers are verified, the customer's mobile phone number is automatically updated in each financial service system based on manual verification or the authorized mobile phone number automatic update service.

[0067] In an optional embodiment of the present invention, automatic updating of customer mobile phone numbers in various financial business systems based on manual verification or authorized mobile phone number automatic update services may include: determining a list of customer mobile phone numbers to be updated based on manual verification or authorized mobile phone number automatic update services; and batch updating of customer mobile phone numbers in various financial business systems according to the list of customer mobile phone numbers to be updated using RPA technology.

[0068] The list of customer mobile phone numbers to be updated may be a list of pending customer applications, and a list of changes in mobile phone number associated information of customers whose new and old mobile phone numbers have passed verification.

[0069] In the embodiment of the present invention, based on manual verification or authorized mobile phone number automatic update service, the customer mobile phone number to be updated list can be determined, and then RPA technology can be used to batch update the customer mobile phone numbers in each financial business system according to the financial business system, the customer's old mobile phone number and the customer's new mobile phone number in the customer mobile phone number to be updated list. Batch updating of customer mobile phone numbers in various financial business systems through RPA technology greatly alleviates the pressure of manual work, effectively improves work efficiency, and avoids the occurrence of missed updates.

[0070] The technical solution of the embodiment of the present invention is based on RPA technology, and logs in to each financial business system in turn, and scans the customer mobile phone numbers stored in each financial business system, thereby obtaining target association relationship data according to the association relationship between the customer mobile phone numbers stored in each financial business system and the corresponding financial business system, and further verifies the corresponding new and old mobile phone numbers according to the target association relationship data and the customer identity, so that after the new and old mobile phone numbers are verified, the customer mobile phone numbers in each financial business system are automatically updated based on manual verification or authorized mobile phone number automatic update service. In this solution, RPA technology is used to replace manual scanning of customer mobile phone numbers stored in each financial business system, so as to create target association relationship data based on the stored customer mobile phone numbers, while reducing labor costs, it can also greatly improve the accuracy and effectiveness of target association relationship data, provide a reliable data basis for the verification of the new and old mobile phone numbers of customers, and finally automatically update the customer mobile phone numbers in multiple financial business systems, solving the current problem that the mobile phone numbers in multiple financial services cannot be updated efficiently and synchronously, and can enable the customer mobile phone numbers under each financial business system to be automatically updated in batches, greatly reducing labor costs, and effectively avoiding the situation where the mobile phone numbers are missed.

[0071] It should be noted that the information collected by this plan is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0072] Embodiment 3

[0073] This embodiment is based on the above embodiment and introduces a mobile phone number batch update system. The specific content is as follows:

[0074] In a specific example, the mobile phone number batch update system may include multiple batch update servers and various financial business systems. The mobile phone number batch update system structure is shown in Figure 3 The method for batch updating of mobile phone numbers is configured in the batch updating server.

[0075] like Figure 4 As shown, the batch update server includes a business system management unit, a mobile phone number scanning and marking unit, a mobile phone number verification unit, a batch change unit and a report unit.

[0076] The process of batch update server execution is as follows: through the business system management unit, maintain the basic access information of each financial business system, through the mobile phone number scanning and marking unit, scan and establish the relationship between the customer's mobile phone number and the financial business system, and through the mobile phone number verification unit, perform relevant verification on the customer's identity and the old and new mobile phone numbers, and then through the batch change unit, complete the automatic update of the customer's mobile phone number in each financial business system, so as to manage and display the processing logs and statistical reports of the above processing flow links through the report unit, including the real-time operation status and historical operation result information of each link, and statistical analysis information, so as to provide reference for decision-making by financial business system managers. For details of the process of batch update server execution, please refer to Figure 5 .

[0077] For the detailed structure of the business system management unit, see Figure 6 ,like Figure 6 As shown, the business system management unit is composed of a business system information maintenance subunit and a business system information storage subunit.

[0078] The business system information maintenance subunit is used to maintain the basic access information of each financial business system, including the business system number, name, access address, database access information, transaction log access information, etc. The business system information storage subunit stores the basic access information maintained by the business system information maintenance unit.

[0079] The processing flow of the business system management unit is for business managers to maintain the basic access information of each financial business system. After the above maintenance operations are completed, the relevant information is saved to the business system information storage subunit. Optionally, the financial business manager can maintain the basic access information of the financial business system under management. The financial business manager can query, add, modify, delete and other operations on the basic access information stored in the financial business system under management. For the flowchart corresponding to the processing flow of the business system management unit, see Figure 7 .

[0080] For detailed structure of mobile phone number scanning and marking unit, see Figure 8 ,like Figure 8 As shown, the mobile phone number scanning and marking unit is composed of a metadata scanning subunit, a business system access subunit, a business system scanning and verification subunit, and a scanning and verification result storage subunit. The mobile phone number scanning and marking unit is used to collect metadata information, databases and log information from different channels and structures of various financial business systems, and form a centralized storage with a unified format for the associated information of mobile phone numbers contained in various financial business systems.

[0081] The metadata scanning sub-unit scans the content including mobile phone numbers in various financial business systems through the existing metadata management system (which saves the table structure, transaction logs and other basic metadata of each business system), and establishes the target association relationship data between mobile phone numbers and each financial business system. The content generated after scanning includes: business system name, storage type (database or file), data type (table or transaction log), table or file name, mobile phone number field and other structural information.

[0082] The business system access subunit interacts with the business system management unit to read the configuration information of each financial business system stored therein (basic access information such as databases and transaction logs).

[0083] The business system scanning and verification sub-unit logs in to each financial business system through the RPA robot, or RPA calls the automated query interface provided by each business system to collect the target association relationship data between the mobile phone number and the financial business system, and searches the corresponding production data (database tables and transaction logs) of each financial business system in turn. RPA performs data query, text analysis, and matching to obtain the corrected target association relationship data, that is, the verified association relationship data, to indicate that the relevant mobile phone number actually exists in the corresponding financial business system and has actual business significance.

[0084] Exemplarily, the business system scanning and verification sub-unit includes a database scanning and verification sub-unit and a transaction log verification sub-unit. Database scanning and verification sub-unit: RPA uses the general database query interface to scan the customer mobile phone number information recorded in all databases in each business system, and collects the target association relationship data for matching and verification. Transaction log verification sub-unit: RPA uses the transaction log query interface provided by each business system to collect the customer mobile phone number information in all transaction logs in each business system, and matches and verifies it with the target association relationship data.

[0085] The scanning and verification result storage subunit stores the verification passing association relationship data after unified processing by the business system scanning and verification subunit.

[0086] For the processing flow of mobile phone number scanning and labeling unit, see Fig. 9 ,like Fig. 9 As shown, the metadata scanning subunit is used to scan the relevant content of the bound mobile phone number in each financial business system, establish the target association relationship data between the customer mobile phone number and the financial business system, and loop through the business system access subunit to connect and access the financial business system. Further, the RPA robot is used to log in to each financial business system in turn, and the automatic query interface provided by each financial business system is called to collect the customer mobile phone numbers stored in each financial business system. For example, the mobile phone number information recorded in the database of each financial business system and the mobile phone number information recorded in the transaction log are obtained through RPA. Further, based on the mobile phone number information recorded in the database and the mobile phone number information recorded in the transaction log, the target association relationship data is verified, and the verified target association relationship data is saved, so as to determine whether the verification of the association relationship data between all financial business systems and mobile phone numbers is completed. If the processing is completed, the association relationship data verification process is terminated. If the processing is not completed, the processing is continued until the verification of the association relationship data between all financial business systems and mobile phone numbers is completed.

[0087] For the detailed structure of the mobile phone number verification unit, see Fig.10 ,like Fig.10 As shown, the mobile phone number verification unit is composed of a customer identity verification subunit, an old mobile phone number verification subunit, a new mobile phone number verification subunit, an old mobile phone number detection subunit, and a new mobile phone number detection subunit. The mobile phone number verification unit is used to verify the legitimacy of the customer and the mobile phone number, and analyze and verify the association relationship information between the old and new mobile phone numbers in each business system.

[0088] The mobile phone number verification unit is composed of a customer identity verification subunit, an old mobile phone number verification subunit, a new mobile phone number verification subunit, an old mobile phone number detection subunit, and a new mobile phone number detection subunit. The customer identity verification subunit is used to identify and verify the customer's mobile phone number change operation to ensure that it is operated by the customer himself. The old mobile phone number verification unit determines whether the old mobile phone number belongs to the customer himself based on the feedback from the telecommunications operator interface. The new mobile phone number verification unit determines whether the new mobile phone number belongs to the customer himself based on the feedback from the telecommunications operator interface. The old mobile phone number detection unit detects whether the old mobile phone number exists in the target association relationship data. The new mobile phone number detection unit detects whether the new mobile phone number exists in the target association relationship data.

[0089] The mobile phone number verification unit processing flow is as follows Fig.11 As shown, the pending customer application list is read, and the current customer in the list is identified and verified to ensure that the operation is performed by the customer himself. The old mobile phone number verification unit determines whether the old mobile phone number belongs to the customer himself based on the feedback from the telecommunications operator interface. The new mobile phone number verification unit determines whether the new mobile phone number belongs to the customer himself based on the feedback from the telecommunications operator interface. The old mobile phone number detection unit detects whether the old mobile phone number exists in the target association relationship data. The new mobile phone number detection unit detects whether the new mobile phone number exists in the target association relationship data. It is determined whether all pending customers have been processed. If not, the processing of the next customer is continued, that is, the operation of identifying and verifying the current customer in the list is returned. If completed, the overall process ends.

[0090] The above customer identity verification subunit, old mobile phone number verification subunit, new mobile phone number verification subunit, old mobile phone number detection subunit, and new mobile phone number detection subunit call the RPA robot and enable multi-threaded parallel working mode. Each type of thread processes one customer data.

[0091] For the detailed structure of the batch change unit, see Fig.12 ,like Fig.12 As shown, the batch change unit consists of a change task generation subunit, a batch approval subunit, a batch update subunit, a notification subunit, and a log subunit. The batch change unit is used to batch change the customer mobile phone numbers in each business system, notify the administrators of each business system by email, and record the log.

[0092] The change task generation subunit is used to generate a list of pending customer applications based on the verified association relationship data, and to notify the administrators of each financial business system by email. The pending customer application list may include information such as business system, storage type, table or file name, old mobile phone number, new mobile phone number, and pending updates. The batch approval subunit is used for the pending customer application list to be approved by the administrator of each business system, and the list status is updated after the approval is completed, such as passed or rejected. The batch update subunit is used to call RPA to automatically update the mobile phone numbers in batches for the pending customer application list, and complete the automatic update of the customer's mobile phone numbers in various financial business systems. The notification subunit is used to notify the administrators and customers of each business system after the batch update is completed. The log subunit is used to record the process information logs generated in each process.

[0093] The detailed structure of the report unit is as follows Fig.13 As shown, Fig.13 The report unit shown is composed of business system report sub-unit, mobile phone number scanning report sub-unit, and batch change result report sub-unit. The relevant details and statistical information of the aforementioned units can be output for customers to query detailed information of each link.

[0094] The business system report sub-unit mainly counts and displays the processing status of the mobile phone number scanning and labeling unit (business system number, name, access address, database access information, transaction log access information, etc.), and records the process information generated by each process in the mobile phone number scanning and labeling unit.

[0095] The mobile phone number scanning report sub-unit mainly counts and displays the processing status of the mobile phone number scanning and annotation unit, including the relationship between the mobile phone number and the business system, such as the business system, storage type, data type, table or file name, mobile phone number field and other information.

[0096] The batch change result report sub-unit mainly counts and displays the processing status of the batch change unit, including change task generation and approval status, batch update status and other information.

[0097] There are hundreds of business systems in the data centers of large financial enterprises. The customer mobile phone number information recorded and saved in each financial business system has large differences in storage methods, data formats, and usage methods. Each financial business system requires a lot of manpower. This system makes full use of RPA robots to replace manual processing, greatly saving the cost of repeated verification, approval, and update of new and old numbers in each business system. Through this system, the access information and scanning verification rules of each financial business system are configured, and the RPA robot can automatically update the data of multiple different customer mobile phone numbers in multiple financial business systems in parallel. The overall review efficiency is high, and there will be no omissions. In addition, this system is conducive to the managers of the financial business system to timely understand the operation of each business system and promptly rectify potential risks according to relevant reasons and suggestions.

[0098] Embodiment 4

[0099] Fig.14 This is a schematic diagram of the structure of a mobile phone number batch update device provided by the fourth embodiment of the present invention. Fig.14 As shown, the device comprises:

[0100] The data collection module 310 is used to collect target association relationship data between mobile phone numbers and various financial business systems based on RPA technology;

[0101] The mobile phone number verification module 320 is used to verify the corresponding new and old mobile phone numbers according to the target association relationship data and the customer identity;

[0102] The mobile phone number automatic update module 330 is used to automatically update the customer's mobile phone number in each financial service system based on manual verification or authorized mobile phone number automatic update service after the new and old mobile phone numbers are verified.

[0103] The technical solution of the embodiment of the present invention collects the target association relationship data between the mobile phone number and each financial business system based on the RPA technology, thereby verifying the corresponding old and new mobile phone numbers based on the target association relationship data and the customer identity, and then automatically updating the customer's mobile phone number in each financial business system based on manual verification or the automatic update service of the authorized mobile phone number after the new and old mobile phone numbers are verified. In this solution, RPA technology is used to replace manual processing of a large number of repetitive, fixed-rule, complex and cumbersome process tasks, automatically collect target association relationship data, reduce the labor cost of collecting target association relationship data, provide a reliable data basis for the verification of the new and old mobile phone numbers of customers, and finally automatically update the customer's mobile phone number in multiple financial business systems, solving the current problem of being unable to efficiently and synchronously update mobile phone numbers in multiple financial services, and can enable automatic batch updates of customer mobile phone numbers under various financial business systems, greatly reducing labor costs, and effectively avoiding the situation where mobile phone numbers are missed from being updated.

[0104] Optionally, the data collection module 310 is specifically used to log in to each of the financial business systems in turn based on the RPA technology, and scan the customer mobile phone numbers stored in each of the financial business systems; according to the association relationship between the customer mobile phone numbers stored in each of the financial business systems and the corresponding financial business systems, the target association relationship data is obtained.

[0105] Optionally, the mobile phone number verification module 320 is specifically used to match and verify the target association data according to the mobile phone number information recorded in the database of each financial business system and / or the mobile phone number information in the transaction log, to obtain verified association data; and verify the corresponding new and old mobile phone numbers according to the verified association data and the customer identity.

[0106] Optionally, the mobile phone number verification module 320 is specifically used to perform initial verification of the old mobile phone number based on the old mobile phone number and customer identity of the customer in the pending customer application list, and to perform initial verification of the new mobile phone number based on the new mobile phone number and customer identity of the customer in the pending customer application list; based on the verification through association relationship data, the association relationship between the old mobile phone number of the customer in the pending customer application list and the business system is verified.

[0107] Optionally, the mobile phone number batch update device also includes a customer identity authentication module, which is used to verify the customer identity of the customers in the pending customer application list; and to remove customer applications in the pending customer application list that fail customer identity authentication.

[0108] Optionally, the mobile phone number automatic update module 330 is specifically used to determine a list of customer mobile phone numbers to be updated based on manual verification or authorized mobile phone number automatic update services; and to batch update customer mobile phone numbers in each of the financial business systems according to the list of customer mobile phone numbers to be updated using RPA technology.

[0109] The mobile phone number batch updating device provided in the embodiment of the present invention can execute the mobile phone number batch updating method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0110] Embodiment 5

[0111] Fig.15A schematic diagram of an electronic device that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0112] like Fig.15 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0113] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0114] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a method for updating mobile phone numbers in batches.

[0115] In some embodiments, the method for updating mobile phone numbers in batches may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for updating mobile phone numbers in batches described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the method for updating mobile phone numbers in batches in any other appropriate manner (e.g., by means of firmware).

[0116] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0117] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0118] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 of the foregoing.

[0119] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0120] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0121] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of traditional physical hosts and VPS servers, which are difficult to manage and have weak business scalability.

[0122] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0123] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for updating mobile phone numbers in batches, characterized in that: include: Based on the Robotic Process Automation (RPA) technology, data on the target association between mobile phone numbers and various financial business systems is collected; Verify the corresponding new and old mobile phone numbers based on the target association relationship data and the customer identity; After the verification of the old and new mobile phone numbers is passed, the customer's mobile phone number in each of the financial service systems is automatically updated based on manual verification or the automatic update service of the authorized mobile phone number.

2. The method according to claim 1, characterized in that Based on RPA technology, collect the target association data between mobile phone numbers and various financial business systems, including: Based on the RPA technology, log in to each of the financial business systems in turn and scan the customer mobile phone numbers stored in each of the financial business systems; The target association relationship data is obtained based on the association relationship between the customer mobile phone numbers stored in each of the financial business systems and the corresponding financial business systems.

3. The method according to claim 1, characterized in that According to the target association data and the customer identity, the corresponding new and old mobile phone numbers are verified, including: According to the mobile phone number information recorded in the database of each of the financial business systems and / or the mobile phone number information in the transaction log, the target association relationship data is matched and verified to obtain the verified association relationship data; According to the verification, the corresponding old and new mobile phone numbers are verified through the associated relationship data and the customer identity.

4. The method according to claim 3, characterized in that According to the verification, the corresponding new and old mobile phone numbers are verified through the associated relationship data and the customer identity, including: Performing an initial verification of the old mobile phone number based on the old mobile phone number and the customer identity of the customer in the pending customer application list, and performing an initial verification of the new mobile phone number based on the new mobile phone number and the customer identity of the customer in the pending customer application list; According to the verified association relationship data, the association relationship between the old mobile phone number of the customer in the pending customer application list and the business system is verified.

5. The method according to claim 4, characterized in that Before the initial verification of the old mobile phone number based on the old mobile phone number and the customer identity in the list of pending customer applications, it also includes: Verify the customer identity of the customer in the pending customer application list; Eliminate customer applications whose customer identity authentication fails from the list of pending customer applications.

6. The method according to claim 1, characterized in that Automatically update the customer's mobile phone number in each of the financial service systems based on manual verification or authorized mobile phone number automatic update service, including: Determine the list of customer mobile numbers to be updated based on manual verification or automatic update of authorized mobile numbers; By using RPA technology, the customer mobile phone numbers in each financial business system are updated in batches according to the list of customer mobile phone numbers to be updated.

7. A device for updating mobile phone numbers in batches, characterized in that: include: The data collection module is used to collect the target association relationship data between mobile phone numbers and various financial business systems based on RPA technology; A mobile phone number verification module, used to verify the corresponding new and old mobile phone numbers according to the target association relationship data and the customer identity; The mobile phone number automatic update module is used to automatically update the customer's mobile phone number in each of the financial service systems based on manual verification or authorized mobile phone number automatic update service after the new and old mobile phone numbers are verified.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for batch updating of mobile phone numbers according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for batch updating of mobile phone numbers according to any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the method for batch updating of mobile phone numbers according to any one of claims 1 to 6.

Images