Crown word number management method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses a crown word number management method and device, equipment and a storage medium, and the method comprises the steps: obtaining a target crown word number file; determining a file storage database corresponding to each type of data in the target serial number file based on a preset data storage table; wherein the preset data storage table is used for representing a corresponding relationship between multiple field types and multiple file storage databases; and storing each type of data in the target serial number file into a corresponding file storage database to complete the serial number management process of the target serial number file. According to the technical scheme, the problem that in the prior art, the storage amount of the serial number files is small is solved, the data in the serial number files can be classified, the file storage database corresponding to each kind of data is determined, the data is stored in the corresponding file storage database, and the data storage amount of the serial number files is increased.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of data storage technology, and in particular to a method, apparatus, device and storage medium for managing prefix numbers. Background Art

[0002] The serial number is used to identify a specific banknote and consists of letters and numbers. The existing system is able to quickly match serial numbers to specific transactions, effectively meeting the requirements of the People's Bank of China, public security agencies, procuratorates, and courts. However, it still has limitations in terms of storing and querying large amounts of data, and generally only provides data queries within three months.

[0003] Currently, serial number data for large state-owned banks typically reaches hundreds of millions or even billions of data points daily. Existing solutions use traditional relational databases to store data, which have limited storage capacity and limited database technology, typically storing terabytes of data and resulting in short verification cycles. Summary of the Invention

[0004] The embodiments of the present invention provide a method, device, equipment and storage medium for managing prefix numbers. The technical solution of the embodiments of the present invention solves the problem of small storage capacity of prefix number files in the prior art. The data in the prefix number files can be classified, and the file storage database corresponding to each type of data can be determined, and the data can be stored in the corresponding file storage database, thereby improving the data storage capacity of the prefix number files.

[0005] In a first aspect, an embodiment of the present invention provides a method for managing prefix numbers, the method comprising:

[0006] Obtain a target crown number file; determine the file storage database corresponding to each type of data in the target crown number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; store each type of data in the target crown number file in the corresponding file storage database, thereby completing the crown number management process of the target crown number file.

[0007] In a second aspect, an embodiment of the present invention provides a prefix number management device, the device comprising:

[0008] A crown number file acquisition module is used to obtain a target crown number file; a database determination module is used to determine the file storage database corresponding to each type of data in the target crown number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; a file storage module is used to store each type of data in the target crown number file in the corresponding file storage database, thereby completing the crown number management process of the target crown number file.

[0009] In a third aspect, an embodiment of the present invention provides a computer device, the computer device comprising:

[0010] one or more processors;

[0011] a memory for storing one or more programs;

[0012] When the one or more programs are executed by the one or more processors, the one or more processors implement the method for managing serial numbers described in any embodiment.

[0013] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for managing prefix numbers described in any embodiment.

[0014] The technical solution provided by the embodiment of the present invention obtains a target serial number file; determines the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; and stores each type of data in the target serial number file in the corresponding file storage database, thereby completing the serial number management process of the target serial number file. The technical solution of the embodiment of the present invention solves the problem of small storage capacity of serial number files in the prior art. It can classify the data in the serial number file, determine the file storage database corresponding to each type of data, and store the data in the corresponding file storage database, thereby increasing the data storage capacity of the serial number file. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a flow chart of a method for managing prefix numbers provided by an embodiment of the present invention;

[0016] Figure 2 This is a flow chart of another method for managing prefix numbers provided by an embodiment of the present invention;

[0017] Figure 3 This is a schematic structural diagram of a prefix number management device provided by an embodiment of the present invention;

[0018] Figure 4 It is a structural diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of 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. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0020] Figure 1 This is a flow chart of a method for managing a serial number provided by an embodiment of the present invention. The embodiment of the present invention is applicable to a scenario in which a storage database is determined to be compatible with each type of data in a serial number file. The method can be executed by a serial number management device, which can be implemented by software and / or hardware.

[0021] like Figure 1 As shown, the method for managing serial numbers includes the following steps:

[0022] S110: Obtain the target serial number file.

