Digital currency red envelope management method and system

Abstract

The embodiment of the invention provides a digital currency red envelope management method and system, and the method comprises the steps: a wallet service platform receives and responds to a login request of a user for logging in a digital currency red envelope light application, and recognizes a light application user group to which the user belongs; under the condition that the user group is a stock user or a new user beyond the login-free validity period, the wallet service platform determines whether a number recycling and reusing condition exists or not according to the authorized login time of the counting currency red envelope light application, the current login time and the registration time of registering the counting currency application account; under the condition that checking is determined, responding to a checking result of number recycling and reusing, and triggering to check the identity of the user; and the wallet service platform responds to a result of passing the identity verification, camps on the counting currency red envelope and prompts the user to register a counting currency application account. The technical problem that digital currency red envelopes are mistakenly taken due to secondary number allocation is solved.

Description

Technical Field

[0001] Embodiments of this disclosure relate to methods, systems, electronic devices, and readable storage media for managing digital currency red envelopes. Background Technology

[0002] With the rapid development of mobile internet and digital payment technologies, mobile phone number-based account systems have become a core infrastructure in the fintech field. The "secondary number release" mechanism prevalent in telecommunications services (i.e., telecom operators reclaiming cancelled numbers and re-releasing them into the market) has led to new types of identity authentication conflicts.

[0003] For example, in existing technologies, digital RMB cash red envelope products typically rely on mobile phone numbers as the core identifier of user identity, combined with methods such as SMS verification codes to authorize the issuance and receipt of cash red envelopes. This model can meet basic needs in conventional scenarios, but in scenarios involving the re-issuance of numbers, it is prone to the risk of digital RMB cash red envelopes being incorrectly claimed, leading to data conflicts. Summary of the Invention

[0004] At least one embodiment of this disclosure provides a method for managing digital currency red envelopes. The method includes: a digital currency wallet service platform receiving and responding to a user's login request for a digital currency red envelope mini-application, identifying the user's mini-application user group, wherein the digital currency red envelope mini-application obtains the user's mobile communication number through a host platform to authorize login and receive digital currency red envelopes; if the user's mini-application user group is an existing user outside the validity period of the login exemption or a new user, the digital currency wallet service platform determines whether to verify whether the mobile communication number has been recycled and reused after the registration time, based on the authorized login time of the digital currency red envelope mini-application authorized by the host platform, the current login time, and the registration time of the digital currency application account registered using the mobile communication number; if verification is determined, the digital currency wallet service platform, in response to the verification result of the mobile communication number being recycled and reused, triggers an identity verification process for the mobile communication number to verify the user's identity; and in response to the successful identity verification, the digital currency wallet service platform pre-claims digital currency red envelopes and prompts the user to register a digital currency application account.

[0005] At least one embodiment of the present disclosure provides a digital currency red envelope management system, which comprises a digital currency wallet service platform, the digital currency wallet service platform comprising: a user group identification module configured to receive and respond to a login request of a user logging into a digital currency red envelope light application, and identify a light application user group to which the user belongs, wherein the digital currency red envelope light application obtains a mobile communication number of the user through a host platform to authorize login to receive a digital currency red envelope; a number recycling judgment module configured to, in a case where the light application user group to which the user belongs is a stock user or a new user outside a login exemption valid period, determine whether to check a number recycling reuse situation of the mobile communication number after a registration time according to an authorized login time of the host platform authorizing login to the digital currency light application, a current login time and the registration time of the mobile communication number registering a digital currency application account; an identity verification module configured to, in a case where it is determined to check, trigger an identity verification process to verify the identity of the user in response to a check result that the mobile communication number has number recycling reuse; and a red envelope management module configured to, in response to a result that the identity verification is passed, preoccupy a digital currency red envelope and prompt the user to register a digital currency application account.

[0006] At least one embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a memory storing one or more computer program modules; wherein the one or more computer program modules are configured to be executed by the one or more processors to implement the method provided by at least one embodiment of the present disclosure.

[0007] At least one embodiment of the present disclosure provides a computer-readable storage medium for storing non-transitory computer-readable instructions, wherein the non-transitory computer-readable instructions, when executed by one or more processors, implement the method provided by at least one embodiment of the present disclosure.

[0008] The digital currency red envelope management scheme of the present disclosure embodiment solves the technical problem of incorrect receipt of a digital RMB red envelope caused by secondary number release in the prior art, identifies the number recycling reuse state through the digital currency wallet service platform and determines the target user who should receive the digital RMB red envelope, and provides key technical support for the application of digital currency business in the secondary number release scenario. BRIEF DESCRIPTION OF DRAWINGS

[0009] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure will be briefly introduced below. Obviously, the drawings described below only relate to some embodiments of the present disclosure, but not limit the present disclosure.

[0010] Figure 1 A block diagram of a digital currency red envelope management system according to at least one embodiment of the present disclosure is shown;

[0011] Figure 2 A block diagram of a digital currency wallet service platform is shown according to at least one embodiment of the present disclosure;

[0012] Figure 3 A flowchart of a management method of a digital currency red packet is shown according to at least one embodiment of the present disclosure;

[0013] Figure 4 A flowchart of another management method of a digital currency red packet is shown according to at least one embodiment of the present disclosure;

[0014] Figure 5 A flowchart of a management method of a digital currency application account is shown according to at least one embodiment of the present disclosure;

[0015] Figure 6 A flowchart of another management method of a digital currency application account is shown according to at least one embodiment of the present disclosure;

[0016] Figure 7 A flowchart of still another management method of a digital currency application account is shown according to at least one embodiment of the present disclosure;

[0017] Figure 8 A schematic diagram of an electronic device is shown according to at least one embodiment of the present disclosure;

[0018] Figure 9 A schematic diagram of a computer readable storage medium is shown according to at least one embodiment of the present disclosure. DETAILED DESCRIPTION

[0019] In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions of the embodiments of the present disclosure will be described clearly and completely below with reference to the drawings of the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by a person of ordinary skill in the art without any creative effort fall within the scope of protection of the present disclosure.

[0020] Unless otherwise defined, technical terms or scientific terms used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terms "first", "second", and similar terms are used herein to distinguish one element from another, and are not necessarily used in a sequence. Also, the terms "include", "comprise", and the like are used herein not to limit the components listed after these terms but to encompass the components listed after these terms and equivalents thereof. The terms "connected" and "coupled" and the like are used herein to indicate an electrical connection, either direct or indirect, between two or more elements, and can encompass wired and / or wireless connections.

[0021] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of the present disclosure to specific shapes, hardware, connection relationships, operations, values, conditions, data, sequences, etc. shown and described. Those skilled in the art can construct more embodiments not mentioned in the present specification by reading the present specification using the concept of the present disclosure.

[0022] The terms used in the present disclosure are those general terms currently widely used in the art in consideration of the functions in the present disclosure, but these terms can vary according to the intention of those of ordinary skill in the art, precedents, or new technology in the art. Also, specific terms can be chosen by the applicant, and in this case, the detailed meanings thereof will be described in the detailed description of the present disclosure. Therefore, the terms used in the specification should not be understood as simple names but based on the meanings of the terms and the overall description of the present disclosure.

[0023] Flowcharts are used in the present disclosure to illustrate operations performed by a system according to embodiments of the present disclosure. It should be understood that the foregoing or following operations are not necessarily performed in sequence. Rather, various steps can be processed in reverse order or simultaneously, as desired. Also, other operations can be added to these processes, or one or more steps can be removed from these processes.

[0024] First, the abbreviations and related terms related to the present disclosure are defined and explained.

[0025] User Equipment: mainly includes devices related to communication technology. Specifically, it includes any electronic device that a user can conveniently carry or operate, which can also provide remote communication capabilities with a network, such as a mobile communication terminal. The mobile communication terminal can communicate using a mobile phone (wireless) network, a wireless data network (e.g., 3G, 4G, 5G or similar network), Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), Wi-Max, or any other communication medium that can provide access to a network, such as the Internet or a private network. Specific examples include cell phone terminals, tablet computers, netbooks, laptop computers, wearable devices (such as smartwatches), and the like.

[0026] Digital currency red packet: for example, a digital RMB red packet, an electronic red packet issued in the form of digital RMB, which can include cash red packets (Cash Red Packets) and consumption red packets (Consumption Red Packet / Coupon), and in the embodiments of the present application, it mainly refers to cash red packets, such as digital RMB red packets issued by a digital RMB App personal user to other personal users.

[0027] Digital currency application account: can be simply referred to as "digital currency application account" or "digital currency account", a credential that can distinguish different users of an application program registered by a user using a mobile communication number such as a mobile phone number on a digital currency application program, and the user logs in to the account by mobile phone number, login password or biometric identification. For example, a digital RMB application account is an account registered by a user using a mobile phone number on a digital RMB application.

