Account number generation method and device

Abstract

The invention provides an account number generation method and device, and can be used in the technical field of computers. The method is applied to accounting equipment, and comprises the following steps: receiving an account opening request sent by business acceptance equipment; the account opening request carries multiple pieces of element information of the target bookkeeping service, the multiple pieces of element information comprise first-class element information and second-class element information, and the first-class element information has readable features; determining a first part of the target account number according to the first type of element information and determining a second part of the target account number according to the second type of element information, so that the second parts of the account numbers of the accounts are different; determining a target account number according to the first part and the second part; and sending the target account number to a service acceptance device to enable the service acceptance device to process the target accounting service based on the target account number. The account number generated in the double environments is unique, the consistency and stability of the basic data in the double environments are guaranteed, and environment simulation and new production function verification are facilitated.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to an account number generation method and apparatus. Background Art

[0002] An accounting system is a system that provides accounting processing and fund accounting, which is composed of distributed services such as a gateway module, a service acceptance module, an accounting module, an accounting module, and a report module. To ensure business continuity, the services are respectively deployed in two environments, A and B. The stable version is deployed in environment A, and the version to be verified is deployed in environment B. When environment A receives a bookkeeping request, the gateway module routes the bookkeeping request to the service acceptance module, and the bookkeeping request is diverted to environment B through a message middleware, so as to achieve the purpose of gray-scale verification of the function to be put into production in environment B.

[0003] In the related art, after the service acceptance module receives a bookkeeping request, it first queries whether there is an account number corresponding to the bookkeeping request. If not, it opens an account through the accounting module, that is, generates a new account number. When generating an account number, generally, a method of splicing a feature code combination + an increment sequence is used, such as using "bank code + currency code + subject code + increment sequence number" to splice to obtain an account number.

[0004] However, in a dual-environment scenario, the increment sequences generated in environment A and environment B may be different, resulting in different generated account numbers, causing inconsistent basic data in the dual-environment, and thus failing to achieve the purpose of fully simulating environment A in environment B for verifying newly put into production functions. Summary of the Invention

[0005] This application provides an account number generation method and apparatus, where the generated account numbers in a dual-environment are unique, ensuring the consistency and stability of the basic data in the dual-environment, and facilitating the simulation of the environment and the verification of newly put into production functions.

[0006] In a first aspect, this application provides an account number generation method, which is applied to an accounting device and includes:

[0007] Receiving an account opening request sent by a service acceptance device; the account opening request carries multiple element information of a target bookkeeping service, and the multiple element information includes first type element information and second type element information, where the first type element information has a readable feature, and the length of each element information in the first type element information is fixed; at least part of the element information in the second type element information has a non-fixed length;

[0008] Determine the first part of the target account number according to the first type of element information, and determine the second part of the target account number according to the second type of element information, so that the second parts of the account numbers of each account are different; the first part has a first preset length, and the second part has a second preset length;

[0009] Determine the target account number according to the first part and the second part;

[0010] Send the target account number to the service acceptance device, so that the service acceptance device processes the target accounting service based on the target account number.

[0011] Optionally, the determining the first part of the target account number according to the first type of element information and the second part of the target account number according to the second type of element information includes:

[0012] If the number of element information included in the first type of element information is one, determine the element information included in the first type of element information as the first part; if the number of element information included in the first type of element information is at least two, splice the element information included in the first type of element information to obtain the first part;

[0013] Splice the element information in the second type of element information to obtain a first hash value;

[0014] Use a preset coding algorithm to code the first hash value to obtain a second hash value;

[0015] If the length of the second hash value is greater than the second preset length, compress the second hash value to obtain the second part.

[0016] Optionally, the determining the target account number according to the first part and the second part includes any one of the following:

[0017] Splice the first part and the second part to obtain the target account number;

[0018] Splice the first part, the second part and the reserved bit to obtain the target account number.

[0019] Optionally, after determining the target account number according to the first part and the second part, the method further includes:

[0020] Correspondingly store the target account number and the multiple element information in a database, so that the service acceptance device locates the target account number from the database based on the multiple element information.

[0021] In a second aspect, the present application provides an account number generation method, which is applied to a service acceptance device and includes:

[0022] Receiving a bookkeeping request for a target bookkeeping service sent by a gateway device; the bookkeeping request carries second type element information of the target bookkeeping service, and the length of at least part of the element information in the second type element information is variable-length;

[0023] Performing account number positioning based on multiple element information of the target bookkeeping service, the multiple element information includes first type element information and the second type element information, the first type element information has a readable feature, and the length of each element information in the first type element information is fixed-length;

[0024] If the account number is not located, sending an account opening request to an accounting device, the account opening request carrying the multiple element information, so that the accounting device determines the first part of the target account number according to the first type element information and determines the second part of the target account number according to the second type element information, and determines the target account number according to the first part and the second part;

[0025] Receiving the target account number sent by the accounting device;

[0026] Processing the target bookkeeping service based on the target account number.

[0027] Optionally, the performing account number positioning based on multiple element information of the target bookkeeping service includes:

[0028] Locating an account number stored corresponding to the multiple element information from a cache space;

[0029] If the account number is not located from the cache space, locating an account number stored corresponding to the multiple element information from a database.

[0030] Optionally, after receiving the target account number sent by the accounting device, the method further includes:

[0031] Storing the target account number into the cache space and the database respectively.

[0032] Optionally, the bookkeeping request further carries a bookkeeping scenario code of the target bookkeeping service, and the first type element information includes an account type code; before performing account number positioning based on multiple element information of the target bookkeeping service, the method further includes:

[0033] Obtaining an accounting entry stored corresponding to the bookkeeping scenario code;

[0034] Obtaining the account type code from the accounting entry.

[0035] In a third aspect, the present application provides an account number generation device disposed in an account device, including:

