Two-wheeled electric vehicle business processing method, device and equipment

Abstract

The embodiments of this specification disclose a two-wheeled electric vehicle business processing method, device, and equipment. The method includes: when the two-wheeled electric vehicle is powered on and in P gear, if a mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, a Bluetooth connection is triggered and a riding page in a platform application is called up; interacting with the two-wheeled electric vehicle via a Bluetooth connection, displaying a binding confirmation control in the riding page, and binding the two-wheeled electric vehicle to the application account in response to a user operation; after successful binding, when the two-wheeled electric vehicle is powered off, if the mobile terminal touches the near-field communication sensing area again, a power-on control is displayed in the riding page, triggering the two-wheeled electric vehicle to power on; determining a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map points of interest.

Description

Technical Field

[0001] This specification relates to the field of near-field communication technology, and in particular to a method, device, and equipment for processing business on a two-wheeled electric vehicle. Background Art

[0002] Two-wheeled electric vehicles have been widely used due to their practicality in short-distance transportation within the city.

[0003] Currently, many families own two or more two-wheeled electric vehicles for family members' convenience. Many people replace their electric vehicles every two or three years, and some users temporarily use other people's electric vehicles, often from different manufacturers. Some users often install one or more apps from electric vehicle manufacturers on their phones for emergencies. However, in practice, the utilization rate of these apps is often low. Most users still use their electric vehicles in a simple way, turning them on and off like bicycles by inserting a key in the lock.

[0004] Based on this, for the scenario of two-wheeled electric vehicles, there is a need for solutions that can help improve user convenience and safety, and help manufacturers obtain more business data to help improve their products. Summary of the Invention

[0005] One or more embodiments of this specification provide a two-wheeled electric vehicle business processing method, device and equipment to solve the following technical problems: For the two-wheeled electric vehicle scenario, it is necessary to help improve user convenience and safety, and help manufacturers obtain more business data to help improve product solutions.

[0006] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0007] One or more embodiments of this specification provide a two-wheeled electric vehicle service processing method, which is applied to a platform application on a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The method includes:

[0008] When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up;

[0009] Interacting with the two-wheeled electric vehicle via a Bluetooth connection, and if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, displaying a binding confirmation control on the riding page, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control;

[0010] After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to turn on;

[0011] Determine a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generate and display a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest.

[0012] One or more embodiments of this specification provide a two-wheeled electric vehicle business processing device, which is applied to a platform application on a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The device includes:

[0013] A connection wake-up module is provided. When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle and wake up the riding page in the platform application.

[0014] an interactive binding module, which interacts with the two-wheeled electric vehicle via a Bluetooth connection, and displays a binding confirmation control on the riding page if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, and binds the two-wheeled electric vehicle to the application account in response to the user's operation of the binding confirmation control;

[0015] An interactive power-on module, which triggers the power-on of the two-wheeled electric vehicle if the mobile terminal touches the near-field communication sensing area again when the two-wheeled electric vehicle is in the power-off state after the binding is successful;

[0016] The matching and display module determines a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generates and displays a dynamic riding status map page for the two-wheeled electric vehicle that has been turned on based on the matched map point of interest.

[0017] One or more embodiments of this specification provide a two-wheeled electric vehicle business processing device, which is applied to a platform application on a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The device includes:

[0018] at least one processor; and,

[0019] a memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores instructions executable by the at least one processor, wherein the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0021] When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up;

[0022] Interacting with the two-wheeled electric vehicle via a Bluetooth connection, displaying a binding confirmation control on the riding page if the two-wheeled electric vehicle has not yet been bound to the user's application account on the platform application, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control;

[0023] After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near-field communication sensing area again, a power-on control is displayed on the riding page, and in response to the user's operation of the power-on control, the two-wheeled electric vehicle is triggered to start;

[0024] Determine a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generate and display a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest.

[0025] At least one of the above-mentioned technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: users do not need to install the applications of one or more two-wheeled electric vehicle manufacturers or use the corresponding mini-programs, but can use the platform application provided by this application to uniformly manage the two-wheeled electric vehicle related businesses of multiple two-wheeled electric vehicle manufacturers that cooperate with the platform application. Based on the riding page provided by the platform application and the Bluetooth and near-field communication processing logic adapted for it, users can use such processing logic to interact with the two-wheeled electric vehicle for the first time, and conveniently bind the two-wheeled electric vehicle to their application account on the platform application. After the binding is successful, they can continue to use such processing logic to interact with the two-wheeled electric vehicle again, conveniently turn on the bound two-wheeled electric vehicle through near-field communication, and obtain riding assistance on the riding status map page that matches the corresponding two-wheeled electric vehicle manufacturer in real time through the riding page, and can also collect relevant business data more efficiently; therefore, it helps to improve user convenience and safety, helps manufacturers obtain more business data to help improve products, and also helps to reduce the management and operation support costs of manufacturers. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0027] Figure 1 A flowchart of a two-wheeled electric vehicle business processing method provided in one or more embodiments of this specification;

[0028] Figure 2 A schematic diagram of a flowchart of an association verification solution for a helmet supporting near field communication provided in one or more embodiments of this specification;

[0029] Figure 3 A schematic diagram of a process for temporarily lending a two-wheeled electric vehicle for a fee to an individual user, provided in one or more embodiments of this specification;

[0030] Figure 4 A schematic diagram of the principle of user binding a two-wheeled electric vehicle in an application scenario provided by one or more embodiments of this specification;

[0031] Figure 5 A schematic diagram of a vehicle binding prompt page provided for one or more embodiments of this specification;

[0032] Figure 6A schematic diagram of a bound two-wheeled electric vehicle information page provided for one or more embodiments of this specification;

[0033] Figure 7 A schematic diagram of a riding status map page provided in one or more embodiments of this specification;

[0034] Figure 8 A schematic diagram of a user management page provided for one or more embodiments of this specification;

[0035] Figure 9 A schematic diagram of the structure of a two-wheeled electric vehicle service processing device provided in one or more embodiments of this specification;

[0036] Figure 10 A schematic diagram of the structure of a two-wheeled electric vehicle business processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0037] The embodiments of this specification provide a two-wheeled electric vehicle business processing method, device, equipment and storage medium.

[0038] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0039] Figure 1 This is a flowchart of a method for processing two-wheeled electric vehicle services provided in one or more embodiments of this specification. This platform application, applied to a user's mobile terminal, collaborates with multiple different external two-wheeled electric vehicle manufacturers (corresponding to different two-wheeled electric vehicle brands) and supports at least some models of these partners' two-wheeled electric vehicles.

