Authorization method and device, terminal, vehicle end and storage medium

Abstract

The invention discloses an authorization method and device, a terminal, a vehicle end and a storage medium, and relates to the field of automatic driving. According to the method, the right to use the first driving system is provided for the first user through the related information of the first driving system and the related information of the authorized system of the first user, and the right to use the first driving system can be provided for the first user without redundant operation, so that the authorization process is simplified, and the user experience is improved. And the use experience of the first user is improved. In addition, the invention also shows triggering conditions and triggering opportunities of a plurality of authorization methods, so that the application range of the authorization methods is enriched, and the experience of the user in the authorization process is comprehensively improved as much as possible.

Description

Authorization methods, devices, terminals, vehicle-mounted devices, and storage media Technical Field

[0001] This application relates to the field of autonomous driving, and more particularly to an authorized method, device, terminal, vehicle-mounted device, and storage medium. Background Technology

[0002] With the development of technology, more and more systems are being installed on mobility devices to enhance the intelligent experience for drivers and passengers and improve driving safety. Examples include driving systems, cockpit systems, and driving control systems.

[0003] As system functions increase, authorization is typically required to meet security and privacy requirements. For example, users can gain access to some or all functions of the cockpit system through learning and examination. However, the numerous versions and rapid updates of systems on mobility devices make the authorization process for drivers and passengers quite complex.

[0004] Summary of the Invention

[0005] This application provides an authorization method, device, terminal, vehicle terminal, and storage medium, relating to the field of autonomous driving. This authorization method can improve the ease with which users can obtain system permissions, thereby providing users with a better product experience.

[0006] In a first aspect, embodiments of this application provide an authorization method, comprising: granting a first user the right to use the first driving system based on relevant information of the first driving system and relevant information of the system already authorized to the first user.

[0007] This application embodiment provides the first user with the right to use the first driving system by using the relevant information of the first driving system and the relevant information of the system that the first user has been authorized to use. This allows the first user to be granted the right to use the first driving system without any extra operations, thereby simplifying the authorization process and improving the user experience of the first user.

[0008] Optionally, the relevant information of the aforementioned driving system includes one or more of the following: the driving system identifier, the driving system system characteristics, or the scope of the driving system usage rights. The driving system identifier is used to identify the driving system and can be its name, ID, or unique code. The driving system characteristics include one or more of the following: followed regulations, followed standards, passed assessments, certification levels, followed specifications, followed guidelines, suppliers, or functions. The scope of the driving system usage rights can be understood as the range of driving systems that can be used within the scope of the target driving system usage rights. For example, if the scope of the usage rights for driving system A includes driving systems B and C, then having the right to use driving system A also allows the use of driving systems B and C. It should be noted that the scope of the driving system usage rights and the standards for setting the scope of the driving system usage rights can be set by the driving system supplier.

[0009] In one possible implementation, the authorization method further includes: obtaining the identifier of the first driving system and the identifier of the first user, determining relevant information of the first driving system based on the identifier of the first driving system, and determining relevant information of the first user that has been authorized by the system based on the identifier of the first user.

[0010] Optionally, the identifier of the first driving system and the identifier of the first user can be obtained by receiving request information from the first user. For example, receiving request information from the first user, which requests the use of the first driving system, and the request information includes the identifier of the first driving system and the identifier of the first user.

[0011] Optionally, the identifiers of the first driving system and the first user can also be obtained by setting preset trigger conditions. For example, when the first user or the vehicle associated with the first user is detected to be in a preset state, or about to be in a preset state, the identifiers of the first driving system and the first user are obtained. This application does not limit the preset state; for example, the preset state can be a state set by the system supplier, the vehicle supplier, the first user, or other users.

[0012] It is understood that the triggering conditions for obtaining the identifier of the first driving system and the identifier of the first user in this application can be actively triggered by the user by initiating a request, or can be automatically triggered by setting preset triggering conditions.

[0013] In another possible implementation, based on relevant information about the first driving system and relevant information about the systems the first user has been authorized to use, granting the first user access to the first driving system includes: determining whether the first user's scope of authority includes the first driving system based on the relevant information about the first driving system and the systems the first user has been authorized to use. If the first user's scope of authority includes the first driving system, then granting the first user access to the first driving system. If the first user's scope of authority does not include the first driving system, then providing the first user with training information on the first driving system allows the first user to acquire access to the first driving system through training.

[0014] In the above embodiments, when the first user's scope of authority includes the first driving system, providing the first user with the right to use the first driving system simplifies the steps for the first user to obtain this right and improves the user experience. When the first user's scope of authority does not include the first driving system, providing the first user with training information on the first driving system allows them to acquire the right to use it through training. This enables the first user to master the usage methods and features of the first driving system, thereby ensuring the first user can use it safely.

[0015] In another possible implementation, information related to the first driving system includes the conditions under which the right to use the first driving system can be obtained.

[0016] In the above embodiments, the relevant information of the first driving system, including the conditions under which the right to use the first driving system can be obtained, allows the determination of whether to grant the first user the right to use the first driving system by judging whether the relevant information of the driving system authorized by the first user meets the conditions under which the right to use the first driving system can be obtained. This simplifies the authorization process and improves the user experience of the first user.

[0017] Optionally, the conditions under which the right to use the first driving system can be obtained can be set by the supplier of the first driving system. Of course, the conditions under which the right to use the first driving system can also be updated. For example, if the regulations or standards related to the first driving system change, the conditions under which the right to use the first driving system can be updated accordingly.

[0018] In another possible implementation, the conditions under which the right to use the first driving system is permitted to be acquired include one or more of the following: required training, association between driving systems, or coverage of the right to use between driving systems.

[0019] In the above embodiments, the required training can be understood as acquiring the right to use the first driving system by completing the target training. The interrelationships between driving systems can be understood as acquiring the right to use the first driving system by analyzing the interrelationships between driving systems, for example, by analyzing the interrelationships of system features between driving systems. For a description of the coverage relationships of the right to use between driving systems, please refer to the corresponding descriptions above.

[0020] Optionally, if there are multiple conditions under which the right to use the first driving system can be obtained, the determination of whether the right to use the first driving system can be provided to the first user can be made by sequentially judging the coverage relationship of the right to use between driving systems, the correlation relationship between driving systems, and the required training.

[0021] In another possible implementation, system features include one or more of the following: regulations, standards, assessments, certification levels, specifications, guidelines, suppliers, or functions.

[0022] The above embodiments illustrate various system features. The relationship between driving systems can be determined using a single system feature, or by combining multiple system features; this application does not limit this approach. Of course, in addition to the system features listed in this application, other system features can also be used to determine the relationship between driving systems. For example, the relationship can also be determined based on the system's usage method.

[0023] In another possible implementation, based on relevant information about the first driving system and relevant information about the system the first user has been authorized to use, the right to use the first driving system is granted to the first user, including: determining first training based on the training corresponding to the first driving system and the training already completed by the first user; providing the first user with training information corresponding to the first training and receiving first instruction information; and granting the first user the right to use the first driving system if the first instruction information indicates that the first user has completed the training.

[0024] Based on the above description, it can be understood that the above implementation method is used to introduce the right to use the first driving system through training. In the above implementation method, the training corresponding to the first driving system refers to the training required to obtain the first driving system. For example, if the first driving system includes multiple functions, and each function corresponds to a training session, then the training corresponding to the first driving system includes the training corresponding to each function in the first driving system. The aforementioned first training refers to the training that the first user has not yet completed within the training corresponding to the first driving system. By providing the first user with the training information corresponding to the first training, and granting the first user the right to use the first driving system only after the first user has completed the training information corresponding to the first training, repetitive training for the first user can be avoided, thereby reducing the time spent by the first user on training, simplifying the authorization process, and improving the user experience.

[0025] Optionally, the relevant information about the first driving system includes the conditions under which the right to use the first driving system can be obtained and the corresponding training. The conditions under which the right to use the first driving system can be obtained include the required training. The relevant information about the first user being authorized to the system includes the training that the first user has completed.

[0026] In another possible implementation, after granting the first user access to the first driving system, the method further includes: expanding the first user's scope of permissions based on relevant information about the first driving system.

[0027] In the above embodiments, the right to use the first driving system is acquired through "required training." That is, once the first user completes new training, their scope of authority can be expanded using relevant information from the first driving system. For example, this can be achieved through "associations between driving systems" or "overriding relationships of usage rights between driving systems." By expanding the first user's scope of authority through relevant information from the first driving system, this embodiment maximizes the scope of authority acquired through training, thereby avoiding redundant training, simplifying the authorization process, and improving the user experience.

[0028] It is understandable that, based on information from the first driving system, expanding the first user's permission scope can be achieved by analyzing the correlation between the system characteristics of the first driving system and the system characteristics of systems not authorized by the first user. Alternatively, it can be achieved by expanding the first user's permission scope based on the coverage of the first driving system's usage rights.

[0029] In another possible implementation, the right to use the first driving system is provided to the first user based on relevant information of the first driving system and relevant information of the system authorized by the first user, including: providing the right to use the first driving system to the first user based on the system characteristics of the first driving system and the system characteristics of the system authorized by the first user.

[0030] The above implementation method can analyze whether there is a relationship between the first driving system and the authorized system of the first user by analyzing the system characteristics of the first driving system and the authorized system of the first user. For example, they may have the same function, the same operation method, or follow the same laws and regulations. If there is a relationship between the first driving system and the authorized system of the first user, the right to use the first driving system can be provided to the first user. On the one hand, this simplifies the authorization process, and on the other hand, it can ensure the safety of the first user when using the first driving system.

[0031] In another possible implementation, the right to use the first driving system is granted to the first user if the system characteristics of the first driving system and the system characteristics of the first user being authorized by the system meet one or more of the following conditions.

[0032] The first driving system and the first user have been authorized by the system to follow the same regulations, or,

[0033] The first driving system and the first user have been authorized by the system to follow the same standards, or,

[0034] The first user has been authorized to follow the standards of the system, including the standards followed by the first driving system; or...

[0035] The first driving system and the first user have passed the same evaluation by the authorized system, or,

[0036] The first driving system and the first user have the same authentication level as the authorized system, or,

[0037] The first driving system and the first user have been authorized by the system to follow the same specifications, or,

[0038] The first driving system and the first user have been authorized by the system to follow the same guidelines, or,

[0039] The supplier of the first driving system is the same as the supplier of the system authorized by the first user, or...

[0040] The first user has been authorized to use the functions of the first driving system; or...

[0041] The functions of the first driving system are the same as those of the first user's authorized system.

[0042] The above embodiments provide various scenarios for granting the first user the right to use the first driving system, thereby simplifying the process of granting the first user the right to use the first driving system. It is understood that the system features in this application are not limited to those shown above; therefore, this application can also grant the first user the right to use the first driving system in other ways. For example, the right to use the first driving system can be granted to the first user when the operating method of the first driving system is the same as that of a system already authorized by the first user.

[0043] Optionally, the various scenarios described above regarding providing the first user with the right to use the first driving system can be set by the supplier of the first driving system.

[0044] In another possible implementation, based on relevant information of the first driving system and relevant information of the first user's authorized system, the right to use the first driving system is provided to the first user, including: the coverage relationship of the right to use the first driving system, and / or the coverage relationship of the first user's authorized system, indicating that the first user's authorized system right to use covers the right to use the first driving system, and in the case where the first user's authorized system right to use covers the right to use the first driving system, the right to use the first driving system is provided to the first user.

[0045] In the above embodiments, the coverage relationship of the right to use the first driving system can be used to indicate which driving systems' right to use can cover the right to use the first driving system. For example, if the coverage relationship of the right to use the first driving system indicates that the right to use the second and third driving systems can cover the right to use the first driving system, then when the first user has been authorized to use systems including the second or third driving system, it can be considered that the coverage relationship of the right to use the first driving system indicates that the first user's right to use systems authorized by the first user covers the right to use the first driving system. The coverage relationship of the right to use systems authorized by the first user can be used to indicate which driving systems the first user's authorized right to use can cover. Therefore, through the above embodiments, the process of authorizing the first user can be simplified, thereby improving the user experience.

[0046] In another possible implementation, the conditions under which the right to use the first driving system can be obtained also include: system usage duration, and / or, violation information.

[0047] In the above embodiments, the condition for obtaining system usage time can be understood as the duration of time the target driving system is used by the target user needing to meet preset conditions. For example, when determining whether to grant the first user the right to use the first driving system, it is necessary to determine whether the first user's authorized system usage time meets the preset conditions. If the preset conditions are met, further judgment is made; if the preset conditions are not met, the first user needs to be granted the right to use the first driving system through training. For example, the condition for "system usage time" is that the first user's usage time of the first user's authorized system is greater than or equal to a first threshold.

[0048] In the above embodiments, the condition for obtaining violation information can be understood as whether the target user's usage record of the target driving system includes any valid violation information. For example, when determining whether to grant the first user the right to use the first driving system, it is necessary to determine whether the first user's usage record of the first user's authorized system includes any valid violation information. If it does not include any valid violation information, further determination is made. If it does include valid violation information, it is necessary to grant the first user the right to use the first driving system through training. For example, the condition for "violation information" is that the first user's usage record of the first user's authorized system does not include any valid violation information.

[0049] It should be noted that the aforementioned target user can be a user requesting to use the first driving system, and the aforementioned target driving system can be a driving system that the target user has authorized.

[0050] In another possible implementation, the relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained, the conditions under which the right to use the first driving system is permitted to be obtained include the system usage duration, and the relevant information of the first user being authorized to the system includes the system usage duration of the first user being authorized to the system.

[0051] Based on the relevant information of the first driving system and the relevant information of the system authorized by the first user, the right to use the first driving system is provided to the first user, including: when the first user uses the system authorized by the first user for a duration greater than or equal to a first threshold, the right to use the first driving system is provided to the first user.

