Vehicle rights sharing method and apparatus

Abstract

Disclosed in the present application are a vehicle rights sharing method and an apparatus. The method comprises: a first vehicle generates a sharing request, the sharing request being used for indicating the first vehicle applies for sharing with a second vehicle first rights that have been ordered by the first vehicle, and the sharing request comprising sharing time information; the first vehicle sends the sharing request; and, on the basis of the sharing request, a network side device generates a first authorization license file for the first vehicle and sends the first license file to the first vehicle, the first license file comprising the remaining period of validity for the first vehicle to use the first rights by means of the sharing. In this way, vehicle rights are designated. Compared with modes in which vehicles can only acquire vehicle rights by means of purchase, the present application allows for vehicle rights that are more flexible to use, thereby helping to improve the coverage rate of the vehicle rights.

Description

Vehicle equity sharing method and device

[0001] This application claims priority to the Chinese patent application filed with the China National Intellectual Property Administration on January 29, 2024, with application number 202410124320.1 and application name “A Method and Device for Sharing Vehicle Equity”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of vehicle equity sharing, and in particular to a vehicle equity sharing method and device. Background Art

[0003] As vehicles become increasingly intelligent, automakers are offering a growing number of subscription services for vehicle benefits. These benefits include at least one of: autonomous driving-related benefits, offline map benefits, and smart cockpit entertainment services. Currently, these benefits are primarily authorized on the vehicle side through license files.

[0004] Currently, when users want to experience a certain benefit of a vehicle, they can only purchase the benefit through their mobile phone or vehicle computer first. The cloud then applies for a license file for the vehicle based on the purchase order of the benefit and sends the license file to the vehicle. The vehicle can activate the corresponding benefit based on the obtained license file, which is not conducive to improving the coverage rate of vehicle benefits. Summary of the Invention

[0005] The present application discloses a vehicle rights and interests sharing method and device, which realizes the division of vehicle rights and interests, which not only makes the use of vehicle rights and interests more flexible, but also helps to improve the coverage and utilization rate of vehicle rights and interests.

[0006] In a first aspect, the present application provides a vehicle rights sharing method, which is applied to a first vehicle and includes: generating a sharing request, the sharing request being used to instruct the first vehicle to apply to share the first rights subscribed by the first vehicle with a second vehicle, the sharing request including sharing time information; and sending the sharing request.

[0007] The first benefit is a vehicle benefit, which includes, for example, at least one of functions or services related to autonomous driving, functions or services related to a smart cockpit, and functions or services related to maps.

[0008] Here, the term "vehicle" refers to a vehicle in a broad sense, such as transportation vehicles (such as commercial vehicles, passenger cars, motorcycles, flying cars, trains, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as mowers, harvesters, etc.), etc.

[0009] Exemplarily, the second vehicle is a vehicle associated with a user (eg, owner) of the first vehicle. For example, the first vehicle and the second vehicle belong to the same owner, or the owner of the second vehicle is acquainted with the owner of the first vehicle.

[0010] In the above method, the first vehicle initiates a sharing request to request the second vehicle to share the first benefit that the first vehicle has subscribed to. Compared with the fact that vehicles can only experience vehicle benefits by purchasing and placing orders, this method provides another solution for the experience of vehicle benefits, making the use of vehicle benefits more flexible and conducive to improving the coverage of vehicle benefits.

[0011] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0012] The sharing duration falls within the valid period of the first benefit stored locally on the first vehicle, meaning that the first vehicle is capable of sharing the first benefit. The sharing duration is measured in hours, days, weeks, or other time units. The other of the three can be determined based on any two of the sharing duration, the start date, and the end date. The usable period of the first benefit provides the legal time for its use.

[0013] By implementing this approach, by including sharing time information in the sharing request, the first benefit shared by the first vehicle can be used simultaneously by the first and second vehicles. This also allows the first benefit to be transferred to the second vehicle when the first vehicle is not using it. The first benefit can be used by different vehicles, increasing the utilization and practicality of the vehicle benefit. If the second vehicle and the first vehicle share the same owner and a vehicle swap is executed, the sharing request can transfer the vehicle benefit, enhancing the value and competitiveness of the vehicle benefit.

[0014] Optionally, sending the sharing request includes: sending the sharing request to a network-side device; the method also includes: receiving a first authorization license file sent by the network-side device, wherein the first license file is associated with the sharing request, and the first license file includes the remaining validity period during which the first vehicle can use the first benefit, and the remaining validity period is associated with the sharing time information; updating the locally stored license file corresponding to the first benefit to the first license file.

[0015] Exemplarily, the association of the first license file with the sharing request is understood to mean that at least part of the information in the sharing request participates in the generation of the first license file, or the first license file includes part of the information in the sharing request.

[0016] Exemplarily, the sharing request also includes the identifier of the first vehicle and the identifier of the first benefit. The association of the remaining validity period with the sharing time information refers to the association of the remaining validity period with the sharing time information and the usable validity period of the first benefit, and the usable validity period of the first benefit is associated with the license files corresponding to the identifier of the first vehicle and the identifier of the first benefit. In other words, the identifier of the first vehicle and the identifier of the first benefit are used to determine the usable validity period of the first benefit, and the usable validity period of the first benefit and the sharing time information are used to calculate the remaining validity period during which the first vehicle can use the first benefit.

[0017] When the above implementation is implemented, after the first vehicle initiates a sharing request, the first vehicle will obtain a new license file (i.e., the first license file) from the network-side device and use the first license file to enable the first benefit.

[0018] Optionally, the method further includes: receiving a second license file sent by a network-side device, the second license file including a validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle; and sending the second license file to the second vehicle.

[0019] When implementing the above implementation method, the first vehicle also forwards the second license file sent by the network-side device to the second vehicle. The second license file is used by the second vehicle to enable the first benefit shared by the first vehicle. In this way, the first benefit is shared by the first vehicle and the second vehicle.

[0020] As an example, the method also includes: receiving indication information sent by a network-side device, the indication information is used to indicate consent for the first vehicle to share the first benefit with the second vehicle; generating a second license file based on the sharing request and information of the second vehicle, the second license file including the validity period for the second vehicle to use the first benefit and the identification of the first vehicle, and the first benefit that the second vehicle can use is shared with the first vehicle; and sending the second license file to the second vehicle.

[0021] By implementing the above implementation method, the first vehicle responds to the instruction information from the network-side device and issues a license file (i.e., the second license file) for the second vehicle on its own, without relying on the network-side device to execute the issuance of the license file. This is beneficial to reducing the load pressure of the network-side device, and even when the second vehicle cannot communicate with the network-side device, it will not delay the first vehicle from sharing the first rights with the second vehicle.

[0022] Optionally, the sharing request further includes at least one of the following information:

[0023] an identification of the first vehicle;

[0024] an identifier of the first interest;

[0025] an identification of the second vehicle;

[0026] The order number of the first vehicle for the first benefit; and

[0027] A license file corresponding to the first benefit currently stored locally in the first vehicle.

[0028] The order number of the first vehicle for subscribing to the first benefit is used by the receiving end of the sharing request to search for and obtain the identifier of the first vehicle, the identifier of the first benefit, and the license file of the first vehicle. The license file of the first vehicle includes the usable validity period of the first benefit corresponding to the first vehicle. Alternatively, the identifier of the first vehicle and the identifier of the first benefit are used by the receiving end of the sharing request to search for and obtain the license file of the first vehicle. Alternatively, the license file corresponding to the first benefit stored locally in the first vehicle is directly carried in the sharing request. In this way, the receiving end of the sharing request can directly obtain the identifier of the first vehicle and the identifier of the first benefit from the license file, so that the receiving end can further locally search and obtain the license file of the first vehicle based on the identifier of the first vehicle and the identifier of the first benefit.

[0029] Optionally, sending the sharing request includes: sending the sharing request to the second vehicle; the method also includes: receiving feedback information sent by the second vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first benefit, and the feedback information includes information of the second vehicle; sending a second license file to the second vehicle, the second license file including the validity period of the first benefit that the second vehicle can use and the identification of the first vehicle, the first benefit that the second vehicle can use is shared with the first vehicle, and the second license file is obtained by the first vehicle based on the sharing request and the information of the second vehicle.

[0030] For example, before sending a sharing request to a second vehicle, the first vehicle broadcasts a probe request to find other vehicles seeking to share vehicle benefits. The first vehicle then receives responses to the probe request from multiple vehicles and determines the second vehicle from among these multiple vehicles. The determination of the second vehicle can depend on a selection strategy. For example, the selection strategy may include at least one of the following conditions: the vehicle currently closest to the first vehicle, the vehicle that responds to the probe request the fastest, the vehicle with the strongest network signal strength, or a vehicle associated with the first vehicle's owner.

[0031] Exemplarily, the second vehicle information includes first identification information for identifying the second vehicle and second identification information for identifying components within the second vehicle that support the first benefit. The first identification information is, for example, the vehicle identification code of the second vehicle, or an identification digest generated based on the vehicle identification code of the second vehicle. The second identification information is, for example, the identification of the components within the second vehicle that support the first benefit, or an identification digest generated based on the identification of the components within the second vehicle that support the first benefit.

[0032] By implementing the above implementation method, the first vehicle directly communicates with the second vehicle. When the first vehicle determines that the second vehicle agrees to accept the first rights and interests shared by the first vehicle, the first vehicle issues a license file to the second vehicle by itself, without relying on the network-side device to execute the issuance of the license file, which is beneficial to reducing the load pressure of the network-side device. In addition, when the second vehicle cannot communicate with the network-side device, it will not delay the first vehicle from sharing the first rights and interests with the second vehicle.