[0040] Platform applications can be those with large user bases and traffic (for example, major payment applications, instant messaging applications, and e-commerce applications). This facilitates smoother integration with a wider range of two-wheeled electric vehicle manufacturers. Mobile terminals support near-field communication and Bluetooth, primarily including smartphones, but also portable devices with screens such as smartwatches and game consoles. Two-wheeled electric vehicles are battery-powered two-wheelers; they primarily include fully battery-powered two-wheelers, but also include partially battery-powered two-wheelers with auxiliary power.

[0041] Figure 1The process in includes the following steps:

[0042] S102: When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and the riding page in the platform application is called up.

[0043] In one or more embodiments of this specification, a user is first bound to a two-wheeled electric vehicle based on a platform application, and then two-wheeled electric vehicle-related services are provided to the user based on the binding relationship. The user can bind one or more two-wheeled electric vehicles to themselves, and the bound two-wheeled electric vehicles support near-field communication and Bluetooth, and interaction between the mobile terminal and the two-wheeled electric vehicles will be achieved based on these two communication methods.

[0044] For the two-wheeled electric vehicle to be bound, the user first needs to turn on the two-wheeled electric vehicle through general means (for example, inserting the key into the lock and turning it). For safety reasons, the two-wheeled electric vehicle needs to be temporarily placed in P gear after turning on to prevent the vehicle from accidentally starting or slipping (if the risk of slipping is not considered and the vehicle has N gear, it may be allowed to continue in N gear), which also facilitates the user's further operations.

[0045] Next, the user can conveniently touch the mobile terminal to the near-field communication sensing area on the two-wheeled electric vehicle to conduct near-field communication. It should be noted that in order to ensure the reliability of the operation, it is recommended to perform the "touch" operation. In actual application, as long as the mobile terminal approaches and enters the near-field communication range of the two-wheeled electric vehicle, the next action may be triggered.

[0046] Thanks to the platform's collaboration with two-wheeled electric vehicle manufacturers, near-field communication (NFC) between a mobile terminal and a two-wheeled electric vehicle can correctly identify and select the platform application, triggering it to launch and automatically opening the riding page within it. The riding page consists of a main page designed for riding services and a series of related sub-pages. For ease of operation and understanding, operations and content are primarily presented within the main page.

[0047] To ensure more stable interaction between the mobile terminal and the two-wheeled electric vehicle, near-field communication (NFC) is also used to trigger a Bluetooth connection between the two. For example, through NFC, at least one of the two devices provides its Bluetooth broadcast-related identifier (device name or universally unique identifier, etc.) to the other device, which then identifies itself and performs Bluetooth pairing, establishing a Bluetooth connection.

[0048] During this process, if the Bluetooth function is not turned on in the mobile terminal, the user can be prompted to turn it on and the page for Bluetooth function settings can be triggered. In addition to establishing the Bluetooth connection, if necessary, the Bluetooth permissions can be further verified to enable the Bluetooth connection to support the required specific data interaction. In addition, for the use rights of other related data, authorization can be requested from the user in a timely manner, and subsequent processing will only proceed if the user authorizes, thereby better protecting user data security.

[0049] S104: Interact with the two-wheeled electric vehicle via a Bluetooth connection. If the two-wheeled electric vehicle has not been bound to the application account of the user on the platform application, a binding confirmation control is displayed on the riding page. In response to the user's operation of the binding confirmation control, the two-wheeled electric vehicle is bound to the application account.

[0050] It is possible to determine whether the two-wheeled electric vehicle and the user's application account on the platform application have been bound offline (for example, by checking whether there is verification data retained locally during binding, etc.) or online (for example, by querying the server whether there is a corresponding binding relationship, etc.).

[0051] Step S104 considers the case where binding has not yet been completed. The user is required to explicitly confirm whether to bind to prevent accidental binding. To facilitate user confirmation, a binding confirmation control, such as a clickable or sliding button, is displayed on the ride interface. If the user performs an action indicating binding confirmation (e.g., click, long press, or sliding, depending on the specific predefined settings) on the binding confirmation control, the binding action is triggered. Specifically, the relevant data required for binding can be exchanged via Bluetooth (of course, if NFC is still in progress, NFC can also be used for interaction). This provides higher reliability and stability, and the user can more easily remove the mobile terminal without having to keep it in contact with the NFC sensing area.

[0052] Through near-field communication or Bluetooth connection, at least one of the following identification data of the two-wheeled electric vehicle is obtained: vehicle material number, frame number, vehicle identification code; by establishing a corresponding relationship between the identification data and the application account (i.e., a binding relationship), the binding of the two-wheeled electric vehicle and the application account is completed. This process can be participated by the server of the platform application, and the binding relationship is saved on the server; of course, in order to facilitate the subsequent verification of the binding relationship in an offline or weak network environment, corresponding verification data reflecting the binding relationship can be generated, and then the verification data can be saved locally on the mobile terminal and / or the two-wheeled electric vehicle. Taking the storage on the mobile terminal as an example, when the relationship needs to be used later, the verification data saved locally on the mobile terminal is sent to the two-wheeled electric vehicle through near-field communication or Bluetooth connection. After the two-wheeled electric vehicle verifies the verification data, it performs the corresponding business action (such as powering on, etc.) for the mobile terminal.

[0053] The specific nature of the application account depends on the platform application's definition. Assuming the platform application is a payment application, the application account could be, for example, a payment account dedicated to the platform; or, alternatively, a more general account bound to the payment account; the user can select one. For example, a mobile phone number, email address, etc. In the latter case, a single general account could be associated with multiple different dedicated payment accounts. If the general account is bound, then the multiple corresponding payment accounts can be considered to be bound to the two-wheeled electric vehicle.

[0054] S106: After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to turn on.

[0055] After the binding is successful, the mobile terminal can use the binding relationship and near-field communication capabilities to quickly trigger (send the corresponding power on / off command through near-field communication) the two-wheeled electric vehicle to start or shut down by "touching (i.e., touching the near-field communication sensing area mentioned above)" the two-wheeled electric vehicle, thereby eliminating the need for tedious operations using traditional keys, simplifying the process and saving user time. Whether in daily travel or special scenarios, it can bring a convenient experience to users and meet people's urgent needs for convenient travel tool operations in modern fast-paced life.

[0056] In the same way, you can also bind multiple different users' application accounts to the same two-wheeled electric vehicle, making it convenient for family members to use it. Of course, if necessary, you can also unbind the relationship through the platform application.

[0057] S108: Determine map points of interest that match the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generate and display a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map points of interest.