[0028] Digital currency wallet: as a carrier of digital currency (which can be simply referred to as "digital currency", referring to digital legal currency such as digital RMB) and a medium for reaching users. In form, it can be a soft wallet and a hard wallet. Among them, the soft wallet can be provided by the wallet service of the smart application supporting the digital currency, and the soft wallet can be understood as existing in the form of an application program (App). For example, the digital wallet of each digital currency operating institution in the digital currency App, the digital wallet in the App of each digital currency operating institution, etc. The hard wallet refers to a physical medium for storing digital currency opened through a counter or an electronic channel, a digital currency carrier with a secure element (Secure Element, SE), which also has basic functions such as redemption, withdrawal, deposit, withdrawal, consumption, transfer, inquiry, etc. For example, mobile phones with secure elements, NFC-SIM cards, IC cards, and wearable devices, etc. In the embodiments of the present disclosure, the digital currency wallet mainly refers to a soft wallet, which can be opened through a digital currency application program (such as a digital RMB App) to select one of the digital currency operating institutions designated by the central bank to open a digital currency wallet (hereinafter referred to as "wallet"), or through a digital currency operating institution to open a wallet.

[0029] Digital currency operators: Commercial banks or other institutions responsible for providing users with digital currency exchange and circulation services.

[0030] Digital Currency Interoperability Platform: This platform, often shortened to "Interoperability Platform," supports the transfer, clearing, and message exchange of digital currencies / electronic payments between the central bank and various operating institutions. It enables interoperability between the central bank and various operating institutions.

[0031] Digital currency wallet service platform: referred to as "wallet service platform" or "wallet management server", it is the back-end support system for digital currency applications (such as the digital RMB App) and wallet ecosystem management. It provides services such as user system, wallet information and user-wallet relationship, and provides standard wallet service capabilities and general product service capabilities (such as digital RMB red envelope products) to participating entities.

[0032] Mobile communication number: A unique combination of numbers used to identify user terminal equipment (such as mobile phones) in a mobile communication network. It is the basis for realizing communication functions such as voice, text message, and data. For example, a mobile phone number.

[0033] Number recycling and reuse: also known as "secondary number release", refers to the process where, after an old user stops using or abandons their mobile phone number, the number is reclaimed by the telecommunications operator and released back into the market for other users to use.

[0034] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in this publicly disclosed technical solution all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0035] In the existing scheme, if a new user obtains a secondary mobile number, and an existing user previously used that number to register a digital currency application account (e.g., an app account registered in the digital RMB application, hereinafter referred to as the "old account"), and / or the new user uses that secondary mobile number to register a new digital currency application account (hereinafter referred to as the "new account"), significant conflicts and impacts will arise when the new and old users conduct digital currency business. For example, when a sender of a digital RMB red envelope chooses a mobile number as the basis for distributing the red envelope, because that mobile number may be associated with different digital currency application accounts (new and old accounts), it is easy for the red envelope to be mistakenly sent to the wrong user. Similarly, the red envelope may be mistakenly received during the red envelope receiving process.

[0036] At least one embodiment of the present disclosure provides a digital currency red envelope management method and system, an electronic device and a storage medium. For the mobile phone number secondary release scenario, the secondary release state of the mobile communication number is identified through the digital currency wallet service platform, the target user who should receive the digital RMB red envelope is accurately positioned, and the technical problem of the digital currency red envelope mis-receiving caused by number recycling and reuse in the existing solution is effectively solved.

[0037] The embodiments of the present disclosure and some examples thereof are described in detail below with reference to the accompanying drawings.

[0038] Figure 1 A block diagram of a digital currency red envelope management system 1000 according to an embodiment of the present disclosure is shown. As shown, the system 1000 includes mainly a user device 120 and a digital currency wallet service platform (hereinafter referred to as "wallet service platform") 130. Among them, the user device 120 can communicate with the wallet service platform 130. Figure 1

[0039] For example, the messages between the user device 120 and the wallet service platform 130 can be sent through a communication network using a secure communication protocol, such as but not limited to: File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), etc. The communication network can include any one and / or combination of the following: direct interconnection, Internet, Local Area Network (LAN), Metropolitan Area Network (MAN), secure custom connection, Wide Area Network (WAN), wireless network, etc.

[0040] As shown in FIG. 1, the user device 120 can include a processor 121, a memory 122, a communication interface 123, and a digital currency red envelope management module 124. The processor 121, the memory 122, the communication interface 123, and the digital currency red envelope management module 124 can be connected through a bus or the like. Figure 1 ​As shown, the user device 120 can include a digital currency application (which can be referred to simply as a "digital currency App" or "digital currency App", such as a digital RMB App) 1200. The digital currency App can be a mobile application provided by a digital currency issuer (such as a central bank) that provides full life cycle management functions of a digital currency wallet, and can communicate with the digital currency wallet server 130 during use to connect and interact with data. The digital currency App 1200 provides a user interaction page (UI) for performing a digital currency transaction or digital currency application account management to the user through the display module of the user device 120, and can receive data and instructions from the wallet service platform 130 to perform corresponding processing. The user device 120 can include a host platform (not shown) with social application attributes, such as WeChat, QQ, Alipay, and other social platform Apps. The user can send a digital RMB red envelope link through these social platform Apps, and the red envelope recipient can log in to the digital currency red envelope light application 1210 through the authorization of these host platforms to receive the red envelope. The digital currency red envelope light application 1210 is a lightweight application that runs on the third-party host platforms of WeChat, QQ, Alipay, etc., and is used to receive digital currency red envelopes (such as digital RMB red envelopes) in a social scenario. In some embodiments of the present disclosure, the digital currency red envelope light application includes a digital currency red envelope applet and / or a digital currency red envelope H5 page for performing the receiving of digital currency red envelopes. For example, if the issuer shares the red envelope link through the WeChat platform, the recipient clicks the link to enter the "digital RMB red envelope" applet, logs in through the mobile phone number associated with the registered digital RMB application account, and can receive the red envelope, which will be stored in the corresponding digital RMB wallet. For example, if the issuer shares the red envelope link to the QQ, Alipay, and other platforms, the recipient clicks the link to enter the "digital RMB red envelope" H5 page, logs in by inputting the mobile phone number associated with the registered digital RMB application account, and can receive the red envelope, which will be stored in the corresponding digital RMB wallet.

[0041] The wallet service platform 130 is a wallet backend computer system of the digital currency issuer (such as the central bank) that manages digital currency application accounts and digital currency wallets. The user can interact with the wallet service platform 130 through the digital currency application 1200 and the digital currency red envelope light application 1210 on the user device 120 to implement the distribution and receipt of digital currency red envelopes. For example, during the process of receiving a digital currency red envelope, after the recipient initiates a login request to log in to the digital currency light application 1210 through the host platform, the wallet service platform 130 identifies the user group of the light application to which the user belongs, and performs corresponding process operations according to the user group to ensure that the target user receives the digital currency red envelope and prevent the red envelope from being received due to secondary number distribution.

[0042] Figure 3A flowchart of a management method 400 of a digital currency red packet according to at least one embodiment of the present disclosure is shown. The method 400 is mainly in the scenario of secondary number allocation, and the user takes a digital currency red packet through a digital currency red packet light application 1210, such as a digital currency red packet applet or an H5 page, to take a digital currency red packet. When the user is identified as a stock user or a new user outside the login-free valid period, the corresponding processing logic is executed. The method steps of the embodiments of the present disclosure will be described below with reference to Figure 1 and Figure 3 .

[0043] In step S410, the wallet service platform 130 receives and responds to the login request of the user logging into the digital currency red packet light application 1210, and identifies the light application user group to which the user belongs. The digital currency light application 1210 obtains the mobile communication number of the user through the host platform to authorize the login to take the digital currency red packet.

[0044] In step S420, the wallet service platform 130 executes step S430 in the case where the light application user group to which the user belongs is a stock user or a new user outside the login-free valid period.

[0045] In step S430, according to the authorized login time of the host platform authorizing the login to the digital currency red packet light application, the current login time, and the registration time of the digital currency application account registered by using the mobile communication number, it is determined whether the mobile communication number is reused after the registration time. If yes, step S440 is executed.

[0046] In step S440, the wallet service platform 130 determines to check the mobile communication number in the case of checking, and triggers an identity verification process for the user according to the checking result of the mobile communication number.

[0047] In step S450, the wallet service platform 130 preoccupies the digital currency red packet and prompts the user to register the digital currency application account in response to the result of the identity verification passing.

[0048] In step S410, for example, when the issuer shares the digital RMB cash red envelope in the form of "group red envelope" to the WeChat platform, the recipient clicks the red envelope link to receive the red envelope through the digital currency red envelope applet. When logging in to the digital currency red envelope applet for the first time, the recipient clicks the red envelope link through the WeChat platform, which triggers an authorization request to obtain user information (mainly including the mobile phone number associated with the WeChat account) to authorize the login of the digital currency red envelope applet. After the recipient authorizes, the applet sends the OpenID (unique identifier of the user identity) obtained from the WeChat platform to the wallet service platform 130, the wallet service platform 130 generates a random string or a JWT format login-free token (Token), and sets the login-free valid period (for example, 30 days), and returns the login-free token to the applet for local caching. In another example, when the user shares the digital RMB cash red envelope in the form of "group red envelope" to the Alipay platform, the red envelope will be received through the digital currency red envelope H5 page. When clicking the digital currency red envelope H5 page to receive the red envelope, the user needs to input the mobile phone number to authorize the login. After login, the login-free token (with a login-free valid period, for example, 30 days) is issued and cached locally.