[0036] A receiving module, configured to receive an account opening request sent by a service acceptance device; the account opening request carries a plurality of element information of a target accounting service, the plurality of element information includes first type element information and second type element information, wherein the first type element information has a readable feature, and the length of each element information in the first type element information is a fixed length; at least part of the element information in the second type element information has a non-fixed length;

[0037] A first determination module, configured to determine a first part of a target account number according to the first type element information, and determine a second part of the target account number according to the second type element information, so that the second parts of the account numbers of each account are different; the first part has a first preset length, and the second part has a second preset length;

[0038] A second determination module, configured to determine the target account number according to the first part and the second part;

[0039] A sending module, configured to send the target account number to the service acceptance device, so that the service acceptance device processes the target accounting service based on the target account number.

[0040] In a fourth aspect, the present application provides an account number generation device disposed in a service acceptance device, including:

[0041] A receiving module, configured to receive a accounting request for a target accounting service sent by a gateway device; the accounting request carries the second type element information of the target accounting service, and at least part of the element information in the second type element information has a non-fixed length;

[0042] A positioning module, configured to perform account number positioning based on a plurality of element information of the target accounting service, the plurality of element information includes first type element information and the second type element information, the first type element information has a readable feature, and the length of each element information in the first type element information is a fixed length;

[0043] A sending module, configured to, if no account number is located, send an account opening request to an accounting device, the account opening request carries the plurality of element information, so that the accounting device determines a first part of a target account number according to the first type element information and determines a second part of the target account number according to the second type element information, and determines the target account number according to the first part and the second part;

[0044] The receiving module is further configured to receive the target account number sent by the accounting device;

[0045] The processing module is configured to process the target accounting service based on the target account number.

[0046] In a fifth aspect, the present application provides an electronic device, including: a processor, and a memory and a transceiver respectively communicatively connected to the processor;

[0047] The memory stores computer-executable instructions; the transceiver is configured to transmit and receive data between the accounting device or the service acceptance device;

[0048] The processor executes the computer-executable instructions stored in the memory to implement the account number generation method according to any one of the first aspects or the account number generation method according to any one of the second aspects.

[0049] In a sixth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the account number generation method according to any one of the first aspects or the account number generation method according to any one of the second aspects.

[0050] In a seventh aspect, the present application provides a computer program product, including computer-executable instructions, and when the computer-executable instructions are executed by a processor, they implement the account number generation method according to any one of the first aspects or the account number generation method according to any one of the second aspects.

[0051] For the account number generation method and device provided by the present application, after the service acceptance device receives a bookkeeping request for a target bookkeeping service, it first locates the account number according to multiple element information of the target bookkeeping service. If the account number is not located, it sends an account opening request to the accounting device to trigger the accounting device to determine the first part according to the first type of element information in the multiple element information and determine the second part according to the second type of element information. It can be seen that the present application does not need to generate an auto-increment serial number, but determines the target account number according to the first part and the second part. Therefore, it avoids the phenomenon that the auto-increment serial numbers generated in the A environment and the B environment are different in the dual environment, resulting in different generated account numbers. Moreover, the second part determined by the present application is different from the second parts of other account numbers. Therefore, the account numbers generated in the dual environment are unique, ensuring the consistency and stability of the basic data in the dual environment, and contributing to the simulation of the environment and the verification of the newly put into production functions. Description of the Drawings

[0052] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0053] Figure 1 is a schematic diagram of an application scenario shown according to an exemplary embodiment;

[0054] Figure 2 is a schematic flowchart of an account number generation method shown according to an exemplary embodiment;

[0055] Figure 3 is a schematic flowchart of an account number generation method shown according to another exemplary embodiment;

[0056] Figure 4 is a schematic diagram of a system architecture shown according to an exemplary embodiment;

[0057] Figure 5 is a schematic diagram of an account number generation process shown according to an exemplary embodiment;

[0058] Figure 6 is a schematic structural diagram of an account number generation device shown according to an exemplary embodiment;

[0059] Figure 7 is a schematic structural diagram of an account number generation device shown according to another exemplary embodiment;

[0060] Figure 8 is a schematic structural diagram of an electronic device shown according to an exemplary embodiment.

[0061] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Description of the Embodiments

[0062] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0063] Terms such as "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. In the description of the following embodiments, "a plurality" means more than two unless otherwise specifically defined.

[0064] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0065] First, the nouns involved in this application are explained:

[0066] Financial institution code: Abbreviation "Jinbian", the unique identifier of a financial institution, consisting of capital English characters and Arabic numerals, with a length of 14 digits.

[0067] Inter-bank number: Also known as the opening bank number, it is the inter-bank code of the bank business institutions affiliated to the People's Bank of China and each professional bank system, represented by Arabic numerals. All levels of bank offices that have obtained the inter-bank number indicate that they can participate in the inter-bank transactions across the country or within the jurisdiction of branches or sub-branches, and directly conduct remittances, with a length of 12 digits.

[0068] Taxpayer identification number: The number on the tax registration certificate, usually abbreviated as "tax number", and the taxpayer identification number of each enterprise is unique. It consists of 15, 18, or 20 digits (character type).

[0069] To clearly understand the technical solution of this application, the solutions of the prior art are first introduced in detail.

[0070] The accounting system is a system that provides accounting processing and capital accounting, consisting of distributed services such as a gateway module, a business acceptance module, an accounting module, an accounting module, and a report module. Each module corresponds to one or more devices, and the device is used to provide the corresponding service. To ensure business continuity, the services are separately deployed in two environments, A and B. The stable version is deployed in environment A, and the version to be verified is deployed in environment B. When environment A receives a bookkeeping request, the gateway module routes the bookkeeping request to the business acceptance module, and the bookkeeping request is diverted to environment B through the message middleware, achieving the purpose of gray-scale verification of the function to be put into production in environment B.

