A method for realizing information synchronization of team travel of car friends

Abstract

This application relates to a method for synchronizing information during group travel among car enthusiasts. The method includes: constructing a team data structure based on a team creation command and sending a team invitation; creating a shared information space for the team based on team identifiers and location authorization information and entering initial data; generating unified navigation and custom navigation route planning data, determining spatiotemporal convergence points, and storing them in association; processing and classifying member voice stream data, responding to voice playback requests and adapting playback attributes; detecting member route deviations and classifying deviation states, obtaining relevant status data, responding to travel description editing commands and updating information, integrating various data to generate a status synchronization message and pushing it to all member terminals. This method enables comprehensive synchronization of navigation, voice, status, and travel descriptions during group travel among car enthusiasts, ensuring team collaboration and improving travel experience and safety.

Description

Technical Field

[0001] This invention belongs to the field of intelligent transportation and mobile Internet applications, and in particular relates to a method for synchronizing information on group travel among car owners. Background Technology

[0002] With the development of intelligent transportation and mobile Internet application technologies, fleet travel assistance technologies that combine instant messaging, navigation sharing and location services have emerged. This technology aims to integrate communication and guidance functions during the travel process through a single application platform, reducing the cumbersome operation of switching between multiple tools.

[0003] In traditional technologies, the synchronization of fleet travel information is usually handled in the following way: the initiator creates a team and sets a unified destination in the navigation application, members join by manually entering a verification code or searching for the team identifier, the whole team shares the same navigation route, and real-time voice intercom function is used for communication.

[0004] However, the current methods for synchronizing group travel information still have several shortcomings: the navigation mode is limited to a unified destination for all members, and cannot accommodate the custom navigation needs of individual members who temporarily change their itineraries, resulting in a disconnect between the location information of individual members and the overall information of the group; the voice function only supports basic real-time intercom, and lacks speaker identification, historical voice playback, and adaptive volume adjustment mechanisms for driving scenarios, which limits communication efficiency and information traceability; the group formation process relies on downloading and registering a separate application, which has a high operational threshold, and the synchronized information is mostly limited to basic data such as location and speed, without collaborative management of refined information such as member driving status and dynamic editing of travel instructions, resulting in insufficient completeness of perception of the entire group's travel status. Summary of the Invention

[0005] Therefore, it is necessary to provide a method for synchronizing information in car-riding group trips that can solve the pain points of navigation, location, and voice asynchrony and delayed route deviation warnings in car-riding group trips, achieve efficient information collaboration, adapt to driving scenarios, and be easy to operate.

[0006] Firstly, this application provides a method for synchronizing information on group travel among car enthusiasts, including:

[0007] S1. Based on the obtained team creation instruction, construct a team data structure containing car travel team information and team identifier. Based on the invited member terminal information in the team data structure, generate a team invitation request signal and send it to the invited member terminal. The team creation instruction includes travel description information, which includes the first navigation destination. The car travel team information includes information on all member terminals, which includes the team creation terminal and the invited member terminal.

[0008] S2. Based on the team identifier and the obtained location authorization information of all member terminals, create a team shared information space, record the location authorization information of all member terminals as the initial state data and initial location data of all member terminal data entries in the team shared information space, and store the first navigation destination in the team shared information space.

[0009] S3. Based on the initial location data and the first navigation destination in the team's shared information space, construct unified navigation path planning data; based on the temporary navigation change request sent by the invited member's terminal, perform destination parsing and path planning calculation on the temporary navigation change request to generate optional navigation path planning data; take the intersection node of the unified navigation path planning data and the optional navigation path planning data as the spatiotemporal convergence point, and store the unified navigation path planning data, the optional navigation path planning data and the spatiotemporal convergence point in association in the team's shared information space. The unified navigation path planning data and the optional navigation path planning data constitute a dual-track navigation operation mode.

[0010] S4. Receive voice stream data uploaded by all member terminals, perform identity identification and real-time location association annotation processing on the voice stream data, adjust the playback attributes of the voice stream data according to the current driving status parameters of all member terminals, obtain adapted voice stream data, and distribute the adapted voice stream data to all member terminals.

[0011] S5. Calculate the deviation of real-time location data and unified navigation route planning data of all member terminals. When the deviation of any member terminal exceeds the preset deviation threshold, generate a status synchronization event. Receive dynamic editing instructions for travel information sent by the team creation terminal. Based on the status synchronization event and the dynamic editing instructions, construct a status synchronization message, write the status synchronization message into the team's shared information space, and push it to all member terminals. The dynamic editing instructions include a description of the meeting point, the estimated departure time, waypoint information, and precautions.

[0012] The aforementioned method for synchronizing information for carpooling trips, derived through core technical features such as constructing a team data structure, creating a shared information space, establishing a dual-track navigation mode, and adapting voice interaction and route deviation detection and status synchronization to driving scenarios, effectively solves technical problems in the background technology, such as inconsistent navigation paths, asynchronous member locations, poor voice communication adaptability, untimely route deviation warnings, and inability to dynamically update travel instructions, achieving significant beneficial effects. It enables rapid team creation and invitation, achieves information collaboration among all members through a shared information space, balances unified planning with personalized needs for dual-track navigation, ensures driving safety through adaptive voice interaction, and reduces communication costs through real-time deviation detection and status synchronization. Overall, it improves the convenience, safety, and collaboration of carpooling trips, meeting the practical needs of carpooling trips. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying 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.

[0014] Figure 1 This is a schematic diagram illustrating the application environment of a method for synchronizing travel information among car enthusiasts provided by the present invention.

[0015] Figure 2 This is a flowchart illustrating a method for synchronizing travel information among car enthusiasts in a group, provided by the present invention.

[0016] Figure 3 This is a schematic diagram illustrating the process of generating unified navigation path planning data and self-selected navigation path planning data in one optional embodiment of the present invention; Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0018] This application provides a method for synchronizing travel information among car enthusiasts, which can be applied to, for example... Figure 1In the application environment shown, terminal 102 can communicate with server 101 via a network. A data storage system can store the data that server 101 needs to process. The data storage system can be integrated onto server 101 or located in the cloud or on other network servers. Terminal 102 can be used to initiate team creation commands, upload member location authorization information, send temporary navigation change requests and voice stream data, and receive navigation paths, adapted voice streams, and status synchronization messages pushed by server 101. Server 101 can, based on this method of synchronizing travel information for car enthusiasts, perform team data structure construction, create a shared information space for the team, plan dual-track navigation paths, annotate and adapt voice streams, and detect route deviations and process status synchronization based on the received data, and synchronously output navigation data, adapted voice streams, and status synchronization messages. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. Server 101 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0019] In one exemplary embodiment, such as Figure 2 As shown, a method for synchronizing travel information among car enthusiasts in a group is provided, and this method is applied to... Figure 1 Taking server 101 as an example, the explanation includes the following steps:

