Method and system for triggering collaborative editing space based on geographic position and social relationship

Abstract

The invention discloses a method and a system for triggering a collaborative editing space based on a geographic position and a social relationship, and relates to the technical field of collaborative editing, and the method comprises the following specific steps: a user terminal judges a triggering condition through a positioning report position and a geofence service, and sends an event to an application server if the triggering condition is met; the server verifies the social relationship, screens visible space-time capsules and notifies the terminal; the server verifies the authority for the second time when the terminal previews and checks; according to the method, the geographical fence and the social relation verification are combined, accurate triggering and personalized display of the content are realized, the timeliness and the correlation of content discovery are improved, and meanwhile, the method has the advantages that the user can edit the content, the version is updated, the terminal is updated and displayed, and the user experience is improved. A multi-dimensional editing authority control and version priority algorithm is introduced, the problem of multi-user concurrent editing conflicts is solved, multi-type content editing is supported, the collaborative creation efficiency is improved, and team collaboration in a geographic scene is supported.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of collaborative editing, in particular to a method and system for triggering a collaborative editing space based on geographical location and social relationship. BACKGROUND

[0002] With the rapid development of mobile Internet and location service technology, social applications and collaborative creation tools based on geographical location have gradually become an important carrier for users to share information and record scenes. The geofencing technology can trigger event push when a user enters, stays or leaves a specific area by setting a virtual boundary, providing a technical basis for scene-based content distribution. At the same time, the demand for friend interaction and content co-creation in social relationship networks is growing, and users expect to share or collaboratively edit associated content with related groups at specific geographical locations to form digital memory capsules with space-time value. However, existing technologies often handle geographical location triggering and social relationship verification in isolation, resulting in insufficient content push accuracy and extensive permission management, making it difficult to meet users' demand for dynamically obtaining and collaboratively editing personalized content in geographical scenes. Therefore, how to combine the scene triggering capability of geofencing with the refined verification of social relationship has become a key technical direction to improve the value of collaborative editing space.

[0003] Traditional content distribution systems based on geographical location usually rely on simple distance thresholds or fixed entry triggers, lacking dynamic analysis of user stay duration and behavior intention, resulting in overly rigid triggering conditions and easy mis-triggering or missed triggering. For example, a user may receive irrelevant push when passing through a certain area briefly, but the expected content may not be triggered when staying for a long time. In terms of social relationship management, traditional solutions often use a binary permission model of "non-public is public", which cannot quantify the social closeness between users and content associates, resulting in overly extensive content visibility control, which may leak privacy or restrict legitimate access. In addition, in the collaborative editing scenario, there is a lack of intelligent version merging strategy when multiple users modify the same content, which may easily cause data conflicts and require manual intervention to coordinate, reducing the efficiency of creation. SUMMARY

[0004] The present application aims to overcome the shortcomings of the prior art and provides a method and system for triggering a collaborative editing space based on geographical location and social relationship. The system realizes scene-based content triggering through geofencing technology, dynamically controls content visibility by combining social relationship quantification verification, ensures that users only obtain space-time capsules that are associated and have matching permissions at specific geographical locations, supports collaborative editing of multiple types of content, and introduces an editing version priority algorithm to solve the conflict of multiple users modifying the same content, thereby improving the efficiency of creation.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution: On one hand, a method for triggering collaborative editing spaces based on geographical location and social relationships, the specific steps of which are as follows: S100, Geofencing Trigger Determination: The user terminal application obtains the user's geographical location through positioning technology and reports it to the geofencing service. The geofencing trigger determination algorithm analyzes the spatial relationship between the user's location and the geofencing. When the user's location is determined to meet the triggering conditions, a trigger event containing the user's unique identifier UID and geofencing identifier FID is sent to the application server. If the conditions are not met, monitoring continues. S200, Social Relationship Verification and Visible Space-Time Capsule Filtering: The application server queries the space-time capsules associated with the fence, first queries friends, then queries the friends' space-time capsules through friend information, and then determines whether to display them. For each space-time capsule, it verifies the social relationship between the current user and the user associated with the space-time capsule, filters visible space-time capsules, and sends a notification containing space-time capsule information and deep links to the user terminal. S300, Time Capsule Preview and Viewing Permission Secondary Verification: The user terminal receives a notification and displays the Time Capsule preview interface; when the user clicks to view, the terminal requests the complete Time Capsule data from the application server. The server verifies the user's viewing permission again. If the preview indicates that the user has been verified before, the server returns the complete data including version history and displays it on the terminal. If the user does not have permission, the server returns a permission error. S400, Collaborative Editing and Editing Permission Control: When a user with permission chooses to edit a time capsule, the editor needs to apply for editing first. The creator agrees to the editing, and the terminal opens the corresponding type editor for the user to submit the edited content. The application server verifies the user's editing permissions. If the user has permission, the new content block is added to the time capsule content list, and the version history is updated at the same time. If the user does not have permission, the editing request is rejected and a permission error is returned. After the editing is completed, the terminal updates the local interface display.

[0006] Further, in the S100, for the determination of geographical fence triggering, the geographical fence service pre-creates geographical fences with triggering conditions for each scenic spot, specifically including: The geographical fence service supports creating two types of fence shapes, namely circular and polygon; for a circular fence, the longitude and latitude coordinates of the fence center point and the fence radius need to be configured; for a polygon fence, the longitude and latitude coordinate sets of at least 3 vertices are configured by importing or manually drawing; the triggering conditions include three types: entry trigger, stay trigger, and departure trigger. Among them, the entry trigger corresponds to a stay duration threshold of 10 seconds, the stay trigger corresponds to a stay duration threshold of 300 seconds, and the departure trigger does not require a stay duration threshold; and a unique geographical fence identifier FID is generated for each geographical fence, and at the same time, it is bound and stored with the POI identifier of the scenic spot, and the binding relationship is recorded in the geographical fence association table; and a trigger count limit is set for each geographical fence, that is, after the user has viewed the corresponding triggering content on the same day, it will not be triggered again on the same day; at the same time, a flag indicating whether to trigger is set for each geographical fence, and the scenic area staff or users who do not want to trigger can turn off this flag.

