A central interface authority matching method, device, equipment and storage medium

By dynamically generating request identification information and configuration permission model, the problem that static configuration in the Internet of Vehicles platform cannot adapt to dynamic permission changes is solved, and flexible and secure permission matching is achieved, ensuring the integrity and security of permission information.

CN118484786BActive Publication Date: 2024-11-05LINGONG GROUP (JINAN) HEAVY MACHINERY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410939486.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-15
Publication Date
2024-11-05
Estimated Expiration
2044-07-15

AI Technical Summary

Technical Problem

The permission matching method of the existing Internet of Vehicles Platform Central Interface is based on static configuration, which cannot adapt to dynamically changing permission needs, and is poor in security and is vulnerable to attacks.

Method used

By obtaining user permission requests, dynamically generate request identification information, configure permission model, determine permission matching results based on the target permission database, and realize dynamic permission matching, ensuring that only users or devices with corresponding permissions can access specific interfaces or resources.

Benefits of technology

It realizes flexible permission management, enhances security, prevents attackers from obtaining unauthorized access, and ensures the integrity and consistency of permission information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118484786B_ABST
    Figure CN118484786B_ABST
Patent Text Reader

Abstract

The present invention discloses a central interface permission matching method, device, equipment and storage medium. Obtain user permission request, dynamically generate request identification information according to the user permission request; configure permission model, obtain target permission database corresponding to the user permission request according to the permission model; determine permission matching result according to the target permission database and request identification information, wherein the permission matching result includes successful matching and failed matching. Dynamically generate request identification information through intercepted user permission request, the request identification information is composed of the target center identification and target function permission identification of the user request, and obtain the corresponding target permission database according to the request identification information, so as to realize dynamic allocation of permissions, with strong flexibility, and ensure that only users or devices with corresponding permissions can access specific interfaces or resources, thereby ensuring the security and integrity of permission information, and preventing attackers from obtaining unauthorized access rights.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of interface configuration, and in particular to a central interface authority matching method, device, equipment and storage medium. Background Art

[0002] The interface permission matching of the IoV platform center is an important part of the IoV system. In the IoV system, different users or devices may need to access different interfaces or resources, and these interfaces or resources may have different permission requirements. Therefore, a mechanism is needed to ensure that only users or devices with corresponding permissions can access specific interfaces or resources.

[0003] Traditional IoV platform central interface permission matching is usually implemented based on static configuration. This method requires the administrator to manually configure the permission information of each user or device and store it in a database or configuration file. When a user or device requests access to an interface or resource, the system will match it based on its permission information and decide whether to allow access.

[0004] However, the existing technology is not flexible enough through static configuration and cannot adapt to dynamically changing permission requirements. For example, when a user's permissions change, the administrator needs to manually update their permission information, which leads to inconsistent or delayed permissions. In addition, the security is poor and it is vulnerable to attacks. Attackers can obtain unauthorized access rights by guessing or cracking permission information. Summary of the invention

[0005] The present invention provides a center interface authority matching method, device, equipment and storage medium, which dynamically matches user authority in a more flexible and secure manner and finely controls the interface requests of each center.

[0006] According to one aspect of the present invention, a central interface authority matching method is provided, which is applied to a vehicle networking platform. The method includes:

[0007] Obtain user permission requests and dynamically generate request identification information based on the user permission requests;

[0008] Configure the permission model, and obtain the target permission database corresponding to the user's permission request according to the permission model;

[0009] The permission matching result is determined according to the target permission database and the request identification information, wherein the permission matching result includes a matching success and a matching failure.

[0010] Optionally, obtaining a user permission request includes: intercepting requests for each center interface and determining the request interception status of each center interface; when the request interception status indicates that an interception request exists, using the center interface as the target center interface; and using the interception request of the target center interface as a user permission request.

[0011] Optionally, request identification information is dynamically generated based on the user permission request, including: obtaining the target function permission identifier included in the user permission request, and determining the target center interface identifier corresponding to the user permission request; and dynamically splicing the target center interface identifier and the target function permission identifier to generate the request identification information.

