Permission combination method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of computers, in particular to a permission combination method and device, electronic equipment and a storage medium, and the method comprises the steps: responding to a permission query operation triggered by a use object on a main control platform, and presenting a permission display interface, the permission display interface comprises joint permissions corresponding to a plurality of joint platforms associated with the main control platform; each joint permission is used for providing a cross-platform service of a joint platform; and in response to a selection operation triggered by the use object for at least one target joint permission in the multiple joint permissions, presenting a binding result of the first identification information of the use object under the main control platform and the at least one target joint permission selected by the use object. Due to the fact that the joint permission can provide numerous cross-platform services for the use object, the service coverage range is wide, and the limitation caused by single service when a platform recommends services can be broken.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly to a method, apparatus, electronic device, and storage medium for combining permissions. Background Technology

[0002] As vehicles increasingly become an important tool for people's travel in modern life, people's travel needs are also becoming more diversified. This has given rise to some platforms that are specifically for vehicles and car owners' travel. These platforms help car owners manage their vehicles and plan their trips by providing various vehicle-related services.

[0003] To further enhance car owner activity and loyalty, platforms typically employ a tiered system, unlocking more privileges and providing additional services to higher-tier car owners, such as vehicle maintenance and chauffeur discounts. However, due to the limited range of services offered by the platform, many services have limited usage scenarios, resulting in low interest among car owners in the limited services recommended by the platform.

[0004] Furthermore, car owners' travel needs are often not highly regular or frequent, and the limited range of services also restricts the platform's ability to recommend services, making it difficult to meet the needs of car owners themselves.

[0005] In conclusion, how to overcome the limitations of platforms in recommendation services is an urgent issue to be addressed. Summary of the Invention

[0006] This application provides a method, apparatus, electronic device, and storage medium for combining permissions, thereby overcoming the limitations of platforms in recommending services.

[0007] On the one hand, a method for joining permissions is provided, including:

[0008] In response to a permission query operation triggered by the user on the main control platform, a permission display interface is presented. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform.

[0009] In response to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, the system presents the user's first identification information under the main control platform and the binding result of the user's selected at least one target joint permission.

[0010] On the one hand, a method for joining permissions is provided, including:

[0011] The system receives a permission query request from a terminal device and sends a permission display interface to the terminal device. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform; the permission query request is sent after the permission query operation is triggered by the object.

[0012] The terminal device receives a binding request for at least one target combined permission; the binding request is sent after the user triggers a selection operation for at least one target combined permission among multiple combined permissions.

[0013] The first identification information of the user under the main control platform is bound to the at least one target joint permission, and the binding result is stored and sent to the terminal device.

[0014] On the one hand, a joint device for authorization is provided, comprising:

[0015] The first presentation unit is used to respond to the permission query operation triggered by the user on the main control platform and present a permission display interface. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform.

[0016] The second presentation unit is used to respond to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, and to present the user's first identification information under the main control platform and the binding result of the user's selected at least one target joint permission.

[0017] Optionally, the device further includes:

[0018] The registration unit is used to present a registration interface in response to the registration operation triggered by the user on the main control platform before the permission display interface is presented in response to the permission query operation triggered by the user on the main control platform.

[0019] In response to the information input operation triggered by the user on the registration interface, the identity information and vehicle information input by the user are presented.

[0020] In response to the user's input completion operation triggered on the registration interface, the user's first identification information under the main control platform is presented.

[0021] Optionally, the second presentation unit is further configured to:

[0022] After the user selects at least one target joint permission among multiple joint permissions in response to the user's selection operation, the user receives and presents the permission level corresponding to each of the at least one target joint permission returned by the backend server. Each permission level is determined by the backend server based on the identity information, after obtaining the first object data of the target joint platform to which the user belongs for each of the at least one target joint permission, and based on at least one of the first object data and the vehicle information, combined with a preset level evaluation rule. Each first object data is the user's service usage under the corresponding target joint platform.

[0023] Optionally, for a permission level corresponding to a target joint permission, if the user does not have corresponding first object data under the target joint platform to which the target joint permission belongs, the permission level corresponding to the target joint permission is determined by the backend server based on the vehicle information and in combination with preset level evaluation rules.

[0024] For a given set of joint permissions, if the user object has corresponding first object data under the target joint platform to which the target joint permission belongs, then the set of joint permissions is determined by the backend server based on the first object data and in conjunction with preset level evaluation rules.

[0025] Optionally, the device further includes:

[0026] The third presentation unit is used to respond to the user's level query operation triggered on the main control platform for a bound target joint permission, and present a corresponding level display interface; the level display interface contains multiple level tasks and the latest permission level corresponding to the target joint permission; each level task is associated with the main control platform, or with the target joint platform to which the target joint permission belongs;

[0027] The latest permission level is determined by the backend server after receiving the level query request sent by the terminal device, based on the completion status of each level task. The completion status is determined based on the second object data of the user on the main control platform and the first object data of the user on the target joint platform that has been re-acquired. The level query request is sent by the user after triggering the level query operation.

[0028] Optionally, the third presentation unit is further configured to:

[0029] After the corresponding level display interface is presented, if the latest permission level meets the preset level requirements, then based on the latest permission level, other joint permissions corresponding to each other joint platform, in addition to the target joint platform to which each of the at least one target joint permission belongs, are presented.

[0030] In response to the user's selection operation triggered by at least one other combined permission, the first identification information of the user under the main control platform is presented, along with the binding result of the user's selection of at least one other combined permission.

[0031] Optionally, the permission display interface may further include:

[0032] The user's basic permissions under the main control platform; the basic permissions are associated with the user's main control platform level under the main control platform.

[0033] On the one hand, a joint device for authorization is provided, comprising:

[0034] The sending unit is used to receive a permission query request sent by a terminal device and send a permission display interface to the terminal device; the permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform; the permission query request is sent after the permission query operation is triggered by the object.

[0035] A receiving unit is configured to receive a binding request sent by the terminal device for at least one target combined permission; the binding request is sent after the user triggers a selection operation for at least one target combined permission among multiple combined permissions;

[0036] The binding unit is used to bind the first identification information of the user object under the main control platform with the at least one target joint permission, and send the binding result to the terminal device after storing it.

[0037] Optionally, the device further includes:

[0038] The registration unit is used to receive a registration request sent by the terminal device before receiving the permission query request, and to send a registration interface to the terminal device; the registration request is sent after the registration operation is triggered by the object.

[0039] Receive identity information and vehicle information sent by the terminal device, and create corresponding first identification information for the user on the main control platform;

[0040] The first identification information is bound and stored together with the identity information and the vehicle information, and the first identification information is sent to the terminal device.

[0041] Optionally, the device further includes:

[0042] The acquisition unit is configured to, after receiving the binding request sent by the terminal device for at least one target joint permission, acquire, based on the identity information, the first object data of the user object to which each of the at least one target joint permission belongs; each first object data represents the service usage of the user object under the corresponding target joint platform;

[0043] Based on at least one of the first object data and the vehicle information, and in conjunction with preset level evaluation rules, the permission level corresponding to each of the at least one target joint permission is determined respectively.

[0044] The permission level corresponding to each of the at least one target combined permission is sent to the terminal device.

[0045] Optionally, the acquisition unit is specifically used for:

[0046] For a given set of joint permissions, if the user does not have corresponding first object data under the target joint platform to which the target joint permission belongs, the permission level corresponding to the target joint permission is determined based on the vehicle information and in conjunction with the preset level evaluation rules.

[0047] If the user object has corresponding first object data under the target joint platform to which the target joint permission belongs, then based on the first object data and combined with the preset level evaluation rules, the permission level corresponding to the target joint permission is determined.

[0048] Optionally, the acquisition unit is further configured to:

[0049] After determining the permission level corresponding to the target joint permission based on the vehicle information and in conjunction with the preset level evaluation rules, the permission level and the identity information are sent to the joint server of the target joint platform via the joint interface. The joint interface is used to: convert the data format of the permission level and the identity information based on preset requirements; the permission level is used to: enable the joint server to determine that the user is granted the target joint permission corresponding to the permission level.

[0050] Based on the federation interface, the second identification information created for the user on the target federation platform based on the identity information sent by the federation server is obtained, and the second identification information is associated with and stored with the first identification information.

[0051] Optionally, the device further includes:

[0052] The determining unit is configured to receive a level query request sent by the terminal device for a target combined permission that has been bound; the level query request is sent after the user triggers a level query operation;

[0053] Obtain the second object data of the user on the main control platform, and based on the federation interface, re-obtain the first object data of the user under the target federation platform in the federation server corresponding to the target federation platform to which the target federation permission belongs;

[0054] Based on the second object data and the reacquired first object data, the completion status of each level of task is determined, and each level of task is associated with the main control platform or the target joint platform.

[0055] Based on the completion status, determine the latest permission level corresponding to the target joint permission, and send the tasks of each level and the latest permission level to the terminal device.

[0056] Optionally, the determining unit is further configured to:

[0057] After sending the tasks of each level and the latest permission level to the terminal device, if the latest permission level meets the preset level requirements, then based on the latest permission level, determine the other joint permissions corresponding to each of the other joint platforms, in addition to the target joint platforms to which each of the at least one target joint permission belongs, and send each of the other joint permissions to the terminal device.

[0058] The terminal device receives a binding request for at least one other combined permission; the binding request is sent after the user triggers a selection operation.

[0059] The first identification information of the user under the main control platform is bound with at least one other joint permission, and the binding result is stored and sent to the terminal device.

[0060] An electronic device provided in this application includes a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of any of the above-described methods for combining permissions.

[0061] This application provides a computer-readable storage medium including a computer program that, when run on an electronic device, causes the electronic device to perform the steps of any of the above-described combined methods of permissions.

[0062] This application provides a computer program product, which includes a computer program stored in a computer-readable storage medium. When a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, causing the electronic device to perform the steps of any of the above-described methods for combining permissions.

[0063] The beneficial effects of this application are as follows:

[0064] This application provides a method, apparatus, electronic device, and storage medium for combining permissions. After the user triggers a permission query operation on the main control platform, the terminal device can present a permission display interface containing multiple combined permissions for the user to select. The user does not need to switch platforms and can directly select the required combined permissions and activate and bind them on the main control platform. This permission combination method greatly simplifies the user's operation process, realizes "one card for all cards", and improves the user's experience.

