An easy-to-avoid bean generation and management system based on necessity consumption

Abstract

This invention belongs to the interdisciplinary field of Internet applications and data processing, specifically a management system for generating and managing Easy Points based on essential consumer needs. It includes a two-way data interaction architecture with three terminals: the consumer end, the platform hub, and the merchant end. The three terminals achieve real-time data transmission through encrypted data interfaces, and all core functions are automatically executed by the platform hub's program code. The platform hub includes modules for onboarding and category review, consumer demand matching and order placement, fulfillment and intelligent settlement and revenue sharing, a composite location SDK module, an Easy Points generation module, and a user mode switching module. This invention pioneers a dual-identity technology confirmation system for users. Easy Points serve as a unique digital identity credential, fundamentally different from traditional points and coupons, completely avoiding the risk of existing technologies being similar. It adopts a pure technical architecture with three terminals working together, and all rules are automatically executed through program code and algorithm modules, without human intervention in business operation rules.

Description

Technical Field

[0001] This invention relates to the field of interdisciplinary technology of Internet applications and data processing, and in particular to an easy-to-use bean generation and management system based on essential consumer needs. Background Technology

[0002] With the rapid popularization of Internet technology, traditional consumption patterns are gradually transforming into a new retail model that integrates online and offline channels. Existing e-commerce platforms and local life service platforms on the market can only meet basic consumption needs such as commodity transactions, service reservations, and payment settlements. They have obvious technical deficiencies in areas such as user identity definition, long-term rights binding, consumption structure guidance, supply and demand adjustment, and long-term user value retention, and cannot achieve a win-win situation for consumers, merchants, platforms, and society.

[0003] The main drawbacks of existing traditional consumer platforms in terms of core technology are as follows: Firstly, the platform defines users' identities in a simplistic way, defining them only as simple buyers of goods / services. It has not built a dual identity system for users through technical means, nor does it have corresponding modules for identity confirmation, rights labeling, and quantitative management. The relationship between users and the platform is only a one-time, superficial transaction, which cannot form a deep and bound ecological connection, resulting in extremely low user stickiness. Secondly, a differentiated technical control mechanism for essential and non-essential consumption has not been established, and differentiated operating rules and rights distribution logic have not been set for essential consumer goods and high-end non-essential consumer goods, making it impossible to guide rational consumption through technical means. Third, although some platforms offer superficial benefits such as points and coupons, these are all short-term marketing tactics that are one-way subsidies from the platform. They lack a complete technical system for identity verification, data accounting, automatic allocation, and long-term binding, resulting in limited benefits with meager value. Fourth, existing platforms are all purely commercial transaction carriers, without embedded technical regulation modules geared towards people's livelihoods, and are unable to guide consumption in response to national needs for people's livelihoods, nor do they possess the technical extension capabilities at the level of social value. Fifth, it is not connected to the official payment interface of the digital RMB, and payment and settlement rely solely on third-party interfaces, resulting in insufficient technical security for fund transfers.

[0004] Sixth, the data flow between merchants and consumers lacks a closed-loop design, the fulfillment and settlement logic of online direct sales and offline services are not technically differentiated, the fund settlement rules are rigid, and there is no underlying technical module support, making it easy to be identified as a simple business operation model.

[0005] Furthermore, existing consumer management technology solutions mostly focus on superficial rule designs such as fund allocation and simple rights return, without innovation in user identity definition and technical rights confirmation. The solutions themselves lack core technical designs such as a complete three-terminal technical architecture, composite positioning SDK verification, differentiated management of essential and non-essential needs, dynamic category rights adjustment, and non-essential benefits feeding back to essential needs. They only remain at the level of business rules, without specific technical modules, data processes, and program logic support, and have long faced review and questioning, making it difficult to obtain stable authorization. Summary of the Invention

[0006] The purpose of this invention is to address the shortcomings of the prior art by proposing an easy-to-use bean generation and management system based on essential consumer needs.

[0007] To achieve the above objectives, the present invention adopts the following technical solution: A system for generating and managing Easy-to-Earn Beans based on essential consumer needs includes a two-way data interaction architecture that coordinates three ends: the consumer end, the platform hub, and the merchant end. The three ends achieve real-time data transmission through encrypted data interfaces, and all core functions are automatically executed by the platform hub program code. The platform hub includes modules for onboarding and category review, consumer demand matching and order placement, fulfillment and intelligent settlement and revenue sharing, composite positioning SDK, Easy-to-Earn Beans generation, user mode switching, activity statistics, dynamic adjustment based on people's livelihood, data storage and risk control, linked management of account activity, and unique sharing and binding to prevent duplicates. The composite positioning SDK module is used for triple cross-verification of device hardware, network environment and geographical location, and automatically identifies abnormal devices and clears the activity of abnormal accounts. The EasyBeans are a unique digital identity credential automatically generated by the platform based on essential consumption needs. They are used for dual identity verification and rights quantification for users. They have no monetary or financial attributes and are generated automatically without manual allocation. Activity level calculation uses a fixed formula: Unit activity level benefit value = Total legal operating profit of platform non-essential commission ÷ Total effective activity level of the platform; User mode switching supports automatic switching between three-month trial mode and automatic switching when the total amount of Easy Beans exceeds the threshold of essential consumption. Both modes are executed automatically without manual intervention. Specifically, in the trial mode, Easy Beans can be used to redeem goods from merchants within the platform. In Easy Mode, the redemption of goods or enjoyment of the platform's real-time monthly benefits is triggered only when Easy Beans exceed the total amount of essential consumption.

[0008] Preferably, a dual identity system is built for users, where users have both the identity of a traditional consumer of goods / services and the identity of a holder of YiMianDou on the platform. YiMianDou is the only digital carrier for confirming this dual identity, which is fundamentally different from traditional points, coupons, and marketing rebate rights.

[0009] Preferably, the onboarding and category review module includes a merchant onboarding review sub-module and a consumer product category review sub-module; after the merchant submits qualification materials and the platform central review is approved, the onboarding is completed, and the factory direct sales zone is only open to regular manufacturers; the merchant declares the essential / non-essential category tags of the goods / services, which are automatically reviewed and approved by the platform central and then bound, serving as the core basis for subsequent Easy Bean generation and commission collection.

[0010] Preferably, the fulfillment and intelligent settlement revenue sharing module embeds differentiated automatic revenue sharing code logic. For offline instant service scenarios, the platform central hub immediately executes automatic revenue sharing after the merchant completes order verification, without requiring the consumer to confirm receipt. For online logistics delivery scenarios, the platform central hub executes automatic revenue sharing only after the consumer confirms receipt or the system automatically confirms receipt after timeout. The revenue sharing rules are automatically matched by the program.

[0011] Preferably, the Easy Bean generation module automatically generates Easy Beans only for essential consumption verified by the platform's central authority, completing dual identity verification. Non-essential consumption does not trigger the Easy Bean generation logic. The generation of Easy Beans is associated with the user's legitimate promotional behavior, and automatically generates corresponding identity verification credentials.