[0049] For example, in some embodiments of the present disclosure, the light application user group includes inventory users within the login-free valid period, inventory users outside the login-free valid period, and new users. For example, when the user opens the digital currency red envelope applet or the digital currency red envelope H5 page, it is queried whether there is a valid login-free token in the local cache. If there is and it is not expired, it is confirmed that the user is an inventory user within the login-free valid period; if it is expired or invalid, it is confirmed that the user is an inventory user outside the login-free valid period, and a re-login process can be triggered. It is easy to understand that if there is no login-free token in the local cache, it is confirmed that the user is a new user, and a new user login process needs to be performed.

[0050] For example, in some embodiments of the present disclosure, the authorized login time generally refers to the time of first login of the digital currency red packet light application. The determination step of the time includes: if the user initiates a request for obtaining the digital currency red packet without changing the mobile communication number, the time of the host platform (first) authorized login of the digital currency red packet light application is taken as the authorized login time; if the user changes the mobile communication number and initiates a request for obtaining the digital currency red packet, the time of the user changing the mobile communication number is taken as the authorized login time. Taking the WeChat platform as an example, generally, the authorized login time can be the time stamp of the user clicking the authorized login button to trigger the login process, or the time stamp of the wallet service platform 130 successfully verifying the login and generating the login state. The wallet service platform 130 can store the time stamp in association with the OpenID and the WeChat bound mobile phone number. If the user changes the mobile phone number, the time stamp marked when the user updates the mobile phone number field after the verification code is verified is taken as the authorized login time. In this way, the authorized login time can be accurately located, the accuracy of the data is guaranteed, and support is provided for the selection and execution of subsequent processes.

[0051] In the embodiments of the present disclosure, the registration time refers to the time stamp of registering the digital currency application account by using the mobile communication number. For example, the wallet service platform 130 queries that there are multiple digital currency application account IDs associated with the target mobile communication number, which can include secondary number release old accounts, secondary number release new accounts and accounts in different states. The secondary number release old account refers to an account registered before the secondary number release and still in an effective association state after the secondary number release. The secondary number release new account refers to an account registered after the secondary number release and in an effective association state. In the embodiments of the present disclosure, the registration time can be the time stamp of the associated mobile phone number of the secondary number release old account or the secondary number release new account.

[0052] If it is identified in step S420 that the light application user group to which the user belongs is a stock user or a new user outside the login-free valid period, the authorized login time and the registration time are compared in sequence.

[0053] For example, according to some embodiments of the present disclosure, in the step S430, in the step of determining whether to check the case of number recycling reuse of the mobile communication number after the registration time, it comprises: if the authorized login time is after the registration time, judging whether the time difference between the current login time and the registration time exceeds the set time threshold, wherein if the time difference exceeds the set time threshold, checking whether the mobile communication number has the case of number recycling reuse after the registration time. According to some embodiments of the present disclosure, if the time difference is less than the set time threshold, the login is successful, and the user is allowed to receive the digital currency red packet. The above scenario example can be: the old user registers the digital currency application account before the second number release, and the new user does not register the account and directly authorizes the login of the WeChat mini-program to receive the red packet. In this scenario example, the registration time refers to the time when the old user registers the digital currency application account, and the current login time refers to the time when the new user logs in to the digital currency application account.

[0054] For example, according to some embodiments of the present disclosure, the digital currency wallet service platform 130 responds to the checking result of the mobile communication number without number recycling reuse, and then the login is successful, and the user is allowed to receive the digital currency red packet.

[0055] In one example, the set time threshold can be the number recycling idle time set by the telecom operator, for example, 180 days. After the mobile phone number is cancelled, the number is not immediately released for the second time, but is idle for a period of time before being put back into the sales system. The number recycling idle time can reduce the risk faced by new users when using the second number to a certain extent, such as reducing the possibility of new users logging in to the original owner's account and receiving the original owner's information, and to a certain extent, ensuring the use experience and information security of new users.

[0056] For example, when the authorized login time is later than the registration time, it indicates that the user's authorized login behavior occurs after the registration of the digital currency application account, and then the time interval between the two times is calculated, and it is judged whether it exceeds the set time threshold. If the user does not log in after the registration exceeds the set time threshold, there can be two cases at this time: (1) the user normally uses it, but has not logged in for a long time; (2) the old user registers the digital currency application account associated with the mobile phone number before the second number release, and the new user obtains the mobile phone number through the second number release and tries to log in using the mobile phone number. Since the above situation has the possibility of second number release, the wallet service platform 130 determines that it is necessary to check whether the mobile phone number has the case of second number release after the registration time. If there is a second number release, it is determined to be case (2), and the short message verification can be performed to prove that the current user is the holder of the mobile phone number. If there is no second number release, it is determined to be case (1), the login is successful, and the digital currency red packet is allowed to be received.

[0057] In one example, the wallet service platform 130 has a secondary number release verification mechanism, which verifies whether the mobile communication number has been released after the "digital currency application account registration time point" by calling the secondary number release query interface of the corresponding communication operator of the mobile communication number. If it is detected that the mobile communication number is associated with multiple digital currency application accounts, the registration time point of the latest associated account is sent to the communication operator as the "digital currency application account registration time point" to make it find out whether the secondary number release has occurred after the time point, and the returned verification result is returned. In another example, the wallet service platform 130 can query the local preset number recycling information library (or local cache) to determine whether the current mobile communication number is recorded therein. The preset number recycling information library stores the secondary number release mobile number and the secondary number release time sent by the secondary number release query interface of the communication operator, and / or the secondary number release mobile number and the secondary number release time synchronously sent by the servers of various operating agencies.

[0058] For example, in step S440, after confirming that the mobile number is a secondary number release, the user's identity is verified by sending, for example, a short message verification code, and then the legitimacy of the current mobile number holder is confirmed, and the data authority of new and old users is isolated to avoid account confusion, privacy leakage or security risks caused by number recycling. Alternatively, in other embodiments, face recognition detection can also be added to verify that the current user is the mobile number holder.

[0059] For example, according to some embodiments of the present disclosure, in step S440, when the wallet service platform 130 receives a verification result indicating that the mobile communication number is a number recycling reused resource, if the user's identity verification is passed in step S450, the digital currency application account associated with the mobile communication number before the number recycling reuse (also referred to as "old account") is also marked for processing, and the login state of the digital currency application account can also be identified. It should be noted that the old account is associated with the mobile communication number before the number recycling reuse, and is in an effective association state after the number recycling reuse. The "pre-occupied" digital currency red packet means that the wallet service platform 130 records the red packet under the corresponding mobile communication number, and then stores the red packet in the digital currency wallet associated with the digital currency application account after the user registers a new digital currency application account with the mobile communication number and opens a digital currency wallet, and the red packet is used in subsequent digital currency business.

[0060] For example, according to some embodiments of the present disclosure, in step S420, in the step of determining whether to check the case of number recycling reuse after the registration time, it comprises: if the LAG user group is the inventory user outside the login effective period, and the authorized login time is before the registration time, it is judged whether the time difference between the authorized login time and the registration time exceeds the set time threshold, wherein if the time difference exceeds the set time threshold, the mobile communication number is not checked for the case of number recycling reuse after the registration time, and the identity verification process is triggered to verify the identity of the user; in response to the result of passing the identity verification, the login is successful, and the user is allowed to receive the digital currency red packet. The above scenario example can be: an old user has not registered a digital currency application account and authorizes to log in to the WeChat mini-program to receive a red packet (at this time, the background is pre-occupied with a red packet), and a new user obtains a mobile phone number and registers a digital currency application account before authorizing to log in to the WeChat mini-program, at this time, the authorized login time is before the account registration time.

[0061] For example, according to some embodiments of the present disclosure, the digital currency wallet service platform 130 responds to the judgment result that the time difference is less than the set time threshold, and then the login is successful, and the user is allowed to receive the digital currency red packet.

[0062] In one example, if the user authorizes to log in and then registers a digital currency application account after exceeding the set time threshold, at this time, the login may have the following cases: the digital currency application account is a new account newly registered by a new user through secondary number allocation, and an old user has not registered a digital currency application account before secondary number allocation. Therefore, when it is confirmed that the time difference between the authorized login time and the registration time exceeds the set time threshold, the above case is defaulted, and then secondary number allocation is not checked, and the user is guided to perform identity verification by using, for example, a short message verification method. If the verification is successful, the new user logs in successfully and is allowed to receive the digital currency red packet; if the verification fails, the digital currency red packet cannot be received. If the time difference between the authorized login time and the registration time is within the set time threshold, it is considered that the secondary number allocation is not involved, and the login is directly successful and the red packet is received.

[0063] Figure 4 A flowchart of another method 400' for managing a digital currency red packet according to at least one embodiment of the present disclosure is shown. The method 400' mainly corresponds to the processing logic when a user is identified as an inventory user within the login effective period through a digital currency red packet light application 1210, such as a digital currency red packet mini-program or H5 page, to receive a red packet in the scenario of secondary number allocation. The method steps of the embodiments of the present disclosure will be described below with reference to Figure 1 and Figure 4