[0065] After the user selects the target joint permissions, the terminal device presents the binding result between the target joint permissions and the user's first identification information under the main control platform. After that, the user can enjoy the cross-platform services brought by the joint permissions of the joint platform. The joint platform can be a platform related to various fields, such as a travel platform, an air travel platform, a car wash and maintenance platform, a navigation platform, etc. The corresponding joint permissions can bring richer services to the user and meet the user's needs. This can break the limitations of existing technologies where platforms recommend services due to the single service.

[0066] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0067] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0068] Figures 1A-1CA schematic diagram illustrating the standardized service content provided by different vehicle management platforms in a related art, as provided in an embodiment of this application;

[0069] Figure 2 A schematic diagram illustrating an application scenario of a permission union method provided in this application embodiment;

[0070] Figure 3 A flowchart illustrating an overall method for combining permissions provided in an embodiment of this application;

[0071] Figure 4 A schematic diagram of the interface of a main control platform provided in an embodiment of this application;

[0072] Figure 5 A schematic diagram of a registration interface provided in an embodiment of this application;

[0073] Figure 6 This is a schematic diagram illustrating the presentation of identity information provided in an embodiment of this application;

[0074] Figure 7 This application provides a schematic diagram of vehicle information filling.

[0075] Figure 8A This is a schematic diagram illustrating a prompt for adding vehicle information, provided in an embodiment of this application.

[0076] Figure 8B This is an illustration of another prompt for adding vehicle information provided in an embodiment of this application;

[0077] Figure 9 This is a schematic diagram illustrating the presentation of vehicle information provided in an embodiment of this application;

[0078] Figure 10 An entry diagram of a permission display interface provided in an embodiment of this application;

[0079] Figure 11 A schematic diagram of a permission display interface provided in an embodiment of this application;

[0080] Figure 12 A schematic diagram illustrating a basic permission provided for an embodiment of this application;

[0081] Figure 13 This is another schematic diagram of vehicle information filling provided in this application embodiment;

[0082] Figure 14 A schematic diagram illustrating the activation of a joint permission as provided in an embodiment of this application;

[0083] Figure 15 A schematic diagram illustrating a joint permission provided for an embodiment of this application;

[0084] Figure 16 This is a schematic diagram illustrating the interaction between the terminal device, the backend server, and the federated server during the activation process of a federated permission, as provided in an embodiment of this application.

[0085] Figure 17 A flowchart illustrating another method for combining permissions provided in this application embodiment;

[0086] Figure 18 A schematic diagram of a system architecture provided for an embodiment of this application;

[0087] Figure 19 An interaction timing diagram of a terminal device, a backend server, and a federated server provided for an embodiment of this application;

[0088] Figure 20 A schematic diagram illustrating the composition of a permission-based joint device provided in this application embodiment;

[0089] Figure 21 A schematic diagram of the composition structure of the joint device for the second type of authority provided in the embodiments of this application;

[0090] Figure 22 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0091] Figure 23 A schematic diagram of the hardware structure of another electronic device provided in the embodiments of this application. Detailed Implementation

[0092] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this application. Obviously, the described embodiments are only some embodiments of the technical solutions of this application, and not all embodiments. Based on the embodiments recorded in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the technical solutions of this application.

[0093] The following describes some of the concepts involved in the embodiments of this application.

[0094] Joint platform: A platform that has a joint relationship with the main control platform can provide various services owned by itself to the users of the main control platform based on the permission level.

[0095] Joint permissions: Permissions provided by the joint platform. Joint permissions can directly provide cross-platform services to users with joint permissions on the main control platform.

[0096] Object data: Information on how the object is used in services on the corresponding platform.

[0097] The design concept of the embodiments of this application is briefly introduced below:

[0098] like Figure 1A , Figure 1B , Figure 1C The diagram illustrates the limited range of services offered by different vehicle management platforms in this application, as provided in an embodiment of the present application. Currently, numerous vehicle management platforms exist, and the services they offer are largely the same, with no significant differences. Most are limited to services such as refueling, chauffeur services, vehicle relocation, car washing, car insurance, car rental, used cars, and annual vehicle inspections. The services offered by these platforms are relatively limited, and many services have limited usage scenarios and extremely long demand cycles. For example, the demand cycle for car insurance is measured in years, leading to low interest among car owners in the services recommended by the platforms. Furthermore, car owners' travel needs are often not highly regular or frequent, and the limited service offerings also significantly restrict the platforms' service recommendations, leaving car owners' needs unmet.

[0099] Based on this, embodiments of this application provide a method, apparatus, electronic device, and storage medium for permission aggregation. Users can trigger a permission query operation on the main control platform. Afterwards, the terminal device presents a permission display interface containing multiple aggregated permissions for the user to select. Once selected, the binding result between the aggregated permissions and the user's first identifier information on the main control platform is displayed. Thus, users do not need to switch back and forth between the main control platform and various aggregated platforms to enjoy services from different platforms. Instead, they can directly enjoy cross-platform services provided by the aggregated permissions of the aggregated platforms on the main control platform, greatly simplifying the user's operation and improving the user experience. Furthermore, the aggregated platforms cover a wide range of fields, including travel, air travel, navigation, and other aspects, offering extremely rich services that better attract users and meet their needs, further overcoming the limitations of platforms recommending services due to their limited availability.

[0100] Furthermore, the method proposed in this application focuses on services with high demand, such as parking services. Users with high demand are more likely to pay attention to the service content, which can increase user activity.

[0101] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0102] like Figure 2The diagram shown is an application scenario illustration of an embodiment of this application. The application scenario diagram includes a terminal device 210 and two servers 220, wherein server 221 is the backend server of the main control platform, and server 222 is the joint server of the joint platform.

[0103] In this embodiment, terminal device 210 includes, but is not limited to, mobile phones, tablets, laptops, desktop computers, e-book readers, smart voice interaction devices, smart home appliances, and in-vehicle terminals. The terminal device may have a client installed related to the main control platform (which is related to vehicle management services). This client can be software (e.g., a browser, vehicle service software), a webpage, or a mini-program. Server 221 is the backend server corresponding to the software, webpage, or mini-program, or a server specifically used for vehicle management; this application does not impose specific limitations. Server 222 is a joint server related to the joint platform. The joint platform is not limited to vehicle management but can involve various fields such as travel, air travel, and car washing and maintenance. Server 220 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0104] It should be noted that the permission combination method in the various embodiments of this application can be jointly executed by the terminal device 210 and the backend server 221. For example, in response to a permission query operation triggered by the user on the main control platform, the terminal device 210 sends a permission query request to the backend server 221. After receiving the permission query request, the backend server 221 returns a permission display interface to the terminal device 210; the terminal device 210 presents a permission display interface containing multiple combined permissions.

[0105] After the user triggers a selection operation for one or more target combined permissions, the terminal device 210 responds to the selection operation by sending a binding request to the server 221. After receiving the binding request, the server 221 binds the user's first identification information under the main control platform with the target combined permissions and returns the binding result to the terminal device 210, which then presents the binding result.

[0106] In one alternative implementation, the terminal device 210 and the server 220 can communicate via a communication network.

[0107] In one alternative implementation, the communication network is a wired network or a wireless network.

[0108] It should be noted that, Figure 2 The examples shown are merely illustrative; in reality, the number of terminal devices and servers is unlimited and is not specifically limited in the embodiments of this application.

[0109] The following describes the method for combining permissions provided by exemplary embodiments of this application in conjunction with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0110] See Figure 3 The diagram shown is a flowchart of an implementation method for a permission union provided in this application. The specific implementation process of this method is as follows:

[0111] S301: The terminal device responds to the permission query operation triggered by the user on the main control platform and presents the permission display interface.

[0112] The permission display interface mentioned above includes: the joint permissions corresponding to each of the multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service for a joint platform.

[0113] This application is mainly aimed at scenarios related to vehicle management platforms. The users in this application can be vehicle owners, drivers, etc. For ease of description, this application will mainly use vehicle owners as an example for further explanation.

[0114] Currently, various vehicle management platforms are emerging one after another. The main function of each platform is to provide users with various vehicle-related services, such as ETC application, car insurance application, vehicle inspection, car rental, and chauffeur services. However, the content of these services is relatively simple, and users often do not frequently need these services. As a result, the platform cannot attract car owners when recommending services, and the needs of car owners themselves cannot be met.

[0115] Based on this, this application proposes a method for granting permissions and a vehicle management platform, namely a master control platform. By combining the master control platform with the joint platform, cross-platform services are provided to users to enrich the service content. The cross-platform services can cover various aspects such as air travel, travel accommodation, and vehicle maintenance.

[0116] Furthermore, considering convenience, in this application, users do not need to switch back and forth between the main control platform and various joint platforms to enjoy the services of different platforms. Instead, they only need to obtain joint permissions for the joint platforms on the main control platform. After obtaining joint permissions, they can directly use the cross-platform services of various joint platforms. The richness of services can better attract users and also break through the limitations of existing vehicle management platforms in recommending services due to the single service, thereby improving user satisfaction.

[0117] Meanwhile, this application considers that most of the services provided in related technologies are services with low demand frequency and long demand cycles. For example, the demand cycle for ETC application, vehicle inspection, and vehicle insurance is basically on the order of years. Users usually only pay special attention to these services when they have a need. At other times, these services are difficult to attract the attention of users. Therefore, this application proposes to provide users with more high-frequency demand services, such as services related to parking, car washing, and refueling, so as to better improve user satisfaction.

[0118] Before performing a permission query operation, the user can first register on the main control platform to create a corresponding primary identifier for the user on the main control platform. Subsequently, permissions can be granted to the user by binding permissions with the primary identifier, and the user with the permissions can enjoy the corresponding services.

[0119] In one optional implementation, the terminal device displays a registration interface in response to a registration operation triggered by the user on the main control platform; displays the user's entered identity information and vehicle information in response to an information input operation triggered by the user on the registration interface; and displays the user's first identification information on the main control platform in response to an input completion operation triggered by the user on the registration interface.