[0020] S1. Based on the acquired team creation instruction, construct a team data structure containing car travel team information and team identifier. Based on the invited member terminal information in the team data structure, generate a team invitation request signal and send it to the invited member terminal. The team creation instruction includes travel description information, which includes the first navigation destination. The car travel team information includes information on all member terminals, which includes the team creation terminal and the invited member terminals.

[0021] Specifically, the team creation command can refer to the command used to create a car travel team, which includes core information related to team formation and travel; the team data structure can refer to the structured carrier used to store data related to the car travel team; the team identifier can be used to distinguish different car travel teams, enabling precise association and management of car travel team data; the invited member terminal information can refer to the terminal information recorded in the team data structure that needs to be invited to join the car travel team, which can be used to send targeted invitation signals; the travel instructions information can refer to the travel-related instructions in the team creation command, which includes the first navigation destination, estimated departure time, meeting point description, waypoint information, estimated travel time, team meeting rules, and travel precautions; the first navigation destination can refer to the unified travel destination agreed upon by all team members; the car travel team information includes a summary of all member terminals and travel instructions, where all member terminals include the team creation terminal and the invited member terminals; the team invitation request signal includes the team identifier, team creation terminal information, and a summary of the travel instructions.

[0022] Optionally, server 101 can receive team creation instructions sent by the team creation terminal, parse the team creation instructions, extract travel instructions, team creation terminal information, and invited member terminal information from the team creation instructions, integrate the travel instructions, team creation terminal information, and invited member terminal information to generate car travel team information; server 101 can create a unique team identifier, associate the car travel team information with the team identifier, and construct a complete team data structure; server 101 can extract the identifier and communication address of the invited member terminal from the team data structure, and generate a standardized team invitation request signal based on the identifier and communication address of the invited member terminal; server 101 can send the team invitation request signal to each invited member terminal via the network.

[0023] S2. Based on the team identifier and the obtained location authorization information of all member terminals, create a team shared information space, record the location authorization information of all member terminals as the initial state data and initial location data of all member terminal data entries in the team shared information space, and store the first navigation destination in the team shared information space.

[0024] Specifically, location authorization information can refer to the permission information granted by all member terminals to server 101 to provide their own location data. Location authorization information includes location coordinate data, authorization status, and authorization timestamp. Team shared information space can refer to the exclusive data sharing area created by server 101 based on team identifier. Team shared information space can be used to centrally store and manage all data related to the car travel team. Initial status data can refer to the initial status information related to the location authorization of all member terminals. Initial status data includes location authorization status and authorization timestamp. Initial location data can refer to the initial location coordinates of all member terminals parsed from the location authorization information. All member terminal data entries can refer to the data storage unit established separately for each terminal in the team shared information space. All member terminal data entries can be used to classify and store the location and status and other related data of all member terminals.

[0025] Optionally, server 101 can obtain location authorization information sent by all member terminals, and server 101 can verify the authorization status of each terminal and filter out authorized member terminals; server 101 can initialize the data storage structure of the team shared information space based on the team identifier, and establish a data entry storage area indexed by the identifiers of all member terminals; server 101 can parse the location authorization information of authorized terminals, extract the location coordinate data of authorized terminals as initial location data, and extract the authorization status and authorization timestamp as initial status data; server 101 can write the initial location data and initial status data into the corresponding data entry of all member terminals for each terminal; server 101 can extract the first navigation destination from the travel instructions information, store the first navigation destination in the shared configuration area of ​​the team shared information space, and complete the creation of the team shared information space and the entry of initial data.

[0026] S3. Based on the initial location data and the first navigation destination in the team's shared information space, construct unified navigation path planning data; based on the temporary navigation change request sent by the invited member's terminal, perform destination parsing and path planning calculation on the temporary navigation change request to generate self-selected navigation path planning data; take the intersection node of the unified navigation path planning data and the self-selected navigation path planning data as the spatiotemporal convergence point, and associate and store the unified navigation path planning data, the self-selected navigation path planning data and the spatiotemporal convergence point in the team's shared information space. The unified navigation path planning data and the self-selected navigation path planning data constitute a dual-track navigation operation mode.

[0027] Specifically, a temporary navigation change request can refer to a request from an invited member terminal to change its own navigation destination. The temporary navigation change request includes a new navigation destination and related route preferences. The self-selected navigation route planning data can refer to the personalized travel route planned separately for the invited member terminal by the server 101 after parsing the temporary navigation change request. The spatiotemporal rendezvous point can be used to ensure that the invited member terminal that initiates the temporary navigation change and other terminals in the car travel team meet at the spatiotemporal rendezvous point to avoid the team from dispersing. The dual-track navigation operation mode can refer to the operation mode in which unified navigation route planning data and self-selected navigation route planning data exist in parallel and are interconnected.

[0028] Optionally, server 101 can read the initial location data and stored first navigation destination of all member terminals from the team's shared information space. Starting from each terminal's initial location data and ending at the first navigation destination, it generates multiple routes and integrates them to generate unified navigation path planning data, combining the route preferences in the travel instructions. Server 101 can receive temporary navigation change requests sent by invited member terminals, parse these requests, and extract the second navigation destination and path preference information from them. Server 101 can then use the real-time location of the invited member terminal as the starting point and the second navigation destination as the destination... Taking the destination as the endpoint, the server performs route planning calculations to generate custom navigation route planning data adapted to the needs of the invited member's terminal. The server 101 can segment the unified navigation route planning data and the custom navigation route planning data, perform spatial intersection detection, filter out all intersection points, and select the intersection point that the invited member's terminal first reaches when traveling along the custom navigation route as the spatiotemporal convergence point. The server 101 can associate and bind the unified navigation route planning data, the custom navigation route planning data, and the spatiotemporal convergence point, and store them in the navigation data area of ​​the team's shared information space to obtain a dual-track navigation operation mode for all member terminals to query and call.

[0029] Preferably, in the dual-track navigation mode, the caravan consists of 5 terminals, all traveling along the planned route to their destination. One terminal needs to exit the route to pick up a passenger and sends a temporary navigation change request. Server 101 can plan a separate pick-up route for this terminal, while the other 4 passengers continue along the original unified route. Server 101 can use a spatial intersection detection algorithm to calculate the earliest intersection point between the unified navigation path planning data and the self-selected navigation path planning data, determine the spatiotemporal convergence point, and synchronize it to all terminals. After picking up the passenger, the terminal can quickly rejoin the group based on the convergence point.

[0030] S4. Receive voice stream data uploaded by all member terminals, perform identity identification and real-time location association annotation processing on the voice stream data, adjust the playback attributes of the voice stream data according to the current driving status parameters of all member terminals, obtain adapted voice stream data, and distribute the adapted voice stream data to all member terminals.