[0023] The target serial number file may be a serial number file that has been managed by serial number management. Specifically, the original serial number file may be obtained from a front-end banknote counting device, and the original serial number files of each banknote counting device may be aggregated and processed to obtain the target serial number file.

[0024] S120: Determine the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table.

[0025] The preset data storage table is used to represent the correspondence between various field types and various file storage databases. The file storage database may be a database for storing serial numbers. Specifically, the field name corresponding to each type of data in the target serial number file can be extracted. Based on the field name, the field type corresponding to each type of data can be determined from the preset data storage table, and the corresponding file storage database for each type of data in the target serial number file can be determined.

[0026] S130: Each type of data in the target serial number file is stored in a corresponding file storage database, thereby completing the serial number management process of the target serial number file.

[0027] Among them, by storing different types of file data in the corresponding database, the traditional serial number field system data can be upgraded from TB level to PB level, which has the characteristics of wide application scenarios, long tracking cycle and high query efficiency.

[0028] The technical solution provided by the embodiment of the present invention obtains a target serial number file; determines the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; and stores each type of data in the target serial number file in the corresponding file storage database, thereby completing the serial number management process of the target serial number file. The technical solution of the embodiment of the present invention solves the problem of small storage capacity of serial number files in the prior art. It can classify the data in the serial number file, determine the file storage database corresponding to each type of data, and store the data in the corresponding file storage database, thereby increasing the data storage capacity of the serial number file.

[0029] Figure 2 This is another flowchart of a method for managing a serial number provided by an embodiment of the present invention. The embodiment of the present invention can be applied to the scenario of determining the storage database adapted for each type of data in a serial number file. Based on the above embodiment, this embodiment further explains how to obtain the target serial number file; and how to determine the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table. The device can be implemented by software and / or hardware and integrated into a computer device with application development capabilities.

[0030] like Figure 2 As shown, the method for managing serial numbers includes the following steps:

[0031] S210: Obtain an original prefix number file sent by at least one front-end device.

[0032] The front-end device may be a banknote counting device serving at the front end. For example, the front-end device may include: a banknote counting machine at a counter, an all-in-one machine, a super counter, and a sorting machine at a treasury clearing center. The original serial number file may be a serial number file that has not undergone data processing. Specifically, the serial number files sent by the front-end device may be aggregated to obtain the original serial number file. The technical solution of the embodiment of the present invention can perform corresponding data splitting on the original serial number file, and then store the split data in corresponding databases respectively.

[0033] S220. For the non-image files in the original serial number file, the non-image files are format-converted and compressed, and the target serial number file is obtained based on the processed non-image files and the image files in the original serial number file.

[0034] Among them, the original serial number file may include files in picture format and files in other formats. Non-picture files are files that are not in picture format. Picture files are files in picture format. Furthermore, the non-picture files in the original serial number file can be converted into JSON format and then compressed. The target serial number file can be a serial number file after data processing. Specifically, the processed non-picture files and the picture files in the original serial number file can be summarized to obtain the target serial number file. By converting and compressing the non-picture files, and obtaining the target serial number file based on the processed non-picture files and the picture files in the original serial number file, the memory occupied by the target serial number file can be reduced, and the transmission resource occupation of the target serial number file can be reduced.

[0035] For example, after pre-processing at the first-tier branch, the original FSN (prefix number) file is stripped of its image portion. The stripped image can be stored on the front-end file system. Transaction data is converted to JSON format, compressed, and transmitted to the back-end service. This reduces network bandwidth pressure and improves transmission speeds under massive data volumes. This module can be developed and implemented in a variety of ways. The overall development framework can be built using the Java open source framework. The TCP service for receiving FSN data files can be built using various open source TCP components, while the batch service can be built using open source components or implemented using a Linux daemon program. Table 1 shows a comparison of prefix number data resource usage. The FSN format prefix number file has a compression ratio of 5:1. For example, 900 million prefix number data entries for a particular bank on a particular day are compressed to 18GB. The JSON format prefix number file has a compression ratio of 100:1, which reduces the compressed data entry to 2.7GB. A comparison shows that compared to FSN format files, compressed JSON format files save more network bandwidth when uploaded and improve subsequent processing speed. Therefore, this module ultimately uploads only the converted JSON message.