[0120] like Figure 4 The diagram shown is an interface diagram of a main control platform provided in an embodiment of this application. The interface includes a vehicle owner registration entry. Users can trigger the registration operation by clicking the vehicle owner registration entry. Afterwards, the terminal device will generate a registration request and send the registration request to the backend server of the main control platform. After receiving the registration request sent by the terminal device, the backend server sends the registration interface to the terminal device, and the terminal device displays the registration interface to the user.

[0121] like Figure 5 The diagram shown is a registration interface provided in an embodiment of this application. Users can fill in relevant identity information on the registration interface, such as nickname, gender, age, mobile phone number, email address, etc. The mobile phone number is a required field. The terminal device displays the identity information entered by the user, such as... Figure 5In the process, the terminal device displays the nickname, mobile phone number, and email address filled in by the user.

[0122] After the user completes the form, they can submit the information to complete the input and upload their identity information. The terminal device will then send the identity information to the backend server. After receiving the identity information from the terminal device, the backend server will create the corresponding first identification information for the user on the main control platform, bind and store the first identification information with the identity information, and then return the first identification information to the terminal device. The terminal device will then present the first identification information to the user and prompt the user that the registration is complete.

[0123] After registration, certain identity information of the user can be displayed on a certain interface of the main control platform, such as... Figure 6 The diagram shown is a schematic representation of identity information provided in an embodiment of this application. In the object interface of the main control platform, the original vehicle owner registration entrance is replaced by an identity information display card. The display card displays the nickname of the user and may also include a brief display of the services already obtained by the user. The specific details of service and permission acquisition will be explained in detail later and will not be repeated here.

[0124] It should be noted that the use of the aforementioned identity-related data requires the user's knowledge and, more importantly, the user's active authorization.

[0125] In addition to identity information, the system can also prompt the user to add vehicle information during the registration process (such as when the user fills in their identity information), similar to the process for adding identity information. Figure 7 The diagram shown illustrates a vehicle information entry method provided in this application embodiment. Users can click the "Add Vehicle Information" button on the registration interface to enter the vehicle information entry interface. After entering the license plate number, clicking "Next" will display an interface with more fillable options. Users can then enter more detailed vehicle information, such as vehicle model, vehicle identification number (VIN), engine number, and registration date. The vehicle model, VIN, and engine number are mandatory fields. This vehicle information can be entered manually or automatically by uploading an image of the vehicle registration certificate in the "Please Add Vehicle Certificate" section.

[0126] The terminal device displays the vehicle information entered by the user in the interface. After the user completes the input (such as clicking the "complete" button), the vehicle information is sent to the backend server. The backend server can bind and store the first identification information with the vehicle information and send a notification of successful binding to the terminal device. The terminal device can display a prompt that the vehicle information has been successfully added.

[0127] If the user fills in vehicle information by uploading an image of the vehicle registration certificate, the front end of the main control platform needs to select an image of the vehicle registration certificate from the local album or take a picture of the vehicle registration certificate through the image selection interface.

[0128] It should be noted that the process of acquiring the vehicle registration certificate image is essentially an operation performed by the terminal device, only the application is different; after the image is acquired, the operations on the terminal device side are all initiated by the front end of the main control platform through the terminal device. Therefore, for the sake of convenience, the term "terminal device" will be used instead of "front end of the main control platform" in the following description.

[0129] After obtaining the vehicle registration certificate image, the terminal device transmits the image to the main control platform's backend server via the corresponding transmission interface, encrypted using HyperText Transfer Protocol Secure (HTTPS). Upon receiving the image, the backend server can use an image recognition interface to call a third-party Optical Character Recognition (OCR) service to recognize the image. It then receives the recognition results, extracts key fields such as the vehicle identification number (VIN), engine number, owner's name, vehicle type, registration date, and license plate number, and compares the extracted information with the vehicle information entered by the user. For example, if the user previously entered a license plate number, the previously entered number can be compared with the license plate number recognized from the image. For vehicle information that the user has not manually entered, a vehicle information verification interface can be used to call a third-party vehicle information database, sending the vehicle information to be compared to the database to verify for any anomalies.

[0130] If the verification is successful, the backend server can update the vehicle information status to "verified", store the vehicle information in the vehicle information table, and bind it with the first identification information of the user under the main control platform.

[0131] If verification fails, the backend server returns an error message to the terminal device, prompting the user to re-upload a clear image or contact customer service for manual review. For verification failures caused by network anomalies or failed API calls, a retry mechanism or downgraded processing can be used.

[0132] During image recognition, the vehicle registration certificate image and vehicle information uploaded by the user can be encrypted and stored to prevent unauthorized access. Specifically, the vehicle registration certificate image can be encrypted and saved to a file storage system, and a unique file path can be generated and recorded in the database. Furthermore, it is necessary to ensure the security of data transmission.

[0133] For example, vehicle information can also be added after registration is complete, such as... Figure 8A The diagram illustrates a prompt for adding vehicle information according to an embodiment of this application. On the same interface that prompts the user to complete registration, the user is prompted to add vehicle information. Alternatively, an entry point for adding vehicle information may be presented on a specific interface of the main control platform. Figure 8B As shown, this is another schematic diagram illustrating the prompt for adding vehicle information provided in an embodiment of this application. In the object interface of the main control platform, in addition to the identity information display card, in Figure 8B (a) also displays a prompt card for adding vehicle information. Users can add vehicle information by clicking the card, or by clicking the vehicle registration certificate or driver's license icon in the card.

[0134] After the vehicle information is successfully added, it can be displayed on a certain interface of the main control platform, such as... Figure 9 The diagram shown is a schematic representation of vehicle information provided in an embodiment of this application. Vehicle information added by an object is presented in the form of a card at the original entry point for adding vehicle information. Figure 9 In (b), the card briefly presents some information about the vehicle, such as the vehicle name and license plate number. Users can click on the card to enter the vehicle information page and add, modify, or view the vehicle information.

[0135] It should be noted that the above methods, such as using objects to trigger various operations (e.g., clicking), the specific content of identity information and vehicle information, and the location and specific form of interactive buttons, registration entry points, and information addition entry points on the interface, are all illustrative examples and are not specifically limited in this application.

[0136] Afterwards, the user can trigger a permission query operation on the main control platform to enter the permission display interface. For example, after the user triggers the permission query operation, the terminal device generates a permission query request and sends it to the backend server. After receiving the permission query request from the terminal device, the backend server sends the permission display interface to the terminal device.

[0137] For example, such as Figure 10 The diagram shown is an entry point diagram of a permission display interface provided in an embodiment of this application. The entry point of the permission display interface is set in the identity information display card, specifically as follows: Figure 10 As shown in (c), users can access the permission display interface by clicking the "More Permissions" button. However, this is just an example, and the main control platform can set the specific method of accessing the permission display interface according to actual needs. This application does not impose any specific restrictions.

[0138] like Figure 11 The diagram shown is a schematic of a permission display interface provided in an embodiment of this application. The permission display interface includes joint permissions that the user can activate and that are associated with multiple joint platforms, such as joint permission 1 of joint platform 1, joint permission 2 of joint platform 2, and joint permission 3 of joint platform 3. Each joint permission can directly provide the user with the corresponding cross-platform service of the joint platform. That is, if the car owner has a certain permission, he / she can enjoy the service content corresponding to that permission.

[0139] In addition, the permission display interface can also include the basic permissions of the user under the main control platform; such as Figure 12 The diagram shown is a schematic of basic permissions provided in an embodiment of this application. The basic permissions include various services related to high-frequency needs, such as parking service, refueling service, chauffeur service, and roadside assistance service. Among them, parking service, chauffeur service, and roadside assistance service are activated and can be viewed by clicking the view button. Refueling service can be activated but has not yet been activated and can be activated by clicking the activation button.

[0140] Terminal devices can also directly jump to the permission display interface after the user successfully registers for the first time or after adding vehicle information for the first time, presenting the existing services and the services that can be activated to the user. This application does not make specific limitations.

[0141] The specific content of the above services can be set based on the actual situation. For example, it can provide parking location recommendations and parking discounts. This application does not impose any specific limitations.

[0142] Basic permissions can be directly issued to the account corresponding to the object after registration, or they can be set to require activation by the object and issued after activation. Alternatively, some basic permissions can be issued directly after registration, while others require activation by the object.

[0143] Basic permissions can be associated with the user's control platform level. For example, the higher the user's control platform level, the more services the basic permissions can provide; or, basic permissions can be granted to the user after the user's control platform level meets certain conditions. The control platform level can be divided in a tiered manner, such as into Level 1, Level 2, Level 3, etc., or it can be divided according to identity type, such as into ordinary level and member level. This application does not specify any particular limitation.

[0144] If the levels are divided according to identity type, car owners who have added some or all vehicle information can be classified as members, while car owners who have not added vehicle information can be classified as ordinary. Basic permissions are granted to members, and if members add all vehicle information, they are given the option to activate joint permissions to encourage all car owners to add vehicle information.

[0145] like Figure 13 The diagram shown illustrates another vehicle information filling method provided in this application embodiment. After entering the vehicle information addition interface, the user is prompted that they can upgrade to a membership level and obtain corresponding basic permissions by adding vehicle information. Furthermore, the service content corresponding to the basic permissions can be displayed, that is, the services that can be provided, such as parking services, refueling services, and chauffeur services. The user can choose to enter the license plate number, which can be completed manually or by taking a picture or uploading an image of the vehicle registration certificate from the local computer to automatically recognize the license plate number.

[0146] After the user completes the input, they click the "Complete" button. The vehicle information is then sent to the backend server. The backend server binds and stores the vehicle information with the user's primary identification information and grants the user's account the corresponding basic permissions. At the same time, it sends a notification to the terminal device that the vehicle information has been successfully added and the basic permissions have been successfully obtained. The terminal device then displays a new interface with messages indicating that the vehicle information has been successfully added, the membership level has been upgraded, and the basic permissions have been obtained.

[0147] Furthermore, the interface can also provide further prompts for users to add more vehicle information, and after adding it, they can obtain more services, such as cross-platform services provided by joint permissions, and expanded service content corresponding to basic permissions (i.e., ETC query and roadside assistance in the figure); users can choose to upload images or fill in manually, or choose not to fill in for the time being.