[0031] Specifically, voice stream data can refer to real-time voice information acquired and uploaded to server 101 by all member terminals through voice acquisition devices; identity identifiers can refer to unique identification information bound to the terminal, which can correspond to the specific member's identity and distinguish the sender of the voice stream data; real-time location association annotation processing can refer to binding the sender's identity identifier of the voice stream data with the real-time location data at the time of voice stream data acquisition and annotating it in the metadata of the voice stream data; current driving status parameters can refer to the driving-related data collected and uploaded by all member terminals, used to determine the current driving scenario of all member terminals, including driving speed, acceleration, and driving road segment type; playback attributes can refer to the playback parameters of the voice stream data, including volume and playback rate; adapted voice stream data can refer to voice data adapted to the member's current driving scenario after identity identifier annotation, real-time location association, and playback attribute adjustment, which can ensure the safety and clarity of voice reception during driving.

[0032] Optionally, server 101 can receive voice stream data uploaded by all member terminals in real time, and record the collection timestamp of each voice stream data. Server 101 can extract member identifiers carried in the voice stream data, query the real-time location data of the terminal corresponding to the member identifier in the team's shared information space, associate the member identifier and the real-time location data as annotation information, and write it into the metadata header of the voice stream data to obtain standard voice stream data. Server 101 can obtain the current driving status parameters uploaded by all member terminals, and determine the driving status category of each terminal based on the driving speed and acceleration in the current driving status parameters. Server 101 can set different volume gain coefficients according to different driving status categories, with a higher volume gain coefficient for high-speed cruising, a medium volume gain coefficient for low-speed urban driving, and a lower volume gain coefficient for stationary driving. Server 101 can write the volume gain coefficient into the audio frame header of the standard voice stream data to obtain adapted voice stream data. Server 101 can distribute the processed adapted voice stream data to all member terminals via the network.

[0033] S5. Calculate the deviation of real-time location data and unified navigation route planning data of all member terminals. When the deviation of any member terminal exceeds the preset deviation threshold, generate a status synchronization event. Receive dynamic editing instructions for travel information sent by the team creation terminal. Based on the status synchronization event and the dynamic editing instructions, construct a status synchronization message, write the status synchronization message into the team's shared information space, and push it to all member terminals. The dynamic editing instructions include a description of the meeting point, the estimated departure time, waypoint information, and precautions.

[0034] Specifically, real-time location data refers to the current location coordinates collected and uploaded by all member terminals to the team's shared information space in real time. This data can be used to track the driving positions of all member terminals in real time. Deviation calculation refers to the server 101 calculating the deviation between the real-time location data of all member terminals and the corresponding planned route points in the unified navigation route planning data. This calculation can be used to determine whether a member has deviated from the preset route. The preset deviation threshold refers to the maximum deviation value allowed for a member terminal from the unified navigation route. This threshold can be dynamically adjusted based on road grade and driving speed. The status synchronization event refers to the event generated when a member terminal's deviation exceeds the preset deviation threshold. This event can be used to trigger status synchronization for all team members. Dynamic editing instructions are instructions used to modify travel instructions, including modifications to the meeting point description, estimated departure time, waypoint information, and precautions. The status synchronization message refers to a standardized data message that integrates status synchronization events and dynamic editing instructions. This message can be used to synchronize route deviation and travel instruction modification information to all member terminals.

[0035] Optionally, server 101 can read the real-time location data of all member terminals and the stored unified navigation path planning data from the team's shared information space in real time, and extract the planned path points in the unified navigation path planning data that match the current time of all member terminals; server 101 can calculate the Euclidean distance between the real-time location data of each member terminal and the planned path points, use the Euclidean distance as the deviation value, and compare the deviation value with a preset deviation threshold; when the deviation value of any member terminal exceeds the preset deviation threshold, server 101 can generate a status synchronization event, and mark the terminal corresponding to the status synchronization event as a deviating member terminal, and record the deviation. The server 101 can receive dynamic editing instructions for travel information sent by the team creation terminal, parse the modified content such as the meeting point description, estimated departure time, waypoint information, and precautions carried in the dynamic editing instructions, and update the travel information in the team's shared information space; the server 101 can integrate the status synchronization events and the modified content of the dynamic editing instructions to construct standardized status synchronization messages, clearly marking the event type, modified content, and related supplementary explanations; the server 101 can write the status synchronization messages into the status data area of ​​the team's shared information space and push the status synchronization messages to all member terminals through the network.

[0036] The aforementioned method for synchronizing travel information among car enthusiasts in a group involves a one-click creation command to build a standardized team data structure and send targeted team invitations, eliminating the need for cumbersome registration and manual joining. It pre-defines core travel information, enabling rapid team formation. A dedicated shared information space is built based on team identifiers, unifying the management of core data such as member locations and navigation, ensuring data synchronization across the entire team and providing a reliable data foundation for end-to-end collaboration. A dual-track navigation mode is constructed, balancing the team's unified itinerary with members' individual travel needs. A spatiotemporal convergence point ensures the team doesn't disperse, addressing the pain point of traditional navigation where one person's deviation leads to the entire team's disconnect. Simultaneously, it enables voice interaction adapted to driving scenarios and synchronizes all-dimensional travel status, improving driving communication safety, providing real-time warnings of route deviations and synchronized travel arrangement changes, comprehensively enhancing the convenience, safety, and collaboration of group travel.

[0037] In an exemplary embodiment, a team-shared information space is created based on the team identifier and the obtained location authorization information of all member terminals. The location authorization information of all member terminals is recorded as the initial state data and initial location data of all member terminal data entries in the team-shared information space, and the first navigation destination is stored in the team-shared information space, including:

[0038] S11. Based on the team identifier, initialize the data storage structure of the team's shared information space and establish a data entry storage area indexed by the identifiers of all member terminals.

[0039] Specifically, the data storage structure can refer to the standardized storage architecture that the server pre-sets for the shared information space of the team. The data storage structure can be used to standardize the storage format and storage path of member information, navigation data, and status data.

[0040] Optionally, the server can initialize the overall data storage structure of the team's shared information space based on the team identifier, and divide it into functional partitions such as member data area, navigation data area, status data area and shared configuration area; the server can extract the terminal identifiers of all members recorded in the team data structure, use the identifier of each terminal in all member terminals as a unique index, and create an independent data entry storage unit for all member terminal identifiers in the member data area, with each storage unit preset with initial position data, initial status data and other fields.

[0041] S12. Obtain the location authorization information of all member terminals, parse the location coordinate data in the location authorization information into initial location data, record the authorization status and timestamp of the location authorization information as initial status data, and write the initial location data and initial status data into the corresponding data entries of all member terminals.