[0007] Furthermore, in the S100, for the determination of geographical fence triggering, the calculation formula of the geographical fence triggering determination algorithm is: , where: is the result of geographical fence triggering determination, 1 indicates that the triggering condition is met, 0 indicates that the triggering condition is not met, P is the real-time position coordinate of the user, G is the geographical fence parameter, is the set of time parameters related to the user's stay in the fence area, is the coordinate of the fence center point, is the radius of the circular fence, is the actual stay duration of the user in the fence candidate area, is the preset trigger stay threshold of the fence, δ(P) is the user position accuracy deviation, is the fence range elasticity coefficient, is the accuracy compensation coefficient, is the Haversine distance between the user position and the fence center point.

[0008] Furthermore, in S200, during the social relationship verification and visible time capsule filtering, the specific content included in the time capsule is as follows: each time capsule includes a unique identifier, associated attraction identifier, creator identifier, creation time, visibility settings, and a list of content blocks; the visibility settings are divided into three types: Private, Friends, and Public. Private means only visible to oneself; Friends means visible to general friends, who can apply to edit; Public means visible to friends and friends of friends, but the permission to apply for editing is only granted to general friends when a general friend has edited it; the list of content blocks consists of at least one content block, and each content block includes a unique identifier, the identifier of the time capsule to which it belongs, the editor identifier, the content type, the content data, the editing time, the parent content block identifier, and a soft delete marker; the time capsule is also associated with a version history, and each record includes a version number, the time capsule identifier, the editor identifier, the editing time, and a version description.

[0009] Furthermore, in S200, the specific steps for verifying the social relationship between the current user and the users associated with the time capsule in the social relationship verification and visible time capsule filtering are as follows: The application server extracts the set of associated users of the current time capsule. This set consists of the time capsule creator identifier and the editor identifiers of all non-soft-deleted content blocks in the content block list after deduplication. Soft deletion refers to not physically deleting the content block data. For the current user and each associated user in the set, the following operations are performed in sequence: Query the user relationship database to obtain whether the two parties are mutual friends, and record it as a mutual friend indicator function; Statistical analysis of the past 90 days... The total interaction time between the two parties through in-app chat, co-editing, likes, and comments is calculated; the block relationship database is queried to determine whether the associated user has blocked the current user, and this is recorded as a block status indicator function; the number of negative interactions and the total number of interactions between the two parties in the past 90 days are counted; the above parameters are substituted into the social weight quantification algorithm to obtain the social weight value between the current user and the associated user; after traversing all associated users in the set, the maximum social weight value is taken as the social association evaluation value between the current user and the time capsule; based on the time capsule visibility settings and the social association evaluation value, the time capsule visibility decision algorithm determines whether the current user has permission to view the time capsule.

[0010] Furthermore, in S200, during the social relationship verification and visible spatiotemporal capsule screening, the calculation formula for the social weight quantification algorithm is as follows: ,in: This is the social weight value between the current triggering user and the users associated with the time capsule, used to quantify the closeness of their social relationship. For the currently triggering user, For users associated with the Time Capsule, This is a function to indicate mutual friend status; 1 = mutual friend, 0 = non-mutual friend. for and Total interaction time over the past 90 days The maximum interaction duration threshold set for the system. This is a masking status indicator function; 1 indicates... shield 0 indicates that it is not blocked. for and Number of negative interactions in the past 90 days for and Total number of interactions in the past 90 days These are weighting coefficients, corresponding to the weighting percentages of two-way friend relationships, interaction duration, blocked status, and negative interactions, respectively. .

[0011] Furthermore, in S200, during the social relationship verification and visible spatiotemporal capsule screening, the calculation formula for the spatiotemporal capsule visibility decision algorithm is as follows: ,in: This is the visibility determination result for the time capsule. 1 indicates that the current user has permission to view the time capsule, and 0 indicates that the user does not have permission to view it. It is a time capsule awaiting determination. It is the currently triggering user. It refers to the visibility settings for the Time Capsule, including three types: public, friend, and private. It is a single user in the set of users associated with the time capsule. It is a collection of users associated with the Time Capsule, consisting of the Time Capsule creator's identifier and the editor's identifiers of all non-soft-deleted content blocks in the content block list, after deduplication. It is the maximum social weight among the current user and the set of associated users. It is the visibility weight threshold, used to determine whether the friend-type visibility capsule has viewing permissions for the current user.

[0012] Furthermore, in the S400, the collaborative editing and editing permission control features include: the editor supports editing four content types: text, images, videos, and routes; the text editor supports inserting emoticons, adding line breaks, and undo / redo functions; the image editor supports selecting images from the album or taking photos with the camera, and provides cropping, rotation, and filter functions; the video editor supports selecting videos from the album or recording videos with the camera, and provides editing and background music addition functions, with a video length limit of 10 minutes; the route editor supports manually drawing routes or importing GPX files, and displays the route trajectory on the map component; simultaneously, after receiving the Time Capsule content push for the first time, the content will be cached locally and in the cloud.

[0013] Furthermore, in S400, during collaborative editing and editing permission control, when multiple users are editing concurrently, the version priority of each content block is evaluated using an editing version priority algorithm. The calculation formula for the editing version priority algorithm is as follows: ,in: This is the priority value of the content block version to be evaluated. The higher the priority, the more likely it is to be used as the baseline version for multi-user concurrent editing and merging of content. This is the version of the content block to be evaluated. It is a related time capsule. yes The effective data length, It is the maximum valid data length of the same type of content block within the time capsule. This is a content block ownership indicator function; 1 indicates... The editor is the creator of the time capsule, and 0 represents other editors. for Related content blocks from the previous version, for and Content similarity, This is the maximum similarity threshold, fixed at 1. for The editing time This represents the average editing time for similar content blocks within a time capsule. These are weighting coefficients, corresponding to the weighting percentages of effective data length of content blocks, editor identity, content similarity, and editing time, respectively. .

[0014] On the other hand, a system for triggering collaborative editing spaces based on geographic location and social relationships includes user terminals, geofencing services, application servers, databases, and push services. The user terminal is an iOS or Android mobile app that supports GPS, Wi-Fi, and Bluetooth positioning. It supports Android Geofencing API and iOS RegionMonitoring low-power positioning mode. It can report user location data, receive event notifications and push notifications, display the time capsule preview interface, send data requests and editing requests to the application server, provide an editor, and support viewing the time capsule version history and filtering the historical status of specific time points. The geofencing service creates circular and polygonal geofences, configures entry, stay, and exit trigger conditions, analyzes user location data, determines whether the trigger conditions are met, and sends a trigger event containing the user's unique identifier (UID) and geofence identifier (FID) to the application server when the conditions are met. The application server: receives the trigger event of the geofence service, queries the list of time capsules from the database according to the FID, extracts the set of associated users, calls the database to query user relationships and blocking status to determine the visibility of time capsules, sends push requests to the push service, receives requests from user terminals and verifies permissions, retrieves or updates database data when permissions are granted, and returns an error when permissions are denied. It can also handle concurrent editing conflicts. The database stores basic user information, user two-way friend relationship data, user blocking status data, and time capsule data. The push service integrates Apple APNs and Google FCM push channels, receives push requests from application servers, and sends notifications containing time capsule information and deep links to user terminals with specified UIDs.