[0148] If you choose to continue adding vehicle information, the vehicle information entry interface will appear as follows: Figure 7 As shown in the lower right image, after filling in the object, you can also... Figure 7 As shown in the lower left image, it indicates that the vehicle information has been successfully added. Further indications may include successful service acquisition, or it may directly redirect to... Figure 12 The permission display interface shown displays the services that have been acquired (i.e. activated) under the basic permissions, the services that can be activated, and the combined permissions that can be acquired.

[0149] In the above scenario, if membership levels require not only vehicle information but also electronic resource exchange (EREE), the user enters the license plate number on the vehicle information addition interface and clicks the "Complete" button. The terminal device then sends an EREE request to the backend server. This request includes the user's primary identifier and login validity period on the main control platform. Upon receiving the request, the backend server creates an EREE form, sets the exchange quantity, and then calls the EREE interface to connect to the EREE platform. It sends the EREE form's identifier, the exchange quantity, a description of the exchange, and a callback address. The EREE platform returns a timestamp, signature algorithm type, and a random string to the backend server to ensure request uniqueness. The backend server then returns these parameters to the terminal device, which calls the relevant interfaces to execute the EREE based on these parameters.

[0150] If the exchange is successful, the electronic resource exchange platform will call the notification interface of the electronic resource exchange result via a callback address using the POST method to send a notification of successful exchange to the backend server. The backend server can verify the signature of the notification content to confirm the authenticity of the electronic resource exchange result. After that, the electronic resource exchange status will be updated to "completed", and the ordinary level of the user will be changed to the member level, and the corresponding basic permissions will be issued. If the level has an expiration date, the expiration date will also need to be recorded.

[0151] If the exchange fails, the terminal device will receive the corresponding error code and information, indicating the reason for the failure of the electronic resource exchange.

[0152] Throughout the exchange process, HTTPS can be used to ensure the security of data transmission; the quantity of electronic resources exchanged and the information of both parties can be verified in real time to prevent parameters from being changed, and certain important information can be signed and encrypted.

[0153] During the exchange process, information related to resource exchange, such as the electronic resource exchange form's identifier, primary identifier information, the quantity of electronic resources exchanged, the exchange status, and the exchange time, can be stored in the corresponding electronic resource exchange form table; information related to changes in the user's level, such as primary identifier information, membership level, and the start and end dates of the validity period, can be stored in the corresponding level table.

[0154] S302: In response to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, the terminal device presents the user's first identification information under the main control platform and the binding result of the user's selected at least one target joint permission.

[0155] After the user triggers the selection operation, the terminal device sends a binding request to the backend server for at least one target combined permission selected by the user. After receiving the binding request, the backend server binds the first identification information of the user under the main control platform with at least one target combined permission selected by the user, and sends the binding result to the terminal device after storing it.

[0156] As mentioned above, the joint platform is not limited to vehicle management and can cover various fields, such as travel and air travel. Therefore, the combination of multiple joint permissions can provide users with richer and broader service content without being limited by a single scenario, which is more attractive to car owners.

[0157] like Figure 14 The diagram shown is an activation illustration of a joint permission provided in an embodiment of this application. When the user selects to activate joint permission 1 of joint platform 1, joint permission 1 is the target joint permission. The terminal device displays a card indicating that joint permission 1 has been activated in the account, indicating that joint permission 1 has been bound to the user's first identification information under the main control platform, joint permission 1 has been issued, and the user can use cross-platform services related to joint permission 1.

[0158] For example, the number of joint permissions that a user can have can be limited, for example, it can only have joint permissions for one joint platform; and the upper limit of the number of joint permissions can be set based on the user's master platform level, which is not specifically limited in this application.

[0159] Each joint platform has its own corresponding joint permissions with its own permission level. This application can evaluate the permission level of each target joint permission after the user selects the target joint permission to determine the permission level that the user can have. In addition, after the user registers and adds vehicle information, it can directly evaluate the permission level of each joint permission that the user can select. When the user enters the permission display interface and selects the target joint permission for activation and binding, the evaluated permission levels of each joint permission can be directly displayed to facilitate the user's selection.

[0160] like Figure 15 The diagram shown is a schematic representation of a set of permissions provided in an embodiment of this application. Before the user selects the target set of permissions, the backend server evaluates the permission level of each set of permissions. The evaluated permission level is displayed on the card corresponding to each set of permissions. Among them, the permission level corresponding to set of permissions 1 is permission level 3, the permission level corresponding to set of permissions 2 is permission level 2, and the permission level corresponding to set of permissions 3 is permission level 4.

[0161] For ease of description, the following example will be used to further illustrate the process of evaluating the permission level after the user selects the target's combined permissions.

[0162] The permission level assessment is based on the user's identity information and vehicle level. For example, after the backend server receives the binding request, it can obtain the first object data of the user on the target joint platform to which each of the at least one target joint permission belongs, based on the identity information. Based on the first object data and at least one of the vehicle information, combined with the preset level assessment rules, the permission level corresponding to each of the at least one target joint permission is determined. Finally, the permission level corresponding to each of the at least one target joint permission is sent to the terminal device. The terminal device receives and presents the permission level corresponding to each of the at least one target joint permission returned by the backend server.

[0163] Each set of first object data represents the user's service usage on the corresponding target joint platform. For example, if a user chooses to activate joint permission 1 on joint platform 1 and joint permission 2 on joint platform 2, then joint platform 1 and joint platform 2 are both target joint platforms. The backend server can obtain the user's first object data on target joint platform 1 and target joint platform 2 based on the user's identity information, such as a mobile phone number. The first object data can include the user's service usage on the corresponding target joint platform. For example, if target joint platform 1 is a tourism-related platform, then the user's first object data on target joint platform 1 can include registration data, travel-related records, etc.; if target joint platform 2 is an air travel-related platform, then the user's first object data on target joint platform 2 can include registration data, air travel-related records, etc.

[0164] It is understood that in the specific implementation of this application, if data related to identity information and first object data is involved, and when this application applies the above data to specific products or technologies, it is necessary to obtain the permission or consent of the user, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0165] Furthermore, taking a target federation platform as an example, if a user has never used a certain target federation platform, there may be a situation where the user's first object data does not exist under that target federation platform. In this case, the backend server can determine the permission level of the target federation permissions corresponding to that target federation platform based solely on vehicle information and in conjunction with preset level assessment rules. The level assessment rules can be set according to specific needs. For example, in a rule that assesses based solely on vehicle information, the permission level can be assessed based on information such as vehicle age (years from the vehicle's registration date to the current date) and vehicle type.

[0166] In addition, if the user does not have first object data under the target joint platform, the user's second object data under the main control platform can be used in combination with vehicle data to assess the permission level. For example, the permission level can be assessed based on the vehicle's usage time and the user's accumulated electronic resource exchange information under the main control platform (such as vehicle owner activity, number of exchanges, exchange frequency, and total number of electronic resources exchanged).

[0167] This application allows the deployment of a rule engine (such as Drools, EasyRules, etc.) on a backend server. The vehicle information and other data required for the assessment are input into the rule engine, which then executes the level assessment rules to evaluate the permission level and obtain the permission level corresponding to the target joint permission. The level assessment rules can be stored in a configuration file or database for easy adjustment and maintenance. The rules can be adjusted through the management backend.

[0168] After determining the permission level, the server can send the permission level and identity information to the corresponding target federation platform's federation server based on the federation interface; then, based on the federation interface, it can obtain the second identification information sent by the federation server, which is created for the user on the target federation platform based on the identity information, and store the second identification information in association with the first identification information.

[0169] In other words, if the user does not have any first object data under a certain target federation platform, then the user needs to be registered under the target federation platform first, so as to create a second identification information for the user on the target federation platform; by binding the first identification information and the second identification information, the accounts registered by the user under the two platforms can be associated, so as to realize the message exchange between different platform accounts of the same user under different platforms (master platform and target federation platform) in the future.

[0170] As mentioned above, since different platforms have differences in data specifications, the two parties need to use a joint interface to convert the data format of the data transmitted by one party (such as permission level and identity information) based on preset requirements so that the data format conforms to the specifications of the other party.

[0171] The federated server can also grant appropriate target federated permissions to users based on their permission levels.

[0172] If the object being used has first object data under a certain target federation platform, the backend server can determine the permission level of the target federation permission corresponding to the target federation platform based solely on the first object data and in combination with preset level evaluation rules. Alternatively, it can determine the permission level of the target federation permission corresponding to the target federation platform by combining vehicle information with the first object data and preset level evaluation rules. Or, it can determine the permission level of the target federation permission corresponding to the target federation platform based on the first object data and the second object data in combination with preset level evaluation rules. This application does not make any specific limitations.

[0173] For example, let's take the target federation permissions of a target federation platform as an example, such as... Figure 16 The diagram illustrates the interaction between the terminal device, the backend server, and the joint server during the activation process of joint permissions according to an embodiment of this application. After the user triggers the operation to enter the permission display interface, the terminal device obtains a pre-stored list of joint platforms from the backend server. The list stores all joint platforms that have a joint relationship with the main control platform, and may also include the platform information of each joint platform, such as name, graphic logo, introduction, and services that can be provided by joint permissions of different permission levels. The terminal device can present a permission display interface containing various joint permissions based on this information. The specific presentation method of joint permissions can be cards, etc., which are not specifically limited in this application.

[0174] After selecting a target federated permission to be activated, the terminal device sends an activation request (i.e., binding request) for the target federated permission to the backend server. The activation request can carry the first identification information and the permission identifier corresponding to the target federated permission, etc. The data can be encrypted during the data transmission process to ensure security.

[0175] After receiving the activation request, the backend server constructs request data based on the target federation platform's interface specifications, including the user's primary identification information, permission level, name, and mobile phone number. This request data may include the federation server's address, request headers, and a request body. The request headers record the request body's format; for example, Content-Type: application / json indicates the request body is in JSON format, meaning the requested data will be sent as a JSON object. Similarly, data parsing also requires parsing in JSON format. Furthermore, the request headers contain authentication information to verify the legitimacy of the request source.

[0176] The request body contains all the data to be sent to the federated server, such as primary identification information, permission level, name, mobile phone number, and permission activation time.