[0064] ​In step S410, the wallet service platform 130 receives and responds to the login request of the user logging in the digital currency red packet light application 1210, and identifies the light application user group to which the user belongs. This step is consistent with the corresponding step of the previous embodiment, and will not be described here.

[0065] In step S420, if the light application user group to which the user belongs is the inventory user within the free login valid period, step S460 is executed. In this step, the user group can be judged in combination with multi-dimensional information such as time window, device identifier, login state validity, etc.

[0066] When the user clicks to log in the applet, it is judged whether the free login token is cached locally. If it exists, it is judged whether the token is legal (login state validity). If it is valid, it is judged whether it is within the free login period (time window). If it is judged to be within the free login period, the device identifier (including, for example, the WeChat identifier of the applet side and the device fingerprint of the device side) of the user device is matched and judged. After matching, it is determined that the current user is the inventory user within the free login valid period.

[0067] In step S460, it is judged whether the first digital currency application account associated with the free login token and the second digital currency application account associated with the mobile communication number are consistent.

[0068] In step S460, if the first digital currency application account and the second digital currency application account are consistent, the user is allowed to claim the digital currency red packet (S470); otherwise, the association between the free login token and the first digital currency application account is cleared, and the new user login process is entered (S480).

[0069] As described above, when logging in the digital currency red packet applet through the WeChat platform authorization, for example, the wallet service platform 130 generates a free login token and returns it to the applet and caches it locally on the user device 120. Correspondingly, the wallet service platform 130 also stores the token and the digital currency account associated with the authorized login mobile phone number together. After the wallet service platform 130 obtains the free login token, it queries whether the first digital currency application account corresponding to the token is consistent with the second digital currency application account corresponding to the previously authorized login mobile phone number. Generally, for normal inventory users, because the user has previously authorized login to the applet through the same mobile phone number and has not changed the mobile phone number, the digital currency application account associated with the free login token should be completely consistent with the digital currency application account bound to the previously authorized login mobile phone number in the case of valid free login token. The user is automatically verified, and after clicking the applet, the user can directly claim the digital currency red packet without additional operation.

[0070] For example, in the following scenario, the account inconsistency may occur: the old user is still in the free login period, the mobile phone number has been released twice, and the new user has registered a new digital currency application account using the mobile phone number. When the old user logs in to the applet to receive the digital currency red packet, the mobile phone number authorized for login is bound to another digital currency application account, and the digital currency application account associated with the free login token is inconsistent with this digital currency application account. For this scenario, the wallet service platform 130 clears the association between the token and the digital currency application account, and triggers the user to re-authorize the mobile phone number to log in to the applet to receive the red packet. At this time, the old user also needs to be reminded to modify the mobile phone number bound to the digital currency application account to prevent conflicts with the digital currency application account registered by the new user using the same mobile phone number when conducting digital currency business.

[0071] For example, in some embodiments of the present disclosure, the above method further comprises: the wallet service platform 130, in response to a user's request for issuing a digital currency red packet initiated by a digital currency application program, querying the digital currency application account associated with the mobile communication number in the request, and if the number of digital currency application accounts is more than one, sending a prompt message to the digital currency application program to prompt the user to issue a digital currency red packet through a host platform, which has a social application attribute.

[0072] In one example, the function of querying the digital currency application account associated with the mobile phone number is added when the user issues a "dedicated red packet" of digital RMB. Specifically, after the user who issues the "dedicated red packet" fills in the recipient's mobile phone number in the page of the digital currency app 1200 and clicks the "put into red packet" button, the wallet service platform 130 queries whether the recipient's mobile phone number corresponds to multiple digital currency application accounts. If the filled-in mobile phone number corresponds to only one digital currency application account, the subsequent process of issuing a red packet is entered; if the corresponding digital currency application accounts exceed two, a pop-up window is displayed in the page to prompt "The following mobile phone number is associated with multiple digital RMB APP accounts. You can choose to issue a "group red packet" and share the red packet with designated friends through WeChat / QQ / Alipay". Because after issuing a "group red packet", the issuer needs to share the red packet link to his own social platform chat box to clearly indicate the user or group receiving the red packet, so that the error of issuing the red packet can be avoided.

[0073] Figure 2 A block diagram of a digital currency wallet service platform 130 according to at least one embodiment of the present disclosure is shown. The digital currency wallet service platform 130 is described below with reference to Figure 2

[0074] As Figure 2 ​As shown, the wallet service platform 130 includes a user group identification module 130A, a number recycling judgment module 130B, an identity verification module 130C, and a red envelope management module 130D. The user group identification module 130A is configured to receive and respond to a login request of a user logging into a digital currency red envelope light application, and identify a light application user group to which the user belongs, wherein the digital currency red envelope light application obtains a mobile communication number of the user through a host platform to authorize login to receive a digital currency red envelope; the number recycling judgment module 130B is configured to, in a case where the light application user group to which the user belongs is a stock user or a new user outside a login-free valid period, determine whether to check a case where the mobile communication number is recycled and reused after a registration time according to an authorized login time of the host platform authorizing login to the digital currency light application, a current login time, and the registration time of the mobile communication number registering a digital currency application account; the identity verification module 130C is configured to, in a case where it is determined to check, trigger an identity verification process for the mobile communication number in response to a check result that the mobile communication number is recycled and reused, and verify the identity of the user; and the red envelope management module 130D is configured to, in response to a result that the identity verification is passed, mark a digital currency application account associated with the mobile communication number before the number recycling and reuse, preoccupy a digital currency red envelope, and prompt the user to register a digital currency application account.

[0075] For example, according to some embodiments of the present disclosure, the number recycling judgment module 130B is further configured to determine the authorized login time by performing the following operations: if the user initiates a request for the digital currency red envelope without changing the mobile communication number, the time at which the host platform authorizes login to the digital currency red envelope light application is taken as the authorized login time; and if the user changes the mobile communication number and initiates a request for the digital currency red envelope, the time at which the user changes the mobile communication number is taken as the authorized login time.

[0076] For example, according to some embodiments of the present disclosure, the number recycling judgment module 130B is further configured to perform the following operations: if the authorized login time is after the registration time, it is determined whether a time difference between the current login time and the registration time exceeds a set time threshold, wherein if the time difference exceeds the set time threshold, it is checked whether the mobile communication number is recycled and reused after the registration time; and if the time difference is less than the set time threshold, the login is successful, and the user is allowed to receive the digital currency red envelope.

[0077] For example, according to some embodiments of the present disclosure, the number recovery judgment module 130B is further configured to perform the following operation: if the light application user group is the inventory user outside the login-free valid period, and the current login time is before the registration time, then judge whether the time difference between the first authorized login time and the registration time exceeds the set time threshold, wherein if the time difference exceeds the set time threshold, then do not check whether the mobile communication number is reused after the registration time, trigger the identity verification process to verify the identity of the user; in response to the result of the identity verification, the login is successful, and the user is allowed to receive the digital currency red packet.

[0078] For example, according to some embodiments of the present disclosure, the red packet management module 130D is further configured to perform the following operation: in response to the check result that the mobile communication number is not reused or the judgment result that the time difference is less than the set time threshold, the login is successful, and the user is allowed to receive the digital currency red packet.

[0079] For example, according to some embodiments of the present disclosure, the red packet management module 130D is configured to perform the following operation: if the user belongs to the inventory user within the login-free valid period, then judge whether the first digital currency application account associated with the login-free token is consistent with the second digital currency application account associated with the mobile communication number, wherein if the first digital currency application account and the second digital currency application account are consistent, then the user is allowed to receive the digital currency red packet; otherwise, the association between the login-free token and the first digital currency application account is cleared, and the new user login process is entered.

[0080] For example, according to some embodiments of the present disclosure, the red packet management module 130D is further configured to perform the following operation: in response to the user's request for issuing a digital currency red packet initiated by the digital currency application program, the digital currency application account associated with the mobile communication number in the issuing request is queried, and if the number of digital currency application accounts is multiple, then the prompt information is sent to the digital currency application program to prompt the user to issue the digital currency red packet through the host platform, and the host platform has a social application attribute.

[0081] The additional aspects of the wallet service platform 130 according to at least one of the embodiments of the present disclosure can correspond to the additional aspects of the management method 400, 400' of the digital currency red packet according to at least one of the embodiments of the present disclosure, and therefore the technical effects of the additional aspects of the management method 400, 400' according to at least one of the embodiments of the present disclosure can also be mapped to the additional aspects of the management method 400, 400' according to at least one of the embodiments of the present disclosure, which will not be repeated here.

[0082] In addition, in some embodiments of this disclosure, a method for managing digital currency application accounts (old accounts) marked in step S450 above is also provided, as detailed below. Figures 5 to 7 Related content.