[0012] Preferably, the user mode switching module is installed on the consumer end, allowing users to choose between an experience mode or an easy-to-use mode. The two modes correspond to different rules for executing identity rights and interests, which are automatically executed by the platform's central program, and the mode switching data is retained in real time.

[0013] Preferably, the activity statistics module automatically collects consumers' essential consumption data from the platform's central hub to calculate user activity, and non-essential consumption is not included in the statistics; for users with an activity level of 0, the system automatically freezes their sharing link rights and platform gain conversion rights to prevent them from lying down and controlling their activity.

[0014] Preferably, the dynamic adjustment module for people's livelihood is embedded in the platform's central hub and is a technical unit with adjustable backend parameters. It can dynamically adjust the weight of Easy Bean generation for essential consumer goods such as maternal and infant products and agricultural products; and implement differentiated high commission rates for non-essential high-end consumption, with the commission revenue automatically fed back to the Easy Bean distribution process for essential consumer goods.

[0015] Preferably, the data storage and risk control module encrypts and retains all operation data, consumption data, identity verification data, Easy Beans data, settlement data, activity data, and mode switching data across the three terminals throughout the entire process, generating an unalterable operation log; at the same time, it is equipped with a risk control monitoring unit to automatically identify and intercept abnormal orders, abnormal Easy Beans generation, and abnormal settlement behavior.

[0016] Preferably, the composite positioning SDK module is used for triple cross-verification of device hardware, network environment, and geographical location. Specific implementation steps include: When a user device starts up and logs into the system, the module automatically and silently starts the verification process. Three types of core data were collected step by step and cross-compared: unique fingerprint information of the device hardware layer; physical address of the currently connected WiFi router and network environment parameters; and real-time geographical location information of the user's consumption scenario. The system backend has a pre-set database of abnormal devices, which automatically compares and identifies virtual machines, multi-instance tools, modified devices, and simulates and locates cheating scenarios. When an account is identified as an abnormal or fake account, the system automatically resets the account's activity level to zero, blocks fake consumption data from entering the algorithm's calculation pool, and retains only valid consumption data from real devices, real networks, and real locations.

[0017] Compared with the prior art, the advantages of the present invention are as follows: Breakthrough in identity innovation and clear technical rights confirmation: It pioneers a dual-identity technical rights confirmation system for users, with Easy Beans serving as the unique digital identity credential, which is fundamentally different from traditional points and coupons; Complete technical architecture to avoid review risks: It adopts a three-terminal collaborative pure technical architecture, and all rules are automatically executed through program code and algorithm modules, without human intervention in business operation rules; Composite location SDK risk control prevents cheating at the source: Through triple verification of device, network, and location, it completely eliminates fake accounts and bulk cheating, ensuring the authenticity and validity of data; Intelligent settlement of obligations, tailored to real-world scenarios: Differentiated intelligent revenue sharing logic adapts to both offline instant services and online logistics delivery scenarios, avoiding consumer disputes; Differentiated consumption management to guide rational consumption: Only essential consumption generates free points, while non-essential consumption is subject to high commission rules, using technical means to guide rational consumption; It has an embedded module for people's livelihood and has social value: it can dynamically adjust the weight of Easy Beans for essential categories such as maternal and infant products and agricultural products, help implement people's livelihood policies, and regulate market supply and demand. A closed-loop system for equity distribution achieves a win-win situation for all parties: non-essential revenue automatically feeds back into essential consumption, balancing the interests of consumers, merchants, platforms, and the public. The mechanism to prevent complacency is robust, and the ecosystem is sustainable: additional benefits are automatically frozen when the activity level is 0, forming a closed loop of "self-consumption, sharing and promotion, and platform benefits"; Attached Figure Description

[0018] Figure 1 This is a framework diagram of an easy-to-use bean generation and management system based on essential consumption proposed in this invention; Figure 2 This is a functional module block diagram of an easy-to-use bean generation and management system based on essential consumption proposed in this invention; Figure 3This invention presents a business process diagram for merchant onboarding and category review of an Easy-to-Ease Beans Generation and Management System based on essential consumer needs. Figure 4 This is a block diagram of the fulfillment and intelligent settlement and revenue sharing logic of an Easy-to-Ease Bean Generation and Management System based on essential consumption proposed in this invention. Figure 5 This invention presents a link diagram of Easy-to-Ease Bean generation and identity verification in a management system based on essential consumption. Detailed Implementation

[0019] The technical solutions in this embodiment will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this embodiment, and not all embodiments.

[0020] Example 1 Reference Figures 1-5 This is a management system for generating and managing Easy Beans based on essential consumer needs. It includes a two-way data interaction architecture that coordinates three ends: the consumer end, the platform hub, and the merchant end. The three ends achieve real-time data transmission through encrypted data interfaces, and all core functions are automatically executed by the platform hub's program code. The platform hub includes modules for onboarding and category review, consumer demand matching and order placement, fulfillment and intelligent settlement and revenue sharing, a composite positioning SDK module, Easy Bean generation, user mode switching, activity statistics, dynamic adjustment based on public welfare, data storage and risk control, linked management of account activity, and a unique sharing and binding module to prevent duplicate transactions. The account activity linkage control module specifically includes: Account activity linkage control rules (a) Detailed explanation of the rules The system categorizes all user accounts by activity level. If an account is determined to be inactive, two restrictions will be triggered simultaneously: 1. When this account acts as the sharing leader, no Easy Points will be generated for any of the downstream users associated with it in the sharing chain; 2. The commission rebate mechanism for non-essential business segments on the platform will cease operation simultaneously, and no more rebate-related data or rights will be generated.

[0021] The above two functions will only automatically resume normal operation once the account returns to normal activity.

[0022] (II) Complete Technical Implementation Logic Account activity status determination module The system has a built-in activity detection algorithm that uses a dual mode of "behavior triggering + timed polling" to verify user status. The verification dimensions include user login, platform operation, consumption behavior, and interaction behavior, and a unified activity judgment threshold is preset. Add a field user_active_flag (activity status flag) to the user basic information data table. The field assignment rule is: 1 = normal active status, 0 = no active status. The algorithm calculates user activity in real time. Once the value falls below a preset threshold, it automatically updates user_active_flag to 0. After a user generates effective behavior and the activity level reaches the target, it automatically returns to 1, and the status data is persistently stored.

[0023] Easy-to-use bean generation link interception technology logic A new pre-state verification node has been added to the entry point of the existing EasyBean generation algorithm as a mandatory step: When a lower-level user's behavior triggers the conditions for generating EasyBeans, the system first traces back to the corresponding upper-level sharing account ID; Query the user_active_flag status based on the parent account ID: Status 1 (Normal and Active): The entire process of Easy Beans numerical calculation, account crediting, and data retention is being executed normally. Status 0 (no activity): The Easy Bean generation process is terminated directly. No calculations are performed, no account data is written, no transaction records are generated, and "Activity Interception - Easy Bean Not Generated" is marked in the business log table.

