Carpooling methods, devices, electronic equipment and storage media

Abstract

This application discloses a carpooling method, apparatus, electronic device, and storage medium, belonging to the field of Internet technology. The method includes: generating a trip receipt based on trip information uploaded by the driver; the trip information includes at least the origin and destination; sending the trip receipt to the driver; in response to a sharing instruction triggered by the driver, sharing an access identifier corresponding to the trip receipt to a target community group; the access identifier points to a carpooling details page containing the trip receipt; receiving an access request triggered by the passenger via the access identifier, and displaying the carpooling details page on the passenger's end; receiving a carpooling request submitted by the passenger on the carpooling details page, and pushing the carpooling request to the driver. This application embodiment realizes the function of drivers actively inviting passengers to carpool, and through the sharing mechanism of community groups, expands the dissemination range of carpooling information and improves the efficiency of travel matching.

Description

Technical Field

[0001] This application belongs to the field of Internet technology, and in particular relates to a carpooling method, device, electronic device and storage medium. Background Technology

[0002] With the rapid development of the social economy and the increasing diversification of people's travel needs, ride-sharing and carpooling have gradually become important choices for people's daily travel.

[0003] In related technologies, a passive matching model is mainly used to meet passengers' travel needs. After passengers post their travel needs on the platform, the platform system automatically matches drivers and passengers according to a certain algorithm, or drivers actively accept orders after browsing relevant orders. However, in some special scenarios, such as during large-scale events like sporting events, cultural performances, and music festivals, a large number of users often have intercity travel needs, and these travel needs are relatively concentrated in terms of departure time and destination. The passive matching model needs to process these needs one by one, resulting in low matching efficiency. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a carpooling method, device, electronic device, and storage medium to improve the efficiency of travel matching.

[0005] Firstly, this application provides a carpooling method, including: A trip receipt is generated based on the trip information uploaded by the driver; the trip information includes at least the origin and destination of the trip. The trip receipt is sent to the driver's end. In response to the driver's shared command, the access identifier corresponding to the trip receipt is shared to the target community group. The access identifier points to the carpooling details page that includes the trip receipt. Receive an access request triggered by the access identifier from the passenger's device, and display a carpooling details page on the passenger's device; The system receives carpooling requests submitted by passengers on the carpooling details page and pushes the carpooling requests to the driver's end.

[0006] The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0007] According to one embodiment of this application, the trip information further includes at least one of the following: travel time, number of seats available for sharing, vehicle information, and driver identity information; the access identifier is at least one of the following: a link, a QR code, and a mini-program card.

[0008] According to one embodiment of this application, the driver terminal provides a tag selection interface, which includes an activity tag option and / or a destination tag option; The method further includes: The system receives a target tag selected by the driver through the driver's terminal, associates the target tag with the trip information, and embeds it into the trip document.

[0009] In this embodiment, by setting a tag selection interface that includes activity tag options and / or destination tag options, it is possible to associate the target tag selected by the driver with trip information and embed it into the trip document, so that the trip document has targeted identification information. This enables the trip document to be accurately pushed to relevant user groups, thereby achieving precise dissemination of carpooling information, reducing invalid matches, and improving the matching success rate and dissemination effect.

[0010] According to one embodiment of this application, the step of sharing the access identifier corresponding to the trip receipt to the target community group in response to a sharing instruction triggered by the driver includes: Based on the target tags, at least one related community group is selected from the target community database; Recommend the at least one associated community group to the driver's device; In response to a sharing instruction triggered by the driver, the access identifier corresponding to the trip document is shared to the target community group selected by the driver from the at least one associated community group.

[0011] In this embodiment, by filtering related community groups from the target community library based on target tags and recommending them to the driver, and then having the driver select the target community group to complete the sharing of the trip document, community groups can be recommended in a targeted manner based on tags. The recommended related community groups have a higher matching degree with the carpooling trip, so that the trip document can be pushed to community groups where people with corresponding travel needs gather, further improving the accuracy of carpooling information dissemination, reducing invalid matches, and increasing the matching success rate.

[0012] According to one embodiment of this application, the method further includes: Determine the community group from which the access request originated; Passengers who initiate access requests to the carpooling details page from the same source community group will be associated with the carpooling details page; The driver's device displays identity tags indicating that the associated passengers belong to the same community group.

[0013] In this embodiment, by identifying the source community group of the access request, passengers who initiate access from the same source community group are associated and marked, and the identity tags of the corresponding community group are displayed on the driver's end. This allows the driver to identify whether the passengers applying for carpooling come from the same community group, making it easier for the driver to select carpoolers based on community association attributes. This transforms carpooling between strangers into carpooling between acquaintances based on shared interests, significantly reducing trust costs and safety concerns.

[0014] According to one embodiment of this application, the method further includes: The system obtains first target information of the passenger corresponding to the passenger terminal and second target information of the driver corresponding to the driver terminal. The first target information includes at least one of interest tags, evaluation parameters, and the number of people in the same community group as the driver. The second target information includes at least one of vehicle information, historical order records, positive review rate of members in the same group, and activity travel experience. Calculate the driver-passenger matching degree based on the first target information and the second target information; The first target information and the driver-passenger matching degree are pushed to the driver's end, and the second target information and the driver-passenger matching degree are pushed to the passenger's end.

[0015] In this embodiment, by calculating the driver-passenger matching degree and pushing the corresponding target information and matching degree results to both the driver and the passenger in both directions, multi-dimensional data references can be provided for both parties, making carpooling no longer a simple location matching, but a precise matching based on social relationships and interest similarity, thus improving the carpooling experience.

[0016] According to one embodiment of this application, the first target information includes interest tags and the community group to which the target belongs, and the method further includes: Interest matching degree is calculated based on each passenger's interest tags, and group overlap degree is calculated based on each passenger's community group; The mutual matching degree between passengers is determined based on the interest matching degree and the group overlap degree; The matching scores are then pushed to the passenger app and the driver app, respectively.

[0017] In this embodiment, by combining passenger interest tags with their respective community groups, the matching degree between passengers is calculated, providing passengers with relevant information about their fellow passengers. Based on the identity of group members and common interests, carpooling between strangers is transformed into carpooling between acquaintances based on common interests, reducing trust costs and safety concerns, enhancing carpooling willingness and travel safety, and also making it easier for drivers to prioritize matching passengers with high matching degrees, reducing communication friction during the trip.

[0018] According to one embodiment of this application, the method further includes: A matching rule setting interface is provided to the driver's end. The matching rule setting interface includes any of the following matching rules: receiving carpooling applications from members of the target community group, prioritizing the review of carpooling applications from members in the same community group, and unlimited carpooling applications. According to the target matching rules selected by the driver, the received carpooling requests are sorted and pushed to the driver's end.

[0019] In this embodiment, by providing a settings interface with multiple carpooling application matching rules to the driver, drivers can flexibly choose matching rules based on their own travel needs and preferences, reducing the operational cost of manually screening and judging a large number of carpooling applications and improving the efficiency of the driver's review and processing of carpooling applications.

[0020] According to one embodiment of this application, the method further includes: If the driver confirms at least one carpooling request, a trip coordination group is created, and the driver and the passenger corresponding to the confirmed carpooling request are added to the trip coordination group.

[0021] In this embodiment, by establishing a trip coordination group and adding the driver and corresponding passenger to the group, a trip communication and collaboration channel is built for carpooling participants, reducing trip communication costs and errors, and forming a carpooling ecosystem based on social circles, thereby enhancing user stickiness and the platform's differentiated competitiveness.

[0022] According to one embodiment of this application, the method further includes: A pricing mode selection interface is provided to the driver's terminal; the pricing mode selection interface includes multiple pricing modes; Generate corresponding price parameters based on the target pricing model selected by the driver; The price parameters are embedded into the trip document.

[0023] In this embodiment, by providing a pricing mode selection interface to the driver, the driver can independently select the target pricing mode and generate corresponding price parameters to be embedded in the trip document. This allows the driver to flexibly set carpooling prices based on actual conditions such as trip cost, number of carpooling seats, and travel scenario, adapting to pricing needs under different carpooling scenarios. Furthermore, by embedding the price parameters in advance into the trip document, passengers can know the carpooling price information when they visit the carpooling details page, enhancing price transparency and improving user trust and decision-making efficiency.