[0071] In the related art, after the business acceptance module receives a bookkeeping request, it first queries whether there is an account number corresponding to the bookkeeping request. If not, it opens an account through the accounting module, that is, generates a new account number. When generating the account number, generally, the method of splicing the feature code combination + self-incrementing sequence (usually 6 digits) is used. For example, the account number is spliced using "inter-bank number + currency code + subject code + self-incrementing serial number", and it is required that the generated account number has global uniqueness and a certain degree of readability. To ensure the uniqueness of the account number under the premise that the feature code is fixed, it is necessary to ensure the uniqueness of the self-incrementing sequence.

[0072] However, in a dual-environment scenario, the process of generating account numbers is generally handled internally by the system. For example, the accounting module automatically generates account numbers instead of receiving them from the gateway. The auto-increment serial numbers generated in Environment A and Environment B may be different, resulting in potentially different generated account numbers, causing inconsistencies in the basic data between the two environments. As a result, it is impossible to fully simulate Environment A in Environment B for the purpose of verifying newly launched functions.

[0073] Regarding the problem that the account numbers generated in the dual-environment of related technologies may be different, the inventors found in their research that to solve this problem, instead of using an auto-increment sequence to concatenate and obtain the account number, since the feature codes used in related technologies cannot uniquely determine an account number, multiple other account-related element information can be used to uniquely determine an account number. Considering the readability and length limitations of the account number, the first part of the account number can be determined based on the first type of element information with readable features among the multiple element information, and the second part of the account number can be determined based on the other element information except the first type of element information. Thus, the determined account number not only has readability but also meets the length limitations. Specifically, after receiving a booking request for a target booking operation, the service acceptance device first locates the account number based on the multiple element information of the target booking operation. If the account number is not located, it sends an account opening request to the accounting device to trigger the accounting device to determine the first part based on the first type of element information among the multiple element information and determine the second part based on the second type of element information. It can be seen that this application does not need to generate an auto-increment serial number, but determines the target account number based on the first part and the second part. Therefore, it avoids the situation where the auto-increment serial numbers generated in Environment A and Environment B are different in a dual-environment scenario, resulting in different generated account numbers. Moreover, the second part determined in this application is different from the second parts of other account numbers. Therefore, the account numbers generated in the dual-environment are unique, ensuring the consistency and stability of the basic data in the dual-environment and facilitating the simulation of the environment and the verification of newly launched functions.

[0074] The application scenario of the account number generation method provided by the embodiments of this application will be introduced below.

[0075] Figure 1 It is a schematic diagram of an application scenario shown according to an exemplary embodiment. As Figure 1 shown, this application scenario includes: a gateway device 1, a service acceptance device 2, and an accounting device 3. Each device is connected through a network.

[0076] Among them, the gateway device 1 is used to provide gateway services. The service acceptance device 2 is used to process services. The accounting device 3 is used to manage accounts. In this embodiment, the gateway device 1 receives a bookkeeping request for a target bookkeeping service sent by the service system, and sends the bookkeeping request to the service acceptance device, so that the service acceptance device processes the target bookkeeping service. The service acceptance device first locates the corresponding account number. If it fails to locate, it sends an account opening request to the accounting device. The accounting device determines a first part according to the first type of element information carried in the account opening request, determines a second part according to the second type of element information carried in the account opening request, and then determines the target account number according to the first part and the second part, and thus sends the target account number to the service acceptance device. The service acceptance device processes the target bookkeeping service based on the target account number.

[0077] The following uses specific embodiments to elaborate in detail on the technical solution of this application and how the technical solution of this application solves the above technical problems. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0078] Figure 2 It is a flowchart of a method for generating an account number shown according to an exemplary embodiment. The execution subject of the account number generation method provided in this application is an account number generation device, and this account number generation device is integrated in the accounting device. As Figure 2 shown, the account number generation method provided in this embodiment includes the following steps:

[0079] Step S101, receive an account opening request sent by the service acceptance device; the account opening request carries multiple element information of the target bookkeeping service, and the multiple element information includes the first type of element information and the second type of element information. Among them, the first type of element information has a readable feature, and the length of each element information in the first type of element information is fixed; at least part of the element information in the second type of element information has a non-fixed length.

[0080] Among them, when the service acceptance device receives a bookkeeping request for a target bookkeeping service but fails to locate the corresponding account number, it sends an account opening request to the accounting device, thereby triggering the accounting device to generate a target account number and sending the target account number to the service acceptance device. Among them, the target bookkeeping service is any bookkeeping service received by the service acceptance device. The target account number is the account number corresponding to the target bookkeeping service.

[0081] Among them, the account opening request carries multiple element information for generating a target account number, and the multiple element information can uniquely determine a target account number. Exemplarily, the first type of element information includes an account type code. The account type code is used to refer to the account type. Exemplarily, the second type of element information includes a service type code, an account affiliated institution code, an institution attribute code, and an institution code. Among them, the lengths of the service type code, the account affiliated institution code, and the institution attribute code are fixed-length, while the length of the institution code is variable-length. The service type code is used to refer to the service type, the account affiliated institution code is used to refer to the account affiliated institution, and the institution attribute code is used to refer to the institution attribute. Exemplarily, the institution code includes any one of a financial institution code, a bank number of the opening bank, and a taxpayer identification number. Among them, the financial institution code is the unique identifier of the financial institution, with a length of 14 digits. The bank number of the opening bank is also called the inter-bank number, with a length of 12 digits. The taxpayer identification number, abbreviated as tax number, can uniquely identify an enterprise, with a length of 15, 18, or 20 digits. The user can set the type of the institution code according to needs, so as to better meet the user's needs while ensuring the unique determination of an account number. It should be noted that the institution code can also adopt other codes that can uniquely identify a financial institution or an enterprise. This embodiment does not limit this, for example, it is the name code of a financial institution or an enterprise, and this name code is obtained by encoding the name, and the encoding algorithm can be set according to needs. This embodiment does not limit this.

[0082] Step S102, determine the first part of the target account number according to the first type of element information, and determine the second part of the target account number according to the second type of element information, so that the second parts of the account numbers of each account are all different; the first part has a first preset length, and the second part has a second preset length.