[0177] Afterwards, the backend server can use an HTTP POST request to call the target federated platform's interface and send the request data. HTTPS can also be used to ensure data transmission security. Interface calls can employ Application Programming Interface (API) authentication, such as API keys, OAuth 2.0, or digital signatures, to prevent unauthorized calls. To improve response speed, interface calls are processed asynchronously; specifically, requests can be placed in a message queue and handled by a dedicated consumer program. For call failures, a retry strategy is set, including a retry interval (e.g., retrying every 5 minutes) and a maximum number of retries (e.g., a maximum of 3 retries). Simultaneously, request and response information for each interface call is recorded for troubleshooting purposes.

[0178] After receiving the request, the federated server issues the target federated permission of the corresponding permission level to the user and returns a successful response through the federated interface, indicating that the target federated permission has been activated. The backend server updates the status of the target federated permission to activated and binds the first identification information and the second identification information to the federated permission activation table, which may also include activation status, activation time, etc.

[0179] After successful activation, a message will be displayed indicating that the object has been successfully activated.

[0180] If the server returns an error message, the backend server records the reason for the error and notifies the relevant personnel to handle it.

[0181] Furthermore, the above method directly triggers the terminal device to send an activation request after the user selects a target joint permission to be activated. To prevent accidental activation by the user, it can be designed so that after the user selects a target joint permission to be activated, the interface jumps to the details page of the target joint permission, displaying more detailed service descriptions, usage rules, etc. The details page can also include "Activate" or "Get" buttons. After the user clicks the button, an activation confirmation dialog box pops up, and it can also prompt the user that this process involves the use of data related to their identity information, vehicle information, etc., requiring the user's active authorization. Only after the user triggers the confirmation dialog box and confirms activation will the terminal device send the activation request.

[0182] It should be noted that in the above process, if the user does not have first object data on the target federation platform, the user needs to be registered on the target federation platform before updating the target federation permission status in order to obtain the user's second identification information on the target federation platform. The permission level assessment can be performed after the user fills in the identity information and vehicle information, or after the user selects a target federation permission that needs to be activated. Both of these processes have been explained in detail above and will not be repeated here.

[0183] In this application, the permission level is not static and can be updated according to the user's service usage on the main control platform and the target joint platform. The prerequisite for implementing this update method is that the main control platform and the target joint platform perform data synchronization regularly. The data synchronization process is as follows:

[0184] The target federation platform periodically provides information on the usage of target federation permissions, i.e., service usage data, which may include points information, electronic resource exchange information, etc. Large-volume data transfers can still be accomplished by calling the federation interface, while small-volume data transfers can be accomplished using a secure file transfer protocol (SFTP) to transfer data files (CSV, JSON, etc.). After receiving the service usage data, the main control platform's backend server parses the transferred data file or the data returned by the interface, extracts the necessary information, such as the first identifier information, the usage time of each service, the service type, and the electronic resource exchange information, and stores this information in the service usage table.

[0185] Based on the continuous changes in the above information, the backend server can reassess the permission level. The reassessment can be triggered periodically, such as once a month, or in real time, or based on a preset precondition. For example, whenever an object performs a permission level query operation on a bound target's combined permissions, a permission level reassessment is triggered for that target's combined permissions.

[0186] For example, in response to a user's request on the main control platform to perform a level query operation for a target federated permission that has been bound, the terminal device sends a level query request to the backend server. After receiving the level query request from the terminal device, the backend server obtains the second object data of the user on the main control platform, and, based on the federated interface, re-obtains the first object data of the user under the target federated platform from the federated server corresponding to the target federated platform to which the target federated permission belongs. Then, based on the second object data and the re-obtained first object data, the backend server determines the completion status of each level task, and determines the latest permission level corresponding to the target federated permission based on the completion status. Finally, it sends each level task and the latest permission level to the terminal device.

[0187] After receiving the tasks of each level and the latest permission level sent by the backend server, the terminal device presents the corresponding level display interface; the level display interface contains multiple level tasks and the latest permission level corresponding to a target joint permission; each level task is associated with the main control platform, or with the target joint platform to which the target joint permission belongs.

[0188] In the above, the backend server obtains the first object data in real time through the joint interface. Alternatively, it can be set to obtain the data periodically, such as once a day, and store the obtained first object data in the service usage table. When the backend server receives a level query request sent by the terminal device, it can directly obtain the latest first object data from the service usage table without calling the interface again.

[0189] The latest permission level redefined by the backend server may be higher, lower, or the same as the original permission level, depending on the completion status of tasks at each level. If the permission level changes, the backend server needs to update the user's permission level table with the latest permission level and record the reassessment time for subsequent periodic reassessments. Simultaneously, it can notify users of the updated permission level and the services currently available via notification messages. Furthermore, after a permission level change, the backend server needs to notify the corresponding target federation platform to update the permission level.

[0190] The aforementioned level tasks are mainly divided into three categories. The first category is mainly related to the usage of the target's joint permissions and basic permissions, that is, to the user's service usage data under the main control platform and the target joint platform. For example, a level task could be to use the parking service more than 10 times this month. The second category of level tasks is to directly upgrade the permission level through electronic resource exchange. The third category of level tasks provides users with some tasks that can be performed immediately, such as information addition tasks (such as adding more vehicle information in S301) and browsing tasks (staying on a certain interface for a certain period of time). Once each type of level task meets certain requirements in terms of completion degree and quantity, the backend server can determine the permission level upgrade.

[0191] The execution status of all three task levels is recorded in the object data. If a task level is associated with the main control platform, its execution status is recorded in the second object data. If a task level is associated with a target joint platform, its execution status is recorded in the first object data corresponding to that target joint platform. Therefore, obtaining the first and second object data can determine the completion status of the task level.

[0192] Furthermore, the process of re-evaluating permission levels based on the completion status of the first type of tasks is essentially the same as the backend server's permission level evaluation process when a user initially binds target federated permissions. Therefore, this level evaluation rule can be directly used, or it can be fine-tuned before use. The other two types each have their own corresponding level evaluation rules, but these rules can all be stored in configuration files or databases and executed by the rule engine. The level evaluation rules also support personalized customization, meaning that the level tasks and level evaluation rules can be adjusted based on the user's first and second object data to better align with the user's interests and habits, thereby improving their satisfaction.

[0193] Furthermore, when the newly acquired permission level meets the preset permission requirements, the backend server can determine, based on the latest permission level, the other joint permissions corresponding to each joint platform, in addition to the target joint platform to which the target joint permissions already bound to the user belong, and send each other joint permission to the terminal device. The terminal device presents each other joint permission based on the latest permission level. After the user triggers a selection operation for one or more other joint permissions, the terminal device responds to the selection operation by sending a binding request to the backend server for these one or more other joint permissions. After receiving the binding request, the backend server binds the user's first identification information under the main control platform with at least one other joint permission, stores the binding result, and sends it to the terminal device. The terminal device presents the binding result of the user's first identification information under the main control platform and the at least one other joint permission selected by the user.

[0194] For example, suppose that for every two levels of any target federated permission, an additional optional federated permission can be provided to the user. After the user selects an additional federated permission, the terminal device and the backend server perform the same operation as when the target federated permission was first activated, issuing the selected additional federated permission to the account. This method can further enhance the user's motivation.

[0195] In the process of selecting other joint permissions, the user's interests, activity level, and other information can be determined based on the user's first and second object data. Based on this information, other joint permissions with higher interest levels can be recommended to the user.

[0196] In addition to automatically updating the permission level after detecting that the permission level of the user object can be updated based on the first object data and the second object data, as mentioned above, the original permission level can also be retained first, and the user object can be reminded to manually update the permission level through a notification message. This application does not make any specific limitations.

[0197] If the combined permissions or basic permissions have an expiration date, this application can also send push notifications to the users before the expiration date. Taking combined permissions as an example, the expiration date of combined permissions is also recorded in the level table. The backend server can periodically check the validity period of combined permissions, for example, at 24:00 every day, to obtain combined permissions that are about to expire, and send an expiration reminder notification to the users. The notification can specifically include information such as permission level and expiration date. The sending time, number of times, and interval of the notification can be set based on actual needs.

[0198] If the user chooses to continue using the joint permissions, they can enter the relevant renewal interface, which displays different renewal methods, such as renewal via electronic resource exchange. After the user selects the method, the electronic resource exchange can be completed in the same way as in S301. Afterwards, the backend server updates the validity period in the level table.

[0199] In summary, the permission sharing method proposed in this application simplifies the cumbersome process of registration and authentication for car owners on multiple platforms, achieving "one card for all cards." It enables car owners to enjoy combined permissions from multiple platforms with a single click on the main control platform, promoting cross-platform cooperation while improving the user experience for car owners. Furthermore, this application focuses on services with high-frequency needs, which can increase the activity of car owners on the main control platform. The rich services can better meet the needs of car owners, and relevant permissions can be personalized for them based on their interests and preferences.

[0200] The overall solution of this application can be divided into five modules: vehicle information authentication module, permission level assessment module, platform interoperability module, data processing and storage module, and security module. The division of labor and implementation of each module are as follows.

[0201] The vehicle information authentication module is mainly used to verify the correctness and validity of the vehicle information of the user. This can be achieved by calling a third-party OCR service.

[0202] II. The permission level assessment module is mainly used to calculate and assess permission levels based on preset level assessment rules, combined with the vehicle information and object information of the user, so as to provide differentiated service content.

[0203] The rating assessment rules can be defined in a rule file, which is stored in the configuration center or database and supports hot updates, making it convenient for relevant personnel to make adjustments. A rule management backend can also be set up to visually add, delete, modify and view rules. Rule execution is completed by the rule engine, and high-frequency rules can reduce the initialization overhead of the rule engine through pre-compilation.

[0204] Before inputting vehicle information and object data into the rule engine, big data analytics tools (such as Spark and Hadoop) can be used to clean, aggregate, and statistically analyze them. Different weights can also be configured for different types of information data. In addition, vehicle information and object data can also assist in adjusting the rating assessment rules.

[0205] For example, this application can also introduce machine learning algorithms to intelligently and accurately optimize the assessment of permission levels, thereby improving the accuracy of the assessment. The machine learning model can be a decision tree, random forest, support vector machine, etc. This approach requires pre-using some data, such as known permission levels and corresponding vehicle information and object data of the users, to construct training samples, train the machine learning model, adjust parameters, evaluate model performance, and then deploy the trained model to an online service to provide real-time permission assessment capabilities. It can be combined with a rule engine to form a hybrid assessment mechanism.