[0024] According to one embodiment of this application, the method further includes: Collect access data from the aforementioned itinerary documents; A demand popularity score is generated based on the access data; Based on the demand popularity score, price adjustment suggestions are pushed to the driver's end.

[0025] In this embodiment, by collecting access data from trip documents and generating a demand popularity score based on the data, and then pushing price adjustment suggestions to the driver based on the demand popularity score, drivers can keep track of the market demand for the current carpooling trip in real time. This allows drivers to flexibly adjust carpooling prices based on demand popularity, achieving dynamic adaptation between carpooling pricing and market demand, and further optimizing the allocation efficiency of carpooling resources.

[0026] According to one embodiment of this application, the method further includes: Receive the price negotiation request submitted by the passenger based on the price parameters; The price negotiation request is pushed to the driver's terminal.

[0027] In this embodiment, by supporting passengers to submit price negotiation requests based on price parameters in the trip receipt and simultaneously pushing the price negotiation request to the driver, passengers can initiate reasonable price negotiations based on their own travel needs and price expectations. Drivers can then decide whether to accept the price negotiation based on their own trip costs, seat availability, and other factors, thus adapting to the price demands of different drivers and passengers and reducing communication costs in the price negotiation process.

[0028] According to one embodiment of this application, the method further includes: Record the sharing statistics of the trip documents; the sharing statistics include at least one of the following: number of shares, number of clicks, and carpooling application conversion rate; A sharing effect analysis report is generated based on the sharing statistics, and the sharing effect analysis report is pushed to the driver's terminal.

[0029] In this embodiment, by recording the sharing statistics of trip receipts and generating a sharing effect analysis report based on these statistics and pushing it to the driver's end, the driver can understand the dissemination and conversion effect of their own carpooling trip receipts, enabling the driver to optimize the sharing strategy of subsequent carpooling trips in a targeted manner, and improve the accuracy and conversion efficiency of subsequent carpooling information sharing.

[0030] According to one embodiment of this application, the method further includes: An invitation management interface is provided to the driver's end; the invitation management interface displays information of candidate passengers accessed through the trip document; In response to the invitation operation triggered by the driver on the invitation management interface, an invitation message is sent to the passenger terminal corresponding to the candidate passenger selected by the driver.

[0031] In this embodiment, by providing the driver with an invitation management interface that displays information on candidate passengers who have accessed the trip receipt, the driver can send invitation information to the passenger terminal of the selected candidate passenger after triggering the invitation operation. This allows the driver to independently select potential passengers and initiate invitations based on the relevant information of the candidate passengers, without having to passively wait for passengers to submit carpooling requests. This allows the driver to better control the carpooling process and improve the final matching success rate.

[0032] Secondly, this application provides a carpooling method, including: In response to driver actions, the system sends trip information to the server; the trip information includes at least the origin and destination of the trip. Display the itinerary document generated by the server based on the itinerary information; In response to the sharing instruction triggered by the driver, the access identifier corresponding to the trip receipt is shared to the target community group; the access identifier points to the carpooling details page containing the trip receipt; Receive carpooling requests; the carpooling request is submitted on the carpooling details page after the passenger triggers an access request through the access identifier.

[0033] The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0034] Thirdly, this application provides a carpooling method, the method comprising: Receive and display an access identifier for the trip document; the access identifier points to a carpooling details page containing the trip document; In response to an access request triggered by the passenger through the access identifier, the carpooling details page is displayed; In response to a passenger's action, a carpooling request is submitted to the server, which then pushes the carpooling request to the driver's end.

[0035] The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0036] Fourthly, this application provides a carpooling device, which includes: The generation module is used to generate a trip document based on the trip information uploaded by the driver; the trip information includes at least the origin and destination of the trip; the trip document carries an access identifier pointing to the carpooling details page; The sending module is used to send the trip receipt to the driver's end, and in response to the sharing instruction triggered by the driver, to share the access identifier corresponding to the trip receipt to the target community group; the access identifier points to the carpooling details page that includes the trip receipt; The receiving module is used to receive the access request triggered by the access identifier of the trip document on the passenger's end, and display the carpooling details page on the passenger's end; The push module is used to receive carpooling requests submitted by passengers on the carpooling details page and push the carpooling requests to the driver's end.

[0037] The carpooling device provided in this application embodiment supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to be quickly spread to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0038] Fifthly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described carpooling method.

[0039] Sixthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described carpooling method.

[0040] Seventhly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described carpooling method.

[0041] The above-described one or more technical solutions in the embodiments of this application have at least the following technical effects: The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0042] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0043] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1 This is one of the flowcharts illustrating the carpooling method provided in the embodiments of this application; Figure 2 This is one of the schematic diagrams illustrating the scenario examples provided in the embodiments of this application; Figure 3 This is a second schematic diagram of a scenario example provided in the embodiments of this application; Figure 4 This is a second schematic flowchart of the carpooling method provided in the embodiments of this application; Figure 5 This is the third flowchart illustrating the carpooling method provided in the embodiments of this application; Figure 6 This is a schematic diagram of the carpooling device provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0046] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0047] The carpooling method, apparatus, electronic device, and storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0048] The carpooling method can be applied to the terminal, and can be executed by the hardware or software in the terminal.

[0049] The terminal includes, but is not limited to, portable communication devices such as mobile phones or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that, in some embodiments, the terminal may not be a portable communication device, but rather a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0050] The following embodiments describe a terminal including a display and a touch-sensitive surface. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and joystick.

[0051] The carpooling method provided in this application can be executed by an electronic device or a functional module or entity within an electronic device that can implement the method. The electronic device mentioned in this application can be a server, which can be a backend server within a carpooling platform capable of data transmission, data processing, and other functions. The carpooling method provided in this application will be described below using a server as an example of the executing entity.

[0052] like Figure 1 As shown, the carpooling method includes steps 110, 120, 130, and 140.

[0053] Step 110: Generate a trip document based on the trip information uploaded by the driver; the trip information should include at least the origin and destination of the trip.

[0054] In this embodiment, the trip information is a set of relevant information representing the driver's planned trip, which is actively uploaded by the driver providing the carpooling service through the driver's terminal of the carpooling platform. The trip information includes at least the origin and destination of the trip.

[0055] The starting point of the trip is the initial geographical location where the driver plans to initiate the carpooling trip. The initial geographical location can be the driver's current real-time location, a non-real-time location that the driver has set in advance based on his own travel plan, or a location around the starting point of the driver's trip that is convenient for passengers to pick up.

[0056] The destination is the driver's planned target geographical location for completing this carpooling trip; that is, the driver's final destination for this trip. The origin and destination can be represented by identifiable geographical markers such as geographic coordinates, address names, landmarks, and specific house numbers.

[0057] In addition to the origin and destination, trip information can also include the driver's planned travel time, vehicle information, driver identity information, estimated carpooling fare, and route information, depending on the actual carpooling service needs.

[0058] The driver's app is the user terminal developed by the carpooling platform for drivers. It can be a mobile app, mini-program, or webpage. Drivers can manually fill in and select trip information, or automatically obtain and upload it via location services, through the app's interface. After collecting and verifying the trip information, the driver's app sends it to the carpooling platform's server. Upon receiving the valid trip information from the driver's app, the server generates a corresponding trip document according to preset document generation rules. The trip document can be structured information about the trip, clearly presenting its content.

[0059] Step 120: Send the trip receipt to the driver's end. In response to the driver's sharing command, share the access identifier corresponding to the trip receipt to the target community group; the access identifier points to the carpooling details page containing the trip receipt.

[0060] In this embodiment, after generating the trip receipt, the server pushes it to the corresponding driver's terminal that initiated the trip information upload. Upon receiving the trip receipt, the driver's terminal displays it visually on its interactive interface, allowing the driver to view the complete information. The driver's terminal includes a sharing function entry for the trip receipt. After confirming the trip receipt information is correct, the driver can trigger a sharing command by clicking the share button or long-pressing the trip receipt. The server receives and responds to the sharing command triggered by the driver's terminal, executing the trip receipt sharing operation.

[0061] Specifically, the server can generate an access identifier corresponding to the trip receipt. This access identifier is a unique identifier assigned by the server, and can be, for example, a QR code, a link address, a mini-program card, or a numerical code. The access identifier forms a unique association with the corresponding carpooling details page, enabling passengers to access and navigate to the carpooling details page for viewing detailed information, including the trip receipt.