[0083] Among them, since the first type of element information has a readable feature, the determined first part has readability. Since the second parts of each account number are all different, the second part is unique.

[0084] Step S103, determine the target account number according to the first part and the second part.

[0085] Among them, since the first part has readability and the second part is unique, the determined target account number has readability and is unique.

[0086] Step S104, send the target account number to the service acceptance device, so that the service acceptance device processes the target accounting business based on the target account number.

[0087] In this embodiment, after determining the target account number, the accounting device sends the target account number to the service acceptance.

[0088] In this embodiment, after receiving a bookkeeping request for a target bookkeeping service, the service acceptance device first locates the account number according to multiple element information of the target bookkeeping service. If the account number cannot be located, an account opening request is sent to the accounting device to trigger the accounting device to determine a first part according to the first type of element information in the multiple element information and a second part according to the second type of element information. It can be seen that this application does not need to generate an auto-increment serial number, but determines the target account number according to the first part and the second part. Therefore, it avoids the phenomenon that the auto-increment serial numbers generated in the A environment and the B environment are different in the dual environment, resulting in different generated account numbers. Moreover, the second part determined by this application is different from the second parts of other account numbers. Therefore, the account numbers generated in the dual environment are unique, ensuring the consistency and stability of the basic data in the dual environment, and contributing to the simulation of the environment and the verification of newly put into production functions.

[0089] The above Figure 2 The above-described embodiment illustrates the account number generation method from the perspective of the accounting device. Next, the account number generation method will be described from the perspective of the service acceptance device.

[0090] Figure 3 FIG. is a schematic flowchart of an account number generation method according to another exemplary embodiment. The execution subject of the account number generation method provided by this application is an account number generation device, and this account number generation device is integrated in the service acceptance device. As Figure 3 shown, the account number generation method provided in this embodiment includes the following steps:

[0091] Step S201, receiving a bookkeeping request for a target bookkeeping service sent by a gateway device; the bookkeeping request carries the second type of element information of the target bookkeeping service, and at least some of the element information in the second type of element information has a variable length.

[0092] Among them, the gateway device is used to communicate with the service system. The service system triggers a bookkeeping request, which is forwarded to the service acceptance device via the gateway device. The service system refers to the system corresponding to the service provider. The gateway device also sends the bookkeeping request to the B environment through the message middleware to enable the B environment to perform simulation and verification. Exemplarily, the second type of element information includes a service type code, an account attribution institution code, an institution attribute code, and an institution code. Among them, the lengths of the service type code, the account attribution institution code, and the institution attribute code are fixed, while the length of the institution code is variable. The service type code is used to represent the service type, the account attribution institution code is used to represent the account attribution institution, and the institution attribute code is used to represent the institution attribute. Exemplarily, the institution code includes any one of a financial institution code, a bank number of the opening bank, and a taxpayer identification number. The user can set the type of the institution code according to needs, so as to better meet the user's needs while ensuring the unique determination of an account number.

[0093] In this embodiment, for the implementation manner of this step, refer to the above step S101, which will not be elaborated here.

[0094] Step S202: Locate the account number based on multiple element information of the target accounting service. The multiple element information includes first-type element information and second-type element information. The first-type element information has a readable feature, and the length of each element information in the first-type element information is fixed-length.

[0095] In this embodiment, after receiving the accounting request, the service acceptance device first obtains the first-type element information of the target accounting service, and then locates the account number. If the account number is located, the target accounting service is processed based on the located target account number. If the account number is not located, it is necessary to generate the target account number with the help of the accounting device. Exemplarily, the first-type element information includes an account type code. The account type code is used to refer to the account type.

[0096] Step S203: If the account number is not located, send an account opening request to the accounting device. The account opening request carries multiple element information, so that the accounting device determines the first part of the target account number according to the first-type element information, determines the second part of the target account number according to the second-type element information, and determines the target account number according to the first part and the second part.

[0097] Among them, the accounting device provides an interface externally. The service acceptance device sends an account opening request to the accounting device by calling this interface. Similarly, after generating the target account number, the accounting device calls the interface provided externally by the service acceptance device and sends the target account number to the service acceptance device.

[0098] Step S204: Receive the target account number sent by the accounting device.

[0099] Step S205: Process the target accounting service based on the target account number.

[0100] Among them, processing the target accounting service based on the target account number means performing accounting for the target account number.

[0101] In this embodiment, after receiving a bookkeeping request for a target bookkeeping service, the service acceptance device first locates the account number based on multiple element information of the target bookkeeping service. If the account number cannot be located, an account opening request is sent to the accounting device to trigger the accounting device to determine the first part according to the first type of element information in the multiple element information and determine the second part according to the second type of element information. It can be seen that this application does not need to generate an auto-increment serial number, but determines the target account number according to the first part and the second part. Therefore, it avoids the phenomenon that the auto-increment serial numbers generated in the A environment and the B environment are different in the dual environment, resulting in different generated account numbers. Moreover, the second part determined by this application is different from the second parts of other account numbers. Therefore, the account numbers generated in the dual environment are unique, ensuring the consistency and stability of the basic data in the dual environment, and contributing to the simulation of the environment and the verification of newly put into production functions.

[0102] The above Figure 2 illustrated embodiments and Figure 3 illustrated embodiments respectively illustrate the account number generation method from the perspectives of the accounting device and the service acceptance device. Next, the account number generation method will be described from the perspective of the system architecture.

[0103] Figure 4 is a schematic diagram of a system architecture shown according to an exemplary embodiment. As Figure 4 shown, this system architecture is the system architecture corresponding to the accounting system. Among them, the accounting system includes but is not limited to: a gateway module, a service acceptance module, and an accounting module. To ensure business continuity, the services are deployed in the A environment and the B environment respectively. The gateway module in the A environment receives the bookkeeping request for the bookkeeping service sent by the business system, routes the bookkeeping request to the service acceptance module in the A environment, and moreover, the gateway module in the A environment also diverts the bookkeeping request through the message middleware, that is, asynchronously forwards the bookkeeping request to the gateway module in the B environment. Thus, the gateway module in the B environment routes the bookkeeping request to the service acceptance module in the B environment. The service acceptance modules in the two environments respectively locate the account number based on multiple element information of the bookkeeping service. If the account number cannot be located, the interfaces provided by the accounting modules in their respective environments are called to trigger the accounting modules to open an account. Accordingly, the accounting modules process the account opening request and generate a new account number.