[0052] In the above embodiments, the conditions for obtaining the right to use the first driving system include system usage time. Before a first user obtains the right to use the first driving system, it needs to be determined whether the first user's usage time in the authorized systems is greater than or equal to a first threshold. If the first user's usage time in the authorized systems is greater than or equal to the first threshold, then the first user is granted the right to use the first driving system. It should be noted that the aforementioned usage time in the authorized systems being greater than or equal to the first threshold can be the usage time of systems associated with the first driving system within the authorized systems, or it can be the usage time of systems within the authorized systems that have an overlapping relationship with the right to use the first driving system. Through the above embodiments, it can be ensured that the first user has a high level of proficiency in using the authorized systems, thereby ensuring that after obtaining the first driving system, the first user is also relatively familiar with its use and can quickly get started, avoiding dangerous accidents caused by unfamiliarity with driving.

[0053] In another possible implementation, the relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained, the conditions under which the right to use the first driving system is permitted to be obtained include violation information, and the relevant information of the first user authorized to the system includes the first user's authorized system usage records.

[0054] Based on the relevant information of the first driving system and the relevant information of the system authorized by the first user, the right to use the first driving system is provided to the first user, including: the first user's usage record of the system authorized by the first user does not include any violation information that is still valid, thus providing the first user with the right to use the first driving system.

[0055] In the above embodiments, the condition for granting access to the first driving system is the inclusion of violation information. Before a first user can obtain access to the first driving system, it is necessary to determine whether the user's usage records in the authorized system include any expired violation information. If the user's usage records in the authorized system do not include expired violation information, then access to the first driving system is granted to the first user. It should be noted that the aforementioned usage records in the authorized system can be usage records of systems associated with the first driving system within the authorized system, or usage records of systems within the authorized system that have an overlapping relationship with the access to the first driving system. Through these embodiments, it can be ensured that first users follow the usage rules and correctly use the authorized system, thereby preventing the granting of access to related systems to users when the authorized system is suspended.

[0056] In another possible implementation, the method further includes: determining the first user's first usage record based on the first user's identifier; and determining, based on the first usage record, that the first user has been authorized by the system.

[0057] In the above embodiments, the first usage record is the historical record of the first user's use of the driving system. Determining that the first user has been authorized by the system through the first usage record helps to quickly determine whether the first user has used the first driving system, thereby reducing authorization time or the time it takes for the first user to activate the first driving system.

[0058] In another possible implementation, the first use record is used to describe the correspondence between the vehicle identifier, the driving system identifier, and the time period during which the driving system is used.

[0059] In the above embodiments, the identifier of the first driving system can be used to search the first usage record to determine whether the first user has used the first driving system, as well as the vehicle and time period in which the first driving system was used.

[0060] Optionally, the initial usage log may also include information on violations by the driving system.

[0061] In another possible implementation, the method further includes: obtaining an identifier of a first vehicle, determining a second usage record of the driving system on the first vehicle based on the identifier of the first vehicle, and determining that the first user has been authorized by the system based on the second usage record.

[0062] In the above embodiments, the second usage record is determined by the identifier of the first vehicle, and the first user is determined to have been authorized by the system based on the second usage record. This helps to quickly determine whether the first user has used the first driving system on the first vehicle, thereby reducing the authorization time or the time it takes for the first user to activate the first driving system.

[0063] Optionally, the first vehicle is the vehicle requested to be driven by the first user.

[0064] In another possible implementation, the second usage record is used to describe the correspondence between the user's identifier, the driving system's identifier, and the time period during which the driving system is used.

[0065] In the above embodiments, the identifier of the first driving system can be used to search in the second usage record to determine whether the first user has used the first driving system on the first vehicle and the time period during which the first driving system was used.

[0066] Optionally, the second usage log may also include information on violations by the driving system.

[0067] Secondly, embodiments of this application provide an authorization device, including a processing unit. The processing unit is used to grant a first user the right to use the first driving system based on relevant information of the first driving system and relevant information of the system already authorized to the first user.

[0068] In one possible implementation, the authorization device further includes a communication unit. The communication unit is used to acquire the identifier of the first driving system and the identifier of the first user. The communication unit is also used to determine relevant information about the first driving system based on the identifier of the first driving system, and to determine relevant information about the first user having been authorized by the system based on the identifier of the first user.

[0069] Optionally, the communication unit can obtain the identifier of the first driving system and the identifier of the first user by receiving request information from the first user.

[0070] Alternatively, the communication unit can obtain the identifier of the first driving system and the identifier of the first user by setting preset trigger conditions.

[0071] In another possible implementation, the processing unit is specifically used to determine whether the first user's scope of authority includes the first driving system based on relevant information about the first driving system and relevant information about the systems the first user has been authorized to use. If the first user's scope of authority includes the first driving system, the first user is granted the right to use the first driving system. If the first user's scope of authority does not include the first driving system, training information for the first driving system can be provided to the first user, allowing the first user to acquire the right to use the first driving system through training.

[0072] In another possible implementation, information related to the first driving system includes the conditions under which the right to use the first driving system can be obtained.

[0073] Optionally, the conditions under which the right to use the first driving system can be obtained can be set by the supplier of the first driving system. Of course, the conditions under which the right to use the first driving system can also be updated.

[0074] In another possible implementation, the conditions under which the right to use the first driving system is permitted to be acquired include one or more of the following: required training, association between driving systems, or coverage of the right to use between driving systems.

[0075] Optionally, if there are multiple conditions under which the right to use the first driving system can be obtained, the processing unit may determine whether the right to use the first driving system can be provided to the first user in the order of judging the coverage relationship of the right to use between driving systems, the association relationship between driving systems, and the required training.

[0076] In another possible implementation, system features include one or more of the following: regulations, standards, assessments, certification levels, specifications, guidelines, suppliers, or functions.

[0077] In another possible implementation, the processing unit is specifically used to determine the first training based on the training corresponding to the first driving system and the training already completed by the first user.

[0078] The communication unit is also used to provide the first user with training information corresponding to the first training session.

[0079] The communication unit is also used to receive the first instruction information.

[0080] The aforementioned processing unit is also used to, when the first instruction information indicates that the first user has completed the training information, grant the first user the right to use the first driving system.

[0081] Optionally, the relevant information about the first driving system includes the conditions under which the right to use the first driving system can be obtained and the corresponding training. The conditions under which the right to use the first driving system can be obtained include the required training. The relevant information about the first user being authorized to the system includes the training that the first user has completed.

[0082] In another possible implementation, after the processing unit grants the first user access to the first driving system, the processing unit is also used to expand the first user's scope of permissions based on relevant information of the first driving system.

[0083] In another possible implementation, the processing unit is also used to provide the first user with the right to use the first driving system based on the system characteristics of the first driving system and the system characteristics of the system that the first user has been authorized to use.

[0084] In another possible implementation, the processing unit is specifically used to grant the first user the right to use the first driving system if the system characteristics of the first driving system and the system characteristics of the first user being authorized by the system meet one or more of the following conditions.

[0085] The first driving system and the first user have been authorized by the system to follow the same regulations, or,

[0086] The first driving system and the first user have been authorized by the system to follow the same standards, or,

[0087] The first user has been authorized to follow the standards of the system, including the standards followed by the first driving system; or...

[0088] The first driving system and the first user have passed the same evaluation by the authorized system, or,

[0089] The first driving system and the first user have the same authentication level as the authorized system, or,

[0090] The first driving system and the first user have been authorized by the system to follow the same specifications, or,

[0091] The first driving system and the first user have been authorized by the system to follow the same guidelines, or,

[0092] The supplier of the first driving system is the same as the supplier of the system authorized by the first user, or...

[0093] The first user has been authorized to use the functions of the first driving system; or...

[0094] The functions of the first driving system are the same as those of the first user's authorized system.

[0095] Optionally, the various scenarios described above regarding providing the first user with the right to use the first driving system can be set by the supplier of the first driving system.

[0096] In another possible implementation, the processing unit is specifically used to provide the first user with access to the first driving system when the first user's access to the first driving system is covered by the access rights of the authorized system, and / or the access rights of the first user have been covered by the access rights of the authorized system.

[0097] In another possible implementation, the conditions under which the right to use the first driving system can be obtained also include: system usage duration, and / or, violation information.

[0098] In another possible implementation, the processing unit is further configured to determine the first user's first usage record based on the first user's identifier, and to determine that the first user has been authorized by the system based on the first usage record.

[0099] In another possible implementation, the first usage record is used to describe the correspondence between the vehicle's identifier, the driving system's identifier, and the time period during which the driving system was used. Optionally, the first usage record may also include information on violations committed by the driving system.

[0100] In another possible implementation, the communication unit is further configured to acquire the identifier of the first vehicle. The processing unit is further configured to determine a second usage record of the driving system on the first vehicle based on the identifier of the first vehicle, and to determine, based on the second usage record, that the first user has been authorized by the system. Optionally, the first vehicle is the vehicle requested to be driven by the first user.

[0101] In another possible implementation, the second usage record is used to describe the correspondence between the user's identifier, the driving system's identifier, and the time period during which the driving system was used. Optionally, the second usage record may also include information on violations committed by the driving system.

[0102] Thirdly, embodiments of this application also provide a terminal device, which includes the authorization device described in any of the second aspects above.

[0103] Fourthly, embodiments of this application also provide a server, which includes the authorization device described in any of the second aspects above.

[0104] Fifthly, embodiments of this application also provide an authorization system, which includes the terminal device described in the third aspect and the server described in the fourth aspect.

[0105] Sixthly, embodiments of this application also provide a vehicle, which includes the authorization device described in any of the second aspects above, or the terminal device described in the third aspect.

[0106] In a seventh aspect, a program is provided that, when executed by a processor, performs the method provided in any of the first aspects above.

[0107] Eighthly, a program product is provided, such as a computer-readable storage medium, comprising the program of any one of the first aspects above.

[0108] Ninth aspect, a computer-readable storage medium is provided, including a program, wherein when the program is run by a processor, the method provided in any of the first aspects is executed.

[0109] In a tenth aspect, embodiments of this application provide a chip including a processor, the processor being configured to execute instructions, which, when executed, cause the chip to perform the collision risk determination method described in any of the first aspects above.

[0110] The beneficial effects of some solutions in aspects two through ten of this application can be referenced to the beneficial effects of the technical solution in aspect one. Attached Figure Description

[0111] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0112] Figures 1A to 1C are schematic diagrams of a scenario architecture provided in this application;

[0113] Figure 2 is a flowchart illustrating one of the authorization methods provided in this application;

[0114] Figure 3 is a flowchart illustrating another authorized method provided in this application;

[0115] Figure 4 is a flowchart illustrating another authorized method provided in this application;

[0116] Figure 5 is a flowchart illustrating another authorized method provided in this application;

[0117] Figure 6 is a flowchart illustrating another authorized method provided in this application;

[0118] Figure 7 is a flowchart illustrating another authorized method provided in this application;

[0119] Figure 8 is a flowchart illustrating another authorized method provided in this application;

[0120] Figure 9 is a schematic block diagram of an authorized device provided in an embodiment of this application;

[0121] Figure 10 is a schematic block diagram of another authorized device provided in an embodiment of this application. Detailed Implementation

[0122] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In this application, "at least one" means one or more, and "more than one" means two or more. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0123] The following is an explanation of some of the terms used in this application. It should be noted that these explanations are for the convenience of those skilled in the art and are not intended to limit the scope of protection claimed in this application.

[0124] (1) Vehicle.

[0125] In this application, "vehicle" refers to equipment that includes a power unit and a traction unit. For example, a vehicle can be a means of transportation (such as commercial vehicles, passenger cars, motorcycles, flying cars, trams, trains, etc.), an industrial vehicle (such as forklifts, trailers, tractors, etc.), an engineering vehicle (such as excavators, bulldozers, cranes, etc.), or agricultural equipment (such as lawnmowers, harvesters, etc.). A vehicle can also refer to a robot (automated guided vehicle, AGV, walking conversational robot, service robot, etc.), industrial equipment (industrial robots, robotic arms, etc.), or leisure and entertainment equipment (virtual reality (VR) equipment, mixed reality (MR) equipment, or 4D cinema cabins, etc.).

[0126] Optionally, the vehicle includes a communication module capable of enabling communication functions (including wired and wireless communication). For example, the vehicle is equipped with a T-BOX, which integrates vehicle network and wireless communication functions to provide communication services. The T-BOX includes, but is not limited to, at least one of the following: a 3G network module, a 4G network module, a 5G network module, a GPS module, a Bluetooth module, an Ethernet module, a CAN communication module, a voice telephone module, a power supply module, an Airbag module, or an E / B-call module. For example, the vehicle can communicate with other terminals and cloud servers through its communication module and exchange data.

[0127] (2) Server.

[0128] In this application, "server" refers to a general term for devices or components capable of processing and storing data. This may include physical devices such as hosts or processors, virtual devices such as virtual machines or containers, and chips or integrated circuits. Furthermore, a server can integrate all functions onto a single physical device, or it can deploy different functions on different physical devices; this application does not limit this. Typically, one server can communicate with multiple vehicles. Optionally, a server may also be called a cloud server, vehicle cloud server, vehicle cloud, vehicle cloud platform, cloud, cloud server, cloud controller, or vehicle networking server, etc. Optionally, in this application, a server can be a server maintained by the vehicle's original equipment manufacturer (OEM), or a server on a cloud service; this application does not limit this either.

[0129] (3) Terminal equipment.

[0130] Terminal equipment can also be called user equipment (UE). In this embodiment, the terminal equipment is a device with wireless transceiver capabilities, capable of communicating with one or more network elements of the core network (CN) via network device 110 in the access network (AN). Terminal equipment can also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user device, etc. Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal devices can be cellular phones, cordless phones, session initiation protocol (SIP) phones, smartphones, mobile phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other devices connected to a wireless modem, vehicle-mounted terminal devices, wearable devices, drone devices, or terminals in the Internet of Things (IoT), vehicle-to-everything (V2X) networks, 5G mobile communication networks, and any form of terminal in future networks, or terminals in future evolved public land mobile networks (PLMNs), etc. For example, terminal devices can be virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. This application does not limit these possibilities.

[0131] The embodiments of this application will be described below with reference to the accompanying drawings.