[0062] The trip itinerary is shared with target community groups. These community groups are online communication groups with specific community attributes, determined based on dimensions such as geographical location, residential area, and social connections. Examples include WeChat groups, QQ groups, or online communication groups on other social media platforms. These community groups could be concert groups, event groups, neighborhood groups, office building colleague groups, or industrial park communication groups. Users within these community groups share similar travel needs or social connections, which can increase the success rate of carpooling matching.

[0063] The target community group can be a community group specified by the driver or a community group recommended by the server. When responding to the sharing command, the server can connect with the social platform through the interface between the carpooling platform and the social platform, and send the trip receipt with access identifier in the form of pictures, links, cards, etc. to the target community group, so that passengers in the target community group can obtain the trip receipt information.

[0064] Step 130: Receive the access request triggered by the passenger's access identifier through the trip document, and display the carpooling details page on the passenger's end.

[0065] In this embodiment, the passenger terminal is an operating terminal developed by the ride-sharing platform for passenger users. The passenger terminal can be a mobile app, mini-program, webpage, etc. After viewing the shared trip receipt, passengers within the target community group can trigger an access request by performing a specified operation on the access identifier in the trip receipt, such as scanning the QR code in the trip receipt, clicking the corresponding link address in the trip receipt, or entering the numerical code of the trip receipt in the passenger terminal. The access request may include information such as the passenger terminal identifier and the access identifier. The server can match the corresponding ride-sharing details page using the access identifier.

[0066] The carpooling details page is an information display page configured by the carpooling platform for carpooling trips. It displays information related to the trip details, such as detailed trip information, and may also include an entry point for carpooling application. After receiving an access request triggered by a passenger, the server verifies the access identifier. If the verification is successful, the corresponding carpooling details page data is pushed to the passenger's client. Upon receiving the data, the passenger's client displays the carpooling details page on the interactive interface. On this page, passengers can view detailed carpooling information, such as the driver's trip origin, destination, planned travel time, available passengers, carpooling fare, and vehicle information.

[0067] Step 140: Receive the carpooling request submitted by the passenger on the carpooling details page and push the carpooling request to the driver's end.

[0068] In this embodiment, the carpooling details page includes a carpooling application entry point. After viewing the trip information on the carpooling details page, if a passenger's travel needs match the carpooling trip, they can submit a carpooling application by clicking the application button and filling in passenger information. The carpooling application includes at least the passenger's identification and travel need confirmation information. It can also include, based on actual needs, the passenger's contact information, the specific pick-up and drop-off locations, and the number of passengers. After submitting the carpooling application, the passenger's app can send the application to the server.

[0069] The server receives carpooling requests submitted by passengers on the carpooling details page, parses the information in the requests, and pushes them to the driver's app according to preset push rules. Upon receiving the carpooling request from the server, the driver can view it on the interactive interface. Drivers can view the detailed information of the carpooling request and, based on their own trip plans, the number of passengers they can carry, and other practical considerations, accept, reject, or negotiate the carpooling request.

[0070] The carpooling method provided in this application supports drivers in generating trip documents with a carpooling details page access identifier based on their own trip information. Drivers can also actively trigger a sharing command to push the trip document to the target community group, enabling drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to potential passengers with concentrated travel needs, such as event participants. This significantly shortens the dissemination chain of carpooling information and the demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform; they can directly submit an application on the carpooling details page to complete the carpooling request, simplifying the passenger's operation process and improving the efficiency of travel matching.

[0071] In some embodiments, the driver's end provides a tag selection interface, which includes active tag options and / or destination tag options; The method also includes: The system receives the target tag selected by the driver through the driver's terminal, associates the target tag with the trip information, and embeds it into the trip document.

[0072] In this embodiment, the carpooling platform has developed and configured a tag selection interface on the driver's end. This interface can be displayed synchronously after the driver initiates the upload of trip information, or it can be displayed as an optional function entry point during the editing stage before trip document generation. The tag selection interface includes multiple tag options, including at least one of activity tag options and destination tag options, allowing drivers to select tags.

[0073] The activity tag option is a scenario-based tag set based on the driver's purpose for this carpooling trip. The tags in the activity tag option can cover various offline activities and specific travel scenarios, such as sports events, cultural and entertainment performances, music festivals, exhibitions, scenic spots, shopping districts, campus activities, etc. Drivers can select the corresponding tags from the activity tag option according to their actual purpose for initiating the carpooling trip, which is used to indicate the travel scenario attribute of this carpooling trip.

[0074] The destination tag option is a tag set based on the driver's destination for this carpooling trip. The destination tag options can be divided into common urban travel destination types, such as transportation hubs, commercial centers, cultural and tourist attractions, industrial parks, residential areas, medical institutions, and educational institutions. Drivers can select the corresponding tag from the destination tag options according to the attributes of their own travel destination.

[0075] In this embodiment, the server can receive target tags selected by the driver through the tag selection interface on the driver's end. The target tag can be a single tag or multiple tags. After receiving the target tag, the server associates the target tag with the trip information uploaded by the driver according to preset association rules, and integrates the target tag into the structured data of the trip document according to preset embedding rules.

[0076] Once the target tag is embedded in the trip document, the tag information will be displayed along with the trip document when it is shared to the target community group. Passengers in the target community group can identify the characteristics of the carpooling trip through the tag and determine whether the carpooling trip matches their travel needs without having to check the trip details one by one, thereby improving the efficiency of passengers in filtering carpooling information.

[0077] In this embodiment, by setting a tag selection interface that includes activity tag options and / or destination tag options, it is possible to associate the target tag selected by the driver with trip information and embed it into the trip document, so that the trip document has targeted identification information. This enables the trip document to be accurately pushed to relevant user groups, thereby achieving precise dissemination of carpooling information, reducing invalid matches, and improving the matching success rate and dissemination effect.

[0078] In some embodiments, in response to a sharing instruction triggered by the driver, the access identifier corresponding to the trip receipt is shared to a target community group, including: Filter at least one related community group from the target community database based on the target tags; Recommend at least one relevant community group to the driver's app; In response to a sharing command triggered by the driver, the access identifier corresponding to the trip document is shared to the target community group selected by the driver from at least one associated community group.

[0079] In this embodiment, the target community library is a collection of online community resources maintained by the carpooling platform. The target community library includes information on various community groups with community attributes and sets corresponding tags for each community group. For example, sports event-related interest groups are labeled with the activity tag "sports event", high-speed rail station surrounding community groups are labeled with the destination tag "transportation hub", and commercial center surrounding office building groups are labeled with the destination tag "commercial center".

[0080] In this embodiment, after receiving the trip document sharing instruction triggered by the driver, or before, the server extracts the target tags that are associated with the current trip information and have been embedded in the trip document. Then, the server matches the target tags with the tags of each community group in the target community library. According to the preset filtering rules, at least one related community group is selected from the target community library. For example, if the driver selects the target tags "music festival" (event tag) and "cultural and tourism scenic spot" (destination tag), the server will select interest activity groups, scenic spot surrounding community groups, and young people's communication groups with tags related to "music festival" and "cultural and tourism scenic spot" as related community groups from the target community library. The server will organize the related community groups into a group recommendation list and push the group recommendation list to the driver.

[0081] After receiving the group recommendation list pushed to the driver's app, the driver can view it visually on the interactive interface. This can include the names of the associated community groups, group attributes, member size, and match rate with the target tags. Drivers can select one or more community groups from the recommendation list as the target groups for sharing their trip receipts.

[0082] In this embodiment, by filtering related community groups from the target community library based on target tags and recommending them to the driver, and then having the driver select the target community group to complete the sharing of the trip document, community groups can be recommended in a targeted manner based on tags. The recommended related community groups have a higher matching degree with the carpooling trip, so that the trip document can be pushed to community groups where people with corresponding travel needs gather, further improving the accuracy of carpooling information dissemination, reducing invalid matches, and increasing the matching success rate.

[0083] In some embodiments, the method further includes: Identify the community group from which the access request originated; Passengers who initiate access requests to the carpooling details page from the same source community group will be associated with the carpooling details page; The driver's app displays identity tags indicating that the associated passengers belong to the same community group.

[0084] To reduce the trust costs between parties in carpooling services and alleviate safety concerns for drivers and passengers, this embodiment can transform stranger carpooling scenarios into semi-acquaintance carpooling scenarios based on community connections.