[0058] In one or more embodiments of this specification, users can bind their platform application accounts to the two-wheeled electric vehicles of any two-wheeled electric vehicle manufacturer they have cooperated with as needed, without relying on the manufacturer's own application. Not only that, the platform application is also specially adapted to the situation of the two-wheeled electric vehicle manufacturer to which the current two-wheeled electric vehicle belongs, and creates a dynamic auxiliary page for users, called the riding status map page, which users can use during riding.

[0059] The "adaptation" here is at least reflected in the selection of map points of interest. For example, determine the location of at least one of the following service stations on the map that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs (you can also make a more detailed distinction between different models of the same two-wheeled electric vehicle manufacturer) as a matching map point of interest: charging stations, battery replacement stations, maintenance stations, sales stations, rider stations, etc. Thus, for two-wheeled electric vehicles of different models bound to different users, they can all get a riding status map page specifically suitable for the two-wheeled electric vehicle, which has a better experience and higher practicality, and helps users to use these map points of interest more reliably, thereby improving riding protection for users and reducing riding risks.

[0060] It should be emphasized that this application also designs more special and practical map points of interest based on the scenario of two-wheeled electric vehicles, which can be flexibly selected according to actual conditions. The details will be explained in the optional options section below.

[0061] During riding, the mobile terminal and the two-wheeled electric vehicle can maintain a Bluetooth connection. Through the Bluetooth connection, the designated business data of the two-wheeled electric vehicle can be synchronized to the mobile terminal. According to the designated business data, the data on the riding status map page can be updated dynamically in a timely manner. For example, vehicle model, vehicle power, communication status, gear status, vehicle speed, location information, navigation route, nearby map points of interest, etc., can better assist users in riding. In this way, users can mainly focus on road conditions and pay attention to the riding status map page, which reduces the burden on users. In particular, when users may use two-wheeled electric vehicles from different manufacturers, it can better support users to operate with a unified habit, reducing the user's learning cost.

[0062] In order to increase users' enthusiasm for using platform applications to bind two-wheeled electric vehicles and using platform applications to assist in riding (for example, quick startup, using the riding status map page, etc.), corresponding strategies can be set to give users who meet the strategy requirements corresponding resource rewards, such as platform points, red envelopes or other virtual resources (for example, virtual props such as energy and water droplets).

[0063] pass Figure 1 According to the method, users do not need to install the applications of one or more two-wheeled electric vehicle manufacturers or use the corresponding mini-programs. Instead, they can use the platform application provided by this application to uniformly manage the two-wheeled electric vehicle related businesses of multiple two-wheeled electric vehicle manufacturers that cooperate with the platform application. Based on the riding page provided by the platform application and the Bluetooth and near-field communication processing logic adapted for it, users can use such processing logic to interact with the two-wheeled electric vehicle for the first time, and conveniently bind the two-wheeled electric vehicle to their application account on the platform application. After the binding is successful, they can continue to use such processing logic to interact with the two-wheeled electric vehicle again, conveniently turn on the bound two-wheeled electric vehicle through near-field communication, and obtain riding assistance on the riding status map page that matches the corresponding two-wheeled electric vehicle manufacturer in real time through the riding page, and can also collect relevant business data more efficiently; therefore, it helps to improve user convenience and safety, helps manufacturers obtain more business data to help improve products, and also helps to reduce the management and operation support costs of manufacturers.

[0064] based on Figure 1 This specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0065] Although it is allowed to bind multiple users' application accounts to the same two-wheeled electric vehicle, in actual applications, two-wheeled electric vehicles are mainly used by the owner user. If people who are acquainted with the owner user want to use the two-wheeled electric vehicle, they usually just borrow it temporarily. For such cases, there is no need to bind these temporary borrowers, but to establish a lighter relationship, so as to avoid these temporary borrowers from having to perform these preparatory operations. Based on the binding relationship, the owner user can add or delete other users as needed, and the added users can also use the two-wheeled electric vehicle bound to the owner user in a similar way.