[0012] Optionally, a configuration permission model includes: obtaining each center interface identifier, and obtaining each configuration function based on each center interface identifier; generating each function permission identifier according to each configuration function, and concatenating each center interface identifier and the corresponding function permission identifier to generate each identification string; configuring each identification string into a role to generate a configuration permission model.

[0013] Optionally, a target permission database corresponding to the user permission request is obtained according to the permission model, including: filtering each identification string by the target center interface identifier to filter out each target identification string corresponding to the target center interface identifier; and generating a target permission database according to each target identification string.

[0014] Optionally, determining the permission matching result based on the target permission database and the request identification information includes: judging whether the target permission database contains the request identification information, and if so, determining that the permission matching result is a successful match; otherwise, determining that the permission matching result is a failed match.

[0015] Optionally, after determining the permission matching result according to the permission database and the request identification information, the method further includes: when the permission matching result is a successful match, obtaining the permission address corresponding to the target function permission identifier, calling the permission address and feeding back to the user; when the permission matching result is a failed match, generating a prompt message according to the permission matching result, and issuing an alarm in a specified manner according to the prompt message.

[0016] According to another aspect of the present invention, a central interface authority matching device is provided, the device comprising:

[0017] A request identification information generation module is used to obtain a user permission request and dynamically generate request identification information according to the user permission request;

[0018] The target permission database acquisition module is used to configure the permission model and acquire the target permission database according to the permission model;

[0019] The permission matching result determination module is used to determine the permission matching result according to the target permission database and the request identification information, wherein the permission matching result includes a successful match and a failed match.

[0020] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0021] at least one processor; and a memory communicatively coupled to the at least one processor;

[0022] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a central interface authority matching method described in any embodiment of the present invention.

[0023] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a central interface authority matching method described in any embodiment of the present invention when executed.

[0024] The technical solution of the embodiment of the present invention dynamically generates request identification information by intercepting the user's permission request. The request identification information is composed of the target center identification and the target function permission identification requested by the user. By obtaining the corresponding target permission database according to the request identification information, dynamic allocation of permissions is achieved, which has strong flexibility and ensures that only users or devices with corresponding permissions can access specific interfaces or resources, thereby ensuring the security and integrity of permission information and preventing attackers from obtaining unauthorized access rights.

[0025] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] Figure 1 This is a flow chart of a central interface authority matching method provided according to the first embodiment of the present invention;

[0028] Figure 2 is a flowchart of another central interface authority matching method provided according to the second embodiment of the present invention;

[0029] Figure 3 This is a schematic diagram of the structure of a central interface authority matching device provided according to Embodiment 3 of the present invention;

[0030] Figure 4 It is a structural schematic diagram of an electronic device for implementing a central interface authority matching method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only 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 should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] Embodiment 1

[0034] Figure 1 A flowchart of a central interface authority matching method is provided for the first embodiment of the present invention. This embodiment is applicable to the case of multi-central interface authority configuration and matching. The method can be executed by a central interface authority matching device. The central interface authority matching device can be implemented in the form of hardware and / or software. The central interface authority matching device can be configured in a vehicle networking platform. Figure 1 As shown, the method includes:

[0035] S110: Obtain a user authority request, and dynamically generate request identification information according to the user authority request.

[0036] Among them, user permission request refers to the authorization request made by the user to the Internet of Vehicles platform for specific functions, data or operations of a specific center. Request identification information refers to identification information generated according to the user permission request. The Internet of Vehicles platform is a system platform that integrates multiple technologies and functions. It connects vehicles with other related elements (such as vehicles, infrastructure, the Internet, etc.) through the network. In the Internet of Vehicles platform, different centers are divided for different models, such as mining car center, high-speed machine center, etc.

[0037] Optionally, obtaining a user permission request includes: intercepting requests for each center interface and determining the request interception status of each center interface; when the request interception status indicates that an interception request exists, using the center interface as the target center interface; and using the interception request of the target center interface as a user permission request.