[0132] Please refer to Figures 1A to 1C, which exemplarily illustrate the scenario architecture 100 of an embodiment of this application. It should be understood that the architecture and applicable scenarios described herein are merely examples. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0133] The scenario architecture 100 shown in Figure 1A includes a vehicle 101 and a server 102. For a description of vehicle 101 and server 102, please refer to the description of vehicles and servers above. In the scenario shown in Figure 1A, vehicle 101 and server 102 can communicate and exchange data. For example, vehicle 101 can send query data to server 102, and server 102 can send the corresponding data back to vehicle 101. As another example, server 102 can also request vehicle-related data from vehicle 101, and vehicle 101 will send the requested data to server 102.

[0134] In one possible implementation, the first user can request information about the first user being authorized by the system from the server 102 via the vehicle 101, and correspondingly, the server 102 sends the information about the first user being authorized by the system to the vehicle 101.

[0135] In another possible implementation, server 102 can request the usage records of the driving system on vehicle 101 from vehicle 101, and correspondingly, vehicle 101 sends the usage records of the driving system to server 102.

[0136] The scenario architecture 100 shown in Figure 1B includes a vehicle 101, a server 102, and a terminal device 103. Descriptions of the vehicle 101, server 102, and terminal device 103 can refer to the descriptions of the vehicle, server, and terminal device above. In the scenario shown in Figure 1B, the vehicle 101 and server 102 can communicate; a detailed description can be found in Figure 1B. Furthermore, the vehicle 101 can also communicate with the terminal device 103 and exchange data. Communication between the vehicle 101 and the terminal device 103 can be achieved through short-range communication technologies such as Bluetooth, WiFi, or GPS, or through mobile communication technologies such as the Global System for Mobile Communications (GSM), 5G, or New Radio (NR).

[0137] In one possible implementation, the first user can send a request to the vehicle 101 to use the first driving system through the terminal device 103. Correspondingly, the vehicle 101 can send relevant information on whether or not the first user is allowed to use the first driving system through the terminal device 103.

[0138] The scenario architecture 100 shown in Figure 1C includes a vehicle 101, a server 102, and a terminal device 103. The descriptions of vehicle 101, server 102, and terminal device 103 can be found in the descriptions of vehicle, server, and terminal device above. In the scenario shown in Figure 1C, vehicle 101, server 102, and terminal device 103 can communicate with each other and transmit data. The specific implementation can be understood by referring to the descriptions in Figures 1A and 1B above, and will not be repeated here.

[0139] In one possible implementation, the first user can send a query request for information about the first user's authorized system to the vehicle 101 via the terminal device 103, and a query request for information about the first driving system to the server 102. Correspondingly, the vehicle 101 can send information about the first user's authorized system to the terminal device, and the server 102 can send information about the first driving system to the terminal device 103.

[0140] Optionally, server 102 may be a server maintained by the vehicle's OEM, a server maintained by a server supplier, or multiple servers maintained by different OEMs; this application does not limit this.

[0141] Optionally, server 102 can also communicate with other services. For example, server 102 can also communicate with servers maintained by other OEMs.

[0142] Optionally, terminal device 103 can be a terminal device associated with vehicle 101. Users can access vehicle 101 through terminal device 103 and have certain access or control permissions. For example, they can access the first system on vehicle 101 through terminal device 103, or modify the configuration of the first system on vehicle 101 through terminal device 103. Of course, with technological advancements, more systems will appear on vehicle 101 to improve the safety and comfort of passengers.

[0143] With technological advancements, intelligent vehicles have entered the era of software-defined vehicles (SDV). Vehicles are equipped with an increasing number of systems, and these systems are constantly being updated. This necessitates that drivers and passengers complete training for each system to gain access, making the authorization process complex in many scenarios (such as chauffeur services, car rentals, or remote vehicle control), and impacting the user experience. Remote vehicle control, in particular, refers to the presence of remote controllers monitoring the vehicle's operation during intelligent driving and intervening promptly in case of malfunctions.

[0144] In view of this, this application provides an authorization method, device, terminal, vehicle terminal, and storage medium, which can improve the ease with which users obtain system permissions and provide users with a better product experience.

[0145] To facilitate understanding of the rights confirmation and authorization process described below, the system information, vehicle information, user information, and training information provided in this application will be introduced as examples.

[0146] System information describes the system's identifier, the conditions under which access rights are permitted, the coverage relationships of access rights, and the correspondence between one or more of the system's characteristics. System information can be represented in tabular form, as exemplified in Table 1.

[0147] Table 1 System Information

[0148] The system identifier is used to identify the system. The system identifier can be the system's name, ID, or unique code, etc.

[0149] The conditions under which usage rights can be obtained are those conditions that must be met to acquire usage rights, including one or more of the following: required training, inter-system relationships, or overlapping usage rights between systems. Required training can be understood as requiring users to acquire system usage rights through training; for example, granting users usage rights to the first system by completing training that they haven't yet completed in the first system. Inter-system relationships describe the relationships between system characteristics, such as the relationship between the regulations followed by the systems, or the relationship between the authentication levels of the systems. The overlapping usage rights between systems can be understood by referring to the section on "Overlapping Usage Rights" below.

[0150] Based on the above description, it can be seen that the conditions under which the right to use is allowed to be obtained and the system characteristics both include multiple sub-items, which can be displayed in the form of a table, such as Table 2, which is an example of the conditions under which the right to use is allowed to be obtained.

[0151] Table 2. Conditions under which the right to use is permitted to be acquired.

[0152] The coverage relationship of usage rights includes the scope that the usage right can cover and the scope that the usage right is covered by. For example, the scope that the usage right can cover means that if the usage right of system A can cover systems B and C, then having the usage right of system A also allows the use of systems B and C. The coverage relationship of usage rights means that if the usage right of system A is covered by systems B and C, then having the usage right of system B and / or system C allows the use of the system. The role and usage method of the conditions for obtaining usage rights in the licensing process will be described in detail below, and will not be elaborated here.

[0153] System characteristics describe the features of the system and can be used as criteria for obtaining system access, as well as to help users better understand the system. System characteristics may include one or more of the following: followed regulations, standards, passed assessments, certification levels, followed specifications, followed guidelines, suppliers, or functions. System characteristics can be represented in tabular form, as shown in Table 3, which is an example of system characteristics.

[0154] Table 3 System Characteristics

[0155] It should be noted that, in the specific implementation process, system features may include one or more of the features shown in Table 3, and may also include other features besides those shown in Table 3, such as the system's operational difficulty. This application does not limit this. The role and usage of system features in the licensing process will be described in detail below, and will not be elaborated here.

[0156] In one possible implementation, a system includes multiple functions or multiple subsystems. When using some functions or some subsystems, secondary authorization is required to obtain the right to use them. In this case, the authorization process can refer to the authorization method of this application. Accordingly, the conditions under which the right to use the system is allowed to be obtained can also refer to the conditions under which the right to use the functions is allowed to be obtained.

[0157] Vehicle information describes the correspondence between one or more of the vehicle's identifiers, the identifiers of installed systems, or the usage records of systems on the vehicle. Vehicle information can be represented in tabular form, as exemplified in Table 4.

[0158] Table 4 Vehicle Information

[0159] Among them, the vehicle identifier is used to identify the vehicle, and the vehicle identifier can be the vehicle's name, ID, or unique code, etc.

[0160] The identifier for an installed system is used to identify systems that are already installed on the vehicle, such as driving systems, cockpit systems, or driving control systems.

[0161] The vehicle system usage log includes the usage records of each system on the vehicle. This log describes the correspondence between the user's identifier, the system's identifier, and the time period during which the system was used. The vehicle system usage log can be represented in tabular form, as shown in Table 5, which is an example of a vehicle system usage log.

[0162] Table 5 Vehicle System Usage Records

[0163] Of course, the system's usage log can also include information related to usage events, such as violation information. Table 6 shows another example of a system's usage log on a vehicle.

[0164] Table 6 Vehicle System Usage Records

[0165] As shown in Table 6, the event is represented by "00" or "01". "00" can indicate no violation information, while "01" can indicate the existence of a valid violation information. Optionally, when the event is "01", the time period in which the system is used can indicate the time period during which the violation event occurred. For example, in Table 6, the time period corresponding to time "01" is designated as the "first time period," indicating that the violation event occurred within the first time period. Of course, other identifiers can also be used to identify the event. For example, A can represent no violation information, and B can represent the existence of a valid violation information. Even richer identifiers can be used to identify the time of use. For example, the event can be represented in the form of "identifier 1 + identifier 2", where identifier 1 indicates whether a violation information occurred and / or whether the violation information is valid, and identifier 2 indicates the time when the event occurred.

[0166] It is understandable that the content shown in Table 5 or Table 6 above can be the "vehicle system usage record" corresponding to a certain vehicle.

[0167] The role and usage of the vehicle's system usage records in the authorization process will be explained in detail below, and will not be repeated here.

[0168] User information describes the user's identifier, the identifier of the system the user has been authorized to use, or one or more of the user's records of using the system. User information can be represented in tabular form, as exemplified in Table 7.

[0169] Table 7 User Information

[0170] The user identifier is used to identify the user. The user identifier can be the user's name, ID, or unique code, etc.

[0171] The system identifier that the user has been authorized to use is used to identify the system that the user has been authorized to use. The system identifier that the user has been authorized to use can include the identifiers of one or more systems.

[0172] User usage records are historical records of how users use various systems. These records describe the correspondence between vehicle identifiers, system identifiers, and the time periods during which the systems were used. User usage records can be represented in tabular form, as exemplified in Table 8.

[0173] Table 8 User System Usage Records

[0174] Of course, the system usage log can also include information related to usage events, such as violation information. Table 9 shows another example of user usage logs.

[0175] Table 9 User System Usage Records

[0176] It is understandable that the content shown in Table 8 or Table 9 above can be the "user's system usage record" for a specific user.

[0177] The role and usage of vehicle user usage records in the authorization process will be explained in detail below, and will not be elaborated here.

[0178] Training information describes the correspondence between identifiers for training information and identifiers for functions. Training information can be represented in tabular form, as exemplified in Table 10.

[0179] Table 10 Training Information

[0180] The training information identifier identifies the training information itself; this identifier can be the name, ID, or unique code of the training information. The function identifier identifies the function; this identifier can be the name, ID, or unique code of the function. The training information allows you to determine the corresponding training information for a function, enabling users to acquire the right to use that function through training. Alternatively, the training information can also describe the correspondence between the system's identifiers and the training information identifiers; in this case, the corresponding training information for the system can be directly determined from the training information.

[0181] Optionally, this application does not limit the training method. For example, relevant training can be completed in a real vehicle, or it can be completed on a mobile phone through document learning or simulation learning.

[0182] It is understood that the system information, vehicle information, user information and training information shown above are exemplary. In specific implementations, the content represented by the above four types of information can also be represented by other information, and this application does not limit this.

[0183] It should be noted that the above-described representation of system information, vehicle information, user information, and training information in tabular form is exemplary. This application does not limit the manner in which the above-mentioned information is represented or recorded. For example, it can also be recorded in the form of documents or diagrams. Furthermore, this application does not limit the location where the above-mentioned information is stored. For example, the above-mentioned multiple pieces of information can all be stored on the same server, or the above-mentioned multiple pieces of information can be stored separately on different servers, or the above-mentioned multiple pieces of information can be partially stored on the vehicle's storage unit and partially stored on the server.

[0184] Please refer to Figure 2, which is a flowchart illustrating an authorization method provided in this application. The authorization method may include one or more steps from S201 to S204. It should be understood that, for ease of description, the authorization method provided in this application is described in the order of S201 to S204, and is not intended to limit the execution to this order. This application embodiment does not limit the order of execution, execution time, or number of executions of the above one or more steps. S201 to S204 are as follows:

[0185] S201, The authorization device obtains the identifier of the first driving system and the identifier of the first user.

[0186] The authorization device is a computing device capable of executing the authorization and authorization process. Furthermore, the authorization device may also have communication capabilities, such as receiving information from other devices or sending information to other devices. The authorization device may be installed in one or more devices, such as a vehicle, a server, or a terminal device. For example, the authorization device may be installed in a vehicle, a server, or a terminal device. As another example, the authorization device may include multiple units, with some units installed in a vehicle and some units installed in a server or terminal device.

[0187] The first driving system is a system that provides driving services to the user. For example, the first driving system can specifically be an automated driving system (ADS), lane keeping assist system, automatic parking assist system, brake assist system, reversing assist system, and driving assist system. Of course, the first driving system can also be replaced by other systems that can provide services to the user; for example, the first driving system can be replaced by a cockpit system or a driving control system. For example, the cockpit system can include one or more of an intelligent vehicle infotainment system, an intelligent interaction system, an intelligent sensing system, or an entertainment system. The driving control system can also include one or more of a powertrain electronic control system, a chassis electronic control system, or a body electronic control system. For ease of description, the following description will use the first driving system as an example.

[0188] The identifier of the first driving system is used to identify the first driving system. For example, the identifier of the first driving system can be the name of the first driving system (e.g., lane keeping assist system or automatic parking assist system), ID (e.g., S_A_1 or S_A_2), or unique code.

[0189] The first user is the person using the driving service, such as a driver, a designated driver, or a car renter. In some solutions, the first user can also be replaced by a computer program using the driving service, as well as other entities or virtual modules. The following describes the first user in specific scenarios. Taking the scenario shown in Figure 1A as an example, the first user can send a request to vehicle 101 through the vehicle's human-machine interface to obtain the right to use the first system on vehicle 101. As another example, the first user can also be a user waiting to be granted the right to use the first system; for example, the first user is a car rental customer who can wait for the car rental company to provide them with the right to use certain driving systems. Taking the scenario shown in Figure 1B as an example, before driving vehicle 101, the first user can use terminal device 103 to query the systems installed on vehicle 101, select the system they wish to use while driving vehicle 101, and send relevant messages to vehicle 101 through terminal device 103 to indicate the system the first user wishes to use.

[0190] The identifier of the first user is used to identify the first user to distinguish different users. For example, the identifier of the first user can be the first user's name (e.g., Xiaoming or Xiaozhang), ID (e.g., P_1 or P_2), or unique code, etc.