[0036] Table 1 Comparison of resource usage of serial number related data

[0037]

[0038] S230: Identify the field name corresponding to each type of data in the target serial number file.

[0039] The field name can be used to represent the meaning of each data type in the target serial number file. For example, the field name may include: currency verification start date, currency verification start time, error code, version number, and currency symbol. Specifically, the target serial number file can be parsed and the field name corresponding to each data type can be determined based on preset field name extraction rules.

[0040] Optionally, identifying the field name corresponding to each type of data in the target prefix number file includes: parsing the target prefix number file to obtain target message data; extracting the message header name and message body name in the target message data to obtain field names corresponding to multiple data.

[0041] The target message data may be message data obtained by parsing the target serial number file. Specifically, the target message data may be a JSON message in a preset format. The meaning of the elements contained in the message data refers to the provisions of the People's Bank of China's FSN2018 document, and mainly includes two parts of transaction data: the header and the message body. For example, an example of a parsed JSON message is as follows:

[0042] {"appliDenom":"XXXXXXX","authSoftVerNo":"MAIN00XX / TMP00XX","bodyList":[{"charNum":"10","date":"202X0X0X","errorCode":"101010101010101000 101000000010101010000XXXXXXX1","moneyFlag":"XXX","reserve2":"","sNo":"ZM40XXXXX","tfFlag":"1","time":"12XXXX","valuta":"XX00","ver":"3"}, ..................

[0044] ,{"charNum":"10","date":"202X0X0X","errorCode":"1010101010101010001010000000101 01010000XXXXXXX1","moneyFlag":"XXXX","reserve2":"","sNo":"ES3757XXXX","tfFlag": "3","time":"121434","valuta":"100","ver":"3"}],"counter":"103","enableTime":"1903","finanIns":"XXXC","finanInst":"C1040334000XXX","finanInstOutlet":"XXXXXX"," handNo":"","hardVerNo":"0XX","headDataTypeFlag":"1","headEnd":"0123","headStart":"2010XXX","headString":"021XXX","machineModel":"XXX-200XX","machineSNo":"XXX- 200CN000015XXXX","machineType":"XX_PL_XXX","mfr":"XXXX","oldBatchNo":"23080812XXXX","operator":"XX","reserve1":"0","transJrn":"","transTlId":"","transTyp":""}.

[0045] Furthermore, the message header name may be the name of the message header data in the target message data. The message body name may be the name of the message body data in the target message data. The extracted message header name and message body name may both be used as field names. For example, the types of message header names are shown in Table 2, and the types of message body names are shown in Table 3.

[0046] Table 2 Example of message header data structure

[0047]

[0048]

[0049] Table 3 Example of message body data structure

[0050] name length type illustrate Date 1 Uint16 Banknote verification start date Time 1 Uint16 Banknote verification start time tfFlag 1 Uint16 Real, fake, damaged and old currency signs ErrorCode 6 Uint16 Error Code MoneyFlag 8 Uint16 Currency Symbol Ver 1 Uint16 Version number Valuta 1 Uint64 Currency CharNUM 1 Uint16 Number of characters in the prefix number SNo 12 Uint16 Serial number Reserve2 16 Uint16 Reserved word 2 Num 1 Int16 Number of characters in the serial number image Height 1 Int16 Glyph height Width 1 Int16 Glyph width Reserve3 1 Uint16 Reserved word 3 TImgSNoData 1536 BYTE Crown number image dot matrix data

[0051] S240: Match a target field type corresponding to each field name from the preset data storage table, and determine a target file storage database corresponding to the field name based on the target field type.

[0052] Among them, the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases. The preset data storage table may contain database types corresponding to multiple field types, and each database type may be used to store data of at least one field type. The target field type may be the field type to which the field name belongs. Specifically, the field name in the target serial number file may be matched with the field name in the preset data storage table. If the match is successful, the target field type corresponding to the field name may be determined. The target file storage database may be a database for storing file data corresponding to the field name. When the target field type corresponding to the field name is determined, the database type corresponding to the target field type may be determined based on the correspondence between the field type and the database type in the preset data storage table.