[0024] Technical Logic for Shutting Down Non-Essential Businesses (Commission Rebate, Subsidy, and Closure) The platform splits essential and non-essential business into modules, with commission and rebate calculation units deployed independently for each type of business. Activity status verification is bound to the front end of the non-essential business module. When a non-essential business generates an order / transaction, the commission rebate process is triggered. The system first verifies the user_active_flag of the corresponding superior sharing account. Status 1 (Normal Activity): Commission statistics, rebate amount conversion, and rights distribution have been completed normally; Status 0 (no activity): Directly cut off the cashback link for non-essential sectors, do not collect commission data, do not calculate cashback amount, do not generate any related business data, and log synchronously mark "Activity interception - non-essential cashback disabled".

[0025] Data traceability fallback design A separate business interception log table is set up to record the interception time, user ID, interception type, and triggering scenario. This is used for backend data verification and problem tracing without affecting the operation of the main business table.

[0026] The specific steps for sharing and binding a unique anti-duplicate module are as follows: Share binding unique anti-duplicate rules + technical implementation (a) Detailed explanation of the rules For scenarios where multiple users initiate sharing and binding to the same target user (e.g., A initiates sharing and binding to B, and subsequently C initiates sharing and binding to B again), the system implements an initial binding effective and lifetime unique binding mechanism: Only the first successfully established sharing and binding relationship will be recognized by the same target user; All subsequent repeated sharing and binding requests for this user will be rejected, and no new binding relationship will be established. Repeated binding will not update the sharing link, will not repeatedly count the sharing level, and will not repeatedly generate Easy Beans and various rebate benefits, thus completely avoiding the problems of repeated binding and repeated calculation; Only after the original binding relationship is legally terminated can the target user accept a new sharing binding.

[0027] (II) Complete Technical Implementation Logic Underlying data table structure design (limiting duplicates at the source) Establish an independent main table for sharing and binding relationships, and set the target user ID as a unique primary key / unique index in the database to prevent the generation of multiple binding records for the same target user from the underlying data.

[0028] Core fields: target_user_id: The target user ID (unique index) to which the share is bound. source_user_id: User ID of the user who initiated the sharing bind_create_time: The time of the first binding. bind_status: Binding status Full-process verification of sharing binding requests The front-end initiates a sharing and binding request, transmitting two core parameters, "Initiator ID" and "Target ID," to the back-end interface. After receiving the request, the backend interface will first perform a uniqueness query: query the sharing binding relationship table based on target_user_id; The execution logic is divided into two scenarios: Scenario 1: No valid binding record found (first binding) Once the new binding is deemed legitimate, data is written, establishing a "initiator-target" binding relationship. The user profiles, sharing hierarchy links, and hierarchical relationship information of both parties are updated simultaneously, allowing normal participation in services such as EasyBean generation, commission rebates, and hierarchical statistics.

[0029] Scenario 2: Querying for existing valid binding records (duplicate binding) If the request is deemed an illegal duplicate request, the interface will directly return a rejection result without performing any data writing or relationship change operations; the original sharing chain, hierarchical relationship, and rights statistics will all remain unchanged, and the "duplicate binding request" will be logged at the same time.

[0030] Full-service chain linkage to prevent duplication Once a target user completes their initial binding, their sharing link and hierarchical relationships are permanently locked. All subsequent services such as EasyBean calculation, commission rebate calculation, sharing ranking, and tier statistics will only read the link data of the first binding, completely shielding the data interference caused by subsequent repeated sharing requests; All business modules share the same binding relationship data to ensure consistent statistical standards across the entire platform.

[0031] Post-unbinding logic (supplementing the closed loop) Only after a valid unbinding operation is performed will the system delete the binding record corresponding to the target user from the database and release the unique index from its position. After the unbinding is completed, the user can receive new sharing binding requests again and go through the initial binding process again. The composite positioning SDK module is used for triple cross-verification of device hardware, network environment, and geographical location, and automatically identifies abnormal devices and clears the activity level of abnormal accounts. EasyBeans are a unique digital identity credential automatically generated by the platform based on essential consumption needs. They are used for dual identity verification and rights quantification for users. They have no monetary or financial attributes and are generated automatically without manual allocation. Activity level calculation uses a fixed formula: Unit activity level benefit value = Total legal operating profit of platform non-essential commission ÷ Total effective activity level of the platform; User mode switching supports automatic switching between three-month trial mode and automatic switching when the total amount of Easy Beans exceeds the threshold of essential consumption. Both modes are executed automatically without manual intervention. Specifically, in the trial mode, Easy Beans can be used to redeem goods from merchants within the platform. In Easy Mode, the redemption of goods or enjoyment of real-time monthly benefits from the platform is triggered only when Easy Beans exceed the total amount of essential consumption.

[0032] In this embodiment, a dual identity system is constructed for users, who possess both the identity of a traditional consumer of goods / services and the identity of a holder of YiMianDou on the platform. YiMianDou is the only digital carrier for confirming this dual identity, which is fundamentally different from traditional points, coupons, and marketing rebate rights.

[0033] In this embodiment, the onboarding and category review module includes a merchant onboarding review sub-module and a consumer product category review sub-module. Merchants submit qualification materials and complete the onboarding process after the platform's central review is approved. The factory direct sales zone is only open to legitimate manufacturers. Merchants declare essential / non-essential product / service category tags, which are automatically reviewed and approved by the platform's central review and then bound, serving as the core basis for subsequent Easy Bean generation and commission collection.

[0034] In this embodiment, the fulfillment and intelligent settlement revenue sharing module embeds differentiated automatic revenue sharing code logic. For offline instant service scenarios, the platform central hub immediately executes automatic revenue sharing after the merchant completes order verification, without requiring the consumer to confirm receipt. For online logistics delivery scenarios, the platform central hub executes automatic revenue sharing only after the consumer confirms receipt or the system automatically confirms receipt after timeout. The revenue sharing rules are automatically matched by the program.

[0035] In this embodiment, the Easy Bean generation module automatically generates Easy Beans only for essential consumption verified by the platform's central authority, thus completing dual identity verification. Non-essential consumption does not trigger the Easy Bean generation logic. The generation of Easy Beans is associated with the user's legitimate promotional behavior, and the corresponding identity verification certificate is automatically generated.

[0036] In this embodiment, the user mode switching module is mounted on the consumer end, allowing users to choose between the experience mode or the Easy Beans mode. The two modes correspond to different identity rights execution rules, which are automatically executed by the platform's central program, and the mode switching data is retained in real time.

[0037] In this embodiment, the activity statistics module automatically collects consumers' essential consumption data from the platform's central hub to calculate user activity. Non-essential consumption is not included in the statistics. For users with an activity level of 0, the system automatically freezes their sharing link rights and platform gain conversion rights to prevent them from becoming complacent.

[0038] In this embodiment, the livelihood-oriented dynamic adjustment module is embedded in the platform's central hub. It is a technical unit with adjustable backend parameters. It can dynamically adjust the weight of Easy Bean generation for essential livelihood categories such as maternal and infant products and agricultural products. For non-essential high-end consumption, it can implement a differentiated high commission rate, and the commission revenue is automatically fed back to the Easy Bean distribution process for essential consumption.