[0033] Optionally, the method further includes: upon receiving a reply from the second vehicle that the second license file has been activated, deducting the usable validity period of the first benefit locally stored in the first vehicle according to the sharing time information.

[0034] In the above implementation, when the first vehicle issues a license file to the second vehicle, only after the second vehicle successfully activates the second license file will the first vehicle locally perform a deduction of the usable validity period of the first benefit based on the sharing time information. In this way, the first vehicle successfully shares the first benefit with the second vehicle this time.

[0035] Optionally, the method further includes: sending sharing information to the network-side device, where the sharing information indicates that the first vehicle has shared the first equity with the second vehicle.

[0036] Exemplarily, the sharing information includes the above-mentioned sharing time information and information of the second vehicle.

[0037] When implementing the above implementation method, when the second license file to be used by the second vehicle is issued by the first vehicle, the first vehicle must also report to the network-side device the sharing information that the first vehicle has shared the first right with the second vehicle, so that the network-side device can timely update the local rights information (such as the validity period of the first right of the first vehicle, the partner vehicle of the first vehicle, etc.) based on the sharing information to ensure that the rights information on the network-side device side is consistent with the rights information on the corresponding vehicle side.

[0038] Optionally, the method further includes: indicating to the user the equity sharing attributes to be set, the equity sharing attributes including the equity to be shared, the identifier of the target vehicle to be shared, and the sharing time information corresponding to the equity; generating the sharing request includes: receiving the setting information of the user, and generating the sharing request based on the setting information.

[0039] The user is, for example, the owner of the first vehicle, the current driver of the first vehicle, or a person who has access to the first vehicle.

[0040] Exemplarily, receiving the setting information of the user includes: acquiring the setting information input by the user through at least one of a touch screen, a button, a keyboard, and voice input.

[0041] In the above implementation, the first vehicle allows the user to configure the equity sharing attributes indicated by the first vehicle, thereby generating a corresponding sharing request based on the user's settings. Furthermore, the user is provided with a variety of channels for configuring equity sharing attributes, which are applicable to a wide range of scenarios.

[0042] In a second aspect, the present application provides a method for sharing vehicle rights and interests, the method comprising: obtaining a first request, the first request being used to instruct a first vehicle to apply to share a first right and interest subscribed by the first vehicle with a second vehicle, the first request including sharing time information; generating a first authorization license file based on the first request, the first license file including the remaining validity period during which the first vehicle can use the first right and interest after the sharing; and sending the first license file to the first vehicle.

[0043] Here, the method is applied to network-side devices. The network-side device is, for example, a server deployed on the network side (such as a license center or a license issuance server), or a system-level device consisting of a license center and a license issuance server, or a system-level device consisting of a rights operation platform, a license center, and a license issuance server. The network-side device can be deployed in a cloud environment or an edge environment, for example, and is not specifically limited here.

[0044] Exemplarily, obtaining the first request includes: receiving the first request from the first vehicle or the user terminal.

[0045] In the above method, the network-side device knows, based on the first request, that the first vehicle applies to share the subscribed first benefit with the second vehicle. In response to the first request, the network-side device reissues a license file (i.e., a first license file) for the first vehicle. The first license file includes the remaining validity period of the first benefit that the first vehicle can use after this sharing, thereby realizing the division of the first benefit.

[0046] Optionally, the first request also includes the identification of the first vehicle and the identification of the first right, and the remaining validity period is determined based on the usable validity period of the first right and the sharing time information. The usable validity period of the first right is obtained from the license file found based on the identification of the first vehicle and the identification of the first right.

[0047] That is to say, the network-side device locally searches for the license file of the first vehicle based on the identification of the first vehicle and the identification of the first right, and obtains the usable validity period of the first right from the license file of the first vehicle. Furthermore, the network-side device determines the remaining validity period of the first right that can be used after sharing the first vehicle based on the obtained usable validity period of the first right and the sharing time information.

[0048] Optionally, the method further includes: generating a second license file based on the first request, the second license file including a validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle; and sending the second license file to the second vehicle or the first vehicle.

[0049] In the above implementation method, the network-side device can also issue a license file (i.e., a second license file) for the second vehicle based on the first request and send the second license file to the second vehicle. The second license file is used by the second vehicle to enable the first benefit shared by the first vehicle. Compared with the vehicle only being able to experience the vehicle benefit through subscription, it is not only conducive to lowering the experience threshold of vehicle benefits, improving the coverage rate of vehicle benefits, but also making the use of vehicle benefits more flexible.

[0050] Exemplarily, after obtaining the first request, the method further includes: sending a yes indication message to the first vehicle, where the indication message is used to indicate that the first vehicle agrees to share the first interest with the second vehicle.

[0051] In the above implementation, the network-side device can also notify the first vehicle through instruction information that it is allowed to share the first benefit with the second vehicle, so that the first vehicle can independently issue a license file for the second vehicle based on the instruction information. Even if the second vehicle cannot communicate with the network-side device, this does not affect the first vehicle's sharing of the first benefit with the second vehicle.

[0052] Optionally, after obtaining the first request, the method further includes: sending a second request to the second vehicle, the second request being used to inquire whether the second vehicle accepts the first vehicle's sharing of the first benefit; receiving feedback information sent by the second vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first benefit, the feedback information including information of the second vehicle; generating a second license file based on the first request includes: generating the second license file based on the first request and information of the second vehicle.

[0053] For information about the second vehicle, please refer to the corresponding description in the first aspect above, which will not be repeated here.

[0054] Exemplarily, the second request is the first request, or the second request is another request independent of the first request.

[0055] In the above implementation, the network-side device issues a license file to the second vehicle only after confirming that the second vehicle accepts the first vehicle's sharing of the first rights.

[0056] Optionally, the method also includes: when it is determined that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, updating the locally recorded usable validity period of the first right corresponding to the first vehicle to the remaining validity period, and storing the correspondence between the identification of the second vehicle, the identification of the first right and the second license file.

[0057] For example, the network-side device learns through the first vehicle that the first license file is locally activated in the first vehicle, and the network-side device learns through the second vehicle that the second license file is locally activated in the second vehicle. Alternatively, the network-side device learns through the first vehicle that the first license file is locally activated in the first vehicle, and the second license file is locally activated in the second vehicle.

[0058] In the above implementation, when both the first license file and the second license file are activated, the network-side device updates the usable validity period of the first benefit corresponding to the first vehicle based on the sharing time information to deduct the time period for the first vehicle to share the first benefit with the second vehicle (such as the above-mentioned sharing time period).

[0059] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0060] In the third aspect, the present application provides a vehicle rights sharing method, which is applied to a second vehicle, and the method includes: receiving a sharing request, the sharing request is used to instruct the first vehicle to apply to share the first rights subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; obtaining a target authorization license file, the target license file is used for the second vehicle to enable the first rights, the target license file includes the validity period during which the second vehicle can use the first rights, and the first rights that the second vehicle can use are shared with the first vehicle.

[0061] In the above method, the second vehicle enables the first benefit shared by the first vehicle by obtaining the target license file. Compared with the vehicle only being able to experience the vehicle benefit through subscription, this method not only helps to lower the experience threshold of the vehicle benefit and increase the coverage rate of the vehicle benefit, but also makes the use of the vehicle benefit more flexible.

[0062] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0063] Optionally, receiving the sharing request includes: receiving the sharing request sent by the network side device; the method also includes: sending feedback information to the network side device, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, and the feedback information includes information of the second vehicle; obtaining the target authorization license file includes: receiving the target license file sent by the network side device, and the target license file is associated with the sharing request and the information of the second vehicle.

[0064] In the above implementation, the second vehicle obtains the sharing request and the target license file from the network-side device, that is, the second vehicle directly communicates with the network-side device, thereby enabling the first vehicle to share the first right with the second vehicle.

[0065] Optionally, receiving the sharing request includes: receiving the sharing request sent by the first vehicle; the method also includes: sending feedback information to the first vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, and the feedback information includes information of the second vehicle; obtaining the target authorization license file includes: receiving the target license file sent by the first vehicle, and the target license file is associated with the sharing request and information of the second vehicle.

[0066] In the above implementation, the second vehicle obtains a sharing request and a target license file from the first vehicle, and the second vehicle communicates with the first vehicle, thereby enabling the first vehicle to share the first benefit with the second vehicle.

[0067] In a fourth aspect, the present application provides a device for sharing vehicle rights and interests, wherein the device is a first vehicle or is included in the first vehicle, and the device includes: a processing unit for generating a sharing request, wherein the sharing request is used to instruct the first vehicle to apply to share the first right and interest subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; and a sending unit for sending the sharing request.

[0068] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0069] Optionally, the sending unit is specifically used to: send the sharing request to the network side device; the device also includes a receiving unit, which is used to receive a first authorization license file sent by the network side device, wherein the first license file is associated with the sharing request, and the first license file includes the remaining validity period of the first vehicle that can use the first right, and the remaining validity period is associated with the sharing time information; the processing unit is also used to update the locally stored license file corresponding to the first right to the first license file.

[0070] Exemplarily, the sharing request also includes the identification of the first vehicle and the identification of the first right, the remaining validity period is associated with the sharing time information and the usable validity period of the first right, and the usable validity period of the first right is associated with the license files corresponding to the identification of the first vehicle and the identification of the first right.

[0071] Optionally, the receiving unit is further used to receive a second license file sent by a network-side device, where the second license file includes a validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared by the first vehicle; the sending unit is further used to send the second license file to the second vehicle.