[0191] The following describes two methods by which the authorization device obtains the identifier of the first driving system and the identifier of the first user:

[0192] Method 1: The authorization device obtains the identifier of the first driving system and the identifier of the first user through the request information of the first user. For example, by operating the vehicle or terminal device, the user can send the identifier of the first user and the identifier of the first driving system to the authorization device. Accordingly, the authorization device can obtain the identifier of the first user and the identifier of the first driving system by receiving the message from the user.

[0193] Method 2: The authorizing device obtains the identifiers of the first driving system and the first user by receiving messages from other users or entities. For example, if the first user is a designated driver who needs other users or entities to grant them access to the first driving system, then the other users or entities can send the identifiers of the first driving system and the first user to the authorizing device. Accordingly, the authorizing device can obtain the identifiers of the first driving system and the first user by receiving messages from other users or entities. These other entities can be other devices on the vehicle (e.g., driver fatigue detection devices or navigation devices), or devices on a server or terminal device; this application does not limit this.

[0194] It should be noted that the above "Method 1" and "Method 2" are only examples. For example, the operation of obtaining the identifier of the first driving system and the identifier of the first user can be periodically triggered by preset trigger conditions.

[0195] S202, The authorization device determines the relevant information of the first driving system based on the identifier of the first driving system.

[0196] The information related to the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained. Optionally, the information related to the first driving system may also include one or more of the following: the identifier of the first driving system, the usage right coverage relationship of the first driving system, or the system characteristics of the first driving system.

[0197] For example, the authorization device can retrieve the system information of the first driving system from the first storage unit by querying or indexing based on the identifier of the first driving system. The first storage unit stores the system information of the first driving system; for example, the first storage unit is a storage unit on a server or a storage unit on a vehicle. As described above, the system information includes the conditions under which the right to use the system is permitted. Therefore, the authorization device can also determine relevant information about the first driving system from the system information. Taking the scenario shown in Figure 1A as an example, the system information of the first driving system can be stored on server 102, and the authorization device is located on vehicle 101. The authorization device can retrieve the system information of the first driving system by sending a request message (which includes the identifier of the first driving system) to server 102, thereby determining the relevant information about the first driving system.

[0198] Of course, in some implementations, the relevant information of the first driving system may also include the usage records of the first driving system by the first user, or the usage records of the first driving system on the target vehicle, etc. In this implementation, the authorization device can obtain the user information of the first user through querying or indexing based on the first user's identifier, and then determine the usage records of the first driving system by the first user. Alternatively, the authorization device can obtain the vehicle information of the target vehicle through querying or indexing based on the identifier of the target vehicle, and then determine the usage records of the first driving system on the target vehicle. The target vehicle can be a vehicle driven by the first user, a vehicle that the first user wishes to drive, or a vehicle that the first user frequently drives, etc.

[0199] S203. The authorization device determines the relevant information of the first user who has been authorized by the system based on the identifier of the first user.

[0200] Among them, the relevant information of the first user being authorized by the system includes one or more of the system information of the first user being authorized by the system.

[0201] For example, the authorization device can retrieve the user information of the first user from the second storage unit by querying or indexing based on the identifier of the first user. The second storage unit can be a storage unit on a server or a storage unit in a vehicle. As described above, the user information includes the identifier of the system the user has been authorized to. Therefore, the authorization device can determine the identifier of the system the first user has been authorized to based on the user information. Further, the authorization device can retrieve the system information of the system the first user has been authorized to based on the identifier of the system the first user has been authorized to based on the identifier of the system the first user has been authorized to, from the third storage unit by querying or indexing, thereby determining the relevant information of the system the first user has been authorized to. The third storage unit can be a storage unit on a server or a storage unit in a vehicle. Taking the scenario shown in Figure 1A as an example, both the user information of the first user and the system information of the system the first user has been authorized to can be stored on server 102. The authorization device is located in vehicle 101. The authorization device can retrieve the user information of the first user by sending a first request message (which includes the identifier of the first user) to server 102, thereby determining the system the first user has been authorized to. Then, the authorization device can also obtain the system information of the system authorized by the first user by sending a second request message (the second request message includes the system authorized by the first user) to the server 102, thereby determining the relevant information of the system authorized by the first user.

[0202] It should be noted that the aforementioned first storage unit, second storage unit, and third storage unit may refer to a single storage unit or multiple storage units, and this application does not limit this.

[0203] Of course, in some implementations, the system information of the first user authorized by the system may also include the first user's usage records of the authorized system, or the first user's usage records of the authorized system on the target vehicle, etc. In this implementation, the authorization device can obtain the user information of the first user based on the first user's identifier through querying or indexing, and then determine the first user's usage records of the system. Alternatively, the authorization device can obtain the vehicle information of the target vehicle based on the target vehicle's identifier through querying or indexing, and then determine the first user's usage records of the system on the target vehicle. The target vehicle can be a vehicle driven by the first user, a vehicle that the first user wishes to drive, or a vehicle that the first user frequently drives, etc.

[0204] S204. The authorization device, based on the relevant information of the first driving system and the relevant information of the system already authorized to the first user, provides the first user with the right to use the first driving system.

[0205] In one possible implementation, the authorization device can check whether the first user has the right to use the first driving system. If the first user has the right to use the first driving system, the authorization device provides the first user with the right to use the first driving system. In some cases, the verification result of the authorization device indicates that the first user's authorized systems do not include the first driving system. The authorization device can then further facilitate the first user's acquisition of the right to use the first driving system based on relevant information about the first driving system and relevant information about the systems the first user is already authorized to use, allowing the first user to conveniently and quickly obtain the right to use the first driving system. The relevant information about the first driving system includes the conditions under which the right to use the first driving system can be obtained. As described above, these conditions include required training, the relationship between driving systems, the coverage relationship of the right to use between driving systems, system usage duration, and violation information. Therefore, the following describes the implementation methods of the authorization device providing the first user with the right to use the first driving system according to the conditions under which the right to use the first driving system can be obtained.

[0206] Scenario 1: The right to use the first driving system is permitted only if the required training is completed.

[0207] In this case, the relevant information of the first driving system includes the conditions under which the right to use the first driving system can be obtained and the training corresponding to the first driving system. The condition under which the right to use the first driving system can be obtained is "required training". The training corresponding to the first driving system includes the training corresponding to the functions of the first driving system. For example, the identifier of the first driving system is S_A_3, and the functions of the first driving system include the functions corresponding to F_2 and F_3. According to Table 10 above, the identifier of the training corresponding to F_2 is T_1, and the identifier of the training corresponding to F_3 is T_2. Therefore, the training corresponding to the first driving system is the training corresponding to T_1 and T_2.

[0208] The information related to the systems authorized by the first user includes the training completed by the first user. The authorized systems can be one or more driving systems. For example, if the first user's identifier is P_1 as shown in Table 7 above, then the authorized systems are the driving systems corresponding to S_A_2 and S_B_3. The completed training includes the training corresponding to the authorized systems. For instance, if the authorized systems are the driving systems corresponding to S_A_2 and S_B_3, the identifiers for the functions of S_A_2 include F_3 and F_4, and the identifiers for the functions of S_B_3 include F_5 and F_6. The training identifier corresponding to F_3 is T_2, the training identifier corresponding to F_4 is T_3, the training identifier corresponding to F_5 is T_4, and the training identifier corresponding to F_6 is T_5. Therefore, the completed training for the first user includes the training corresponding to T_2, T_3, T_4, and T_5. For ease of understanding, the training corresponding to the first driving system and the training completed by the first user can be represented in tabular form, as shown in Table 11, which is an example of the training corresponding to the first driving system and the training completed by the first user.

[0209] Table 11 Training corresponding to the first driving system and training completed by the first user

[0210] As can be seen from Table 11, the training corresponding to T_2 is the training that the first user has already completed. Therefore, the authorization device only needs to have the user complete the training corresponding to T_1 to provide the first user with the right to use the first driving system.

[0211] In another possible implementation, the first driving system is an upgraded version of the second driving system already authorized by the first user. The identifier for the new function added by the first driving system compared to the second driving system is F_7, and the identifier for the training corresponding to F_7 is T_9. The authorization device can then push the training information corresponding to T_9 to the user, and grant the first user the right to use the first driving system after the user completes the training. A description of the authorization method corresponding to "Scenario 1: The condition for obtaining the right to use the first driving system is the required training" can be found in Figure 3 below.

[0212] Scenario 2: The condition for granting the right to use the first driving system is the association between driving systems. In this case, the authorization device can grant the first user the right to use the first driving system based on the system characteristics of the first driving system and the system characteristics of the systems already authorized to the first user.

[0213] In one possible implementation, the relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained and the system characteristics of the first driving system. The condition for permitting the right to use the first driving system to be obtained is the "association relationship between driving systems." The relevant information of the first user-authorized system includes the system characteristics of the first user-authorized system. The system characteristics of the first driving system and the system characteristics of the first user-authorized system can be referred to in Table 3 above, and will not be repeated here. It should be noted that the system characteristics of the first driving system or the system characteristics of the first user-authorized system can be one or more of those in Table 3 above. For example, the system characteristics of the first driving system and the system characteristics of the first user-authorized system can also be represented in tabular form, such as Table 12, which shows an exemplary system characteristic of the first driving system, and Table 13, which shows an exemplary system characteristic of the first user-authorized system.

[0214] Table 12 System characteristics of the first driving system

[0215] Table 13 System characteristics of the first user who has been authorized to the system

[0216] Table 12 above shows that the system characteristics of the first driving system include certification level and supplier. Table 13 above shows that the system characteristics of the first user's authorized system include regulations and supplier. That is, both the system characteristics of the first driving system and the system characteristics of the first user's authorized system include supplier, and the supplier is OEM_1 in both cases. Therefore, it can be considered that there is a relationship between the first driving system and the first user's authorized system, and the authorized device can also provide the first user with the right to use the first driving system. For a description of the authorization method corresponding to "Scenario Two: The condition for obtaining the right to use the first driving system is the relationship between the driving systems," please refer to Figure 4 below.

[0217] Scenario 3: The condition for obtaining the right to use the first driving system is the overlapping relationship of the right to use between driving systems.

[0218] For a detailed introduction to the "coverage relationship of usage rights", please refer to the corresponding description in the aforementioned "System Information" (Table 1), which will not be repeated here.

[0219] In this case, the relevant information about the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained and the coverage relationship of the right to use the first driving system. The conditions under which the right to use the first driving system is permitted to be obtained include the coverage relationship of the right to use between driving systems. The relevant information about the first user's authorized systems includes the coverage relationship of the first user's authorized system's right to use.

[0220] For ease of description, the coverage relationship of the first user's authorized system usage rights and the coverage relationship of the first driving system usage rights can be represented in tabular form. For example, Table 14 shows an exemplary coverage relationship of the first user's authorized system usage rights, and Table 15 shows an exemplary coverage relationship of the first driving system usage rights.

[0221] Table 14 shows the coverage of the first user's authorized system usage rights.

[0222] Table 15 Coverage of the First Driving System Usage Rights

[0223] In one possible implementation, where the coverage relationship of the right to use the first driving system indicates that the first user's right to use the first driving system has been covered by the right to use the authorized system, the authorization device provides the first user with the right to use the first driving system.

[0224] For example, in the coverage relationship of the right to use the first driving system, "the scope of the right to use is covered" includes the system that the first user has been authorized to use. This can be understood as the coverage relationship of the right to use the first driving system indicating that the right to use the system that the first user has been authorized to use covers the right to use the first driving system. For example, as shown in Table 15, if the right to use the first driving system includes a driving system with the identifier S_B_7 or S_B_8 in the system that the first user has been authorized to use, the authorization device provides the first user with the right to use the first driving system.

[0225] In another possible implementation, where the coverage relationship of the first user's authorized system access rights indicates that the first user's authorized system access rights cover the first driving system access rights, the authorization device provides the first user with access to the first driving system.

[0226] For example, in the coverage relationship of the first user's authorized system usage rights, "the scope that the usage rights can cover" includes the first driving system. This can be understood as the coverage relationship of the first user's authorized system usage rights indicating that the first user's authorized system usage rights cover the first driving system usage rights. For example, as shown in Table 14, when the identifier of the first driving system is S_B_1 or S_B_2, the authorization device provides the first user with the right to use the first driving system.

[0227] Optionally, the coverage relationship between the first user's authorized system access rights and the first driving system access rights can be set by the corresponding system supplier, and the coverage relationship settings can be updated during system use. For example, the scope of system access rights can be increased, decreased, or adjusted.

[0228] Based on the above description, it can be seen that the authorization device can complete the authorization of the first user by using the coverage relationship of the first driving system's right of use and the coverage relationship of the first user's right of use of the authorized system, without requiring the first user to learn about the first driving system. This simplifies the authorization process and improves the user experience.

[0229] The above content describes how to grant a first user access to the first driving system through three scenarios: "Scenario 1: The condition for granting access to the first driving system is the required training," "Scenario 2: The condition for granting access to the first driving system is the association between driving systems," and "Scenario 3: The condition for granting access to the first driving system is the coverage relationship between the usage rights of driving systems." However, the above implementation does not consider the first user's existing system usage, such as usage duration or violations. Considering factors such as security and authorization accuracy, this application also proposes the following conditions for granting access, as shown in "Scenario 4" and "Scenario 5."

[0230] Scenario 4: The conditions under which the right to use the first driving system can be obtained include the duration of system use.

[0231] In this case, the relevant information for the first driving system includes the conditions under which the right to use the first driving system is permitted, and these conditions include "system usage duration." The relevant information for the systems authorized by the first user includes the system usage duration for each system authorized by the first user. For example, the authorization device can obtain the usage duration of each system authorized by the first user by querying the "user's system usage records" in the user information, or by querying the "vehicle system usage records" in the vehicle information. The query method of the authorization device can be referred to the foregoing content and will not be repeated here. The authorization device can determine whether to grant the first user the right to use the first driving system by analyzing the relationship between the system usage durations in the systems authorized by the first user and the "system usage duration."