[0015] A time capsule is a digital content entity used in collaborative editing systems to store, organize, and strongly associate with specific geographical locations (such as tourist attractions or business districts). Its core purpose is to support content management and collaborative creation based on location-triggered and social relationship-based access control. This entity combines technical precision with user interactivity, and is defined as follows: Technical perspective: A time capsule is a versionable, evolving multimodal content container with the following core attributes: Unique Identifier: Each time capsule has a globally unique ID, which is used for precise location and retrieval within the system.

[0016] Geographic association: By binding "associated attraction identifiers" (such as POIIDs) to one or more predefined geofences, it is the technical basis for content to be automatically triggered based on the user's location.

[0017] Multimodal content organization: Content is stored in the form of a list of "content blocks". Each content block supports multiple data types such as text, images, videos, routes, etc., and records metadata such as editor, editing time, and parent version identifier.

[0018] Dynamic version control: By maintaining a version history, the modification process of the content can be fully tracked, ensuring that all editing operations are traceable and auditable.

[0019] Soft deletion mechanism: The deletion operation of content blocks adopts mark deletion instead of physical deletion, so as to maintain the integrity of version history and data consistency.

[0020] User perspective: Time capsules are digital collective memory carriers and community co-creation tools. Users or teams can create themed content (such as travel notes or restaurant guides) at specific physical locations. When other users arrive at that location, the system can automatically push relevant capsules based on their geographical location; users have differentiated viewing and editing permissions based on their social closeness with the capsule creator / participant. Through collaborative editing mechanisms, the content of time capsules is continuously enriched and evolved, ultimately forming a continuously growing digital knowledge base and story collection maintained by the community around a geographical point.

[0021] Compared with existing technologies, this method and system for triggering collaborative editing spaces based on geographic location and social relationships has the following advantages: I. This invention achieves precise content triggering and personalized display through a deep integration of geofencing technology and social relationship verification. Traditional collaborative editing spaces often rely on users actively searching or accessing through fixed entry points. However, this invention pre-configures trigger conditions for attractions through geofencing services. When a user's location meets the conditions, relevant content is automatically pushed, improving the timeliness and relevance of content discovery. At the same time, combined with the social relationship verification mechanism, the system dynamically filters the time capsule content visible to users. Based on social weight factors such as two-way friendship, interaction frequency, and blocking status, the system quantifies the intimacy between the user and the content associates, ensuring that only personalized information that meets the permissions is displayed. This design not only avoids interference from irrelevant information but also optimizes content visibility through social association evaluation values, allowing users to obtain a more emotionally resonant and practically valuable content experience in specific geographical locations.

[0022] Second, this invention solves the conflict and data consistency problems in multi-user concurrent editing by introducing multi-dimensional editing permission control and version priority algorithms. Traditional collaborative editing tools usually only support simple permission division, while this invention dynamically allocates editing permissions through an editing permission verification mechanism that combines user identity, content type, and historical editing records, ensuring that only authorized users can modify specific content blocks. At the same time, the editing version priority algorithm automatically selects the optimal version as the merging benchmark by evaluating factors such as the effective data length of the content block, the editor's identity, content similarity, and editing time, significantly reducing manual coordination costs. In addition, the system supports editors for multiple types of content such as text, images, videos, and routes, and is compatible with manual drawing and GPX file import, further improving the flexibility and efficiency of collaborative creation and providing strong support for team work or social co-creation in geographical scenarios.

[0023] Other advantages, objectives and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination or study, or may be learned from the practice of the invention. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0025] Figure 1 A flowchart illustrating the method for triggering collaborative editing spaces based on geographic location and social relationships; Figure 2 A system architecture diagram for triggering collaborative editing spaces based on geographic location and social relationships; Figure 3 This is a flowchart illustrating the core steps of a method for triggering collaborative editing spaces based on geographic location and social relationships. Detailed Implementation

[0026] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0027] Example 1: An implementation example of a method for triggering collaborative editing spaces based on geographic location and social relationships, the specific steps of which are as follows: Figure 1 As shown.

[0028] S100, Geofence Trigger Determination: To enhance the tourist experience and promote the sharing and interaction of travel records among tourists, a 5A-level scenic area creates a dedicated geofence for the core scenic spot "Cloud Sea Viewing Platform" within the scenic area through geofence services. Considering the游览需求 around the viewing platform, a circular fence shape is selected, the longitude and latitude coordinates of the center point of the viewing platform are accurately configured, and a fence radius of 50 meters is set to ensure coverage of the viewing platform and the surrounding areas where tourists gather for activities. Combining with the behavior habit that tourists usually stay at the viewing platform to take pictures and打卡, the trigger condition is set to "entry trigger", and the corresponding停留时长阈值 is 10 seconds, which can not only avoid误触发 when tourists pass by briefly but also capture real游览需求 in a timely manner. The geofence service generates a unique geofence identifier FID for this fence, binds it to the POI identifier of the "Cloud Sea Viewing Platform" scenic spot, and stores it in the geofence association table. At the same time, a trigger count limit is set for each geofence, that is, after the user has viewed the corresponding trigger content on the same day, it will not be triggered again on the same day. At the same time, a flag indicating whether it has been triggered is set for each geofence, and scenic area staff or users who do not want to trigger can关闭 this flag. This binding operation can enable subsequent rapid定位 of associated scenic spots and related data through FID, laying a foundation for subsequent时空胶囊查询.