[0083] Figure 5 A flowchart of a method 200 for managing digital currency application accounts according to at least one embodiment of this disclosure is shown. Method 200 primarily addresses scenarios involving secondary account allocation, where existing users registered digital currency application accounts using the same mobile number before the secondary allocation. When new users with the secondary allocated mobile number register new digital currency application accounts or open new digital currency wallets through the Digital Currency App 1200, this method provides a way to ensure that new users can normally use digital currency services, while also providing existing users with an operable path to change the mobile number associated with their digital currency application account / digital currency wallet, thus avoiding conflicts between old and new accounts. The following references... Figure 5 The method steps of the embodiments of this disclosure will be explained.

[0084] In step S210, when the wallet service platform 130 detects that the mobile communication number is a resource for number recycling, it determines whether the mobile communication number is associated with a digital currency application account and a digital currency wallet.

[0085] In step S220, when the mobile communication number is associated with the first digital currency application account (old account), the first digital currency application account is marked and its login status is identified. The first digital currency application account is a digital currency application account that was associated with the mobile communication number before the number was recycled and reused, and is in a valid association state after the number was recycled and reused.

[0086] When the verification result indicates that the mobile communication number is a recycled and reused resource, the wallet service platform 130 marks and identifies the login status of the first digital currency application account associated with the mobile communication number. It should be noted that the first digital currency application account was associated with the mobile communication number before the number was recycled and reused, and remains in a valid association state after the recycling and reuse. For example, the wallet service platform 130 may find multiple digital currency application account IDs associated with the number, which may include accounts in different states such as old accounts from secondary number releases and new accounts from secondary number releases. Old accounts from secondary number releases refer to accounts registered before the secondary number release and still in a valid association state after the secondary number release; new accounts from secondary number releases refer to accounts registered after the secondary number release and in a valid association state. In this embodiment, the wallet service platform 130 only needs to mark and identify the login status of old accounts from secondary number releases.

[0087] In the example of the marking process, when the wallet service platform 130 confirms that the mobile communication number belongs to the secondary number resource through the data interface of the communication operator or the preset number recycling information library, a special identification tag will be added to the first digital currency application account associated with the mobile communication number in the local account database. The tag can contain detailed marking information, such as the specific time of number recycling, the timestamp of the marking operation, and the trigger reason for the marking, etc. In addition, the wallet service platform 130 will also synchronize this marking information to each subsystem or module associated with the account, including but not limited to the account login verification module, the transaction processing module, and the risk warning module, to ensure that the entire digital currency application account management system can be aware of the special state of the account in time and make corresponding processing.

[0088] In some embodiments, the wallet service platform 130 will start the identification mechanism of the login state of the first digital currency application account. For example, in the account login link, it includes the first digital currency application account logged-in state, and the login state of detecting that the mobile communication number is used to attempt password login or other non-password login of the first digital currency application account and find the login password.

[0089] In step S220, the wallet service platform 130 performs corresponding operations on the first digital currency application account according to the identified login state of the first digital currency application account and the determination result of the specific matter.

[0090] In some embodiments of the present disclosure, the specific matter includes: the wallet service platform 130 determines whether to register a second digital currency application account (new account) using the mobile communication number, whether to open a digital currency wallet (new wallet) of a digital currency operation institution using the mobile communication number, and / or whether there is an association relationship between the digital currency wallet and the second digital currency application account, wherein the second digital currency application account and the digital currency wallet are established after the number recycling and reuse, and the second digital currency application account is a digital currency application account associated with the mobile communication number after the number recycling and reuse.

[0091] In some examples, the new user of the secondary number mobile phone will try to register a new account associated with the mobile phone number through the digital currency App 1200 or open a new wallet of a certain digital currency operation institution using the mobile phone number. Although the current mobile phone number is a secondary number, as long as it is detected that the mobile phone number has not registered a digital currency application account or opened a digital currency wallet of a certain operation institution after the secondary number, the account registration and wallet opening of the new user are allowed.

[0092] The wallet service platform 130 is responsible for analyzing and verifying the registration request and the opening request in the digital currency application account registration process or the digital currency wallet opening process. After the digital currency application account registration is completed and the digital currency wallet is opened, it can be learned in real time that a new digital currency application account has been registered and a new digital currency wallet has been opened by using a mobile phone number, and it is determined whether the two are associated. Moreover, the wallet service platform 130 can also determine the above content according to the association table of the user information (including the mobile phone number), the digital currency application account and the digital currency wallet stored in the local database.

[0093] For example, in some embodiments of the present disclosure, in step S230, the wallet service platform 130 performs at least one of the following operations on the first digital currency application account according to the login state of the identified first digital currency application account and the determination result of the specific matter: performing account access control corresponding to the login state, pushing a prompt message for modifying the mobile communication number by using a multi-dimensional notification system, and guiding the user to perform a modification operation on the mobile communication number through the digital currency application program.