[0042] Optionally, the server can obtain location authorization information uploaded by all member terminals, perform legality verification on each location authorization message, and remove invalid authorization information; the server can call a coordinate parsing algorithm to parse the location coordinate data in the verified location authorization information, convert the original coordinate format into a standardized coordinate format to obtain initial location data, and perform accuracy verification on the initial location data; the server can extract the authorization status and authorization timestamp from each location authorization message, associate the authorization status and authorization timestamp with records, and generate initial status data; the server can use the identifier of all member terminals as an index to find the data entry corresponding to each terminal in all member terminals, and write the initial location data and initial status data into the fields of the data entry respectively.

[0043] S13. Extract the first navigation destination from the travel instructions information and store the first navigation destination in the shared configuration area of ​​the team's shared information space.

[0044] Specifically, the shared configuration area can refer to the area in the shared information space of the team that stores the public configuration data of the car travel team. Storing the first navigation destination in the shared configuration area can realize the centralized management of the first navigation destination.

[0045] Optionally, the server can retrieve stored travel instructions, filter the travel instructions, and extract the first navigation destination from the travel instructions; the server can locate the shared configuration area of ​​the team's shared information space, call the data writing interface, and write the extracted first navigation destination into the shared configuration area.

[0046] In one exemplary embodiment, such as Figure 3 As shown, based on the initial location data and the first navigation destination in the team's shared information space, unified navigation path planning data is constructed; based on the temporary navigation change request sent by the invited member's terminal, destination parsing and path planning calculations are performed on the temporary navigation change request to generate self-selected navigation path planning data; the intersection node of the unified navigation path planning data and the self-selected navigation path planning data is used as the spatiotemporal convergence point, and the unified navigation path planning data, the self-selected navigation path planning data, and the spatiotemporal convergence point are associated and stored in the team's shared information space, including:

[0047] S21. Read the first navigation destination from the team's shared information space, take the initial location data of all members' terminals as the starting point and the first navigation destination as the ending point, and generate a first navigation route set as unified navigation path planning data.

[0048] Optionally, the server can locate the shared configuration area of ​​the team's shared information space and retrieve the stored first navigation destination; the server can read the initial position data corresponding to all member terminals, take the initial position data of all member terminals as the starting point and the first navigation destination as the ending point, call the path planning algorithm, and generate each navigation route from the starting point to the ending point; the server can integrate all the generated navigation routes to generate the first navigation route set.

[0049] S22. Receive a temporary navigation change request sent by an invited member terminal, parse the second navigation destination in the temporary navigation change request, and generate a second navigation route with the real-time location of the invited member terminal that sent the temporary navigation change request as the starting point and the second navigation destination as the ending point, as the self-selected navigation path planning data.

[0050] Specifically, the second navigation destination can refer to the new navigation endpoint specified in the temporary navigation change request, replacing the first navigation destination in the unified navigation path planning data.

[0051] Optionally, the server can receive a temporary navigation change request sent by an invited member terminal, parse the temporary navigation change request, and extract the second navigation destination from the temporary navigation change request; the server can obtain the real-time location data of the invited member terminal that sent the request, and use the real-time location data of the invited member terminal as the starting point and the extracted second navigation destination as the ending point to call a path planning algorithm to generate a second navigation route; the server can associate and store the generated second navigation route as self-selected navigation path planning data and the identifier of the invited member terminal that initiated the request.

[0052] Preferably, the calculation formula for the path planning algorithm can be:

[0053]

[0054] in, This represents the total length of the planned path; and These are the coordinates of two adjacent path points on the path; This represents the total number of waypoints in the planned path. The unified navigation path and the custom navigation path differ only in their starting and ending points; the calculation formulas for the path planning algorithms are completely identical.

[0055] S23. Divide each navigation route in the unified navigation path planning data into road segments to generate a first road segment sequence set; divide each navigation route in the self-selected navigation path planning data into road segments to generate a second road segment sequence set.

[0056] Specifically, road segmentation can refer to breaking down each navigation route into multiple continuous road segment units according to preset road segment division rules, with each road segment unit corresponding to a continuous driving path.

[0057] Optionally, the server can retrieve all navigation routes in the unified navigation route planning data, call the segmentation algorithm, and divide each navigation route into multiple continuous segment units according to the preset segment division rules; integrate all segment units to generate a first segment sequence set; the server can retrieve all navigation routes in the optional navigation route planning data, use the same segmentation algorithm and division rules to segment each navigation route into multiple segment units; the server can integrate these segment units to generate a second segment sequence set.

[0058] Preferably, the road segmentation rule can refer to using key road nodes such as highway interchanges, entrance and exit ramps, intersections, and route turning points on the navigation path as mandatory dividing points, and dividing continuous roads between two adjacent key nodes into an independent road segment unit; for long-distance continuous roads without key nodes, uniform division is performed according to a preset mileage that matches the road level; at the same time, division is performed at locations where the road driving direction, level, and speed limit standards change, and the path start point, end point, and preset waypoints are used as mandatory dividing nodes to ensure the uniformity of road attributes within the same road segment and improve the accuracy and efficiency of subsequent spatial intersection detection.

[0059] S24. Perform spatial intersection detection on the first road segment sequence set and the second road segment sequence set, filter out the road segment intersection points with the same geographical coordinates, select the intersection point that the invited member terminal that sent the temporary navigation change request first arrives at during the journey along the second navigation route from the road segment intersection points, and determine the first arrival intersection point as the spatiotemporal convergence point.

[0060] Specifically, spatial intersection detection can refer to comparing the geographical locations of all road segment units in the first road segment sequence set and the second road segment sequence set, and identifying the intersection points of road segment units whose geographical coordinates completely overlap, which are the road segment intersection points.

[0061] Optionally, the server can invoke a spatial intersection detection algorithm to compare all road segment units in the first and second road segment sequence sets one by one, detect whether there is overlap in the geographical coordinates between each road segment unit, and filter out all road segment intersections with the same geographical coordinates; the server can retrieve the second navigation route of the invited member terminal that sent the temporary navigation change request, and calculate the estimated time for the invited member terminal to reach each road segment intersection along the second navigation route by combining the real-time driving speed of the invited member terminal and the road segment information of the second navigation route; the server can sort the estimated arrival times of all road segment intersections, filter out the intersection with the earliest estimated arrival time, and determine the intersection with the earliest estimated arrival time as the spatiotemporal convergence point.

[0062] Preferably, the calculation formula for the spatial intersection detection algorithm can be:

[0063]

[0064] in, For road segment intersection parameters, when At that time, determine whether the two road segments intersect; and To unify the coordinates of the two endpoints of the navigation route; and The coordinates of the two endpoints of the selected navigation segment. These are the coordinates of the intersection of the road segments.