[0066] For example, after the user successfully binds, the name and mobile phone number of the vehicle user to be added, as specified by the user, are received (if the vehicle user's application account is known, the application account can also be directly specified); based on the vehicle user's name and mobile phone number, a vehicle user addition request is sent to the platform application's server, so that the server can verify the vehicle user's identity, and query one or more application accounts of the vehicle user corresponding to the mobile phone number on the platform application (the vehicle user needs to pre-register the mobile phone number on the platform application), and authorize one or more application accounts, so that the vehicle user can also control the two-wheeled electric vehicle on and off in a convenient "touch" manner. In this way, there is no need to expose the vehicle user's application account to the user. For the vehicle user, it is more secure, and for the user, it is easier to perform the addition operation. The reason is that mobile phone numbers are often known to acquaintances, while application accounts are indeed more private. Users may not know other people's application accounts, especially accounts such as payment accounts that directly involve property security.

[0067] In one or more embodiments of this specification, a helmet supporting near-field communication is provided for use with a two-wheeled electric vehicle, and can be supported by platform applications, so that the helmet can be easily adapted to two-wheeled electric vehicles produced by different manufacturers, thereby increasing the possibility of users consciously wearing helmets when riding two-wheeled electric vehicles. Based on this idea, a flowchart of an association verification scheme for a helmet supporting near-field communication is provided, see Figure 2 .

[0068] Figure 2 The process in includes the following steps:

[0069] S202: The mobile terminal is successfully bound to the two-wheeled electric vehicle through near field communication and Bluetooth connection.

[0070] S204: When the two-wheeled electric vehicle is turned on and in P gear, if the near-field communication sensing area of a helmet that supports near-field communication touches the near-field communication sensing area on the mobile terminal or the two-wheeled electric vehicle, the helmet is associated with the two-wheeled electric vehicle or the application account through near-field communication.

[0071] After successful binding, users can further associate (bind, or establish a looser correspondence than binding) a helmet. It should be noted that mandatory helmet association can be determined on a case-by-case basis. For example, the platform application or two-wheeled electric vehicle can make corresponding requirements or recommendations to users. Furthermore, relevant policy requirements can be issued if necessary. For ease of description, it is assumed that the user decides to associate a helmet to improve safety, which includes both traffic safety and property safety.

[0072] In one or more embodiments of this specification, for ease of operation, the near-field communication (NFC) sensing area of a user's helmet can be positioned in the ear area of the helmet. This way, if a user needs to communicate with a mobile device, they can put on the helmet first, then simply hold the mobile device to their ear, as if answering a phone call, to sense the helmet. This facilitates operation and helps users develop a habit of putting on their helmet, creating a smooth transition to riding.

[0073] After the association is completed, if the two-wheeled electric vehicle is not used temporarily, it can be turned off by "touching" it, similar to the power-on operation.

[0074] S206: When the two-wheeled electric vehicle is needed later, when the two-wheeled electric vehicle is turned off, if the mobile terminal touches the near-field communication sensing area again, the user is prompted to use the two-wheeled electric vehicle to verify the association relationship with the helmet through near-field communication.

[0075] If a helmet is associated, the helmet also needs to participate in the verification process. From the user's perspective, the user can first put on the helmet, then "touch" the mobile terminal with the NFC sensing area of the two-wheeled electric vehicle, and then "touch" the mobile terminal with the NFC sensing area of the helmet again to trigger the two-wheeled electric vehicle to start.

[0076] S208: If the association relationship verification is passed, the two-wheeled electric vehicle is triggered to start up.

[0077] If the verification fails or the helmet has not been verified, you do not need to turn it on.

[0078] pass Figure 2 In this solution, if the user needs to use a helmet when turning on the vehicle, the user will either bring the helmet with him to the vehicle, or prepare a helmet on the vehicle, so it is not easy to forget to wear a helmet, which helps to develop a safer two-wheeled electric vehicle riding habit.

[0079] In one or more embodiments of this specification, scenarios in which two-wheeled electric vehicles are ridden with people, especially children, are also considered. In real life, the applicant has noticed that some users ride with children who are too young, which increases safety risks. This application provides a solution to assist in verifying scenarios in which two-wheeled electric vehicles are ridden with people, so as to reduce social risks. Specifically, a front seat is provided in front of the main seat of the two-wheeled electric vehicle, and the front seat is provided with a smart lock that is linked to the near-field communication sensing area; it should be noted that the front seat mentioned here is a regular accessory that the two-wheeled electric vehicle manufacturer is capable of pre-configuring, and is not an illegally modified part. If there is corresponding policy support, this solution can be adopted optionally.

[0080] When the smart lock is locked, the front seat cannot be used normally and needs to be unlocked. In this case, if the user wants to ride with a child and let the child sit in the front seat, they need to "touch" the two-wheeled electric vehicle to turn it on, and then have the child use their own terminal (preferably a children's smart watch, or an ordinary smart watch or even a mobile phone for older children) to "touch" it again to trigger the smart lock to unlock, so that the front seat can be used normally.

[0081] Based on this, if the mobile terminal touches the NFC sensing area again, the two-wheeled electric vehicle will be powered on. The mobile terminal or the two-wheeled electric vehicle can then detect whether another terminal has touched the NFC sensing area on the two-wheeled electric vehicle. If so, the smart lock will be unlocked, allowing the front seat to be used normally. The other terminal can be required to be pre-bound to the mobile terminal, so that identity verification can be performed to confirm the actual person using the front seat, which helps improve safety.

[0082] It should be noted that for children who are too young, they do not have the "other terminal" mentioned here. Therefore, normally they cannot trigger the smart lock to unlock. This is exactly what this application hopes for. Because users have greater safety risks when riding with children who are too young, this application wants to reduce the risk of riding through such a solution and help users ride with others in a more standardized manner.

[0083] In one or more embodiments of this specification, in actual applications, many users only use a two-wheeled electric vehicle for commuting, and the frequency of use may even be less. In this case, the platform application's auxiliary capabilities can be considered to help users find other potential users, creating a convenient business link for individual users to temporarily lend their two-wheeled electric vehicles for a fee. This can generate benefits for users and bring convenience to other users, achieving the full utilization and rational allocation of resources in society as a whole.

[0084] Based on this idea, one or more embodiments of this specification provide a flowchart of a solution for a personal user to temporarily lend a two-wheeled electric vehicle for a fee, see Figure 3 This can be done when determining the points of interest on the map. The previous steps can be referred to Figure 1 The method in , will not be repeated here.

[0085] Figure 3 The process in includes the following steps:

[0086] S302: Obtain, from the server of the platform application, the pick-up location on the map provided by a specific vehicle requester selected based on the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, as a matching map point of interest, wherein the specific vehicle requester has also bound the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, or has registered the riding ability of the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer on the server.

[0087] The specific person requesting a vehicle may not know the current user. If other users need to use a two-wheeled electric vehicle, they can send a request through the platform application and the server will match them.

[0088] To improve reliability, priority is given to matching specific vehicle requesters with two-wheeled electric vehicles they are capable of riding. Here, two optional conditions are used for matching: the first condition is that the user has also been bound to an electric vehicle from the manufacturer corresponding to the current user; the second condition is that the user has registered their riding ability for the two-wheeled electric vehicle from that manufacturer on the server. Meeting either condition is considered a match, as this basically ensures that the specific vehicle requester can ride the two-wheeled electric vehicle from that manufacturer without any obstacles.

[0089] If the strict matching above fails to produce a result, the matching conditions can be relaxed to some extent. For example, you can try matching other two-wheeled electric vehicles with similar operating methods.

[0090] For the current user, you can allow the pick-up location corresponding to the specific vehicle requester mentioned above to be displayed on your riding status map page. In particular, you can pay attention to the pick-up location near your current location or your destination. This way, when the current user rides to the pick-up location, it will not delay your work, and at the same time, it is equivalent to delivering your two-wheeled electric vehicle to the pick-up location for delivery to the specific vehicle requester.

[0091] S304: After the dynamic riding status map page is generated and displayed for the powered-on two-wheeled electric vehicle, after the user (i.e., the current user) arrives at the pick-up location, if the mobile terminal of the specific vehicle requester performs designated near-field communication with the mobile terminal of the user, or, when the two-wheeled electric vehicle is powered on and in P gear, the mobile terminal of the specific vehicle requester touches the near-field communication sensing area on the two-wheeled electric vehicle, the specific vehicle requester is added as a temporary user of the two-wheeled electric vehicle.

[0092] After the current user meets the specific vehicle requester at the pick-up location, they can perform an authorization operation (the authorization operation can also be performed remotely in advance) to add the specific vehicle requester as a temporary user. In this way, the specific vehicle requester can use the current user's two-wheeled electric vehicle by "touching".

[0093] S306: charging the temporary user, and settling at least part of the charged fee to the user after the temporary user finishes using the two-wheeled electric vehicle.

[0094] When the temporary user turns on the two-wheeled electric vehicle, billing can begin, and billing will stop when it is turned off. After the use ends, the temporary user can be removed. After removal, the specific vehicle requester can no longer continue to use it. The specific vehicle requester uses the current user's two-wheeled electric vehicle for a fee. The relevant fees can be confirmed or negotiated in advance on the platform application. The current user can obtain income through this flexible lending of two-wheeled electric vehicles based on the platform application and the corresponding "touch and go" capability, which can increase the enthusiasm for lending and bring convenience to more people.

[0095] The platform application may include a payment application, and the application account may correspondingly be a payment account, so that billing, deduction and settlement can be performed seamlessly through the corresponding payment account.

[0096] S308: After the temporary user finishes using the two-wheeled electric vehicle, a return instruction is sent to the server of the platform application, and the return instruction includes the location of the return task specified by the user, so that the server can publish the location of the return task specified by the user to at least some other users of the two-wheeled electric vehicle who have also been bound to the two-wheeled electric vehicle manufacturer, so that other users who accept the return task can temporarily control the two-wheeled electric vehicle to start up and ride the two-wheeled electric vehicle to the location of the return task specified by the user.

[0097] For the current user, although they do not need to use the two-wheeled electric vehicle for the time being, they may need to use it again after a period of time (for example, after the daytime working hours). In this case, the user needs to return their two-wheeled electric vehicle to the designated location in a timely manner. This location may be the pick-up location mentioned above, or it may be a location re-designated by the user based on their needs. This location is called the user-designated return task location.

[0098] After the temporary user finishes using the two-wheeled electric vehicle, they can prepare to return the two-wheeled electric vehicle to the location of the return task. Specifically, the return task can be actively issued by the current user, or automatically issued by the server at an appropriate time. In these cases, the matched map points of interest mentioned above also include one or more return task locations determined by the platform application server on the map.

[0099] The return route can be completed individually by a single user who accepts the task, or by multiple users who accept the task in a relay. In the relay scenario, these users can be selected from a specific user who requested a ride (this approach is preferred), or users who do not have a ride request can freely accept the task. Other users who complete the return task can be rewarded accordingly. For example, the specific user who requested the ride can receive a reduced or waived ride fee, while other users who do not have a ride request can receive additional benefits as a token of appreciation for their dedicated return of the ride to the current user.

[0100] Based on the above approach, from the perspective of the current user, on their own cycling status map page, they can see map points of interest such as other people's pick-up locations and other people's return locations. The user can decide whether to display these map points of interest as needed.

[0101] pass Figure 3 The solution provides individual users with a flexible channel for temporary lending and precise recovery of two-wheeled electric vehicles. In real life, compared with cars, two-wheeled electric vehicles are not that valuable, and the actual idle time is longer. Therefore, many users have such intentions, and the above solution can better bring additional benefits to such users and bring convenience to other users who need cars, achieving a win-win situation.

[0102] According to the above description, in order to facilitate understanding and be more intuitive, one or more embodiments of this specification also provide Figure 1 A specific implementation scheme of the method in an application scenario, combined with Figures 4 to 9 In this application scenario, the mobile terminal is a mobile phone, the platform application is, for example, a payment application, and the near-field communication sensing area of the two-wheeled electric vehicle is set on the driving instrument panel. For ease of operation, this area can have corresponding text prompts. The above-mentioned riding status map page is called, for example, a "riding position" page, or it can also be a subpage of the "riding position" page or a part of it.

[0103] Figure 4 A schematic diagram of the principle of user binding a two-wheeled electric vehicle (hereinafter referred to as a vehicle) in an application scenario provided in one or more embodiments of this specification.

[0104] exist Figure 4In the process of binding, the car owner needs to first turn on the vehicle and put it in P gear by using the usual means such as the key (in other states, for safety reasons, the binding operation may not be allowed, but the user will be automatically redirected to the "Riding Position" page to prompt the user). At this time, the car owner performs a "touch" operation and touches the phone to the dashboard. If the vehicle has been bound before, the platform application can be called up, the "Riding Position" page will be opened, and a pop-up window will be displayed to remind the user that the binding has been done. If it has not been bound yet, proceed with the following process. It should be noted that for some operating systems, the user may need to click to jump before reaching the "Riding Position" page.

[0105] The binding process includes, for example, establishing a near-field communication (NFC, Bluetooth, etc.) connection, verifying Bluetooth permissions, data authorization (e.g., geolocation authorization, account data authorization, etc.), redirecting to the "Cycling Position" page, exchanging relevant data and establishing a corresponding relationship, and successful binding. For platform applications, for example, the vehicle's vehicle identification number, Bluetooth module serial number, vehicle material number, frame number, brand information, model, etc., can be obtained. For vehicle manufacturers, for example, the mobile phone number and other authorization information for platform applications can be obtained.

[0106] After successfully binding, you will be redirected to the relevant information page of the successfully bound vehicle, which is also part of the "Cycling Position" page. Later, if the owner wants to use the vehicle, they can "touch" it to call up the "Cycling Position" page, which automatically triggers the power-on command (the same applies to powering off), thereby turning the vehicle on. After powering on, the "Cycling Position" page will display dynamic information such as matched map points of interest, vehicle location, navigation route, etc.

[0107] During riding, the vehicle and mobile phone can maintain a Bluetooth connection to synchronize information such as vehicle status, battery level, power on / off status, etc.

[0108] If the "Cycling Position" page is not accessed by "touch and go," the content displayed to the user can be determined based on whether the user's app account is bound to a two-wheeled electric vehicle. For example, if the two-wheeled electric vehicle is not bound, the user will be redirected to the page indicating that the two-wheeled electric vehicle has not been bound. If the two-wheeled electric vehicle is already bound, the user will be redirected to the list of bound two-wheeled electric vehicles.

[0109] Figure 5 A schematic diagram of a vehicle binding prompt page provided for one or more embodiments of this specification.

[0110] As you can see, this is the content displayed on a "Car Service" sub-page under the "Cycling Position" page in two different situations.

[0111] The left side shows the "touch" prompt message when the vehicle is turned off, prompting the user to start the vehicle first and then "touch".

[0112] The right side shows that after turning on the device and "touch it once", the vehicle has not yet been bound, so the user is prompted to bind the vehicle by "touch it once". After clicking the "Bind My Electric Vehicle" button, for example, the user can further display some of the two-wheeled electric vehicle manufacturers currently cooperating with the user so that the user can make an accurate selection.

[0113] Figure 6 A schematic diagram of the bound two-wheeled electric vehicle information page provided for one or more embodiments of this specification.

[0114] The left side shows that a user has bound a list of 3 two-wheeled electric vehicles, which shows information such as the vehicle name, color, frame number, etc. The page also provides a button to add more vehicles.

[0115] The right side shows the specific information of one of the bound two-wheeled electric vehicles, such as more specific model information, version information, etc. The page also provides a function button for unbinding.

[0116] Figure 7 A schematic diagram of a riding status map page provided for one or more embodiments of this specification.

[0117] exist Figure 7 The map shows the location layout and description of some controls. Above the map are the vehicle model, battery level, Bluetooth status, GSM signal status, vehicle power on / off status, virtual energy as a reward, and red envelope status. Taking the battery level as an example, it can be obtained from the vehicle's battery level. If it is not obtained, it will not be displayed. When riding or charging, it can be updated once a minute, and when not riding, it can be updated once every 24 hours. The status of the two vehicles can be modified according to the specific model.

[0118] The map shows the location of the vehicle, and also displays special map points of interest such as the "Black Knight Club" that match the current manufacturer (assuming it is called "Black Knight"). Not only that, it is also specially matched with the "Black Knight" manufacturer, providing personalized function controls, such as the Black Knight Assistant button, the sliding power on / off button, the car search button, etc. Of course, according to the above options, more special map points of interest can be displayed, such as the pick-up location, the return location, etc. At the bottom, some operational reward elements are also provided, such as how to distribute red envelopes.

[0119] Figure 8A schematic diagram of the user management page provided for one or more embodiments of this specification. Users can add other users as users through the page. After entering the page on the left, you can delete the added users, or click the button below to add users. After clicking, you will enter the page in the middle to add users, enter the name and mobile phone number, and then click the Add button below to add the corresponding user as a user. Of course, you can also call up the address book and directly select a user as a user. The user being added needs to have a registered application account (specifically a payment account in this scenario) before it can be added successfully.

[0120] It should be noted that some of the above page renderings are exemplary and only reflect the ideas of part of the solutions in this application. For solutions not reflected, the page layout and page functions can be modified as needed.

[0121] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 9 、 Figure 10 The apparatus and device can accordingly execute the above method and related optional solutions.

[0122] Figure 9 This is a schematic diagram of the structure of a two-wheeled electric vehicle business processing device provided in one or more embodiments of this specification, which is applied to a platform application on a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The device includes:

[0123] The connection wake-up module 902 is configured to trigger the mobile terminal to establish a Bluetooth connection with the two-wheeled electric vehicle when the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, and to wake up the riding page in the platform application if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle;

[0124] An interactive binding module 904 interacts with the two-wheeled electric vehicle via a Bluetooth connection, and if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, displays a binding confirmation control on the riding page, and binds the two-wheeled electric vehicle to the application account in response to the user's operation of the binding confirmation control;

[0125] Interactive startup module 906, after the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to start up;

[0126] The matching display module 908 determines the map points of interest that match the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generates and displays a dynamic riding status map page for the two-wheeled electric vehicle that has been turned on based on the matched map points of interest.

[0127] Optionally, the interactive binding module 904 obtains at least one of the following identification data of the two-wheeled electric vehicle through near field communication or the Bluetooth connection: vehicle material number, frame number, and vehicle identification code;

[0128] By establishing a corresponding relationship between the identification data and the application account, the binding of the two-wheeled electric vehicle and the application account is completed.

[0129] Optionally, the interactive binding module 904 saves verification data corresponding to the binding relationship locally in the mobile terminal after the binding is successful;

[0130] The interactive startup module 906 sends the verification data stored locally in the mobile terminal to the two-wheeled electric vehicle through near field communication or Bluetooth connection, so that the two-wheeled electric vehicle starts after verifying the verification data.

[0131] Optionally, the interactive binding module 904, after the binding is successful, when the two-wheeled electric vehicle is turned on and in P gear, if the near field communication sensing area of a helmet supporting near field communication touches the near field communication sensing area on the mobile terminal or the two-wheeled electric vehicle, then the helmet is associated with the two-wheeled electric vehicle or the application account through near field communication;

[0132] The interactive startup module 906 prompts the user to use the two-wheeled electric vehicle to verify the association relationship with the helmet through near field communication;

[0133] If the association relationship is verified to be successful, the two-wheeled electric vehicle is triggered to start up.

[0134] Optionally, the near field communication sensing area of the helmet is arranged in the ear area of the helmet.

[0135] Optionally, a front seat is provided in front of a main seat of the two-wheeled electric vehicle, and the front seat is provided with a smart lock linked to the near-field communication sensing area;

[0136] The interactive startup module 906 detects whether another terminal pre-associated with the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle after the mobile terminal touches the near-field communication sensing area again to trigger the startup of the two-wheeled electric vehicle, wherein the other terminal includes a children's smart watch;

[0137] If so, the smart lock is triggered to unlock so that the front seat can be used normally.

[0138] Optionally, the matching display module 908 determines the location of at least one of the following service sites on the map that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs as a matching map point of interest:

[0139] Charging stations, battery replacement stations, maintenance stations, sales stations, and car owner stations.

[0140] Optionally, the matching display module 908 obtains, from the server of the platform application, a pick-up location on the map provided by a specific vehicle requester selected according to the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, as a matching map point of interest, wherein the specific vehicle requester has also bound a two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, or has registered the riding ability of the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer on the server;

[0141] The interactive binding module 904 generates and displays a dynamic riding status map page for the powered-on two-wheeled electric vehicle, and after the user arrives at the pick-up location, if the mobile terminal of the specific vehicle requester performs designated near-field communication with the mobile terminal of the user, or if the mobile terminal of the specific vehicle requester touches the near-field communication sensing area on the two-wheeled electric vehicle while the two-wheeled electric vehicle is powered on and in P gear, then the specific vehicle requester is added as a temporary user of the two-wheeled electric vehicle;

[0142] The temporary user is charged, and after the temporary user finishes using the two-wheeled electric vehicle, at least part of the charged fee is settled to the user.

[0143] Optionally, the map points of interest further include locations in the map of one or more sendback tasks issued by the server of the platform application;

[0144] The interactive binding module 904 sends a return instruction to the server of the platform application after the temporary user finishes using the two-wheeled electric vehicle. The return instruction includes the location of the return task specified by the user, so that the server can publish the location of the return task specified by the user to at least some other users of the two-wheeled electric vehicle who have also bound the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, so that other users who accept the return task can temporarily control the two-wheeled electric vehicle to start up and ride the two-wheeled electric vehicle to the location of the return task specified by the user.

[0145] Optionally, the interactive binding module 904 receives the name and mobile phone number of the vehicle user to be added specified by the user after the binding is successful;

[0146] Based on the name and mobile phone number of the vehicle user, a vehicle user addition request is sent to the server of the platform application so that the server can verify the identity of the vehicle user, query one or more application accounts of the vehicle user corresponding to the mobile phone number on the platform application, and authorize the one or more application accounts so that the vehicle user can also control the startup of the two-wheeled electric vehicle.

[0147] Optionally, the application account is a payment account.

[0148] Figure 10 This is a schematic diagram of a two-wheeled electric vehicle business processing device provided in one or more embodiments of this specification, which is a platform application applied to a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The device includes:

[0149] at least one processor; and,

[0150] a memory communicatively connected to the at least one processor; wherein,

[0151] The memory stores instructions executable by the at least one processor, wherein the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0152] When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up;

[0153] Interacting with the two-wheeled electric vehicle via a Bluetooth connection, and if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, displaying a binding confirmation control on the riding page, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control;

[0154] After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to turn on;

[0155] Determine a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generate and display a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest.

[0156] Based on the same idea, one or more embodiments of this specification further provide a non-volatile computer storage medium, which is applied to a platform application on a user's mobile terminal. The platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers. The medium stores computer-executable instructions, which are configured as follows:

[0157] When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up;

[0158] Interacting with the two-wheeled electric vehicle via a Bluetooth connection, and if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, displaying a binding confirmation control on the riding page, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control;

[0159] After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to turn on;

[0160] Determine a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generate and display a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest.

[0161] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using physical hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly performed using software called a "logic compiler." This is similar to the software compilers used during program development. Before compilation, the original code must be written in a specific programming language, called a Hardware Description Language (HDL). There are many types of HDL, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that simply by programming a method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0162] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the memory control logic. Those skilled in the art will also appreciate that, in addition to implementing the controller purely in computer-readable program code, the controller can also be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing the various functions included therein can also be considered as structures within the hardware component. Alternatively, the means for implementing the various functions can be considered both a software module implementing the method and a structure within the hardware component.