[0232] When the conditions for obtaining the right to use the first driving system include the duration of system use, the conditions for obtaining the right to use the first driving system may also include "required training" or "the relationship between driving systems", which will be introduced in detail below.

[0233] Scenario 1: The conditions under which the right to use the first driving system can be obtained include "system usage time" and "required training".

[0234] In this case, the "system usage time" mentioned above refers to the duration of time the target driving system is used by the target user. The target driving system is a driving system for which the required training is partially the same as the training required to obtain the first driving system. The target user can be a user who requests the right to use the first driving system, or a user who wishes to obtain the right to use the first driving system.

[0235] The information related to the first driving system includes the conditions under which the right to use the first driving system can be obtained and the corresponding training. The conditions for obtaining the right to use the first driving system include "system usage duration" and "required training," while the corresponding training includes training related to the functions of the first driving system. For example, the condition for obtaining the right to use the first driving system is "system usage."

[0236] The relevant information of the first user's authorized system includes the usage time of the first user's authorized system and the training completed by the first user. The first user's authorized system can be one or more driving systems.

[0237] Regarding the conditions under which the right to use the first driving system can be obtained, including "system usage time" and "required training," a description of the corresponding authorization methods can be found in Figure 5 below.

[0238] Scenario 2: The conditions under which the right to use the first driving system can be obtained include "system usage time" and "the relationship between driving systems".

[0239] In this case, the "system usage time" refers to the duration of time the target driving system is used by the target user. The target driving system is related to the first driving system. The target user can be a user who requests or wishes to obtain the right to use the first driving system.

[0240] The relevant information of the first driving system includes the conditions under which the right to use the first driving system can be obtained and the system characteristics of the first driving system. Among them, the conditions under which the right to use the first driving system can be obtained include "system usage time" and "the relationship between driving systems".

[0241] The relevant information of the first user authorized system includes the usage time of the first user authorized system and the system characteristics of the first user authorized system. The first user authorized system can be one or more driving systems.

[0242] Regarding the conditions under which the right to use the first driving system can be obtained, including "system usage time" and "the relationship between driving systems," the relevant description of the authorization method can be found in Figure 6 below.

[0243] Scenario 5: The conditions under which the right to use the first driving system can be obtained include violation information.

[0244] In this case, the relevant information of the first driving system includes the conditions under which the right to use the first driving system can be obtained, and these conditions include "violation information." The relevant information of the systems authorized by the first user includes the usage records of each system authorized by the first user. For example, the authorization device can obtain the usage records of each system authorized by the first user by querying the "user's system usage records" in the user information, or by querying the "vehicle system usage records" in the vehicle information, and thus obtain the violation information of each system. The query method of the authorization device can be referred to the foregoing content, and will not be repeated here. The authorization device can determine whether to grant the first user the right to use the first driving system by analyzing whether the violation information of each system authorized by the first user meets the "violation information" criteria.

[0245] Where the conditions under which the right to use the first driving system is permitted include violation information, the conditions under which the right to use the first driving system is permitted may also include "required training" or "the relationship between driving systems," which will be described in detail below.

[0246] Scenario 1: The conditions under which the right to use the first driving system can be obtained include "violation information" and "required training".

[0247] In this case, the aforementioned "violation information" refers to the fact that the target user's records of using the target driving system do not include any violation information that is still valid. The target driving system is a driving system for which the required training is partially the same as the training required to obtain the first driving system. The target user can be a user who requests the right to use the first driving system, or a user who wishes to obtain the right to use the first driving system.

[0248] The relevant information for the first driving system includes the conditions under which the right to use the first driving system is permitted and the corresponding training for the first driving system. The conditions under which the right to use the first driving system is permitted include "violation information" and "required training". The corresponding training for the first driving system includes training related to the functions of the first driving system.

[0249] The relevant information of the first user's authorized system includes violation information of the first user's authorized system and the training completed by the first user. The first user's authorized system can be one or more driving systems.

[0250] Regarding the conditions under which the right to use the first driving system can be obtained, including "violation information" and "required training," a description of the corresponding authorization methods can be found in Figure 7 below.

[0251] Scenario 2: The conditions under which the right to use the first driving system can be obtained include "violation information" and "the relationship between driving systems".

[0252] In this case, the aforementioned "violation information" refers to the fact that the target user's records of using the target driving system do not include any violation information that is still valid. The target driving system is related to the first driving system, and the target user can refer to a user who requests the right to use the first driving system.

[0253] The relevant information of the first driving system includes the conditions under which the right to use the first driving system can be obtained and the system characteristics of the first driving system. Among them, the conditions under which the right to use the first driving system can be obtained include "violation information" and "the relationship between driving systems".

[0254] The relevant information of the first user authorized system includes the violation information of the first user authorized system and the system characteristics of the first user authorized system. The first user authorized system can be one or more driving systems.

[0255] Regarding the conditions under which the right to use the first driving system can be obtained, including "violation information" and "the relationship between driving systems," a description of the authorization method can be found in Figure 8 below.

[0256] It is understandable that the conditions for obtaining the right to use shown in "Scenario 4" or "Scenario 5" above can appear together with the conditions for obtaining the right to use shown in "Scenario 1", "Scenario 2" or "Scenario 3" above, in order to ensure that reasonable authorization can be carried out, thereby improving the security, comfort and smoothness of the system used by the user after authorization.

[0257] Figure 2 illustrates the authorization methods corresponding to the conditions under which the right to use the first driving system can be obtained in different situations. To describe the above authorization methods more clearly, the following section will further introduce the authorization methods in conjunction with specific flowcharts.

[0258] Please refer to Figure 3, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 3 is used to further illustrate the authorization method corresponding to "Scenario 1: The condition for obtaining the right to use the first driving system is the required training." It is understood that the steps in the embodiments of this application can be regarded as reasonable modifications or supplements to the embodiments in Figure 2 above; or, it is understood that the authorization method in the embodiments of this application can also be regarded as an embodiment that can be executed independently, and this application does not limit it. The authorization method shown in Figure 3 includes, but is not limited to, the following steps:

[0259] S301. The authorizing device determines the first training based on the training corresponding to the first driving system and the training already completed by the first user.

[0260] Among them, the training corresponding to the first driving system refers to the training required to obtain the right to use the first driving system, and the training completed by the first user refers to the training that the first user has completed. The aforementioned first training refers to the training that the first user has not completed in the training corresponding to the first driving system.

[0261] For example, taking the training of the first driving system and the training completed by the first user as shown in Table 11 above, the training corresponding to T_1 is the training that the first user has not completed in the training corresponding to the first driving system.

[0262] It is understood that "first training" can refer to multiple training sessions, and this application does not limit this.

[0263] S302, The authorized device provides the first user with the training information corresponding to the first training.

[0264] It is understandable that the authorization device can obtain the training information corresponding to the first training based on the identifier of the first training. Taking the architecture shown in Figure 1A above as an example, the relevant information of the training is stored in the storage unit on the vehicle 101. The authorization device can obtain the relevant information of the first training by retrieving the identifier of the first training in the storage unit on the vehicle 101.

[0265] In one possible implementation, the authorization device can provide the first user with training information corresponding to the first training through various forms such as sound, text, images, or animation.

[0266] For example, the authorization device can provide the first user with training information corresponding to the first training through the in-vehicle infotainment system in vehicle 101. The authorization device can also provide the first user with training information corresponding to the first training through a terminal device connected to vehicle 101 (such as terminal device 103 shown in Figure 1B or Figure 1C).

[0267] S303. The authorizing device receives the first instruction information. If the first instruction information indicates that the first user has completed the training information, the first user is granted the right to use the first driving system.

[0268] The first instruction information is used to indicate the status of the first user's learning and training information, and can be used to indicate: the first user is learning and training information, the first user's learning and training information timeout, the first user has not completed the learning and training information, or the first user has completed the learning and training information, etc.

[0269] It should be noted that this application does not limit how the first instruction information is generated. For example, the system can generate the first instruction information by analyzing the first user's learning situation according to preset rules.

[0270] In one possible implementation, after granting the first user access to the first driving system, the scope of the first user's permissions can be expanded based on relevant information about the first driving system. This relevant information includes the system characteristics of the first driving system and / or the coverage relationships of the first driving system's access rights.

[0271] It is understandable that the first user acquires access to the first driving system through "required training," which may introduce new system features, such as compliance with new regulations, passing new assessments, or possessing new functionalities. Therefore, the scope of the first user's permissions can be expanded based on relevant information from the first driving system. For example, the scope of the first user's permissions can be expanded based on the system features of the first driving system; the specific implementation can be seen in Figure 4 below, which will not be detailed here. Another example is that the scope of the first user's permissions can be expanded based on the coverage relationship of the first driving system's access rights; the specific implementation can be seen in Figure 5 below, which will not be detailed here.

[0272] It should also be noted that this application does not limit the location of the authorization device. Taking the scenario architecture shown in Figure 1C as an example, the authorization device can be set in one or more of the following: vehicle 101, server 102, or terminal device 103. Taking the authorization device set in vehicle 101 as an example, the authorization device can obtain the training corresponding to the first driving system and the training already completed by the first user, and determine the first training. Then, the authorization device can provide the training information corresponding to the first training to the first user through the vehicle's infotainment system. Finally, the authorization device receives the first instruction information, and when the first instruction information indicates that the first user has completed the training information, it grants the first user the right to use the first driving system.

[0273] Based on the method shown in Figure 3 above, it can be seen that in the process of the authorization device granting the first user the right to use the first driving system, only the first user needs to complete the first training. This can reduce the training content required for the first user to obtain the right to use the first driving system, thereby simplifying the authorization process and improving the user experience.

[0274] Please refer to Figure 4, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 4 is used to further illustrate the authorization method corresponding to "Scenario 2: The condition for obtaining the right to use the first driving system is the association relationship between driving systems." It is understood that the steps in the embodiments of this application can be regarded as reasonable modifications or supplements to the embodiments in Figure 2 above; or, it is understood that the authorization method in the embodiments of this application can also be regarded as an embodiment that can be executed independently, and this application does not limit it. The authorization method shown in Figure 2 includes, but is not limited to, the following steps:

[0275] S401, The authorization device determines the first association relationship between the first driving system and the first user's authorized system.

[0276] The relationship between driving systems describes the relationship between the system features of the driving systems. As described above, the system features include multiple features, and each system feature can determine at least one relationship between the systems. Therefore, the aforementioned first relationship can include one or more relationships between the systems.

[0277] Next, based on the system features provided in this application, taking the first driving system and the first user-authorized driving system as examples, we will introduce several ways to determine the relationship.

[0278] Method 1: The first driving system and the first user authorized system comply with the same regulations. For example, if both the first driving system and the first user authorized system comply with UN R157, then the first driving system and the first user authorized system are considered to be related.

[0279] In some implementations, the driving system may only follow a few legal provisions. In such implementations, if the first driving system and the first user's authorized system follow the same legal provisions, it can also be considered that there is a relationship between the first driving system and the first user's authorized system.

[0280] In other implementations, the regulations followed by the first user-authorized system, including the legal provisions followed by the first driving system, can be considered to have a unidirectional relationship with the first user-authorized system and the first driving system. This is because the first user-authorized system also follows the legal provisions followed by the first driving system, but may not follow some of these provisions. Therefore, the unidirectional relationship between the first user-authorized system and the first driving system can be understood as allowing association from the first user-authorized system to the first driving system, but not vice versa.

[0281] Method 2: The first driving system and the first user authorized system follow the same standards. For example, if both the first driving system and the first user authorized system follow ISO standards, then a relationship is considered to exist between the first driving system and the first user authorized system.

[0282] Method 3: The standards followed by the first user's authorized system include those followed by the first driving system. For example, if the first user's authorized system follows ISO and GB standards, and the first driving system follows GB standards, then a relationship can be considered between the first driving system and the first user's authorized system. However, it should be noted that the relationship shown in Method 3 is a one-way relationship between the first user's authorized system and the first driving system; that is, it is possible to link from the first user's authorized system to the first driving system, but not vice versa. For a detailed explanation, please refer to the relevant introduction in "Method 1" above.

[0283] Method 4: The first driving system and the first user authorized system pass the same evaluation. For example, if both the first driving system and the first user authorized system pass the AEB test, then the first driving system and the first user authorized system are considered to be related.

[0284] Method 5: The first driving system and the first user's authorized system have the same authentication level. For example, if both the first driving system and the first user's authorized system have a five-star CNCAP authentication level, then a relationship is considered to exist between them. It's understandable that authentication typically involves multiple sub-items, and the authentication result is usually a combination of these sub-items. In some implementations, "same authentication level" can also mean that the results of each sub-item of the authentication are the same.

[0285] Method Six: The first driving system and the first user authorized system follow the same specifications. For example, if both the first driving system and the first user authorized system follow the autonomous driving highway specifications, then the first driving system and the first user authorized system are considered to have a relationship.

[0286] Method 7: The first driving system and the first user authorized system follow the same guidelines. For example, if both the first driving system and the first user authorized system follow electric vehicle safety intelligence, then a correlation is considered between the first driving system and the first user authorized system.

[0287] Method 7: The supplier of the first driving system is the same as the supplier of the first user's authorized system. Taking Tables 12 and 13 above as examples, if the supplier of both the first driving system and the first user's authorized system is OEM_1, then it is considered that there is a relationship between the first driving system and the first user's authorized system.

[0288] Method 8: The functions of the first user's authorized system include the functions of the first driving system. For example, if the functions of the first user's authorized system include F_1, F_2, and F_3, and the functions of the first driving system include F_1 and F_2, then it is considered that there is a relationship between the first driving system and the first user's authorized system.

[0289] Method Nine: The functions of the first user's authorized system are the same as those of the first driving system. For example, if the functions of the first user's authorized system include F_1 and F_2, and the functions of the first driving system also include F_1 and F_2, then it is considered that there is a relationship between the first driving system and the first user's authorized system.

[0290] For example, the system characteristics of the first driving system and the system characteristics of the first user authorized system can also be represented in tabular form, such as Table 16, which is an example of the system characteristics of the first driving system, and Table 17, which is an example of the system characteristics of the first user authorized system.