[0085] Specifically, the server can pre-identify the sharing links of itinerary documents for each target community group, assigning a source identifier to each community group. This source identifier can be letters, numbers, a combination of letters and numbers, or the name of the community group. When itinerary documents are shared to a target community group, the access identifier of the itinerary document is bound to the source identifier of the target community group. When a passenger triggers an access request through itinerary documents within a target community group, the access request carries the bound source identifier. By parsing the source identifier in the access request, the server can determine the source community group of the access request. The server can also anonymize the original information of the source community group, retaining distinctive features that do not pose a risk of privacy leakage. For example, the original group name "XX City 2026 XX Concert Fan Exchange Group" can be anonymized to "From XX Concert Group," and "XX Community Phase III Owners Exchange Group" can be anonymized to "From XX Community Group."

[0086] After identifying the community group from which the access request originated, the server establishes a separate passenger access information management ledger for the carpooling details page of a single carpooling trip. This ledger records the identity of each passenger initiating the access request, including, for example, the passenger's identifier, the anonymized information of the source community group, and the access time. For passengers with consistent source community group information in the ledger, a pre-defined association tag can be used to indicate that these passengers all obtained carpooling information and accessed the carpooling details page through the same community group.

[0087] When a passenger submits a carpooling request on the carpooling details page and the server pushes it to the driver's end, the server will synchronize the passenger's corresponding association tag information to the driver's end. After receiving the carpooling request, the driver's end will display an identity tag representing the community identity of the associated passenger on the carpooling request display interface, such as "Member of the same group", "From XX concert group", "From XX community group", etc.

[0088] In this embodiment, by identifying the source community group of the access request, passengers who initiate access from the same source community group are associated and marked, and the identity tags of the corresponding community group are displayed on the driver's end. This allows the driver to identify whether the passengers applying for carpooling come from the same community group, making it easier for the driver to select carpoolers based on community association attributes. This transforms carpooling between strangers into carpooling between acquaintances based on shared interests, significantly reducing trust costs and safety concerns.

[0089] In some embodiments, the method further includes: Obtain first target information of passengers corresponding to the passenger terminal and second target information of drivers corresponding to the driver terminal; the first target information includes at least one of interest tags, evaluation parameters, and the number of people in the same community group as the driver; the second target information includes at least one of vehicle information, historical order records, positive review rate of members in the same group, and activity travel experience. Calculate the driver-passenger matching degree based on the first target information and the second target information; The first target information and driver-passenger matching score are pushed to the driver's end, and the second target information and driver-passenger matching score are pushed to the passenger's end.

[0090] In this embodiment, passenger first target information corresponding to the passenger terminal and driver second target information corresponding to the driver terminal can be collected respectively.

[0091] The primary target information is a set of information characterizing a passenger's carpooling attributes, social characteristics, and historical behavior, including at least one of the following: interest tags, evaluation parameters, and the number of times the passenger shares the same community groups as the driver. Interest tags are generated based on the passenger's platform usage behavior and can be personalized tags automatically assigned by the server by analyzing data such as tags from the passenger's historical carpooling trips, carpooling detail pages visited, and community group attributes joined. For example, interest tags could be rock music, sports events, family outings, or shopping districts. Evaluation parameters are historical carpooling behavior evaluation data for the passenger, including indicators such as driver ratings of the passenger, punctuality rate, and compliance with ride-sharing rules, reflecting the passenger's historical carpooling performance. The number of times the passenger shares the same community groups as the driver represents the overlap in social communities between the passenger and the driver for this carpooling trip.

[0092] The second target information is a set of information characterizing a driver's carpooling service capabilities, vehicle configuration, and historical service performance, including at least one of the following: vehicle information, historical order records, positive feedback rate from group members, and event travel experience. Vehicle information may include vehicle type, vehicle compliance qualifications, and safety features; historical order records are the driver's carpooling service history data, including historical order volume, trip completion rate, order cancellation rate, and average pick-up time; positive feedback from group members is the driver's evaluation data regarding carpooling services provided to passengers within the community group; and event travel experience is a representation of the driver's scenario-based carpooling service capabilities, such as experience traveling to music festivals, connecting with sporting events, or carpooling for sightseeing.

[0093] In this embodiment, the server can integrate various dimensions of the first and second target information to calculate the driver-passenger matching degree and output the result in the form of a score or star rating. Specifically, it can calculate the interest tag similarity by matching the passenger's interest tags with the driver's trip target tags and historical service activity travel experience tags, and calculating the proportion of identical or highly related tags to the total number of tags to obtain an interest tag similarity score. It can also calculate the group overlap score by using the number of the passenger and driver in the same community group as the numerator and the total number of community groups joined by both parties as the denominator to calculate the group overlap ratio, and then converting the ratio into a standardized score using a preset algorithm. Furthermore, it can calculate the historical behavior score by integrating the passenger's evaluation parameters with the driver's historical order records and positive feedback rates from members of the same group, and then taking the combined score as the historical behavior score. The server can then perform a weighted sum of the scores for each dimension according to preset weight coefficients to obtain the driver-passenger matching degree.

[0094] The server can push the passenger's primary target information and the calculated driver-passenger matching degree to the driver's end of the corresponding carpooling trip. After receiving the information, the driver's end can visualize the passenger's primary target information and display the driver-passenger matching degree in the carpooling application display interface and passenger information details interface. The driver can use this information to comprehensively judge the compatibility between the passenger and himself and make a more reasonable decision to accept, reject or negotiate the carpooling application.

[0095] The server can also push the driver's second target information and the calculated driver-passenger matching degree to the passenger's app after submitting the carpooling application. After receiving the information, the passenger's app can visualize the second target information and display the driver-passenger matching degree on the carpooling application progress interface and the driver information details interface. Passengers can use this information to understand the driver's service capabilities, vehicle conditions, suitability, and other information to determine whether the driver meets their carpooling needs.

[0096] In this embodiment, by calculating the driver-passenger matching degree and pushing the corresponding target information and matching degree results to both the driver and the passenger in both directions, multi-dimensional data references can be provided for both parties, making carpooling no longer a simple location matching, but a precise matching based on social relationships and interest similarity, thus improving the carpooling experience.

[0097] In some embodiments, the first target information includes interest tags and affiliated community groups, and the method further includes: Interest matching degree is calculated based on each passenger's interest tags, and group overlap degree is calculated based on each passenger's community group; The degree of mutual matching between passengers is determined based on interest matching and group overlap. The matching scores are pushed to the corresponding passenger and driver terminals respectively.

[0098] To reduce the high trust costs and poor experience caused by the lack of social connections among fellow passengers, this embodiment uses passengers' interest tags and their respective community groups as references to calculate the interest matching degree and group overlap degree among passengers, thereby generating a mutual matching degree. This transforms the stranger carpooling scenario into an acquaintance carpooling scenario based on shared interests and community connections, reducing the trust costs and safety concerns among passengers.

[0099] In some embodiments, the server can perform similarity matching on the interest tag sets of multiple passengers, count the number of identical or highly related tags, and calculate the ratio with the total number of tags of multiple passengers. The interest matching degree is expressed as a percentage, which reflects the degree of fit between passengers' interests and travel scenarios. The higher the interest matching degree, the stronger the interest association between passengers.

[0100] The server can count the number of community groups that multiple passengers have joined together, and divide it by the total number of community groups that multiple passengers have joined to obtain the group overlap. The group overlap reflects the strength of the connection between these passengers at the social group level. The more common the number of groups, the stronger the social trust foundation among passengers.

[0101] The server can calculate the mutual matching score between passengers by weighting and summing the interest matching score and group overlap score according to preset weighting rules. The weighting rules can be dynamically adjusted according to the attributes of the carpooling scenario. For example, in event scenarios such as music festivals and concerts, the weight of interest matching score can be set to 60%, and the weight of group overlap score can be set to 40%; in daily commuting and community shuttle scenarios, the weight of group overlap score can be set to 60%, and the weight of interest matching score can be set to 40%. The higher the mutual matching score, the closer the interest and social connection between passengers, and the stronger the trust and experience during the ride. For example, if passenger A and passenger B have an interest matching score of 70% and a group overlap score of 50%, and the current scenario is an event shuttle, then the mutual matching score between passenger A and passenger B is 70% × 0.6 + 50% × 0.4 = 62%. It should be noted that interest matching degree, group overlap degree, mutual matching degree, etc. can be expressed as a percentage, or they can be standardized and converted into scores of 1-100, 1-10, etc. This application embodiment does not limit this.