[0104] Based on the above system architecture, the account number generation method will be described below by taking the data interaction process between the accounting device and the service acceptance device as an example.

[0105] Figure 5 is a schematic diagram of an account number generation process shown according to an exemplary embodiment. As Figure 5 shown, the account number generation process provided in this embodiment includes the following steps:

[0106] Step S301: The service acceptance device receives a bookkeeping request for a target bookkeeping service sent by the gateway device. The bookkeeping request carries second - type element information of the target bookkeeping service, and the length of at least some of the element information in the second - type element information is variable - length.

[0107] In this embodiment, the implementation manner of this step refers to the above - mentioned step S201 and will not be elaborated here.

[0108] Step S302: The service acceptance device locates the account number based on multiple element information of the target bookkeeping service. The multiple element information includes first - type element information and second - type element information. The first - type element information has a readable feature, and the length of each element information in the first - type element information is fixed - length.

[0109] Among them, before step S302, the service acceptance device first obtains the first - type element information. In an optional embodiment, the bookkeeping request also carries a bookkeeping scenario code of the target bookkeeping service, and the first - type element information includes an account type code. Correspondingly, the implementation manner of obtaining the first - type element information before step S302 includes: obtaining the accounting entry stored corresponding to the bookkeeping scenario code; and obtaining the account type code from the accounting entry.

[0110] Among them, the bookkeeping scenario code is the basis for bookkeeping by the business party, indicating the bookkeeping scenario, and the bookkeeping scenario code includes but is not limited to: information indicating the business type, information indicating the business scenario, and information indicating the scenario refinement. Optionally, the bookkeeping scenario code is obtained by splicing a business type code, a business scenario code, and a scenario refinement code. Among them, the business type code is used to refer to the business type, the business scenario code is used to refer to the business scenario, and the scenario refinement code is used to refer to the scenario refinement. Among them, the business type can be liquidation, charging, handling fee expenditure, or manual operation, etc. The business scenario indicates what scenarios are included under the corresponding business type. For example, when the business type is liquidation, the business scenario is the business liquidation of small - amount batch payment, and the scenario refinement is transferred from the bank clearing account to the network clearing account; another example is that when the business type is handling fee expenditure, the business scenario is system handling fees, and the scenario refinement is large - value payment system - transferred from the network clearing account.

[0111] In the above - mentioned optional embodiment, the bookkeeping scenario code has a corresponding accounting entry, and the accounting entry is the accounting entry corresponding to the bookkeeping scenario represented by the bookkeeping scenario code, and the accounting entry contains the account type code. Then, by determining the account type code with the help of the bookkeeping scenario code, the determined account type code is relatively accurate.

[0112] In an alternative embodiment, the service acceptance device stores multiple account numbers in both the cache space and the database, facilitating the processing of accounting services. However, the account numbers stored in the cache space and the database may be different. Correspondingly, the implementation of step S302 includes: locating the account number stored corresponding to multiple element information from the cache space; if the account number is not located from the cache space, then locating the account number stored corresponding to multiple element information from the database.

[0113] Among them, the service acceptance device first locates the account number from the cache space. If located, it processes the target accounting service; if not located, it locates the account number from the database. If the account number is located from the database, it processes the target accounting service. If the account number is not located from the database, then step S303 is executed.

[0114] In the above alternative embodiment, by sequentially locating the account number from the cache space and the database, the location range is relatively comprehensive, ensuring the accuracy of the location result; and since the data stored in the cache space is less than the data stored in the database, the method of first locating from the cache space and then from the database is more efficient.

[0115] In another alternative embodiment, the service acceptance device can also directly locate the account number stored corresponding to multiple element information from the database; if the account number is located from the database, it processes the target accounting service. If the account number is not located from the database, then step S303 is executed.

[0116] Step S303, if the service acceptance device does not locate the account number, it sends an account opening request to the accounting device, and the account opening request carries multiple element information of the target accounting service.

[0117] Correspondingly, the accounting device receives the account opening request sent by the service acceptance device.

[0118] In this embodiment, the implementation manner of this step refers to the above step S203 and the above step S101, which will not be elaborated here.

[0119] Step S304, the accounting device determines the first part of the target account number according to the first type of element information, and determines the second part of the target account number according to the second type of element information, so that the second parts of the account numbers of each account are all different; the first part has a first preset length, and the second part has a second preset length.

[0120] In this embodiment, the length of the account number field defined by the database is fixed, for example, 32 bits. Since there are many database tables related to the account number, such as the account balance table, the income and expenditure details table, the account historical balance table, etc., if the length of the account number field is expanded, the change range is large and the business impact is significant. Therefore, the present application does not adjust the length of the account number field defined by the database. In this regard, when generating the target account number, the length of the target account number needs to be controlled within the length defined by the database to comply with the constraints of the database.

[0121] Exemplarily, the implementation manner of determining the first part of the target account number according to the first type of element information in step S304 includes: if the number of element information included in the first type of element information is one, then the element information included in the first type of element information is determined as the first part; if the number of element information included in the first type of element information is at least two, then the respective element information included in the first type of element information are concatenated to obtain the first part.

[0122] In an alternative embodiment, the implementation manner of determining the second part of the target account number according to the second type of element information in step S304 includes: concatenating the respective element information in the second type of element information to obtain the second part of the target account number. This method is relatively simple and efficient. However, the length of some of the element information in the second type of element information is fixed-length, while the length of some other element information is variable-length. The length of the second part obtained by direct concatenation is also variable-length, and in the case where the length of other element information except the institution code is relatively long, the length of the second part obtained by concatenation is very likely to exceed the length defined by the database. In this case, the implementation manner provided by the following alternative embodiment can be used to generate the second part.