[0072] As an example, the receiving unit is further used to receive indication information sent by a network-side device, wherein the indication information indicates that the first vehicle agrees to share the first benefit with the second vehicle; the processing unit is further used to generate a second license file based on the sharing request and information of the second vehicle, wherein the second license file includes the validity period during which the second vehicle can use the first benefit and the identification of the first vehicle, and the first benefit that the second vehicle can use is shared with the first vehicle; the sending unit is also used to send the second license file to the second vehicle.

[0073] Optionally, the sharing request further includes at least one of the following information:

[0074] an identification of the first vehicle;

[0075] an identifier of the first interest;

[0076] an identification of the second vehicle;

[0077] The order number of the first vehicle for the first benefit; and

[0078] The license file corresponding to the first benefit when the first vehicle makes the sharing request.

[0079] Optionally, the sending unit is specifically used to: send the sharing request to the second vehicle; the device also includes a receiving unit, the receiving unit is used to receive feedback information sent by the second vehicle, the feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first benefit, and the feedback information includes information of the second vehicle; the sending unit is also used to send a second license file to the second vehicle, the second license file includes the validity period of the first benefit that the second vehicle can use and the identification of the first vehicle, the first benefit that the second vehicle can use is shared with the first vehicle, and the second license file is obtained by the first vehicle based on the sharing request and the information of the second vehicle.

[0080] Optionally, the processing unit is further configured to: when the receiving unit receives a reply from the second vehicle that the second license file has been activated, deduct the usable validity period of the first benefit locally stored in the first vehicle according to the sharing time information.

[0081] Optionally, the sending unit is further configured to send sharing information to the network-side device, where the sharing information indicates that the first vehicle has shared the first equity with the second vehicle.

[0082] Optionally, the processing unit is also used to: indicate to the user the equity sharing attributes to be set, the equity sharing attributes including the equity to be shared, the identification of the target vehicle to be shared and the sharing time information corresponding to the equity; the processing unit is specifically used to: receive the setting information of the user, and generate the sharing request based on the setting information.

[0083] Exemplarily, the sending unit is also used to broadcast a detection request, which is used to find a vehicle that expects to obtain vehicle rights through sharing; the processing unit is also used to determine the second vehicle from the multiple vehicles after receiving responses to the detection request from the multiple vehicles.

[0084] In a fifth aspect, the present application provides a device for sharing vehicle rights and interests, the device comprising: a receiving unit for obtaining a first request, the first request being used to instruct a first vehicle to apply to share a first right and interest subscribed by the first vehicle with a second vehicle, the first request including sharing time information; a processing unit for generating a first authorization license file based on the first request, the first license file including the remaining validity period during which the first vehicle can use the first right and interest after the sharing; and a sending unit for sending the first license file to the first vehicle.

[0085] Exemplarily, the receiving unit is specifically configured to receive the first request from the first vehicle or the user terminal.

[0086] Optionally, the first request also includes the identification of the first vehicle and the identification of the first right, and the remaining validity period is determined by the processing unit based on the usable validity period of the first right and the sharing time information. The usable validity period of the first right is obtained by the processing unit from the license file found based on the identification of the first vehicle and the identification of the first right.

[0087] Optionally, the processing unit is further used to generate a second license file based on the first request, the second license file including the validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared by the first vehicle; the sending unit is further used to send the second license file to the second vehicle or the first vehicle.

[0088] Optionally, the sending unit is also used to send a second request to the second vehicle, and the second request is used to inquire whether the second vehicle accepts the first vehicle's sharing of the first benefit; the receiving unit is also used to receive feedback information sent by the second vehicle, and the feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first benefit, and the feedback information includes information of the second vehicle; the processing unit is specifically used to: generate the second license file based on the first request and the information of the second vehicle.

[0089] Optionally, the processing unit is also used to: when it is determined that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, update the locally recorded usable validity period of the first right corresponding to the first vehicle to the remaining validity period, and store the correspondence between the identification of the second vehicle, the identification of the first right and the second license file.

[0090] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0091] In the sixth aspect, the present application provides a device for sharing vehicle rights and interests, which is a second vehicle or is included in the second vehicle. The device includes: a receiving unit for receiving a sharing request, the sharing request is used to instruct the first vehicle to apply to share the first right and interest subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; the receiving unit is also used to obtain a target authorization license file, the target license file is used for the second vehicle to enable the first right and interest, the target license file includes the validity period during which the second vehicle can use the first right and interest, and the first right and interest that the second vehicle can use is shared with the first vehicle.

[0092] Optionally, the sharing time information includes at least one of the following information: sharing duration, a start date of the sharing, an end date of the sharing, and a usable time period of the first benefit.

[0093] Optionally, the receiving unit is specifically used to: receive the sharing request sent by the network side device; the device also includes a sending unit, which is used to send feedback information to the network side device, the feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first right, and the feedback information includes information of the second vehicle; the receiving unit is specifically used to: receive the target license file sent by the network side device, and the target license file is associated with the sharing request and the information of the second vehicle.

[0094] Optionally, the receiving unit is specifically used to: receive the sharing request sent by the first vehicle; the device also includes a sending unit, the sending unit is used to send feedback information to the first vehicle, the feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first equity, and the feedback information includes information of the second vehicle; the receiving unit is specifically used to: receive the target license file sent by the first vehicle, and the target license file is associated with the sharing request and the information of the second vehicle.

[0095] In the seventh aspect, the present application provides a device for vehicle equity sharing, which includes a processor and a memory, wherein the memory is used to store program instructions; the processor calls the program instructions in the memory to enable the device to execute the method in the first aspect or any possible implementation of the first aspect, or execute the method in the second aspect or any possible implementation of the second aspect, or execute the method in the third aspect or any possible implementation of the third aspect.

[0096] In the eighth aspect, the present application provides a vehicle rights sharing system, which includes a first device and a second device, or includes a first device, a second device and a third device, wherein the first device is used to implement the method in the first aspect or any possible implementation of the first aspect, the second device is used to implement the method in the third aspect or any possible implementation of the third aspect, and the third device is used to implement the method in the second aspect or any possible implementation of the second aspect.

[0097] Exemplarily, the first device is a device in the fourth aspect or any possible implementation of the fourth aspect, the second device is a device in the sixth aspect or any possible implementation of the sixth aspect, and the third device is a device in the fifth aspect or any possible implementation of the fifth aspect.

[0098] In a ninth aspect, the present application provides a vehicle comprising a device as in the fourth aspect or any possible implementation of the fourth aspect, or comprising a device as in the sixth aspect or any possible implementation of the sixth aspect.

[0099] In the tenth aspect, the present application provides a computer-readable storage medium comprising computer instructions, which, when executed by a processor, implement the method of the first aspect or any possible implementation of the first aspect, or implement the method of the second aspect or any possible implementation of the second aspect, or implement the method of the third aspect or any possible implementation of the third aspect.

[0100] In the eleventh aspect, the present application provides a computer program product, which, when executed by a processor, implements the method in the first aspect or any possible embodiment of the first aspect, or implements the method in the second aspect or any possible implementation of the second aspect, or implements the method in the third aspect or any possible implementation of the third aspect.

[0101] Exemplarily, the computer program product is a software installation package. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] FIG1 is a schematic diagram of the architecture of a vehicle equity sharing system provided in an embodiment of the present application;

[0103] FIG2 is a flow chart of a vehicle equity sharing method provided in an embodiment of the present application;

[0104] FIG3 is a schematic diagram of a display interface for setting equity sharing attributes provided in an embodiment of the present application;

[0105] FIG4A is a schematic diagram of an interaction for sharing vehicle rights and interests provided by an embodiment of the present application;

[0106] FIG4B is a schematic diagram of an interaction for sharing vehicle rights and interests provided by an embodiment of the present application;

[0107] FIG4C is a schematic diagram of an interaction for sharing vehicle rights and interests provided in an embodiment of the present application;

[0108] FIG5 is a flowchart of another vehicle equity sharing method provided in an embodiment of the present application;

[0109] FIG6 is a schematic diagram of an interaction for sharing vehicle rights and interests provided in an embodiment of the present application;

[0110] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0111] FIG8 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0112] FIG9 is a schematic structural diagram of a vehicle equity sharing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0113] It should be noted that the prefixes such as "first" and "second" used in this application are only for distinguishing different description objects, and do not have any limiting effect on the position, order, priority, quantity or content of the described objects. For example, if the described object is a "field", then the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the described object is a "level", then the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of described objects is not limited by the prefix and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the described object is a "device," then the "first device" and the "second device" can be the same device, the same type of device, or different types of devices. For another example, if the described object is "information," then the "first information" and the "second information" can be information of the same content or information of different contents. In short, the use of prefixes to distinguish the described objects in the embodiments of this application does not constitute a limitation on the described objects. For the description of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0114] It should be noted that the descriptions used in the embodiments of the present application, such as "at least one of a1, a2, ..., and an" and the like, include any one of a1, a2, ..., and an existing alone, and any combination of any multiple of a1, a2, ..., and an, each of which can exist alone. For example, the description "at least one of a, b, and c" includes a alone, b alone, c alone, a combination of a and b, a combination of a and c, a combination of b and c, or a combination of ab and c.

[0115] To facilitate understanding, the following first introduces relevant terms that may be involved in the embodiments of this application.

[0116] In the embodiment of the present application, the license file is a permission control file. For example, the license file is an authorization file used to control the capacity, function, and time of the software version.

[0117] The license file used to manage vehicle rights and interests generally includes the vehicle identification (such as the vehicle identification code VIN of the vehicle), the vehicle rights and interests identification, the identification of the components in the vehicle that support the vehicle rights and interests, the validity period during which the vehicle can use the vehicle rights and interests, and the license signature, wherein the license signature is associated with at least one of the vehicle identification, the vehicle rights and interests identification, the identification of the components in the vehicle that support the vehicle rights and interests, and the validity period during which the vehicle can use the vehicle rights and interests.