[0163] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0164] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0165] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Thus, the embodiments of this specification may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware. Furthermore, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0166] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0167] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0168] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0169] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0170] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0171] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0172] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0173] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0174] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device, apparatus, and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simplified. For relevant details, refer to the descriptions of the method embodiments.

[0175] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0176] The foregoing description is merely one or more embodiments of this specification and is not intended to limit this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of one or more embodiments of this specification are intended to be within the scope of the claims of this specification.

Claims

1. A two-wheeled electric vehicle business processing method, applied to a platform application on a user's mobile terminal, wherein the platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers, the method comprising: When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up; Interacting with the two-wheeled electric vehicle via a Bluetooth connection, and if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, displaying a binding confirmation control on the riding page, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control; After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to turn on; Determining a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest; The determining of a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs specifically includes: Obtaining, from the server of the platform application, a pick-up location on a map provided by a specific vehicle requester selected based on the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, as a matching map point of interest, wherein the specific vehicle requester has also bound the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, or has registered the riding ability of the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer on the server; After generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle, the method further includes: After the user arrives at the vehicle pick-up location, if the mobile terminal of the specific vehicle requester conducts designated near-field communication with the mobile terminal of the user, or if the mobile terminal of the specific vehicle requester touches the near-field communication sensing area on the two-wheeled electric vehicle when the two-wheeled electric vehicle is turned on and in P gear, the specific vehicle requester is added as a temporary user of the two-wheeled electric vehicle; The temporary user is charged, and after the temporary user finishes using the two-wheeled electric vehicle, at least part of the charged fee is settled to the user.