[0053] Optionally, the preset data storage table includes: a data master table and a data slave table, matching the target field type corresponding to each field name from the preset data storage table, and determining the target file storage database corresponding to the field name based on the target field type, including: for each field name, when the field name successfully matches any field type in the data master table, determining the target file storage database corresponding to the field name as a search engine library; when the field name successfully matches any field type in the data slave table, determining the target file storage database corresponding to the field name as a relational database.

[0054] The data master table and data detail table can be two types of tables in a preset data storage table. Field types belonging to the data master table can be stored in a search engine library; field types belonging to the data master table can be stored in a relational database. Open-source relational databases are open-source databases that use a relational model to organize data. Commonly used free and open-source libraries include SQLite, MySQL, and PostgreSQL. Search engine databases are a type of NoSQL database specialized for data content search, offering full-text search capabilities and generally used to process massive amounts of data. They offer high flexibility and scalability. Commonly used open-source search engine databases include Lucene, Solr, Elasticsearch, ManticoreSearch, and RediSearch. Optionally, for image files in the target serial number file, the target file storage database corresponding to the image files is determined to be a preset image storage database. The preset image storage database can be a database different from the search engine library and the relational database. The master-detail table stores small, frequently used data, while images store large, infrequently used data. Storing the data in the master-detail table and the image data in separate databases can improve query speed and bandwidth usage.

[0055] For example, Table 4 is an example diagram of a preset data storage table. As shown in Table 4, the serial number file can be split into three separate data structures for storage. The master and slave tables are linked by batch number, and the additional image file storage information is read from a distributed storage location using the date batch number plus the transaction log number. The data in the master file table is stored in a relational database and used for page list queries. The data in the slave file table is stored in a search engine database and primarily contains the specific banknote serial number data in the serial number file, used for detailed queries of specific banknote serial numbers. Image data, due to its high storage and transmission bandwidth consumption, is directly stored in distributed file storage, such as NAS storage.

[0056] Table 4 Example of preset data storage table

[0057]

[0058] S250: Each type of data in the target serial number file is stored in a corresponding file storage database, thereby completing the serial number management process of the target serial number file.

[0059] Among them, through the field types in the target serial number file, the file data of different field types are stored in the corresponding database, which can upgrade the traditional serial number field system data from TB level to PB level, with the characteristics of wide application scenarios, long tracking cycle and high query efficiency.

[0060] Optionally, when a data query instruction is received, the data to be queried and the file storage database corresponding to the data to be queried are determined based on the data query instruction; the data query result corresponding to the data query instruction is determined based on the file storage database, and the data query result is returned to the terminal corresponding to the data query instruction.

[0061] The technical solution provided by the embodiment of the present invention obtains the original crown number file sent by at least one front-end device; for non-image files in the original crown number file, the non-image files are formatted and compressed, and the target crown number file is obtained based on the processed non-image files and the image files in the original crown number file; the field name corresponding to each type of data in the target crown number file is identified; the target field type corresponding to each field name is matched from a preset data storage table, and the target file storage database corresponding to the field name is determined based on the target field type; each type of data in the target crown number file is stored in the corresponding file storage database, thereby completing the crown number management process of the target crown number file. The technical solution of the embodiment of the present invention solves the problem of small storage capacity for crown number files in the prior art. It can classify the data in the crown number file, determine the file storage database corresponding to each type of data, and store the data in the corresponding file storage database, thereby increasing the data storage capacity of the crown number file.

[0062] Figure 3 This is a structural diagram of a serial number management device provided by an embodiment of the present invention. The embodiment of the present invention is applicable to the scenario of determining the storage database that is adapted for each type of data in a serial number file. The device can be implemented by software and / or hardware and integrated into a computer device with application development capabilities.