[0118] Exemplarily, the license file for managing vehicle rights and interests further includes at least one of the creator, creation time, issuer, and user of the license file.

[0119] Here, vehicle benefits include, for example, at least one of functions or services related to autonomous driving, functions or services related to smart cockpits, functions or services related to maps, etc.

[0120] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0121] Referring to Figure 1 , Figure 1 is a schematic diagram of the architecture of a vehicle equity sharing system provided in an embodiment of the present application. This system is used to implement the sharing or division of vehicle equity. The system includes a network-side device and multiple terminals. Each of these multiple terminals communicates with the network-side device, for example, wirelessly, and the terminals communicate with each other, for example, wirelessly.

[0122] The terminals involved in this application include, for example, intelligent terminals or vehicles such as vehicles, robots, drones, ships, and boats. Vehicles are vehicles in a broad sense and can include transportation vehicles (such as commercial vehicles, passenger cars, motorcycles, flying cars, trains, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as mowers, harvesters, etc.), etc. For another example, robots can include intelligent transport robots (automated guided vehicles, AGVs), walking conversational robots, service robots, and other robots.

[0123] As shown in Figure 1, the terminal uses a vehicle as an example. For example, the vehicle is an autonomous vehicle. Here, autonomous driving is not limited to fully autonomous driving, highly autonomous driving, conditionally autonomous driving, or partially autonomous driving. Those skilled in the art will understand that any non-fully manual driving that provides intelligent driving is also covered by this concept.

[0124] For example, depending on the power source of the vehicle, the vehicle may be a new energy vehicle or a traditional vehicle, etc. Traditional vehicles refer to fuel vehicles (e.g., gasoline vehicles, diesel vehicles, etc.), while new energy vehicles include electric vehicles (EV), hybrid electric vehicles (HEV), range-extended EV, plug-in hybrid vehicles (HEV), fuel cell vehicles, or other new energy vehicles, without specific limitation herein.

[0125] As shown in Figure 1, network-side devices include a rights management platform, a license authorization center, and a license issuance server. The rights management platform and the license authorization center communicate wirelessly or wired, while the license authorization center and the license issuance server communicate wirelessly or wired. Here, the rights management platform and the license authorization center are, for example, servers, or software and hardware modules running on servers.

[0126] Among them, the rights operation platform is used to maintain the order information of the vehicle rights purchased by the user, and the license center is used to apply for a license file from the license issuance server based on the order information sent by the rights operation platform. The license issuance server is responsible for issuing the license file. In the embodiment of this application, the rights operation platform can also be used to maintain the sharing order information of the vehicle rights.

[0127] For example, the network-side device can also be understood as a system-level device consisting of a rights management platform, a license authorization center, and a license issuance server. The network-side device can be deployed in a cloud environment or an edge environment, for example, without specific limitation here.

[0128] The communication system shown in FIG1 can be applied to a variety of application scenarios, such as the following application scenarios: mobile internet (MI), industrial control (industrial control), self-driving, transportation safety (transportation safety), Internet of Things (IoT), smart city (smart city), or smart home.

[0129] The communication system shown in Figure 1 can be applied to various network types, for example, one or more of the following network types: SparkLink, long term evolution (LTE) network, 5th generation mobile communication technology (5G), wireless local area network (for example, Wi-Fi), Bluetooth (BT), Zigbee, or vehicle-mounted short-range wireless communication network, etc.

[0130] It should be noted that Figure 1 is merely an exemplary architecture diagram and does not limit the number of network elements included in the system shown in Figure 1. Although not shown in Figure 1, Figure 1 may also include other functional entities in addition to the functional entities shown in Figure 1. Furthermore, the methods provided in the embodiments of the present application can be applied to the communication system shown in Figure 1. Of course, the methods provided in the embodiments of the present application can also be applied to other communication systems, and the embodiments of the present application are not limited in this regard.

[0131] Currently, users of any vehicle can only experience the corresponding vehicle benefits by purchasing benefits. Taking the second vehicle in Figure 1 as an example, the user of the second vehicle purchases the vehicle benefits through a mobile phone or a car computer. The order information of the vehicle benefits will be synchronized to the benefits operation platform. The benefits operation platform stores, converts and synchronizes the order information to the license center. The license center stores the order information sent by the benefits operation platform and applies for a license file from the license issuance server based on the content in the order information (such as the identifier of the subscribed benefits, the subscription duration, etc.) and sends the applied license file to the user's vehicle. The vehicle installs the license file locally and activates it, and the corresponding vehicle benefits can be enabled. However, the subscription period of vehicle benefits is relatively long even for the minimum period, and the threshold for trying out new things is high, which is not conducive to users experiencing vehicle benefits. In addition, the issuance of license files can only rely on network-side devices, and there are few applicable scenarios. In response to the above problems, the embodiment of the present application proposes a vehicle benefits sharing method that can realize the division of vehicle benefits, which not only makes the use of vehicle benefits more flexible, but also helps to improve the coverage rate of vehicle benefits.

[0132] As shown in Figure 1, the multiple terminals include a first vehicle and a second vehicle, with the first vehicle serving as a shared vehicle (i.e., the end for sharing vehicle rights and interests), and the second vehicle serving as the target vehicle (i.e., the end for sharing vehicle rights and interests). In an embodiment of the present application, if the first vehicle wants to share the first rights and interests subscribed by the first vehicle with the second vehicle, the first vehicle can generate a license file for the second vehicle through a network-side device, or the first vehicle itself can also generate a license file for the second vehicle, and the license file is used by the second vehicle to enable the first rights and interests shared by the first vehicle. Based on the differences in the generator and sender of the license file obtained by the second vehicle, it is mainly divided into the following situations:

[0133] Case 1: The license file is generated by the network-side device and sent to the second vehicle by the network-side device;

[0134] Case 2: The license file is generated by the network-side device but sent to the second vehicle via the first vehicle;

[0135] Case 3: The license file is generated by the first vehicle and sent by the first vehicle to the second vehicle.

[0136] For scenario 1 above, a possible implementation method may be: in response to a sharing request sent by the first vehicle, the network-side device generates a first license file for the first vehicle and a second license file for the second vehicle. The network-side device sends the first license file to the first vehicle and the second license file to the second vehicle.

[0137] For scenario 2 above, one possible implementation might be: in response to a sharing request sent by the first vehicle, the network device generates a first license file for the first vehicle and a second license file for the second vehicle. The network device then sends the first and second license files to the first vehicle. Finally, the first vehicle sends the second license file to the second vehicle.

[0138] For scenario 3 above, a possible implementation method may be: In response to a sharing request sent by the first vehicle, the network device generates a first license file for the first vehicle. The network device sends the first license file and an instruction to the first vehicle, indicating that the first vehicle agrees to share the first benefit with the second vehicle. The first vehicle generates a second license file for the second vehicle based on the instruction. As an example, this implementation method is applicable in a scenario where the network device and the second vehicle cannot communicate.

[0139] For scenario 3 above, another possible implementation is as follows: the first vehicle sends a sharing request to the second vehicle. Upon receiving confirmation from the second vehicle, the first vehicle generates a second license file for the second vehicle and sends the second license file to the second vehicle. As an example, this implementation is applicable to scenarios where the network-side device cannot communicate with either the first or second vehicle.

[0140] Here, for details of the above-mentioned sharing request, the first license file and the second license file, please refer to the description of the corresponding contents in the following method embodiment, which will not be repeated here.

[0141] The following is a detailed introduction to the vehicle rights sharing method involved above.

[0142] See Figure 2, which is a flow chart of a vehicle equity sharing method provided in an embodiment of the present application. This method is applied to the vehicle equity sharing system shown in Figure 1, which includes network-side equipment, a first vehicle, and a second vehicle. The first vehicle serves as the sharing end of vehicle equity, and the second vehicle serves as the receiving end of the shared vehicle equity. This method includes, but is not limited to, the following steps shown in Figure 2.

[0143] S201: A first vehicle generates a sharing request.

[0144] The sharing request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information.

[0145] Exemplarily, the second vehicle is a vehicle associated with a user (eg, owner) of the first vehicle. For example, the first vehicle and the second vehicle belong to the same owner, or the owner of the second vehicle is acquainted with the owner of the first vehicle.

[0146] In one implementation, the sharing time information includes at least one of the following information: sharing duration, a start date of sharing, an end date of sharing, and a usable time period of the first benefit.

[0147] Here, the sharing duration is within the usable validity period of the first benefit stored locally in the first vehicle, that is, the first vehicle has the ability to share the first benefit.

[0148] For example, when the sharing time information includes the sharing duration and the sharing start date, the sharing end date may be determined based on the sharing duration and the sharing start date.

[0149] For another example, when the sharing time information only includes the sharing duration, the start date of the sharing is set by default to the time when the sharing request is generated.

[0150] Here, the usable time period of the first benefit provides the legal time for using the first benefit. For example, if the usable time period of the first benefit is 8-11 AM and 2-5 PM, it means that it is legal to use the first benefit between 8-11 AM and 2-5 PM.

[0151] Here, there is no specific limitation on the representation of the start date of sharing, the end date of sharing, and the usable time period of the first right. For example, absolute time representation (such as using the standard time of the National Time Service Center) or relative time representation can be used.