2. The method according to claim 1, wherein binding the two-wheeled electric vehicle to the application account specifically comprises: Acquiring at least one of the following identification data of the two-wheeled electric vehicle through near-field communication or the Bluetooth connection: vehicle material number, frame number, and vehicle identification code; By establishing a corresponding relationship between the identification data and the application account, the binding of the two-wheeled electric vehicle and the application account is completed.

3. The method according to claim 1, wherein after the binding is successful, the method further comprises: Saving verification data corresponding to the binding relationship locally on the mobile terminal; The triggering of starting the two-wheeled electric vehicle specifically includes: The verification data stored locally in the mobile terminal is sent to the two-wheeled electric vehicle through near field communication or Bluetooth connection, so that the two-wheeled electric vehicle is turned on after the verification data is verified.

4. The method according to claim 1, wherein after the binding is successful, the method further comprises: When the two-wheeled electric vehicle is turned on and in P gear, if the near-field communication sensing area of a helmet supporting near-field communication touches the near-field communication sensing area on the mobile terminal or the two-wheeled electric vehicle, the helmet is associated with the two-wheeled electric vehicle or the application account through near-field communication; The triggering of starting the two-wheeled electric vehicle specifically includes: Prompting the user to use the two-wheeled electric vehicle to verify the association relationship with the helmet through near-field communication; If the association relationship is verified to be successful, the two-wheeled electric vehicle is triggered to start up.