[0063] like Figure 3 As shown, the serial number management device includes: a serial number file acquisition module 310, a database determination module 320 and a file storage module 330.

[0064] Among them, the crown number file acquisition module 310 is used to obtain the target crown number file; the database determination module 320 is used to determine the file storage database corresponding to each type of data in the target crown number file based on the preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; the file storage module 330 is used to store each type of data in the target crown number file in the corresponding file storage database, thereby completing the crown number management process of the target crown number file.

[0065] The technical solution provided by the embodiment of the present invention obtains a target serial number file; determines the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; and stores each type of data in the target serial number file in the corresponding file storage database, thereby completing the serial number management process of the target serial number file. The technical solution of the embodiment of the present invention solves the problem of small storage capacity of serial number files in the prior art. It can classify the data in the serial number file, determine the file storage database corresponding to each type of data, and store the data in the corresponding file storage database, thereby increasing the data storage capacity of the serial number file.

[0066] In an optional embodiment, the crown number file acquisition module 310 is specifically used to: obtain the original crown number file sent by at least one front-end device; for non-image files in the original crown number file, convert and compress the non-image files, and obtain the target crown number file based on the processed non-image files and the image files in the original crown number file.

[0067] In an optional embodiment, the database determination module 320 is specifically used to: identify the field name corresponding to each type of data in the target serial number file; match the target field type corresponding to each field name from the preset data storage table, and determine the target file storage database corresponding to the field name based on the target field type.

[0068] In an optional embodiment, the database determination module 320 includes: a field name identification unit, which is used to: parse the target serial number file to obtain target message data; extract the message header name and message body name in the target message data to obtain field names corresponding to multiple data.

[0069] In an optional embodiment, the preset data storage table includes: a data master table and a data slave table, and the database determination module 320 also includes: a target file storage database determination unit, which is used to: for each field name, when the field name successfully matches any field type in the data master table, determine that the target file storage database corresponding to the field name is a search engine library; when the field name successfully matches any field type in the data slave table, determine that the target file storage database corresponding to the field name is a relational database.

[0070] In an optional implementation, the serial number management device further includes: an image file analysis module, configured to: for an image file in the target serial number file, determine that the target file storage database corresponding to the image file is a preset image storage database.

[0071] In an optional embodiment, the serial number management device further includes: a data query module, which is used to: upon receiving a data query instruction, determine the data to be queried based on the data query instruction, and a file storage database corresponding to the data to be queried; determine a data query result corresponding to the data query instruction based on the file storage database, and return the data query result to the terminal corresponding to the data query instruction.

[0072] The serial number management device provided in the embodiment of the present invention can execute the serial number management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0073] Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Figure 4 A block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 4 The computer device 12 shown is only an example and should not limit the functionality and scope of use of the embodiments of the present invention. The computer device 12 can be any terminal device with computing capabilities and can be configured in the prefix number management device.

[0074] like Figure 4 As shown, computer device 12 is implemented as a general-purpose computing device. Components of computer device 12 may include, but are not limited to, one or more processors or processing units 16, system memory 28, and a bus 18 that connects various system components (including system memory 28 and processing unit 16).

[0075] The bus 18 may be 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, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

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

[0077] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache 32. Computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be configured to read and write non-removable, non-volatile magnetic media ( Figure 4 Not shown, often called a "hard drive"). Although Figure 4 Not shown, a magnetic disk drive for reading and writing to a removable non-volatile magnetic 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 18 via one or more data media interfaces. System memory 28 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.

[0078] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28. Such program modules 42 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 42 generally perform the functions and / or methods of the embodiments described herein.

[0079] The computer device 12 may also communicate with one or more external devices 14 (e.g., a keyboard, a pointing device, a display 24, etc.), one or more devices that enable a user to interact with the computer device 12, and / or any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may occur through an input / output (I / O) interface 22. Furthermore, the computer device 12 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 20. Figure 4 As shown, the network adapter 20 communicates with the other modules of the computer device 12 via the bus 18. Figure 4 Not shown, other hardware and / or software modules may be used in conjunction with computer device 12, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0080] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the prefix number management method provided in an embodiment of the present invention, which includes:

[0081] Obtain a target crown number file; determine the file storage database corresponding to each type of data in the target crown number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; store each type of data in the target crown number file in the corresponding file storage database, thereby completing the crown number management process of the target crown number file.

[0082] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for managing serial numbers provided in any embodiment of the present invention is implemented, including:

[0083] Obtain a target crown number file; determine the file storage database corresponding to each type of data in the target crown number file based on a preset data storage table; wherein the preset data storage table is used to represent the correspondence between multiple field types and multiple file storage databases; store each type of data in the target crown number file in the corresponding file storage database, thereby completing the crown number management process of the target crown number file.

[0084] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples (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 of the above. In this document, a computer-readable storage medium can 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.

[0085] 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.

[0086] 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.

[0087] Computer program code for performing the operations of the present invention can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as C, Java, Smalltalk, C++, C#, and Python, and also conventional procedural programming languages ​​such as the "C" language 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).

[0088] Those skilled in the art will appreciate that the modules or steps of the present invention described above can be implemented using a general-purpose computing device. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they can be implemented using program code executable by a computer device, which can then be stored in a storage device and executed by the computing device. Alternatively, they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

[0089] Note that the above are only preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will appreciate that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments, and substitutions are possible for 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 scope of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for managing prefix numbers, characterized in that: include: Get the target serial number file; Determine the file storage database corresponding to each type of data in the target serial number file based on a preset data storage table; wherein the preset data storage table is used to indicate the correspondence between multiple field types and multiple file storage databases; Each type of data in the target serial number file is stored in a corresponding file storage database to complete the serial number management process of the target serial number file.

2. The method according to claim 1, characterized in that The step of obtaining the target serial number file includes: Obtaining an original prefix number file sent by at least one front-end device; For the non-image files in the original serial number file, the non-image files are format converted and compressed, and the target serial number file is obtained based on the processed non-image files and the image files in the original serial number file.

3. The method according to claim 1, characterized in that The step of determining the file storage database corresponding to each type of data in the target serial number file based on the preset data storage table includes: Identify the field name corresponding to each type of data in the target serial number file; A target field type corresponding to each field name is matched from the preset data storage table, and a target file storage database corresponding to the field name is determined based on the target field type.

4. The method according to claim 3, characterized in that The identifying of the field name corresponding to each type of data in the target serial number file includes: Parsing the target prefix number file to obtain target message data; Extract the message header name and message body name in the target message data to obtain field names corresponding to the various data.

5. The method according to claim 3, characterized in that The preset data storage table includes: a data master table and a data slave table, the slave table matches the target field type corresponding to each field name, and determines the target file storage database corresponding to the field name based on the target field type, including: For each field name, if the field name successfully matches any field type in the data master table, determining that the target file storage database corresponding to the field name is a search engine library; In the case where the field name successfully matches any field type in the data table, it is determined that the target file storage database corresponding to the field name is a relational database.

6. The method according to claim 3, characterized in that The method further comprises: For the picture file in the target serial number file, it is determined that the target file storage database corresponding to the picture file is a preset picture storage database.

7. The method according to claim 1, characterized in that The method further comprises: When a data query instruction is received, determining the data to be queried and the file storage database corresponding to the data to be queried based on the data query instruction; A data query result corresponding to the data query instruction is determined based on the file storage database, and the data query result is returned to the terminal corresponding to the data query instruction.

8. A serial number management device, characterized in that: The device comprises: The serial number file acquisition module is used to obtain the target serial number file; a database determination module, configured to determine, based on a preset data storage table, the file storage database corresponding to each type of data in the target serial number file; wherein the preset data storage table is configured to indicate the correspondence between multiple field types and multiple file storage databases; The file storage module is used to store each type of data in the target serial number file into the corresponding file storage database to complete the serial number management process of the target serial number file.

9. A computer device, characterized in that: The computer device comprises: one or more processors; a memory 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 serial number management method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for managing serial numbers as described in any one of claims 1 to 7 is implemented.

Images