[0152] In some possible embodiments, the sharing time information also includes the time when the first vehicle deactivated the first benefit during the sharing period and / or the time when the first vehicle reactivated the first benefit. Thus, by sharing this time information, the user of the first vehicle can share the first benefit with the second vehicle, allowing both the first and second vehicles to use the first benefit simultaneously. Alternatively, the user can transfer the first benefit to the second vehicle when not in use. The first benefit can be used by different vehicles, increasing the utilization and practicality of the vehicle benefit. If the second vehicle and the first vehicle share the same owner, a sharing request can be used to transfer the vehicle benefit when a vehicle swap is executed, enhancing the value and competitiveness of the vehicle benefit.

[0153] In one implementation, the sharing request also includes at least one of the following information: the identification of the first vehicle, the identification of the first benefit, the identification of the second vehicle, the order number of the first vehicle for ordering the first benefit, and the license file corresponding to the local first benefit of the first vehicle.

[0154] The first vehicle identifier is used to identify the first vehicle, and the second vehicle identifier is used to identify the second vehicle. Here, the vehicle identifier is, for example, the vehicle identification number (VIN) of the vehicle. The first interest identifier is used to identify the first interest. The first interest identifier can be a combination of one or more characters, where the characters can be one or more of numbers, letters, and other symbols. The first interest identifier can be, for example, a combination of one or more numbers, or a combination of one or more numbers and letters.

[0155] For example, the order number of the first vehicle for the first benefit is used to find the first vehicle identifier, the first benefit identifier, and the first vehicle license file. The first vehicle identifier and the first benefit identifier can be obtained from the first vehicle license file.

[0156] In one implementation, before generating a sharing request, the user is informed of the equity sharing attributes to be set. The equity sharing attributes include the equity to be shared, the identifier of the target vehicle to be shared, and the corresponding sharing time information for the equity. Generating the sharing request includes obtaining the setting information input by the user and generating the sharing request based on the setting information. Here, the first vehicle locally searches for the identifier of the equity to be shared based on the equity sharing attributes.

[0157] The user is, for example, the owner of the first vehicle, the current driver of the first vehicle, or a person who has access to the first vehicle.

[0158] Exemplarily, obtaining the setting information input by the user includes:

[0159] Get the setting information entered by the user through the touch screen;

[0160] Get the setting information entered by the user through the button;

[0161] Get the setting information entered by the user through the keyboard; or

[0162] Get the setting information entered by the user through voice.

[0163] For example, the first vehicle includes a display device, and the first vehicle indicates to the user the equity sharing attributes to be set via the display device, and the equity sharing attributes to be set are presented on a display interface of the display device. The display device may be, for example, a vehicle-mounted tablet, an onboard display, or a head-up display (HUD) system, and is not specifically limited herein.

[0164] The following describes how a user inputs setting information through a touch screen based on FIG. 3 .

[0165] Refer to Figure 3, which is a schematic diagram of a display interface for setting equity sharing attributes provided in an embodiment of the present application. The interface shown in Figure 3 is a human-computer interaction interface. On the equity sharing attribute setting interface shown in Figure 3, the user can set the equity to be shared, the identification of the target vehicle, and the sharing time information, wherein the sharing time information includes at least one of the sharing duration, the start time of sharing, and the end time of sharing. For example, the interface shown in Figure 3 shows an input box for the equity to be shared, an input box for the identification of the target vehicle, an input box for the sharing duration, a selection box corresponding to the start time of sharing, and a selection box corresponding to the end time of sharing, etc.

[0166] In Figure 3, when the user clicks the input box on the interface, a touch keyboard appears, allowing the user to enter the corresponding settings. As shown in Figure 3, the "Smart Driving Package 1.0" input box is entered in the "Benefits to be Shared" input box. As can be seen in Figure 3, the user can freely select and set the sharing duration, sharing start time, and sharing end time for the "Sharing Time Information" displayed on the interface. After the user completes the settings on the interface shown in Figure 3, they click the "OK" button. In response to this operation, the control generates a sharing request.

[0167] Here, Figure 3 is only an example of a display interface for setting equity sharing attributes. The embodiment of the present application does not limit the display interface to the form shown in Figure 3, and it can also be other display interfaces for users to set equity sharing attributes. In some possible embodiments, Figure 3 can also display more or less information than what is currently shown, such as deleting the selection box corresponding to the "end time of sharing" in Figure 3, or adding a setting box for "usable time period of equity" in Figure 3, etc., which are not specifically limited here. In some possible embodiments, the "equity to be shared" in the interface shown in Figure 3 may not be input by the user through the touch keyboard, but may be a drop-down selection box for setting "equity to be shared", and the drop-down selection box lists the equity currently available for sharing, and the user selects the equity to be shared from the drop-down selection box as the "equity to be shared".

[0168] S202: The first vehicle sends a sharing request to the network-side device.

[0169] Correspondingly, the network-side device receives the sharing request from the first vehicle.

[0170] Exemplarily, based on the system architecture shown in FIG1 , the first vehicle sends a sharing request to the network-side device, including: the first vehicle sends a sharing request to the equity operation platform, and the equity operation platform sends the sharing request to the license issuing server through the license center.

[0171] In some possible embodiments, the sharing request may also be generated by the user terminal, and the network-side device receives the sharing request from the user terminal. For example, the user terminal (such as a mobile phone, tablet, smart wearable device, etc.) indicates to the user the equity sharing attributes to be set, and when the user terminal detects the setting information input by the user through the user terminal, it generates a sharing request based on the setting information. The user terminal presents the equity sharing attributes to be set, for example, through the display interface of its own display device. For example, the display interface presented by the display device of the user terminal refers to the description of the embodiment of Figure 3 above, which will not be repeated here.

[0172] S203: The network-side device generates a first license file based on the sharing request and sends the first license file to the first vehicle.

[0173] The first license file includes the remaining validity period of the first right that can be used through the shared first vehicle.

[0174] Exemplarily, the network-side device that generates the first license file is the license issuing server in FIG1 .

[0175] Exemplarily, the first license file also includes the identification of the first vehicle, the identification of the first benefit, the identification of the components in the first vehicle that support the first benefit, and first signature information. The first signature information is generated based on at least one other information in the first license file except the first signature information.

[0176] In one implementation, the sharing request also includes the identification of the first vehicle and the identification of the first right. The network-side device searches for the license file of the first vehicle based on the identification of the first vehicle and the identification of the first right. The network-side device obtains the usable validity period of the first right corresponding to the first vehicle from the license file of the first vehicle, and determines the remaining validity period of the first right that can be used through the shared first vehicle based on the usable validity period of the first right and the sharing time information in the sharing request.

[0177] For example, if the sharing request includes the order number for the first benefit subscribed by the first vehicle, the network-side device may also locally search for the license file for the first vehicle based on the order number. Here, the license file for the first vehicle is understood to be the latest license file locally stored on the network-side device for enabling the first benefit for the first vehicle before the first license file is generated, or the latest license file issued by the network-side device for enabling the first benefit for the first vehicle.

[0178] Exemplarily, based on the system architecture shown in FIG1 , the network-side device sends the first license file to the first vehicle, including: the license issuing server sends the first license file to the license center, and then the license center sends the first license file to the first vehicle.

[0179] S204: The first vehicle updates the locally stored license file corresponding to the first right to the first license file.

[0180] Here, the first corresponding license file locally stored in the first vehicle is the license file of the first vehicle in S203 .

[0181] For example, a first vehicle receives a first license file from a network-side device, updates a locally stored license file corresponding to the first benefit to the first license file, installs and activates the first license file locally, and reports the activation result of the first license file to the network-side device.

[0182] S205: The network-side device generates a second license file based on the sharing request.

[0183] The second license file includes the validity period of the first benefit that the second vehicle can use, and the first benefit that the second vehicle can use is shared with the first vehicle. The generation of the first license file and the second license file can be performed simultaneously or one after the other, and are not specifically limited here.

[0184] For example, the validity period for the second vehicle to use the first benefit is obtained by the network device based on the sharing time information in the sharing request. For example, if the sharing time information includes a sharing duration of one week and a sharing start date of January 1, XX, then the validity period for the second vehicle to use the first benefit is from January 1, XX to January 7, XX.

[0185] In one implementation, after receiving a sharing request from a first vehicle, the network device sends a request message to the second vehicle based on the second vehicle's identifier in the sharing request. The request message inquires whether the second vehicle accepts the first vehicle's sharing of the first benefit. For example, the request message can be the aforementioned sharing request or another request independent of the sharing request.

[0186] Accordingly, when the second vehicle detects that it has components that support the first benefit and needs to use the first benefit, the second vehicle sends feedback information to the network device in response to the request information. The feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first benefit, and the feedback information includes information about the second vehicle. The network device generates a second license file based on the sharing request, including: the network device generates the second license file based on the sharing request and the information about the second vehicle.

[0187] Exemplarily, the second vehicle information includes first identification information for identifying the second vehicle and second identification information for identifying components within the second vehicle that support the first benefit. The first identification information is, for example, the vehicle identification code of the second vehicle, or an identification digest generated based on the vehicle identification code of the second vehicle. The second identification information is, for example, the identification of the components within the second vehicle that support the first benefit, or an identification digest generated based on the identification of the components within the second vehicle that support the first benefit.

[0188] Exemplarily, the second license file also includes the identification of the second vehicle, the identification of the first right, the identification of the components in the second vehicle that support the first right, and the second signature information. The second signature information is generated based on at least one other information in the second license file except the second signature information.

[0189] S206: The network-side device sends a second license file to the second vehicle.

[0190] Exemplarily, based on the system architecture shown in FIG1 , the network-side device sends the second license file to the second vehicle, including: the license issuing server sends the second license file to the license center, and then the license center sends the second license file to the second vehicle.

[0191] Correspondingly, the second vehicle receives the second license file from the network-side device, the second vehicle locally installs and activates the first license file, and reports the activation result of the second license file to the network-side device.