[0065] S25. Link and store the unified navigation path planning data, the self-selected navigation path planning data, and the spatiotemporal rendezvous point to the navigation data area of ​​the team's shared information space.

[0066] Optionally, the server can retrieve the navigation data area of ​​the team's shared information space, specifying the storage path and data format requirements for the navigation data area; the server can retrieve unified navigation path planning data, self-selected navigation path planning data, and related data of spatiotemporal rendezvous points, and perform format verification on the unified navigation path planning data, self-selected navigation path planning data, and spatiotemporal rendezvous points; the server can associate and bind the unified navigation path planning data, self-selected navigation path planning data, and spatiotemporal rendezvous points, marking the association relationship between the unified navigation path planning data, self-selected navigation path planning data, and spatiotemporal rendezvous points; the server can call the data writing interface to store the associated unified navigation path planning data, self-selected navigation path planning data, and spatiotemporal rendezvous points in the navigation data area of ​​the team's shared information space.

[0067] In an exemplary embodiment, the system receives voice stream data uploaded by all member terminals, performs identification and real-time location association annotation processing on the voice stream data, adjusts the playback attributes of the voice stream data according to the obtained current driving status parameters of all member terminals to obtain adapted voice stream data, and distributes the adapted voice stream data to all member terminals, including:

[0068] S31. Receive voice stream data uploaded by all member terminals, extract the sender member identifier and collection timestamp from the voice stream data, query the real-time location data of all member terminals at the corresponding time based on the collection timestamp, associate the sender member identifier and real-time location data as annotation information, and write the annotation information into the metadata header of the voice stream data to obtain annotated voice stream data.

[0069] Specifically, the sender member identifier can be an identifier that distinguishes different terminals; the collection timestamp can record the collection time of the voice stream data, and the collection timestamp can be used to trace the generation time of the voice stream data;

[0070] Optionally, the server can receive voice stream data uploaded by all member terminals in real time, perform legality verification on each voice stream data, and remove invalid voice data; the server can extract the sender member identifier and collection timestamp from each voice stream data; the server can query the real-time location data of all member terminals at the corresponding time based on the collection timestamp, associate the sender member identifier and real-time location data, and generate annotation information; the server can write the annotation information into the metadata header of the voice stream data to generate annotated voice stream data.

[0071] S32. Obtain the current driving status parameters of all member terminals, and determine the current driving status category based on the speed threshold and acceleration sensor data in the current driving status parameters. The current driving status category is used to characterize that all member terminals belong to one of the following states: high-speed cruise state, urban low-speed state, and stationary state.

[0072] Specifically, the speed threshold can refer to the critical speed value used to distinguish different driving states, and the speed threshold can be used to initially determine the driving speed; acceleration sensor data can refer to dynamic data reflecting speed changes during driving, and acceleration sensor data can be used to assist in determining the stability of the driving state; driving state categories include high-speed cruising state, urban low-speed state, and stationary state.

[0073] Optionally, the server can obtain the current driving status parameters uploaded by all member terminals in real time, verify the legality and integrity of the parameters, and remove invalid parameters. The server can then retrieve the preset speed classification standard and acceleration judgment threshold, combine the speed threshold in the current driving status parameters to initially divide the driving speed range, and then combine the acceleration sensor data to judge driving stability. When the speed threshold is higher than the preset high speed threshold and the acceleration sensor data tends to be stable, it is judged as a high-speed cruise state. When the speed threshold is in the preset low speed range and the acceleration sensor data fluctuates greatly, it is judged as a low-speed urban state. When the speed threshold is zero and the acceleration sensor data does not change significantly, it is judged as a stationary state.

[0074] S33. Set the volume gain coefficient according to the current driving state category. Set the volume gain coefficient corresponding to the high-speed cruise state to the first preset value, set the volume gain coefficient corresponding to the urban low-speed state to the second preset value, and set the volume gain coefficient corresponding to the stationary state to the third preset value. The first preset value is greater than the second preset value, and the second preset value is greater than the third preset value.

[0075] Specifically, the volume gain coefficient is a core parameter used to adjust the volume of the voice stream playback. The value of the volume gain coefficient determines the clarity of the voice playback, adapting to the auditory needs under different driving conditions. During high-speed cruising, passengers are focused on driving, and ambient noise is relatively stable and slightly high. Setting the volume gain coefficient to the first preset value ensures clear and intelligible voice. In low-speed urban driving, ambient noise fluctuates more, so setting the volume gain coefficient to the second preset value ensures clear voice while avoiding excessive volume that might interfere with driving. In a stationary state, with no driving noise, setting the volume gain coefficient to the third preset value meets basic communication needs while avoiding excessive volume that could cause interference. The first, second, and third preset values ​​are all fixed values ​​preset by the server and strictly follow the relationship of first preset value > second preset value > third preset value, ensuring precise matching of volume adjustment to driving conditions.

[0076] Preferably, the formula for calculating the volume gain coefficient can be:

[0077]

[0078] in, Volume gain factor; This is the status indicator for high-speed cruising. This is a status indicator for low-speed urban conditions. This is a status indicator for a static state. This is a preset coefficient for high-speed cruising. Preset coefficients for low-speed urban conditions; This is a preset coefficient for the static state.

[0079] Optionally, the server can retrieve preset volume gain coefficient standards, specify the exact values ​​of the first preset value, the second preset value, and the third preset value, and ensure that the values ​​meet the auditory requirements of different driving states; the server can retrieve the current driving state category of all member terminals that have been determined, and match the preset value corresponding to each member terminal according to the correspondence between the current driving state category and the volume gain coefficient.

[0080] S34. Write the volume gain coefficient into the audio frame header information of the labeled voice stream data to obtain the adapted voice stream data, and send the adapted voice stream data to all member terminals.

[0081] Specifically, the audio frame header information can indicate the core area in the audio stream data that stores audio-related configuration parameters.

[0082] Optionally, the server can retrieve the labeled audio stream data and volume gain coefficients, and through the audio editing interface, write the matched volume gain coefficients into the audio frame header information of the labeled audio stream data to generate adapted audio stream data; the server can then send the adapted audio stream data to all member terminals through the data distribution channel.

[0083] In one exemplary embodiment, generating adapted playback audio stream data includes:

[0084] S41. Obtain the estimated departure time and waypoint information from the travel instructions. Calculate the time intervals for each travel node of all member terminals based on the estimated departure time and waypoint information. According to the matching relationship between the collected timestamps and time intervals, classify and store the labeled voice stream data into the corresponding travel node partitions in the voice event database. The travel node partitions include the pre-departure partition, the mid-trip rest partition, and the near-destination partition.