[0094] For example, in one example, the wallet service platform 130 can obtain the login state data of the first digital currency application account and the association operation data of the secondary number in real time through different data interfaces. The login state data can include a basic state and a risk state, wherein the basic state includes: logged in, not logged in, and logging in; the risk state, for example, out-of-place login, high-frequency login failure (≥5 times), new device login (device fingerprint not recorded), and silent login (no operation for more than 30 minutes. The association operation data includes the second digital currency application account (new account) registration state: registered, not registered; the digital currency wallet (new wallet) opening state: the wallet of target operator A has been opened, not opened; the association relationship state: the new account is associated with the new wallet, and the new wallet is not associated with any account.

[0095] In an embodiment of the present disclosure, the login state mainly includes logged in and logging in, for the logged in old account, the account access control operation of forced exit can be performed; for the old account in the logging in, the operation related to the login is suspended.

[0096] For example, in some embodiments of the present disclosure, the multi-dimensional notification system pushes key information (such as a "modify mobile phone number prompt") to users through multiple independent and complementary communication channels, mainly to ensure that users receive important notifications in a timely and accurate manner, and to improve notification reach rate and operation guidance efficiency. The notification system includes two channels: within the digital currency App (in-app message mode) and outside the digital currency App (out-of-app message mode). In some cases, the notification is pushed within the digital currency App, for example, by displaying the guide information for modifying the mobile phone number through the display mode of the pop-up banner or pop-up window of the digital currency App, and adding an "modify mobile phone number" entry control, through which the corresponding mobile phone number modification page can be jumped to. The in-app message system of the digital currency App, such as the message center module in the digital currency App, can also be used for pushing. The out-of-app message mode refers to a mechanism for transmitting and reaching messages through communication channels or infrastructure outside the digital currency App. The core is that the sending, transmission and receiving of messages do not depend on the internal environment of the digital currency App (such as whether the user is logged in or online), but realize cross-system information interaction through third-party general channels. For example, PUSH message notification can be used to send notifications to user device 120, which can include user ID, current bound mobile phone number, operation prompt (such as "detected number two-time number release risk, please modify the bound mobile phone number in time") and security link (jump to the digital currency App or official website). The out-of-app message mode can also use email notification, social media / instant messaging to notify the modification of the mobile phone number, and the embodiments of the present disclosure do not limit this.

[0097] For example, in some embodiments of the present disclosure, when performing a corresponding operation on the first digital currency application account, the operation can include at least one of the following steps: if the second digital currency application account has been registered or the digital currency wallet is associated with the second digital currency application account, in the case of detecting that the first digital currency application account has been logged in (referred to as the first scenario), a login state termination operation is performed, and a first prompt message for modifying the mobile communication number associated with the first digital currency application account is pushed through the out-of-app message mode; if the second digital currency application account has been registered or the digital currency wallet is associated with the second digital currency application account, in the case of detecting that the first digital currency application account is to be logged in (referred to as the second scenario), a login suspension operation is performed, and a second prompt message for modifying the mobile communication number is pushed to the first digital currency application account through the in-app message mode; if the second digital currency application account has not been registered, and the digital currency wallet has been opened (referred to as the third scenario), a third prompt message for modifying the mobile communication number is pushed to the first digital currency application account through the in-app message mode.

[0098] First scene example 1: When the new user successfully registers the digital currency App account B, if it is detected that the old user's digital currency App account A is in a login state, the login state of the digital currency App account A is immediately "kicked out" through the digital currency App 1200, and a message is pushed to remind the old user to modify the mobile phone number outside the station. The content of the first prompt message can be consistent or similar to that of the second prompt message of the second scene.

[0099] First scene example 2: When the new user successfully registers the digital currency App account B and simultaneously associates the digital currency wallet W, if it is detected that the old user's digital currency App account A is in a login state, the login state of the digital currency App account A is immediately "kicked out" through the digital currency App 1200, and a message is pushed to remind the old user to modify the mobile phone number outside the station. The content of the first prompt message can be consistent or similar to that of the second prompt message of the second scene.

[0100] After determining that the mobile phone number is a secondary number, since the old user's digital currency App account A will be "kicked out" of the login state and be in an unlogged state, an instant notification can be sent to the user device 120 in the form of, for example, a PUSH message, without the user having to actively open the digital currency application. The notification can be directly displayed through the notification bar, lock screen interface or interface pop-up window of the user device 120, and the user can go to the corresponding mobile phone number modification page after clicking. For example, the PUSH content of the first prompt message can be: Please modify the mobile phone number as soon as possible to ensure normal use of digital renminbi services. The landing page of the PUSH click is the page for modifying the mobile phone number.

[0101] Second scene example 1: When the new user successfully registers the digital currency App account B, after determining that the mobile phone number is a secondary number, the old user attempts to log in to the digital currency App account A using the password or other non-password methods or retrieve the password for logging in to the digital currency App account A using the digital currency App 1200, the user operation is terminated, and a second prompt message is displayed through a pop-up pop-up window to strongly remind the user to modify the mobile phone number of the digital currency App account A.

[0102] Second scene example 2: When the new user successfully registers the digital currency App account B and simultaneously associates the digital currency wallet W, after determining that the mobile phone number is a secondary number, the old user attempts to log in to the digital currency App account A using the password or other non-password methods or retrieve the password for logging in to the digital currency App account A using the digital currency App 1200, the user operation is terminated, and a second prompt message is displayed through a pop-up pop-up window to strongly remind the user to modify the mobile phone number of the digital currency App account A.

[0103] For example, for the second prompt message, the pop-up window can be set as follows:

[0104] Pop-up window position: set at the login page of the digital currency App 1200.

[0105] Pop-up window pop-up timing: old users do not switch devices, there is local login information, try to log in for free.

[0106] Pop-up window priority: all pop-up windows at the end.

[0107] Pop-up window prompt text:

[0108] "The current mobile phone number has been registered by a new user. In order to ensure normal use of digital RMB services, please modify your mobile phone number as soon as possible."

[0109] Provide

I know

modify mobile phone number

I know

modify mobile phone number

[0110] Third scenario example: the new user has not registered any digital currency application account with the secondary mobile phone number, but has opened a new digital currency wallet B with the mobile phone number in a digital currency operating agency, and it is identified as a secondary mobile phone number scenario. If there is an old digital currency wallet A and a digital currency application account A opened by binding the same mobile phone number, the digital currency application account A will be notified and a station message will be pushed to the digital currency application account A, guiding the old user to modify the mobile phone number of the digital currency application account A. At this time, the login state of the digital currency application account A is not "kicked out".

[0111] For example, in some embodiments of the present disclosure, the user is guided to modify the mobile communication number through the digital currency application program, including: displaying a user interface for modifying the mobile communication number; receiving the modified mobile communication number input by the user on the user interface; completing the identity verification of the modified mobile communication number; after the modification is successful, the original mobile communication number associated with the first digital currency application account is unbound, and the modified mobile communication number is bound.

[0112] According to the above embodiment of the present disclosure, when it is detected that a new digital currency application account or digital currency wallet is opened with the same mobile phone number, the login state termination or login suspension operation is performed on the old account, avoiding the identity confusion, fund risk or operation conflict caused by the repeated binding of the mobile phone number. Whether the old digital currency application account is in the "logged in" or "logging in" scenario, an explicit mobile phone number modification prompt is pushed through the corresponding in-station or off-station channel to ensure that the old user discovers and corrects the mobile phone number binding problem in time. Moreover, through the scenario-based difference message pushing strategy, the user can immediately obtain the mobile phone number correction guide, ensuring the normal application of the new and old digital currency application accounts.

[0113] For example, in some embodiments of the present disclosure, the method 200 further comprises: the wallet service platform 130 sending a notification message to the digital currency operating institutions to which the other digital currency wallets associated with the first digital currency application account and opened using the mobile communication number belong, the notification message indicating that the mobile communication number used to open the digital currency wallet is a number recycling resource.

[0114] For example, if the digital currency application account is labeled as a "second number release old account", the digital currency App 1200 synchronously notifies the wallet operating institutions of the other digital currency wallets associated with the old account and opened using the mobile phone number, informing that the old wallet opened using the mobile phone number exists the case of second number release.

[0115] In one example, the wallet service platform 130 extracts the wallet ID, operating institution code and other information (which can be desensitized and does not include the original user's name, ID number and other sensitive data) of all wallets opened using the mobile phone number under the old account from the account-wallet association table of the local account database through retrieval. The wallet service platform 130 sends a notification message to each wallet operating institution 1 through the interconnection platform. The notification message can include: the second number release mobile phone number, the old wallet ID, the old account registration time (YYYY-MM-DD HH:MM). The notification message can also include a risk prompt: "The mobile phone number has been released twice. The old wallet may exist a new user mis-association risk. Please check the wallet status and take safety measures.

[0116] Figure 6 A flowchart of another method 300 of managing a digital currency application account according to at least one embodiment of the present disclosure is shown. The method 300 is mainly for the following scenario: in the second number release, a new user has registered a digital currency application account B and bound a mobile phone number M1, and then the new user purchases a mobile phone number M2 from a telecom operator and wants to change the bound mobile phone number M1 to the mobile phone number M2; and the mobile phone number M2 is used by an old user and is bound to a digital currency application account A. Then in this scenario, when the new user changes the bound mobile phone number to the mobile phone number M2, it will be detected that the mobile phone number M2 is occupied by the digital currency application account A and cannot be changed. The method 300 gives a specific solution to solve the problem existing in the above scenario. The method steps of the embodiments of the present disclosure will be explained below with reference to Figure 6

[0117] In step S310, the wallet service platform 130 receives a first modification request initiated by the user through the digital currency App 1200 to modify the current bound mobile communication number of the target digital currency application account, and the first modification request includes the modified target mobile communication number.

[0118] ​For example, a user initiates an operation of modifying a mobile phone number bound to a certain digital currency application account through the digital currency App 1200. After triggering the "mobile phone number modification" function control in the App, the App client encrypts and encapsulates the modified mobile phone number input by the user, the user identity token, the operation timestamp, the device fingerprint information and other parameters, and transmits them to the wallet service platform 130.

[0119] In step S320, the wallet service platform 130 determines whether the target mobile communication number has been associated with other digital currency application accounts. If not, step S340 is performed. If yes, step S330 is performed. The other digital currency application accounts establish an association relationship with the target mobile communication number before the number recycling and reuse, and are in an effective association state after the number recycling and reuse.

[0120] In one example, after receiving the first modification request, the wallet service platform 130 first performs basic format checking and signature verification on the request. After verification, the core business parameters are parsed, including the modified target mobile phone number, to provide a data basis for subsequent business logic such as secondary number release verification and old account association relationship verification.

[0121] The other digital currency application accounts refer to the old account associated with the target mobile phone number. The content related to the other digital currency application accounts is similar to the first digital currency application account in the previous embodiments, and can be referred to the previous content, which will not be repeated here.

[0122] After parsing the target mobile phone number, the wallet service platform 130 can retrieve the account database to determine whether there is a currency account associated with the target mobile phone number. If no account is found, it means that the target mobile phone number is not occupied, and step S340 is performed for mobile phone number modification. Otherwise, the business logic of secondary number release verification is continued.

[0123] In step S330, it is checked whether the target mobile communication number exists number recycling after the registration time of the other digital currency application account. If yes, step S340 is performed. Otherwise, step S350 is performed. The content related to the wallet service platform 130 checking whether the target mobile phone number exists secondary number release can be referred to the related content in the previous examples, which will not be repeated here.

[0124] In one example, when it is checked that the target mobile phone number exists secondary number release, it means that the other digital currency application account is registered before the secondary number release of the target mobile phone number, which does not affect the use of the target mobile phone number by the new user after the secondary number release. Therefore, the mobile phone number is allowed to be modified to the target mobile phone number.

[0125] In step S340, the wallet service platform 130 modifies the mobile communication number currently associated with the target digital currency application account to the target mobile communication number in response to the check result of the target mobile communication number existing number recycling reuse.

[0126] In step S350, a prompt message is sent to the digital currency App 1200.

[0127] In embodiments of the present disclosure, the wallet service platform 130 sends a prompt message to the digital currency App 1200 indicating a binding conflict in response to the target mobile communication number not existing number recycling reuse after the registration time of the other digital currency application account. The prompt message may, for example, be displayed in the form of a pop-up window within the digital currency App (in-app message mode), and the prompt text may be set as “This mobile phone number is bound to other accounts”.

[0128] For example, in some embodiments of the present disclosure, the method 300' further comprises: the wallet service platform 130 sending a notification message to the digital currency operation institution to which the other digital currency wallet associated with the other digital currency application account and opened using the target mobile communication number belongs, the notification message indicating that the target mobile communication number used to open the digital currency wallet is a number recycling reuse resource. This step can refer to the related content in the foregoing embodiments, and will not be described here.

[0129] In the above embodiments, after the wallet service platform 130 receives the first modification request for modifying the mobile phone number associated with the digital currency application account, in the case where it is detected that the target digital currency application account is not associated with a digital currency wallet or the modification permission of the operation institution to which the digital currency wallet associated with the digital currency application account belongs is not considered, the modification of the mobile phone number associated with the target digital currency application account can be performed after the completion of the above business processes.

[0130] Figure 7 A flowchart of another method 300' of managing a digital currency application account according to at least one embodiment of the present disclosure is shown. The method 300' is mainly for Figure 7 Another solution for the scenario shown is for the solution when the target digital currency application account is associated with a digital currency wallet. Steps that are the same as or similar to the method 300 are denoted by the same reference numerals, and will not be described here. Only the different content will be described. The method steps of the embodiments of the present disclosure will be described below with reference to Figure 7

[0131] In step S330, if the target mobile communication number exists number recycling reuse, step S360 is performed.

[0132] ​In step S360, the wallet service platform 130 determines whether there is a digital currency wallet associated with the target digital currency application account, and if so, sends a modification operation permission request to the digital currency operation institutions to which all digital currency wallets associated with the target digital currency application account belong, wherein the modification operation permission request indicates whether to allow the current mobile communication number associated with the digital currency wallet to be modified to the target mobile communication number.

[0133] When the mobile phone number associated with the digital currency application account is to be modified, if the digital currency application account is also associated with multiple digital currency wallets, the permission of all relevant digital currency operation institutions is required. Here, the main consideration is that different operation institutions may set personalized risk control rules (such as A bank requires that the mobile phone number must be a domestic mobile phone number). If a certain institution disagrees to modify (such as the target mobile phone number does not meet its compliance requirements), it indicates that there is a potential risk, and the modification process needs to be terminated to avoid the risk of loopholes.

[0134] In addition, it can also prevent account takeover attacks. If an attacker forges operator data to pass the secondary number placement verification, since there is also this step of modifying the permission of the digital currency operation institution, the operation institution can refuse to modify through independent risk control rules (such as detecting that the modification request IP does not match the usual login location), forming a "multi-institution cross-verification" security barrier, and avoiding the risk of account theft caused by the failure of single-institution verification.

[0135] If it is determined in this step that the target mobile phone number does not have an associated digital currency wallet, step S340 can be directly executed to modify the mobile phone number of the target account.

[0136] In step S370, the wallet service platform 130 obtains the response information returned by each digital currency operation institution to the modification operation permission request, and determines whether to modify the current mobile communication number associated with the target digital currency application account to the target mobile communication number according to the response information of all digital currency operation institutions.

[0137] For example, in some embodiments of the present disclosure, step S370 further includes: if the response information returned by any digital currency operating agency indicates that the modification operation is rejected or the response is timed out, a risk prompt message containing the digital currency wallet information of the rejected modified mobile communication number is generated and sent to the digital currency application 1200. If the response information returned by all digital currency operating agencies indicates that the modification operation is permitted, the target mobile communication number is modified to the target mobile communication number currently associated with the target digital currency application account, and the other digital currency application account (old account) is marked and the login state is identified. According to the identified login state of the other digital currency application account, at least one of the following operations is performed on the other digital currency application account: performing account access control corresponding to the login state, pushing a prompt message for modifying the target mobile communication number using a multi-dimensional notification system, and guiding the user to modify the target mobile communication number through the digital currency application.

[0138] In one example, the wallet service platform 130 identifies the meaning of the response information returned by each operating agency after receiving the response information. The response information includes permission to modify the state, rejection to modify the state, response timeout state, etc., wherein the rejection to modify the state also carries specific rejection codes, such as 001-foreign login risk, 002-non-domestic mobile phone risk, etc.

[0139] When the wallet service platform 130 receives the rejection to modify the state or the response timeout state, a risk prompt message containing multiple core fields can be generated. For example, the risk prompt message can include: wallet ID, target mobile number, visual rejection code (such as "new mobile number detected as an overseas number, modification not supported"), rejection timeout agency abbreviation, user operation suggestion, etc. Then, the risk prompt message is sent to the digital currency App 1200, which can be sent through a landing page (Land Page). The prompt text may, for example, be: XX bank rejects mobile number modification, new mobile number is an overseas mobile number, and there is a high risk.

[0140] For example, in some embodiments of the present disclosure, in step S370, in the step of performing at least one of the following operations on the other digital currency application account, it includes: if it is detected that the other digital currency application account is logged in, a login state termination operation is performed, and a first prompt message for modifying the target mobile communication number associated with the other digital currency application account is pushed through an off-site message mode outside the digital currency application; if it is detected that the other digital currency application account is to be logged in, a login suspension operation is performed, and a second prompt message for modifying the target mobile communication number is pushed to the other digital currency application account through an in-site message mode within the digital currency application.

[0141] The steps involving marking old accounts and identifying login status are similar to those in the aforementioned embodiments and will not be repeated here.

[0142] For example, in some embodiments of this disclosure, method 300' further includes: when the mobile communication number currently associated with the target digital currency application account is modified to the target mobile communication number, the wallet service platform 130 sends a second modification request to the digital currency operating institutions to which all digital currency wallets associated with the target digital currency application account belong, so that each digital currency operating institution modifies the mobile communication number currently associated with the digital currency wallet to the target mobile communication number according to the second modification request.

[0143] In one example, the second modification request generated by the wallet service platform 130 may include the following parameters: target wallet ID and the modified target mobile phone number. These parameters are encrypted and encapsulated before being sent to each operating institution. Upon receiving the second modification request, each operating institution verifies and parses it, and modifies the mobile phone number of the relevant digital currency wallet to the target mobile phone number based on the parsing result. This step ensures that all operating institutions complete the mobile phone number modification simultaneously, avoiding the situation of "account mobile phone number has been modified, associated wallet uses old mobile phone number," thus eliminating conflicts. Moreover, users only need to initiate a mobile phone number modification request once on the digital currency app, and the wallet service platform can automatically synchronize all associated operating institutions to perform the modification operation, optimizing the user experience.

[0144] According to embodiments of this disclosure, the wallet service platform 130 described above can be configured to implement a method for managing digital currency red envelopes, a method for managing digital currency application accounts, and / or a process for doing so. References are provided below. Figure 2 The wallet service platform 130 described herein can operate one or more computer devices to facilitate the functions described herein. The wallet service platform 130 may include a processor and a computer-readable medium comprising processor-executable code for implementing any of the methods described herein.

[0145] It should be noted that the above application scenarios are merely exemplary in order to describe one or more aspects of this disclosure in specific scenarios. However, these aspects are not essential, and various modifications can be made to the application scenario. The embodiments of this disclosure are not limited.

[0146] At least some embodiments of this disclosure also provide an electronic device. Figure 8 A schematic diagram of an electronic device 600 according to at least one embodiment of the present disclosure is shown.

[0147] like Figure 8As shown, the electronic device 600 includes one or more processors 610 and memory 620. The memory 620 includes one or more computer program modules 621. The one or more computer program modules 621 are stored in the memory 620 and configured to be executed by the processor 610, the one or more computer program modules 621 include instructions for performing the method 400, 400', 200, 300, 300' and additional aspects thereof according to at least one embodiment of the present disclosure, which, when executed by the processor 610, can perform one or more steps of the method 400, 400', 200, 300, 300' and additional aspects thereof according to at least one embodiment of the present disclosure. The memory 620 and the processor 610 can be interconnected by a bus system and / or other form of connection mechanism (not shown). For example, the bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0148] Exemplarily, the processor 610 can be a central processing unit (CPU), a digital signal processor (DSP), or other forms of processing units having data processing and / or program executing capabilities, such as field programmable gate arrays (FPGAs), etc. The processor 610 can be a general purpose processor or a dedicated processor, and can control other components in the electronic device 600 to perform desired functions.

[0149] Exemplarily, the memory 620 can include any combination of one or more computer program products. The computer program product can include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory, for example, can include random access memory (RAM), cache memory, etc. The non-volatile memory, for example, can include read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), compact disc read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules 621 can be stored on the computer-readable storage media, and the processor 610 can run the one or more computer program modules 621 to implement various functions of the electronic device 600. The computer program modules include a plurality of computer-executable instructions. Various application programs and various data used and / or generated by the application programs, etc. can also be stored in the computer-readable storage media.