[0038] Specifically, the Internet of Vehicles platform will implement request interception on each central interface, that is, monitor and control requests to each central interface during data transmission. The Internet of Vehicles platform will determine the request interception status of each central interface and clarify whether any request has been intercepted. When it is found that the request interception status is an interception request, the central interface corresponding to the intercepted request can be selected as the target central interface, and the interception request for the target central interface can be regarded as a user permission request.

[0039] Optionally, request identification information is dynamically generated based on the user permission request, including: obtaining the target function permission identifier included in the user permission request, and determining the target center interface identifier corresponding to the user permission request; and dynamically splicing the target center interface identifier and the target function permission identifier to generate the request identification information.

[0040] Specifically, the Internet of Vehicles platform will obtain the target function permission identifier contained in the user permission request and determine the target center interface identifier corresponding to the user permission request. Then the obtained target center interface identifier and target function permission identifier are dynamically spliced, that is, flexibly processed and constructed according to the specific situation of the user permission request, so as to finally generate request identification information that can accurately reflect user needs and permission status, so that subsequent processes can perform more accurate and effective operations and processing based on this identification information.

[0041] For example, it can be assembled through dynamic center identifiers and spliced ​​into center + function permission identifiers, such as a complete identifier string of center_functionCode, to match user permissions and finely control the interface requests of each center.

[0042] Furthermore, if the user permission request is more complex, including functional permission requirements at multiple different levels and involving multiple central interfaces, then it is necessary to analyze the association and logical relationship between each functional permission identifier and the corresponding central interface identifier more finely. For example, according to the priority, dependency or specific business logic order of different functional permissions, arrange the order and method of splicing the target central interface identifier and the target functional permission identifier. In actual applications, it may also be necessary to consider real-time changing factors, such as dynamic adjustments or new requirements may occur during the execution of user permission requests. At this time, the Internet of Vehicles platform needs to capture these changes in a timely manner, make corresponding adjustments quickly, and re-plan the generation strategy of request identification information. It is necessary to be able to flexibly select, adjust or add corresponding identification information according to these real-time changes to ensure that the generated request identification information is always consistent with the latest status of the user permission request.

[0043] S120: Configure a permission model, and obtain a target permission database corresponding to the user permission request according to the permission model.

[0044] Among them, the permission model (Role-Based Access Control, RBAC) refers to the role-based access control permission model. RBAC can be used to associate permissions with roles. Roles represent a specific set of permissions. Users are not directly associated with permissions, but are assigned to different roles. The target permission database refers to the database related to the target center corresponding to the user permission request, which is used to compare and match with the user permission request.

[0045] Optionally, a configuration permission model includes: obtaining each center interface identifier, and obtaining each configuration function based on each center interface identifier; generating each function permission identifier according to each configuration function, and concatenating each center interface identifier and the corresponding function permission identifier to generate each identification string; configuring each identification string into a role to generate a configuration permission model.

[0046] Specifically, when performing the configuration permission model operation, the backend of the Internet of Vehicles platform will obtain the identifiers of each central interface. Then, based on the obtained central interface identifiers, the various configuration functions corresponding to each central interface are further obtained. According to the obtained configuration functions, corresponding functional permission identifiers can be generated. Permission identifiers represent different functional permission levels and types. The Internet of Vehicles platform will splice the central interface identifiers and their corresponding functional permission identifiers to generate identification strings with specific meanings, and configure these generated identification strings to the corresponding roles. Through such configuration operations, different roles have specific permission combinations, and finally successfully generate a permission model. The permission model can clearly define and distinguish the scope and degree of permissions that different roles can have in the system, providing a solid foundation and guarantee for the safe operation and permission management of the system.

[0047] Optionally, a target permission database corresponding to the user permission request is obtained according to the permission model, including: filtering each identification string by the target center interface identifier to filter out each target identification string corresponding to the target center interface identifier; and generating a target permission database according to each target identification string.

[0048] Specifically, the Internet of Vehicles platform will filter each identification string through the target center interface identifier to determine each target identification string corresponding to the target center interface identifier. By further integrating and processing the permission information contained in the target identification string, a target permission database for the current user permission request can be formed. The target permission database will centrally reflect all permission information related to the target center interface, including specific functional permissions, operation permissions and other aspects.