[0085] Specifically, waypoint information refers to information related to pre-set stops and transfer points during the trip, including core details such as the location of the waypoint and the planned duration of the stop. The time intervals for trip nodes refer to the time ranges corresponding to different stages of the trip, defined by combining the estimated departure time, the distance between waypoints, the preset driving speed, and rest stop arrangements, clearly distinguishing three core trip nodes: before departure, rest stops, and near the destination. The voice event database refers to a standardized database used to store various voice-related data, divided into corresponding partitions according to trip nodes to achieve categorized storage of annotated voice stream data.

[0086] Optionally, the server can extract the estimated departure time and all waypoint information from the travel instructions and verify them. The server can combine the estimated travel speed of all member terminals, the distance between each waypoint, and the preset rest stop duration to calculate the time interval for each travel node. The pre-departure zone corresponds to the time period before the estimated departure time, including the team assembly and preparation for departure. The rest stop zone corresponds to the time period of stopping at waypoints and resting during the journey, including the member rest and replenishment of supplies. The destination proximity zone corresponds to the time period of approaching the first navigation destination and after arrival, including the member rendezvous and the end of the journey.

[0087] S42. Receive voice playback requests sent by all member terminals and record the terminal corresponding to the voice playback request as the requesting terminal. The voice playback request includes at least one of the following: target member identifier, target time period, and target trip node.

[0088] Specifically, a voice playback request can refer to a request to retrieve historical annotated voice stream data from a voice event database, and the requesting terminal is the terminal that initiates the voice playback request. The target member identifier can be used to specify the sender of the voice to be played back, the target time period can be used to limit the collection time range of the voice to be played back, and the target trip node can be used to limit the trip stage to which the voice to be played back belongs.

[0089] Optionally, the server can receive voice playback requests sent by all member terminals in real time, perform legality verification on each voice playback request, and eliminate invalid requests; the server can extract the core parameters in each voice playback request, identify at least one of the target member identifier, target time period, and target trip node included in the voice playback request, and record the terminal identifier that initiated the request, marking the terminal as the requesting terminal.

[0090] S43. Based on at least one of the target member identifier, target time period, and target trip node in the voice playback request, perform corresponding member-dimensional search, time-dimensional search, or trip node-dimensional search in the voice event database, filter out matching historical voice records, sort them according to time series, and generate a categorized voice playback list.

[0091] Specifically, member-based retrieval can refer to filtering all historical annotated voice stream data sent by a target member in the voice event database based on the target member identifier; time-based retrieval can refer to filtering all historical annotated voice stream data collected within a target time period; and trip node-based retrieval can refer to filtering all historical annotated voice stream data belonging to a target trip node. At least one parameter from the voice playback request must be considered during the retrieval process.

[0092] Optionally, the server can retrieve the core parameters extracted from the voice playback request to define the search dimensions. If the search dimension is a target member identifier, the server can perform a member-dimensional search to locate all historical annotated voice stream data corresponding to that target member identifier in the voice event database. If the search dimension is a target time period, the server can filter out voice data whose acquisition time falls within that target time period within the corresponding search range. If the search dimension is a target travel node, the server can filter out voice data belonging to the target travel node partition of that row. The search dimensions may include at least one, two, or all of the following parameters: target member identifier, target time period, and target travel node.

[0093] S44. Adjust the playback attributes of historical voice records in the classified voice playback list based on the current driving status parameters of the requesting terminal to obtain the adapted playback voice stream data, and send the adapted playback voice stream data to the requesting terminal.

[0094] Optionally, the server can determine the current driving state category of the requesting terminal based on the speed threshold and acceleration sensor data in the current driving state parameters, and match the corresponding volume gain coefficient. The server can retrieve all historical voice records in the categorized voice playback list, write the matched volume gain coefficient into the audio frame header information of each historical voice record, adjust the playback attributes of the historical voice records, generate adapted playback voice stream data, and the server can send the adapted playback voice stream data to the requesting terminal.

[0095] In an exemplary embodiment, deviations are calculated for the real-time location data and unified navigation path planning data of all member terminals. When the deviation of any member terminal exceeds a preset deviation threshold, a status synchronization event is generated. The system receives a dynamic editing instruction for travel information sent by the team creation terminal. Based on the status synchronization event and the dynamic editing instruction, a status synchronization message is constructed, written into the team's shared information space, and pushed to all member terminals, including:

[0096] S51. Calculate the deviation degree of the planned path points that match the current time in the real-time location data and unified navigation path planning data of all member terminals, and calculate the Euclidean distance between the real-time location data and the planned path points as the deviation degree value; compare the deviation degree value with the preset deviation threshold, and when the deviation degree value is greater than the preset deviation threshold, generate a state synchronization event and mark the terminal corresponding to the state synchronization event among all member terminals as the deviating member terminal.

[0097] Specifically, the preset deviation threshold can refer to the maximum allowable deviation distance preset by the server, which is used to determine whether a member terminal deviates from the planned route.

[0098] Optionally, the server can read real-time location data and unified navigation path planning data of all member terminals from the team's shared information space in real time, extract the planned path points in the unified navigation path planning data that match the current time of all member terminals, and ensure that the time dimension of the planned path points and the real-time location data are consistent; the server can call the Euclidean distance calculation algorithm to calculate the Euclidean distance between the real-time location data of all member terminals and the planned path points respectively, and use the Euclidean distance as the deviation value of the terminal; the server can retrieve a preset deviation threshold and compare the deviation value of all member terminals with the preset deviation threshold one by one; when the deviation value of a member terminal is greater than the preset deviation threshold, the server can immediately generate a status synchronization event, and mark the terminal as a deviating member terminal, and record the deviation time, deviation value and current real-time location data.

[0099] S52. Based on the state synchronization event, obtain the real-time speed data of the deviating member terminal within the preset time window, and classify the deviating member terminal into a static stationary state terminal or a deviating route state terminal according to the real-time speed data.

[0100] Specifically, a preset time window refers to a fixed time range used to collect speed data of deviating member terminals. This range is used to comprehensively capture speed changes after deviation and ensure the accuracy of status determination. Real-time speed data refers to the driving speed information collected and uploaded by the deviating member terminal in real time within the preset time window. A static stationary terminal refers to a deviating member terminal whose real-time speed data is continuously zero or below a preset static threshold within the preset time window, indicating that the terminal is in a stationary state. A deviating route terminal refers to a deviating member terminal whose real-time speed data is continuously above a preset static threshold within the preset time window, indicating that the terminal is still moving and has deviated from the unified navigation route.

[0101] Optionally, the server can extract the deviating member terminal identifier and deviating time recorded in the state synchronization event based on the state synchronization event, and determine the time range of the preset time window by extending the deviation time forward by a preset duration. The server can obtain all real-time speed data of the deviating member terminal within the preset time window in real time through the team shared information space. The server can retrieve a preset static threshold and compare the real-time speed data within the preset time window with the preset static threshold one by one. If all real-time speed data are zero or lower than the preset static threshold, and the duration reaches the preset standard, the server can classify the deviating member terminal as a static resident terminal. If the real-time speed data is continuously higher than the preset static threshold, the server can classify the deviating member terminal as a deviating route terminal.