5. The method according to claim 4, wherein the near field communication sensing area of the helmet is set in the ear area of the helmet.

6. The method according to claim 1, wherein a front seat is provided in front of a main seat of the two-wheeled electric vehicle, and the front seat is provided with a smart lock linked to the near-field communication sensing area; When the mobile terminal touches the near field communication sensing area again, the two-wheeled electric vehicle is triggered to start up, and the method further includes: Detecting whether another terminal pre-associated with the mobile terminal touches a near field communication sensing area on the two-wheeled electric vehicle, wherein the other terminal includes a children's smart watch; If so, the smart lock is triggered to unlock so that the front seat can be used normally.

7. The method according to claim 1, wherein determining a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs comprises: Determine the location of at least one of the following service sites on the map that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs as a matching map point of interest: Charging stations, battery replacement stations, maintenance stations, sales stations, and car owner stations.

8. The method of claim 1, wherein the map points of interest further include locations in the map of one or more sendback tasks issued by the server of the platform application; After the temporary user ends using the two-wheeled electric vehicle, the method further includes: A return instruction is sent to the server of the platform application, wherein the return instruction includes the location of the return task specified by the user, so that the server publishes the location of the return task specified by the user to at least some other users of the two-wheeled electric vehicles that have also been bound to the two-wheeled electric vehicle manufacturer, so that other users who accept the return task can temporarily control the two-wheeled electric vehicle to start up and ride the two-wheeled electric vehicle to the location of the return task specified by the user.

9. The method according to claim 1, wherein after the binding is successful, the method further comprises: Receive the name and mobile phone number of the vehicle user to be added specified by the user; Based on the name and mobile phone number of the vehicle user, a vehicle user addition request is sent to the server of the platform application so that the server can verify the identity of the vehicle user, query one or more application accounts of the vehicle user corresponding to the mobile phone number on the platform application, and authorize the one or more application accounts so that the vehicle user can also control the startup of the two-wheeled electric vehicle.