[0206] Machine learning models need to be updated with new training samples to maintain their accuracy and applicability.

[0207] III. The platform interoperability module is used to exchange relevant data with multiple joint platforms, enabling users to share services across different platforms. This process relies on API interfaces. A unified API interface specification needs to be established between the main control platform and the joint platforms, including request methods, data formats, and error code definitions. The interface can adopt a RESTful style and supports JSON data format.

[0208] Furthermore, detailed API documentation should be written, including interface descriptions, request parameters, return parameters, sample code, etc. Tools such as Swagger can be used to generate online documentation, facilitating integration with the joint platform.

[0209] Regularly manage API versions and use version numbers from Uniform Resource Identifiers (URIs) to identify different API versions. When adding or updating APIs, ensure backward compatibility.

[0210] The interface is designed using the adapter pattern, and corresponding adapters are developed for different joint platforms to convert the data format of the master platform to the format required by the joint platform, or to convert the data format of the joint platform to the data format required by the master platform.

[0211] Establish a field mapping table to define the correspondence between fields on both sides; support conversion of field data types and formats, such as date formats and encoding methods.

[0212] Configure field mapping and transformation rules and store them in configuration files or databases for easy maintenance and updates.

[0213] The data interaction process with the joint platform can adopt an asynchronous communication mechanism, using an asynchronous HTTP client to make interface calls to avoid blocking threads; for time-consuming requests, asynchronous callbacks or Future patterns can be used to improve concurrency performance; for failed requests, retrying can be performed according to a certain strategy and call logs can be recorded to facilitate troubleshooting.

[0214] Furthermore, messages can be saved as files for persistent storage, allowing them to be recovered from the corresponding files if lost, thus preventing message loss.

[0215] By leveraging blockchain's distributed ledger and smart contracts, trusted sharing of information related to permission levels and automatic settlement of permission levels can be achieved, enhancing the system's transparency and security.

[0216] IV. The data processing and storage module is responsible for the system's data storage, processing, and management, ensuring high availability, consistency, and security of the data.

[0217] Specifically, the database can be a relational database, storing the following data.

[0218] User Information Table: Stores the user's identity information and registration information related to the main control platform, such as primary identification information, name, mobile phone number, registration time, etc.

[0219] Vehicle Information Sheet: Stores detailed vehicle information, such as vehicle identification number, engine number, license plate number, vehicle type, etc.

[0220] Level table: Stores the permission level, permission status, and acquisition time of combined permissions and basic permissions.

[0221] Electronic Resource Exchange Form: Records relevant information for each electronic resource exchange, such as the quantity of electronic resources exchanged and the exchange time.

[0222] The database can create indexes on key fields to improve query performance; it also supports database sharding and table partitioning strategies, enabling horizontal and vertical scaling of data.

[0223] Using Redis as a caching middleware, we cache permission levels, vehicle information, and related information from the unified platform to accelerate access to hot data; when data changes, we update or delete the cache in a timely manner to prevent data inconsistency; and we set reasonable expiration times to prevent cached data from not being updated for a long time.

[0224] Deploy a Redis cluster using master-slave replication or sentinel mode to ensure high availability of the cache; use consistent hashing algorithm to achieve load balancing of the cache; perform full and incremental backups of the database regularly, with the backup cycle configurable based on actual needs; backup data can be encrypted and stored on secure storage media, such as cloud storage services or offline disks, and access permissions for backup data should be controlled, allowing only authorized personnel to access it.

[0225] Develop a data recovery operation manual, including recovery steps and precautions, and conduct data recovery drills regularly to ensure that data can be recovered quickly in emergency situations.

[0226] V. The security module is used to ensure the security and stability of the system. It sets access permissions for each of the above functional modules to prevent unauthorized operations, records key system operation logs, and prevents external attacks.

[0227] Specifically, identity authentication is used to prevent unauthorized access. An access token is generated for the administrator upon login, and subsequent requests must include this token for verification. Furthermore, biometric authentication methods such as facial recognition and fingerprints can be used to enhance both convenience and security.

[0228] By using a role-based access control model, different roles and permissions are defined, and the user's roles and permissions are checked in the backend service to control access to interfaces and resources.

[0229] Administrators can manage users, roles, and permissions in the permission management backend interface, and also support the dynamic allocation and revocation of permissions.

[0230] Record various operations performed on the user, such as login and information modification, to the operation log; record system running status, error messages, and abnormal situations to the system log; record security-related events, such as login failures, permission verification failures, and abnormal access, to the system log; collect logs centrally and store them in a log server or log management system, and use a log framework to uniformly manage log output.

[0231] Regularly analyze logs to identify potential system problems and security risks, issue warnings and alerts for abnormal behavior, and take timely measures.

[0232] Deploy firewalls, set security group rules, restrict network access, and use intrusion detection and prevention systems to monitor network traffic and prevent attacks.

[0233] Regularly conduct code security reviews, security tests, and penetration tests to prevent, discover, and fix security vulnerabilities.

[0234] Encrypt and store important data, and restrict access to important data.

[0235] In summary, the modular design facilitates the addition of new functions and integration with more joint platforms, while the distributed architecture and asynchronous communication ensure stable system operation, and multi-layered security measures protect data security.

[0236] Next, the method for joining permissions proposed in this application will be introduced on the backend server side, such as... Figure 17 The diagram shown is an overall flowchart of another method for combining permissions provided in this application embodiment. The specific implementation process of this method is as follows:

[0237] S1701: The backend server receives the permission query request sent by the terminal device and sends the permission display interface to the terminal device.

[0238] After the terminal device triggers the permission query operation using the object, it sends a permission query request to the backend server. After the server accepts the request, it obtains the permission display interface and sends it. The permission display interface contains the joint permissions corresponding to multiple joint platforms. A joint platform is a platform that has a joint relationship with the main control platform. Each joint permission is used to provide a cross-platform service of a joint platform.

[0239] S1702: The backend server receives a binding request from the terminal device for at least one target joint permission.

[0240] A binding request is sent from the terminal device to the backend server after a selection operation is triggered using the object against one or more target permissions.

[0241] S1703: The backend server will use the object's first identification information under the main control platform to bind it with at least one target joint permission, and send the binding result to the terminal device after storing it.

[0242] After receiving the binding result, the terminal device displays it to the user.

[0243] From a system architecture perspective, the overall architecture of this application can be mainly divided into three parts: the front end of the main control platform (terminal devices), the back end of the main control platform and the joint platform (backend servers and joint servers), and the joint interface, such as... Figure 18 The diagram illustrates a system architecture provided in this application embodiment. The front-end can be software, a mini-program, etc., responsible for interaction with users, such as information display, data input, and result feedback. The back-end handles business logic; for example, the back-end of the main control platform handles user account registration, permission level assessment, data storage, and security management, while the back-end of the joint platform can register joint permissions for users and provide the user's primary data. The joint interface is used to connect the main control platform and the joint platform, enabling data interoperability.

[0244] See Figure 19 The diagram shown is an interaction sequence diagram of a terminal device, a backend server, and a federated server provided in an embodiment of this application. Taking a federated platform as an example, assuming that the user object has first object data under the federated platform, the specific implementation process of this method is as follows:

[0245] Step 1901: The terminal device sends its identity information to the backend server.

[0246] Step 1902: The backend server registers an account for the user and returns the first identification information.

[0247] Step 1903: The terminal device sends vehicle information to the backend server.

[0248] Step 1904: The backend server verifies the vehicle information.

[0249] Step 1905: The backend server retrieves the first object data of the object being used from the federated server based on the federated interface.

[0250] Step 1906: The backend server determines the permission level of the joint permissions based on at least one of the vehicle information and the first object data.

[0251] Step 1907: The backend server returns the permission level of the combined permissions to the terminal device.

[0252] Step 1908: The terminal device sends a binding request for the combined permissions to the backend server.

[0253] Step 1909: The backend server sends the first identifier information, permission level and other data to the federation server based on the federation interface, requesting the issuance of federation permissions.

[0254] Step 1910: The federated server returns the result that federated permissions have been granted.

[0255] Step 1911: The backend server sends the result that the combined permissions have been bound to the terminal device.

[0256] Based on the same inventive concept, embodiments of this application also provide a joint device for authorization. For example... Figure 20 As shown, this is a schematic diagram of the structure of the authorization unit 200, which may include:

[0257] The first presentation unit 2001 is used to respond to the permission query operation triggered by the user on the main control platform and present the permission display interface. The permission display interface includes: the joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform.

[0258] The second presentation unit 2002 is used to respond to a selection operation triggered by the user for at least one target joint permission among multiple joint permissions, and to present the first identification information of the user under the main control platform and the binding result of the user selecting at least one target joint permission.

[0259] Optionally, the device also includes:

[0260] Registration unit 2003 is used to present a registration interface in response to a registration operation triggered by the user on the main control platform before presenting the permission display interface in response to a permission query operation triggered by the user on the main control platform.

[0261] In response to the information input operation triggered by the user on the registration interface, the identity information and vehicle information entered by the user are displayed.

[0262] In response to the user's input completion operation triggered on the registration interface, the user's first identification information under the main control platform is presented.

[0263] Optionally, the second presentation unit 2002 is also used for:

[0264] After responding to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, the system receives and presents the permission level corresponding to each of the at least one target joint permission returned by the backend server. Each permission level is determined by the backend server based on identity information, after obtaining the first object data of the user in the target joint platform to which each of the at least one target joint permission belongs, and based on at least one of the first object data and vehicle information, combined with preset level evaluation rules. Each first object data is the user's service usage under the corresponding target joint platform.

[0265] Optionally, for a certain target joint permission corresponding to a certain permission level, if the object being used does not have corresponding first object data under the target joint platform to which the target joint permission belongs, then the permission level corresponding to the target joint permission is determined by the backend server based on vehicle information and in combination with preset level evaluation rules.

[0266] For a given set of joint permissions, if the user object has corresponding first object data under the target joint platform to which the joint permission belongs, then the permission level corresponding to the joint permission is determined by the backend server based on the first object data and in combination with the preset level evaluation rules.

[0267] Optionally, the device also includes:

[0268] The third presentation unit 2004 is used to respond to the user's level query operation triggered on the main control platform for a bound target joint permission, and present the corresponding level display interface; the level display interface contains multiple level tasks and the latest permission level corresponding to a target joint permission; each level task is associated with the main control platform, or with the target joint platform to which the target joint permission belongs.