[0049] S130. Determine a permission matching result according to the target permission database and the request identification information, wherein the permission matching result includes a matching success and a matching failure.

[0050] The permission matching result refers to the conclusion obtained by comparing the request identification information with the target permission database, indicating whether the request and the permission are consistent.

[0051] Specifically, the Internet of Vehicles platform will compare the target permission database with the generated request identification information to determine the permission matching result. In this process, two situations will be obtained. One is a successful match, that is, the user's permission request matches the permission information in the target permission database; the other is a failed match, indicating that the user's permission request cannot find a corresponding match in the target permission database. By performing permission matching on the intercepted user permission requests, refined management of user permissions can be achieved.

[0052] The technical solution of the embodiment of the present invention dynamically generates request identification information by intercepting the user's permission request. The request identification information is composed of the target center identification and the target function permission identification requested by the user. By obtaining the corresponding target permission database according to the request identification information, dynamic allocation of permissions is achieved, which has strong flexibility and ensures that only users or devices with corresponding permissions can access specific interfaces or resources, thereby ensuring the security and integrity of permission information and preventing attackers from obtaining unauthorized access rights.

[0053] Embodiment 2

[0054] Figure 2 This is a flowchart of a central interface permission matching method provided in the second embodiment of the present invention. This embodiment adds a specific process of determining the permission matching result according to the target permission database and the request identification information on the basis of the above-mentioned first embodiment. Among them, the specific contents of steps S210-S220 are roughly the same as steps S110-S120 in the first embodiment, so they will not be repeated in this embodiment. Figure 2 As shown, the method includes:

[0055] S210: Obtain a user permission request, and dynamically generate request identification information according to the user permission request.

[0056] Optionally, obtaining a user permission request includes: intercepting requests for each center interface and determining the request interception status of each center interface; when the request interception status indicates that an interception request exists, using the center interface as the target center interface; and using the interception request of the target center interface as a user permission request.

[0057] Optionally, request identification information is dynamically generated based on the user permission request, including: obtaining the target function permission identifier included in the user permission request, and determining the target center interface identifier corresponding to the user permission request; and dynamically splicing the target center interface identifier and the target function permission identifier to generate the request identification information.

[0058] S220: Configure a permission model, and obtain a target permission database corresponding to the user permission request according to the permission model.

[0059] Optionally, a configuration permission model includes: obtaining each center interface identifier, and obtaining each configuration function based on each center interface identifier; generating each function permission identifier according to each configuration function, and concatenating each center interface identifier and the corresponding function permission identifier to generate each identification string; configuring each identification string into a role to generate a configuration permission model.

[0060] Optionally, a target permission database corresponding to the user permission request is obtained according to the permission model, including: filtering each identification string by the target center interface identifier to filter out each target identification string corresponding to the target center interface identifier; and generating a target permission database according to each target identification string.

[0061] S230, determine whether the target authority database contains request identification information, if so, execute S240, otherwise, execute S250.

[0062] S240: Determine that the permission matching result is a successful match.

[0063] S250: Determine that the permission matching result is a matching failure.

[0064] Specifically, when making a permission judgment, the Internet of Vehicles platform will compare the received request identification information with the content in the target permission database one by one, that is, to determine whether the content that is completely consistent with the request identification information can be found in the target permission database. If it is found that such request identification information does exist in the target permission database, it can be determined that the permission matching result is a successful match. At this time, it means that the identification information carried by the request is consistent with the permission information pre-set in the database. However, if the content corresponding to the request identification information cannot be found in the entire target permission database, this indicates that the two do not match, and the permission matching result can be determined as a failed match, that is, the operation or behavior represented by the request is not within the scope of the permitted permissions.

[0065] Optionally, after determining the permission matching result according to the permission database and the request identification information, the method further includes: when the permission matching result is a successful match, obtaining the permission address corresponding to the target function permission identifier, calling the permission address and feeding back to the user; when the permission matching result is a failed match, generating a prompt message according to the permission matching result, and issuing an alarm in a specified manner according to the prompt message.