[0192] In this case, the interaction process between the network-side device, the first vehicle and the second vehicle is shown in Figure 4A, for example. Figure 4A is an interactive schematic diagram of vehicle equity sharing provided in an embodiment of the present application, which will not be repeated here.

[0193] Alternatively, in some possible embodiments, S207 may be executed instead of S206. For example, in a scenario where the second vehicle cannot communicate with the network-side device but the first vehicle can communicate with the network-side device, S207 may be executed instead of S206.

[0194] S207: The network-side device sends a second license file to the second vehicle through the first vehicle.

[0195] Exemplarily, the network-side device sends the second license file to the second vehicle through the first vehicle, including: the network-side device sends the second license file to the first vehicle, and the first vehicle sends the second license file to the second vehicle.

[0196] S207 is applied, for example, to a scenario where the second vehicle cannot communicate with the network-side device. In this case, the information of the second vehicle in S205 can be sent to the network-side device through the first vehicle, and the information of the second vehicle is, for example, carried in the sharing request; the activation result of the second license file in S206 can also be reported to the network-side device through the first vehicle.

[0197] In this case, the interaction process between the network-side device, the first vehicle and the second vehicle is shown in Figure 4B, for example. Figure 4B is another interactive schematic diagram of vehicle equity sharing provided in an embodiment of the present application, which will not be repeated here.

[0198] S208 : When the network-side device determines that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, the network-side device performs a deduction based on the sharing time information in the sharing request.

[0199] In one implementation, a network-side device determines that a first license file is locally activated in a first vehicle and a second license file is locally activated in a second vehicle, including: the network-side device receives a first activation result from the first vehicle and a second activation result from the second vehicle, wherein the first activation result indicates that the first license file is activated and the second activation result indicates that the second license file is activated; the network-side device determines that the first license file is activated based on the first activation result and determines that the second license file is activated based on the second activation result.

[0200] In another implementation, the network-side device determines that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, including: the network-side device receives a first activation result and a second activation result from the first vehicle, wherein the first activation result indicates that the first license file is activated and the second activation result indicates that the second license file is activated; the network-side device determines that the first license file is activated based on the first activation result and determines that the second license file is activated based on the second activation result.

[0201] Exemplarily, performing a deduction based on the sharing time information in the sharing request includes updating the locally recorded usable validity period of the first benefit corresponding to the first vehicle to the remaining validity period of the first benefit available for use by the first vehicle through the sharing request as specified in the first license file. Furthermore, upon determining that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, the network-side device further stores the corresponding relationship between the identifier of the second vehicle, the identifier of the first benefit, and the second license file.

[0202] As can be seen from S208, the network-side device uses the method of first activation and then deduction to cancel the validity period of the vehicle rights. In some possible embodiments, the network-side device may also use the method of first deduction and then verification to cancel the validity period of the vehicle rights. For example, when generating the first license file, the network-side device performs deduction based on the sharing time information in the sharing request, and stores the correspondence between the identifier of the second vehicle, the identifier of the first right and the second license file after generating the second license file. In this case, if the network-side device determines that any one of the above-mentioned first license file and the second license file fails to be activated (that is, the first vehicle fails to share the first right with the second vehicle this time), the network-side device will make up for the deducted period of the first right of the first vehicle and delete the locally stored identifier of the second vehicle, the identifier of the first right and the correspondence between the second license file, and the license file corresponding to the first right stored locally by the first vehicle will also be restored to the version before the update.

[0203] In some possible embodiments, the network-side device is only responsible for generating the first license file for the first vehicle, and the first vehicle generates the second license file for the second vehicle. In this case, the embodiment of Figure 2 above needs to execute S201-S205. Furthermore, the network-side device also sends an instruction message to the first vehicle (the order in which the instruction message and the first license file are sent to the first vehicle is not specifically limited). The instruction message is used to indicate that the first vehicle agrees to share the first rights with the second vehicle; in response to the instruction message, the first vehicle generates a second license file based on the sharing request and the information of the second vehicle; and the first vehicle sends the second license file to the second vehicle. Accordingly, the second vehicle locally installs and activates the second license file and sends the second activation result to the first vehicle. The first vehicle reports the second activation result to the network-side device, so that the network-side device executes the above S208. The first license file can, for example, be carried by the instruction message. This embodiment can be applied, for example, to a scenario where the second vehicle cannot communicate with the network-side device, in which case the first vehicle is responsible for issuing the license file for the second vehicle.

[0204] Here, the interaction process between the network-side device, the first vehicle and the second vehicle is shown in Figure 4C, which is an example of an interaction diagram of another vehicle equity sharing provided in an embodiment of the present application, and will not be repeated here.

[0205] Furthermore, when communication between the second vehicle and the network-side device is restored, the first vehicle can report to the network-side device the information that the first vehicle has issued a second license file for the second vehicle. The network-side device can locally store the second license file or the network-side device can re-issue the license file for the second vehicle and send the newly issued license file to the second vehicle.

[0206] In the method embodiment shown in Figure 2, the network-side device supports the sharing of vehicle benefits. The vehicle can share the subscribed vehicle benefits with other vehicles through the network-side device. Compared with the fact that vehicles can only experience vehicle benefits through subscription, this not only helps to lower the experience threshold of vehicle benefits, improve the coverage and utilization rate of vehicle benefits, but also makes the use of vehicle benefits more flexible.

[0207] The method described in the embodiment of Figure 2 above is applicable to scenarios where the first vehicle and the network device are communicating well. In some possible embodiments, network communication between the vehicle and the network device may fail, preventing the network device from issuing a license file for the vehicle. In this case, vehicles can share vehicle rights through vehicle-to-vehicle communication, as described in the embodiment of Figure 5 below.

[0208] See Figure 5, which is a flowchart of another vehicle equity sharing method provided in an embodiment of the present application. This method is applied to the vehicle equity sharing system shown in Figure 1, which includes network-side equipment, a first vehicle, and a second vehicle. The first vehicle serves as the sharing end of vehicle equity, and the second vehicle serves as the receiving end of the shared vehicle equity. This method includes, but is not limited to, the following steps shown in Figure 5.

[0209] S501: The first vehicle generates a sharing request.

[0210] The sharing request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information. This step can be specifically referred to the description of S201 in the embodiment of Figure 2 and will not be repeated here.

[0211] S502: The first vehicle sends a sharing request to the second vehicle.

[0212] Correspondingly, the second vehicle receives the sharing request from the first vehicle.

[0213] In one implementation, before a first vehicle generates a sharing request, it broadcasts a probe request to identify other vehicles seeking to share the vehicle. The first vehicle receives responses to the probe request from multiple vehicles and determines a second vehicle from the multiple vehicles based on a selection strategy.

[0214] Exemplarily, the selection strategy includes at least one of the following conditions: a vehicle currently closest to the first vehicle, a vehicle that responds fastest to the detection request, a vehicle with the strongest network signal strength, and a vehicle associated with the owner of the first vehicle.

[0215] S503: The second vehicle sends feedback information to the first vehicle.

[0216] Accordingly, the first vehicle receives feedback information from the second vehicle.

[0217] The feedback information indicates that the second vehicle accepts the first vehicle's sharing of the first benefit. It is understood that when the second vehicle receives the sharing request from the first vehicle and determines through self-inspection that it has components that support the first benefit, the second vehicle sends feedback information to the first vehicle.

[0218] In one implementation, the feedback information includes information about the second vehicle, wherein the information about the second vehicle includes first identification information for indicating the second vehicle and second identification information for indicating a component in the second vehicle that supports the first benefit.

[0219] As an example, considering the security of vehicle-to-vehicle communication, the first identification information is, for example, an identification digest generated based on the identification of the second vehicle, and the second identification information is, for example, an identification digest generated based on the identification of a component in the second vehicle that supports the first right.

[0220] S504: The first vehicle generates a target license file according to the feedback information and the sharing request.

[0221] The target license file includes the validity period of the first benefit that the second vehicle can use, and the identification information of the first vehicle. The first benefit that the second vehicle can use is shared with the first vehicle. The validity period of the first benefit that the second vehicle can use is related to the sharing time information in the sharing request. The identification information of the first vehicle is, for example, an identification digest generated based on the identification of the first vehicle.

[0222] In one implementation, the first vehicle generates a target license file according to the feedback information and the sharing request, including: the first vehicle generates the target license file according to the information of the second vehicle in the feedback information and the sharing request.

[0223] Exemplarily, the target license file also includes the above-mentioned first identification information (for example, an identification summary generated based on the identification of the second vehicle), second identification information (for example, an identification summary generated based on the identification of the component in the second vehicle that supports the first right), the identification of the first right and the target signature information, where the target signature information is generated based on at least one other information in the target license file other than the target signature information.

[0224] S505: The first vehicle sends the target license file to the second vehicle.

[0225] Correspondingly, the second vehicle receives the target license file from the first vehicle.

[0226] After the second vehicle receives the target license file, the second vehicle locally installs and activates the target license file, and feeds back the activation result of the target license file to the first vehicle.

[0227] When the first vehicle receives a reply from the second vehicle indicating that the target license file has been activated, the first vehicle deducts the valid period of the first benefit stored locally on the first vehicle based on the sharing time information. In some possible embodiments, the first vehicle may also deduct the valid period of the first benefit stored locally on the first vehicle based on the sharing time information. In this case, if the second vehicle responds that the license file activation failed, the first vehicle must refund the deducted valid period.

[0228] In an embodiment of the present application, although the first vehicle can issue a license file for the second vehicle, in order to keep the information recorded by the network-side device consistent, the following steps S506-S509 can also be executed when the network communication between the first vehicle and the network-side device is restored.