[0102] S53. Obtain the static real-time location data and estimated recovery time uploaded by the static stationary terminal, and extract the location description information corresponding to the static real-time location data; obtain the deviation real-time location data of the deviation terminal, calculate the remaining path distance between the deviation real-time location data and the spatiotemporal rendezvous point, and calculate the estimated rendezvous time based on the remaining path distance and real-time speed data.

[0103] Specifically, static real-time location data refers to the current stationary coordinates collected and uploaded in real time by the statically stationary terminal; estimated resumption time refers to the planned restart time of the statically stationary terminal, which can be used to inform other members of the travel group when the statically stationary terminal will resume its journey; location description information is a textual description of the geographical location corresponding to the static real-time location data. Deviation from real-time location data refers to the current driving position coordinates collected and uploaded in real time by the deviating-from-route terminal; remaining path distance refers to the path length between the deviation from the real-time location data and the spatiotemporal convergence point, used to determine the distance of the terminal to the convergence point; estimated convergence time refers to the estimated time of arrival at the spatiotemporal convergence point calculated by combining the remaining path distance and the terminal's real-time speed data.

[0104] Optionally, based on the partitioning results, the server can separately locate statically stationary terminals and off-route terminals, establishing independent data association tables for these terminals. The server can acquire real-time static location data and estimated recovery time uploaded by statically stationary terminals. The server can call a geocoding interface to convert the static real-time location data into location description information. The server can also acquire real-time deviation location data and real-time speed data uploaded by off-route terminals. The server can retrieve the spatiotemporal rendezvous point coordinates stored in the team's shared information space, call a path distance calculation algorithm to calculate the remaining path distance between the deviation location data and the spatiotemporal rendezvous point, and combine this with the off-route terminal's real-time speed data to calculate the estimated rendezvous time by dividing the remaining path distance by the real-time speed.

[0105] S54. Receive the dynamic editing instruction sent by the team creation terminal for travel description information in the team shared information space, parse the modification fields and modification content carried in the dynamic editing instruction, update the travel description information stored in the team shared information space according to the modification fields and modification content, and generate a travel description update event.

[0106] Specifically, the "modify field" can refer to the specific content items in the travel description information that need to be modified, such as the estimated departure time, waypoint information, first navigation destination, and meeting point description; the "modify content" can refer to the new content corresponding to the "modify field," which is used to replace the original information.

[0107] Optionally, the server can receive dynamic editing instructions sent by the team creation terminal, perform legality verification on the dynamic editing instructions, and remove invalid instructions; the server can parse the data of the verified dynamic editing instructions, extract the modified fields and corresponding modified content in the dynamic editing instructions, and identify the specific information items and new content that need to be updated; then the server can locate the area in the team shared information space where the travel instructions information is stored, find the field position that needs to be updated corresponding to the extracted modified fields, replace the original content with the modified content, and generate a travel instructions update event.

[0108] S55. Integrate current driving status, location description information, estimated resumption time, estimated rendezvous time, and travel information update events to obtain a status synchronization message; push the status synchronization message to all member terminals.

[0109] Optionally, the server can first retrieve the current driving status category of all member terminals, the location description information and estimated resumption time of statically stationary terminals, and the estimated rendezvous time and travel instruction update event information of terminals that have deviated from the route. The server can then classify and integrate the current driving status category of all member terminals, the location description information and estimated resumption time of statically stationary terminals, and the estimated rendezvous time and travel instruction update event information of terminals that have deviated from the route according to a preset message format, and generate a standardized status synchronization message. The server can then push the status synchronization message to all member terminals.

[0110] In an exemplary embodiment, the formula for calculating the preset deviation threshold is:

[0111]

[0112] in, Based on the offset threshold; The velocity correlation coefficient; For real-time speed; The location sampling interval; This is a road grade correction factor; This represents the current road grade coefficient.

[0113] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0114] The above-described embodiments are merely illustrative of several implementation methods of the embodiments of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the embodiments of this application, and these modifications and improvements all fall within the protection scope of the embodiments of this application.

Claims

1. A method for synchronizing information on group travel among car enthusiasts, characterized in that, The method includes: S1. Based on the acquired team creation instruction, construct a team data structure containing car travel team information and team identifier. Based on the invited member terminal information in the team data structure, generate a team invitation request signal and send it to the invited member terminal. The team creation instruction includes travel description information, the travel description information includes a first navigation destination, the car travel team information includes information of all member terminals, and all member terminals include the team creation terminal and the invited member terminal. S2. Based on the team identifier and the obtained location authorization information of all member terminals, create a team shared information space, record the location authorization information of all member terminals as the initial state data and initial location data of the data entries of all member terminals in the team shared information space, and store the first navigation destination in the team shared information space. S3. Based on the initial location data and the first navigation destination in the team's shared information space, construct unified navigation path planning data; based on the temporary navigation change request sent by the invited member's terminal, perform destination parsing and path planning calculation on the temporary navigation change request to generate optional navigation path planning data; use the intersection node of the unified navigation path planning data and the optional navigation path planning data as a spatiotemporal convergence point, and associate and store the unified navigation path planning data, the optional navigation path planning data, and the spatiotemporal convergence point in the team's shared information space, wherein the unified navigation path planning data and the optional navigation path planning data constitute a dual-track navigation operation mode; S4. Receive the voice stream data uploaded by all member terminals, perform identity identification and real-time location association labeling on the voice stream data, adjust the playback attributes of the voice stream data according to the obtained current driving status parameters of all member terminals, obtain adapted voice stream data, and distribute the adapted voice stream data to all member terminals. S5. Calculate the deviation degree of the real-time location data of all member terminals and the unified navigation path planning data. When the deviation degree of any of the all member terminals exceeds a preset deviation threshold, generate a status synchronization event; receive the dynamic editing instruction for travel instructions sent by the team creation terminal, construct a status synchronization message based on the status synchronization event and the dynamic editing instruction, write the status synchronization message into the team shared information space, and push it to all member terminals; wherein, the dynamic editing instruction includes a description of the meeting point, the estimated departure time, the waypoint information, and precautions.

2. The method according to claim 1, characterized in that, Based on the team identifier and the obtained location authorization information of all member terminals, a team shared information space is created, the location authorization information of all member terminals is recorded as the initial state data and initial location data of the data entries of all member terminals in the team shared information space, and the first navigation destination is stored in the team shared information space, including: S11. Based on the team identifier, initialize the data storage structure of the team shared information space and establish a data entry storage area indexed by the identifiers of all member terminals; S12. Obtain the location authorization information of all member terminals, parse the location coordinate data in the location authorization information into the initial location data, record the authorization status and timestamp of the location authorization information as the initial status data, and write the initial location data and the initial status data into the data entries corresponding to all member terminals. S13. Extract the first navigation destination from the travel instructions information and store the first navigation destination in the shared configuration area of ​​the team shared information space.

