A method and system for information distribution based on geographic fence and unified reputation evaluation
Patent Information
- Application Number
- CN202610828092.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-09
- Publication Date
- 2026-08-04
AI Technical Summary
[0008]本发明的目的在于提供一种基于地理围栏和统一信誉评估的信息分发方法及系统,以解决现有技术中数字平台在用户角色管理、分发控制、质量预检以及流量机制等方面存在的缺陷
[0039] (1) Break through information barriers and enable users to acquire traffic independently: Users can customize geofences for each business event information. Information is only pushed to users within the fence who meet the conditions, avoiding broadcasting to irrelevant areas, reducing the consumption of network and server resources by invalid information transmission, and getting rid of the dependence on social relationship chains and platform algorithm recommendations, enabling small and medium-sized enterprises and individual users to acquire accurate traffic independently and reduce customer acquisition costs.
Smart Images

Figure CN122513466A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of big data processing technology, and in particular to an information distribution method and system based on geofencing and unified reputation assessment. Background Technology
[0002] Existing digital platforms generally employ closed, pre-defined role mechanisms, preventing users from independently selecting or instantly switching between multiple identities such as demanders, service providers, or individuals based on their participation intentions in different business scenarios. This rigid identity structure results in a lack of dynamic identity context based on user-declared identities during information matching and resource scheduling, directly reducing the computational accuracy and response efficiency of service matching.
[0003] In the distribution phase, existing technologies suffer from two core pain points: First, users cannot independently set geofences for each message. The information dissemination area is vaguely controlled by the platform, preventing users from accurately targeting specific business events to designated geographical areas. This results in a large amount of content being delivered to irrelevant regions, leading to ineffective consumption of network, storage, and computing resources. While some existing technologies involve geofencing, the geofences are pre-set by the server and used only for terminal location monitoring (such as triggering alerts when a device enters / leaves an area), without granting users the ability to customize them as information distribution filtering criteria. Second, there is a disconnect between reputation scores and information distribution permissions. Existing systems do not use user reputation scores as a screening threshold for information recipients. High-reputation users cannot receive higher-quality information, while low-reputation users are not effectively filtered, weakening the accuracy and credibility of distribution. Simultaneously, information flow heavily relies on social relationship chains and centralized recommendation algorithms, creating a double barrier that prevents a large amount of business information from reaching potential audiences within a reasonable timeframe.
[0004] Regarding information quality assurance, existing mechanisms largely rely on post-publication error correction, lacking automatic verification and interception methods for the authenticity and rationality of information's business logic at the distribution front end. False, malicious, or logically contradictory information entering the distribution channel not only consumes additional resources for review, storage, and error correction, but also damages the credibility of the information ecosystem and weakens the matching efficiency of genuine, high-quality content.
[0005] In terms of traffic acquisition, existing platforms highly concentrate exposure allocation on bidding rankings and centralized traffic funnels. Small and medium-sized information publishers lack independent traffic-generating methods, and long-tail content struggles to achieve reasonable distribution, thus limiting the overall traffic utilization and distribution diversity of the system. Simultaneously, the over-reliance on instant feedback and variable rewards in interaction design distorts the natural distribution of user behavior data, reduces the model's ability to identify new behavioral patterns, and further exacerbates the uneven distribution of traffic.
[0006] Furthermore, the highly fragmented content presentation and frequent interruptions in the interactive context increase the switching overhead of human-computer interaction, making it difficult for the system to support continuous focused interaction and long-term task planning. In terms of resource allocation, the incentive weight for virtual item generation and trading is excessively skewed, with a large amount of computing and storage resources occupied by low-quality, homogeneous virtual content, while the information processing capacity related to physical services is relatively insufficient. This results in a structural imbalance of digital resources, weakening the platform's overall effectiveness in virtual-real collaborative scenarios.
[0007] In summary, existing technologies suffer from systemic flaws in user role management, distribution control, quality pre-inspection, and traffic mechanisms, hindering the efficient flow of information and business opportunities. Therefore, there is an urgent need for a technical solution that can overcome the dual barriers of social relationships and algorithmic recommendations, empower users with the ability to autonomously choose and switch between multi-dimensional identities, and support users in anchoring business events to specific geofences and pre-distributing them for authenticity and business logic prediction. Summary of the Invention
[0008] The purpose of this invention is to provide an information distribution method and system based on geofencing and unified reputation assessment, so as to solve the defects of existing digital platforms in terms of user role management, distribution control, quality pre-inspection and traffic mechanism.
[0009] To achieve the above objectives, this application adopts the following technical solution:
[0010] This application discloses an information distribution method based on geofencing and uniform reputation assessment, comprising the following steps:
[0011] Receive business event information published by the first user, as well as the geofence and recipient reputation threshold set by the first user for the business event information;
[0012] Identify at least one second user currently located within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and push the business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior;
[0013] In response to the second user's acceptance of the business event information, an interaction relationship is established between the first user and the second user;
[0014] In response to the mutual evaluation results between the first user and the second user after the interaction ends, the reputation scores of the first user and / or the second user are adjusted.
[0015] Preferably, before receiving the business event information published by the first user, a publishing permission verification step is also included:
[0016] Obtain the first user's current reputation score and the authentication status corresponding to their current role;
[0017] If the current reputation score does not reach the preset publication threshold, or the authentication status is not passed, then the publication of the business event information will be refused.
[0018] Preferably, the first user publishes demand-type events and / or service-type events using the same account, and the reputation score is shared among different event types under the same account.
[0019] Preferably, before determining the second user, the following steps are also included:
[0020] The business event information is subject to a feasibility review, which includes at least one of the following: content compliance review, business logic authenticity review, and user behavior review.
[0021] If the review is approved, the business event information will be set to the distribution status, and the reputation score of the first user will be increased.
[0022] If the review fails, the posting will be blocked and the first user's reputation score will be deducted.
[0023] Preferably, the geofence is determined by at least one of the following methods:
[0024] a. Receive the target location name input by the first user and match it to obtain the preset geofence boundary corresponding to the target location name;
[0025] b. Receive the selection operation of the first user on the geographic interface and generate a circular fence.
[0026] Preferably, after determining the geofence, the method further includes prompting the first user that the business event information will be pushed to a second user located within the geofence, and waiting for the first user's confirmation.
[0027] Preferably, the reputation score is determined based on both the platform's objective evaluation of user behavior and the subjective evaluation after user interactions.
[0028] Preferably, the method for determining the second user currently located within the geofence includes:
[0029] The geofence is converted into several spatial units using spatial indexing. Candidate second users are obtained from the set of online users corresponding to each spatial unit, and the location of the candidate second user is determined to be within the geofence using a point containment algorithm.
[0030] Preferably, when pushing the business event information to the second user, the information is pushed in order of priority. The priority is determined by weighting the second user's current reputation score, the degree of matching with the business event information, and the distance between the second user and the geofence center point.
[0031] Preferably, the matching degree is calculated based on the similarity between the second user's historical behavior data and the business event information.
[0032] Preferably, the method further includes removing the business event information from the distribution list after the interaction ends and both parties have given each other feedback.
[0033] An information distribution system based on geofencing and unified reputation assessment includes:
[0034] The information receiving module is used to receive business event information published by the first user, as well as the geofence and the recipient reputation threshold value set by the first user for the business event information.
[0035] The filtering and push module is used to identify at least one second user who is currently located within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and to push the business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior;
[0036] The relationship establishment module is used to establish an interaction relationship between the first user and the second user in response to the second user's acceptance operation of the business event information;
[0037] The rating adjustment module is used to adjust the reputation score of the first user and / or the second user in response to the mutual rating results between the first user and the second user after the interaction ends.
[0038] Compared with the prior art, this application has the following beneficial effects:
[0039] (1) Break through information barriers and enable users to acquire traffic independently: Users can customize geofences for each business event information. Information is only pushed to users within the fence who meet the conditions, avoiding broadcasting to irrelevant areas, reducing the consumption of network and server resources by invalid information transmission, and getting rid of the dependence on social relationship chains and platform algorithm recommendations, enabling small and medium-sized enterprises and individual users to acquire accurate traffic independently and reduce customer acquisition costs.
[0040] (2) Improve information distribution efficiency and accuracy: By combining geofencing and reputation threshold for dual filtering, information is ensured to reach only potential interactors who are location-related and meet the reputation threshold, reducing interference from irrelevant information. At the same time, spatial indexing and point inclusion algorithms are used to quickly filter online users within the geofence, and asynchronous distribution via message queues is combined to achieve low-latency push under high concurrency.
[0041] (3) Construct a dual-source reputation assessment system to enhance platform trust: The reputation score integrates the platform's objective evaluation and the user's subjective evaluation, which not only prevents malicious score manipulation but also incentivizes users to publish true and high-quality information. The reputation score is dynamically adjusted and used for distributed access control, recipient filtering, and push ranking, forming a virtuous cycle.
[0042] (4) Supports unified account for multiple roles, reducing the threshold for use: Users can freely switch between the roles of demander and service provider using the same account. All credit changes of business behavior are accumulated in the same account, avoiding the inconvenience of traditional platforms requiring registration of multiple accounts or re-accumulation of credit, thus improving user experience and platform stickiness.
[0043] (5) Improve the authenticity and feasibility of information: Before information is distributed, a feasibility review is enforced to intercept false, illegal or logically contradictory information, thus ensuring the quality of information on the platform from the source and reducing transaction risks.
[0044] (6) Granting recipients the right to choose and optimizing the interactive experience: After the information is pushed, the recipient can choose whether to accept it according to their own wishes. The system establishes a two-way interactive relationship rather than a forced match, fully respecting the user's right to make independent decisions and improving the satisfaction after the transaction is completed.
[0045] (7) Automatic information sinking to maintain content freshness: After the interaction is completed, the information is automatically removed from the distribution list to avoid the continuous display of expired information and ensure that users see the current valid business event information, thus improving information browsing efficiency. Attached Figure Description
[0046] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0047] Figure 1 This is a flowchart of an information distribution method based on geofencing and unified reputation assessment provided in Embodiment 1 of this application;
[0048] Figure 2 This is a flowchart of the publishing permission verification method provided in Embodiment 1 of this application;
[0049] Figure 3 This is an example diagram of the polygonal fence setup provided in Embodiment 1 of this application;
[0050] Figure 4 This is an example diagram of the circular fence setup provided in Embodiment 1 of this application;
[0051] Figure 5 This is a three-tiered flowchart illustrating the feasibility review process provided in Embodiment 1 of this application;
[0052] Figure 6 This is a schematic diagram of the structure of an information distribution system based on geofencing and unified reputation assessment provided in Embodiment 3 of this application. Detailed Implementation
[0053] To make the technical solution of this application clearer, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The terms "first," "second," etc., in the claims and specification of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate. This is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to these processes, methods, products, or apparatuses.
[0054] Example 1
[0055] like Figure 1 As shown, this embodiment provides an information distribution method based on geofencing and unified reputation assessment, including steps S110-S140.
[0056] S110. Receive business event information published by the first user, as well as the geofence and recipient reputation threshold set by the first user for the business event information.
[0057] In this embodiment, the first user logs into the system using an account verification code or password. The server can perform JWT authentication, and after successful authentication, retrieves the user's session information from Redis. This session information contains the first user's identity identifier. After successful login, the first user enters the system homepage, selects a role module according to their needs (e.g., a demand-side role or a service-side role), and fills in the business event information.
[0058] Business event information can include a detailed event description, event-related condition settings such as the recipient's reputation threshold, and related images. It's important to note that business events can be categorized into two types based on their attributes: demand-based events (such as procurement needs and recruitment needs) and service-based events (such as group tours and design services). This is merely an example and not an exhaustive list. Firstly, when posting different types of events, users do not need to switch accounts; they only need to select the corresponding role module. All actions under the same account share the same reputation score.
[0059] Furthermore, it's important to note that in this embodiment, the first user can switch roles under different business intentions using the same account. Specifically, when the first user needs to publish a demand-related event, they only need to select the "Demand-Side Role Module" on the system homepage; when they need to publish a service-related event, they select the "Service-Side Role Module"—the entire process requires no logging out, no new account registration, and no application for role change approval from the platform. Correspondingly, the first user's historical behaviors, such as publishing actions, performance records, and mutual evaluation results generated under the aforementioned role modules, are all aggregated and applied to the same reputation score. This reputation score is completely shared between demand-related and service-related events, without any isolation or discounting. This design breaks the rigid model of traditional platforms where "one account can only be bound to one fixed role" or "multiple roles need to accumulate credit separately," enabling users to participate in different types of information interactions with the lowest operational cost and the most complete credit accumulation, thereby significantly improving the coverage and matching efficiency of information distribution.
[0060] Before receiving business event information from the first user, the system needs to verify the first user's publishing permissions. Specifically, for example... Figure 2 As shown, it includes the following steps:
[0061] S210. Obtain the current reputation score of the first user and the authentication status corresponding to its current role;
[0062] The system queries a database table storing user account information (such as the `user_account` table in MySQL) based on the first user's identity to obtain the first user's current credit score. Simultaneously, it determines the authentication type to be verified based on the role module selected by the first user. For example, if the first user selects the enterprise service provider role, the enterprise authentication identifier may need to be true; if the first user selects the individual service provider role, the real-name authentication identifier may need to be true. It is understood that the authentication type may differ in different business scenarios; this is merely an example.
[0063] S220. If the current reputation score does not reach the preset release threshold, or the authentication status is not passed, then the release of business event information will be refused.
[0064] The system determines whether the first user's reputation score is greater than the preset publishing threshold (e.g., reputation score ≥ 90, the specific threshold can be set according to business needs) and whether the authentication identifier is true. When both conditions are met, it means that the first user has the right to publish information; if either condition is not met, the system returns the corresponding rejection message (e.g., "Insufficient reputation score, unable to publish" or "Please complete enterprise authentication first") and terminates the publishing process.
[0065] After successful authentication, the system receives the business event information uploaded by the first user and performs a preliminary review. This preliminary review occurs before the first user formally submits and publishes the information, primarily to intercept obviously invalid or unauthorized input. The review content may include, but is not limited to:
[0066] 1) Form field non-empty validation: such as using Hibernate Validator to validate whether necessary fields (such as event description, price, quantity / number of people, etc., the specific fields are determined according to the business type) are empty, and whether numeric fields are positive numbers, etc.
[0067] 2) Image compliance review: Upload images to Alibaba Cloud OSS and call Alibaba Cloud Content Security API to check whether they contain pornography, violence, or political content; other third-party or self-developed detection services can also be used.
[0068] 3) Image duplication detection: For example, the pHash algorithm is used to calculate the fingerprint of an image and compare it with the existing image fingerprints in the database to identify the risk of duplication or theft (if the similarity is >85%, it is marked as suspicious).
[0069] After approval, the system caches unsubmitted business event information (including the recipient's reputation threshold) as a draft in Redis, with the key `draft:service:{user_id}` or `draft:demand:{user_id}`. The expiration time can be set to 24 hours to allow the first user to resume submission from where they left off. The recipient's reputation threshold is stored as a separate field (e.g., `min_reputation`) in the draft data. If the approval fails, the system prompts the first user to modify the corresponding content.
[0070] It should be noted that the above draft cache is only used to temporarily store data that the first user has not yet submitted. After the feasibility review is passed and the first user officially submits the data, the system will write the business event information (including the recipient's reputation threshold value) into the official database. For example, in a service release scenario, the reputation threshold value will be stored in the min_reputation field of the MySQL service table; in a demand release scenario, it will be stored in the corresponding field of the demand table.
[0071] After initial approval, the first user is directed to a map page, which displays their current location by default. The first user then sets geofences for the target location based on business requirements.
[0072] In one specific implementation, a geofence is determined by at least one of the following methods:
[0073] a. Receive the target location name input by the first user and match it to obtain the preset geofence boundary corresponding to the target location name;
[0074] like Figure 3 As shown, the first user enters the name of the target location (e.g., "Z Province Future Science and Technology City HaiChuang Park") in the search box on the map page. Based on this name, the system matches the corresponding polygonal boundary (e.g., park boundary, business district boundary, market boundary, etc.) from a pre-stored geographic area boundary database. The map highlights the geofenced area. After the first user clicks "OK," a prompt box appears stating, "This information will only be pushed to the second user currently located within this geofence," awaiting the first user's confirmation. Once confirmed, the geofence setting is complete.
[0075] On the server side, the system receives fence data (of type POLYGON) submitted from the front end and uses the JTS (JavaTopology Suite) library to verify that the polygon has at least 3 vertices, does not self-intersect, and is closed. After successful verification, the vertex coordinates of the polygon are converted sequentially into a WKT (Well-Known Text) format string (e.g., POLYGON ((x1 y1, x2 y2, ..., x1 y1))). Subsequently, this string is stored in the polygon_fence table of the MySQL database, with the corresponding spatial field type POLYGON, and a GIS spatial index is created to accelerate spatial queries. It should be noted that the specific library and storage method described above are merely examples; those skilled in the art can use other spatial data processing methods.
[0076] b. Receive the first user's selection operation on the geographic interface and generate a circular fence.
[0077] like Figure 4 As shown, the first user long-presses the target location on the map page as the center, and then sets the radius (e.g., 3 kilometers) by sliding the radius bar or directly entering data. The system generates a circular fence based on the center and radius, and the circular area is highlighted on the map. After the first user clicks "OK," a prompt box appears stating, "This information will only be pushed to the second user currently located within this fence," awaiting the first user's confirmation. Once confirmed, the geofence setting is complete.
[0078] On the server side, the system receives fence data (of type CIRCLE, containing the center latitude and longitude and radius) submitted by the front end, and verifies that the radius is positive and the center coordinates are within the valid range. After successful verification, the center latitude and longitude and radius can be stored in a MySQL table (e.g., circle_fence), with fields including center precision (center_lng), center latitude (center_lat), and radius (radius). A composite index can be created on the latitude and longitude fields to accelerate retrieval as needed for queries. Alternatively, the center can be stored as a POINT type and a spatial index can be created.
[0079] It is important to note that in actual business scenarios, users can flexibly choose the fence type based on the characteristics of the service area: for services with a radial service area (such as housekeeping services and food delivery), users typically choose the convenient circular fence; for services requiring precise coverage of irregular geographical boundaries (such as industrial parks, markets, and residential areas), users choose polygonal fences to ensure that information only reaches potential users within the target area, avoiding the waste of network and server resources by pushing information to irrelevant users outside the area. This embodiment fully meets the latter's need for precise anchoring of irregular boundaries by using a pre-built polygonal boundary library (such as industrial park boundaries and business district boundaries) and supporting users to manually draw polygons.
[0080] S120. Identify at least one second user who is currently within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and push business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior;
[0081] In one specific implementation, before determining the second user, the method further includes:
[0082] Perform feasibility audits on business event information. Feasibility audits include at least one of the following: content compliance audit, business logic authenticity audit, and user behavior audit.
[0083] If the review is approved, the business event information will be set to distribution status, and the reputation score of the first user will be increased.
[0084] If the review fails, the posting will be blocked and the first user's reputation score will be deducted.
[0085] After the first user confirms the geofence and clicks "Submit Publish," the system reads the draft content (including business event information and recipient reputation threshold) and geofence data from the Redis cache, merges them into a complete publish request, and then performs a feasibility review. This feasibility review includes at least one of the following: content compliance review, business logic authenticity review, and user behavior review. The following example illustrates each layer of the review process. Figure 5As shown, it is understood that the specific review methods listed (such as sensitive word databases, price reasonableness judgments, etc.) are merely examples, and those skilled in the art can use other equivalent methods.
[0086] (a) Content compliance review
[0087] The system performs compliance checks on the text and images of business event information. For text review, the Aho-Corasick automaton algorithm can be used to match a pre-defined sensitive word library to detect the presence of prohibited words (such as "illegal group buying" or "forced shopping"). For image review, third-party content security APIs (such as Alibaba Cloud Green Network) can be called to detect whether images contain pornography, violence, or political content.
[0088] (ii) Verification of the authenticity of business logic
[0089] The system assesses the commercial reasonableness of business event information, including but not limited to:
[0090] a. Price / Budget Reasonableness: For example, for service-related events (such as group tours), you can query the average transaction price of similar services recently from ClickHouse or similar analytics databases to determine whether the first user's quote is within a reasonable fluctuation range (such as ±20%); for demand-related events (such as procurement needs), you can query the recent market price of similar products to determine whether the budget is reasonable.
[0091] b. Logical consistency: For example, verify whether the itinerary description is consistent with the included items (e.g., whether a 7-day itinerary includes airfare, accommodation, meals, etc.), or whether the quantity and specifications in the procurement requirements match.
[0092] c. Reasonableness of Reputation Threshold: The system determines whether the reputation threshold set by the first user for the recipient does not exceed their own reputation score. For example, if the first user's own reputation score is 126, but they require the recipient's reputation score to be greater than 130, it is deemed unreasonable and the review will not be approved. This prevents the first user from posting requirements that exceed their own credit rating.
[0093] If any of the above judgments fails, the verification of the authenticity of the business logic will fail.
[0094] (III) User Behavior Review
[0095] The system evaluates the first user's historical behavior. For example, it can query the first user's fraudulent posting records, number of complaints, order cancellation rate, etc., within the past 30 days, and use sliding window counting (such as Redis's ZSET) to count the frequency of bad behavior. If the first user has a high reputation score and a good history, the application is approved; if there are multiple violations, the application is rejected.
[0096] If any of the three layers of review determines that the application is not approved, the system will block the publication, deduct the first user's reputation score (e.g., 5 points for each failure), and return the specific reason for the failure to the first user (e.g., "price exceeds reasonable range", "illegal image detected", "set reputation threshold is higher than the user's own reputation"), while also recording the reputation change log.
[0097] If all reviews pass, the system will positively adjust the first user's reputation score (e.g., increase the content credibility score by 1) and write the business event information to the official database. During the write process, the system uses the Snowflake algorithm to generate a globally unique business event information identifier (e.g., service_id or demand_id), inserts it into the MySQL table, and sets the status to "Distributing" (e.g., status=1). Simultaneously, the recipient reputation threshold set by the first user is stored in the corresponding field of the business table (e.g., min_reputation). At this point, the business event information has been successfully published and enters the pending distribution state.
[0098] After the business event information is successfully written to the formal database and set to the "distributing" status, the system automatically triggers the information distribution process, which identifies at least one second user who is currently within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and pushes the business event information to that user.
[0099] Specifically, the system sends distribution messages to a message queue (such as Kafka). The message content includes at least the business event information identifier (such as service_id or demand_id), geofence data (type and coordinates), and the recipient's reputation threshold. To ensure reliability, at-least-once consumption semantics can be used to ensure that distribution tasks are not lost.
[0100] After the distribution scheduler (Kafka Consumer) pulls the message, it executes the corresponding second user query based on the geofence type (polygon or circle) to obtain the candidate second user set.
[0101] For polygonal fences, a two-stage strategy of "coarse screening + fine screening" is employed. Coarse screening uses an H3 hexagonal hierarchical index (resolution res=9) to easily convert the polygons into a set of H3 cells covering the area. For each cell, all online user IDs currently located within that cell are retrieved from the h3_cell:{cell_id} set stored in Redis, merged, and deduplicated to obtain a set of candidate second-tier users. Fine screening involves obtaining the current geographical location (latitude and longitude) of each user within that cell (considered a candidate second-tier user), and using the Ray Casting Algorithm to precisely determine whether the point is located inside the polygon. Users who pass the fine screening are confirmed as candidate second-tier users.
[0102] It is understood that H3 indexing and ray casting are merely examples, and those skilled in the art can use other spatial indexes such as Geohash and S2, as well as point containment algorithms such as ray casting.
[0103] For circular fences, Redis's GEORADIUS command can be used directly to quickly return the online user identifiers within the area based on the center latitude and longitude and the radius. Alternatively, an H3 index can be used to convert the circular area into a set of H3 cells before querying. Since the circular boundary calculation is inherently accurate, further fine-tuning is unnecessary.
[0104] Exclude the publisher (i.e., the first user) from the candidate second users. Then, retrieve the current reputation score of each candidate second user in batches from Redis based on the user identifier (the reputation score is dynamically adjusted based on the user's historical behavior, including the platform's objective evaluation and the results of mutual evaluation after interaction), and remove candidate second users whose reputation score is lower than the recipient's reputation threshold.
[0105] For the remaining second-ranked users, calculate their matching score relative to the business event information. This score is used for subsequent push ranking. The matching score can consider the following factors (weights can be adjusted according to business needs):
[0106] a. Reputation Score (R) responuder ): This refers to the current reputation score of the candidate second user. The higher the score, the higher the priority, reflecting the user's credibility.
[0107] b. Distance decay factor (d): The distance between the candidate second user and the geofence center point (for polygons, the geometric center or the publisher-specified point can be used). The closer the distance, the higher the score, for example, using exponential decay e^(-λ·d), where d is the distance (in kilometers) and λ is the decay coefficient.
[0108] c. Interest Match tarvel This is based on the similarity between the candidate second user's historical behavior (such as browsing, clicking, ordering, and saving records) and the category and keywords of the current business event information. For example, a collaborative filtering algorithm can be used to calculate the user's preference for the current event type. For instance, the categories of the second user's historical clicks, orders, and saves can be constructed as a preference vector, and the category of the current business event information can be constructed as a feature vector. The cosine similarity between the two is then calculated. The similarity value ranges from 0 to 1, with a higher value indicating greater user interest in that type of business.
[0109] Example scoring formula: Score = α·R responuder +β·e^(-λ·d)+δ·Match tarvelα, β, and δ are weighting coefficients, and α is usually taken as a large value (such as 0.6) to highlight the core role of reputation.
[0110] Based on the matching scores, the top K candidate second users are selected as the target second users (e.g., K=100).
[0111] For each target second user, the system performs a push notification operation:
[0112] a. Online push: If the target second user is currently maintaining a WebSocket (a full-duplex communication protocol) long connection with the server (e.g., a WebSocket gateway implemented through the Netty framework), the system directly sends a JSON (a lightweight data exchange format) message through this connection. The message content may include: {type:"new_service", service_id, title, price, min_reputation, poster_reputation}, etc.
[0113] b. Offline processing: If the target second user is offline, the system will store the push message in a MySQL offline message table (such as offline_notification), and the client will call the interface to retrieve it when the user logs in next time.
[0114] c. Third-party supplementary push notifications: As an enhancement, third-party push services can be invoked simultaneously, such as JPush (a third-party push platform) or Apple Push Notification Service (APNs), to send notification messages through the manufacturer's channel, thus covering situations where the app is in the background or the process is killed. To save resources, asynchronous batch APIs can be used to aggregate the device registration IDs of the target secondary users and then call them all at once.
[0115] To avoid excessive push notifications interfering with secondary users, the system can implement anti-harassment strategies. For example, a Redis bitmap (a bit-based data structure) can be used to record the number of push notifications received by each secondary user within a recent period (e.g., 60 minutes). If a single secondary user receives more than 5 push notifications of the same type within 60 minutes, they are temporarily added to a silent queue, and a push is only forced when the matching score is higher than a preset threshold (e.g., 95 points). For high-reputation secondary users (reputation score > 100), the push frequency limit can be relaxed to 10 notifications per 60 minutes.
[0116] At the same time, the system sends a success message to the first user. For example, it sends a message via WebSocket stating, "Your business event information has been approved and is being pushed to users within the designated area," and updates the status of this information to "Distributing" in the first user's "My Published" list. Successful publication logs can also be recorded to ELK for monitoring and analysis.
[0117] After receiving the push notification, the second user can open the app to view the details by clicking the notification. In addition, when the second user opens the "Message Center" or "Browse Nearby" module of the app, the system will dynamically query all "Distributing" business event information in the area where the second user is located, and display them in descending order of comprehensive reputation score.
[0118] Specifically, the system constructs a circular query fence (with a configurable radius, e.g., 2 kilometers) centered on the second user's current geographic location. It then uses H3 indexes or Redis's GEORADIUS command to quickly retrieve valid information identifiers within this area. For each candidate message, the system checks whether the second user is within the geofence set by the information publisher, and calculates a comprehensive reputation score for messages that pass the geofence verification.
[0119] The comprehensive reputation score is used to rank information from multiple business events, and its calculation method is based on a weighted combination of the following factors:
[0120] Publisher Reputation Score: This is the current reputation score of the first user, reflecting the credibility of their historical behavior;
[0121] Timeliness score: Calculated based on the time difference between the release time of the business event information and the current event, with a value range of [0,1]. The closer the release time, the higher the timeliness score.
[0122] Distance score: Based on the distance between the second user's current location and the information anchor point (such as the center point of a geofence or the location specified by the publisher), the closer the distance, the higher the score.
[0123] The formula is Score = α·(Publisher Reputation Score) + β·(Timeliness Score) + γ·(Distance Score), where α, β, and γ are weighting coefficients, and α is usually taken as the largest value to highlight the dominant role of reputation.
[0124] Sort the business event information from highest to lowest based on the overall reputation score, and return the sorted list to the front end. The client typically loads the first 20 items first, and then retrieves more items via cursor pagination when scrolling to the bottom.
[0125] When a second user becomes interested in a business event and decides to participate, they can perform an acceptance action. This acceptance action includes, but is not limited to, initiating inquiries, confirming cooperation, placing orders, registering, and making appointments—interactive behaviors that express acceptance. The system provides a real-time chat function for the first and second users, allowing them to communicate through the system's chat interface to further confirm details and negotiate terms.
[0126] S130. In response to the second user's operation of accepting business event information, establish an interactive relationship between the first user and the second user;
[0127] After detecting the second user's acceptance operation, the system establishes a corresponding interactive relationship based on the type of business event information. If the acceptance operation is to initiate a consultation or establish a chat session, the system creates a chat room and adds both parties; if the acceptance operation is to place an order or confirm cooperation, the system generates an order or cooperation order, recording the identities of both parties, event information, agreed conditions, etc., and the order status is initially "pending confirmation" or "pending payment".
[0128] After the interactive relationship is established, the system updates the status according to the actual performance process of both parties. For example, when the second user completes the payment, the system updates the order status to "paid" and notifies the first user; when the first user confirms the service, completes the shipment, or confirms the order, the system updates the status to "confirmed" or "shipped"; when the second user confirms receipt or the service is completed, the system updates the status to "completed".
[0129] If the business event information includes a limit on the number of participants or quantities (such as the number of participants required to form a group or the maximum inventory limit), the system uses atomic counting to accumulate the number of participants. When the preset limit is reached, the system automatically changes the status of the business event information from "Distributing" to "Full" or "Ended", stops pushing it to new users, and removes the record from the distribution index.
[0130] S140. In response to the mutual evaluation results between the first user and the second user after the interaction ends, adjust the reputation scores of the first user and / or the second user.
[0131] After the interaction ends (e.g., service completion, goods receipt, termination of cooperation), the system provides a mutual rating interface for the first and second users. Users can choose from 1 to 5 stars to rate each other, adjusting the reputation score of the first and / or second user. The reputation score adjustment is based on the default score (e.g., 100 points), with the change ΔR calculated according to the mutual rating: a positive review (4-5 stars) adds 1 reputation point, a negative review (1-2 stars) deducts 1 reputation point, and a neutral review (3 stars) remains unchanged. Simultaneously, the platform makes additional objective adjustments based on the user's performance record during the interaction (e.g., whether orders were canceled without cause, whether services were completed on time, whether complaints were received, etc.). For example, good performance adds 1-2 points, while breach of contract deducts 2-5 points. The final reputation score is the original score plus the basic change and the platform's additional adjustments, and upper and lower limits can be set (e.g., minimum 0 points, maximum 200 points). Each adjustment is recorded for traceability. The adjusted reputation score will affect the user's eligibility to post and receive information, as well as the priority of push notifications.
[0132] After the interaction is complete, the system triggers an automatic information sinking process. Specifically, when the order status changes to "completed," the server sends a Kafka event. The event content includes at least a business event identifier (such as service_id or demand_id) and the event type. Upon receiving this event, the downstream Kafka consumer performs the following atomic operations:
[0133] 1. Update the status field of this business event information in the database from "Distributing" (status=1) to "Completed" (status=2) to prevent new users from obtaining this information through queries;
[0134] 2. Execute the ZREM command to delete the member of the information from the ordered set of nearby information stored in Redis (e.g., key is nearby_services:{geohash_cell}, using a Sorted Set structure, member is the business event information identifier, and score is the comprehensive reputation score).
[0135] 3. Clear the mapping of this information in the H3 spatial index: Traverse all H3 cells (resolution res=9) covered by the geofence of this information, execute the SREM command on the Redis Set (e.g., h3_cell:{cell_id}:services) corresponding to each cell, and remove the business event identifier;
[0136] 4. If the system uses a circular fence-based GEORADIUS cache, then the information should also be removed from the corresponding cache structure.
[0137] After completing the above operations, the platform will be unable to retrieve the business event information when any subsequent second user initiates a "browse request" or performs a geofence query, thus achieving automatic and thorough information sinking. Simultaneously, the system archives historical records for user retrieval. The method provided in this embodiment, by allowing users to independently set geofences and reputation thresholds for each piece of information, combined with a dual-source reputation system built through platform verifiability verification and user peer review, achieves targeted, efficient, and reliable information distribution. Users can freely switch between demand and service provider roles using the same account, and all reputation changes are stored in the same account, lowering the barrier to entry. Furthermore, the system intelligently sorts and pushes information based on reputation scores and location information, and automatically sinks information after interaction, thereby breaking through the traffic barriers of traditional social and algorithmic recommendations and improving information authenticity, interactive autonomy, and overall platform trust.
[0138] Example 2
[0139] This embodiment illustrates the typical application of Embodiment 1 through three specific scenarios, but the scope of protection of this application is not limited thereto. Scenario 1 is the complete embodiment, while Scenario 2 and Scenario 3 only describe the main differences from Scenario 1; common steps can be referred to in Scenario 1.
[0140] Scenario 1: A travel company launches group tour services.
[0141] In this scenario, the first user is a verified travel company (reputation score 126) that posts a "7-day tour of T Province" as a service provider. The company sets the group size at 21 people, the price at 9900 yuan per person, and requires the recipient to have a reputation score of at least 100. The first user enters "H Province Future Science and Technology City HaiChuang Park" into the map search box, and the system automatically matches the park's pre-defined polygonal boundaries as geofences.
[0142] The system first verifies the first user's publishing permissions: it obtains the user's current reputation score of 126 and enterprise authentication status (authenticated), both of which meet the preset publishing threshold (reputation score ≥ 90 and authentication true). Upon receiving a business event, the system performs a preliminary review: form field non-empty validation passes; the image is uploaded to Alibaba Cloud OSS and the content security API is called for testing, with no violations found; the pHash algorithm calculates the image fingerprint and compares it with the database, with a similarity of 12% < 85%, indicating no risk of duplication / theft. After the preliminary review is passed, the first user confirms the geofence settings, and the system performs a feasibility review:
[0143] Content compliance review: Using the AC automaton to match the preset sensitive word library, the text "7-day tour of T province" did not match any prohibited words; the image compliance review passed.
[0144] Verification of the authenticity of the business logic: According to ClickHouse, the average transaction price of similar "7-day tour of T province" in the past 30 days is 9,500 yuan, and the user's quoted price of 9,900 yuan is within a reasonable fluctuation range (±20%), so it passes; the description of the 7-day itinerary and the included items (airfare, accommodation, meals, and attraction tickets) are logically consistent; the recipient's reputation threshold is 100 ≤ and the publisher's own reputation score is 126, which is reasonable.
[0145] User behavior review: The user's records for the past 30 days show no false postings, 0 complaints, and a 0% order cancellation rate. Approved.
[0146] After all three levels of review are passed, the system will increase the first user's reputation score from 126 to 127 (content credibility score +1), and set the information status to "distributing".
[0147] The system sends a distribution task to the message queue, querying online users within the polygon fence. A coarse screening using an H3 hexagonal hierarchical index (resolution res=9) yields 47 online users within the fence. A fine screening using ray casting removes 2 users located at the polygon boundaries, leaving 45. Excluding the poster, 44 users remain. Further filtering based on reputation score (≥100) removes 4 users, leaving 40. Users are sorted by matching score (reputation score weight 0.6, distance decay factor weight 0.3, interest matching weight 0.1). The top 100 users are actually all 40 (since the score is less than 100), and the system pushes the information to these 40 users. Employee Xiao Liu (reputation score 105, distance 1.2 km from the fence center, 7 browsing history of travel-related information) has a matching score of 89.6. After receiving the push, he clicks to view details and inquires, then places and pays for 11 orders. The system uses Redis atomic counters to accumulate the number of participants; currently, it's 11 / 21, not yet reaching the limit, so the distribution continues. Nine more people subsequently placed orders, bringing the total to 20. The system then sent a "Group Formation Imminent" notification. After the 21st person placed their order, the system automatically changed the status from "Distributing" to "Group Formation Completed," stopped sending notifications, and removed the group from the distribution index. After the trip, both parties left feedback. Xiao Liu gave a 5-star review, increasing the travel company's reputation score from 127 to 128 (+1), and Xiao Liu's reputation score from 105 to 106 (+1).
[0148] Scenario 2: Designers post procurement requests
[0149] The main difference between this scenario and Scenario 1 is that the first user is a designer who has already verified their identity (reputation score 101), and posts a request to "purchase 100 Huawei P40 phones" with a budget of 2000 yuan per phone. The request requires the recipient to have a reputation score of ≥95, and there is no limit to the number of people required to form a group. The geofence is set to the preset polygon boundary of "XX Communications Market".
[0150] Publishing permission verification: Reputation score 101 ≥ 90, real-name authentication status is true, passed.
[0151] Preliminary review: Form fields not empty validation passed; no images uploaded, image review skipped.
[0152] Feasibility review:
[0153] Content compliance review: The text "purchase 100 Huawei P40 units" did not match the sensitive word list.
[0154] Verification of the authenticity of the business logic: The average transaction price of "Huawei P40" in the past 30 days, as found in the historical transaction database, is 2100 yuan. The user's budget of 2000 yuan is within a reasonable fluctuation range (±10%), so it passes; no images are found in the reverse image search, so it is skipped; the reputation threshold of 95 ≤ the publisher's reputation score of 101 is reasonable.
[0155] User behavior review: The user's records for the past 30 days show no false posts and 0 complaints, so the review is approved.
[0156] After the three-level review is passed, the system will increase the designer's credibility score from 101 to 102 (content credibility score +1), and the information status will be set to "distributing".
[0157] User filtering within the fence: A combination of coarse and fine filtering using polygonal fences was used to identify 63 online users within the fence; excluding the poster, 62 users remained; based on reputation score (≥95), 8 users were removed, leaving 54 users. The system then pushed information to these 54 users.
[0158] Merchant Mr. Wang (reputation score 106, 0.5 km from the center of the fence, 32 past sales of mobile phones) has a matching score of 94.2. After receiving the push notification, he contacted the designer. The two communicated via chat, Mr. Wang listed the product, and the designer placed an order for 100 units. After the transaction was completed, Mr. Wang shipped the goods, the designer confirmed receipt, and both parties rated each other 5 stars. The designer's reputation score increased from 102 to 103 (+1), and Mr. Wang's reputation score increased from 106 to 107 (+1).
[0159] Since there is no limit to the number of users, the information remains distributed until the order is completed. Once the order status changes to "Completed," a Kafka event is triggered, and the consumer executes an automatic sinking process: updating the database status to "Completed"; deleting the information from the Redis nearby_services sorted set; and clearing the H3 cell mapping. Subsequent queries will no longer return this information.
[0160] Scenario 3: Designers publish UI design services
[0161] The main difference between this scenario and Scenario 1 is that the first user is a designer who has already verified their identity (reputation score 102), and posts a "UI design service" as a service provider, priced at 50 yuan per page, with no limit on the number of users, and requiring the recipient's reputation score to be ≥90. The geofencing uses a circular fence (the user long-presses a map point to set the center, and slides the radius bar to generate a 3-kilometer circular area).
[0162] Publishing permission verification: Reputation score 102 ≥ 90, real-name authentication status is true, passed.
[0163] Preliminary review: Form field non-empty validation passed; image upload detection found no violations.
[0164] Feasibility review:
[0165] Content compliance review: The text "UI design services" did not match the sensitive word list.
[0166] Verification of the authenticity of business logic: The average transaction price of "UI design services" in the past 30 days, as found in the historical transaction database, is 55 yuan / page. The user's quoted price of 50 yuan is within a reasonable fluctuation range (±20%), so it passes the verification. The reputation threshold is 90 ≤ and the publisher's reputation score is 102, which is reasonable.
[0167] User behavior review: No violations in the past 30 days, approved.
[0168] After the review is approved, the designer's credibility score increases from 102 to 103 (content credibility score +1), and the information status is set to "distributing".
[0169] User filtering within the fence: Using the Redis GEORADIUS command, based on the center (30.1234°N, 120.5678°E) and a radius of 3 kilometers, 28 online users within the range are directly returned; excluding the poster, 27 users remain; based on reputation score (≥90), 2 users are removed, leaving 25 users. The system pushes information to these 25 users.
[0170] When business owner Xiao Wang browsed information in the "Browse Nearby" module, the system displayed the information in descending order of comprehensive reputation score (poster reputation score weighted at 0.5, timeliness weighted at 0.3, and distance weighted at 0.2). Xiao Wang's comprehensive score was 88.3 (current reputation score 92, distance from the center of the fence 2.1 km, posting time 2 hours), ranking him 3rd. After Xiao Wang inquired and placed an order, the service was completed and both parties gave each other a 5-star rating. The designer's reputation score increased from 103 to 104 (+1), and Xiao Wang's reputation score increased from 92 to 93 (+1).
[0171] The information is automatically posted after the order is completed, following the same process as in scenario two.
[0172] Example 3
[0173] like Figure 3 As shown, this embodiment provides an information distribution system 100 based on geofencing and unified reputation assessment, including:
[0174] The information receiving module 10 is used to receive business event information published by the first user, as well as the geofence and the reputation threshold value of the receiver set by the first user for the business event information.
[0175] The filtering and push module 20 is used to identify at least one second user who is currently located within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and to push business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior;
[0176] The relationship establishment module 30 is used to establish an interactive relationship between the first user and the second user in response to the second user's acceptance of business event information.
[0177] The rating adjustment module 40 is used to adjust the reputation score of the first user and / or the second user in response to the mutual rating results between the first user and the second user after the interaction ends.
[0178] This embodiment is used to implement the method provided in the above embodiments and has the corresponding beneficial effects of the method. Technical details not described in detail in this embodiment can be found in the methods provided in all the foregoing embodiments of this invention.
[0179] The embodiments described above are merely illustrative of several implementations of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention. Therefore, the scope of protection of this patent should be determined by the appended claims.
Claims
1. An information distribution method based on geofencing and unified reputation assessment, characterized in that, Includes the following steps: Receive business event information published by the first user, as well as the geofence and recipient reputation threshold set by the first user for the business event information; Identify at least one second user currently located within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and push the business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior; In response to the second user's acceptance of the business event information, an interaction relationship is established between the first user and the second user; In response to the mutual evaluation results between the first user and the second user after the interaction ends, the reputation scores of the first user and / or the second user are adjusted.
2. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, Before receiving the business event information published by the first user, a publication permission verification step is also included: Obtain the first user's current reputation score and the authentication status corresponding to their current role; If the current reputation score does not reach the preset publication threshold, or the authentication status is not passed, then the publication of the business event information will be refused.
3. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, The first user publishes demand-type events and / or service-type events using the same account, and the reputation score is shared among different event types under the same account.
4. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, Before determining the second user, the process also includes: The business event information is subject to a feasibility review, which includes at least one of the following: content compliance review, business logic authenticity review, and user behavior review. If the review is approved, the business event information will be set to the distribution status, and the reputation score of the first user will be increased. If the review fails, the posting will be blocked and the first user's reputation score will be deducted.
5. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, The geofence is determined by at least one of the following methods: a. Receive the target location name input by the first user and match it to obtain the preset geofence boundary corresponding to the target location name; b. Receive the selection operation of the first user on the geographic interface and generate a circular fence.
6. The information distribution method based on geofencing and unified reputation assessment according to claim 5, characterized in that, After determining the geofence, the process also includes prompting the first user that the business event information will be pushed to a second user located within the geofence, and waiting for the first user's confirmation.
7. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, The reputation score is determined based on the platform's objective evaluation of user behavior and the subjective evaluation after user interactions.
8. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, The method for determining the second user currently located within the geofence includes: The geofence is converted into several spatial units using spatial indexing. Candidate second users are obtained from the set of online users corresponding to each spatial unit, and the location of the candidate second user is determined to be within the geofence using a point containment algorithm.
9. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, When pushing the business event information to the second user, the information is pushed in order of priority. The priority is determined by weighting the second user's current reputation score, the degree of matching with the business event information, and the distance between the second user and the geofence center point.
10. The information distribution method based on geofencing and unified reputation assessment according to claim 8, characterized in that, The matching degree is calculated based on the similarity between the second user's historical behavior data and the business event information.
11. The information distribution method based on geofencing and unified reputation assessment according to claim 1, characterized in that, Also includes: After the interaction ends and both parties have given each other feedback, the business event information will be removed from the distribution list.
12. An information distribution system based on geofencing and unified reputation assessment, characterized in that, include: The information receiving module is used to receive business event information published by the first user, as well as the geofence and the recipient reputation threshold value set by the first user for the business event information. The filtering and push module is used to identify at least one second user who is currently located within the geofence and whose reputation score is not lower than the recipient's reputation threshold, and to push the business event information to the second user, wherein the reputation score is dynamically adjusted based on the user's historical behavior; The relationship establishment module is used to establish an interaction relationship between the first user and the second user in response to the second user's acceptance operation of the business event information; The rating adjustment module is used to adjust the reputation score of the first user and / or the second user in response to the mutual rating results between the first user and the second user after the interaction ends.