[0123] In another alternative embodiment, the implementation manner of determining the second part of the target account number according to the second type of element information in step S304 includes the following steps S3041 - S3044:

[0124] Step S3041, concatenating the respective element information in the second type of element information to obtain a first hash value.

[0125] For example, the splicing order can be set as needed, and this embodiment does not limit it. Exemplarily, if the second type of element information includes a service type code, an accounting attribution institution code, an institution attribute code, and an institution code, then the splicing can be performed in the order of the service type code, the accounting attribution institution code, the institution attribute code, and the institution code, or in the order of the accounting attribution institution code, the service type code, the institution attribute code, and the institution code. Regarding the length of the first hash value obtained by splicing, for example, the length of the accounting attribution institution code is 6 digits, the length of the service type code is 6 digits, the length of the institution attribute code is 2 digits, and the length of the institution code ranges from 11 digits to 20 digits. Then, the length of the first hash value obtained by splicing is from 25 digits to 34 digits.

[0126] Step S3042: Use a preset coding algorithm to code the first hash value to obtain a second hash value.

[0127] Optionally, the preset coding algorithm is the MD5 message-digest algorithm or other encryption algorithms. Among them, the MD5 message-digest algorithm is a widely used cryptographic hash function that can generate a 128-bit (16-byte) hash value to ensure the integrity and consistency of information transmission. The security of the second hash value obtained by coding the first hash value using the preset coding algorithm is higher.

[0128] Step S3043: If the length of the second hash value is greater than the second preset length, compress the second hash value to obtain a second part.

[0129] Among them, the sum of the first preset length and the second preset length should be less than or equal to the length of the account number defined by the database. When the length of the second hash value is greater than the second preset length, it is necessary to compress the second hash value to meet the requirements of the database for the length of the account number.

[0130] Among them, the compression method can be high-radix bit compression, such as 16-bit compression, 32-bit compression, etc. Taking the preset coding algorithm as the MD5 message-digest algorithm as an example, the length of the second hash value is 128 bits, the length of the account number defined by the database is 32 bits, and the first preset length is 3 bits. Then, the second preset length needs to be equal to or less than 29 bits. It can be seen that the length of the second hash value is greater than the second preset length. In this case, the second hash value can be compressed in base 32 to obtain a second part with a length less than the second preset length.

[0131] In the above optional embodiments, in order to avoid database field expansion and reduce business impact, the first part is determined separately according to the number of element information included in the first type of element information, and the original element information included in the first type of element information is used when determining the first part to ensure readability. The second type of element information is concatenated to obtain the first hash value, and the second hash value obtained by encoding ensures the security of the element information on the basis of the first hash value. When the length of the second hash value is greater than the second preset length, the second hash value is also compressed, so that the length of the second part obtained by compression meets the length requirement, solving the problem that directly concatenating multiple element information may result in an indefinite length of the account number and not meeting the database constraints.

[0132] In the above embodiment, step S3043 is described by taking the case where the length of the second hash value is greater than the second preset length as an example. In some other embodiments, step S3043 may be replaced with: if the length of the second hash value is not greater than the second preset length, the second hash value is determined as the second part.

[0133] Step S305, the accounting device determines the target account number according to the first part and the second part.

[0134] In this embodiment, the target account number generated by combining the first part and the first part has both certain security, stability and fixed length. Optionally, the implementation manner of step S305 includes any one of the following:

[0135] The first way is to concatenate the first part and the second part to obtain the target account number.

[0136] The second way is to concatenate the first part, the second part and the reserved bit to obtain the target account number.

[0137] In the above optional implementation manner, directly concatenating the first part and the second part is simple and efficient; while adding a reserved bit on the basis of the first part and the second part facilitates the user to set the function of the reserved bit according to needs.

[0138] In an optional embodiment, after step S305, the account number generation method provided by the present application further includes the following steps: storing the target account number corresponding to multiple element information in a database, so that the service acceptance device locates the target account number from the database based on the multiple element information.

[0139] In the above optional embodiments, by storing the generated target account number corresponding to multiple element information in the database, each account number and the corresponding multiple element information are stored in the database, so that the service acceptance device can locate the account number from the database after receiving the accounting request, providing data support for account number location.

[0140] Step S306: The accounting device sends the target account number to the service acceptance device.

[0141] Correspondingly, the service acceptance device receives the target account number sent by the accounting device. In an alternative embodiment, when the service acceptance device receives the target account number sent by the accounting device, it stores the target account number in the cache space and the database respectively.

[0142] In the above alternative embodiment, by storing the generated target account number corresponding to multiple element information in the cache space and the database, the service acceptance device can locate the account number from the cache space and the database after receiving the accounting request, providing data support for account number location.

[0143] Step S307: The service acceptance device processes the target accounting service based on the target account number.

[0144] In this embodiment, the implementation manner of this step refers to the above step S205 and will not be elaborated here.

[0145] Considering that the method of generating account numbers through an auto-increment sequence in the related art cannot ensure the stability of account numbers on both sides in a dual environment, this application uniquely locates an account number by refining multiple element information, and the method of generating a new account number can ensure the stability of data on both sides in a dual environment. At the same time, the exclusive lock required by the auto-increment sequence is removed, improving the concurrent processing ability of automatically opening an account to generate account numbers.

[0146] Figure 6 is a schematic structural diagram of an account number generation device shown according to an exemplary embodiment, as Figure 6 shown. In this embodiment, the account number generation device 400 can be set in the accounting device. The account number generation device 400 includes:

[0147] A receiving module 401, configured to receive an account opening request sent by the service acceptance device; the account opening request carries multiple element information of the target accounting service. The multiple element information includes first type element information and second type element information. Among them, the first type element information has a readable feature, and the length of each element information in the first type element information is a fixed length; at least part of the element information in the second type element information has a non-fixed length;