[0102] The server can push the matching scores to both the passenger's app and the driver's app for this trip. For the passenger's app, the anonymized information and matching scores of fellow passengers can be displayed on the carpooling order confirmation page. For example, "Fellow passenger: From the XX concert fan group, interest matching 70%, group overlap 50%, mutual matching 62%." Passengers can use this information to determine the interests and community connections of their fellow passengers, realizing that they are not complete strangers but acquaintances with shared interests or community connections. This reduces trust costs and safety concerns during carpooling, increasing willingness to carpool and a sense of security.

[0103] For drivers, the matching degree between passengers can be displayed on the invitation management interface and the carpooling progress interface. For example, "Passenger A and B have a matching degree of 62%, and passenger A and C have a matching degree of 35%". Drivers can prioritize matching passengers with high matching degrees based on the matching degree between passengers.

[0104] In this embodiment, by combining passenger interest tags with their respective community groups, the matching degree between passengers is calculated, providing passengers with relevant information about their fellow passengers. Based on the identity of group members and common interests, carpooling between strangers is transformed into carpooling between acquaintances based on common interests, reducing trust costs and safety concerns, enhancing carpooling willingness and travel safety, and also making it easier for drivers to prioritize matching passengers with high matching degrees, reducing communication friction during the trip.

[0105] In some embodiments, the method further includes: Provide a matching rule settings interface to drivers. The matching rule settings interface includes any of the following matching rules: accept carpooling requests from members of the target community group, prioritize the review of carpooling requests from members in the same community group, and allow unlimited carpooling requests. Based on the target matching rules selected by the driver, the received carpooling requests are sorted and pushed to the driver's end.

[0106] In this embodiment, the matching rule setting interface can be displayed in conjunction with the trip document generation interface and the carpooling application receiving interface, or it can be displayed after the driver publishes the trip document. This allows drivers to enter the matching rule setting interface at any time before sharing the trip document and during the carpooling application receiving process to set and modify the matching rules, thus meeting the driver's rule adjustment needs at different stages of the carpooling service.

[0107] The matching rules settings interface can include multiple rule options, such as accepting carpooling requests from members of the target community group, prioritizing the review of carpooling requests from members in the same community group, and allowing unlimited carpooling requests.

[0108] The carpooling rules for accepting carpooling requests from members of the target community group are closed. The server only accepts and processes carpooling requests submitted by members of the target community group from which the trip itinerary is shared, and automatically rejects carpooling requests from members of other target community groups. For example, if the driver is a member of a music festival fan group, after posting the trip, he only wants to accept carpooling requests from members of that fan group to achieve exclusive carpooling within the community.

[0109] Prioritizing carpooling requests from members in the same community group is a group-priority carpooling rule. The server can accept carpooling requests from both members of the target community group and members of other community groups, but it will prioritize carpooling requests from members of the same community group so that drivers can choose to carpool with members of the same community group.

[0110] Unrestricted carpooling requests are open carpooling rules, which can be the server's default matching rules. The server accepts all submitted carpooling requests indiscriminately, without setting any filtering or priority restrictions related to community identity, and is suitable for general carpooling scenarios.

[0111] After receiving the target matching rule selected by the driver through the matching rule settings interface, the server uniquely associates the target matching rule with the current carpooling trip. When the server receives a carpooling request submitted by a passenger, it filters, sorts, and pushes the carpooling request in a targeted manner according to the target matching rule.

[0112] In this embodiment, by providing a settings interface with multiple carpooling application matching rules to the driver, drivers can flexibly choose matching rules based on their own travel needs and preferences, reducing the operational cost of manually screening and judging a large number of carpooling applications and improving the efficiency of the driver's review and processing of carpooling applications.

[0113] In some embodiments, the method further includes: Once the driver confirms at least one carpooling request, a trip coordination group is created, and the driver and the passenger corresponding to the confirmed carpooling request are added to the trip coordination group.

[0114] In this embodiment, after the driver reviews and confirms the carpooling application on the driver's end, he will send an instruction signal containing the confirmation result to the server. After the server receives the signal and verifies it, it will automatically start the process of creating the trip coordination group.

[0115] Specifically, when the server creates a trip coordination group, it adds the driver who initiated the trip and the passengers whose carpooling requests have been confirmed by the driver to the trip coordination group.

[0116] In some embodiments, during the joining process, each member can be configured with an identity identifier, such as "Driver-XXX" or "Passenger-XXX (from XX Community Group)", and a group name can be generated for the trip coordination group. The group name can include core information about the trip, such as "XX Music Festival - XX Community to Venue Carpooling Group", which further strengthens the trip-specific attributes of the group and makes it easier for members to identify it.

[0117] The trip coordination group facilitates communication between drivers and passengers. For example, drivers and passengers can coordinate departure times within the group. Drivers can post their planned departure times, and passengers can suggest adjustments based on their own circumstances. Both parties quickly reach an agreement on the departure time through message exchange within the group, and the server can synchronously link the final confirmed departure time to the trip document. Drivers and passengers can also further negotiate specific pick-up points within the group, such as "next to the bus stop at Gate 2 of XX Community." Drivers can also post trip updates within the group, such as "Arrived at the pick-up point" or "Currently 3 / 4 seats confirmed, 1 more group member can apply." Passengers can also post their travel preparation status. Of course, the trip coordination group can also be used to communicate other related travel matters, but this embodiment does not limit this.

[0118] In this embodiment, by establishing a trip coordination group and adding the driver and corresponding passenger to the group, a trip communication and collaboration channel is built for carpooling participants, reducing trip communication costs and errors, and forming a carpooling ecosystem based on social circles, thereby enhancing user stickiness and the platform's differentiated competitiveness.

[0119] In some embodiments, the method further includes: Provides a pricing mode selection interface for drivers; the pricing mode selection interface includes multiple pricing modes. Generate corresponding price parameters based on the target pricing model selected by the driver; Embed price parameters into the trip document.

[0120] To adapt to the pricing needs of different carpooling scenarios (such as event shuttles, daily commutes, late-night travel, etc.) and to give drivers pricing autonomy, this embodiment provides a pricing mode selection interface on the driver's end, allowing drivers to select a target pricing mode based on trip characteristics and market demand. The server then generates price parameters based on the target pricing mode and embeds them into the trip document.

[0121] Specifically, the pricing model selection interface can be displayed in conjunction with the trip information upload interface. For example, after drivers complete the trip information such as the origin and destination, they can enter the pricing model selection interface to complete the pricing settings. The pricing model selection interface includes multiple pricing models, which can be presented in tabs or lists, each with detailed rule descriptions.

[0122] In some embodiments, multiple pricing models may include a time-based differentiated pricing model, which allows drivers to set differentiated pricing strategies for different times of the trip, adapting to scenarios where travel demand fluctuates over time. Drivers can configure corresponding pricing rules based on different time periods, such as setting a 10-30% premium during peak hours, offering discounted prices to attract passengers during off-peak return periods, and adding a night service fee during late-night hours. The server can also provide drivers with intelligent pricing references based on historical pricing data for the same region and scenario.

[0123] In some embodiments, multiple pricing models may include a group-buying discount pricing model, which sets various incentive rules, allowing drivers to choose to activate single or combined discounts. For example: full-occupancy discounts, where drivers can set rules such as "X% off when all seats are filled" or "X yuan off when all seats are filled"; early bird discounts, supporting settings like "X yuan off for booking N days / hours in advance," incentivizing passengers to book their trips early; group member discounts, offering exclusive discounts (such as 10% off) to members of the target community group sharing the trip, strengthening the community-exclusive benefits; and returning customer discounts, providing exclusive prices for passengers previously served by the driver, enhancing user loyalty.

[0124] In some embodiments, multiple pricing models can be dynamically adjusted, which allows drivers to flexibly adjust prices based on real-time carpooling demand.