[0029] When a tourist enters the scenic area with a smartphone installed with the corresponding travel App, the GPS定位技术 is automatically activated in the App background to实时获取 the tourist's geographical location information and continuously上报 it to the geofence service in a low-power mode. This process does not require manual operation by the tourist to ensure the smoothness of the user experience. After receiving the position data, the geofence service immediately运用 the geofence trigger determination algorithm to analyze the spatial relationship between the tourist's position and the geofence of the "Cloud Sea Viewing Platform". The calculation formula of the geofence trigger determination algorithm is: [[ID=VI]] [[ID=VII]]where: [[ID=VIII]] [[ID=IX]]is the geofence trigger determination result, 1 indicates that the trigger condition is met, 0 indicates that the trigger condition is not met, P is the user's real-time position coordinate, G is the geofence parameter, [[ID=X]] [[ID=XI]]is the set of time parameters related to the user's stay in the fence area, [[ID=XII]] [[ID=XIII]]is the coordinate of the fence center point, [[ID=XIV]] [[ID=XV]]is the radius of the circular fence, [[ID=XVI]] [[ID=XVII]]is the actual stay duration of the user in the fence candidate area, [[ID=XVIII]] [[ID=XIX]]is the preset trigger stay threshold of the fence, δ(P) is the user position accuracy deviation, [[ID=XX]] [[ID=XXI]]is the fence range elasticity coefficient, [[ID=XXII]] [[ID=XXIII]]is the accuracy compensation coefficient, [[ID=XXIV]] It should be noted that there are some unclear terms in the original text such as "游览需求", "打卡", "停留时长阈值", "误触发", "关闭", "定位", "时空胶囊查询", etc. The above translation tries to make sense based on the context, but it may need further clarification and refinement according to the specific meaning.The algorithm calculates the Haversine distance between the user's location and the center point of the geofence. It comprehensively considers the accuracy deviation of the visitor's location (avoiding misjudgments due to location drift), the elasticity coefficient of the geofence range (adjusting for different coverage needs in various scenarios), and the accuracy compensation coefficient (further improving accuracy). Simultaneously, it rigorously determines whether the visitor's actual dwell time in the candidate geofence area reaches the preset 10-second trigger threshold, effectively filtering invalid trigger scenarios. When the visitor's location meets the trigger conditions, the geofence service quickly sends a trigger event containing the visitor's unique identifier (UID) and the "Cloud Sea Viewpoint" geofence identifier (FID) to the application server. This event provides a crucial trigger signal for subsequent time capsule filtering and push notifications. If the trigger conditions are not met, real-time monitoring of the visitor's location continues to ensure timely response when the visitor enters the valid area and meets the dwell requirements. Figure 3 As shown.

[0030] S200, Social Relationship Verification and Visible Spacetime Capsule Filtering: After receiving the trigger event sent by the geofencing service, the application server first queries and obtains all the current user's friend information (friends here refer to friends who have created or edited other people's time capsules). Then, based on the FID in the event and the IDs of these friends, it accurately queries the database for all time capsules associated with the "Cloud Sea Viewpoint" fence and created or edited by these friends. These time capsules may contain travel notes, photo collections, and tour guides created by other tourists at the attraction, providing rich reference resources for current tourists. Each time capsule contains a unique identifier (to distinguish different capsules), an associated attraction identifier (i.e., the "Cloud Sea Viewpoint" POI identifier to ensure matching with the current attraction), a creator identifier, creation time, visibility settings (divided into three types: Private, Friends, and Public; Private means only visible to the user; Friends means visible to general friends and can request editing; Public means visible to friends and friends of friends, but editing permission is still only available to general friends), and a list of content blocks (containing specific content). It is also associated with a detailed version history (to facilitate tracing the content modification process). This structured data provides clear data support for subsequent verification and filtering.

[0031] The application server processes each queried time capsule one by one. First, it extracts the set of associated users for that time capsule. This set consists of the time capsule creator's identifier and the editor identifiers of all non-soft-deleted content blocks in the content block list after deduplication (soft deletion refers to not physically deleting the content block data, but only marking the deletion status, which preserves the possibility of data traceability and does not affect the current content display). This operation can accurately identify all users related to that time capsule, clarifying the scope of objects for subsequent social relationship verification.

[0032] Next, for the currently triggered visitor (current user) and each associated user in the associated user set, a series of operations are performed sequentially: The user relationship database is queried to determine whether the two parties are mutual friends, and this is recorded as a mutual friend indicator function. The result of this function is an important basis for judging the closeness of the social relationship; the total interaction time generated by the two parties in the past 90 days through in-app chat (real-time communication and interaction), joint editing (collaborative behavior), and likes and comments (content interaction) is calculated. The duration data can intuitively reflect the recent interaction frequency of the two parties; the blocking relationship database is queried to determine whether the associated user has blocked the current visitor, and this is recorded as a blocking status indicator function. This function can effectively avoid pushing content from blocked users to users, ensuring user experience; the number of negative interactions (such as malicious comments and disputed communication) and the total number of interactions between the two parties in the past 90 days are calculated. The percentage of negative interactions can help judge the quality of the social relationship between the two parties.

[0033] Subsequently, the parameters obtained above are substituted into the social weight quantification algorithm to calculate the social weight value between the current visitor and the associated user. The calculation formula of the social weight quantification algorithm is as follows: ,in: This is the social weight value between the current triggering user and the users associated with the time capsule, used to quantify the closeness of their social relationship. For the currently triggering user, For users associated with the Time Capsule, This is a function to indicate mutual friend status; 1 = mutual friend, 0 = non-mutual friend. for and Total interaction time over the past 90 days The maximum interaction duration threshold set for the system. This is a masking status indicator function; 1 indicates... shield 0 indicates that it is not blocked. for and Number of negative interactions in the past 90 days for and Total number of interactions in the past 90 days These are weighting coefficients, corresponding to the weighting percentages of two-way friend relationships, interaction duration, blocked status, and negative interactions, respectively. This value can scientifically quantify the closeness of the social relationship between the two parties, providing data basis for subsequent visibility determination. After traversing all users in the set of associated users, the maximum value of the social weight value is taken as the social association evaluation value between the current visitor and the time capsule. This maximum value can ensure that the current visitor can obtain the time capsule permissions related to the users with the closest social relationship with him to the greatest extent.