[0148] A first determination module 402, configured to determine the first part of the target account number according to the first type element information, and determine the second part of the target account number according to the second type element information, so that the second parts of the account numbers of each account are different; the first part has a first preset length, and the second part has a second preset length;

[0149] The second determination module 403 is configured to determine a target account number according to the first part and the second part;

[0150] The sending module 404 is configured to send the target account number to a service acceptance device, so that the service acceptance device processes a target accounting service based on the target account number.

[0151] Optionally, the first determination module 402 is configured to:

[0152] If the number of element information included in the first type of element information is one, determine the element information included in the first type of element information as the first part; if the number of element information included in the first type of element information is at least two, splice the respective element information included in the first type of element information to obtain the first part;

[0153] Splice the respective element information in the second type of element information to obtain a first hash value;

[0154] Use a preset coding algorithm to code the first hash value to obtain a second hash value;

[0155] If the length of the second hash value is greater than a second preset length, compress the second hash value to obtain the second part.

[0156] Optionally, the second determination module 403 is configured to:

[0157] Splice the first part and the second part to obtain the target account number; or,

[0158] Splice the first part, the second part, and a reserved bit to obtain the target account number.

[0159] Optionally, the apparatus 400 further includes:

[0160] A storage module, configured to store the target account number and multiple pieces of element information in a database in a corresponding manner, so that the service acceptance device locates the target account number from the database based on the multiple pieces of element information.

[0161] The account number generation apparatus provided in this embodiment may execute the technical solutions of the corresponding method embodiment, and its implementation principle and technical effects are similar to those of the corresponding method embodiment, and will not be elaborated here.

[0162] Figure 7 is a schematic structural diagram of an account number generation apparatus shown according to an exemplary embodiment. As Figure 7 shown, in this embodiment, the account number generation apparatus 500 may be disposed in a service acceptance device. The account number generation apparatus 500 includes:

[0163] A receiving module 501, configured to receive a charging request for a target charging service sent by a gateway device; the charging request carries second - type element information of the target charging service, and at least some of the element information in the second - type element information has a variable length.

[0164] A positioning module 502, configured to perform account number positioning based on multiple element information of the target charging service, where the multiple element information includes first - type element information and second - type element information, the first - type element information has a readable feature, and the length of each element information in the first - type element information is fixed.

[0165] A sending module 503, configured to, if the account number is not located, send an account opening request to an accounting device, where the account opening request carries multiple element information, so that the accounting device determines the first part of the target account number according to the first - type element information, determines the second part of the target account number according to the second - type element information, and determines the target account number according to the first part and the second part.

[0166] The receiving module 501 is further configured to receive the target account number sent by the accounting device.

[0167] A processing module 504, configured to process the target charging service based on the target account number.

[0168] Optionally, the positioning module 502 is configured to:

[0169] Locate the account number stored corresponding to the multiple element information from the cache space.

[0170] If the account number is not located from the cache space, locate the account number stored corresponding to the multiple element information from the database.

[0171] Optionally, the device 500 further includes:

[0172] A storage module, configured to store the target account number into the cache space and the database respectively.

[0173] Optionally, the charging request further carries a charging scenario code of the target charging service, and the first - type element information includes an account type code; the device 500 further includes:

[0174] An obtaining module, configured to obtain the accounting entry stored corresponding to the charging scenario code; and obtain the account type code from the accounting entry.

[0175] The account number generation device provided in this embodiment can execute the technical solutions of the corresponding method embodiment, and its implementation principle and technical effects are similar to those of the corresponding method embodiment, which will not be elaborated here.

[0176] The embodiments of the present application further provide an accounting device and a service acceptance device. Optionally, both the accounting device and the service acceptance device are electronic devices. Exemplarily, the electronic device is a server, a blade server, a distributed server, a server cluster, or other suitable servers.

[0177] Figure 8 FIG. 4 is a schematic structural diagram of an electronic device shown according to an exemplary embodiment. As Figure 8 shown, the electronic device 600 includes: a processor 601, and a memory 602 and a transceiver 603 that are communicatively connected to the processor 601 respectively.

[0178] The memory 602 stores computer-executable instructions; the transceiver 603 is configured to transmit and receive data between the accounting device or the service acceptance device. Exemplarily, when the electronic device is an accounting device, the transceiver 603 is configured to transmit and receive data with the service acceptance device; when the electronic device is a service acceptance device, the transceiver 603 is configured to transmit and receive data with the accounting device.

[0179] The processor 601 executes the computer-executable instructions stored in the memory 602 to implement the account number generation method provided by the present application.

[0180] Wherein, in the embodiments of the present application, the memory 602 and the transceiver 603 are respectively connected to the processor 601 through a bus. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity, only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.

[0181] The components shown herein, their connections and relationships, and their functions are merely exemplary and are not intended to limit the implementation of the present application described herein and / or claimed. The various components are interconnected using different buses and can be mounted on a common motherboard or otherwise as needed.

[0182] In an exemplary embodiment, a computer-readable storage medium is further provided. The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the account number generation method provided by the present application.

[0183] In an exemplary embodiment, a computer program product is further provided, including computer-executable instructions that, when executed by a processor, are used to implement the account number generation method provided in this application.

[0184] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0185] Furthermore, it should be noted that although the steps in the flowchart are sequentially shown according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limitation, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0186] It should be understood that the above device embodiments are illustrative, and the devices of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0187] In addition, without special description, in each embodiment of this application, each functional unit / module can be integrated in one unit / module, or each unit / module can exist physically alone, or two or more units / modules can be integrated together. The above integrated unit / module can be implemented in the form of hardware or in the form of a software program module.

