Method and system for managing digital currency red packets

Abstract

Embodiments of the present disclosure provide a digital currency red envelope management method and system, wherein the method comprises: a wallet service platform receiving and responding to a login request of a user logging into a digital currency red envelope light application, identifying a light application user group to which the user belongs; in the case that the user group is a user with a remaining amount outside the free login period or a new user, the wallet service platform determines whether to check for number recycling reuse according to the authorized login time of the digital currency red envelope light application, the current login time and the registration time of the registered digital currency application account; in the case of determining to check, in response to the check result of the existence of number recycling reuse, triggering identity verification of the user; the wallet service platform preoccupies the digital currency red envelope and prompts the user to register a digital currency application account in response to the result of passing the identity verification. The technical problem of incorrect collection of digital currency red envelopes caused by secondary number release 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 this disclosure provides a management system for digital currency red envelopes. The system includes a digital currency wallet service platform, comprising: a user group identification module configured to receive and respond to a user's login request for a digital currency red envelope mini-application, and identify the user's mini-application user group, wherein 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; a number recycling judgment module configured to, if the user's mini-application user group is an existing user or a new user whose login exemption period has expired, determine whether to verify if the mobile communication number has been recycled and reused after the registration time based on the authorized login time of the digital currency 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; an identity verification module configured to, in response to the verification result indicating that the mobile communication number has been recycled and reused, trigger an identity verification process to verify the user's identity if verification is determined; and a red envelope management module configured to, in response to the successful identity verification, pre-claim digital currency red envelopes and prompt the user to register a digital currency application account.

[0006] At least one embodiment of this disclosure provides an electronic device, including: one or more processors; and 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 a method provided according to at least one embodiment of this disclosure.

[0007] At least one embodiment of this 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 a method provided according to at least one embodiment of this disclosure.

[0008] The digital currency red envelope management scheme of this disclosure addresses the scenario where the mobile phone number is a reissued number. It identifies the number recycling and reuse status through the digital currency wallet service platform and determines the target user who should receive the digital RMB red envelope. This solves the technical problem of incorrect receipt of digital RMB red envelopes caused by reissued numbers in existing solutions and provides key technical support for the application of digital currency business in the reissued number scenario. Attached Figure Description

[0009] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments of this disclosure will be briefly described below. Clearly, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit the scope of this 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 according to at least one embodiment of the present disclosure is shown;

[0012] Figure 3 A flowchart illustrating a method for managing digital currency red envelopes according to at least one embodiment of the present disclosure is shown.

[0013] Figure 4 A flowchart illustrating another method for managing digital currency red envelopes according to at least one embodiment of the present disclosure is shown;

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

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

[0016] Figure 7 A flowchart illustrating another method for managing digital currency application accounts according to at least one embodiment of the present disclosure is shown;

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

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

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0020] Unless otherwise defined, the technical or scientific terms used herein should have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms “first,” “second,” and similar terms used in this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, terms such as “comprising” or “including” mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as “connected” or “linked” are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as “upper,” “lower,” “left,” and “right” are used only to indicate relative positional relationships, which may change accordingly when the absolute position of the described objects changes.

[0021] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of this disclosure to the specific shapes, hardware, connections, operations, values, conditions, data, sequences, etc., shown and described. Those skilled in the art can utilize the concepts of this disclosure to construct further embodiments not mentioned herein by reading this specification.

[0022] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0023] This disclosure uses flowcharts to illustrate the operations performed by a system according to embodiments of this disclosure. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously, as needed. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0024] First, the abbreviations and related terms involved in this disclosure are defined and explained.

[0025] User equipment primarily includes devices involving communication technologies. Specifically, it includes any electronic device that a user can easily carry or operate, which can also provide remote communication capabilities with networks, such as mobile communication terminals. Mobile communication terminals can communicate using mobile phone (wireless) networks, wireless data networks (e.g., 3G, 4G, 5G, or similar networks), Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), Wi-Max, or any other communication medium that provides access to networks such as the Internet or private networks. Specific examples include mobile phone terminals, tablet computers, netbooks, laptop computers, wearable devices (e.g., smartwatches), etc.

[0026] Digital currency red envelopes: such as digital RMB red envelopes, which are electronic red envelopes issued in the form of digital RMB. They may include cash red envelopes and consumption red envelopes / coupons. In this application embodiment, it mainly refers to cash red envelopes, such as digital RMB red envelopes sent by individual users of the digital RMB App to other individual users.

[0027] Digital currency application account: This can be abbreviated as "digital currency application account" or "digital currency account." It's a credential used by users to register on digital currency applications using a mobile phone number (e.g., a phone number) to distinguish different users within the application. Users log in to their accounts using their phone number, password, or biometric login. For example, a digital RMB application account is an account registered by a user using their phone number on the digital RMB application.

[0028] Digital currency wallets serve as the carrier and medium for reaching users of digital currencies (hereinafter referred to as "digital currencies," referring to digital legal tender, such as the digital yuan). They can take the form of soft wallets or hardware wallets. Soft wallets can be provided through wallet services offered by smart applications that support digital currencies; they can be understood as existing in the form of an application (App). Examples include digital wallets within digital currency apps and digital wallets within apps of various digital currency operating institutions. Hardware wallets refer to physical media for storing digital currencies, opened through over-the-counter or electronic channels. They are digital currency carriers with a secure element (SE) and also possess basic functions such as redemption, deposit, withdrawal, consumption, transfer, and inquiry. Examples include mobile phones, NFC-SIM cards, IC cards, and wearable devices with secure elements. In this embodiment, digital currency wallets primarily refer to soft wallets. Users can open a digital currency wallet (hereinafter referred to as "wallet") through a digital currency application (such as the digital yuan App) by selecting one of the digital currency operating institutions designated by the central bank, or they can open a wallet directly through a digital currency operating institution.