[0034] Finally, based on the visibility settings of the time capsule (divided into three types: Private, Friends, and Public; Private: visible only to the user; Friends: visible to general friends, with the option to edit; Public: visible to friends and their friends, but editing access is still only available to general friends) and the calculated social association evaluation value, the time capsule visibility decision algorithm determines whether the current visitor has permission to view the time capsule. The calculation formula for the time capsule visibility decision algorithm is as follows: , in: This is the visibility determination result for the time capsule. 1 indicates that the current user has permission to view the time capsule, and 0 indicates that the user does not have permission to view it. It is a time capsule awaiting determination. It is the currently triggering user. It refers to the visibility settings for the Time Capsule, including three types: public, friend, and private. It is a single user in the set of users associated with the time capsule. It is a collection of users associated with the Time Capsule, consisting of the Time Capsule creator's identifier and the editor's identifiers of all non-soft-deleted content blocks in the content block list, after deduplication. It is the maximum social weight among the current user and the set of associated users. This is the visibility weight threshold, used to determine whether the friend-type visibility capsule has viewing permissions for the current user. This algorithm can accurately filter out capsules that match the current visitor's permissions, ensuring both user privacy and security while ensuring that users can access appropriate content resources. After filtering, the application server sends a notification containing information about these capsules and deep links to the visitor's mobile terminal. Deep links allow users to directly jump to the corresponding content page after clicking, improving user convenience.

[0035] S300, Time Capsule Preview and Viewing Permission Secondary Verification: After receiving a notification from the application server, the visitor's mobile device immediately displays a preview interface of the time capsule on the App interface in the form of a pop-up window or message list. The preview interface presents key information such as the creation time of the time capsule, thumbnails of some content blocks (such as landscape photo thumbnails, guide titles), and associated user avatars, helping visitors quickly understand the core content of the time capsule and assisting them in deciding whether they need to view the full content. When a visitor clicks on a time capsule to view the full content, the mobile device automatically sends a request to the application server to obtain the complete data of that time capsule. This request includes the visitor's UID and the unique identifier of the time capsule, ensuring that the application server can accurately locate the target data.

[0036] Upon receiving the request, the application server, to further ensure the security of the Time Capsule data and avoid permission issues caused by oversights in the initial verification, re-verifies the visitor's viewing permissions. This verification process comprehensively considers the results of previous social relationship verification, the Time Capsule's visibility settings, and the visitor's current account status (e.g., whether it has been banned), forming a dual permission protection mechanism. If the visitor has permission to view, the application server returns complete data containing the Time Capsule's version history. Upon receiving this data, the mobile terminal displays the Time Capsule's complete content in a clear layout within the app, including all content blocks (such as complete photos, detailed text guides, and tour maps) and version history (showing the time of each edit, the editor, and a summary of the modified content), allowing visitors to fully understand the Time Capsule's detailed information and evolution. If the visitor does not have permission to view, the application server returns a clear permission error message (e.g., "You do not have permission to view this content"). Upon receiving this error message, the mobile terminal displays a user-friendly pop-up window informing the visitor of the lack of viewing permission, avoiding any confusion.

[0037] S400, Collaborative Editing and Editing Permission Control: When a tourist views a time capsule, if the tourist has editing permissions for that time capsule (permission determination is based on user permission settings stored in the application server, such as the scope of editing permissions granted by the time capsule creator, the tourist's social relationship permissions with the creator, and other time capsule-related configurations), and wishes to supplement their travel experience (such as adding new photo locations or correcting errors in the travel guide), they can click the "Edit" button on the app interface of their mobile device to select the editing function. At this time, editing requires prior application, and editing is only allowed after the creator's approval. The mobile device will then automatically open the corresponding editor based on the current content type of the time capsule and the tourist's editing needs. The editor supports editing four content types: text, images, videos, and routes, meeting the diverse content creation needs of tourists.

[0038] If tourists choose to edit text (such as adding to their visit experience or modifying details of the itinerary), the text editor supports inserting emoticons (enriching expression), line breaks (optimizing layout), and undo / redo functions (facilitating editing and reducing the impact of accidental operations). Tourists can freely input and modify text content in the editor and click "Preview" to confirm the effect after completion. If they choose to edit images (such as adding photos they took of the observation deck), the image editor supports selecting images from the phone's album or taking images in real time with the camera, and provides cropping (adjusting image size), rotation (correcting image angle), and filter functions (optimizing image effects). Tourists can personalize the image and then click "Upload." If they choose to edit videos (such as adding viewing views), the text editor supports editing videos of the observation deck. The video editor supports selecting existing videos from the album or recording videos on-site using the camera. It also provides editing functions (trimming video length, deleting redundant segments) and adding background music (to enhance the video's appeal), and strictly limits the video length to 10 minutes (to avoid consuming too much storage and transmission resources). After completing the video editing, tourists can click "Submit". If choosing to edit a route (such as adding a hidden route from the observation deck to the next attraction), the route editor supports manually dragging and drawing routes on the map or importing GPX files (for professional users). It can also display the route trajectory in real time on the map component. After editing the route, tourists can zoom in on the map to confirm the details, and then click "Confirm" to submit.