[0039] In this embodiment, the data storage and risk control module encrypts and retains all operation data, consumption data, identity verification data, Easy Beans data, settlement data, activity data, and mode switching data across the three terminals, generating an unalterable operation log; at the same time, it is equipped with a risk control monitoring unit to automatically identify and intercept abnormal orders, abnormal Easy Beans generation, and abnormal settlement behavior.

[0040] In this embodiment, the composite positioning SDK module is used for triple cross-verification of device hardware, network environment, and geographical location. The specific implementation steps are as follows: When a user device starts up and logs into the system, the module automatically and silently starts the verification process. Three types of core data were collected step by step and cross-compared: unique fingerprint information of the device hardware layer; physical address of the currently connected WiFi router and network environment parameters; and real-time geographical location information of the user's consumption scenario. The system backend has a pre-set database of abnormal devices, which automatically compares and identifies virtual machines, multi-instance tools, modified devices, and simulates and locates cheating scenarios. When an account is identified as an abnormal or fake account, the system automatically resets the account's activity level to zero, blocks fake consumption data from entering the algorithm's calculation pool, and retains only valid consumption data from real devices, real networks, and real locations.

[0041] This invention adopts a technical architecture with independent deployment and bidirectional data interaction across three terminals: the consumer terminal, the platform hub, and the merchant terminal. Each terminal is an independent set of functional modules, achieving real-time data transmission and command interaction through encrypted data interfaces. All core logic is uniformly controlled and automatically executed by the platform hub, eliminating manual intervention in business rule adjustments. All functions are implemented through program code, algorithm modules, and data processing flows. The specific architecture and functional division are as follows: 1. Consumer side: Targeting end consumers, it includes modules for request initiation, product / service browsing, order placement, payment settlement, Easy Free Beans viewing, identity mode switching, rights inquiry, and receipt confirmation. It supports voice-initiated requests, location matching of nearby merchants, online purchase of factory direct sales products, and online and offline fulfillment status viewing. Consumers are the sole holders of Easy Free Beans and can choose between experience mode or Easy Free mode. All consumption data, identity verification data, and Easy Free Beans data are synchronized to the platform central hub in real time.

[0042] 2. Platform Hub: The core control unit of the system, equipped with a full range of functional modules including data processing, essential / non-essential category review, Easy Points generation and calculation, dual identity verification, activity statistics, intelligent settlement and revenue sharing, dynamic parameter configuration, data storage, composite positioning SDK risk control monitoring, and log retention. It is the "data brain" of the entire system, responsible for receiving all data uploaded by consumers and merchants, performing algorithm calculations, issuing instructions, executing rules, and controlling settlement. It also embeds modules for adjusting the weight of consumer goods rights, differentiated commission extraction, and automatic revenue sharing logic. All rules are fixed in the form of program code, eliminating the need for manual operation and achieving fully automated operation.

[0043] 3. Merchant side: Targeting offline physical merchants and legitimate manufacturers, it adopts a unified onboarding review mechanism and does not accept individual sellers to join the factory direct sales zone. It includes functional modules such as qualification submission, product / service listing, essential / non-essential category declaration, order receipt, order confirmation, fulfillment verification, logistics information upload, fund settlement, and reconciliation inquiry. It distinguishes between two fulfillment scenarios: offline instant service and online logistics delivery. All operation data is synchronized to the platform central hub in real time and is subject to unified review and control by the platform central hub.

[0044] Onboarding and Category Review Module This module is divided into two sub-modules: merchant onboarding review and consumer product category review. Both are completed collaboratively between the platform's central control and the merchant's side, forming the foundation for the operation of all subsequent functions of the system. Merchant Onboarding Submodule: Merchants submit relevant materials such as business licenses, operating qualifications, and legal person information through the merchant portal. The material data is encrypted and uploaded to the platform central hub. The platform central hub completes the qualification review through automatic comparison and manual review. After the review is passed, the merchant obtains the onboarding permission. The Factory Direct Sales Zone is only open to formal enterprises with production qualifications. Individual businesses and individuals cannot onboard. Consumer Category Review Submodule: After merchants join the platform, they can declare their products and services as essential or non-essential through the merchant portal. The declaration information is synchronized to the platform's central hub, which automatically reviews the information according to preset standards. Once the review is approved, the category tag is bound. This tag serves as the core basis for subsequent Easy Bean generation, commission rate execution, and rights distribution.

[0045] Consumer demand matching and order placement module Consumers can use location services to find nearby offline merchants and browse products in the factory direct sales zone across regions. Users can initiate consumption requests via text or voice. After receiving the request data, the platform's central hub performs precise matching based on user location and product category tags, pushing suitable merchants, products, and services to the consumer. After the user confirms and completes the order, the order data is synchronized in real time to the platform's central hub and the merchant's end, providing data support for subsequent processes.

[0046] Performance and Intelligent Settlement and Revenue Sharing Module For offline instant service scenarios: Consumers enjoy services in stores, and after the merchants complete the services, they verify the orders. The verification data is synchronized to the platform's central hub. The platform's central hub immediately triggers the smart contract to automatically distribute the revenue based on the preset commission rate, and the payment after deducting the platform commission is directly settled to the merchant's account. For online logistics delivery scenarios: Merchants pack and ship goods and upload the tracking number. After consumers receive the goods and confirm receipt, the confirmation data is uploaded to the platform's central hub, which then triggers a smart contract for automatic revenue sharing. If consumers do not manually confirm receipt, the system will automatically confirm receipt and execute the revenue sharing process after a preset time limit is reached. All of the above revenue sharing logic is embedded in the smart contract code in the platform's central core, and the corresponding revenue sharing rules are automatically matched according to the order fulfillment method tag.

[0047] Composite Positioning SDK Module This system is equipped with a separate technology module for composite positioning SDK, used for triple cross-verification of device hardware, network environment, and geographical location. Specific implementation steps are as follows: The system front-end embeds a composite positioning SDK program module. When the user device starts up and logs into the system, the module automatically and silently starts the verification process. Three types of core data were collected step by step and cross-compared: ① Unique fingerprint information of the device hardware layer (factory code, network access license identifier, hardware serial number); ② Physical address of the currently connected WiFi router and network environment parameters; ③ Geographic location information of the user's real-time consumption scenario. The system backend has a pre-set database of abnormal devices, which automatically compares and identifies cheating scenarios such as virtual machines, multi-instance tools, modified devices, and simulated location. When an account is identified as an abnormal or fake account, the system automatically resets the account's activity level to zero, blocks fake consumption data from entering the algorithm's calculation pool, and retains only valid consumption data from real devices, real networks, and real locations. The entire verification process is executed automatically, providing a real and reliable computational basis for the EasyBean generation algorithm and activity calculation.