[0269] The latest permission level is determined by the backend server after receiving a level query request from the terminal device, based on the completion status of each level's tasks. The completion status is determined based on the user's second object data on the main control platform and the user's first object data on the target joint platform, which has been re-acquired. The level query request is sent by the user after triggering the level query operation.

[0270] Optionally, the third presentation unit 2004 is also used for:

[0271] After the corresponding level display interface is presented, if the latest permission level meets the preset level requirements, then based on the latest permission level, other joint permissions corresponding to each other joint platform will be presented, except for the target joint platform to which each of the target joint permissions belongs.

[0272] In response to a selection operation triggered by the user for at least one other combined permission, the system presents the user's first identification information under the main control platform and the binding result of the user's selected at least one other combined permission.

[0273] Optionally, the permissions display interface may also include:

[0274] The user's basic permissions under the main control platform; the basic permissions are related to the user's main control platform level.

[0275] The second type of combined device with permissions provided in the embodiments of this application. For example... Figure 21 As shown, this is a schematic diagram of the structure of the authorization device 210, which may include:

[0276] The sending unit 2101 is used to receive the permission query request sent by the terminal device and send the permission display interface to the terminal device. The permission display interface includes: the joint permissions corresponding to each of the multiple joint platforms associated with the main control platform. Each joint permission is used to provide a cross-platform service of a joint platform. The permission query request is sent after the permission query operation is triggered by the object.

[0277] The receiving unit 2102 is used to receive a binding request sent by the terminal device for at least one target joint permission; the binding request is sent after the user triggers a selection operation for at least one target joint permission among multiple joint permissions.

[0278] Binding unit 2103 is used to bind the first identification information of the user object under the main control platform with at least one target joint permission, and send the binding result to the terminal device after storing it.

[0279] Optionally, the device also includes:

[0280] Registration unit 2104 is used to receive a registration request sent by the terminal device before receiving a permission query request, and to send a registration interface to the terminal device; the registration request is sent after the registration operation is triggered by the object.

[0281] Receive identity and vehicle information sent by terminal devices, and create corresponding first identification information for the user on the main control platform;

[0282] The first identification information is bound and stored together with the identity information and vehicle information, and then the first identification information is sent to the terminal device.

[0283] Optionally, the device also includes:

[0284] The acquisition unit 2105 is used to, after receiving a binding request sent by the terminal device for at least one target joint permission, acquire, based on identity information, the first object data of the user in the target joint platform to which each of the at least one target joint permission belongs; each first object data is the service usage of the user in the corresponding target joint platform;

[0285] Based on at least one of the first object data and vehicle information, and combined with preset level evaluation rules, the permission level corresponding to each of the at least one target joint permission is determined.

[0286] Send the permission level corresponding to each of the at least one target joint permission to the terminal device.

[0287] Optionally, the acquisition unit 2105 is specifically used for:

[0288] For a given set of joint permissions, if the user does not have corresponding first object data under the target joint platform to which the joint permission belongs, the permission level corresponding to the joint permission is determined based on the vehicle information and the preset level evaluation rules.

[0289] If the object being used exists within a target federation platform to which a target federation permission belongs, and there is corresponding first object data, then based on the first object data and in conjunction with the preset level evaluation rules, the permission level corresponding to a target federation permission is determined.

[0290] Optionally, the acquisition unit 2105 is also used for:

[0291] After determining the permission level corresponding to a target joint permission based on vehicle information and in conjunction with preset level evaluation rules, the permission level and identity information are sent to the joint server of the target joint platform via the joint interface. The joint interface is used to: convert the data format of the permission level and identity information according to preset requirements; the permission level is used to: enable the joint server to determine the user object and grant the target joint permission corresponding to the permission level.

[0292] Based on the federation interface, obtain the second identification information sent by the federation server, which is based on identity information and created for the user on the target federation platform, and store the second identification information in association with the first identification information.

[0293] Optionally, the device also includes:

[0294] The determining unit 2106 is used to receive a level query request sent by the terminal device for a target joint permission that has been bound; the level query request is sent after the level query operation is triggered by the object.

[0295] Obtain the second object data of the user on the main control platform, and based on the federation interface, re-obtain the first object data of the user under the target federation platform in the federation server corresponding to the target federation platform to which the target federation permission belongs;

[0296] Based on the second object data and the reacquired first object data, the completion status of each level of task is determined, and each level of task is associated with the main control platform or the target joint platform.

[0297] Based on the completion status, determine the latest permission level corresponding to a target joint permission, and send the tasks of each level and the latest permission level to the terminal device.

[0298] Optionally, the determining unit 2106 is also used for:

[0299] After sending the tasks of each level and the latest permission level to the terminal device, if the latest permission level meets the preset level requirements, then based on the latest permission level, determine the other joint permissions corresponding to each other joint platform, except for the target joint platform to which each of the at least one target joint permission belongs, and send each other joint permission to the terminal device.

[0300] Receive a binding request sent by the terminal device for at least one other combined permission; the binding request is sent after a selection operation is triggered using an object;

[0301] The first identification information of the user object under the main control platform is bound with at least one other joint permission, and the binding result is stored and sent to the terminal device.

[0302] For ease of description, the above sections are divided into modules (or units) according to their functions and described separately. Of course, in implementing this application, the functions of each module (or unit) can be implemented in one or more software or hardware components.

[0303] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0304] Having described the combined methods and apparatus of the exemplary embodiments of this application, we will now describe an electronic device according to another exemplary embodiment of this application.

[0305] Those skilled in the art will understand that various aspects of this application can be implemented as a system, method, or program product. Therefore, various aspects of this application can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, collectively referred to herein as a "circuit," "module," or "system."

[0306] Based on the same inventive concept as the above-described method embodiments, this application also provides an electronic device. In one embodiment, the electronic device may be a server, such as... Figure 2 The server 220 is shown. In this embodiment, the structure of the electronic device can be as follows: Figure 22 As shown, it includes a memory 2201, a communication module 2203, and one or more processors 2202.

[0307] The memory 2201 is used to store computer programs executed by the processor 2202. The memory 2201 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and programs required to run instant messaging functions, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

[0308] Memory 2201 may be volatile memory, such as random-access memory (RAM); memory 2201 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 2201 may be any other medium capable of carrying or storing a desired computer program having the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 2201 may be a combination of the above-described memories.

[0309] Processor 2202 may include one or more central processing units (CPUs) or digital processing units, etc. Processor 2202 is used to implement the aforementioned combined method of permissions when calling a computer program stored in memory 2201.

[0310] The communication module 2203 is used to communicate with terminal devices and other servers.

[0311] This application embodiment does not limit the specific connection medium between the memory 2201, communication module 2203, and processor 2202. This application embodiment... Figure 22 The memory 2201 and the processor 2202 are connected via a bus 2204, and the bus 2204 is in Figure 22 The diagram uses thick lines to describe the connections between other components; these are for illustrative purposes only and should not be considered limiting. The 2204 bus can be divided into address bus, data bus, control bus, etc. For ease of description, Figure 22 It is described using only a thick line, but does not indicate that there is only one bus or one type of bus.

[0312] The memory 2201 stores a computer storage medium, which in turn stores computer-executable instructions for implementing the permission combination method of the embodiments of this application. The processor 2202 is used to execute the aforementioned permission combination method, such as... Figure 17 As shown.

[0313] In another embodiment, the electronic device can also be other electronic devices, such as... Figure 2 The terminal device 210 is shown. In this embodiment, the electronic device can be structured as follows: Figure 23As shown, it includes components such as: communication component 2310, memory 2320, display unit 2330, camera 2340, sensor 2350, audio circuit 2360, Bluetooth module 2370, processor 2380, etc.

[0314] The communication component 2310 is used to communicate with the server. In some embodiments, it may include a Wireless Fidelity (WiFi) module, which is a short-range wireless transmission technology, and the electronic device can use the WiFi module to help the user send and receive information.

[0315] The memory 2320 can be used to store software programs and data. The processor 2380 executes various functions of the terminal device 210 and performs data processing by running the software programs or data stored in the memory 2320. The memory 2320 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The memory 2320 stores an operating system that enables the terminal device 210 to run. In this application, the memory 2320 may store the operating system and various application programs, and may also store computer programs that execute the combined methods permitted by the embodiments of this application.

[0316] The display unit 2330 can also be used to display information input by the user or information provided to the user, as well as various menus of the terminal device 210, in a graphical user interface (GUI). Specifically, the display unit 2330 may include a display screen 2332 disposed on the front of the terminal device 210. The display screen 2332 may be configured as a liquid crystal display, a light-emitting diode, or the like. The display unit 2330 can be used to display the main control platform interface, etc., as described in this application embodiment.

[0317] The display unit 2330 can also be used to receive input digital or character information and generate signal inputs related to object settings and function control of the terminal device 210. Specifically, the display unit 2330 may include a touch screen 2331 disposed on the front of the terminal device 210, which can collect touch operations on or near the object, such as clicking a button, dragging a scroll box, etc.

[0318] The touchscreen 2331 can be placed on top of the display screen 2332, or the touchscreen 2331 and the display screen 2332 can be integrated to realize the input and output functions of the terminal device 210. After integration, it can be referred to as a touch display screen. In this application, the display unit 2330 can display the application and the corresponding operation steps.

[0319] Camera 2340 can be used to capture still images, and objects can publish images captured by camera 2340 through an application. There can be one or multiple cameras 2340. An object generates an optical image through a lens, which is projected onto a photosensitive element. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to processor 2380 to be converted into a digital image signal.

[0320] The terminal device may also include at least one sensor 2350, such as an accelerometer 2351, a proximity sensor 2352, a fingerprint sensor 2353, and a temperature sensor 2354. The terminal device may also be equipped with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, and motion sensor.

[0321] Audio circuitry 2360, speaker 2361, and microphone 2362 provide an audio interface between the device and terminal device 210. Audio circuitry 2360 converts received audio data into electrical signals, which are then transmitted to speaker 2361, where they are converted into sound signals for output. Terminal device 210 may also be equipped with volume buttons for adjusting the volume of the sound signal. On the other hand, microphone 2362 converts collected sound signals into electrical signals, which are then received by audio circuitry 2360, converted back into audio data, and output to communication component 2310 for transmission to, for example, another terminal device 210, or to memory 2320 for further processing.