[0229] S506: The first vehicle sends sharing information to the network-side device.

[0230] The sharing information indicates that the first vehicle shares the first benefit with the second vehicle, which means that the second vehicle is a partner vehicle of the first vehicle.

[0231] For example, the shared information includes the sharing time information and the information of the second vehicle in S503. Furthermore, the shared information also includes the identification information of the first vehicle (eg, an identification summary generated based on the identification of the first vehicle).

[0232] The first vehicle, for example, periodically and proactively reports sharing information to the network-side device.

[0233] In some possible embodiments, the network-side device periodically queries the first vehicle to determine whether the license file used to enable the first benefit is consistent. If the network-side device determines that the locally stored license file of the first vehicle is inconsistent with the license file stored in the first vehicle for enabling the first benefit (for example, the first vehicle locally deducts the validity period of the first benefit, resulting in inconsistency between the license file stored by the network-side device and the first vehicle), the network-side device queries the first vehicle to determine whether the first vehicle has a partner vehicle. In response to the query, the first vehicle reports sharing information to the network-side device. It is understandable that if the first vehicle reports that there is no partner vehicle, the network-side device confirms that the report is abnormal and sends a disablement message, which is used to instruct the first vehicle to disable the local license file.

[0234] S507: The network-side device generates a first license file and a second license file based on the shared information.

[0235] Exemplarily, the network-side device locally stores a correspondence between the identification information of the first vehicle, the identification of the first vehicle, and the license file for the first vehicle. The network-side device searches for the license file for the first vehicle based on the identification information of the first vehicle in the sharing information and obtains the usable validity period of the first benefit corresponding to the first vehicle from the license file of the first vehicle. The network-side device determines the remaining validity period of the first benefit that can be used by the shared first vehicle based on the usable validity period of the first benefit and the sharing time information in the sharing information. The remaining validity period is included in the first license file.

[0236] For example, the network-side device searches for the second vehicle's information in the shared information to obtain the second vehicle's identifier and the identifier of the component in the second vehicle that supports the first benefit. The network-side device generates a second license file based on the sharing time information in the shared information, the second vehicle's identifier, and the identifier of the component in the second vehicle that supports the first benefit.

[0237] In addition, the network-side device also records the correspondence between the second vehicle and the first vehicle based on the information of the second vehicle in the shared information, which means that the second vehicle is the partner vehicle of the first vehicle.

[0238] Here, for the first license file, please refer to the description of the “first license file” in S203 of the embodiment of FIG. 2 , and for the second license file, please refer to the description of the “second license file” in S205 of the embodiment of FIG. 2 . For the sake of brevity, they will not be described here.

[0239] That is to say, the license file (such as the target license file) issued by the first vehicle to the second vehicle is a temporary license file, and the network-side device reissues a new license file for the first vehicle and the second vehicle based on the sharing information reported by the first vehicle.

[0240] S508: The network-side device sends the first license file to the first vehicle. Please refer to the description of the corresponding content in the above S203 for this step.

[0241] S509: The network-side device sends the second license file to the second vehicle. This step is described in S206 above and will not be repeated here.

[0242] In this case, the interaction process between the network-side device, the first vehicle and the second vehicle is shown in Figure 6, which is another interactive schematic diagram of vehicle equity sharing provided in an embodiment of the present application and will not be repeated here.

[0243] In some possible embodiments, when the network-side device determines that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, the network-side device updates the locally stored license file of the first vehicle to the first license file, and stores the corresponding relationship between the identification information of the second vehicle, the identification of the second vehicle, the identification of the first benefit, and the second license file. This implementation method can be referred to the description of the corresponding content in the embodiment S208 of Figure 2 above, and will not be repeated here.

[0244] In the method embodiment shown in Figure 5, a vehicle can independently issue license files to share its subscribed vehicle benefits with other vehicles without relying on network-side equipment. Compared to vehicles that can only experience vehicle benefits through subscription, this helps lower the threshold for experiencing vehicle benefits and improves the coverage of vehicle benefits. In addition, the method of the embodiment of Figure 5 can be applied in scenarios where network communication between the vehicle and network-side equipment is abnormal or fails, making the use of vehicle benefits more flexible.

[0245] 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 30 includes a processing unit 310 and a sending unit 312. The communication device 30 can be implemented in hardware, software, or a combination of hardware and software.

[0246] In one implementation, the communication device 30 is the vehicle that generates the sharing request (eg, the first vehicle) or is included in the first vehicle.

[0247] The processing unit 310 is used to generate a sharing request, which is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; the sending unit 312 is used to send the sharing request.

[0248] The communication device 30 is used to implement the first vehicle-side method described in the embodiment of FIG2 . In the embodiment of FIG2 , the processing unit 310 is used to execute S201 and S204 , and the sending unit 312 is used to execute S202 and S207 . The communication device 30 is also used to implement the first vehicle-side method described in the embodiment of FIG5 , which will not be detailed here for the sake of brevity.

[0249] In another implementation, the communication device 30 is the network-side device deployed in the cloud or is included in the network-side device. In this case, the communication device 30 further includes a receiving unit 314.

[0250] Among them, the receiving unit 314 is used to obtain a first request (i.e., the above-mentioned sharing request), the first request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the first request includes sharing time information; the processing unit 310 is used to generate a first license file based on the first request, and the first license file includes the remaining validity period of the first benefit that the first vehicle can use through the sharing; the sending unit 312 is used to send the first license file to the first vehicle.

[0251] The communication device 30 can be used to implement the network-side device-side method described in the embodiment of FIG2 . In the embodiment of FIG2 , the receiving unit 314 is used to execute S202 , the processing unit 310 is used to execute S203 , S205 , and S208 , and the sending unit 312 is used to execute S203 , S206 , and S207 . The communication device 30 can also be used to implement the network-side device-side method described in the embodiment of FIG5 , which will not be described in detail here for the sake of brevity.

[0252] 8 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device 40 includes a receiving unit 410. The communication device 40 can be implemented in hardware, software, or a combination of hardware and software.

[0253] Exemplarily, the communication device 40 is a sharing object of the vehicle benefit (eg, a second vehicle) or is included in the second vehicle.

[0254] Among them, the receiving unit 410 is used to receive a sharing request, which is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; the receiving unit 410 is also used to obtain a target authorization license file, which is used for the second vehicle to activate the first benefit, and the target license file includes the validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle.

[0255] The communication device 40 is used to implement the method on the second vehicle side described in the embodiment of Figure 2. In the embodiment of Figure 2, the receiving unit 410 is used to execute S206 and S207. The communication device 40 is also used to implement the method on the second vehicle side described in the embodiment of Figure 5. In this case, the communication device 40 also includes a sending unit (not shown) for sending feedback information to the first vehicle. For the sake of brevity, this will not be repeated here.

[0256] It should be understood that the division of the various units in the above communication devices (e.g., communication device 30 or communication device 40) is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or they may be physically separated. In addition, the units in the device may be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or the functions of the various units of the device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0257] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the processor loads a configuration document to implement the process of hardware circuit configuration, which can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0258] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0259] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0260] Referring to Figure 9 , which is a schematic diagram of the structure of a vehicle equity sharing device provided in an embodiment of the present application, as shown in Figure 9 , the vehicle equity sharing device 50 includes a processor 501 , a communication interface 502 , a memory 503 , and a bus 504 . The processor 501 , the memory 503 , and the communication interface 502 communicate with each other via the bus 504 .

[0261] It should be understood that the present application does not limit the number of processors and memories in the vehicle equity sharing device 50 .

[0262] In one implementation, the vehicle equity sharing device 50 is the network-side device in the above-described implementation. The network-side device may be, for example, a network-side server (e.g., a license authorization center or a license issuance server), or a system-level device consisting of a license authorization center and a license issuance server, or a system-level device consisting of a rights operation platform, a license authorization center, and a license issuance server. The network-side device may be deployed in a cloud environment or an edge environment, for example, without specific limitation herein.

[0263] In another implementation, the vehicle equity sharing device 50 is the aforementioned vehicle or a device contained in a vehicle. Here, the vehicle is, for example, a vehicle that shares vehicle equity (eg, a first vehicle) or a subject of vehicle equity sharing (eg, a second vehicle).

[0264] Bus 504 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses can be categorized as address buses, data buses, control buses, and so on. For ease of illustration, FIG9 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 504 may include a pathway for transmitting information between the various components of the vehicle equity sharing device 50 (e.g., memory 503, processor 501, and communication interface 502).

[0265] The processor 501 can refer to the relevant description of the processor in the above embodiment, which will not be repeated here.

[0266] Memory 503 is used to provide storage space for storing data such as the operating system and computer programs. Memory 503 can be one or a combination of random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM). Memory 503 can exist independently or be integrated into processor 501.

[0267] The communication interface 502 can be used to provide information input or output for the processor 501. Alternatively, the communication interface 502 can be used to receive data transmitted externally and / or transmit data externally. It can be a wired link interface such as an Ethernet cable, or a wireless link interface (such as Wi-Fi, Bluetooth, general wireless transmission, etc.). Alternatively, the communication interface 502 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) or a receiver coupled to the interface.

[0268] In some possible embodiments, the vehicle equity sharing device 50 further includes a display 505. The display 505 is connected or coupled to the processor 501 via a bus 504. The display 505 can be used to indicate to the user the equity sharing attributes to be set. The display 505 can be a display screen, which can be a liquid crystal display (LCD), an organic or inorganic light-emitting diode (OLED), an active matrix organic light-emitting diode (AMOLED), etc. The display 505 can also be a vehicle-mounted tablet, an onboard display, or a head-up display (HUD) system.