[0048] Easy-to-use beans generation and digital identity module E-Bean Definition: E-Bean is a digital identity credential for consumers that is automatically generated by the platform's central algorithm, uniquely bound to the user's account, encrypted, and tamper-proof. It is the sole technical carrier for confirming the user's dual identity, and has no monetary circulation, transaction redemption, or financial attributes. It is fundamentally different from traditional points, coupons, and marketing rebates. It is generated automatically by the system throughout the entire process, without any manual allocation.

[0049] Dual Identity Confirmation: Users have two identities within the system: one is the traditional consumer of goods / services, and the other is the holder of Easy Beans. The two identities are confirmed and bound together through Easy Beans. The number of Easy Beans directly corresponds to the accumulated value of the user's digital identity rights.

[0050] Generation logic: Only essential consumption triggers the generation of Easy Beans; non-essential consumption does not generate them. After a user completes compliant essential consumption and fulfills the contract, the platform's central hub automatically maps and generates Easy Beans based on order data. When a user legally promotes a new user to complete essential consumption, the system automatically generates Easy Beans for the inviter according to preset rules, with no human intervention throughout the process.

[0051] Activity Calculation Module Activity level is automatically generated based on users' real essential consumption behavior. It is the core accounting parameter of the system and the carrier of anti-cash-out technology. Non-essential consumption is not included in the activity level statistics.

[0052] Fixed calculation formula: Unit activity value = Total legal profit from platform non-essential commissions ÷ Total effective activity on the platform Each period, the system automatically collects the total legitimate operating gains of non-essential business on the platform, calculates the total effective activity across the entire network after verification by the composite positioning SDK, and performs batch calculations using a fixed formula to obtain the corresponding rights value for each activity level. Finally, it converts these into equivalent benefits to generate easy-to-use beans. Users with an activity level of 0 have their sharing link rights and platform benefit conversion rights terminated to prevent users from profiting passively.

[0053] User mode switching module The system has a built-in dual-operation mechanism of experience mode and easy-to-use mode, fully implementing the rules: Trial Mode: A three-month trial period is automatically enabled by default after user registration. Users can manually skip the trial mode and directly enter the free trial mode. Automatic switching time limit: After the three-month trial period, the system will automatically switch to the easy-to-exempt mode without intervention; Automatic threshold-triggered switching: When the total amount of Easy Beans from all sources in a user's personal account is greater than or equal to the user's total accumulated essential consumption amount, the system will immediately and automatically trigger the second round of Easy Beans to accumulate activity points; Both modes are automatically switched by the system program based on timeliness and data thresholds, without any manual intervention.

[0054] People-oriented dynamic adjustment module The platform's central control system has a preset category rights weight adjustment function. For categories such as maternal and infant products, agricultural products, and daily necessities, the system can increase the proportion of Easy Beans generated through the backend to guide consumers to increase their consumption of these essential items. For non-essential high-end consumption and luxury goods consumption, the platform's central control system automatically implements a higher commission rate. The commission revenue is included in the platform's overall operating revenue and is automatically calculated by the system to be directed back to the Easy Beans distribution process for essential consumption.

[0055] Data storage and risk control module The platform's central hub is equipped with a distributed data storage unit that encrypts and retains all operation data, consumption data, identity verification data, Easy Beans data, settlement data, activity data, and mode switching data across the three terminals, generating tamper-proof operation logs. It also features a risk control and monitoring unit that automatically identifies and intercepts abnormal orders, abnormal Easy Beans generation, and abnormal settlement behaviors.

[0056] Overall system data flow Merchant side: Merchant submits qualifications → Platform central review for onboarding → Merchant declares product / service categories → Platform central review of category tags → Merchant lists products / services → Receives consumer orders → Confirms order acceptance → Fulfills according to scenario → Order verification / logistics information upload → Platform central intelligent revenue sharing → Merchant account receives payment; Consumer side: Register and log in → Automatic verification by the composite location SDK → Initiate consumption request → Platform matches merchants / products → Place order and pay → Enjoy service / confirm receipt → Platform central hub generates Easy Beans and completes dual identity verification → Easy Beans accumulate and identity rights increase → Activity statistics → Enjoy the allocation of rights corresponding to the platform identity; The platform's central hub receives data from three terminals throughout the entire process, followed by automatic review, algorithmic calculation, instruction issuance, intelligent revenue sharing, generation of Easy Beans and identity verification, activity statistics, dynamic adjustment of category benefits, and data storage and risk control monitoring, achieving a closed-loop data flow throughout the entire process.

[0057] The system also includes a heterogeneous device fingerprint anti-counterfeiting algorithm based on multi-source feature fusion (MSF-HDFA), a dynamic weight allocation algorithm for easy-free beans based on essential consumer behavior graphs (CGA-DW), a dynamic activity weighted model based on time decay factor and behavioral entropy (TDA-HEM), an online learning algorithm for the weight of consumer rights in livelihood categories based on multi-objective optimization (MOO-PAR), an intelligent revenue sharing triggering and anomaly detection algorithm based on the time sequence chain of performance behavior (PF-TSAD), and an algorithm for predicting the timing of experience → easy-free mode switching based on consumer behavior sequence (CBS-TP); as detailed below: A heterogeneous device fingerprint anti-forgery algorithm based on multi-source feature fusion (MSF-HDFA) It replaces the traditional single device ID collection method and improves the composite positioning SDK module's ability to identify virtual machines, device modification tools, simulated positioning, and group control devices.

[0058] The data acquisition device has multidimensional heterogeneous characteristics, including the hardware layer (CPU model, sensor list, screen resolution, battery serial number, storage partition table), the system layer (kernel version, system property ro.build.fingerprint, language and time zone settings, debug mode status) and the network layer (WiFi router BSSID, IP segment, DNS server, TLS handshake characteristics).

[0059] A weighted heterogeneous feature hashing model is constructed to generate a dynamic anti-collision fingerprint vector for each device. A time-series sliding window is introduced to compare the fingerprint consistency of the same device in multiple logins, identify forgery behavior, automatically mark abnormal devices and add them to the blacklist, and simultaneously clear the activity of associated accounts.

[0060] The embedded composite positioning SDK module serves as the underlying feature extraction and comparison algorithm, significantly improving the accuracy of cheating detection and ensuring the authenticity of the data generated by Easy Beans.

[0061] EaseBean Dynamic Weight Allocation Algorithm Based on Essential Consumption Behavior Map (CGA-DW) Optimize the generation logic of Easy Beans to avoid simple linear mapping based on consumption amount and prevent arbitrage through fraudulent transactions or dilution of rights.

[0062] Construct a consumer behavior graph: nodes represent users, products, merchants, and categories, while edges represent consumption frequency, amount, fulfillment rate, return rate, etc. Graph Convolutional Network (GCN) is introduced to embed users and extract their essential consumption stability features.

[0063] Dynamic weighting factors are calculated based on characteristics, affecting the number of Easy Beans generated: users with high-frequency essential needs, low return rates, and high fulfillment rates receive high weighting; users with abnormally concentrated consumption and frequent account switching receive low weighting.

[0064] Design an anti-dilution mechanism: When the growth rate of the total amount of free beans generated across the entire network exceeds the growth rate of the total amount of essential consumption, the weighting factor (anti-dilution coefficient) will be automatically compressed.