[0188] When an integrated unit / module is implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a controller, a microcontroller, a microprocessor, or other electronic components. Unless otherwise specified, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as a USB flash drive, a Random-Access Memory (RAM), a Static Random-Access Memory (SRAM), a Dynamic Random-Access Memory (DRAM), an Enhanced Dynamic Random-Access Memory (EDRAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an Erasable Programmable Read-Only Memory (EPROM), a Programmable Read-Only Memory (PROM), a Read-Only Memory (ROM), a Resistive Random Access Memory (RRAM), a High-Bandwidth Memory (HBM), a Hybrid Memory Cube (HMC), a magnetic memory, a flash memory, a disk, an optical disk, a mobile hard disk, or a magnetic disk, etc., which are various media that can store program codes.

[0189] When the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of this application.

[0190] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as within the scope described in this specification.

[0191] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily think of other implementation manners of this application. This application is intended to cover any variations, uses, or adaptive changes of this application. These variations, uses, or adaptive changes follow the general principles of this application and include the common general knowledge or conventional technical means in this technical field not disclosed in this application. The specification and the embodiments are only regarded as exemplary, and the true scope and spirit of this application are pointed out by the following claims.

[0192] It should be understood that this application is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is only limited by the appended claims.

Claims

1. An account number generation method, characterized in that, Applied to accounting devices, including: Receiving an account opening request sent by a service acceptance device; the account opening request carries multiple element information of a target accounting service, and the multiple element information includes first type of element information and second type of element information, where the first type of element information has a readable feature, and the length of each element information in the first type of element information is fixed; at least part of the element information in the second type of element information has a non-fixed length; Determining a first part of a target account number according to the first type of element information, and determining a second part of the target account number according to the second type of element information, so that the second parts of the account numbers of each account are different; the first part has a first preset length, and the second part has a second preset length; Determining the target account number according to the first part and the second part; Sending the target account number to the service acceptance device, so that the service acceptance device processes the target accounting service based on the target account number.

2. The method according to claim 1, characterized in that, The determining a first part of a target account number according to the first type of element information, and determining a second part of the target account number according to the second type of element information includes: If the number of element information included in the first type of element information is one, determining the element information included in the first type of element information as the first part; if the number of element information included in the first type of element information is at least two, splicing the element information included in the first type of element information to obtain the first part; Splicing the element information in the second type of element information to obtain a first hash value; Encoding the first hash value using a preset encoding algorithm to obtain a second hash value; If the length of the second hash value is greater than the second preset length, compressing the second hash value to obtain the second part.

3. The method according to claim 1, wherein The determining the target account number according to the first part and the second part includes any one of the following: Splicing the first part and the second part to obtain the target account number; Splicing the first part, the second part and a reserved bit to obtain the target account number.

4. The method according to claim 1, wherein After determining the target account number according to the first part and the second part, the method further includes: Correspondingly storing the target account number and the multiple element information in a database, so that the service acceptance device locates the target account number from the database based on the multiple element information.

5. A method for generating an account number, characterized in that, Applied to service acceptance devices, including: Receiving a accounting request for a target accounting service sent by a gateway device; the accounting request carries the second type of element information of the target accounting service, and at least part of the element information in the second type of element information has a non-fixed length; Performing account number location based on the multiple element information of the target accounting service, where the multiple element information includes first type of element information and the second type of element information, the first type of element information has a readable feature, and the length of each element information in the first type of element information is fixed; If the account number cannot be located, send an account opening request to the accounting device. The account opening request carries the multiple element information, so that the accounting device determines the first part of the target account number according to the first type of element information and determines the second part of the target account number according to the second type of element information, and determines the target account number according to the first part and the second part; Receive the target account number sent by the accounting device; Process the target accounting transaction based on the target account number.

6. The method according to claim 5, wherein The locating the account number based on the multiple element information of the target accounting transaction includes: Locate the account number stored corresponding to the multiple element information from the cache space; If the account number cannot be located from the cache space, locate the account number stored corresponding to the multiple element information from the database.

7. The method according to claim 6, characterized in that, After receiving the target account number sent by the accounting device, the method further includes: Store the target account number into the cache space and the database respectively.

8. The method according to claim 5, wherein The accounting request further carries the accounting scenario code of the target accounting transaction, and the first type of element information includes the account type code; before locating the account number based on the multiple element information of the target accounting transaction, the method further includes: Obtain the accounting entry stored corresponding to the accounting scenario code; Obtain the account type code from the accounting entry.

9. An account number generation device, characterized in that, The [device] is set in the account device, including: A receiving module, configured to receive an account opening request sent by the service acceptance device; the account opening request carries multiple element information of the target accounting transaction, and the multiple element information includes the first type of element information and the second type of element information, wherein the first type of element information has a readable feature, and the length of each element information in the first type of element information is a fixed length; at least part of the element information in the second type of element information has a non-fixed length; A first determination module, configured to determine the first part of the target account number according to the first type of element information and determine the second part of the target account number according to the second type of element information, so that the second parts of the account numbers of each account are different; the first part has a first preset length, and the second part has a second preset length; A second determination module, configured to determine the target account number according to the first part and the second part; A sending module, configured to send the target account number to the service acceptance device, so that the service acceptance device processes the target accounting transaction based on the target account number.

10. An account number generation device, characterized in that, The [device] is set in the service acceptance device, including: A receiving module, configured to receive an accounting request for a target accounting transaction sent by the gateway device; the accounting request carries the second type of element information of the target accounting transaction, and at least part of the element information in the second type of element information has a non-fixed length; A locating module, configured to locate the account number based on the multiple element information of the target accounting transaction, where the multiple element information includes the first type of element information and the second type of element information, the first type of element information has a readable feature, and the length of each element information in the first type of element information is a fixed length; A sending module, configured to send an account opening request to an accounting device if the account number is not located, where the account opening request carries the multiple element information, so that the accounting device determines the first part of the target account number according to the first type of element information, determines the second part of the target account number according to the second type of element information, and determines the target account number according to the first part and the second part; The receiving module is further configured to receive the target account number sent by the accounting device; A processing module, configured to process the target accounting business based on the target account number.

Images