[0150] For example, the electronic device 600 can further include input devices such as a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices such as a liquid crystal display, a speaker, a vibrator, etc.; storage devices such as a magnetic tape, a hard disk (HDD or SDD), etc.; and communication devices such as a LAN card, a modem, etc. The communication devices can allow the electronic device 600 to communicate with other devices wirelessly or via wires to exchange data, perform communication processing via a network such as the Internet. Drivers are connected to the I / O interface as needed. Removable storage media such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. are mounted on the drivers as needed, so that computer programs read out from them are installed in the storage devices as needed.

[0151] For example, the electronic device 600 can further include a peripheral interface (not shown) and the like. The peripheral interface can be various types of interfaces, such as a USB interface, a lighting interface, and the like. The communication devices can communicate with networks and other devices through wireless communication, the networks being, for example, the Internet, an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN). The wireless communication can use any of a plurality of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi (e.g., based on IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n standards), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email, instant messaging, and / or Short Message Service (SMS), or any other suitable communication protocol.

[0152] The electronic device 600 can be, for example, a system on chip (SOC) or a device including the SOC, such as a mobile phone, a tablet computer, a notebook computer, an e-book, a game console, a television, a digital photo frame, a navigator, a home appliance, a communication base station, an industrial controller, a server, or any device, and can be any data processing apparatus and combination of hardware, without limitation. The specific functions and technical effects of the electronic device 600 can be referred to the description of the method 400, 400', 200, 300, 300', and additional aspects thereof according to at least one embodiment of the present disclosure above, which will not be repeated here.