[0065] The embedded EasyBean generation module replaces the fixed-ratio generation logic, improving the system's robustness to abnormal behavior and enhancing the fairness and sustainability of rights distribution.

[0066] Dynamic Activity Weighted Model Based on Time Decay Factor and Behavioral Entropy (TDA-HEM) The original simple linear model of activity level = essential consumption amount is supplemented by introducing the time dimension and behavioral diversity to prevent users from becoming inactive after making a large one-time purchase.

[0067] Define a time decay function: user activity decays exponentially with the number of days without consumption (e.g., multiplied by 0.95 per day).

[0068] Introducing behavioral entropy: Statistics on the quantity, frequency, and time period distribution of users' essential consumption categories. The higher the entropy value (the more diverse the behavior), the higher the activity weight.

[0069] Final effective activity calculation formula: Effective activity level = Σ (essential consumption amount × category weight × time decay coefficient × entropy factor). When the effective activity level is 0, the system automatically freezes the sharing link benefits and platform gain conversion benefits.

[0070] An embedded activity calculation module replaces the original static formula, enhancing the depth of user behavior modeling and building a true anti-lying mechanism.

[0071] An online learning algorithm for weighting consumer rights in essential goods categories based on multi-objective optimization (MOO-PAR) This method replaces manual parameter adjustment in the background, enabling dynamic and optimal adjustment of the weighting of easily generated beans for essential product categories such as maternal and infant products and agricultural products.

[0072] A multi-objective optimization function is constructed, with objectives including: maximizing the total consumption of consumer goods, minimizing the fluctuation of platform equity distribution, and maintaining stable commission income for non-essential goods. Online gradient descent (OGD) or Bayesian optimization is introduced to adjust the weights of each category based on real-time consumption data. The weight coefficients are updated every T+1 day and automatically sent to the EasyBean generation module.

[0073] By embedding a dynamic adjustment module oriented towards people's livelihood, the system achieves automated and data-driven policy response capabilities, significantly enhancing its social value and technological depth.

[0074] A Smart Revenue Sharing Triggering and Anomaly Detection Algorithm Based on Performance Behavior Sequence Chain (PF-TSAD) Enhance the security and robustness of the performance and intelligent settlement and revenue sharing modules to prevent arbitrage activities such as malicious order placement and false performance.

[0075] Construct a time-series chain of fulfillment behavior: order placement → payment → order acceptance → verification / delivery → confirmation of receipt. Use a Hidden Markov Model (HMM) to model the probability distribution of the normal fulfillment path.

[0076] Identify abnormal paths: abnormally short reconciliation time (second-level reconciliation), abnormally short receipt time (confirmation before shipment), high frequency of order reconciliation on the same device / network, etc. Abnormal orders will automatically trigger account splitting delays, manual review, or account freezing.

[0077] It embeds a contract performance and intelligent settlement and revenue sharing module, providing underlying security monitoring capabilities to ensure the compliance of fund transfers.

[0078] Experience-Based Easy-to-Escape Mode Switching Timing Prediction Algorithm Based on Consumer Behavior Sequence (CBS-TP) It replaces fixed-time or threshold-based triggering methods to enable personalized prediction and guidance of user mode switching, thereby improving conversion rates.

[0079] Extract the user's early consumption behavior sequence (frequency, category, amount, fulfillment rate), and use a Long Short-Term Memory (LSTM) network to predict whether the user will reach the threshold of total Easy Beans ≥ Total Essential Consumption within the next 7 days. If the prediction is that it is difficult to reach, the system can actively push guidance tasks (such as completing 3 essential consumption transactions). The timing of the switch is determined by the actual data and the prediction model.

[0080] An embedded user mode switching module enhances its intelligence, improves user experience, and increases system activity.

[0081] In this embodiment, the criteria for determining essential / non-essential product categories are as follows: The criteria for determining essential consumer goods categories are as follows: focusing on residents' basic daily needs, including food and fresh produce, agricultural products, maternal and infant products, daily necessities, basic medical care, housekeeping services, home repair, basic clothing, and utility bill payments, etc., which guarantee basic living needs and are free from high premiums, luxury goods attributes, and entertainment attributes.

[0082] The publicly disclosed criteria for determining non-essential consumer goods include: high-end luxury goods, accessible luxury jewelry, high-end cosmetics, entertainment and leisure, cultural tourism and vacations, high-end digital products, customized services, high-end catering, and investment and wealth management-related consumption, which are not essential for basic livelihoods.

[0083] Special category adjudication rules: Cross-border categories are determined by a combination of manual review and algorithm from the platform's central management. The determination result is permanently stored as a category label and cannot be modified by the merchant. Once a category label is bound, it can only be reviewed and adjusted annually, and each adjustment is valid for 12 months.

[0084] Definition of effective essential consumption: Excluded invalid consumption includes: refunded orders, partially refunded orders, fraudulently fulfilled orders, overdue unpaid orders, abnormal orders blocked by the system, abnormal orders paid on behalf of relatives and friends, and high-frequency orders from the same device in batches. These are not included in the essential consumption statistics, do not generate Easy Points, and do not accumulate activity points.

[0085] Valid consumption fulfillment standards: offline services are completed and verified without any after-sales disputes; online logistics orders are received normally without any fraudulent logistics and there is no full refund within the 7-day after-sales window. Only then can it be determined as a valid essential consumption and the final rights and interests are calculated.

[0086] Consumption amount statistics: Only the actual amount paid by users is counted. Coupons, platform subsidies, and merchant subsidies are not included in the total amount of essential consumption and are not involved in the generation of Easy Points or the calculation of activity.

[0087] Supplementary constraints to the core attributes of Easy Beans: Completely prohibited attributes: It does not support any financial operations such as transfer, transaction, monetization, cashing out, recharge, cash exchange, pledging, lending, etc. It has no secondary market circulation attributes and is only a digital identity confirmation certificate within the platform.

[0088] Ownership constraints: Easy Beans are permanently bound to the user's real-name account and do not support cross-account transfer, merging, or gifting. All Easy Beans will be automatically cleared and archived after the account is cancelled and cannot be recovered.

[0089] Clearing and Freezing Rules: For abnormal accounts, inactive accounts, and accounts that violate order-brushing rules, the platform may automatically freeze / clear your Easy Points. No rights will be generated during the freezing period, and the points cannot be recovered after clearing.

[0090] Activity threshold: Criteria for determining inactivity status (user_active_flag=0): If there is no valid essential consumption behavior for 30 consecutive days, and there is no valid platform interaction or order fulfillment behavior, the system will automatically determine that the user is inactive.

[0091] Active status recovery threshold: When a user completes one or more valid essential consumption transactions or generates compliant and valid interactive behaviors on the platform, the system will verify in real time and immediately restore the user to normal active status (user_active_flag=1).

[0092] Thresholds cannot be customized: Activity time thresholds and behavior thresholds are fixed by the system code. The backend can only view them and has no manual modification authority, ensuring that the rules are fair and consistent.