[0125] In some embodiments, multiple pricing models may include a multi-dimensional combined pricing model, which supports drivers in pricing using a combination of "basic fee + additional service fee + shared fee + special scenario fee". The basic fee is the base price of the trip and can be set based on mileage and duration. The additional service fee can be enabled or disabled by the driver as needed, including fees for large luggage (such as for music festival camping equipment, suitcases, etc.), pet travel, child safety seat fees, and in-vehicle equipment usage fees. The shared fee is set for public costs incurred during the trip (such as highway tolls and bridge tolls) and can be shared equally among the passengers. The special scenario fee corresponds to scenarios such as event shuttles and scenic spot travel, and can include shared items such as parking fees and scenic spot entrance fees. All fee items are displayed independently, and passengers can choose whether to accept a trip including the additional service fee as needed.

[0126] After receiving the selected target pricing model, the server can combine information such as the trip's mileage, duration, and estimated time period to calculate and generate price parameters that include basic fees, various additional fees, discount rules, and effective conditions. These price parameters are then embedded into the structured data of the trip document, allowing passengers to understand the pricing details and determine whether it fits their budget.

[0127] In this embodiment, by providing a pricing mode selection interface to the driver, the driver can independently select the target pricing mode and generate corresponding price parameters to be embedded in the trip document. This allows the driver to flexibly set carpooling prices based on actual conditions such as trip cost, number of carpooling seats, and travel scenario, adapting to pricing needs under different carpooling scenarios. Furthermore, by embedding the price parameters in advance into the trip document, passengers can know the carpooling price information when they visit the carpooling details page, enhancing price transparency and improving user trust and decision-making efficiency.

[0128] In some embodiments, the method further includes: Access data from travel itinerary documents; A demand popularity score is generated based on access data; Price adjustment suggestions are pushed to drivers based on demand popularity scores.

[0129] In this embodiment, the access data is a collection of behavioral data generated by the passenger terminal performing various operations on the trip receipt. The access data may include at least one of the following: the number of clicks on the trip receipt, i.e., the number of times the passenger terminal triggers the access icon in the community group; the number of views on the trip receipt, i.e., the number of valid visits by the passenger terminal to the carpooling details page through the access icon; the dwell time on the trip receipt, i.e., the average dwell time and the longest single dwell time of the passenger on the carpooling details page; the number of carpooling applications, i.e., the number of valid carpooling applications submitted by the passenger on the carpooling details page; and the application conversion rate, i.e., the ratio of the number of carpooling applications to the number of valid views.

[0130] The server can generate a demand popularity score based on a preset demand popularity scoring model. The input to the demand popularity scoring model is access data, and different types of access data correspond to weight coefficients. The access data can be normalized to transform raw data with different dimensions into standardized data with a unified score range. Then, the demand popularity scoring model calculates the score based on the weight coefficients, generating a demand popularity score. The demand popularity score is positively correlated with the demand for carpooling; a higher score indicates stronger carpooling demand for that trip, while a lower score indicates weaker carpooling demand.

[0131] The server can push price adjustment suggestions to drivers based on demand popularity scores. For example, the server pre-establishes a mapping relationship between demand popularity scores and price adjustment suggestions, configuring corresponding price adjustment suggestions for different demand popularity score ranges. Specifically, when the demand popularity score is in a low range, the server can push price reduction suggestions to drivers, such as combining the base price of the trip and preset price adjustment limits, providing drivers with specific price reduction percentages or amount references (e.g., suggesting a price reduction of 10%-20%), helping drivers increase the attractiveness of their trips and activate passengers' willingness to carpool.

[0132] When the demand rating is in a high range, the server can push a price increase suggestion to the driver. If there are remaining seats for this trip, a small price increase (such as 10%-30%) can be suggested.

[0133] When the demand popularity score is in the middle range, the server can push a suggestion to drivers to maintain the current pricing.

[0134] In this embodiment, by collecting access data from trip documents and generating a demand popularity score based on the data, and then pushing price adjustment suggestions to the driver based on the demand popularity score, drivers can keep track of the market demand for the current carpooling trip in real time. This allows drivers to flexibly adjust carpooling prices based on demand popularity, achieving dynamic adaptation between carpooling pricing and market demand, and further optimizing the allocation efficiency of carpooling resources.

[0135] In some embodiments, the method further includes: Receive price negotiation requests submitted by passengers based on price parameters; The price negotiation request is pushed to the driver's end.

[0136] In this embodiment, the carpooling details page also includes an entry point for requesting a price negotiation. After viewing the price parameters in the trip receipt, if passengers have a desire to negotiate the current price, they can submit a price negotiation request to the server based on the price parameters by clicking the negotiation button, entering the negotiation amount, and other interactive operations.

[0137] In some embodiments, the server sets risk control rules for passengers' negotiating behavior, limiting the price adjustment range of negotiation requests. For example, the negotiation range is limited to ±10% of the current price. Negotiation requests exceeding the range will be automatically rejected by the server, and a prompt message indicating the negotiation range limit will be returned to the passenger, along with a prompt indicating the compliant price negotiation range, thereby reducing passengers' malicious negotiating behavior.

[0138] The price negotiation request submitted by the passenger can include the passenger's identity identifier, a unique identifier for the corresponding trip document, the price parameters for the current trip, the passenger's target price for negotiation, and a description of the negotiation request. After the passenger completes and submits the negotiation information, the passenger sends the price negotiation request to the server. Upon receiving the price negotiation request, the server verifies its validity. If the request is deemed valid, it is pushed to the driver's end for the corresponding trip. The driver's interface displays the content of the price negotiation request and provides the driver with an action entry point for handling the request. This allows the driver to intuitively understand the passenger's price negotiation demands and make decisions through the action entry point, such as accepting, rejecting, or offering a reverse quote.

[0139] In this embodiment, by supporting passengers to submit price negotiation requests based on price parameters in the trip receipt and simultaneously pushing the price negotiation request to the driver, passengers can initiate reasonable price negotiations based on their own travel needs and price expectations. Drivers can then decide whether to accept the price negotiation based on their own trip costs, seat availability, and other factors, thus adapting to the price demands of different drivers and passengers and reducing communication costs in the price negotiation process.

[0140] In some embodiments, the method further includes: Share statistics metrics for recording itinerary documents; these metrics include at least one of the following: number of shares, number of clicks, and carpooling application conversion rate. A sharing performance analysis report is generated based on the sharing statistics, and then pushed to the driver's device.

[0141] In this embodiment, after the trip document is generated and the driver completes the first sharing, the server records sharing statistics such as the number of shares, clicks, and carpooling application conversion rate.

[0142] The number of shares refers to the number of valid sharing operations triggered by the driver through the driver's app for this trip order, and also includes the number of secondary shares of the trip order by the passenger. The number of clicks refers to the number of valid clicks triggered by the passenger's app in response to the trip order access marker displayed in the community. The carpooling application conversion rate is the ratio of the number of valid carpooling applications submitted by the passenger for this trip order to the number of valid clicks on the trip order. In addition to the above indicators, the server may also record other sharing statistics such as click-to-browse dwell time and application-to-confirmation conversion rate according to actual analysis needs; this embodiment of the application does not limit these.

[0143] The server can generate a sharing performance analysis report based on recorded sharing statistics. This report can combine data charts and textual analysis, such as displaying specific values ​​for metrics like share count, clicks, and carpooling application conversion rates using bar charts, line charts, and percentage charts, as well as detailed data for each target community group. It can also rate the sharing performance of the trip based on these statistics, categorizing it as excellent, good, average, or poor, and compare it with average metrics for similar trips within the same scenario on the server, allowing drivers to understand the level of sharing effectiveness. Furthermore, the server can analyze these statistics to identify strengths that improve conversion rates and weaknesses that lead to poor conversion rates. For example, it could state, "The XX concert group achieved a 35% conversion rate, higher than other community groups, making this a high-value channel for this sharing," or "This trip had high clicks but low conversion rates because the pricing did not include exclusive community discounts, exceeding passenger expectations."

[0144] After generating the sharing performance analysis report, the server can push the report to the driver's end for the corresponding trip. Based on the issues and strengths identified in the report, the server can also generate sharing strategy optimization suggestions for drivers and embed them into the report. For example, suggestions could include, "For similar trips in the future, prioritize sharing to high-value community groups of type XX to reduce the number of shares to low-conversion communities," or "For event-related trips, it is recommended to use exclusive pricing for group members to improve conversion efficiency within the community." This allows drivers to develop optimized sharing strategies based on the report.