[0066] Specifically, when the permission matching result shows a successful match, the Internet of Vehicles platform will call the corresponding permission function to the target user, that is, obtain the permission address corresponding to the permission identifier of the target function. The permission address includes a path that can implement a specific function or operation. After obtaining the address, the system will call it and feedback to the target user, that is, start the corresponding permission function, so that the user can clearly know that the permission request initiated by him has been approved and executed smoothly. When the permission matching result is a match failure, the Internet of Vehicles platform will generate corresponding prompt information based on this permission matching result, and use a specified method to alarm according to the generated prompt information. For example, a warning box pops up on the interface, a message notification is sent, and a specific sound is emitted, etc., in order to enable managers to promptly detect the failure of permission matching so as to take further measures or make corresponding processing and adjustments.

[0067] The technical solution of the embodiment of the present invention dynamically generates request identification information by intercepting the user's permission request. The request identification information is composed of the target center identification and the target function permission identification requested by the user. By obtaining the corresponding target permission database according to the request identification information, dynamic allocation of permissions is achieved, which has strong flexibility and ensures that only users or devices with corresponding permissions can access specific interfaces or resources, thereby ensuring the security and integrity of permission information and preventing attackers from obtaining unauthorized access rights.

[0068] Embodiment 3

[0069] Figure 3 This is a schematic diagram of the structure of a central interface authority matching device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a request identification information generation module 310, which is used to obtain a user permission request and dynamically generate request identification information according to the user permission request;

[0070] The target authority database acquisition module 320 is used to configure the authority model and acquire the target authority database according to the authority model;

[0071] The permission matching result determination module 330 is used to determine the permission matching result according to the target permission database and the request identification information, wherein the permission matching result includes a successful match and a failed match.

[0072] Optionally, the request identification information generation module 310 specifically includes: a user authority request acquisition unit, used to: intercept requests for each center interface and determine the request interception status of each center interface; when the request interception status is that there is an interception request, use the center interface as the target center interface; use the interception request of the target center interface as a user authority request.

[0073] Optionally, the request identification information generation module 310 specifically includes: a request identification information production unit, used to: obtain the target function authority identifier included in the user authority request, and determine the target center interface identifier corresponding to the user authority request; dynamically splice the target center interface identifier and the target function authority identifier to generate the request identification information.

[0074] Optionally, the target permission database acquisition module 320 specifically includes: a permission model configuration unit, used to: obtain each center interface identifier, and obtain each configuration function based on each center interface identifier; generate each function permission identifier according to each configuration function, and concatenate each center interface identifier and the corresponding function permission identifier to generate each identification string; configure each identification string into a role to generate a configuration permission model.

[0075] Optionally, the target authority database acquisition module 320 specifically includes: a target authority database acquisition unit, used to: filter each identification string by the target center interface identifier to filter out each target identification string corresponding to the target center interface identifier; generate a target authority database according to each target identification string.

[0076] Optionally, the permission matching result determination module 330 is specifically used to: determine whether the target permission database contains the request identification information, and if so, determine that the permission matching result is a successful match; otherwise, determine that the permission matching result is a failed match.

[0077] Optionally, the device also includes: a permission calling and prompting module, which is used to: after determining the permission matching result based on the permission database and the request identification information, when the permission matching result is a successful match, obtain the permission address corresponding to the target function permission identifier, call the permission address and feedback to the user; when the permission matching result is a failed match, generate a prompt message based on the permission matching result, and use a specified method to alarm based on the prompt message.

[0078] The technical solution of the embodiment of the present invention dynamically generates request identification information by intercepting the user's permission request. The request identification information is composed of the target center identification and the target function permission identification requested by the user. By obtaining the corresponding target permission database according to the request identification information, dynamic allocation of permissions is achieved, which has strong flexibility and ensures that only users or devices with corresponding permissions can access specific interfaces or resources, thereby ensuring the security and integrity of permission information and preventing attackers from obtaining unauthorized access rights.