[0093] Activity interception supplementary fallback logic: Timeliness of hierarchical status linkage: When the activity status of the superior account changes to 0, all unsettled and ungenerated Easy Beans of the subordinate will be immediately intercepted; historical Easy Beans that have been credited and generated will not be cleared back, only newly added benefits will be intercepted.

[0094] Non-essential order rebate suspension as a fallback: During periods of 0 activity, non-essential orders will only have their rebate benefits suspended. This will not affect the merchant's normal commission collection, order fulfillment, or settlement. Only the user's rebate benefits will be closed, distinguishing between merchant-side and user-side permissions.

[0095] State synchronization timeliness: After a user's activity status changes, the entire network is synchronized in real time with a delay of no more than 1 second, eliminating the problem of state caching lag.

[0096] Activity-based equity value calculation cycle (the original formula did not include a time dimension). The unit activity value adopts a T+1 calculation mechanism: on the 1st of each month, the total non-essential commission gains of the entire platform and the total effective activity of the entire network in the previous month are automatically collected, and the unit value is calculated in batches. It takes effect in the current month and is recalculated and updated in the following month. Monthly data is settled independently and does not accumulate across the year.

[0097] Binding Effectiveness Determination Time Limit 1. Conditions for initial binding to take effect: The binding relationship is officially solidified after the shared user completes account real-name authentication and makes its first valid essential purchase. Temporary binding relationships that have not completed real-name authentication and purchase are not effective and can be overwritten by new valid bindings.

[0098] 2. Temporary binding window: If a new user fails to complete real-name consumption within 7 days of registration, the temporary binding will automatically expire and the binding quota will be released; if the user completes the compliance process within 7 days, the binding will be permanently locked.

[0099] Complete rules for legal unbinding Allowed scenarios for unbinding: Only three legitimate scenarios are supported: account cancellation, correction of real-name information of account, and malicious binding cheating determined by the platform. Users cannot initiate unbinding applications on their own.

[0100] Unbinding execution logic: After unbinding, the unique index record in the database is deleted, the data of the upstream and downstream links is cleared, and historical sharing income and historical free points are not retroactively reclaimed; after unbinding, users can accept new sharing and binding.

[0101] Unbinding limit: Each account can only legally unbind 2 times in its lifetime. If the limit is exceeded, the initial binding relationship will be permanently locked, and unbinding will be prohibited again.

[0102] Repeated binding interception fallback scenario Account cancellation and re-registration: Accounts cancelled and re-registered using the same mobile phone number / real-name information are considered new accounts and can participate in sharing and binding again, but historical binding relationships are not inherited.

[0103] Accidental Binding Appeal Mechanism: A single manual appeal channel is established on the platform, which is only for erroneous bindings caused by system failures. After manual verification, the binding can be forcibly unbound and will not be counted in the number of unbinding attempts.

[0104] Verification trigger timing In addition to silent verification upon login, real-time verification has been added for four core scenarios: order payment, fulfillment verification, large-amount essential consumption, and sharing and binding. High-risk operation scenarios will be subject to mandatory secondary device, network, and location cross-verification.

[0105] Complete gradient rules for handling abnormal equipment 1. Minor anomalies (temporary network fluctuations, location drift): This order will not be included in the accounting, the activity level will not be cleared, and a minor anomaly log will be recorded.

[0106] 2. Moderate anomaly (frequent device switching, multiple IP logins): Sharing privileges will be frozen for 7 days, and Easy Points generation will be suspended. It will be automatically restored after continuous verification.

[0107] 3. Severe anomalies (virtual machines, modified machines, simulated location, group control): Immediately clear all account activity, permanently block fake data, mark the account as a risky account, and continuously monitor it.

[0108] Positioning error tolerance threshold In offline consumption scenarios, a location error of ≤100 meters is considered a valid and accurate location; an error >100 meters is considered an abnormal location, and the order will be temporarily suspended and entered into the manual review pool.

[0109] Three-month trial mode precise timeliness rules The trial mode timer starts at 00:00 on the day the account is registered and verified. It automatically switches after 90 days, without distinguishing between registration time periods, without extension, and without pause. Once a user manually skips the trial mode, they can never resume the trial mode again.

[0110] Details of the differentiated rights and benefits under the dual-mode model: In both the trial mode and the free mode, the rules for generating free points are the same. The difference lies in that in the trial mode, free points can be redeemed for goods in a short period of time, aiming to give consumers a sense of experience. In the free mode, points are accumulated over a long period, using the principle of time for space, thus giving the platform sufficient time and space to reward consumers and achieve full free service.

[0111] 1. Experience Mode: Easy Beans can be used to redeem goods from merchants within the platform.

[0112] 2. Easy-Free Mode: This mode is triggered only when Easy-Free Beans are greater than or equal to the total amount of essential consumption. Users can redeem goods or enjoy the platform's real-time monthly bonuses.

[0113] Threshold switching repeatedly triggers interception rules Once a user's total Easy Beans amount reaches the threshold of total essential consumption and the automatic switch is completed, the threshold switching logic will never be triggered again for life; only the time-limited switching rule will remain in effect.

[0114] The system automatically confirms the fixed time limit for receiving goods. In online logistics scenarios, if the user does not manually confirm receipt, the system will automatically confirm receipt 15 days after shipment, triggering the final settlement of accounts. This time limit is fixed and cannot be modified.

[0115] After-sales revenue sharing rollback rules If a full refund is issued after settlement: the platform will automatically recover the platform commission earnings, cancel all Easy Points, activity points, and rebate benefits for the order, and the data will be retrospectively corrected.

[0116] If a partial refund occurs after settlement: the corresponding number of Easy Beans and activity points will be deducted proportionally according to the refund ratio, and the remaining valid portion will be retained normally.

[0117] Revenue Sharing Ratio Rules The revenue sharing ratio for essential and non-essential businesses is differentiated and fixed: the platform takes the lowest commission rate for essential consumer goods, while the commission rate for non-essential high-end consumption is increased by 30%-80%. The fluctuation range is automatically adapted by a dynamic adjustment algorithm guided by people's livelihood, without any manual fixed configuration.

[0118] Example 2: Offline local essential consumption scenario (hairdressing service) On the merchant side: Offline barbershops submit their business qualifications, complete the onboarding process through the platform's central review, declare their hairdressing services as essential products, and once the platform's central review is approved and the essential product tag is attached, the barbershops can then list their service information. Consumer side: Users register and log in. The composite positioning SDK automatically completes triple verification of device, network, and location. Users can choose the easy-free mode, find nearby barbershops through the consumer's location, initiate a hair service request, complete the order and pay the fee. Fulfillment and Settlement: The merchant confirms the order, the user goes to the store to enjoy the hairdressing service, the merchant verifies the order after the service is completed, and the verification data is synchronized to the platform's central hub; System execution: The platform's central hub executes the corresponding commission rate based on the essential product category tag, immediately triggering the smart contract for automatic revenue sharing; at the same time, it automatically generates corresponding Easy Points based on the consumption amount and credits them to the user's account, completing dual identity verification and rights accumulation, and simultaneously calculating the user's daily activity level; Ecosystem regulation: The platform's central control can adjust the weight of hair-related products in the background to increase the amount of free points generated, thereby enhancing users' willingness to consume.