[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 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 this disclosure provides a method, system, electronic device, and storage medium for managing digital currency red envelopes. Targeting scenarios involving the secondary release of mobile phone numbers, the method identifies the secondary release status of mobile communication numbers through a digital currency wallet service platform, accurately locates target users who should receive digital RMB red envelopes, and effectively solves the technical problem of misreceiving digital currency red envelopes due to number recycling and reuse in existing solutions.

[0037] The embodiments and some examples of this disclosure will now be described in detail 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. Figure 1 As shown, the system 1000 mainly includes user equipment 120 and a digital currency wallet service platform (hereinafter referred to as "wallet service platform") 130. The user equipment 120 can communicate with the wallet service platform 130.

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

[0040] like Figure 1As shown, user device 120 may include a digital currency application (hereinafter referred to as "digital currency App" or "digital currency app," such as a digital RMB App) 1200. The digital currency App can be a mobile application providing full lifecycle management functions for a digital currency wallet, provided by the digital currency issuer (such as a central bank). During use, it can communicate and interact with the digital currency wallet server 130. The digital currency App 1200 provides users with a user interface (UI) for performing digital currency transactions or managing digital currency application accounts through the display module of user device 120. It can receive data and instructions from the wallet service platform 130 and execute corresponding processing. User device 120 may include a host platform (not shown) with social application attributes, such as WeChat, QQ, Alipay, and other social platform Apps. Users can send digital RMB red envelope links through these social platform Apps, and red envelope recipients can log in to the digital currency red envelope mini-application 1210 through these host platforms to receive the red envelopes. The Digital Currency Red Packet Lite Application 1210 is a lightweight application running on third-party host platforms such as WeChat, QQ, and Alipay, used to receive digital currency red packets (such as digital RMB red packets) in social scenarios. In some embodiments of this disclosure, the Digital Currency Red Packet Lite Application includes a digital currency red packet mini-program and / or a digital currency red packet H5 page for receiving digital currency red packets. For example, if the sender shares a red packet link through the WeChat platform, the recipient clicks the link to enter the "Digital RMB Red Packet" mini-program, logs in with the mobile phone number associated with their registered digital RMB application account, and receives the red packet, which will be stored in the corresponding digital RMB wallet. Similarly, if the sender shares the red packet link to platforms such as QQ or Alipay, the recipient clicks the link to enter the "Digital RMB Red Packet" H5 page, logs in with the mobile phone number associated with their registered digital RMB application account, and receives the red packet, which will be stored in the corresponding digital RMB wallet.

[0041] Wallet service platform 130 is the backend computer system for digital currency issuers (such as central banks) to manage digital currency application accounts and digital currency wallets. Users can interact with wallet service platform 130 through digital currency application 1200 and digital currency red packet mini-application 1210 on user device 120 to distribute and receive digital currency red packets. For example, during the process of receiving a digital currency red packet, after the recipient initiates a login request to the digital currency mini-application 1210 through the host platform, wallet service platform 130 identifies the user's mini-application user group and executes the corresponding process operation according to the user group, ensuring that the real target user receives the digital currency red packet and preventing red packets from being mistakenly received due to secondary distribution of accounts.

[0042] Figure 3A flowchart of a digital currency red packet management method 400 according to at least one embodiment of the present disclosure is shown. Method 400 mainly addresses the processing logic in a secondary redemption scenario where users receive digital currency red packets through a digital currency red packet mini-program 1210, such as a digital currency red packet app or H5 page, when the user is identified as an existing user whose login expiration period has expired or a new user. The following refers to... Figure 1 and Figure 3 The method steps of the embodiments of this disclosure will be explained.

[0043] In step S410, the wallet service platform 130 receives and responds to the user's login request to log in to the digital currency red packet mini-application 1210, identifies the mini-application user group to which the user belongs, wherein the digital currency mini-application 1210 obtains the user's mobile communication number through the host platform to authorize login and receive digital currency red packets.

[0044] In step S420, if the user's light application user group is an existing user or a new user whose login exemption period has expired, the wallet service platform 130 executes step S430.

[0045] In step S430, 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, it is determined whether the mobile communication number has been recycled and reused after the registration time. If so, step S440 is executed.

[0046] In step S440, if the verification is confirmed, the wallet service platform 130, 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.

[0047] In step S450, in response to the successful identity verification, the wallet service platform 130 pre-claims the digital currency red envelope and prompts the user to register a digital currency application account.

[0048] In step S410, for example, when a distributor shares a digital RMB cash red packet link to the WeChat platform in the form of a "group red packet," the recipient clicks the link to receive the red packet through the digital currency red packet mini-program. Upon first login to the digital currency red packet mini-program, clicking the link through the WeChat platform triggers an authorization request to obtain user information (mainly including the mobile phone number associated with the WeChat account) to authorize login. After authorization, the mini-program sends the OpenID (a unique identifier for the user) obtained from the WeChat platform to the wallet service platform 130. The wallet service platform 130 generates a random string or JWT format login-free token and sets a login-free validity period (e.g., 30 days), returning the login-free token to the mini-program for local caching. In another example, when a user shares a digital RMB cash red packet link to the Alipay platform in the form of a "group red packet," the red packet is received through the digital currency red packet H5 page. When clicking on the digital currency red envelope H5 page to claim the red envelope, users need to enter their mobile phone number to authorize login. After logging in, a login-free token (with a login-free validity period set, such as 30 days) is issued and cached locally.

[0049] For example, in some embodiments of this disclosure, the user group of the lightweight application includes existing users within the validity period of the no-login access period, existing users outside the validity period of the no-login access period, and new users. For example, when a user opens the digital currency red envelope mini-program or the digital currency red envelope H5 page, the system checks whether a valid no-login access token exists in the local cache. If it exists and has not expired, the user is confirmed as an existing user within the validity period of the no-login access period; if it has expired or become invalid, the user is confirmed as an existing user outside the validity period of the no-login access period, and a re-login process can be triggered. It is easy to understand that if no no-login access token exists in the local cache, the user is confirmed as a new user, and a new user login process needs to be executed.

[0050] For example, in some embodiments of this disclosure, the authorized login time generally refers to the time of the first login to the digital currency red packet mini-application. The steps for determining this time include: if the user initiates a request to receive a digital currency red packet without changing their mobile phone number, the time of the first authorized login to the digital currency red packet mini-application on the host platform is taken as the authorized login time; if the user changes their mobile phone number and initiates a request to receive a digital currency red packet, the time of the change of the user's mobile phone number is taken as the authorized login time. Taking WeChat as an example, the authorized login time can typically be the timestamp of the user clicking the authorized login button to trigger the login process, or the timestamp of the wallet service platform 130 successfully verifying the login and generating a login state. The wallet service platform 130 can associate and store this timestamp with the OpenID and the WeChat-bound mobile phone number. If the user changes their mobile phone number, the timestamp marked when the user submits the new mobile phone number and the verification code is verified and the mobile phone number field is updated is taken as the authorized login time. In this way, the authorized login time can be accurately located, ensuring data accuracy and providing support for the selection and execution of subsequent processes.

[0051] In this embodiment, the registration time refers to the timestamp of registering a digital currency application account using a mobile communication number. For example, the wallet service platform 130 finds multiple digital currency application account IDs associated with the target mobile communication 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 associated 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 associated state. In this embodiment, the registration time can be the timestamp of the mobile phone number associated with either the old or new accounts from secondary number releases.

[0052] If, in step S420, it is identified that the user belongs to a lightweight application user group that is an existing user or a new user whose login exemption period has expired, then the order of the authorized login time and the registration time is compared.

[0053] For example, according to some embodiments of this disclosure, in step S430, the step of determining whether to check 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, determining whether the 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, checking whether the mobile communication number has been recycled and reused after the registration time. According to some embodiments of this disclosure, if the time difference is less than the set time threshold, the login is successful, and the user is allowed to receive a digital currency red envelope. An example of the above scenario could be: an existing user who has registered a digital currency application account, and a new user who has not registered an account and directly authorizes login to the WeChat mini-program to receive a red envelope. In this scenario example, the registration time refers to the time when the existing user registers the digital currency application account, and the current login time is the time when the new user logs into the digital currency application account.

[0054] For example, according to some embodiments of this disclosure, the digital currency wallet service platform 130 responds to the verification result that the mobile communication number does not exist and is recycled for reuse, then the login is successful and the user is allowed to receive a digital currency red envelope.

[0055] In one example, the time threshold could be the number recycling idle period set by the telecom operator, such as 180 days. After a mobile number is cancelled, it is not immediately reissued; it is left idle for a period before being reintroduced into the sales system. This number recycling idle period can reduce the risks faced by new users when using a recycled number, such as lowering the likelihood of new users logging into the original owner's account or receiving information related to the original owner, thus protecting the user experience and information security of new users to some extent.

[0056] For example, if the authorized login time is later than the registration time, it indicates that the user's authorized login behavior occurred after the digital currency application account registration. Then, the time interval between these two times is further calculated, and it is determined whether it exceeds the set time threshold. If the user does not log in after the set time threshold after registration, there may be two situations: (1) The user is using the service normally, but has not logged in for a long time; (2) An old user registered a digital currency application account associated with a mobile phone number before the secondary number release, and a new user obtained the mobile phone number through the secondary number release and tried to log in using the mobile phone number. Since there is a possibility of secondary number release in the above situations, the wallet service platform 130 determines that it is necessary to check whether there is a secondary number release after the registration time. If there is a secondary number release, it is determined to be situation (2), and SMS verification can be performed to prove that the current user is the holder of the mobile phone number. If there is no secondary number release, it is determined to be situation (1), the login is successful, and the user is allowed to receive the digital currency red envelope.

[0057] In one example, the wallet service platform 130 has a secondary number release verification mechanism. By calling the secondary number release query interface of the corresponding telecommunications operator for the mobile communication number, it verifies whether the mobile communication number has been secondary released after the "digital currency application account registration time". If it is detected that the mobile communication number is associated with multiple digital currency application accounts, the registration time of the latest associated account is sent as the "digital currency application account registration time" to the telecommunications operator, so that the operator can check whether secondary number release has occurred after that time, and the verification result returned by the operator is obtained and returned. In another example, the wallet service platform 130 can query a local preset number recycling information database (or local cache) to determine whether the current mobile communication number is recorded there. The preset number recycling information database stores the mobile phone number and secondary number release time sent by the telecommunications operator's secondary number release query interface, and / or the mobile phone number and secondary number release time sent synchronously by the servers of various operating institutions.

[0058] For example, in step S440, after confirming that the mobile number is a reissued number, the user's identity is verified by sending a verification code, such as an SMS verification code, thereby confirming the legitimacy of the current mobile number holder and isolating the data permissions of the old and new users to avoid account confusion, privacy leaks, or security risks caused by number recycling. Alternatively, in other embodiments, facial recognition detection can be added to verify that the current user is the mobile number holder.

[0059] For example, according to some embodiments of this disclosure, in step S440, if the received verification result indicates that the mobile communication number is a recycled and reused resource, in step S450, if the user's identity verification is successful, the wallet service platform 130 will also mark the digital currency application account (also known as the "old account") associated with the mobile communication number before the number was recycled and reused, and can also identify the login status of the digital currency application account. It should be noted that the old account was associated with the mobile communication number before the number was recycled and reused, and is in a valid association state after the number is recycled and reused. The "pre-reserved" digital currency red packet means that the wallet service platform 130 records the red packet under the corresponding mobile communication number. After the user registers a new digital currency application account and opens a digital currency wallet using the mobile communication number, the red packet can be stored in the digital currency wallet associated with the digital currency application account for use in subsequent digital currency business.

[0060] For example, according to some embodiments of this disclosure, in step S420, the step of determining whether to check whether the mobile communication number has been recycled and reused after the registration time includes: if the user group of the lightweight application is an existing user outside the validity period of the no-login period, 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, then it is not checked whether the mobile communication number has been recycled and reused after the registration time, and the identity verification process is triggered to verify the user's identity. In response to the result of successful identity verification, the login is successful, and the user is allowed to receive a digital currency red envelope. An example of the above scenario is: an old user has not registered a digital currency application account and has authorized login to the WeChat mini program to receive a red envelope (at this time, the background is pre-reserving the red envelope). After obtaining the mobile phone number, a new user first registers a digital currency application account but has not yet authorized login to the WeChat mini program. At this time, the authorized login time will be before the account registration time.

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

[0062] In one example, if a user authorizes login but registers a digital currency application account after a set time threshold has elapsed, the login process might fall into the following categories: the digital currency application account is a new account registered by a new user who obtained the phone number through a secondary number allocation process, and the existing user did not register a digital currency application account before the secondary number allocation. Therefore, if the time difference between the authorized login time and the registration time exceeds the set time threshold (assuming the above situation), secondary number allocation will not be checked, and the user will be guided to verify their identity using methods such as SMS verification. If the verification is successful, the new user logs in successfully and is allowed to receive a digital currency bonus; if the verification fails, the user cannot receive the digital currency bonus. If the difference between the user's authorized login time and the registration time is within the set time threshold, it is considered that there is no secondary number allocation involved, and the user logs in successfully and receives the bonus.

[0063] Figure 4 A flowchart illustrating another digital currency red packet management method 400' according to at least one embodiment of the present disclosure is shown. Method 400' mainly describes the processing logic for users claiming red packets through a digital currency red packet mini-program 1210, such as a digital currency red packet app or H5 page, in a secondary red packet distribution scenario, when the user is identified as an existing user within the no-login validity period. The following refers to... Figure 1 and Figure 4 The method steps of the embodiments of this disclosure will be explained.

[0064] In step S410, the wallet service platform 130 receives and responds to the user's login request to log in to the digital currency red envelope mini-application 1210, and identifies the mini-application user group to which the user belongs. This step is consistent with the steps in the previous embodiment, and will not be repeated here.

[0065] In step S420, if the user's light application user group is an existing user within the login-free validity period, then step S460 is executed. In this step, the user group can be determined by combining multi-dimensional information such as time window, device identifier, and login status validity.

[0066] When a user clicks to log in to the mini-program, the system checks if a login-free token is cached locally. If it exists, the system checks if the token is valid (login status validity). If valid, the system checks if the user is within the login-free period (time window). If the user is within the login-free period, the system matches the user's device identifier (including the WeChat identifier on the mini-program and the device fingerprint on the device). If the match is found, the system determines that the current user is an existing user within the login-free validity period.

[0067] In step S460, 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.

[0068] In step S460, 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 (S470); otherwise, the association between the login-free token and the first digital currency application account is cleared, and the new user login process is initiated (S480).

[0069] As mentioned earlier, when authorizing login to the digital currency red envelope mini-program via WeChat, for example, the wallet service platform 130 generates a login-free token, returns it to the mini-program, and caches it locally on the user's device 120. Correspondingly, the wallet service platform 130 also stores this token together with the digital currency account associated with the authorized login mobile number. After obtaining the login-free token, the wallet service platform 130 checks whether the first digital currency application account corresponding to the token is consistent with the second digital currency application account associated with the previously authorized login mobile number. Generally, for existing users, since they have previously authorized login to the mini-program using the same mobile number and have not changed the mobile number, the digital currency application account associated with the login-free token should be completely consistent with the digital currency application account bound to the previously authorized login mobile number, provided the login-free token is valid. The user automatically passes verification and can directly receive the digital currency red envelope after clicking on the mini-program without any additional action.

[0070] For example, in the following scenario, account inconsistencies may occur: An existing user is still within the no-login period, but their phone number has been reissued. A new user uses that phone number to register a new cryptocurrency application account. When the existing user logs into the mini-program to claim a cryptocurrency reward, the cryptocurrency application account associated with the no-login token will be inconsistent with this new account because the previously authorized login phone number is now linked to a different cryptocurrency application account. In this scenario, the wallet service platform 130 will clear the association between the token and the cryptocurrency application account, triggering the user to re-authorize their phone number to log in to the mini-program and claim the reward. At this point, the existing user should also be reminded to change the phone number linked to their cryptocurrency application account to prevent conflicts when conducting cryptocurrency transactions with a new user's cryptocurrency application account registered using the same phone number.

[0071] For example, in some embodiments of this disclosure, the above method further includes: the wallet service platform 130 responds to the user's request to distribute digital currency red envelopes initiated in the digital currency application, queries the associated digital currency application account based on the mobile communication number in the distribution request, and if there are multiple digital currency application accounts, sends a prompt message to the digital currency application to prompt the user to distribute digital currency red envelopes through the host platform, which has social application attributes.

[0072] In one example, a function to query the linked digital RMB application accounts for mobile phone numbers has been added when users send out digital RMB "exclusive red envelopes." Specifically, after the user sending the "exclusive red envelope" fills in the recipient's mobile phone number on the digital currency app's 1200 page and clicks the "Add Red Envelope" button, the wallet service platform 130 checks whether the recipient's mobile phone number corresponds to multiple digital currency application accounts. If the entered mobile phone number corresponds to only one digital currency application account, the subsequent red envelope sending process proceeds; if it corresponds to more than two digital currency application accounts, a pop-up window is displayed on the page prompting, "The following mobile phone number is linked to multiple digital RMB APP accounts. You can choose to send a 'group red envelope' and share it with designated friends via WeChat / QQ / Alipay." Because after sending a "group red envelope," the sender needs to share the red envelope link to their social media chat box to clearly identify the user or group receiving the red envelope, this avoids the incorrect sending of red envelopes.

[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. Reference is made below. Figure 2 Let's explain the digital currency wallet service platform 130.

[0074] like Figure 2As 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. User group identification module 130A is configured to receive and respond to user login requests for the digital currency red envelope mini-application, identify the user group to which the user belongs, wherein 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; Number recycling judgment module 130B is configured to, if the user's user group to which the user belongs is an existing user or a new user whose login exemption period has expired, determine 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 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; Identity verification module 130C is configured to, in response to the verification result that the mobile communication number has been recycled and reused, trigger an identity verification process for the mobile communication number to verify the user's identity if the verification result is determined; Red envelope management module 130D is configured to, in response to the identity verification result, mark the digital currency application account associated with the mobile communication number before the number was recycled and reused, pre-claim the digital currency red envelope, and prompt the user to register a digital currency application account.

[0075] For example, according to some embodiments of this disclosure, the number recycling judgment module 130B is further configured to perform the following operations to determine the authorized login time: if the user initiates a request to receive a digital currency red packet without changing the mobile communication number, the time when the host platform authorizes login to the digital currency red packet mini-application is taken as the authorized login time; if the user changes the mobile communication number and initiates a request to receive a digital currency red packet, the time when the user changes the mobile communication number is taken as the authorized login time.

[0076] For example, according to some embodiments of this 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, 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; if the time difference is less than the set time threshold, the login is successful and the user is allowed to receive a digital currency red envelope.

[0077] For example, according to some embodiments of this disclosure, the number recycling judgment module 130B is further configured to perform the following operations: if the user group of the light application is an existing user outside the validity period of the login exemption, and the current login time is before the registration time, then it is determined whether the time difference between the first authorized login time and the registration time exceeds a set time threshold. If the time difference exceeds the set time threshold, then it does not check whether the mobile communication number has been recycled and reused after the registration time, and triggers the identity verification process to verify the user's identity. In response to the result of successful identity verification, the login is successful, and the user is allowed to receive a digital currency red envelope.

[0078] For example, according to some embodiments of this disclosure, the red envelope management module 130D is also configured to perform the following operation: in response to the verification result that the mobile communication number does not exist for number recycling and reuse or the judgment result that the time difference is less than a set time threshold, the login is successful and the user is allowed to receive digital currency red envelopes.

[0079] For example, according to some embodiments of this disclosure, the red packet management module 130D is configured to perform the following operations: if the user's light application user group is an existing user within the validity period of the no-login period, then it is determined whether the first digital currency application account associated with the no-login 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 consistent, then the user is allowed to receive the digital currency red packet; otherwise, the association between the no-login 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 this disclosure, the red packet management module 130D is further configured to perform the following operations: in response to a user's request to distribute digital currency red packets initiated in a digital currency application, querying the associated digital currency application account based on the mobile communication number in the distribution request; if there are multiple digital currency application accounts, sending a prompt message to the digital currency application to prompt the user to distribute digital currency red packets through a host platform, wherein the host platform has social application attributes.

[0081] The additional aspects of the wallet service platform 130 according to at least one embodiment of the present disclosure can correspond to the additional aspects of the digital currency red envelope management method 400, 400' according to at least one embodiment of the present disclosure. Therefore, the technical effects of the additional aspects of the management method 400, 400' according to at least one embodiment of the present disclosure can also be mapped to the additional aspects of the management method 400, 400' according to at least one embodiment 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-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 tagging process, when the wallet service platform 130 confirms that a mobile communication number belongs to a secondary number resource through the data interface of a telecommunications operator or a preset number recycling information database, it will add a special identification tag to the first digital currency application account associated with that mobile communication number in the local account database. This tag can contain detailed tagging information, such as the specific time of number recycling, the timestamp of the tagging operation, and the reason for the tagging. In addition, the wallet service platform 130 will also synchronize this tagging information to various subsystems or modules associated with the account, including but not limited to the account login verification module, transaction processing module, and risk warning module, to ensure that the entire digital currency application account management system can be aware of the special status of the account in a timely manner and take appropriate action.

[0088] In some embodiments, the wallet service platform 130 will initiate a mechanism to identify the login status of the first digital currency application account. For example, in the account login process, this includes a logged-in status for the first digital currency application account, and a login in progress status when it is detected that the mobile communication number is being used to attempt password login or other non-password login methods to the first digital currency application account and to retrieve the login password.

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

[0090] In some embodiments of this disclosure, specific matters include: the wallet service platform 130 determining whether to use the mobile communication number to register a second digital currency application account (new account), whether to use the mobile communication number to open a digital currency wallet (new wallet) of a digital currency operator, and / or whether there is an association 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 is recycled and reused, and the second digital currency application account is the digital currency application account associated with the mobile communication number after the number is recycled and reused.

[0091] In some examples, new users of a reissued mobile number may attempt to register a new account associated with that mobile number through the Digital Currency App 1200, or use that mobile number to open a new wallet of a digital currency operator. Although the current mobile number is a reissued number, as long as it is detected that the mobile number has not been registered with a digital currency application account or opened a digital currency wallet of an operator after the reissue, the new user's account registration and wallet opening are allowed.

[0092] Wallet service platform 130 is responsible for parsing and verifying registration and activation requests during the digital currency application account registration or digital currency wallet activation process. After digital currency application account registration and digital currency wallet activation are completed, it can see in real time that a new digital currency application account has been registered and a new digital currency wallet has been activated using a specific mobile phone number, and determine whether there is a correlation between the two. Furthermore, wallet service platform 130 can also determine the above information based on the user information (including mobile phone number), digital currency application account, and digital currency wallet association table stored in its local database.

[0093] For example, in some embodiments of this disclosure, in step S230, the wallet service platform 130 performs at least one of the following operations on the first digital currency application account based on the identified login status of the first digital currency application account and the determination result of specific matters: performing account access control corresponding to the login status, pushing a prompt message to modify the mobile communication number using a multi-dimensional notification system, and guiding the user to modify the mobile communication number through the digital currency application.

[0094] For example, in one instance, the wallet service platform 130 can obtain real-time login status data of the first digital currency application account and associated operation data of the secondary mobile phone number through different data interfaces. Login status data can include basic status and risk status. Basic status includes: logged in, not logged in, and logging in; risk status includes, for example, login from a different location, high-frequency login failures (≥5 times), login from a new device (device fingerprint not recorded), and silent login (no operation for more than 30 minutes). Associated operation data includes the registration status of the second digital currency application account (new account): registered or not registered; the activation status of the digital currency wallet (new wallet): activated with the target operator A's wallet, not activated; and the association status: the new account is associated with the new wallet, and the new wallet is not associated with any account.

[0095] In the embodiments of this disclosure, the login status mainly includes logged in and logged in. For logged-in old accounts, a forced logout account access control operation can be performed; for logged-in old accounts, login-related operations are suspended.

[0096] For example, in some embodiments of this disclosure, the multi-dimensional notification system pushes key information (such as "Modify Phone Number Prompt") to users through multiple independent and complementary communication channels. This is mainly to ensure that users receive important notifications in a timely and accurate manner, improving notification reach and operational 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, notifications are pushed through the Digital Currency App, such as through pop-up banners or pop-up windows, displaying guidance information for changing phone numbers and adding a "Change Phone Number" entry control, which allows users to jump to the corresponding phone number modification page. The Digital Currency App's in-app messaging system, such as the message center module within the Digital Currency App, can also be used for push notifications. The out-of-app message mode refers to a mechanism where messages are transmitted and delivered through external communication channels or infrastructure of the Digital Currency App. Its 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 rather achieve cross-system information interaction through third-party general channels. For example, a push notification can be used to send a notification to the user device 120. This notification may include the user ID, the currently bound mobile phone number, an operation prompt (such as "A risk of secondary number issuance has been detected. Please change the bound mobile phone number in time"), and a secure link (redirecting to the digital currency app or official website). External message mode can also use email notifications or social media / instant messaging to notify users of changes to their mobile phone numbers, but this disclosure does not limit this approach.

[0097] For example, in some embodiments of this disclosure, when performing corresponding operations on the first digital currency application account, the steps may include at least one of the following operations: if a second digital currency application account has been registered, or a digital currency wallet is associated with the second digital currency application account, and the first digital currency application account is detected to be logged in (referred to as the first scenario), a login termination operation is performed, and a first prompt message to modify the mobile communication number associated with the first digital currency application account is pushed through an external message mode; if a second digital currency application account has been registered, or a digital currency wallet is associated with the second digital currency application account, and the first digital currency application account is detected to be logged in (referred to as the second scenario), a login suspension operation is performed, and a second prompt message to modify the mobile communication number is pushed to the first digital currency application account through an internal message mode; if a second digital currency application account has not been registered, but a digital currency wallet has been activated (referred to as the third scenario), a third prompt message to modify the mobile communication number is pushed to the first digital currency application account through an internal message mode.

[0098] Example 1 of the first scenario: When a new user successfully registers a digital currency App account B, if it is detected that an old user's digital currency App account A is already logged in, the user will be immediately "kicked out" of the digital currency App account A through the digital currency App 1200, and a message will be pushed to the old user outside the platform to remind them to change their mobile phone number. The content of the first prompt message can be the same as or similar to the content of the second prompt message in the second scenario.

[0099] Example 2 of the first scenario: When a new user successfully registers a digital currency App account B and simultaneously associates it with a digital currency wallet W, if it is detected that an old user's digital currency App account A is already logged in, the user will be immediately "kicked out" of the digital currency App account A through the digital currency App 1200, and a message will be pushed to the old user outside the platform to remind them to change their mobile phone number. The content of the first prompt message can be the same as or similar to the content of the second prompt message in the second scenario.

[0100] After determining that the phone number was reissued, the original user's digital currency app account A will be "kicked out" and will be in an logged-out state. An instant notification can be sent to the user's device 120 via a push message, for example. This notification doesn't require the user to actively open the digital currency application; it will appear directly in the notification bar, lock screen, or pop-up window on the user's device 120. Clicking the notification will take the user to the corresponding page to change their phone number. For example, the initial push message could read: "Please change your phone number as soon as possible to ensure your normal use of digital RMB services." Clicking the push message will lead to the page for changing the phone number.

[0101] Example 1 of the second scenario: When a new user successfully registers a digital currency App account B, after determining that the mobile phone number is a second-hand number, if an existing user tries to log in to the digital currency App account A using password login or other non-password methods or tries to retrieve the password for the digital currency App account A, the user's operation will be stopped, and a second prompt message will be displayed in a pop-up window, strongly reminding the user to change the mobile phone number of the digital currency App account A.

[0102] Example 2 of the second scenario: When a new user successfully registers a digital currency App account B and simultaneously links it to a digital currency wallet W, after determining that the mobile phone number is a second-hand number, if an existing user tries to log in to the digital currency App account A using the digital currency App 1200 with a password or other non-password method, or tries to retrieve the password for logging into the digital currency App account A, the user's operation will be stopped, and a second prompt message will be displayed in a pop-up window, strongly reminding the user to change the mobile phone number of the digital currency App account A.

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

[0104] Pop-up location: Located on the login page of the Digital Currency App 1200.

[0105] Pop-up window appears when: Existing users have not switched devices, have local login information, and attempt to log in to the cryptocurrency app without logging in.

[0106] Pop-up priority: Last of all pop-ups.

[0107] Pop-up notification text:

[0108] "Your current mobile number has been registered by a new user. To ensure you can use the digital RMB service normally, please change your mobile number as soon as possible."

[0109] The system provides entry controls for "I understand" and "Change phone number". Clicking "I understand" will make the pop-up disappear, while clicking "Change phone number" will redirect you to the process of changing your account's phone number in a non-login state.

[0110] Example of the third scenario: A new user has not yet registered any digital currency application account using the reissued mobile number, but a digital currency operator has opened a new digital currency wallet B using the mobile number, and this is identified as a reissue scenario. If there is an old digital currency wallet A that is bound to a digital currency application account A opened with the same mobile number, the digital currency app will receive a notification and push an in-app message to the digital currency application account A to guide the old user to change the mobile number of the digital currency application account A. At this time, the user will not be "kicked out" of the login state of the digital currency application account A.

[0111] For example, in some embodiments of this disclosure, guiding a user to modify a mobile communication number through a digital currency application includes: displaying a user interface for modifying the mobile communication number; receiving the modified mobile communication number entered by the user on the user interface; completing the authentication of the modified mobile communication number; and after successful modification, unlinking the mobile communication number originally associated with the first digital currency application account and binding the modified mobile communication number.

[0112] According to the embodiments of this disclosure, when a new digital currency application account or digital currency wallet is detected to be opened using the same mobile phone number, the login status of the old account is terminated or the login is suspended, avoiding identity confusion, financial risks, or operational conflicts caused by duplicate mobile phone number binding. Regardless of whether the old digital currency application account is in a "login" or "login in progress" scenario, a clear mobile phone number modification prompt is pushed through the corresponding in-app or external channels to ensure that the old user can promptly discover and correct the duplicate mobile phone number binding issue. Moreover, through a scenario-based differentiated message push strategy, it can be ensured that users receive mobile phone number correction guidance in a timely manner, guaranteeing the normal use of both new and old digital currency application accounts.

[0113] For example, in some embodiments of this disclosure, method 200 further includes: wallet service platform 130 sending a notification message to the digital currency operating institution of other digital currency wallets opened using the mobile communication number associated with the first digital currency application account, 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 a digital currency application account is labeled as a "secondary account," the Digital Currency App 1200 will simultaneously notify the wallet operators of other digital currency wallets opened with that mobile number under the old account, informing them that the old wallet opened with that mobile number has been reissued.

[0115] In one example, the wallet service platform 130 retrieves information such as wallet IDs and operating institution codes (which can be anonymized and do not include sensitive data such as the original user's name and ID number) from the account-wallet association table in the local account database for all wallets opened using the old account with that mobile number. The wallet service platform 130 sends notification messages to each wallet operating institution 1 through the interconnection platform. The notification message may include: the reissued mobile number, the old wallet ID, and the old account registration time (YYYY-MM-DD HH:MM). The notification message may also include a risk warning: "This mobile number has been reissued. There may be a risk of new users mistakenly associating the original wallet with it. Please check the wallet status and take security measures."

[0116] Figure 6 A flowchart of another method 300 for managing digital currency application accounts according to at least one embodiment of the present disclosure is shown. Method 300 mainly addresses the following scenario: In a secondary account allocation process, a new user has registered a digital currency application account B and bound it to a mobile phone number M1. The new user then purchases a mobile phone number M2 from a telecom operator, intending to change the bound mobile phone number M1 to M2; however, mobile phone number M2 is a number previously used by an existing user and is already bound to a digital currency application account A. In this scenario, when the new user tries to change the bound mobile phone number to M2, it will be detected that mobile phone number M2 is already occupied by digital currency application account A and cannot be modified. To solve the problem in the above scenario, method 300 provides a specific solution. See below for reference. Figure 6 The method steps of the embodiments of this disclosure will be explained.

[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 mobile communication number currently associated with the target digital currency application account. The first modification request includes the modified target mobile communication number.

[0118] For example, when a user initiates an operation to modify the mobile phone number bound to a digital currency application account through the digital currency App 1200, after the operation triggers the "mobile phone number modification" function control inside the App, the App client encrypts and encapsulates the parameters such as the modified mobile phone number, user identity token, operation timestamp, and device fingerprint information entered by the user 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 executed. If it has been associated with other digital currency application accounts, step S330 is executed. Specifically, the other digital currency application accounts establish an association with the target mobile communication number before the number is recycled and reused, and remain in a valid association state after the number is recycled and reused.

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

[0121] Other digital currency application accounts refer to old accounts associated with the target mobile phone number. The content of other digital currency application accounts is similar to that of the first digital currency application account in the previous embodiment, and can be found in the previous content, so it will not be repeated here.

[0122] After parsing the target mobile number, the wallet service platform 130 can search the account database to determine whether there is a currency account associated with the target mobile number. If no account is found, it means that the target mobile number is not in use, and step S340 is executed to modify the mobile number. Otherwise, the business logic of the second number release verification continues to be initiated.

[0123] In step S330, it is checked whether the target mobile communication number has been recycled and reused after the registration time of other digital currency application accounts. If so, proceed to step S340. Otherwise, proceed to step S350. For details regarding the wallet service platform 130's verification of whether the target mobile number has been reissued, please refer to the relevant content in the aforementioned example; it will not be repeated here.

[0124] In one example, if it is found that the target mobile number has been reissued, it means that other cryptocurrency application accounts were registered before the target mobile number was reissued. Therefore, it does not affect the use of the target mobile number by new users after the target mobile number is reissued, and the mobile number can be changed to the target mobile number.

[0125] In step S340, in response to the verification result that the target mobile communication number has been recycled and reused, 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.

[0126] In step S350, a notification message is sent to the Digital Currency App 1200.

[0127] In the embodiments of this disclosure, the wallet service platform 130, in response to the fact that the target mobile communication number has not been recycled and reused after the registration time of other digital currency application accounts, sends a notification message to the digital currency App 1200 indicating a binding conflict. This notification message can be displayed, for example, through a pop-up window within the digital currency App (in-app message mode), and the notification text can be set to "This mobile number is already bound to another account".

[0128] For example, in some embodiments of this disclosure, method 300' further includes: the wallet service platform 130 sending a notification message to the digital currency operating institution to which other digital currency wallets opened using the target mobile communication number belong, and the notification message indicates that the target mobile communication number used to open the digital currency wallet is a number recycling resource. This step can be referred to the relevant content in the foregoing embodiments and will not be repeated here.

[0129] In the above embodiments, after the wallet service platform 130 receives the first modification request to modify the mobile phone number associated with the digital currency application account, if it detects that the target digital currency application account is not associated with a digital currency wallet or does not consider the modification permission of the operating institution to which the digital currency wallet to which the digital currency application account belongs, it can modify the mobile phone number associated with the target digital currency application account after completing the above business processes.

[0130] Figure 7 A flowchart of a method 300' for managing another digital currency application account according to at least one embodiment of the present disclosure is shown. Method 300' is mainly aimed at... Figure 7 Another solution for the scenario shown is for when a target cryptocurrency application account is linked to a cryptocurrency wallet. Steps that are the same as or similar to method 300 are indicated by the same labels and will not be repeated; only the differences will be explained. See below for reference. Figure 7 The method steps of the embodiments of this disclosure will be explained.

[0131] In step S330, if the target mobile communication number is subject to number recycling and reuse, then step S360 is executed.

[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. If there is, it sends a modification operation permission request to the digital currency operating institution to which all digital currency wallets associated with the target digital currency application account belong. The modification operation permission request indicates whether it is allowed to modify the mobile communication number currently associated with the digital currency wallet to the target mobile communication number.

[0133] When modifying the mobile phone number associated with a cryptocurrency application account, if the account is also associated with multiple cryptocurrency wallets, full permission from the relevant cryptocurrency operating institutions is required. This is primarily because different operating institutions may have personalized risk control rules (e.g., Bank A requires a domestic mobile phone number). If an institution does not agree to the modification (e.g., the target mobile phone number does not meet its compliance requirements), it indicates a potential risk, and the modification process must be terminated to avoid potential vulnerabilities.

[0134] In addition, it can also prevent account takeover attacks. If an attacker passes the secondary number release verification by forging operator data, since there is also a step of permission modification by the digital currency operator, the operator can refuse the modification through independent risk control rules (such as detecting that the modification request IP does not match the commonly used login location), forming a security barrier of "multi-institutional cross-verification" to avoid the risk of account theft caused by the failure of a single institution's verification.

[0135] If it is determined in this step that the target mobile number is not associated with a digital wallet, then step S340 can be executed directly to modify the mobile number of the target account.

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

[0137] For example, in some embodiments of this disclosure, step S370 further includes: if any digital currency operator returns a response indicating refusal to allow the modification operation or fails to respond within a timeout period, a risk warning message containing digital currency wallet information indicating refusal to modify the mobile communication number is generated and sent to the digital currency application 1200. If all digital currency operators return response information indicating agreement to allow the modification operation, the mobile communication number currently associated with the target digital currency application account is modified to the target mobile communication number, and other digital currency application accounts (old accounts) are marked and their login status is identified. Based on the identified login status of other digital currency application accounts, at least one of the following operations is performed on the other digital currency application accounts: performing account access control corresponding to the login status, pushing a prompt message to modify the target mobile communication number using a multi-dimensional notification system, or guiding the user to modify the target mobile communication number through the digital currency application.

[0138] In one example, after receiving response information from various operating institutions, the wallet service platform 130 identifies the meaning of the response information. The response information includes states such as "agree to permission modification", "reject permission modification", and "response timeout". The "reject permission modification" status also carries a specific rejection code, such as "001 - Risk of login from a different location" or "002 - Risk of non-domestic mobile phone number".

[0139] When the wallet service platform 130 receives a rejection message or a response timeout status, it can generate a risk warning message containing multiple core fields. For example, the risk warning message may include: wallet ID, target mobile number, visual rejection code (e.g., "New mobile number detected as an overseas number, modification not currently supported"), abbreviation of the institution where the rejection timeout occurred, and user operation suggestions. Afterwards, a risk warning message is sent to the digital currency app 1200, which can be sent via a landing page. The message text could be something like: "XX Bank rejects mobile number modification; the new mobile number is an overseas number, posing a significant risk."

[0140] For example, in some embodiments of this disclosure, in step S370, the step of performing at least one of the following operations on other digital currency application accounts includes: if it is detected that another digital currency application account has been logged in, then a login state termination operation is performed, and a first prompt message to modify the target mobile communication number associated with the other digital currency application account is pushed through an external message mode outside the digital currency application; if it is detected that someone wants to log in to another digital currency application account, then a login abort operation is performed, and a second prompt message to modify the target mobile communication number is pushed to the other digital currency application account through an internal 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 a 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 methods 400, 400', 200, 300, 300' and their additional aspects according to at least one embodiment of the present disclosure. When executed by the processor 610, they can perform one or more steps of methods 400, 400', 200, 300, 300' and their additional aspects according to at least one embodiment of the present disclosure. The memory 620 and the processor 610 can be interconnected via a bus system and / or other forms of connection mechanisms (not shown). For example, the bus may be a Peripheral Component Interconnect Standard (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

[0148] For example, processor 610 may be a central processing unit (CPU), a digital signal processor (DSP), or other processing unit with data processing and / or program execution capabilities, such as a field-programmable gate array (FPGA). Processor 610 may be a general-purpose processor or a special-purpose processor, capable of controlling other components in electronic device 600 to perform desired functions.

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

[0150] For example, electronic device 600 may also include input devices such as touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices such as liquid crystal displays, speakers, and vibrators; storage devices such as magnetic tapes and hard disks (HDDs or SDDs); and communication devices such as network interface cards like LAN cards and modems. The communication devices allow electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data and perform communication processing via networks such as the Internet. A drive is connected to the I / O interface as needed. Removable storage media, such as disks, optical disks, magneto-optical disks, and semiconductor memories, are installed on the drive as needed so that computer programs read from them can be installed into the storage device as required.

[0151] For example, the electronic device 600 may further include a peripheral interface (not shown in the figure). This peripheral interface can be of various types, such as a USB interface, a Lightning interface, etc. The communication device can communicate wirelessly with networks and other devices, such as the Internet, intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs). Wireless communication can use any of a variety 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 may be, for example, a system-on-a-chip (SOC) or a device including the SOC. For instance, it may be any device such as a mobile phone, tablet computer, laptop computer, e-reader, game console, television, digital photo frame, navigator, home appliance, communication base station, industrial controller, server, etc., or any combination of data processing devices and hardware. The embodiments of this disclosure do not limit this. The specific functions and technical effects of the electronic device 600 can be found in the description above of methods 400, 400', 200, 300, 300' and their additional aspects according to at least one embodiment of this disclosure, and 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] like Figure 9 As shown, a non-transitory computer instruction 710 is stored on a computer-readable storage medium 700, which, when executed by a processor, performs one or more steps of the methods 400, 400', 200, 300, 300' and their additional aspects as described above.

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

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

[0157] At least some of the embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other.

[0158] It should be noted that, in this document, relational terms such as "first," "second," etc., are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0159] The following points should be noted regarding this disclosure:

[0160] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0161] (2) Where there is no conflict, the embodiments of this disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0162] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure, which is determined 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 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 digital currency wallet service platform responds to the verification result that the mobile communication number does not have a number recycling and reuse function, then the login is successful and the user is allowed to receive the digital currency red envelope.

7. 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.

8. 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.

9. The method according to claim 1 or 7, 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.

10. 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.

11. The system according to claim 10, 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.

12. The system according to claim 10, 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.

13. The system according to claim 10, 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.

14. The system according to claim 12 or 13, 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.

15. The system according to claim 10, wherein, The red envelope management module is also configured to perform the following operations: If the verification result shows that the mobile communication number has not been recycled and reused, the login is successful and the user is allowed to receive the digital currency red envelope.

16. The system according to claim 10, 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.

17. The system according to claim 10, 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.

18. 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-9.

19. 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-9.

Images