[0039] After a visitor submits edits, the mobile device encrypts and sends the edited content (including content data, the editor's UID, and the editing time) to the application server. Encrypted transmission ensures the security of the edited content during transmission, preventing data tampering or leakage. Upon receiving the edit request, the application server first verifies the visitor's editing permissions. If the verification is successful, to ensure the integrity and traceability of the time capsule content, a new content block is added to the time capsule's content list (the new content block exists independently of the original content block and does not overwrite the original data). Simultaneously, the time capsule's version history is updated in real time, recording the editor's identifier, editing time, and version description information for future reference. The user continues to view the content evolution; if the visitor does not have editing permissions, the application server rejects the editing request and returns a clear permission error message to the mobile terminal (such as "You do not have permission to edit this time capsule"). After receiving the error message, the mobile terminal informs the visitor of the lack of editing permissions in the form of a pop-up window on the interface, and at the same time provides an entry point for "Apply for editing permissions" (if the function supports it) to improve the user experience. When the editing request is successfully processed, the mobile terminal will receive the update confirmation information returned by the application server, and then automatically update the display of the local application interface to show the edited time capsule content and the updated version history in real time, ensuring that the visitor can immediately see their editing results and enhance user participation.

[0040] When multiple users (such as tourists in the same tour group) concurrently edit the same time capsule (e.g., multiple people adding photos from different angles of the observation deck or their tour experiences at different times), to avoid data corruption or content loss due to editing conflicts, the application server will evaluate the version priority of each user's submitted content block using an editing version priority algorithm. The formula for calculating the editing version priority algorithm is as follows: , in: This is the priority value of the content block version to be evaluated. The higher the priority, the more likely it is to be used as the baseline version for multi-user concurrent editing and merging of content. This is the version of the content block to be evaluated. It is a related time capsule. yes The effective data length, It is the maximum valid data length of the same type of content block within the time capsule. This is a content block ownership indicator function; 1 indicates... The editor is the creator of the time capsule, and 0 represents other editors. for Related content blocks from the previous version, for and Content similarity, This is the maximum similarity threshold, fixed at 1. for The editing time This represents the average editing time for similar content blocks within a time capsule. These are weighting coefficients, corresponding to the weighting percentages of effective data length of content blocks, editor identity, content similarity, and editing time, respectively. The algorithm comprehensively considers factors such as the effective data length of the content block (the richer the data, the higher the priority may be, such as detailed text guides having higher priority than short comments), the editor's identity (the time capsule creator's editing priority is higher than that of ordinary tourists, ensuring the creator's control over the content), the similarity between the content block and the previous version of the content block (new content with low similarity may have higher priority, such as adding a completely new tour route having higher priority than modifying individual text), and the editing time (deep editing that takes longer may have higher priority, such as a well-made video having higher priority than a quickly taken photo), to scientifically calculate the priority value of each content block version. The higher the priority of the content block version, the more likely it is to be used as the base version for merging content edited by multiple users concurrently. During the merging process, the core information of each version is preserved to ensure the orderliness and data consistency of collaborative editing. Finally, the complete and accurate collaborative editing results are presented to the user, giving full play to the advantages of multi-person collaboration and enriching the content value of the time capsule.

[0041] In summary, in the scenario of collaborative editing of scenic area travel records, this method accurately captures tourists' sightseeing behavior at core attractions through geofencing trigger judgment, avoids false triggers with corresponding algorithms, and provides a precise entry point for subsequent services. Through social relationship verification and visible time capsule filtering, combined with social weight quantification algorithms and visibility decision algorithms, appropriate content is pushed to tourists while protecting user privacy. Data security is strengthened through secondary verification of viewing permissions. In the collaborative editing process, multiple types of editors meet diverse creative needs, and the editing version priority algorithm resolves concurrent editing conflicts. The overall process not only improves the tourist's travel experience and sense of participation, but also ensures the security, integrity, and collaboration of the time capsule content.

[0042] Example 2: A system implementation example that triggers collaborative editing spaces based on geographic location and social relationships.

[0043] This system is applicable to the aforementioned method of triggering collaborative editing spaces based on geographic location and social relationships. The system consists of five parts: user terminal, geofencing service, application server, database, and push service. These parts work collaboratively in a collaborative scenario of exploring and sharing stores in urban commercial districts. The specific operation process is as follows: Figure 2 As shown: User terminal: The user terminal is a business district exploration and sharing app installed on an iOS or Android phone. The app supports GPS, Wi-Fi, and Bluetooth positioning technologies, as well as Android Geofencing API and iOS RegionMonitoring low-power positioning mode. It can accurately obtain the user's location data in the city's business district while reducing the phone's power consumption, and report the location data to the geofencing service in real time.

[0044] When a user enters a business district and the geofencing service determines that the triggering conditions have been met, the user's device can receive event notifications and push notifications from the push service. The notifications contain information and deep links to relevant time capsules within the business district (such as store visit notes and business district guides created by other users). When the user clicks on a deep link in the notification, the app will display a preview interface of the time capsule, where the user can view brief information about the time capsule.

[0045] In addition, if users want to view the complete content of the Time Capsule or edit it, they can send data requests and editing requests to the application server through the App. The App also provides various types of editors, supporting users to edit the Time Capsule with text, images, videos, routes and other content. Editing requires prior application and the creator's approval. Users can also view the version history of the Time Capsule and filter the historical status at specific points in time, making it convenient for users to understand the modification process of the Time Capsule.

[0046] Geofencing service: Business district operators use geofencing services to create geofences for various business districts within the city. For regularly shaped business districts, circular geofences are created, configuring the latitude and longitude coordinates of the business district's center point and an appropriate fence radius. For irregularly shaped business districts, polygonal geofences are created by importing business district boundary data or manually drawing them on a map, ensuring that the vertex intervals of the polygonal fences do not exceed 10 meters to guarantee the accuracy of the fence boundaries.

[0047] Meanwhile, the geofencing service configures trigger conditions for each business district's geofence, including three types: entry trigger, stay trigger, and departure trigger. The entry trigger corresponds to a stay duration threshold of 10 seconds, the stay trigger corresponds to a stay duration threshold of 300 seconds, and the departure trigger has no stay duration threshold. Each geofence generates a unique geofence identifier (FID) and binds it to the business district's POI identifier. The binding relationship is recorded in the geofence association table, and a trigger limit is set for each geofence. That is, if a user has already viewed the corresponding trigger content on the same day, it will not be triggered again on that day. At the same time, a trigger flag is set for each geofence, which can be turned off by business district operators or users who do not want to trigger it.

[0048] When the geofencing service receives user location data reported by the user terminal, it analyzes the spatial relationship between the user's location and the geofences of each business district to determine whether the user meets the trigger conditions. If the conditions are met, the geofencing service sends a trigger event containing the user's unique identifier (UID) and the corresponding business district geofence identifier (FID) to the application server. If the conditions are not met, the service continues to receive location data reported by the user terminal and continues to monitor changes in the user's location.

[0049] Application server: The application server is the core processing unit of the system. When it receives a trigger event sent by the geofencing service, it queries the database for a list of business district time capsules associated with the FID in the trigger event. Then, the application server extracts the set of associated users for each time capsule. This set consists of the time capsule creator identifier and the editor identifiers of all non-soft deleted content blocks in the content block list after deduplication.

[0050] Subsequently, the application server calls the database, queries the user relationship database to obtain the two-way friend relationship between the current user and each user in the set of associated users, queries the blocking relationship database to determine whether the associated user has blocked the current user, and at the same time, it counts data such as the total interaction time, the number of negative interactions and the total number of interactions between the two parties in the past 90 days, and then determines the visibility of the time capsule to the current user.

[0051] If the time capsule is visible to the current user, the application server sends a push request to the push service, which includes the time capsule information and a deep link. If it is not visible, no push operation is performed. When the application server receives a data request (such as viewing the complete data of the time capsule) or an editing request from the user terminal, it will verify the user's permissions. Editing requires prior application and the creator's approval. If the user has permission, the application server will retrieve the corresponding data from the database and return it to the user terminal, or update the time capsule data in the database based on the user's edits. If the user does not have permission, an error message will be returned to the user terminal.

[0052] In addition, when multiple users edit the same time capsule simultaneously, resulting in concurrent editing, the application server uses a specific algorithm to handle concurrent editing conflicts, ensuring the accuracy and consistency of the time capsule data.

[0053] database: Databases are used to store various types of data generated during system operation, specifically including: Basic user information: Stores user data such as UID, registration information, and personal information, providing a basis for user identification and permission determination.

[0054] User two-way friend relationship data: Records the two-way friend connections between users, which is an important basis for verifying social relationships.

[0055] User blocking status data: Stores the blocking relationship between users, used to determine whether a user can view a specific time capsule.

[0056] Time Capsule Data: This includes a unique identifier for each time capsule, associated business district POI identifier, creator identifier, creation time, and visibility settings divided into three types: Private, Friends, and Public. Private means only visible to the user; Friends means visible to general friends, who can apply to edit; Public means visible to friends and their friends, but editing permission is still only available to general friends. It also includes a list of content blocks and version history, forming the data foundation for the system's time capsule preview, viewing, and editing functions.

[0057] The database provides real-time services such as data query, data update, and data storage based on the application server's requests, ensuring that all parts of the system can obtain the required data in a timely manner and guaranteeing the normal operation of the system.

[0058] Push service: The push service integrates Apple APNs (for iOS devices) and Google FCM (for Android devices) push channels, enabling it to cover user terminals on different systems. When the push service receives a push request from the application server, it determines the target user terminal to be pushed to based on the user UID contained in the request.

[0059] Subsequently, the push service sends a notification containing information about the business district time capsule and deep links to the user's terminal with the specified UID through the corresponding push channel. After receiving the push notification, the user's terminal displays the notification content in the phone's notification bar. The user can click on the notification to jump to the corresponding time capsule preview interface in the App, realizing accurate delivery of time capsule information and improving the user experience in the scenario of exploring and sharing stores in the business district.

[0060] In summary, in the collaborative scenario of exploring and sharing stores in urban commercial districts, the system's components work together efficiently. User terminals enhance the user experience with low-power positioning and convenient operation; the geofencing service creates precise boundaries for commercial districts and triggers events in a timely manner; the application server, as the core processing unit, completes data querying, permission verification, and conflict resolution; the database stores various key data, providing support for system operation; and the push service achieves precise notification delivery through multiple channels. The interconnectedness of all parts not only allows users to conveniently access commercial district exploration resources and participate in collaborative editing, but also helps commercial districts enhance user interaction and sharing atmosphere, effectively meeting user needs and operational goals in the commercial district exploration scenario.

[0061] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A method for triggering a co-editing space based on geographical location and social relationship, characterized in that, The specific steps of the method are: S100, geographic fence trigger determination: the application program of the user terminal acquires the user geographic position through positioning technology and reports to the geographic fence service, analyzes the spatial relationship between the user position and the fence through a geographic fence trigger determination algorithm, sends a trigger event containing the user unique identifier UID and the geographic fence identifier FID to the application server when it is determined that the user position meets the trigger condition, and continues to monitor if it does not meet the condition; S200, social relationship verification and visible spatiotemporal capsule screening: the application server queries the spatiotemporal capsule associated with the fence, first queries friends, queries the spatiotemporal capsule of the friends through the friend information, then judges whether to display, verifies the social relationship between the current user and the spatiotemporal capsule associated user for each spatiotemporal capsule, screens the visible spatiotemporal capsule and sends a notification containing the spatiotemporal capsule information and a deep link to the user terminal; S300, spatiotemporal capsule preview and viewing permission secondary verification: the user terminal receives the notification and displays the spatiotemporal capsule preview interface; when the user clicks to view, the terminal requests the spatiotemporal capsule complete data from the application server, the server verifies the user viewing permission again, preview represents that the viewing has been verified before, and returns the complete data containing the version history and displays it on the terminal if there is permission, or returns a permission error if there is no permission; S400, collaborative editing and editing permission control: when a user with permission selects to edit the spatiotemporal capsule, editing needs to be applied first, and the creator can edit after agreeing, and the terminal opens the corresponding type editor to provide the user with editing content; The application server verifies the user editing permission, appends a new content block in the spatiotemporal capsule content list and updates the version history if there is permission; If there is no permission, the editing request is rejected and a permission error is returned; After editing is completed, the terminal updates the local interface display.

2. The method of claim 1, wherein the method further comprises: In the S100, geographic fence trigger determination, the geographic fence service pre-creates a geographic fence containing trigger conditions for each scenic spot, specifically including: the geographic fence service supports the creation of two types of fence shapes, circular and polygonal; for a circular fence, the fence center point latitude and longitude coordinates and the fence radius need to be configured; for a polygonal fence, at least three vertex latitude and longitude coordinate sets are configured through import or manual drawing; the trigger conditions include three types of entering trigger, staying trigger and leaving trigger, wherein the entering trigger corresponds to a staying time threshold of 10 seconds, the staying trigger corresponds to a staying time threshold of 300 seconds, and the leaving trigger does not require a staying time threshold; a unique geographic fence identifier FID is generated for each geographic fence, which is bound and stored with the POI identifier of the scenic spot, and the binding relationship is recorded in the geographic fence association table; and the trigger number limit is set for each geographic fence, that is, the user has viewed the corresponding trigger content on the same day, and the trigger will not occur on the same day; at the same time, an identifier of whether to trigger is set for each geographic fence, which can be turned off by the staff of the scenic area or the user who does not want to trigger.

3. The method of claim 1, wherein the method further comprises: The S100, in the geofence trigger determination, a calculation formula of a geofence trigger determination algorithm is: Wherein: is a geofence trigger determination result, 1 represents that a trigger condition is met, 0 represents that the trigger condition is not met, P is a real-time position coordinate of a user, G is a geofence parameter, is a set of stay-related time parameters of the user in the fence area, is a center point coordinate of the fence, is a radius of a circular fence, is an actual stay duration of the user in a fence candidate area, is a preset trigger stay threshold value of the fence, and δ(P) is a position accuracy deviation of the user, is a fence range elasticity coefficient, is an accuracy compensation coefficient, is a Haversine distance between the position of the user and the center point of the fence.

4. The method of claim 1, wherein, The S200, social relationship verification and visible spatiotemporal capsule screening, the specific content contained in the spatiotemporal capsule is: each spatiotemporal capsule contains a unique identifier, an associated scenic spot identifier, a creator identifier, a creation time, a visibility setting and a content block list; the visibility setting is divided into three types of private, friends and public, the private is: only visible to oneself; the friends is: visible to general friends, and the editing permission can be applied; the public is: visible to friends and friends of friends, but only when a general friend has edited, the permission of applying for editing is open to general friends; the content block list is composed of at least one content block, and each content block contains a unique identifier, a spatiotemporal capsule identifier, an editor identifier, a content type, content data, an editing time, a parent content block identifier and a soft deletion flag; The spatiotemporal capsule is also associated with a version history record, and each record contains a version number, a spatiotemporal capsule identifier, an editor identifier, an editing time and a version description.

5. The method of claim 1, wherein, The S200, social relationship verification and visible spatiotemporal capsule screening, the specific steps for verifying the social relationship between the current user and the associated user of each spatiotemporal capsule are: the application server extracts the associated user set of the current spatiotemporal capsule, which is composed of the spatiotemporal capsule creator identifier and the editor identifier of all non-soft-deleted content blocks in the content block list after deduplication processing, wherein soft deletion means not physically deleting the content block data; for each associated user in the set, the following operations are performed in turn: querying the user relationship database to obtain whether the two parties are two-way friends, and recording a two-way friend indication function; and counting the total interaction time between the two parties through the application internal chat, joint editing, like and comment in the past 90 days; Query the shielding relationship database to determine whether the associated user shields the current user, and record a shielding state indication function; count the number of negative interactions and the total number of interactions between the two parties in the past 90 days; the above parameters are substituted into the social weight quantification algorithm to obtain the social weight value of the current user and the associated user; after traversing all associated users in the set, the maximum value of the social weight value is taken as the social association evaluation value of the current user and the spatiotemporal capsule; according to the visibility setting and the social association evaluation value of the spatiotemporal capsule, the current user is determined whether to have the permission to view the spatiotemporal capsule through the spatiotemporal capsule visibility decision algorithm.

6. The method of claim 4, wherein the method further comprises: The S200, social relationship verification and visible space-time capsule screening, the calculation formula of the social weight quantification algorithm is: Wherein: is the social weight value between the current trigger user and the space-time capsule associated user, which is used to quantify the closeness of their social relationship, is the current trigger user, is the space-time capsule associated user, is a two-way friend indication function, 1=two-way friend, 0=non-two-way friend, is and the total interaction time in the last 90 days, is the maximum interaction time threshold set by the system, is a shielding state indication function, 1 represents shielding , 0 represents not shielding, is and the number of negative interactions in the last 90 days, is and the total number of interactions in the last 90 days, is the weight coefficient, which corresponds to the weight proportion of two-way friend relationship, interaction time, shielding state, and negative interaction respectively, and .

7. The method of claim 1, wherein the method further comprises: The S200, social relationship verification and visible space-time capsule screening, the calculation formula of the space-time capsule visibility decision algorithm is: Wherein: is the space-time capsule visibility decision result, 1 indicates that the current user has the right to view the space-time capsule, 0 indicates no right to view, is the space-time capsule to be judged, is the current trigger user, is the space-time capsule visibility setting, including publi=public, friend=friend visible and private=only self visible three types, is a single user in the space-time capsule associated user set, is the space-time capsule associated user set, which is composed of the space-time capsule creator identifier and the editor identifier of all non-soft deleted content blocks in the content block list after de-duplication processing, is the maximum value of the social weight of the current user and the associated user set, is the visibility weight threshold value, used to determine whether the friend type visibility space-time capsule is open to the current user for viewing permission.

8. The method of claim 1, wherein the method further comprises: The S400, collaborative editing and editing permission control, the editor supports four types of content type editing: text, picture, video and route; the text editor supports expression insertion, line break and undo / redo functions; the picture editor supports selecting pictures from the album or taking pictures with the camera, and provides cropping, rotating and filter functions; the video editor supports selecting videos from the album or recording videos with the camera, and provides editing and adding background music functions, and the video length is limited to 10 minutes; the route editor supports manual route drawing or GPX file import, and displays the route track on the map component; at the same time, after receiving the spatiotemporal capsule content for the first time, the content is cached locally and in the cloud.

9. The method of claim 1, wherein the method further comprises: In S400, during collaborative editing and editing permission control, when multiple users are editing concurrently, the version priority of each content block is evaluated using an editing version priority algorithm. The calculation formula for the editing version priority algorithm is as follows: ,in: This is the priority value of the content block version to be evaluated. The higher the priority, the more likely it is to be used as the baseline version for multi-user concurrent editing and merging of content. This is the version of the content block to be evaluated. It is a related time capsule. yes The effective data length, It is the maximum valid data length of the same type of content block within the time capsule. This is a content block ownership indicator function; 1 indicates... The editor is the creator of the time capsule, and 0 represents other editors. for Related content blocks from the previous version, for and Content similarity, This is the maximum similarity threshold, fixed at 1. for The editing time This represents the average editing time for similar content blocks within a time capsule. These are weighting coefficients, corresponding to the weighting percentages of effective data length of content blocks, editor identity, content similarity, and editing time, respectively. .

10. A system for triggering a co-editing space based on geographic location and social relationship, the system comprising: The system is suitable for the method for triggering a collaborative editing space based on geographical position and social relationship according to any one of claims 1-9, characterized in that the system comprises a user terminal, a geographical fence service, an application server, a database and a push service; The user terminal is an iOS or Android mobile App, supports GPS, Wi-Fi, Bluetooth positioning, supports Android Geofencing API and iOS Region Monitoring low-power consumption positioning mode, can report user position data, receive event notification and push notification, display a space-time capsule preview interface, send data request and editing request to the application server, provide an editor, support viewing space-time capsule version history and filtering specific time point history state; The geographical fence service: creates a circular or polygon-shaped geographical fence, configures entering, staying and leaving trigger conditions, can analyze user position data, judges whether the trigger conditions are met, and sends a trigger event containing a user unique identifier UID and a geographical fence identifier FID to the application server when the trigger conditions are met; The application server: receives the trigger event of the geographical fence service, queries the space-time capsule list from the database according to the FID, extracts an associated user set, calls the database to query user relationship and shielding state to determine space-time capsule visibility, sends a push request to the push service, receives the request of the user terminal and checks the authority, calls or updates the database data when the authority is available, returns an error when the authority is not available, and can handle concurrent editing conflicts; The database: stores user basic information, user bidirectional friend relationship data, user shielding state data and space-time capsule data; The push service: integrates Apple APNs and Google FCM push channels, receives the push request of the application server, and sends a notification containing space-time capsule information and a deep link to the user terminal of the specified UID.

Images