[0322] The Bluetooth module 2370 is used to interact with other Bluetooth devices that also have a Bluetooth module via the Bluetooth protocol. For example, a terminal device can establish a Bluetooth connection with a wearable electronic device (such as a smartwatch) that also has a Bluetooth module through the Bluetooth module 2370, thereby exchanging data.

[0323] The processor 2380 is the control center of the terminal device, connecting various parts of the terminal through various interfaces and lines. It executes various functions and processes data by running or executing software programs stored in the memory 2320 and calling data stored in the memory 2320. In some embodiments, the processor 2380 may include one or more processing units; the processor 2380 may also integrate an application processor and a baseband processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the baseband processor mainly handles wireless communication. It is understood that the baseband processor may not be integrated into the processor 2380. In this application, the processor 2380 can run the operating system, applications, user interface display and touch response, and the combined method of permissions in the embodiments of this application. Furthermore, the processor 2380 is coupled to the display unit 2330.

[0324] In some possible implementations, various aspects of the combined methods of permissions provided in this application can also be implemented in the form of a program product comprising a computer program that, when run on an electronic device, causes the electronic device to perform the steps of the combined methods of permissions according to the various exemplary embodiments of this application described above. For example, the electronic device may perform actions such as... Figure 3 or Figure 17 The steps are shown in the figure.

[0325] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0326] The program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include a computer program, and may run on an electronic device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with a command execution system, apparatus, or device.

[0327] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a readable computer program. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with a command execution system, apparatus, or device.

[0328] Computer programs contained on readable media may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0329] Computer programs for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The computer program can execute entirely on the target electronic device, partially on the target electronic device, as a standalone software package, partially on the target electronic device and partially on a remote electronic device, or entirely on a remote electronic device or server. In cases involving remote electronic devices, the remote electronic device can be connected to the target electronic device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external electronic device (e.g., via the Internet using an Internet service provider).

[0330] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0331] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0332] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing a computer-usable computer program.

[0333] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0334] These computer program commands may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the commands stored in the computer-readable storage medium produce an article of manufacture including command means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0335] These computer program commands may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the commands executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0336] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0337] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for joining permissions, characterized in that, Applied to a terminal device, the method includes: In response to a permission query operation triggered by the user on the main control platform, a permission display interface is presented. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform. In response to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, the system presents the user's first identification information under the main control platform and the binding result of the user's selected at least one target joint permission.

2. The method as described in claim 1, characterized in that, Before presenting the permission display interface in response to a permission query operation triggered by the user on the main control platform, the method further includes: In response to the registration operation triggered by the user on the main control platform, a registration interface is displayed; In response to the information input operation triggered by the user on the registration interface, the identity information and vehicle information input by the user are presented. In response to the user's input completion operation triggered on the registration interface, the user's first identification information under the main control platform is presented.

3. The method as described in claim 2, characterized in that, Following the selection operation triggered by the user for at least one target joint permission among multiple joint permissions, the method further includes: The system receives and presents the permission levels corresponding to each of the at least one target joint permission returned by the backend server. Each permission level is determined by the backend server based on the identity information, after obtaining the first object data of the target joint platform to which the user belongs for each of the at least one target joint permission, and based on at least one of the first object data and the vehicle information, combined with a preset level evaluation rule. Each first object data represents the user's service usage under the corresponding target joint platform.

4. The method as described in claim 3, characterized in that, The method further includes: For a given set of joint permissions, if the user does not have corresponding first object data under the target joint platform to which the target joint permission belongs, then the set of joint permissions is determined by the backend server based on the vehicle information and in conjunction with preset level evaluation rules. For a given set of joint permissions, if the user object has corresponding first object data under the target joint platform to which the target joint permission belongs, then the set of joint permissions is determined by the backend server based on the first object data and in conjunction with preset level evaluation rules.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: In response to the user's request on the main control platform to trigger a level query operation for a bound target joint permission, a corresponding level display interface is presented; the level display interface contains multiple level tasks and the latest permission level corresponding to the target joint permission; each level task is associated with the main control platform, or with the target joint platform to which the target joint permission belongs; The latest permission level is determined by the backend server after receiving the level query request sent by the terminal device, based on the completion status of each level task. The completion status is determined based on the second object data of the user on the main control platform and the first object data of the user on the target joint platform that has been re-acquired. The level query request is sent by the user after triggering the level query operation.

6. The method as described in claim 5, characterized in that, After presenting the corresponding level display interface, the method further includes: If the latest permission level meets the preset permission requirements, then based on the latest permission level, other joint permissions corresponding to each other joint platform, in addition to the target joint platform to which each of the at least one target joint permission belongs, are presented. In response to the user's selection operation triggered by at least one other combined permission, the first identification information of the user under the main control platform is presented, along with the binding result of the user's selection of at least one other combined permission.

7. The method according to any one of claims 1 to 4, 6, characterized in that, The permission display interface also includes: The user's basic permissions under the main control platform; the basic permissions are associated with the user's main control platform level under the main control platform.

8. A method for combining permissions, characterized in that, The method, applied to the backend server of the main control platform, includes: The system receives a permission query request from a terminal device and sends a permission display interface to the terminal device. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform; the permission query request is sent after the permission query operation is triggered by the object. The terminal device receives a binding request for at least one target combined permission; the binding request is sent after the user triggers a selection operation for at least one target combined permission among multiple combined permissions. The first identification information of the user under the main control platform is bound to the at least one target joint permission, and the binding result is stored and sent to the terminal device.

9. The method as described in claim 8, characterized in that, Before receiving the permission query request, the method further includes: The system receives a registration request from the terminal device and sends a registration interface to the terminal device; the registration request is sent after the registration operation is triggered by the object. Receive identity information and vehicle information sent by the terminal device, and create corresponding first identification information for the user on the main control platform; The first identification information is bound and stored together with the identity information and the vehicle information, and the first identification information is sent to the terminal device.

10. The method as described in claim 9, characterized in that, After receiving the binding request sent by the terminal device for at least one target combined permission, the method further includes: Based on the identity information, obtain the first object data of the user on the target federation platform to which each of the at least one target federation permission belongs; each first object data is the service usage of the user on the corresponding target federation platform. Based on at least one of the first object data and the vehicle information, and in conjunction with preset level evaluation rules, the permission level corresponding to each of the at least one target joint permission is determined respectively. The permission level corresponding to each of the at least one target combined permission is sent to the terminal device.

11. The method as described in claim 10, characterized in that, The step of determining the permission level corresponding to each of the at least one target joint permission based on at least one of the first object data and the vehicle information, combined with a preset level evaluation rule, includes: For a given set of joint permissions, if the user does not have corresponding first object data under the target joint platform to which the target joint permission belongs, the permission level corresponding to the target joint permission is determined based on the vehicle information and in conjunction with the preset level evaluation rules. If the user object has corresponding first object data under the target joint platform to which the target joint permission belongs, then based on the first object data and combined with the preset level evaluation rules, the permission level corresponding to the target joint permission is determined.

12. The method as described in claim 11, characterized in that, After determining the permission level corresponding to the target joint permission based on the vehicle information and in accordance with preset level evaluation rules, the method further includes: Based on the federated interface, the permission level and the identity information are sent to the federated server of the target federated platform. The federated interface is used to: convert the data format of the permission level and the identity information based on preset requirements; the permission level is used to: enable the federated server to determine that the user object is granted the target federated permission corresponding to the permission level. Based on the federation interface, the second identification information created for the user on the target federation platform based on the identity information sent by the federation server is obtained, and the second identification information is associated with and stored with the first identification information.

13. The method according to any one of claims 8 to 12, characterized in that, The method further includes: The terminal device receives a level query request for a target combined permission that has been bound; the level query request is sent after the user triggers a level query operation; Obtain the second object data of the user on the main control platform, and based on the federation interface, re-obtain the first object data of the user under the target federation platform in the federation server corresponding to the target federation platform to which the target federation permission belongs; Based on the second object data and the reacquired first object data, the completion status of each level of task is determined, and each level of task is associated with the main control platform or the target joint platform. Based on the completion status, determine the latest permission level corresponding to the target joint permission, and send the tasks of each level and the latest permission level to the terminal device.

14. The method as described in claim 13, characterized in that, After sending the tasks at each level and the latest permission level to the terminal device, the method further includes: If the latest permission level meets the preset permission requirements, then based on the latest permission level, determine the other joint permissions corresponding to each of the other joint platforms, in addition to the target joint platform to which each of the at least one target joint permission belongs, and send each of the other joint permissions to the terminal device; The terminal device receives a binding request for at least one other combined permission; the binding request is sent after the user triggers a selection operation. The first identification information of the user under the main control platform is bound with at least one other joint permission, and the binding result is stored and sent to the terminal device.

15. A device for the joint authority, characterized in that, include: The first presentation unit is used to respond to the permission query operation triggered by the user on the main control platform and present a permission display interface. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform. The second presentation unit is used to respond to the user's selection operation triggered by at least one target joint permission among multiple joint permissions, and to present the user's first identification information under the main control platform and the binding result of the user's selected at least one target joint permission.

16. A device for the joint authority, characterized in that, include: The sending unit is used to receive permission query requests sent by the terminal device and send a permission display interface to the terminal device. The permission display interface includes: joint permissions corresponding to multiple joint platforms associated with the main control platform; each joint permission is used to provide a cross-platform service of a joint platform; the permission query request is sent after the permission query operation is triggered by the object. A receiving unit is configured to receive a binding request sent by the terminal device for at least one target joint permission; The binding request is sent after the user triggers a selection operation for at least one target combined permission among multiple combined permissions; The binding unit is used to bind the first identification information of the user object under the main control platform with the at least one target joint permission, and send the binding result to the terminal device after storing it.

17. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of any of the methods described in claims 1 to 14.

18. A computer-readable storage medium, characterized in that, It includes a computer program that, when run on an electronic device, causes the electronic device to perform the steps of any of the methods described in claims 1 to 14.

19. A computer program product, characterized in that, The method includes a computer program stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, causing the electronic device to perform the steps of any one of claims 1 to 14.

Images