[0079] A central interface authority matching device provided in an embodiment of the present invention can execute a central interface authority matching method provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0080] Embodiment 4

[0081] Figure 4 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0082] like Figure 4As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. The input / output (I / O) interface 15 is also connected to the bus 14.

[0083] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0084] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a central interface authority matching method.

[0085] In some embodiments, a central interface authority matching method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the central interface authority matching method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform a central interface authority matching method in any other appropriate manner (e.g., by means of firmware).

[0086] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0087] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0088] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0089] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0090] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0091] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0092] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0093] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A central interface authority matching method, applied to a vehicle networking platform, characterized in that: include: Obtaining a user permission request, and dynamically generating request identification information according to the user permission request; Configure a permission model, and acquire a target permission database corresponding to the user permission request according to the permission model; Determine a permission matching result according to the target permission database and the request identification information, wherein the permission matching result includes a match success and a match failure; The obtaining of the user permission request includes: Intercept requests from each central interface and determine the request interception status of each central interface; When the request interception situation is that there is an interception request, the central interface is used as the target central interface; Using the interception request of the target center interface as the user authority request; The dynamically generating request identification information according to the user authority request includes: Obtaining the target function permission identifier included in the user permission request, and determining the target center interface identifier corresponding to the user permission request; Dynamically concatenate the target center interface identifier and the target function authority identifier to generate the request identifier information; The configuration permission model includes: Obtaining each center interface identifier, and obtaining each configuration function based on each center interface identifier; Generate each function permission identifier according to each of the configuration functions, and concatenate each of the central interface identifiers and the corresponding function permission identifier to generate each identifier string; Each identification string is configured into a role to generate the configuration permission model, wherein the permission model refers to a role-based access control permission model.

2. The method according to claim 1, characterized in that: The acquiring a target permission database corresponding to the user permission request according to the permission model includes: Filtering each of the identification strings by the target center interface identifier to filter out each target identification string corresponding to the target center interface identifier; The target authority database is generated according to each of the target identification strings.

3. The method according to claim 1, characterized in that The determining the permission matching result according to the target permission database and the request identification information includes: Determine whether the target authority database contains the request identification information, and if so, determine that the authority matching result is a successful match; Otherwise, it is determined that the permission matching result is a matching failure.

4. The method according to claim 1, characterized in that: After determining the authority matching result according to the authority database and the request identification information, the method further includes: When the permission matching result is a successful match, obtaining the permission address corresponding to the target function permission identifier, calling the permission address and feeding back to the user; When the permission matching result is a matching failure, a prompt message is generated according to the permission matching result, and an alarm is issued in a specified manner according to the prompt message.

5. A central interface authority matching device, applied to the method according to any one of claims 1 to 4, characterized in that: include: A request identification information generation module, used to obtain a user permission request and dynamically generate request identification information according to the user permission request; A target permission database acquisition module is used to configure a permission model and acquire a target permission database according to the permission model; A permission matching result determination module, used to determine a permission matching result according to the target permission database and the request identification information, wherein the permission matching result includes a match success and a match failure; The request identification information generation module specifically includes: a user authority request acquisition unit, which is used to: intercept requests from each central interface and determine the request interception status of each central interface; When the request interception situation is that there is an interception request, the central interface is used as the target central interface; Using the interception request of the target center interface as the user authority request; The request identification information generation module specifically includes: a request identification information production unit, which is used to: obtain the target function permission identifier included in the user permission request, and determine the target center interface identifier corresponding to the user permission request; Dynamically concatenate the target center interface identifier and the target function authority identifier to generate the request identifier information; The target authority database acquisition module specifically includes: an authority model configuration unit, which is used to: obtain each center interface identifier, and obtain each configuration function based on each center interface identifier; Generate each function permission identifier according to each of the configuration functions, and concatenate each of the central interface identifiers and the corresponding function permission identifier to generate each identifier string; Each identification string is configured into a role to generate the configuration permission model, wherein the permission model refers to a role-based access control permission model.

6. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 4.

7. A computer storage medium, characterized in that: The computer storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method according to any one of claims 1 to 4 when executed.