[0153] Figure 9 A schematic diagram of a computer-readable storage medium 700 according to at least one embodiment of the present disclosure is shown.

[0154] As shown in Figure 9 The non-transitory computer readable medium 700 stores non-transitory computer instructions 710 which, when executed by a processor, perform one or more steps of the methods 400, 400', 200, 300, 300' and additional aspects thereof as described above.

[0155] Exemplarily, when the program code is read by the computer, the computer can execute the program code stored in the computer storage medium to perform one or more steps of the methods 400, 400', 200, 300, 300' and additional aspects thereof according to at least one embodiment of the present disclosure.

[0156] Exemplarily, the computer readable storage medium can include a memory card of a smart phone, a storage component of a tablet computer, a hard disk of a personal computer, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM), a portable compact disc read only memory (CD-ROM), a flash memory, and other computer readable medium or any combination thereof.

[0157] At least some embodiments in the present specification are described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and the same or similar parts between embodiments can be referred to each other.

[0158] It should be noted that, in this document, the relationship terms such as first, second and the like are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. The terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements not only includes those elements, but further includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or equipment. Without more limitations, the elements defined by the statement "include" do not exclude the presence of other same elements in the process, method, article or equipment including the elements.

[0159] For the present disclosure, the following points need to be explained:

[0160] (1) The drawings of the embodiments of the present disclosure only involve the structures involved in the embodiments of the present disclosure, and other structures can refer to the general design.

[0161] (2) In the case of no conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0162] The above-described exemplary embodiments of the present disclosure are merely for the purpose of illustration, and should not be construed as limiting the scope of the present disclosure, which is defined by the appended claims.

Claims

1. A method for managing digital currency red envelopes, the method comprising: The digital currency wallet service platform receives and responds to the login request of the user to log in to the digital currency red envelope mini-application, and identifies the user group to which the user belongs. The digital currency red envelope mini-application obtains the user's mobile communication number through the host platform to authorize login and receive digital currency red envelopes. If the user's mini-application user group is an existing user or a new user whose login exemption period has expired, the digital currency wallet service platform determines whether to check whether the mobile communication number has been recycled and reused after the registration time based on the authorized login time of the digital currency red packet mini-application authorized by the host platform, the current login time, and the registration time of the digital currency application account registered using the mobile communication number. If the verification is confirmed, the digital currency wallet service platform, in response to the verification result that the mobile communication number has been recycled and reused, triggers an identity verification process for the mobile communication number to verify the user's identity. In response to the successful identity verification, the digital currency wallet service platform pre-claims the digital currency red envelope and prompts the user to register a digital currency application account.

2. The method according to claim 1, wherein, The steps for determining the authorized login time include: If the user initiates a request to receive a digital currency red envelope without changing their mobile communication number, the time when the host platform authorizes login to the digital currency red envelope mini-application will be used as the authorized login time. If the user changes their mobile phone number and initiates a request to receive a digital currency red envelope, the time when the user changes their mobile phone number will be used as the authorized login time.

3. The method according to claim 1, wherein, The step of determining whether the mobile communication number has been recycled and reused after the registration time includes: If the authorized login time is after the registration time, determine whether the time difference between the current login time and the registration time exceeds a set time threshold. If the time difference exceeds the set time threshold, check whether the mobile communication number has been recycled and reused after the registration time.

4. The method according to claim 1, wherein, The step of determining whether the mobile communication number has been recycled and reused after the registration time includes: If the user group of the lightweight application consists of existing users whose login exemption period has expired, and the authorized login time is before the registration time, then it is determined whether the time difference between the authorized login time and the registration time exceeds a set time threshold. If the time difference exceeds the set time threshold, the system will not check whether the mobile communication number has been recycled and reused after the registration time, and will trigger the identity verification process to verify the user's identity; in response to the successful identity verification, the user will log in successfully and be allowed to receive the digital currency red envelope.

5. The method according to claim 1, 3 or 4, wherein, The method further includes: If the digital currency wallet service platform responds to the verification result that the mobile communication number does not have a number recycling and reuse result or the judgment result that the time difference is less than the set time threshold, then the login is successful and the user is allowed to receive the digital currency red envelope.

6. The method according to claim 1, wherein, The method further includes: If the user's virtual application user group is an existing user within the login-free validity period, the digital currency wallet service platform determines whether the first digital currency application account associated with the login-free token and the second digital currency application account associated with the mobile communication number are consistent. If the first digital currency application account and the second digital currency application account are the same, the user is allowed to receive the digital currency red envelope; otherwise, the association between the login-free token and the first digital currency application account is cleared, and the new user login process begins.

7. The method according to claim 1, wherein, The digital currency red envelope mini-application includes a digital currency red envelope mini-program and / or a digital currency red envelope H5 page for receiving digital currency red envelopes.

8. The method according to claim 1 or 6, wherein, The method further includes: The digital currency wallet service platform responds to a user's request to distribute digital currency red envelopes initiated by the digital currency application. It queries the associated digital currency application account based on the mobile communication number in the distribution request. If there are multiple digital currency application accounts, it sends a prompt message to the digital currency application to prompt the user to distribute the digital currency red envelopes through the host platform, which has social application attributes.

9. A management system for digital currency red envelopes, the system comprising a digital currency wallet service platform, the digital currency wallet service platform comprising: The user group identification module is configured to receive and respond to the login request of a user to log in to the digital currency red envelope mini-application, and identify the user group to which the user belongs. The digital currency red envelope mini-application obtains the user's mobile communication number through the host platform to authorize login and receive digital currency red envelopes. The number recycling judgment module is configured to determine whether to check whether the mobile communication number has been recycled and reused after the registration time when the user belongs to the user group of the light application and is an existing user or a new user whose login exemption period has expired, based on the authorized login time of the digital currency light application authorized by the host platform, the current login time, and the registration time of the digital currency application account registered using the mobile communication number. The identity verification module is configured to, in response to the verification result that the mobile communication number has been recycled and reused, trigger an identity verification process to verify the user's identity if a verification is determined; The red envelope management module is configured to, in response to the successful identity verification, pre-claim the digital currency red envelope and prompt the user to register a digital currency application account.

10. The system according to claim 9, wherein, The number recycling judgment module is also configured to perform the following operations to determine the authorized login time: If the user initiates a request to receive a digital currency red envelope without changing their mobile communication number, the time when the host platform authorizes login to the digital currency red envelope mini-application will be used as the authorized login time. If the user changes their mobile phone number and initiates a request to receive a digital currency red envelope, the time when the user changes their mobile phone number will be used as the authorized login time.

11. The system according to claim 9, wherein, The number recycling judgment module is also configured to perform the following operations: If the authorized login time is after the registration time, determine whether the time difference between the current login time and the registration time exceeds a set time threshold. If the time difference exceeds the set time threshold, check whether the mobile communication number has been recycled and reused after the registration time.

12. The system according to claim 9, wherein, The number recycling judgment module is also configured to perform the following operations: If the user group of the lightweight application consists of existing users whose login exemption period has expired, and the authorized login time is before the registration time, then it is determined whether the time difference between the authorized login time and the registration time exceeds a set time threshold. If the time difference exceeds the set time threshold, the system will not check whether the mobile communication number has been recycled and reused after the registration time, and will trigger the identity verification process to verify the user's identity; in response to the successful identity verification, the user will log in successfully and be allowed to receive the digital currency red envelope.

13. The system according to claim 9, 11 or 12, wherein, The red envelope management module is also configured to perform the following operations: If the verification result indicates that the mobile communication number does not have a number recycling and reuse function, or if the time difference is less than the set time threshold, then the login is successful and the user is allowed to receive the digital currency red envelope.

14. The system according to claim 9, wherein, The red envelope management module is configured to perform the following operations: If the user belongs to a lightweight application user group that is an existing user within the validity period of the login-free period, then it is determined whether the first digital currency application account associated with the login-free token and the second digital currency application account associated with the mobile communication number are consistent. If the first digital currency application account and the second digital currency application account are the same, the user is allowed to receive the digital currency red envelope; otherwise, the association between the login-free token and the first digital currency application account is cleared, and the new user login process begins.

15. The system according to claim 9, wherein, The red envelope management module is also configured to perform the following operations: In response to a user's request to distribute digital currency red envelopes initiated by a digital currency application, the associated digital currency application account is queried based on the mobile communication number in the distribution request. If there are multiple digital currency application accounts, a prompt message is sent to the digital currency application to prompt the user to distribute the digital currency red envelopes through the host platform, which has social application attributes.

16. An electronic device comprising: One or more processors; Memory, which stores one or more computer program modules. The one or more computer program modules are configured to be executed by the one or more processors to implement the method according to any one of claims 1-8.

17. A computer-readable storage medium for storing non-transitory computer-readable instructions, wherein, When a non-transitory computer-readable instruction is executed by one or more processors, it is used to implement the method according to any one of claims 1-8.

Images