3. The method according to claim 1, characterized in that, Based on the initial location data and the first navigation destination in the team's shared information space, unified navigation path planning data is constructed; based on the temporary navigation change request sent by the invited member's terminal, destination parsing and path planning calculations are performed on the temporary navigation change request to generate self-selected navigation path planning data; the intersection node of the unified navigation path planning data and the self-selected navigation path planning data is used as a spatiotemporal convergence point, and the unified navigation path planning data, the self-selected navigation path planning data, and the spatiotemporal convergence point are associated and stored in the team's shared information space, including: S21. Read the first navigation destination from the team's shared information space, and generate a first navigation route set with the initial location data of all members' terminals as the starting point and the first navigation destination as the ending point, as the unified navigation path planning data. S22. Receive the temporary navigation change request sent by the invited member terminal, parse the second navigation destination in the temporary navigation change request, and generate a second navigation route with the real-time location of the invited member terminal that sent the temporary navigation change request as the starting point and the second navigation destination as the ending point, as the self-selected navigation path planning data. S23. Divide each navigation route in the unified navigation path planning data into road segments to generate a first road segment sequence set; divide each navigation route in the self-selected navigation path planning data into road segments to generate a second road segment sequence set; S24. Perform spatial intersection detection on the first road segment sequence set and the second road segment sequence set, filter out road segment intersection points with the same geographical coordinates, select the intersection point that the invited member terminal that sent the temporary navigation change request first arrives at during its journey along the second navigation route from the road segment intersection points, and determine the first arrived intersection point as the spatiotemporal convergence point. S25. The unified navigation path planning data, the self-selected navigation path planning data, and the spatiotemporal rendezvous point are associated and stored in the navigation data area of ​​the team shared information space.

4. The method according to claim 1, characterized in that, The process of receiving voice stream data uploaded by all member terminals, performing identity identification and real-time location association annotation processing on the voice stream data, adjusting the playback attributes of the voice stream data according to the obtained current driving status parameters of all member terminals to obtain adapted voice stream data, and distributing the adapted voice stream data to all member terminals includes: S31. Receive the voice stream data uploaded by all member terminals, extract the sender member identifier and collection timestamp from the voice stream data, query the real-time location data of all member terminals at the corresponding time based on the collection timestamp, associate the sender member identifier and the real-time location data as annotation information, and write the annotation information into the metadata header of the voice stream data to obtain annotated voice stream data. S32. Obtain the current driving status parameters of all member terminals, and determine the current driving status category based on the speed threshold and acceleration sensor data in the current driving status parameters. The current driving status category is used to characterize that all member terminals belong to one of the following: high-speed cruise state, urban low-speed state, and stationary state. S33. Set the volume gain coefficient according to the current driving state category, set the volume gain coefficient corresponding to the high-speed cruise state to a first preset value, set the volume gain coefficient corresponding to the urban low-speed state to a second preset value, and set the volume gain coefficient corresponding to the stationary state to a third preset value, wherein the first preset value is greater than the second preset value, and the second preset value is greater than the third preset value. S34. Write the volume gain coefficient into the audio frame header information of the labeled voice stream data to obtain the adapted voice stream data, and send the adapted voice stream data to all member terminals.

5. The method according to claim 4, characterized in that, The method further includes: S41. Obtain the estimated departure time and waypoint information from the travel instructions information, calculate the time interval of each travel node of all member terminals based on the estimated departure time and waypoint information, and classify and store the labeled voice stream data into the corresponding travel node partition in the voice event database according to the matching relationship between the collection timestamp and the time interval. The travel node partition includes a pre-departure partition, a midway rest partition, and a destination near partition. S42. Receive the voice playback request sent by all member terminals, and record the terminal corresponding to the voice playback request as the requesting terminal. The voice playback request includes at least one of the following: target member identifier, target time period, and target itinerary node. S43. Based on at least one of the target member identifier, the target time period, and the target trip node in the voice playback request, perform corresponding member-dimensional search, time-dimensional search, or trip node-dimensional search in the voice event database, filter out matching historical voice records, sort them according to time sequence, and generate a categorized voice playback list. S44. Adjust the playback attributes of the historical voice records in the classified voice playback list based on the current driving status parameters of the requesting terminal to obtain adapted playback voice stream data, and send the adapted playback voice stream data to the requesting terminal.

6. The method according to claim 1, characterized in that, The deviation degree of the real-time location data of all member terminals and the unified navigation path planning data is calculated, and a status synchronization event is generated when the deviation degree of any of the all member terminals exceeds a preset deviation threshold. Receiving a dynamic editing instruction for travel information sent by the team creation terminal, constructing a status synchronization message based on the status synchronization event and the dynamic editing instruction, writing the status synchronization message into the team shared information space, and pushing it to all member terminals, including: S51. Calculate the deviation degree between the real-time location data of all member terminals and the planned path point in the unified navigation path planning data that matches the current time, and calculate the Euclidean distance between the real-time location data and the planned path point as the deviation degree value; compare the deviation degree value with the preset deviation threshold, and when the deviation degree value is greater than the preset deviation threshold, generate the state synchronization event and mark the terminal corresponding to the state synchronization event among all member terminals as a deviating member terminal; S52. Based on the state synchronization event, obtain the real-time speed data of the deviating member terminal within a preset time window, and classify the deviating member terminal into a static stationary state terminal or a deviating route state terminal according to the real-time speed data. S53. Obtain the static real-time location data and estimated recovery time uploaded by the static stationary terminal, and extract the location description information corresponding to the static real-time location data; obtain the deviation real-time location data of the deviation terminal, calculate the remaining path distance between the deviation real-time location data and the spatiotemporal rendezvous point, and calculate the estimated rendezvous time based on the remaining path distance and the real-time speed data; S54. Receive the dynamic editing instruction sent by the team creation terminal for the travel description information in the team shared information space, parse the modification field and modification content carried in the dynamic editing instruction, update the travel description information stored in the team shared information space according to the modification field and modification content, and generate a travel description update event; S55. Integrate the current driving status, the location description information, the estimated driving resumption time, the estimated rendezvous time, and the travel instructions update event to obtain a status synchronization message; push the status synchronization message to all member terminals.

7. The method according to claim 6, characterized in that, The formula for calculating the preset deviation threshold is: in, Based on the offset threshold; The velocity correlation coefficient; For real-time speed; The location sampling interval; This is a road grade correction factor; This represents the current road grade coefficient.

Images