[0119] Example 3: Non-essential high-end consumption scenarios (luxury goods) Merchant side: Legitimate luxury goods merchants complete the onboarding process, declare luxury goods as non-essential items, and the platform central review approves and binds the non-essential item label; Consumer side: Users place orders for luxury goods and complete the payment and fulfillment process; System execution: The platform's central system executes a high commission rate. This transaction does not trigger the generation of Easy Beans. The commission revenue is included in the platform's operating revenue and, after automatic calculation by the system, is directed to the distribution of Easy Beans for essential consumption.

[0120] Example 4: Essential Consumption Scenarios for Mothers and Infants (Mother and Infant Products) On the merchant side: Maternal and infant product manufacturers / stores complete the onboarding process, declare maternal and infant products as essential product categories, and the platform central review approves and binds the essential product tag; System pre-adjustment: In response to the birth incentive policy, the platform central control increases the weight of Easy Bean generation for the maternal and infant category in the background; On the consumer side: After a user purchases maternity and baby products and completes the purchase process, the platform central system generates Easy Beans, which are higher than those for ordinary essential products, and completes the identity verification and credits them to the user's account.

[0121] The above description is only a preferred embodiment of this practice, but the scope of protection of this embodiment is not limited thereto. Any equivalent substitutions or changes made by those skilled in the art within the scope of the technology disclosed in this embodiment, based on the technical solution and inventive concept of this embodiment, should be covered within the scope of protection of this embodiment.

Claims

1. A management system for generating and managing "Easy-Free Beans" based on essential consumer needs, characterized in that... It includes a two-way data interaction technology architecture that coordinates the consumer end, the platform hub, and the merchant end. The three ends achieve real-time data transmission through encrypted data interfaces, and all core functions are automatically executed by the platform hub program code. The platform hub includes modules for onboarding and category review, consumer demand matching and order placement, fulfillment and intelligent settlement and revenue sharing, composite positioning SDK, easy-to-use bean generation, user mode switching, activity statistics, dynamic adjustment based on people's livelihood, data storage and risk control, linked management of account activity, and unique sharing and binding to prevent duplicates. The composite positioning SDK module is used for triple cross-verification of device hardware, network environment and geographical location, and automatically identifies abnormal devices and clears the activity of abnormal accounts. The EasyBeans are a unique digital identity credential automatically generated by the platform based on essential consumption needs. They are used for dual identity verification and rights quantification for users. They have no monetary or financial attributes and are generated automatically without manual allocation. Activity level calculation uses a fixed formula: Unit activity level benefit value = Total legal operating profit of platform non-essential commission ÷ Total effective activity level of the platform; User mode switching supports automatic switching between three-month trial mode and automatic switching when the total amount of Easy Beans exceeds the threshold of essential consumption. Both modes are executed automatically without manual intervention. Specifically, in the trial mode, Easy Beans can be used to redeem goods from merchants within the platform. In Easy Mode, the redemption of goods or enjoyment of real-time monthly benefits from the platform is triggered only when Easy Beans exceed the total amount of essential consumption.

2. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 1, characterized in that, A dual identity system is built for users, who possess both the identity of a traditional consumer of goods / services and the identity of a holder of YiMianDou on the platform. YiMianDou is the only digital carrier for confirming this dual identity, which is fundamentally different from traditional points, coupons, and marketing rebate benefits.

3. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 2, characterized in that, The onboarding and category review module includes a merchant onboarding review sub-module and a consumer goods category review sub-module. Merchants submit qualification materials and complete the onboarding process after the platform's central review is approved. The factory direct sales zone is only open to legitimate manufacturers. Merchants declare essential / non-essential category tags for their goods / services, which are automatically reviewed and approved by the platform's central review and then bound to the category. These tags serve as the core basis for subsequent Easy Bean generation and commission collection.

4. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 3, characterized in that, The fulfillment and intelligent settlement revenue sharing module has embedded differentiated automatic revenue sharing code logic. For offline instant service scenarios, the platform central hub immediately executes automatic revenue sharing after the merchant completes order verification, without the need for the consumer to confirm receipt. For online logistics delivery scenarios, the platform central hub executes automatic revenue sharing only after the consumer confirms receipt or the system automatically confirms receipt after timeout. The revenue sharing rules are automatically matched by the program.

5. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 4, characterized in that, The Easy Bean generation module automatically generates Easy Beans only for essential consumption verified by the platform's central authority, completing dual identity verification. Non-essential consumption does not trigger the Easy Bean generation logic. Easy Bean generation is associated with the user's legitimate promotional activities, automatically generating corresponding identity verification credentials.

6. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 5, characterized in that, The user mode switching module is installed on the consumer end, allowing users to choose between an experience mode or an easy-to-use mode. The two modes correspond to different rules for executing identity rights and interests, which are automatically executed by the platform's central program, and the mode switching data is retained in real time.

7. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 6, characterized in that, The activity statistics module automatically collects consumers' essential consumption data from the platform's central hub to calculate user activity. Non-essential consumption is not included in the statistics. For users with an activity level of 0, the system automatically freezes their sharing link rights and platform gain conversion rights to prevent them from becoming complacent.

8. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 7, characterized in that, The dynamic adjustment module for people's livelihood orientation is embedded in the platform's central hub. It is a technical unit with adjustable backend parameters. It can dynamically adjust the weight of Easy Bean generation for essential consumer goods and implement differentiated high commission rates for non-essential high-end consumption. The commission revenue is automatically fed back to the Easy Bean distribution process for essential consumer goods.

9. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 8, characterized in that, The data storage and risk control module encrypts and retains all operation data, consumption data, identity verification data, Easy Beans data, settlement data, activity data, and mode switching data across the three terminals, generating an unalterable operation log. It is also equipped with a risk control monitoring unit to automatically identify and intercept abnormal orders, abnormal Easy Beans generation, and abnormal settlement behavior.

10. The Easy-to-Ease Bean Generation and Management System based on Essential Consumption as described in claim 9, characterized in that, The composite positioning SDK module is used for triple cross-verification of device hardware, network environment, and geographical location. Specific implementation steps are as follows: When a user device starts up and logs into the system, the module automatically and silently starts the verification process. Three types of core data were collected step by step and cross-compared: unique fingerprint information of the device hardware layer; physical address of the currently connected WiFi router and network environment parameters; and real-time geographical location information of the user's consumption scenario. The system backend has a pre-set database of abnormal devices, which automatically compares and identifies virtual machines, multi-instance tools, modified devices, and simulates and locates cheating scenarios. When an account is identified as an abnormal or fake account, the system automatically resets the account's activity level to zero, blocks fake consumption data from entering the algorithm's calculation pool, and retains only valid consumption data from real devices, real networks, and real locations.

Images