Vehicle automatic driving authority management method, device and electronic device
By introducing distributed access control into the vehicle autonomous driving system and utilizing a unified interface and inter-process/Ethernet communication, the problems of insufficient security and scalability of vehicle autonomous driving control software are solved, and flexible access control and efficient resource access control are achieved.
Patent Information
- Application Number
- CN202211059923.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-30
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2042-08-30
AI Technical Summary
Existing vehicle autonomous driving control software lacks a unified interface for obtaining resource permissions, resulting in poor security and scalability. Furthermore, permission configuration depends on a single developer, making it difficult to manage flexibly.
A distributed permission management approach is adopted, which distributes permission requests and arbitration by setting up a unified interface on the vehicle and server sides, provides a unified permission management interface, and allows permission configuration to be independent of function development. Permission management is carried out using inter-process communication or Ethernet communication.
It improves the safety and scalability of vehicle autonomous driving systems, and makes permission management more flexible and efficient. Developers only need to call a unified interface to obtain resource permissions, and permissions can be configured independently at the system level.
Smart Images

Figure CN115426172B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of vehicle autonomous driving, and in particular to a method, device and electronic equipment for managing permissions for vehicle autonomous driving. Background Art
[0002] The autonomous driving domain controller deployed in the vehicle has functions such as remote network connection, vehicle control, and sensor interaction. If there is no function or resource access permission control, it may lead to the theft of key vehicle data or incorrect operation of key functions, which may also lead to autonomous driving safety accidents. A typical case is that although the vehicle's networking template is exposed to the Internet, it is never allowed to call any vehicle operation-related functions.
[0003] However, the vehicle's autonomous driving control software generally has not yet implemented access rights management, or has adopted relatively simple restriction measures. For example, access rights are fixed directly in the relevant software when the function is developed, and the acquisition of permissions is completely determined by a single developer, and there are many inconveniences in the subsequent changes of software permissions.
[0004] Therefore, the existing vehicle autonomous driving control software does not have a unified resource permission acquisition interface, and has poor security and scalability. Summary of the invention
[0005] In view of this, the purpose of the present invention is to provide a method, device and electronic device for permission management of vehicle automatic driving, so as to set a unified interface to obtain resource permissions and improve security and scalability.
[0006] In a first aspect, an embodiment of the present invention provides a method for permission management of vehicle autonomous driving, which is applied to a permission management system for vehicle autonomous driving. The permission management system includes a vehicle end and a service end. The vehicle end is provided with a first interface for resource access request, and the service end is provided with a second interface for access permission management, and the first interface is connected to the second interface. The method includes: determining whether the first interface caches permission information of the target resource; if not, the first interface sends a permission configuration request for the target resource to the second interface; if the second interface determines that the first interface has permission to the target resource based on the permission configuration request, a query result including the permission information of the target resource is generated; the second interface sends the query result to the first interface; the first interface processes the target resource based on the permission information of the target resource.
[0007] In a preferred embodiment of the present invention, the method further comprises: initializing the first interface; and establishing a connection between the first interface and the second interface.
[0008] In a preferred embodiment of the present invention, the above-mentioned step of establishing a connection between the first interface and the second interface includes: if the vehicle end and the service end are set in the same electronic control unit, establishing a connection between the first interface and the second interface by means of inter-process communication; if the vehicle end and the service end are set in different electronic control units, establishing a connection between the first interface and the second interface by means of Ethernet communication.
[0009] In a preferred embodiment of the present invention, after the step of determining whether the first interface caches the permission information of the target resource, the method further comprises: if yes, processing the target resource based on the permission information of the target resource.
[0010] In a preferred embodiment of the present invention, after the step of the second interface sending the query result to the first interface, the method further comprises: the first interface caches the permission information of the target resource.
[0011] In a preferred embodiment of the present invention, after the step of the first interface caching the permission information of the target resource, the method further comprises: the first interface performing a management operation on the permission information of the target resource.
[0012] In a preferred embodiment of the present invention, after the step of the first interface processing the target resource based on the permission information of the target resource, the method further includes: deinitializing the first interface; and disconnecting the first interface from the second interface.
[0013] In a second aspect, an embodiment of the present invention also provides a permission management device for vehicle autonomous driving, which is applied to a permission management system for vehicle autonomous driving. The permission management system includes a vehicle end and a service end. The vehicle end is provided with a first interface for resource access request, and the service end is provided with a second interface for access permission management, and the first interface is connected to the second interface. The device includes: a permission information query module, used to determine whether the first interface caches permission information of the target resource; a permission configuration request module, used if not, the first interface sends a permission configuration request for the target resource to the second interface; a query result generation module, used if the second interface determines that the first interface has permission to the target resource based on the permission configuration request, generates a query result including the permission information of the target resource; a query result sending module, used for the second interface to send the query result to the first interface; a target resource processing module, used for the first interface to process the target resource based on the permission information of the target resource.
[0014] In a third aspect, an embodiment of the present invention provides an electronic device, including a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the steps of the above-mentioned vehicle autonomous driving authority management method.
[0015] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the steps of the above-mentioned vehicle autonomous driving authority management method.
[0016] The embodiments of the present invention bring the following beneficial effects:
[0017] The embodiment of the present invention provides a method, device and electronic device for permission management of vehicle automatic driving. If the first interface set at the vehicle end does not cache the permission information of the target resource, the first interface sends a permission configuration request of the target resource to the second interface set at the server end; the second interface determines that the first interface has the permission of the target resource based on the permission configuration request, and generates a query result including the permission information of the target resource; the first interface processes the target resource based on the permission information of the target resource sent by the second interface. This method realizes distributed master-slave permission management, and the permission request and permission arbitration are distributed to different processes, with strong scalability and security; this method provides a unified permission management interface, and developers only need to call the unified interface to obtain the result of whether they have the permission to access the response resource; the configuration of permissions in this method can be completely independent of the development of functions, and the permission configuration can be completely formulated by the system level, so that developers can focus more on the development of functions.
[0018] Other features and advantages of the present disclosure will be set forth in the following description, or some features and advantages may be inferred or unambiguously determined from the description, or may be learned by implementing the above-mentioned technology of the present disclosure.
[0019] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0021] Figure 1 A schematic diagram of a vehicle autonomous driving authority management system provided by an embodiment of the present invention;
[0022] Figure 2 A flowchart of a method for managing permissions for automatic driving of a vehicle provided by an embodiment of the present invention;
[0023] Figure 3 A flowchart of another method for managing permissions for autonomous driving of a vehicle provided by an embodiment of the present invention;
[0024] Figure 4 A schematic diagram of a method for managing permissions for automatic driving of a vehicle provided by an embodiment of the present invention;
[0025] Figure 5 A schematic diagram of the structure of a permission management device for automatic driving of a vehicle provided by an embodiment of the present invention;
[0026] Figure 6 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0028] At present, the autonomous driving domain controller deployed in the vehicle has functions such as remote network connection, vehicle control, and sensor interaction. If there is no function or resource access permission control, it may lead to the theft of key vehicle data or incorrect operation of key functions, which may also lead to autonomous driving safety accidents. A typical case is that although the vehicle's networking template is exposed to the Internet, it is never allowed to call any vehicle operation-related functions.
[0029] However, the vehicle's autonomous driving control software generally has not yet implemented access rights management, or has adopted relatively simple restriction measures. For example, the access rights are fixed directly in the relevant software when the function is developed, the acquisition of permissions is entirely determined by a single developer, and there are many inconveniences in the subsequent changes of software permissions. Therefore, the existing vehicle's autonomous driving control software does not have a unified resource permission acquisition interface, and its security and scalability are poor.
[0030] Based on this, an embodiment of the present invention provides a method, device and electronic device for permission management of vehicle autonomous driving, and specifically provides a method for managing software access rights of a distributed autonomous driving domain controller, which can set a unified interface to obtain resource permissions, thereby improving security and scalability.
[0031] To facilitate understanding of this embodiment, a method for managing permissions for automatic driving of a vehicle disclosed in an embodiment of the present invention is first introduced in detail.
[0032] Embodiment 1:
[0033] An embodiment of the present invention provides a method for permission management of vehicle autonomous driving. The method for permission management of vehicle autonomous driving is applied to a permission management system for vehicle autonomous driving. The permission management system includes a vehicle end and a service end. The vehicle end is provided with a first interface for resource access requests, and the service end is provided with a second interface for access permission management. The first interface is connected to the second interface.
[0034] See also Figure 1 A schematic diagram of a permission management system for vehicle autonomous driving is shown, in which the first interface may be an AP (Access Point, resource access request point) and the second interface may be an AM (Access Manager, access permission manager).
[0035] The permission management method provided in this embodiment provides a unified first interface AP, which can actively connect to the second interface AM through Ethernet or IPC (Inter-Process Communication) when the process starts, and pass in the resource ID that needs to be accessed when calling the interface.
[0036] If the first interface and the second interface are not in the same ECU (Electronic Control Unit), the user process with access rights can be requested through an encrypted network (such as Ethernet); if the first interface and the second interface are in the same ECU, the user process with access rights can be requested through IPC. Among them, ECU is also called "driving computer" or "on-board computer", which is composed of microcontroller, memory, input / output interface, analog-to-digital converter, and large-scale integrated circuits such as shaping and driving.
[0037] In addition, the access permission manager set by the server is used to arbitrate permission requests, and the server can also be set with encrypted permission configuration data.
[0038] Based on the above description, see Figure 2 A flowchart of a method for managing permissions for autonomous driving of a vehicle is shown, and the method for managing permissions for autonomous driving of a vehicle comprises the following steps:
[0039] Step S202: Determine whether the first interface has cached permission information of the target resource.
[0040] After initializing the first interface and establishing a connection between the first interface and the second interface, first determine whether the first interface has cached permission information of the target resource. If the first interface has cached permission information of the target resource, the first interface does not need to request permission information from the second interface, and can directly process the target resource based on the permission information of the target resource cached by the first interface.
[0041] Step S204: If not, the first interface sends a permission configuration request for the target resource to the second interface.
[0042] If the first interface does not cache the permission information of the target resource, the first interface needs to send a permission configuration request for the target resource to the second interface. The first interface can send the permission configuration request for the target resource to the second interface via IPC or Ethernet. IPC refers to the interaction between the data of two processes, and Ethernet is a computer local area network.
[0043] Step S206: If the second interface determines that the first interface has the permission of the target resource based on the permission configuration request, a query result including the permission information of the target resource is generated.
[0044] After the second interface receives the permission configuration request sent by the first interface, it can search the permission configuration data pre-stored on the server whether the first interface has the permission to the target resource. If yes, the second interface can generate a query result including the permission information of the target resource. If not, it can be determined that the first interface does not have the permission to the target resource. If the first interface cannot process the target resource, the second interface can send an error report to the first interface.
[0045] Step S208: The second interface sends the query result to the first interface.
[0046] If the first interface has the authority of the target resource, the second interface may generate a query result including the authority information of the target resource, and send the query result to the first interface.
[0047] Step S210: The first interface processes the target resource based on the permission information of the target resource.
[0048] After the first interface receives the query result including the permission information of the target resource, the permission information of the target resource can be parsed from the query result, and the target resource can be processed according to the permission information of the target resource to complete the overall operation of permission management and resource processing.
[0049] The first interface may also cache the permission information of the target resource so that the next time the target resource is processed, there is no need to send a permission configuration request for the target resource to the second interface again, thereby improving the processing efficiency of permission management and resource processing.
[0050] The embodiment of the present invention provides a method for managing permissions for automatic driving of a vehicle. If the first interface set at the vehicle end does not cache the permission information of the target resource, the first interface sends a permission configuration request for the target resource to the second interface set at the server end; the second interface determines that the first interface has the permission for the target resource based on the permission configuration request, and generates a query result including the permission information of the target resource; the first interface processes the target resource based on the permission information of the target resource sent by the second interface. This method implements distributed master-slave permission management, and permission requests and permission arbitration are distributed to different processes, with strong scalability and security; this method provides a unified permission management interface, and developers only need to call the unified interface to obtain the result of whether they have the permission to access the response resource; the configuration of permissions in this method can be completely independent of the development of functions, and the permission configuration can be completely formulated by the system level, so that developers can focus more on the development of functions.
[0051] Embodiment 2:
[0052] The embodiment of the present invention also provides another method for managing the rights of the automatic driving of a vehicle; this method is implemented on the basis of the method of the above embodiment; see Figure 3 A flowchart of another method for managing permissions for autonomous driving of a vehicle is shown, and the method for managing permissions for autonomous driving of a vehicle comprises the following steps:
[0053] Step S302: Determine whether the first interface has cached permission information of the target resource.
[0054] The method provided in this embodiment further includes: initializing the first interface; and establishing a connection between the first interface and the second interface.
[0055] See also Figure 4 A schematic diagram of a method for managing permissions for autonomous driving of a vehicle is shown. After the second interface AM reads the encrypted permission configuration, the user program calls the first interface, initializes the first interface AP, and establishes an IPC or Ethernet connection between AP and AM.
[0056] Specifically, if the vehicle end and the service end are set in the same electronic control unit, the connection between the first interface and the second interface is established through inter-process communication; if the vehicle end and the service end are set in different electronic control units, the connection between the first interface and the second interface is established through Ethernet communication.
[0057] like Figure 4As shown in the figure, AP connects to AM via IPC or Ethernet. The connection method depends on whether AP and AM are in the same ECU. When the user program needs to access a certain resource or a certain function (i.e., the target resource), it can request the resource from AP, i.e., the permission of the corresponding resourceId. AP needs to search the local cache to check whether the permission information corresponding to resourceId, i.e., the permission information of the target resource, has been cached locally.
[0058] Step S304: if yes, process the target resource based on the permission information of the target resource.
[0059] If the AP has cached the permission information corresponding to the resourceId, the permission information may be read from the cache, and the target resource may be processed based on the permission information.
[0060] Step S306: If not, the first interface sends a permission configuration request for the target resource to the second interface.
[0061] like Figure 4 As shown, if the AP does not cache the permission information corresponding to resourceId or the permission lease has timed out, the AP can query the configuration information corresponding to resourceId from the AM through IPC or network, that is, send a permission configuration request for the target resource.
[0062] Step S308: If the second interface determines that the first interface has the permission of the target resource based on the permission configuration request, a query result including the permission information of the target resource is generated.
[0063] like Figure 4 As shown, AM needs query permission and can query whether AP has permission to the target resource. If yes, AM generates a query result and returns the query result to AP.
[0064] Step S310, the second interface sends the query result to the first interface;
[0065] Specifically, the first interface of this embodiment can cache the permission information of the target resource. Figure 4 As shown, after the AM returns the query result to the AP, the AP can cache the permission corresponding to the resourceId (ie, the permission information of the target resource) to the local memory. Among them, the cache can be performed in a non-file manner, that is, a cache method that does not store data on the disk.
[0066] In addition, the first interface of this embodiment can also perform management operations on the permission information of the target resource. Figure 4 As shown, the AP can manage the local permission cache and perform management operations on the local permission cache, such as whether the lease period of the permission has timed out and synchronization with the AM.
[0067] Step S312: the first interface processes the target resource based on the permission information of the target resource.
[0068] like Figure 4 As shown, after the AP returns the final permission information to the user program, the user program selects to perform different operations according to the permission. In addition, after the target resource is processed, this embodiment can deinitialize the first interface; disconnect the first interface from the second interface. Figure 4 As shown, the user exits the program and performs a deinitialization operation on the AP; the AP actively disconnects from the AM.
[0069] The above method provided by the embodiment of the present invention realizes the distributed permission management of vehicle-mounted software, facilitates the flexible configuration and update of permissions, and is also conducive to the tailoring and expansion of the system. Among them, the AP can cache permissions locally. In scenarios with high real-time requirements or high operation frequency, querying permissions from AM each time will consume a certain amount of time. Through the local caching method, this unnecessary overhead can be effectively avoided. The AP and AM can automatically determine whether they are on the same ECU and select the IPC or Ethernet communication method to reduce the overhead as much as possible.
[0070] Embodiment three:
[0071] Corresponding to the above method embodiment, an embodiment of the present invention provides a permission management device for vehicle autonomous driving, which is applied to a permission management system for vehicle autonomous driving. The permission management system includes a vehicle end and a service end. The vehicle end is provided with a first interface for resource access requests, and the service end is provided with a second interface for access permission management. The first interface is connected to the second interface.
[0072] Based on the above description, see Figure 5 A schematic diagram of a structure of a permission management device for automatic driving of a vehicle is shown, and the permission management device for automatic driving of a vehicle includes:
[0073] The permission information query module 51 is used to determine whether the first interface has the permission information of the target resource cached;
[0074] The permission configuration request module 52 is used for, if not, the first interface to send a permission configuration request for the target resource to the second interface;
[0075] A query result generating module 53, configured to generate a query result including permission information of the target resource if the second interface determines that the first interface has permission to the target resource based on the permission configuration request;
[0076] A query result sending module 54, used for the second interface to send the query result to the first interface;
[0077] The target resource processing module 55 is used for the first interface to process the target resource based on the permission information of the target resource.
[0078] The embodiment of the present invention provides a permission management device and electronic device for automatic driving of a vehicle. If the first interface set at the vehicle end does not cache the permission information of the target resource, the first interface sends a permission configuration request for the target resource to the second interface set at the server end; the second interface determines that the first interface has the permission of the target resource based on the permission configuration request, and generates a query result including the permission information of the target resource; the first interface processes the target resource based on the permission information of the target resource sent by the second interface. This method implements distributed master-slave permission management, and permission requests and permission arbitration are distributed to different processes, with strong scalability and security; this method provides a unified permission management interface, and developers only need to call the unified interface to obtain the result of whether they have the permission to access the response resource; the configuration of permissions in this method can be completely independent of the development of functions, and the permission configuration can be completely formulated by the system level, so that developers can focus more on the development of functions.
[0079] The above device also includes: a first interface initialization module, which is used to initialize the first interface; and establish a connection between the first interface and the second interface.
[0080] The above-mentioned first interface initialization module is used to establish a connection between the first interface and the second interface through inter-process communication if the vehicle end and the service end are set in the same electronic control unit; if the vehicle end and the service end are set in different electronic control units, establish a connection between the first interface and the second interface through Ethernet communication.
[0081] The target resource processing module is further configured to process the target resource based on the permission information of the target resource.
[0082] The above-mentioned device also includes: a permission information caching module, which is used for the first interface to cache the permission information of the target resource.
[0083] The above-mentioned device also includes: a permission information management module, which is used for the first interface to perform management operations on the permission information of the target resource.
[0084] The above device also includes: a first interface deinitialization module, which is used to deinitialize the first interface; and disconnect the first interface from the second interface.
[0085] Technical personnel in the relevant field can clearly understand that, for the convenience and conciseness of description, the specific working process of the vehicle autonomous driving permission management device described above can refer to the corresponding process in the aforementioned embodiment of the vehicle autonomous driving permission management method, and will not be repeated here.
[0086] Embodiment 4:
[0087] The embodiment of the present invention also provides an electronic device for running the above-mentioned vehicle automatic driving authority management method; see Figure 6 A structural schematic diagram of an electronic device is shown, which includes a memory 100 and a processor 101, wherein the memory 100 is used to store one or more computer instructions, and the one or more computer instructions are executed by the processor 101 to implement the above-mentioned vehicle automatic driving permission management method.
[0088] Further, Figure 6 The electronic device shown further includes a bus 102 and a communication interface 103 , and the processor 101 , the communication interface 103 and the memory 100 are connected via the bus 102 .
[0089] The memory 100 may include a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 103 (which may be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. may be used. The bus 102 may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0090] The processor 101 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 101. The above processor 101 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present invention can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module may be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 100, and the processor 101 reads the information in the memory 100 and completes the steps of the method of the above embodiment in combination with its hardware.
[0091] An embodiment of the present invention also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the above-mentioned vehicle automatic driving permission management method. The specific implementation can be found in the method embodiment, which will not be repeated here.
[0092] The computer program product of the vehicle autonomous driving permission management method, device and electronic device provided in the embodiments of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method in the previous method embodiment. The specific implementation can be found in the method embodiment, which will not be repeated here.
[0093] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system and / or device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0094] In addition, in the description of the embodiments of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0095] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program codes.
[0096] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.
[0097] Finally, it should be noted that the above-described embodiments are only specific implementations of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The protection scope of the present invention is not limited thereto. Although the present invention is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed by the present invention, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims
1. A method for managing permissions for vehicle automatic driving, characterized in that: A rights management system applied to vehicle automatic driving, the rights management system includes a vehicle end and a service end, the vehicle end is provided with a first interface for resource access request, the service end is provided with a second interface for access permission management, the first interface is connected with the second interface, the first interface is a resource access request point, the second interface is an access permission manager, the source access request point and the access permission manager select inter-process communication or Ethernet communication by automatically determining whether they are in the same electronic control unit; the method includes: Determining whether the first interface caches permission information of the target resource; If not, the first interface sends a permission configuration request for the target resource to the second interface; If the second interface determines, based on the permission configuration request, that the first interface has permission for the target resource, generating a query result including permission information for the target resource; The second interface sends the query result to the first interface; The first interface processes the target resource based on the permission information of the target resource; The method also includes: initializing the first interface; if the vehicle end and the service end are set in the same electronic control unit, establishing a connection between the first interface and the second interface through inter-process communication; if the vehicle end and the service end are set in different electronic control units, establishing a connection between the first interface and the second interface through Ethernet communication.
2. The method according to claim 1, characterized in that: After the step of determining whether the first interface has cached permission information of the target resource, the method further includes: If yes, the target resource is processed based on the permission information of the target resource.
3. The method according to claim 1, characterized in that After the step of sending the query result by the second interface to the first interface, the method further includes: The first interface caches permission information of the target resource.
4. The method according to claim 3, characterized in that After the step of caching the permission information of the target resource by the first interface, the method further includes: The first interface performs a management operation on the permission information of the target resource.
5. The method according to claim 1, characterized in that After the step of processing the target resource by the first interface based on the permission information of the target resource, the method further includes: Deinitializing the first interface; Disconnect the first interface from the second interface.
6. A vehicle automatic driving authority management device, characterized in that: A rights management system applied to vehicle automatic driving, the rights management system includes a vehicle end and a service end, the vehicle end is provided with a first interface for resource access request, the service end is provided with a second interface for access permission management, the first interface is connected with the second interface, the first interface is a resource access request point, the second interface is an access permission manager, the source access request point and the access permission manager select inter-process communication or Ethernet communication by automatically determining whether they are in the same electronic control unit; the device includes: A permission information query module, used to determine whether the first interface caches the permission information of the target resource; a permission configuration request module, configured to, if no, send the permission configuration request of the target resource by the first interface to the second interface; a query result generating module, configured to generate a query result including permission information of the target resource if the second interface determines, based on the permission configuration request, that the first interface has permission of the target resource; A query result sending module, used for the second interface to send the query result to the first interface; A target resource processing module, used for the first interface to process the target resource based on the permission information of the target resource; The device also includes: a first interface initialization module, used to initialize the first interface; if the vehicle end and the service end are set in the same electronic control unit, a connection between the first interface and the second interface is established through inter-process communication; if the vehicle end and the service end are set in different electronic control units, a connection between the first interface and the second interface is established through Ethernet communication.
7. An electronic device, characterized in that: It includes a processor and a memory, the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the steps of the vehicle automatic driving authority management method as described in any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to implement the steps of the vehicle automatic driving authority management method as described in any one of claims 1 to 5.