[0145] In this embodiment, by recording the sharing statistics of trip receipts and generating a sharing effect analysis report based on these statistics and pushing it to the driver's end, the driver can understand the dissemination and conversion effect of their own carpooling trip receipts, enabling the driver to optimize the sharing strategy of subsequent carpooling trips in a targeted manner, and improve the accuracy and conversion efficiency of subsequent carpooling information sharing.

[0146] In some embodiments, the method further includes: Provide an invitation management interface to drivers; the invitation management interface displays information on candidate passengers who have accessed the service through trip documents; In response to the driver's invitation action triggered on the invitation management interface, an invitation message is sent to the passenger terminal corresponding to the candidate passenger selected by the driver.

[0147] In this embodiment, the invitation management interface can be activated and displayed after the trip receipt is shared, allowing drivers to access it through a specific entry point from the main trip management interface. The invitation management interface can display information such as candidate passenger information and carpooling progress. Candidate passenger information refers to passengers who trigger an access request through the trip receipt's access identifier and enter the carpooling details page. The server can collect information about candidate passengers, anonymize it, and then push it to the invitation management interface. This information includes the passenger's anonymized identity identifier, the source community group from which the trip receipt was accessed (anonymized, e.g., "from XX Music Festival group"), driver-passenger matching score, and the time the passenger accessed the carpooling details page.

[0148] After viewing the candidate passenger information, the driver can choose one or more candidate passengers as target invitation recipients based on factors such as driver-passenger matching score, passenger community identity tags, and carpooling progress. The driver can trigger the invitation operation by clicking the invitation button or selecting target passengers and then clicking the invitation icon in batches. The driver's terminal will send an invitation instruction to the server containing information such as the driver's identity identifier, the unique identifier of the trip document, and the identity identifier of the target candidate passenger. After receiving the invitation instruction, the server generates an invitation message and pushes the invitation message to the passenger terminal corresponding to the candidate passenger selected by the driver.

[0149] The invitation management interface can also display carpooling progress, including information such as the number of invited passengers, the number of confirmed passengers, and the number of remaining seats. The carpooling progress will be updated when the driver initiates an invitation, the passenger confirms the carpool, and the seat is locked.

[0150] In this embodiment, by providing the driver with an invitation management interface that displays information on candidate passengers who have accessed the trip receipt, the driver can send invitation information to the passenger terminal of the selected candidate passenger after triggering the invitation operation. This allows the driver to independently select potential passengers and initiate invitations based on the relevant information of the candidate passengers, without having to passively wait for passengers to submit carpooling requests. This allows the driver to better control the carpooling process and improve the final matching success rate.

[0151] The following is combined Figure 2 The process described in this application uses "community carpooling after the XX music festival" as an example to illustrate the process of inviting drivers in the carpooling method of this embodiment.

[0152] In this scenario example, driver A plans to return to XX community from the venue after the music festival ends, and several passengers in the XX music festival fan group have the same return trip needs.

[0153] Step 1: The driver publishes the trip and generates the trip receipt.

[0154] In this step, driver A fills in the trip information through the driver's terminal, such as the starting point being "Exit 2 of XX Music Festival Venue" and the destination being "Gate 3 of XX Community", and adds the planned travel time as "19:30 after the music festival ends".

[0155] Driver A selects the "Music Festival" event tag and the "Residential Area" destination tag on the driver's tag selection interface. The server then associates the selected target tags with the trip information.

[0156] Driver A selects the "group purchase discount pricing mode" and sets discount rules such as "20% off when there are 4 people in the group" and "10% off for members in the same group". The server generates price parameters including basic fees and discount rules based on this mode.

[0157] The server generates a trip receipt based on the trip information, destination tags, and price parameters filled in by driver A, and sets a unique access identifier, such as a QR code, for the trip receipt.

[0158] Step 2: Share the itinerary to the target community group.

[0159] Driver A triggers a sharing command on the driver's end. Based on the "music festival" tag, the server selects "XX Music Festival Fan Group" from the target community database as an associated community group and recommends it. Driver A selects this group as the target community group, and the access identifier corresponding to the server's trip receipt is shared to the XX Music Festival Fan Group.

[0160] Step 3: Passengers trigger access and submit carpooling requests.

[0161] Passengers B and C saw the trip itinerary in the XX Music Festival fan group. By scanning the QR code (access icon) on the itinerary, they triggered an access request to enter the carpooling details page and view information such as the trip origin, destination, and price.

[0162] Passengers B and C confirm that the trip matches their needs and submit a carpooling request on the carpooling details page; the server identifies passengers B and C's community identity as "from the XX Music Festival fan group" and assigns them an association tag.

[0163] Step 4: The driver reviews the application and completes the carpooling match.

[0164] Driver A sees the information of passengers B and C on the invitation management interface, such as "from XX Music Festival fan group" and "driver-passenger matching score of 90". Based on the carpooling progress, such as the current 3 seats remaining, driver A approves the carpooling application of passengers B and C.

[0165] The server pushes the driver A's review result to the passengers B and C's terminals. After both parties confirm, the carpooling is successful. The server creates a "XX Music Festival Return Trip Coordination Group" and adds driver A and passengers B and C to the group chat.

[0166] Step 5: Trip Execution and Completion Driver A posted a status update in the trip coordination group stating "Arrived at Exit 2 of the venue." Passengers B and C reported that they would arrive at the pick-up point in 5 minutes. Both parties agreed that the final pick-up location was "the bus stop next to Exit 2 of the venue."

[0167] Driver A picked up passengers B and C and completed the trip. Passengers B and C completed the payment through the passenger app.

[0168] The following is combined Figure 3 The process described in this application uses "commuter carpooling in XX office building" as an example to illustrate the process after a passenger triggers the access identifier in the carpooling method of this embodiment.

[0169] In this example scenario, driver D posted a carpooling trip from XX residential area to XX office building at 8:00 AM, and the trip details have been shared to the XX office building commuter group. Passenger E (a member of the same group) who needs to commute along the same route sees the trip details in the group and clicks the access icon.

[0170] Step 1: Passengers access the carpooling details page via the access icon. Passenger E, in the XX office building commuter group, clicks on the trip receipt access icon (such as a link) shared by driver D, triggering an access request and redirecting to the carpooling details page.

[0171] After receiving the access request, the server records passenger E's information, such as the source community "XX Office Building Commuter Group" and the driver-passenger matching score.

[0172] Step 2: Passengers view trip details and perform actions. Passenger E views the trip information on the carpooling details page. If passenger E only browses and does not apply, the process ends directly.

[0173] If passenger E chooses to apply for a carpool, submitting the carpooling request on the carpooling details page, the server will push the carpooling request to driver D's driver's end.

[0174] Step 3: The driver receives and processes the carpooling request. Driver D receives a carpooling request from passenger E on the driver's app and sees passenger E's information, such as "from XX office building commuter group" and "driver-passenger matching score of 88".

[0175] After verifying passenger E's social network identity, driver-passenger compatibility, and other information, driver D makes a decision: If the carpooling request is accepted, the server updates the carpooling progress, such as "1 / 3 seats confirmed", generates a carpooling order, and notifies passenger E. If the application is rejected, the server sends a "application rejected" notification to passenger E, and the process ends. Driver D can also initiate a trip invitation based on passenger E's information, and after passenger E confirms, update the carpooling progress, generate an order, and notify the driver.

[0176] After passenger E confirms the order information, they can wait for the driver to pick them up.

[0177] This application also provides a carpooling method, applied to the driver's end, such as... Figure 4 As shown, the carpooling method includes steps 410, 420, 430 and 440.

[0178] Step 410: In response to the driver's operation, send trip information to the server; the trip information includes at least the origin and destination of the trip; Step 420: Display the itinerary document generated by the server based on the itinerary information; Step 430: In response to the driver's shared instruction, share the access identifier corresponding to the trip receipt to the target community group; the access identifier points to the carpooling details page containing the trip receipt; Step 440: Receive carpooling request; The carpooling request is submitted on the carpooling details page after the passenger triggers an access request through an access identifier.

[0179] The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0180] This application also provides a carpooling method, applied to the passenger side, such as... Figure 5 As shown, the carpooling method includes steps 510, 520 and 530.

[0181] Step 510: Receive and display the access identifier for the trip document; the access identifier points to the carpooling details page containing the trip document; Step 520: In response to the access request triggered by the passenger's access identifier, display the carpooling details page; Step 530: In response to the passenger's action, submit a carpooling request to the server so that the server can push the carpooling request to the driver's end.