[0291] Table 16 System characteristics of the first driving system

[0292] Table 17 System characteristics of the first user who has been authorized to use the system

[0293] As can be seen from Tables 16 and 17 above, the first association between the first driving system and the first user and the authorized system includes: passing the same evaluation and having the same CNCAP certification level.

[0294] It should be noted that methods one through nine described in this application can all be used to determine whether a relationship exists between the first driving system and the first user's authorized system. In some implementations, multiple methods one through nine can be combined to determine whether a relationship exists between the first driving system and the first user's authorized system. For example, a relationship is considered to exist between the first driving system and the first user's authorized system only if both methods one and two are satisfied simultaneously.

[0295] S402, if the first association relationship satisfies the association relationship between driving systems, the authorization device provides the first user with the right to use the first driving system.

[0296] It is understandable that the "association between driving systems" here refers to a condition used to determine whether the authorizing device grants the first user the right to use the first driving system, which can include the following two forms:

[0297] Form 1: Any type of association exists between the driving systems.

[0298] In this form, the first association is not empty, meaning the association between driving systems is satisfied, and the authorizing device can provide the first user with the right to use the first driving system. Taking the cases shown in Tables 16 and 17 above as examples, the first association includes: passing the same evaluation and having the same CNCAP certification level; therefore, the authorizing device can provide the first user with the right to use the first driving system.

[0299] Form 2: There are specified associations between the driving systems.

[0300] The specified association relationship may be, for example, simultaneously satisfying the association relationship shown in "Method 1" and "Method 2", or simultaneously satisfying the association relationship shown in "Method 3" and "Method 4". This application does not specifically limit this.

[0301] In this format, in addition to being non-empty, the first association must also satisfy the aforementioned specified association for the authorized device to provide the first user with the right to use the first driving system. Assuming the specified association is the same assessment and the same certification level, the authorized device can only provide the first user with the right to use the first driving system if the first association includes the same assessment and the same certification level. Again, taking the cases shown in Tables 16 and 17 above as examples, the first association includes: passing the same assessment and having the same CNCAP certification level. Therefore, the first association satisfies the aforementioned specified association (the same assessment and the same certification level), and the authorized device can provide the first user with the right to use the first driving system.

[0302] Based on the method shown in Figure 4 above, it can be seen that in the process of the first user obtaining the right to use the first driving system, it is only necessary to analyze the relationship between the first driving system and the system that the first user has been authorized to complete the authorization to the first user, which can simplify the authorization process and thus improve the user experience.

[0303] Please refer to Figure 5, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 5 further illustrates the authorization method corresponding to "Scenario 1: The conditions for obtaining the right to use the first driving system include 'system usage time' and 'required training.'" It is understood that the steps in the embodiments of this application can be considered as reasonable variations or supplements to the embodiments in Figure 2 or Figure 3 above; or, it is understood that the authorization method in the embodiments of this application can also be considered as an embodiment that can be executed independently, and this application does not limit it. The authorization method shown in Figure 5 includes, but is not limited to, the following steps:

[0304] S501, the authorizing device determines the first training based on the training of the first driving system and the training already completed by the first user. For specific implementation details, please refer to the description in S301 above; it will not be repeated here.

[0305] S502, The authorization device determines whether the duration of the first user's use of the second driving system is greater than or equal to the first threshold.

[0306] The second driving system is a system authorized by the first user, and the training information required to obtain the second driving system is partially the same as the training information required to obtain the first driving system. The first threshold may be, for example, 10 hours, 50 hours, or 100 hours, etc., and this application does not limit this.

[0307] For example, the authorization device can obtain the duration of the first user's use of the second driving system by querying "vehicle information" or "user information". For instance, if the identifier of the first user is P_1 and the identifier of the second driving system is S_A_1, the authorization device can determine that S_A_1 was used by P_1 in the first time period by querying the vehicle information shown in Table 2 above. If the duration of the first time period is 30 hours and the first threshold is 10 hours, the duration of the first user's use of the second driving system is greater than the first threshold. As another example, if the identifier of the first user is P_1 and the identifier of the second driving system is S_A_2, the authorization device can determine that S_A_2 was used by P_1 in the first time period by querying the user information shown in Table 3 above. If the duration of the first time period is 30 hours and the first threshold is 50 hours, the duration of the first user's use of the second driving system is less than the first threshold.

[0308] S503A: If the duration of the first user's use of the second driving system is greater than or equal to the first threshold, the authorization device provides the first user with training information corresponding to the first training. For specific implementation details, please refer to the description of S302 above; it will not be repeated here.

[0309] S503B: If the duration of the first user's use of the second driving system is less than the first threshold, the authorization device provides the first user with training information corresponding to the training of the first driving system. Specific implementation details can be found in existing technologies and will not be elaborated here. Alternatively, if the duration of the first user's use of the second driving system is not greater than the first threshold, the method shown in Figure 4 above, or the authorization process shown in "Case Three" above, can also be executed.

[0310] S504. The authorizing device receives the first instruction information. If the first instruction information indicates that the first user has completed the training, the authorizing device grants the first user the right to use the first driving system. For specific implementation details, please refer to the description in S303 above; it will not be repeated here.

[0311] Please refer to Figure 6, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 6 further illustrates the authorization method corresponding to "Scenario Two: The conditions for obtaining the right to use the first driving system include 'system usage time' and 'the association between driving systems'." It is understood that the steps in the embodiments of this application can be considered as reasonable variations or supplements to the embodiments in Figure 2 or Figure 4 above; or, it is understood that the authorization method in the embodiments of this application can also be considered as an embodiment that can be executed independently, and this application does not limit it. The authorization method shown in Figure 6 includes, but is not limited to, the following steps:

[0312] S601, the authorization device determines the first association relationship between the first driving system and the first user's authorized system. For a detailed implementation, please refer to the description of S601 above; it will not be repeated here.

[0313] S602, The authorization device determines whether the duration of the first user's use of the second driving system is greater than or equal to the first threshold.

[0314] The second driving system is a system authorized by the first user, and the first driving system and the second driving system have the aforementioned first association relationship. The first threshold is, for example, 10 hours, 50 hours, or 100 hours, etc., and this application does not limit this. For the specific implementation of this step, please refer to the description of S502 above, which will not be repeated here.

[0315] S603: If the duration of the first user's use of the second driving system is greater than or equal to the first threshold, and the first association relationship satisfies the conditions for obtaining the right to use the first driving system, the authorization device provides the first user with the right to use the first driving system. For specific implementation details, please refer to the description of S603 above; it will not be repeated here.

[0316] Optionally, if the duration of the first user's use of the second driving system is less than the first threshold, the method shown in Figure 3 above or the authorization process shown in "Scenario 3" above can be executed.

[0317] As can be seen from the descriptions in Figures 5 and 6, before confirming that the first user has acquired the first driving system, it will first determine whether the duration of the first user's use of the second driving system exceeds the first threshold. This ensures that the first user has a certain level of proficiency with the second driving system, thus enabling the first user to have a high level of safety when using the first driving system.

[0318] Please refer to Figure 7, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 7 further illustrates the authorization method corresponding to "Scenario 1: The conditions for obtaining the right to use the first driving system include 'violation information' and 'required training.'" It is understood that the steps in the embodiments of this application can be considered as reasonable variations or supplements to the embodiments in Figure 2 or Figure 3 above; or, it is understood that the authorization method in the embodiments of this application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The authorization method shown in Figure 7 includes, but is not limited to, the following steps:

[0319] S701, the authorizing device determines the first training based on the training of the first driving system and the training already completed by the first user. For specific implementation details, please refer to the description in S301 above; it will not be repeated here.

[0320] S702, The authorization device determines whether the first user's record of using the second driving system includes any violation information that is still valid.

[0321] The second driving system is a system authorized by the first user, and the training information required to obtain the second driving system is partially the same as the training information required to obtain the first driving system.

[0322] For example, the authorization device can obtain whether the first user's usage record of the second driving system includes valid violation information by querying "vehicle information" or "user information". For instance, the authorization device obtains the system usage record of the vehicle by querying "vehicle information" as shown in Table 6 above. From the "Usage Events" in Table 6, it can be seen that the user with user identifier P_1 committed a violation while using the system with system identifier S_A_1, and the violation information is valid. Therefore, when the second driving system is S_A_1, it is considered that the first user's usage record of the second driving system includes valid violation information. As another example, the authorization device obtains the first user's system usage record by querying "user information" as shown in Table 9 above. From the "Usage Events" in Table 9, it can be seen that the first user committed a violation while using the system with system identifier S_A_2, and the violation information is valid. Therefore, when the second driving system is S_A_2, it is considered that the first user's usage record of the second driving system includes valid violation information. Please refer to Table 9. When the second driving system is S_A_1, it is assumed that the first user's record of using the second driving system does not include any violation information that is still valid.

[0323] It should be noted that the usage events recorded in the "vehicle information" or "user information" system can be more detailed or more concise, and this application does not impose any restrictions on this.

[0324] S703A: If the first user's record of using the second driving system does not contain any valid violation information, the authorization device provides the first user with the training information corresponding to the first training. For specific implementation details, please refer to the description in S302 above; it will not be repeated here.

[0325] S703B: If the first user's record of using the second driving system includes expired violation information, the authorization device provides the first user with training information corresponding to the training of the first driving system. Specific implementation details can be found in existing technologies and will not be elaborated here. Alternatively, if the first user's record of using the second driving system includes expired violation information, the method shown in Figure 4 above, or the authorization process shown in "Situation Three" above, can also be executed.

[0326] S704. The authorizing device receives the first instruction information. If the first instruction information indicates that the first user has completed the training, the first user is granted access to the first driving system. For specific implementation details, please refer to the description in S303 above; it will not be repeated here.

[0327] Please refer to Figure 8, which is a flowchart illustrating another authorization method provided in this application. The authorization method shown in Figure 8 further illustrates the authorization method corresponding to "Scenario Two: The conditions under which the right to use the first driving system is permitted include 'violation information' and 'the association between driving systems'." It is understood that the steps in the embodiments of this application can be considered reasonable variations or supplements to the embodiments in Figure 2 or Figure 4 above; or, it is understood that the authorization method in the embodiments of this application can also be considered an embodiment that can be executed independently, and this application does not limit this. The authorization method shown in Figure 8 includes, but is not limited to, the following steps:

[0328] S801, the authorization device determines the first association relationship between the first driving system and the first user's authorized system. For details on the implementation, please refer to the description of S401 above; it will not be repeated here.

[0329] S802, the authorization device determines whether the first user's record of using the second driving system includes any valid violation information. For the specific implementation of this step, please refer to the description in S702 above; it will not be repeated here.

[0330] S803: If the first user's record of using the second driving system does not contain any expired violation information, and the first association meets the conditions for obtaining the right to use the first driving system, the authorization device provides the first user with the right to use the first driving system. For specific implementation details, please refer to the description of S403 above; it will not be repeated here.

[0331] Optionally, if the first user's record of using the second driving system includes valid violation information, the method shown in Figure 3 above or the authorization method shown in "Situation 3" above can be executed.

[0332] As can be seen from the descriptions in Figures 7 and 8, before confirming that the first user has access to the first driving system, it will first determine whether the first user's record of using the second driving system includes any valid violation information. This can prevent the first user from being provided with the right to use the first driving system, which is similar to the second driving system, in the event of violation of the second driving system. This reduces the occurrence of unexpected dangers and ensures that the first user can deal with the violation information related to the second driving system in a timely manner.

[0333] In one possible implementation, the authorization device can determine whether the first user has the right to use the first driving system based on the relevant information of the first user and the identifier of the first driving system.

[0334] If the relevant information of the first user includes the first user's "user's system usage record" or the first user's "user has been authorized by the system identifier", the authorization device can determine whether the first user has the right to use the first driving system in the following ways.

[0335] Method 1: The authorization device determines whether the first user has used the first driving system based on the 'user's system usage record' in the user information, and thus determines whether the first user has the right to use the first driving system.

[0336] For example, the identifier of the first user is P_1, and the user information corresponding to the first user can be found in Table 7 above. The identifier of the first driving system is S_B_3. From Table 7, we can see that P_1 uses S_A_2 in the first time period, so it can be considered that the first user does not have the right to use the first driving system. Correspondingly, from Table 7, we can see that the first user has the right to use the S_A_2 system.

[0337] Optionally, if the 'User System Usage Record' indicates that a first user violated regulations while using a certain system, and the first user's access to the system has been suspended, then it can be considered that the first user does not have the right to use the system. As shown in Table 9, the 'User System Usage Record' records that a user violated regulations while using the system with system identifier S_A_2, and the violation information is still valid. In this case, although P_1 previously had the right to use S_A_2, it is still considered that P_1 does not have the right to use S_A_2.

[0338] Method 2: The authorization device can determine whether the first user has the right to use the first driving system based on the 'identifier of the user who has been authorized by the system' in the user information.

[0339] For example, the identifier of the first user is P_1, and the user information corresponding to the first user can be found in Table 7 above. The identifier of the first driving system is S_B_3. Table 7 shows that P_1 has been authorized by system identifiers including S_A_2 and S_B_3; therefore, the first user has the right to use the first driving system. As another example, the identifier of the first user is P_1, and the user information corresponding to the first user can be found in Table 7 above. The identifier of the first driving system is S_B_4. Table 7 shows that the first user does not have the right to use the first driving system.

[0340] Optionally, if a user's system usage records indicate that a first user violated regulations while using a certain system, and the first user's access to the system is suspended, then it can be considered that the first user does not have the right to use the system. As shown in Table 9, the "User System Usage Records" record that a user violated regulations while using the system with system identifier S_A_2, and the violation information is still valid. In this case, although P_1 previously had the right to use S_A_2, it is still considered that P_1 does not have the right to use S_A_2.

[0341] If the relevant information of the first user includes the usage records related to the first user in the "Usage Records of Systems on the Vehicle", the authorization device can determine whether the first user has the right to use the first driving system in the following ways.

[0342] Method 3: The authorization device can determine whether the first user has used the first driving system based on the 'vehicle system usage record' in the vehicle information, and thus determine whether the first user has the right to use the first driving system.