[0269] The processor 501 in the vehicle equity sharing device 50 is used to read the computer program stored in the memory 503 to execute the aforementioned method, such as the method described in FIG. 2 or FIG. 5 .

[0270] In one possible design, the vehicle equity sharing device 50 is one or more modules in an execution entity (e.g., a first vehicle) that executes the method shown in FIG. 2 . The processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0271] Generate a sharing request, where the sharing request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information;

[0272] The sharing request is sent via the sending unit 312 .

[0273] In one possible design, the vehicle equity sharing device 50 is one or more modules in an execution entity (e.g., a network-side device) that executes the method shown in FIG2 . The processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0274] The receiving unit 314 obtains a first request (i.e., the aforementioned sharing request), wherein the first request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the first request includes sharing time information;

[0275] generating a first license file based on the first request, the first license file including a remaining validity period of the first benefit that can be used via the shared first vehicle;

[0276] The first license file is sent to the first vehicle via the sending unit 312 .

[0277] In one possible design, the vehicle equity sharing device 50 is one or more modules in an execution entity (e.g., a second vehicle) that executes the method shown in FIG5 . The processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0278] A sharing request is received through the receiving unit 410, where the sharing request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; and a target authorization license file is obtained, where the target license file is used to enable the first benefit for the second vehicle, and the target license file includes a validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle.

[0279] In the embodiments described above, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. In addition, in the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0280] It should be noted that, those skilled in the art can see that all or part of the steps in the various methods of the above embodiments can be completed by a program to instruct relevant hardware. The program can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0281] The technical solution of the present application may essentially or contribute to the part or all or part of the technical solution in the form of a software product. The computer program product is stored in a storage medium and includes a number of instructions for enabling a device (which may be a personal computer, a server, or a network device, a robot, a single-chip microcomputer, a chip, a robot, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.

Claims

1. A vehicle equity sharing method, characterized in that: The method is applied to a first vehicle, and includes: generating a sharing request, the sharing request being used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, the sharing request including sharing time information; Send the sharing request.

2. The method according to claim 1, characterized in that The sharing time information includes at least one of the following information: The duration of the sharing, the start date of the sharing, the end date of the sharing, and the period of time during which the first benefit can be used.

3. The method according to claim 1 or 2, characterized in that The sending of the sharing request includes: Sending the sharing request to the network side device; The method further comprises: receiving a first authorization license file sent by the network-side device, wherein the first license file is associated with the sharing request, the first license file includes a remaining validity period during which the first vehicle can use the first benefit, and the remaining validity period is associated with the sharing time information; The locally stored license file corresponding to the first right is updated to the first license file.

4. The method according to claim 3, characterized in that The method further comprises: receiving a second license file sent by a network-side device, where the second license file includes a validity period for the second vehicle to use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle; Send the second license file to the second vehicle.

5. The method according to claim 3 or 4, characterized in that The sharing request also includes at least one of the following information: an identification of the first vehicle; an identifier of the first interest; an identification of the second vehicle; The order number of the first vehicle for ordering the first benefit; and A license file corresponding to the first benefit stored locally in the first vehicle.

6. The method according to claim 1 or 2, characterized in that The sending of the sharing request includes: sending the sharing request to the second vehicle; The method further comprises: receiving feedback information sent by the second vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, the feedback information including information about the second vehicle; A second license file is sent to the second vehicle. The second license file includes a validity period during which the second vehicle can use the first benefit and an identifier of the first vehicle. The first benefit that the second vehicle can use is shared with the first vehicle. The second license file is obtained by the first vehicle based on the sharing request and information about the second vehicle.

7. The method according to claim 6, characterized in that The method further comprises: When a reply is received from the second vehicle indicating that the second license file has been activated, the usable validity period of the first benefit locally stored in the first vehicle is deducted according to the sharing time information.

8. The method according to claim 6 or 7, characterized in that The method further comprises: Sharing information is sent to the network-side device, where the sharing information indicates that the first vehicle has shared the first equity with the second vehicle.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Indicating to the user the equity sharing attributes to be set, the equity sharing attributes including the equity to be shared, the identifier of the target vehicle to be shared, and the sharing time information corresponding to the equity; Generating a sharing request includes: Receive setting information of the user, and generate the sharing request based on the setting information.

10. A vehicle equity sharing method, characterized in that: The method comprises: Obtaining a first request, where the first request is used to instruct a first vehicle to apply to share a first benefit subscribed by the first vehicle with a second vehicle, and the first request includes sharing time information; generating a first authorization license file based on the first request, wherein the first license file includes a remaining validity period for using the first benefit through the sharing of the first vehicle; Send the first license file to the first vehicle.

11. The method according to claim 10, characterized in that The first request also includes the identification of the first vehicle and the identification of the first benefit. The remaining validity period is determined based on the usable validity period of the first benefit and the sharing time information. The usable validity period of the first benefit is obtained from the license file found based on the identification of the first vehicle and the identification of the first benefit.

12. The method according to claim 10 or 11, characterized in that The method further comprises: generating a second license file based on the first request, wherein the second license file includes a validity period during which the second vehicle can use the first benefit, and the first benefit that the second vehicle can use is shared with the first vehicle; Send the second license file to the second vehicle or the first vehicle.

13. The method according to claim 12, characterized in that After obtaining the first request, the method further includes: Sending a second request to the second vehicle, where the second request is used to inquire whether the second vehicle accepts the first vehicle's sharing of the first equity; receiving feedback information sent by the second vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, the feedback information including information about the second vehicle; Generating a second license file based on the first request includes: The second license file is generated based on the first request and the information of the second vehicle.

14. The method according to claim 12 or 13, characterized in that The method further comprises: When it is determined that the first license file is locally activated in the first vehicle and the second license file is locally activated in the second vehicle, the locally recorded usable validity period of the first benefit corresponding to the first vehicle is updated to the remaining validity period, and the correspondence between the identifier of the second vehicle, the identifier of the first benefit, and the second license file is stored.

15. The method according to any one of claims 10 to 14, characterized in that: The sharing time information includes at least one of the following information: The duration of the sharing, the start date of the sharing, the end date of the sharing, and the period of time during which the first benefit can be used.

16. A vehicle equity sharing method, characterized in that: The method is applied to a second vehicle, and includes: receiving a sharing request, the sharing request being used to instruct a first vehicle to apply to share a first benefit subscribed by the first vehicle with a second vehicle, the sharing request including sharing time information; Obtain a target authorization license file, where the target license file is used to enable the first benefit for the second vehicle. The target license file includes a validity period during which the second vehicle can use the first benefit. The first benefit that the second vehicle can use is shared with the first vehicle.

17. The method according to claim 16, characterized in that The sharing time information includes at least one of the following information: The duration of the sharing, the start date of the sharing, the end date of the sharing, and the period of time during which the first benefit can be used.

18. The method according to claim 16 or 17, characterized in that The receiving the sharing request includes: receiving the sharing request sent by the network side device; The method further includes: sending feedback information to the network-side device, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, the feedback information including information about the second vehicle; The acquiring of the target authorization license file includes: receiving the target license file sent by the network-side device, wherein the target license file is associated with the sharing request and the information of the second vehicle.

19. The method according to claim 16 or 17, characterized in that The receiving the sharing request includes: receiving the sharing request sent by the first vehicle; The method further includes: sending feedback information to the first vehicle, the feedback information indicating that the second vehicle accepts the first vehicle's sharing of the first equity, the feedback information including information of the second vehicle; The acquiring of the target authorization license file includes: receiving the target license file sent by the first vehicle, wherein the target license file is associated with the sharing request and information of the second vehicle.

20. A device for sharing vehicle rights and interests, characterized in that: The device is a first vehicle or is included in the first vehicle, and the device includes: a processing unit, configured to generate a sharing request, wherein the sharing request is used to instruct the first vehicle to apply to share the first benefit subscribed by the first vehicle with the second vehicle, and the sharing request includes sharing time information; A sending unit is configured to send the sharing request.

21. A device for sharing vehicle rights and interests, characterized in that: The device comprises: A receiving unit, configured to obtain a first request, wherein the first request is used to instruct a first vehicle to apply to share a first benefit subscribed by the first vehicle with a second vehicle, the first request including sharing time information; a processing unit, configured to generate a first authorization license file based on the first request, wherein the first license file includes a remaining validity period for using the first benefit through the sharing of the first vehicle; A sending unit is used to send the first license file to the first vehicle.

22. A device for vehicle equity sharing, characterized in that: The device is a second vehicle or is contained in the second vehicle, and the device includes: a receiving unit, configured to receive a sharing request, wherein the sharing request is used to instruct a first vehicle to apply to share a first benefit subscribed by the first vehicle with a second vehicle, the sharing request including sharing time information; The receiving unit is further configured to obtain a target authorization license file, where the target license file is used for the second vehicle to enable the first benefit. The target license file includes a validity period during which the second vehicle can use the first benefit. The first benefit that the second vehicle can use is shared with the first vehicle.

23. A device for sharing vehicle rights and interests, characterized in that: The device includes a memory and a processor, the memory storing computer program instructions, and the processor executing the computer program instructions to enable the device to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 15, or the method according to any one of claims 16 to 19.

24. A vehicle equity sharing system, characterized in that: The system includes a first device and a second device, or includes a first device, a second device and a third device, wherein the first device is used to implement the method according to any one of claims 1 to 9, the second device is used to implement the method according to any one of claims 16 to 19, and the third device is used to implement the method according to any one of claims 10 to 15.

25. A vehicle, characterized in that: The vehicle comprises the apparatus according to claim 20 or comprises the apparatus according to claim 22.

26. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 9, or implement the method according to any one of claims 10 to 15, or the method according to any one of claims 16 to 19.

Images