[0182] The carpooling method provided in this application supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to spread quickly to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0183] The carpooling method provided in this application can be executed by a carpooling device. This application uses a carpooling device executing the carpooling method as an example to illustrate the carpooling device provided in this application.

[0184] This application also provides a carpooling device.

[0185] like Figure 6 As shown, the carpooling device includes: The generation module 610 is used to generate a trip document based on the trip information uploaded by the driver; the trip information includes at least the origin and destination of the trip; the trip document carries an access identifier pointing to the carpooling details page; The sending module 620 is used to send the trip order to the driver's end. In response to the sharing instruction triggered by the driver, the access identifier corresponding to the trip order is shared to the target community group; the access identifier points to the carpooling details page containing the trip order. The receiving module 630 is used to receive the access request triggered by the access identifier of the trip document on the passenger's end, and display the carpooling details page on the passenger's end; The push module 640 is used to receive carpooling requests submitted by passengers on the carpooling details page and push the carpooling requests to the driver's end.

[0186] The carpooling device provided in this application embodiment supports drivers in generating trip receipts based on their own trip information. Drivers can also actively trigger a sharing command to push the access identifier corresponding to the trip receipt to the target community group. This enables drivers to actively invite passengers to carpool. Through the sharing mechanism of the community group, the dissemination range of carpooling information is expanded, allowing carpooling information to be quickly spread to users with concentrated travel needs, such as event participants. This shortens the carpooling travel demand matching cycle. Passengers also do not need to perform complex search and filtering operations on the platform. They can complete the carpooling request by accessing the carpooling details page through the access identifier and submitting an application. This simplifies the passenger's operation process and improves the efficiency of travel matching.

[0187] The carpooling device in this application embodiment can be an electronic device or a component of an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0188] The carpooling device in this embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this embodiment does not specifically limit the specific operating system.

[0189] In some embodiments, such as Figure 7 As shown, this application embodiment also provides an electronic device 700, including a processor 701, a memory 702, and a computer program stored in the memory 702 and executable on the processor 701. When the program is executed by the processor 701, it implements the various processes of the above-described carpooling method embodiment and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0190] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0191] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described carpooling method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0192] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0193] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described carpooling method.

[0194] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0195] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described carpooling method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0196] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0197] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0198] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0199] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0200] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0201] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A carpooling method, characterized in that, include: Generate a trip receipt based on the trip information uploaded by the driver; The itinerary information includes at least the origin and destination of the trip; The trip receipt is sent to the driver's end. In response to the driver's shared command, the access identifier corresponding to the trip receipt is shared to the target community group. The access identifier points to the carpooling details page that includes the trip receipt. Receive an access request triggered by the access identifier from the passenger's device, and display a carpooling details page on the passenger's device; The system receives carpooling requests submitted by passengers on the carpooling details page and pushes the carpooling requests to the driver's end.

2. The method according to claim 1, characterized in that, The trip information also includes at least one of the following: travel time, number of seats available for sharing, vehicle information, and driver identity information; the access identifier is at least one of the following: a link, a QR code, and a mini-program card.

3. The method according to claim 1, characterized in that, The driver's terminal provides a tag selection interface, which includes activity tag options and / or destination tag options; The method further includes: The system receives a target tag selected by the driver through the driver's terminal, associates the target tag with the trip information, and embeds it into the trip document.

4. The method according to claim 3, characterized in that, The step of sharing the access identifier corresponding to the trip receipt to the target community group in response to the driver's shared instruction includes: Based on the target tags, at least one related community group is selected from the target community database; Recommend the at least one associated community group to the driver's device; In response to a sharing instruction triggered by the driver, the access identifier corresponding to the trip document is shared to the target community group selected by the driver from the at least one associated community group.

5. The method according to claim 1, characterized in that, The method further includes: Determine the community group from which the access request originated; Passengers who initiate access requests to the carpooling details page from the same source community group will be associated with the carpooling details page; The driver's device displays identity tags indicating that the associated passengers belong to the same community group.

6. The method according to claim 1, characterized in that, The method further includes: The system obtains first target information of the passenger corresponding to the passenger terminal and second target information of the driver corresponding to the driver terminal. The first target information includes at least one of interest tags, evaluation parameters, and the number of people in the same community group as the driver. The second target information includes at least one of vehicle information, historical order records, positive review rate of members in the same group, and activity travel experience. Calculate the driver-passenger matching degree based on the first target information and the second target information; The first target information and the driver-passenger matching degree are pushed to the driver's end, and the second target information and the driver-passenger matching degree are pushed to the passenger's end.

7. The method according to claim 6, characterized in that, The first target information includes interest tags and the community groups to which the target belongs. The method further includes: Interest matching degree is calculated based on each passenger's interest tags, and group overlap degree is calculated based on each passenger's community group; The mutual matching degree between passengers is determined based on the interest matching degree and the group overlap degree; The matching scores are then pushed to the passenger app and the driver app, respectively.

8. The method according to claim 1, characterized in that, The method further includes: A matching rule setting interface is provided to the driver's end. The matching rule setting interface includes any of the following matching rules: receiving carpooling applications from members of the target community group, prioritizing the review of carpooling applications from members in the same community group, and unlimited carpooling applications. According to the target matching rules selected by the driver, the received carpooling requests are sorted and pushed to the driver's end.

9. The method according to claim 1, characterized in that, The method further includes: If the driver confirms at least one carpooling request, a trip coordination group is created, and the driver and the passenger corresponding to the confirmed carpooling request are added to the trip coordination group.

10. The method according to claim 1, characterized in that, The method further includes: A pricing mode selection interface is provided to the driver's terminal; the pricing mode selection interface includes multiple pricing modes; Generate corresponding price parameters based on the target pricing model selected by the driver; The price parameters are embedded into the trip document.

11. The method according to claim 10, characterized in that, The method further includes: Collect access data from the aforementioned itinerary documents; A demand popularity score is generated based on the access data; Based on the demand popularity score, price adjustment suggestions are pushed to the driver's end.

12. The method according to claim 10, characterized in that, The method further includes: Receive the price negotiation request submitted by the passenger based on the price parameters; The price negotiation request is pushed to the driver's terminal.

13. The method according to claim 1, characterized in that, The method further includes: Record the sharing statistics of the trip documents; the sharing statistics include at least one of the following: number of shares, number of clicks, and carpooling application conversion rate; A sharing effect analysis report is generated based on the sharing statistics, and the sharing effect analysis report is pushed to the driver's terminal.

14. The method according to claim 1, characterized in that, The method further includes: An invitation management interface is provided to the driver's end; the invitation management interface displays information of candidate passengers accessed through the trip document; In response to the invitation operation triggered by the driver on the invitation management interface, an invitation message is sent to the passenger terminal corresponding to the candidate passenger selected by the driver.

15. A carpooling method, characterized in that, include: In response to driver actions, send trip information to the server; The itinerary information includes at least the origin and destination of the trip; Display the itinerary document generated by the server based on the itinerary information; In response to the sharing instruction triggered by the driver, the access identifier corresponding to the trip receipt is shared to the target community group; the access identifier points to the carpooling details page containing the trip receipt; Receive carpooling requests; the carpooling request is submitted on the carpooling details page after the passenger triggers an access request through the access identifier.

16. A carpooling method, characterized in that, include: Receive and display an access identifier for the trip document; the access identifier points to a carpooling details page containing the trip document; In response to an access request triggered by the passenger through the access identifier, the carpooling details page is displayed; In response to a passenger's action, a carpooling request is submitted to the server, which then pushes the carpooling request to the driver's end.

17. A carpooling device, characterized in that, include: The generation module is used to generate trip documents based on the trip information uploaded by the driver. The itinerary information includes at least the origin and destination of the trip; The trip receipt carries an access identifier pointing to the carpooling details page; The sending module is used to send the trip receipt to the driver's end, and in response to the sharing instruction triggered by the driver, to share the access identifier corresponding to the trip receipt to the target community group; the access identifier points to the carpooling details page that includes the trip receipt; The receiving module is used to receive the access request triggered by the access identifier of the trip document on the passenger's end, and display the carpooling details page on the passenger's end; The push module is used to receive carpooling requests submitted by passengers on the carpooling details page and push the carpooling requests to the driver's end.

18. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1-16.

19. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-16.

Images