[0343] For example, the vehicle information of the first vehicle is shown in Table 4, the identifier of the first user is P_1, and the identifier of the first driving system is S_B_5. From Table 4, we can see that P_1 used the S_A_1 system during the first time period, therefore we can conclude that the first user did not have the right to use the first driving system. Correspondingly, from Table 2, we can see that the first user had the right to use the S_A_1 system.

[0344] Optionally, if the 'Vehicle System Usage Record' indicates that the first user violated regulations while using a certain system, and the first user's access to the system has been suspended, then it can be considered that the first user does not have the right to use the system. As shown in Table 6, the 'Vehicle System Usage Record' records that P_1 violated regulations while using the system with system identifier S_A_1, and the violation information is still valid. In this case, although P_1 previously had the right to use S_A_1, it is still considered that P_1 does not have the right to use S_A_1.

[0345] It should be noted that one or more of the methods mentioned above (method 1, method 2, or method 3) can be combined to determine whether a user has the right to use the first system. For example, method 1 can be used first to determine whether the user has the right to use the first system. If the result of method 1 is no, method 2 can be used to further determine whether the user has the right to use the first system. If the result of method 2 is still no, then the user is considered not to have the right to use the first system. Otherwise, the user is considered to have the right to use the first system.

[0346] In another possible implementation, the user can be granted access to the first system by updating the identifier of the authorized system in the "User Information".

[0347] For example, if the first user's "user information" is stored on server 102 and the authorization device is located on vehicle 101, the authorization device can complete the process of providing the first user with the right to use the first driving system by sending an instruction to server 102 to update the first user's "user information". The instruction includes the identifier of the first driving system.

[0348] Taking the user information of the first user as the user information corresponding to P_1 in Table 7 above, and the identifier of the first driving system as S_C_2 as an example, the instruction information sent by the authorization device to the server 102 to update the "user information" of the first user includes S_C_2. The updated user information can be represented in the form of a table, such as Table 18, which is an example of user information.

[0349] Table 18 User Information

[0350] It should be noted that this application does not limit the storage format or location of user information. For example, user information may also be stored in the vehicle's storage unit or distributed across multiple devices' storage units.

[0351] Understandably, once the authorization device grants the first user the right to use the first driving system, the first user can then use the first driving system. For example, the first user can use the first driving system by logging into their account.

[0352] To better understand the licensing method provided in this application, several possible licensing scenarios are provided below as examples.

[0353] Authorization Scenario 1: The authorization device grants the first user the right to use the same system in different vehicle models.

[0354] For example, the user information of the first user is shown in Table 19 below, the vehicle information of the first user's frequently used vehicles is shown in Table 20 below, the vehicle information of the first user's vehicles to be used is shown in Table 21 below, and the system information requested by the first user is shown in Table 22 below.

[0355] Table 19 User Information

[0356] Table 20 Vehicle Information

[0357] Table 21 Vehicle Information

[0358] Table 22 System Information

[0359] Based on Tables 19 to 22 above, it can be seen that the system authorized by the first user includes S_A_1_OEM2_Model2 on vehicle V_2, and the system the first user wishes to use is S_A_1_OEM1_Model1 on vehicle V_1. The authorization device can determine whether the suppliers of S_A_1_OEM2_Model2 and S_A_1_OEM1_Model1 are the same by querying the supplier's system information. If the suppliers of S_A_1_OEM2_Model2 and S_A_1_OEM1_Model1 are the same, the authorization device can grant the first user the right to use S_A_1_OEM1_Model1. For a detailed understanding of the authorization process, please refer to the corresponding content above; it will not be elaborated upon here.

[0360] Authorization Scenario 2: The authorization device grants the first user the right to use different systems that are related.

[0361] For example, the user information of the first user is shown in Table 23 below, the system information of the system authorized by the first user is shown in Tables 24 and 25 below, and the system information requested by the first user is shown in Table 26 below.

[0362] Table 23 User Information

[0363] Table 24 System Information for S_A_1_OEM2_Model2

[0364] Table 25 System Information for S_M_1_OEM3_Model3

[0365] Table 26 System Information

[0366] As shown in Tables 23 to 26 above, the systems authorized by the first user include vehicles S_A_1_OEM2_Model2 and S_M_1_OEM3_Model3. S_A_1_OEM2_Model2 conforms to both ISO and GB standards. The system S_B_2_OEM1_Model1, which the first user wishes to use, also conforms to both ISO and GB standards. Therefore, the authorization device can grant the first user the right to use S_B_2_OEM1_Model1. The specific authorization process can be understood by referring to the corresponding content mentioned above, and will not be detailed here.

[0367] The above content exemplifies the authorization method provided by this application. This method allows the first user to be granted the right to use the first driving system without any additional operations, thereby simplifying the authorization process and improving the user experience of the first user.

[0368] In addition, this application provides several triggering conditions for the above-mentioned authorized methods, as follows:

[0369] Condition 1: The authorization device receives the request message from the first user.

[0370] The aforementioned request message is used to request the use of the first driving system, and the request message includes the identifier of the first driving system and the identifier of the first user.

[0371] For example, when a first user needs to use the first driving system on the first vehicle, they can send a request message to the authorization device through the human-machine interface on the first vehicle to request the use of the first driving system. For instance, the first user can send the request message to the authorization device through the human-machine interface of the vehicle's infotainment system. Another example is sending the request message to the authorization device through the voice interaction system on the first vehicle.

[0372] For example, if a first user needs to use the first driving system on the first vehicle, a request message can also be sent to the authorization device through a terminal device connected to the vehicle. For instance, the first user can send the request message to the authorization device through a terminal device such as a mobile phone, smartwatch, smart glasses, smart headphones, smart speaker, or smart screen connected to the vehicle.

[0373] Condition 2: The condition of the vehicle and / or the condition of the driver and passengers meet the preset conditions.

[0374] The vehicle condition includes the surrounding environment and the vehicle's driving status. The occupant condition includes their physical condition and behavioral state. Preset conditions can be set by the system supplier based on the system's usage scenario. For example, the usage scenario of a third-party driving system is typically a target scenario; therefore, the aforementioned preset conditions can be set as the target scenario. When the detected vehicle condition or occupant condition falls within the target scenario, the aforementioned authorization method is triggered.

[0375] For example, lane keeping assist systems are typically used on long, straight roads. Therefore, when the system detects that the road a vehicle is about to cross consists mostly of long, straight sections, it can trigger an authorization device to grant the driver permission to use the lane keeping assist system. Upon authorization, relevant information can be sent to the driver and passengers, indicating that they can use the lane keeping assist system to help them better participate in traffic. Of course, if the lane keeping assist system is already authorized by the driver and passengers, relevant information can be directly sent to them, indicating that they can use the lane keeping assist system.

[0376] For example, audio-visual entertainment systems are typically used when there are passengers in the back seat of a vehicle, or during long-distance driving. Therefore, when passengers are detected in the back seat, the authorization device can be triggered to grant the driver and passengers access to the audio-visual entertainment system. Upon authorization, relevant information can be pushed to the driver and passengers, indicating that they can use the system to enhance their travel experience. Of course, if the audio-visual entertainment system is already authorized by the driver and passengers, relevant information can be directly pushed to them, indicating that they can use the system.

[0377] It is understandable that, in the above situation, the driver and passengers can be understood as the aforementioned first user, and the lane keeping assist system or audio-visual entertainment system can be understood as the aforementioned first system.

[0378] Condition 3: The authorized device receives the target message.

[0379] The target message in "Condition Three" is similar to the request message in "Condition One," both used to trigger the authorization method that grants the first user access to the first driving system. The difference lies in that the request message in "Condition One" is sent by the first user, while the target message in "Condition Three" is sent by a user or entity other than the first user. For example, the target message could be sent by the system vendor or by a superuser capable of managing the first user. Several possible scenarios are shown below:

[0380] Scenario 1: The designated driver company authorizes designated drivers in batches.

[0381] For example, designated drivers often need to drive different car models and use different systems. Expecting them to learn these systems on their own would obviously reduce efficiency and affect service quality. Designated driver companies can negotiate with system suppliers or OEMs to provide centralized training to drivers before granting them system access in batches. The authorization method provided in this application can be used to increase the speed of authorization during this process.

[0382] Scenario 2: The car rental company authorizes the car rental user.

[0383] For example, the vehicles and systems rented by car rental users may be ones they have never used before. It is clearly inappropriate to require rental users to acquire access to the systems on the rental vehicles through training. Therefore, car rental companies can negotiate with system suppliers or OEMs to obtain completed training from rental users and then grant them access to the systems on the rental vehicles in batches using the authorization method provided in this application. This application does not limit how the completed training from rental users is obtained. For example, rental users can provide proof of completed training themselves. Another example is that the car rental company can obtain the completed training from the OEM associated with the rental user. Yet another example is that various OEMs or system suppliers can build a public cloud to share one or more of the following: system information, user information, vehicle information, or training information. The car rental company can then access the completed training from rental users through this public cloud.

[0384] As can be seen from the above description, the authorization method provided in this application can be triggered actively by the user, automatically by preset rules, or by other entities. It can cover a wide range of application scenarios, comprehensively simplify the system's authorization process, improve the speed of system authorization, and thus enhance the user experience.

[0385] In one possible implementation, this application does not limit when the authorization method is triggered. For example, the authorization method can be triggered temporarily or in advance. Temporary triggering can be understood as triggering the authorization method only when the first user needs to use the first system. In advance triggering can be understood as triggering the authorization method some time before the first user uses the first system.

[0386] The use cases for temporary triggering are as follows:

[0387] For example, if a vehicle needs to reverse due to a temporary road closure while driving, the driver can send a message to the authorization device requesting access to the reversing assistance system to trigger the authorization operation of the authorization device.

[0388] For example, while the vehicle is in motion, if the vehicle's condition and / or the condition of the occupants meet preset conditions, the authorization device will be triggered to perform an authorization operation. For a specific example, please refer to the above description of "Condition Two: The vehicle's condition and / or the condition of the occupants meet preset conditions".

[0389] The scenarios that are triggered prematurely are as follows:

[0390] For example, before setting off, if a driver anticipates needing to use a specific system (e.g., an automatic parking assist system), they can send a request to the authorization device to obtain access to the system in advance. It's important to note that during the advance authorization process, the driver can perform the relevant operations either through the vehicle or through a terminal device associated with the vehicle. For instance, a driver could perform the advance authorization process at home by operating a mobile phone associated with the vehicle.

[0391] In summary, the authorization method provided in this application grants the first user access to the first driving system by using relevant information about the first driving system and information about the systems already authorized to the first user. This allows the first user to access the first driving system without requiring additional operations, thus simplifying the authorization process and improving the user experience. Furthermore, this application also illustrates various triggering conditions and timings for the authorization method to broaden its application scope and comprehensively enhance the user experience during the authorization process.

[0392] The methods provided in the above embodiments of this application are described from the perspective of an authorized device. To implement the functions of the methods provided in the above embodiments of this application, the authorized device may include hardware structures and / or software units, implementing the above functions in the form of hardware structures, software units, or a combination of hardware structures and software units. Whether a particular function is executed in the form of hardware structures, software units, or a combination of hardware structures and software units depends on the specific application and design constraints of the technical solution.

[0393] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 2 to 8. The authorized apparatus provided by the embodiments of this application is described in detail below with reference to Figure 9. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments. Therefore, for any content not described in detail, please refer to the descriptions in the method embodiments above.

[0394] Figure 9 is a schematic block diagram of an authorization device provided in an embodiment of this application, used to implement the authorization methods shown in Figures 2 to 8 above. For example, the authorization device 900 can be a software unit or a chip system. The chip system can be composed of chips, or it can include chips and other discrete devices. The authorization device 900 includes a processing unit 901, which is used to process data. For example, the processing unit 901 can determine whether to grant the first user the right to use the first driving system based on the relevant information of the first driving system and the relevant information of the first user having been authorized by the system. The authorization device 900 may also include a communication unit 902, which can communicate with the processor. For example, the identifier of the first driving system and the identifier of the first user can be obtained through the communication unit 902. The communication unit 902 may also be called a communication interface, transceiver unit, input / output interface, etc.

[0395] In one possible implementation, the processing unit 901 is used to provide the first user with the right to use the first driving system based on relevant information of the first driving system and relevant information of the system that the first user has been authorized to use.

[0396] In another possible implementation, the communication unit 902 is used to acquire the identifier of the first driving system and the identifier of the first user. The communication unit 902 is also used to determine relevant information about the first driving system based on the identifier of the first driving system, and further to determine relevant information about the first user being authorized by the system based on the identifier of the first user.

[0397] Optionally, the communication unit 902 can obtain the identifier of the first driving system and the identifier of the first user by receiving request information from the first user.

[0398] Alternatively, the communication unit 902 can acquire the identifier of the first driving system and the identifier of the first user by setting preset trigger conditions.

[0399] In another possible implementation, the processing unit 901 is specifically used to determine whether the first user's scope of authority includes the first driving system based on relevant information about the first driving system and relevant information about the system the first user has been authorized to. If the first user's scope of authority includes the first driving system, the first user is granted the right to use the first driving system. If the first user's scope of authority does not include the first driving system, training information for the first driving system can be provided to the first user, allowing the first user to acquire the right to use the first driving system through training.

[0400] In another possible implementation, information related to the first driving system includes the conditions under which the right to use the first driving system can be obtained.

[0401] Optionally, the conditions under which the right to use the first driving system can be obtained can be set by the supplier of the first driving system. Of course, the conditions under which the right to use the first driving system can also be updated.

[0402] In another possible implementation, the conditions under which the right to use the first driving system is permitted to be acquired include one or more of the following: required training, association between driving systems, or coverage of the right to use between driving systems.

[0403] Optionally, if there are multiple conditions under which the right to use the first driving system can be obtained, the processing unit 901 may determine whether the right to use the first driving system can be provided to the first user in the order of judging the coverage relationship of the right to use between driving systems, the association relationship between driving systems, and the required training.