10. A two-wheeled electric vehicle business processing device, applied to a platform application on a user's mobile terminal, wherein the platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers, the device comprising: A connection wake-up module is provided. When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle and wake up the riding page in the platform application. an interactive binding module, which interacts with the two-wheeled electric vehicle via a Bluetooth connection, and displays a binding confirmation control on the riding page if the two-wheeled electric vehicle and the user's application account on the platform application have not yet been bound, and binds the two-wheeled electric vehicle to the application account in response to the user's operation of the binding confirmation control; An interactive power-on module, which triggers the power-on of the two-wheeled electric vehicle if the mobile terminal touches the near-field communication sensing area again when the two-wheeled electric vehicle is in the power-off state after the binding is successful; a matching and display module for determining map points of interest that match the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map points of interest; The matching display module obtains, from the server of the platform application, a pick-up location on the map provided by a specific vehicle requester selected based on the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, as a matching map point of interest, wherein the specific vehicle requester has also bound the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, or has registered the riding ability of the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer on the server; The interactive binding module generates and displays a dynamic riding status map page for the powered-on two-wheeled electric vehicle, and after the user arrives at the vehicle pick-up location, if the mobile terminal of the specific vehicle requester performs designated near-field communication with the mobile terminal of the user, or if the mobile terminal of the specific vehicle requester touches the near-field communication sensing area on the two-wheeled electric vehicle when the two-wheeled electric vehicle is powered on and in P gear, then the specific vehicle requester is added as a temporary user of the two-wheeled electric vehicle; The temporary user is charged, and after the temporary user finishes using the two-wheeled electric vehicle, at least part of the charged fee is settled to the user.

11. The device according to claim 10, wherein the interactive binding module obtains at least one of the following identification data of the two-wheeled electric vehicle through near field communication or the Bluetooth connection: vehicle material number, frame number, and vehicle identification code; By establishing a corresponding relationship between the identification data and the application account, the binding of the two-wheeled electric vehicle and the application account is completed.

12. The apparatus according to claim 10, wherein the interactive binding module stores verification data corresponding to the binding relationship locally in the mobile terminal after the binding is successful; The interactive startup module sends the verification data stored locally in the mobile terminal to the two-wheeled electric vehicle through near field communication or Bluetooth connection, so that the two-wheeled electric vehicle starts after verifying the verification data.

13. The device according to claim 10, wherein the interactive binding module is configured to, after the binding is successful, associate the helmet with the two-wheeled electric vehicle or the application account via near-field communication if the near-field communication sensing area of a helmet supporting near-field communication touches the near-field communication sensing area on the mobile terminal or the two-wheeled electric vehicle while the two-wheeled electric vehicle is powered on and in P gear; The interactive startup module prompts the user to use the two-wheeled electric vehicle to verify the association relationship with the helmet through near field communication; If the association relationship is verified to be successful, the two-wheeled electric vehicle is triggered to start up.

14. The device according to claim 13, wherein the near field communication sensing area of the helmet is arranged in the ear area of the helmet.

15. The device according to claim 10, wherein a front seat is provided in front of a main seat of the two-wheeled electric vehicle, and the front seat is provided with a smart lock linked to the near-field communication sensing area; The interactive startup module detects whether another terminal pre-associated with the mobile terminal touches the near field communication sensing area on the two-wheeled electric vehicle after the mobile terminal touches the near field communication sensing area again to trigger the startup of the two-wheeled electric vehicle, wherein: The other terminal includes a children's smart watch; If so, the smart lock is triggered to unlock so that the front seat can be used normally.

16. The device of claim 10, wherein the matching display module determines a location on a map of at least one of the following service sites that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs as a matching map point of interest: Charging stations, battery replacement stations, maintenance stations, sales stations, and car owner stations.

17. The apparatus of claim 10, wherein the map points of interest further include locations in the map of one or more sendback tasks issued by a server of the platform application; The interactive binding module sends a return instruction to the server of the platform application after the temporary user finishes using the two-wheeled electric vehicle. The return instruction includes the location of the return task specified by the user, so that the server publishes the location of the return task specified by the user to at least some other users of the two-wheeled electric vehicle who have also been bound to the two-wheeled electric vehicle manufacturer, so that other users who accept the return task can temporarily control the two-wheeled electric vehicle to start up and ride the two-wheeled electric vehicle to the location of the return task specified by the user.

18. The device according to claim 10, wherein the interactive binding module receives the name and mobile phone number of the vehicle user to be added specified by the user after the binding is successful; Based on the name and mobile phone number of the vehicle user, a vehicle user addition request is sent to the server of the platform application so that the server can verify the identity of the vehicle user, query one or more application accounts of the vehicle user corresponding to the mobile phone number on the platform application, and authorize the one or more application accounts so that the vehicle user can also control the startup of the two-wheeled electric vehicle.

19. A two-wheeled electric vehicle business processing device, applied to a platform application on a user's mobile terminal, wherein the platform application cooperates with multiple different external two-wheeled electric vehicle manufacturers, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, wherein the instructions are executed by the at least one processor to enable the at least one processor to perform: When the two-wheeled electric vehicle currently targeted by the user is turned on and in P gear, if the mobile terminal touches the near-field communication sensing area on the two-wheeled electric vehicle, the mobile terminal is triggered to establish a Bluetooth connection with the two-wheeled electric vehicle, and a riding page in the platform application is called up; Interacting with the two-wheeled electric vehicle via a Bluetooth connection, displaying a binding confirmation control on the riding page if the two-wheeled electric vehicle has not yet been bound to the user's application account on the platform application, and binding the two-wheeled electric vehicle to the application account in response to the user operating the binding confirmation control; After the binding is successful, when the two-wheeled electric vehicle is in the off state, if the mobile terminal touches the near-field communication sensing area again, a power-on control is displayed on the riding page, and in response to the user's operation of the power-on control, the two-wheeled electric vehicle is triggered to start; Determining a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, and generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle based on the matched map point of interest; The determining of a map point of interest that matches the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs specifically includes: Obtaining, from the server of the platform application, a pick-up location on a map provided by a specific vehicle requester selected based on the two-wheeled electric vehicle manufacturer to which the two-wheeled electric vehicle belongs, as a matching map point of interest, wherein the specific vehicle requester has also bound the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer, or has registered the riding ability of the two-wheeled electric vehicle of the two-wheeled electric vehicle manufacturer on the server; After generating and displaying a dynamic riding status map page for the powered-on two-wheeled electric vehicle, the method further includes: After the user arrives at the vehicle pick-up location, if the mobile terminal of the specific vehicle requester conducts designated near-field communication with the mobile terminal of the user, or if the mobile terminal of the specific vehicle requester touches the near-field communication sensing area on the two-wheeled electric vehicle when the two-wheeled electric vehicle is turned on and in P gear, the specific vehicle requester is added as a temporary user of the two-wheeled electric vehicle; The temporary user is charged, and after the temporary user finishes using the two-wheeled electric vehicle, at least part of the charged fee is settled to the user.

Images