[0404] In another possible implementation, system features include one or more of the following: regulations, standards, assessments, certification levels, specifications, guidelines, suppliers, or functions.

[0405] In another possible implementation, the processing unit 901 is specifically used to determine the first training based on the training corresponding to the first driving system and the training already completed by the first user.

[0406] The communication unit 902 is also used to provide the first user with training information corresponding to the first training.

[0407] The communication unit 902 is also used to receive the first instruction information.

[0408] The aforementioned processing unit 901 is further configured to, when the first instruction information indicates that the first user has completed the training information, grant the first user the right to use the first driving system.

[0409] Optionally, the relevant information about the first driving system includes the conditions under which the right to use the first driving system can be obtained and the corresponding training. The conditions under which the right to use the first driving system can be obtained include the required training. The relevant information about the first user being authorized to the system includes the training that the first user has completed.

[0410] In another possible implementation, after the processing unit 901 grants the first user the right to use the first driving system, the processing unit 901 is also used to expand the scope of the first user's permissions based on relevant information of the first driving system.

[0411] In another possible implementation, the processing unit 901 is further configured to provide the first user with the right to use the first driving system based on the system characteristics of the first driving system and the system characteristics of the system that the first user has been authorized to use.

[0412] In another possible implementation, the processing unit 901 is specifically used to grant the first user the right to use the first driving system when the system characteristics of the first driving system and the system characteristics of the first user being authorized by the system meet one or more of the following conditions.

[0413] The first driving system and the first user have been authorized by the system to follow the same regulations, or,

[0414] The first driving system and the first user have been authorized by the system to follow the same standards, or,

[0415] The first user has been authorized to follow the standards of the system, including the standards followed by the first driving system; or...

[0416] The first driving system and the first user have passed the same evaluation by the authorized system, or,

[0417] The first driving system and the first user have the same authentication level as the authorized system, or,

[0418] The first driving system and the first user have been authorized by the system to follow the same specifications, or,

[0419] The first driving system and the first user have been authorized by the system to follow the same guidelines, or,

[0420] The supplier of the first driving system is the same as the supplier of the system authorized by the first user, or...

[0421] The first user has been authorized to use the functions of the first driving system; or...

[0422] The functions of the first driving system are the same as those of the first user's authorized system.

[0423] Optionally, the various scenarios described above regarding providing the first user with the right to use the first driving system can be set by the supplier of the first driving system.

[0424] In another possible implementation, the processing unit 901 is specifically used to provide the first user with the right to use the first driving system when the first user's right to use the first driving system is covered by the right to use the authorized system, and / or the right to use the first user is covered by the right to use the authorized system.

[0425] In another possible implementation, the conditions under which the right to use the first driving system can be obtained also include: system usage duration, and / or, violation information.

[0426] In another possible implementation, the processing unit 901 is further configured to determine the first user's first usage record based on the first user's identifier, and to determine that the first user has been authorized by the system based on the first usage record.

[0427] In another possible implementation, the first usage record is used to describe the correspondence between the vehicle's identifier, the driving system's identifier, and the time period during which the driving system was used. Optionally, the first usage record may also include information on violations committed by the driving system.

[0428] In another possible implementation, the communication unit 902 is further configured to acquire the identifier of the first vehicle. The processing unit 901 is further configured to determine a second usage record of the driving system on the first vehicle based on the identifier of the first vehicle, and to determine, based on the second usage record, that the first user has been authorized by the system. Optionally, the first vehicle is the vehicle requested to be driven by the first user.

[0429] In another possible implementation, the second usage record is used to describe the correspondence between the user's identifier, the driving system's identifier, and the time period during which the driving system was used. Optionally, the second usage record may also include information on violations committed by the driving system.

[0430] The unit division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into a single processor, exist as separate physical units, or be integrated into a single unit. The integrated units described above can be implemented in hardware or as software functional units.

[0431] It is understood that the functions of the communication unit in the above embodiments can be implemented by a transceiver, and the functions of the processing unit can be implemented by a processor. The transceiver may include a transmitter and / or a receiver, etc., respectively used to implement the functions of the sending unit and / or the receiving unit. The following description, with reference to Figure 10, illustrates this point.

[0432] Figure 10 is a schematic block diagram of another licensing device provided in an embodiment of this application. The licensing device 1000 shown in Figure 10 can be a hardware circuit implementation of the device shown in Figure 9. The licensing device 1000 is used to implement the licensing methods shown in Figures 2 to 8 above. For ease of explanation, Figure 10 only shows the main components of this licensing device.

[0433] The licensing device 1000 shown in Figure 10 includes at least one processor 1001. The licensing device 1000 may also include at least one memory 1002 for storing program instructions and / or data. The memory 1002 and the processor 1001 are coupled. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information interaction between devices, units, or modules. The processor 1001 can operate collaboratively with the memory 1002, and the processor 1001 can execute program instructions stored in the memory 1002. At least one of the at least one memory 1002 may be included in the processor 1001.

[0434] The licensing device 1000 may further include a communication interface 1003 for communicating with other devices via a transmission medium, thereby enabling the licensing device 1000 to communicate with other devices. In this embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface. In this embodiment, when the communication interface is a transceiver, the transceiver may include an independent receiver, an independent transmitter, or a transceiver integrating transceiver functions, or an interface circuit.

[0435] It should be understood that the connection medium between the processor 1001, memory 1002, and communication interface 1003 is not limited in the embodiments of this application. In the embodiments of this application, the memory 1002, processor 1001, and communication interface 1003 are connected by a communication bus 1004 in FIG10. The bus is represented by a thick line in FIG10. The connection methods between other components are only illustrative and are not intended to be limiting. The bus may include an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in FIG10, but this does not mean that there is only one bus or one type of bus. The operations performed by the processor 1001 can be referred to the operations performed by the processing unit 901 in FIG9, and will not be repeated here. The operations performed by the communication interface 1003 can be referred to the operations performed by the communication unit 902 in FIG9, and will not be repeated here.

[0436] A chip includes: a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, a method is provided to cause the device to perform the flow shown in any one of Figures 2 to 8 above.

[0437] In this application embodiment, the processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application embodiment. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0438] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0439] This application also provides another licensing device, which includes a processor and a memory, wherein the memory is used to store a computer program and the processor is used to execute the computer program, causing the device to perform the licensing method obtained by the above-described Figures 2 to 8 and combinations thereof.

[0440] This application also provides a vehicle that includes the aforementioned authorized device. Optionally, a detailed description of the vehicle can be found in the description of the vehicle 101 above, and will not be repeated here.

[0441] This application also provides a server, which includes the aforementioned authorized device. Optionally, a detailed description of the server can be found in the description of the server 102 described above, and will not be repeated here.

[0442] This application also provides a terminal device, which includes the aforementioned authorized apparatus. Optionally, a detailed description of the terminal device can be found in the description of the terminal device 103 described above, and will not be repeated here.

[0443] This application also provides an authorization system, including the authorization device described above. Optionally, the authorization system includes a vehicle and a server, or a vehicle, a server, and a terminal device.

[0444] This application provides a computer program that, when executed by a processor, performs the authorized method obtained by the above-described Figures 2 to 8 and combinations thereof.

[0445] This application provides a computer program product comprising: a computer program (also referred to as code or instructions); when the computer program is run, it causes a computer to execute the authorization method obtained by the above-described Figures 2 to 8 and their combinations.

[0446] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor, implement the authorized method obtained by the above-described Figures 2 to 8 and their combinations.

[0447] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

1. An authorization method, characterized in that, The method includes: Obtain the identifier of the first driving system and the identifier of the first user; Relevant information about the first driving system is obtained based on the identifier of the first driving system; Based on the identifier of the first user, the relevant information of the first user that has been authorized by the system is determined; Based on the relevant information of the first driving system and the relevant information of the system that the first user has been authorized to use, the right to use the first driving system is granted to the first user.

2. The method according to claim 1, characterized in that, Information related to the first driving system, including the conditions under which the right to use the first driving system can be obtained.

3. The method according to claim 2, characterized in that, The conditions under which the right to use the first driving system is permitted include one or more of the following: necessary training, the relationship between driving systems, or the overlap of the right to use between driving systems.

4. The method according to claim 3, characterized in that, The relationships between driving systems are used to describe the relationships between the system characteristics of the driving systems; the system characteristics include one or more of the following: regulations, standards, assessments, certification levels, specifications, guidelines, suppliers, or functions.

5. The method according to any one of claims 1-4, characterized in that, The relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained and the corresponding training for the first driving system. The conditions under which the right to use the first driving system is permitted to be obtained include the required training. The relevant information of the first user authorized system includes the training that the first user has completed. The provision of access to the first driving system to the first user based on relevant information of the first driving system and relevant information of the system authorized to the first user includes: Based on the training corresponding to the first driving system and the training already completed by the first user, the first training is determined; the first training is the training that the first user has not completed in the training corresponding to the first driving system. Provide the first user with training information corresponding to the first training, and receive first instruction information; the first instruction information is used to instruct the first user on the status of learning the training information; If the first instruction indicates that the first user has completed the training, the first user is granted the right to use the first driving system.

6. The method according to any one of claims 1-5, characterized in that, The relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained and the system characteristics of the first driving system. The conditions under which the right to use the first driving system is permitted to be obtained include the relationship between driving systems. The relevant information of the system authorized by the first user includes the system characteristics of the system authorized by the first user. The system characteristics include one or more of the following: regulations, standards, assessments, certification levels, specifications, guidelines, suppliers, or functions. The provision of access to the first driving system to the first user based on relevant information of the first driving system and relevant information of the system authorized to the first user includes: Based on the system characteristics of the first driving system and the system characteristics of the system that the first user has been authorized to use, the right to use the first driving system is granted to the first user.

7. The method according to claim 6, characterized in that, The provision of the right to use the first driving system to the first user based on the system characteristics of the first driving system and the system characteristics of the system authorized by the first user includes: providing the right to use the first driving system to the first user when the system characteristics of the first driving system and the system characteristics of the system authorized by the first user meet one or more of the following conditions; The first driving system and the first user's authorized system follow the same regulations; or, The first driving system follows the same standards as the system authorized by the first user; or, The standards followed by the first user's authorized system include those followed by the first driving system; or, The first driving system and the first user have passed the same evaluation by the authorized system; or, The first driving system has the same authentication level as the first user's authorized system; or, The first driving system follows the same specifications as the system authorized by the first user; or, The first driving system follows the same guidelines as the first user's authorized system; or, The supplier of the first driving system is the same as the supplier of the system authorized by the first user; or, The first user has been authorized to use the functions of the first driving system; or, The functions of the first driving system are the same as those of the system authorized by the first user.

8. The method according to any one of claims 1-7, characterized in that, The relevant information of the first driving system includes the conditions under which the right to use the first driving system is allowed to be obtained and the coverage relationship of the right to use the first driving system. The conditions under which the right to use the first driving system is allowed to be obtained include the coverage relationship of the right to use between driving systems. The relevant information of the first user's authorized system includes the coverage relationship of the right to use the first user's authorized system. Based on relevant information of the first driving system and relevant information of the system authorized to the first user, the right to use the first driving system is granted to the first user, including: In cases where the first user's right to use the first driving system is overridden by the right to use the authorized system, and / or the first user's right to use the authorized system is overridden by the right to use the first driving system, the first user is provided with the right to use the first driving system.

9. The method according to any one of claims 1-8, characterized in that, The conditions under which the right to use the first driving system can be obtained also include: system usage time, and / or, violation information.

10. The method according to claim 9, characterized in that, The relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained, and the conditions under which the right to use the first driving system is permitted to be obtained include the system usage time; the relevant information of the first user authorized to the system includes the system usage time of the first user authorized to the system; The provision of access to the first driving system to the first user based on relevant information of the first driving system and relevant information of the system authorized to the first user includes: If the first user uses the system that has been authorized to the first user for a duration greater than or equal to a first threshold, the first user is granted the right to use the first driving system.

11. The method according to claim 9 or 10, characterized in that, The relevant information of the first driving system includes the conditions under which the right to use the first driving system is permitted to be obtained, and the conditions under which the right to use the first driving system is permitted to be obtained include violation information; the relevant information of the first user authorized to the system includes the first user's authorized system usage records; The provision of access to the first driving system to the first user based on relevant information of the first driving system and relevant information of the system authorized to the first user includes: The system does not include any expired violation information in the first user's authorized usage records, thus granting the first user the right to use the first driving system.

12. The method according to any one of claims 1-11, characterized in that, The step of determining the relevant information of the authorized system based on the first user's identifier includes: The first user's first usage record is determined based on the first user's identifier, and the first usage record is the first user's history of using the driving system. Based on the first usage record, it is determined that the first user has been authorized by the system.

13. The method according to claim 12, characterized in that, The first usage record is used to describe the correspondence between the vehicle identifier, the driving system identifier, and the time period during which the driving system is used.

14. The method according to any one of claims 1-13, characterized in that, The step of determining the relevant information of the authorized system based on the identifier of the first user further includes: Obtain the identifier of the first vehicle, which is the vehicle requested by the first user to drive; A second usage record of the driving system on the first vehicle is determined based on the identifier of the first vehicle, and the second usage record is the usage record of the driving system on the first vehicle; Based on the second usage record, it is determined that the first user has been authorized by the system.

15. The method according to claim 14, characterized in that, The second usage record is used to describe the correspondence between the user's identifier, the driving system's identifier, and the time period during which the driving system is used.

16. The method according to any one of claims 1-15, characterized in that, The method further includes: The system receives a request message from the first user, the request message being used to request the use of the first driving system, the request message including the identifier of the first driving system and the identifier of the first user.

17. An authorization device, characterized in that, Includes units for performing the method as described in any one of claims 1 to 16.

18. An authorization device, characterized in that, Includes a processor for performing the method as described in any one of claims 1 to 16.

19. A terminal, characterized in that, The terminal includes the authorized device as described in any one of claims 17 or 18.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1 to 16.

21. A computer program product, characterized in that, include: Instructions or computer programs; When the instructions or the computer program are executed, the method as described in any one of claims 1 to 16 is implemented.

Images