A cascading interconnection and vehicle service switching method across a cloud control basic platform

Abstract

The application provides a cascading interconnection and vehicle service switching method of cross-cloud control basic platforms, which is applied to a system composed of a first cloud control basic platform and a second cloud control basic platform, a cross-cloud control basic platform mutual trust relationship is built between the first cloud control basic platform and the second cloud control basic platform, and the method comprises the following steps: when the second cloud control basic platform receives a vehicle service area switching instruction, the second cloud control basic platform initiates a vehicle cross-platform identity authentication request to the first cloud control basic platform based on the cross-platform mutual trust relationship; the first cloud control basic platform verifies the vehicle cross-platform identity authentication request and returns a vehicle identity verification result and a cross-platform authorization credential to the second cloud control basic platform; the second cloud control basic platform completes vehicle access based on the identity verification result and the cross-platform authorization credential, and allocates corresponding cloud control service capabilities to the vehicle based on the vehicle identity. Through implementation of the application, the continuity in a high-speed moving scene of the vehicle is improved.

Description

Technical Field

[0001] This invention belongs to the field of intelligent vehicle networking technology, specifically relating to a method for cross-cloud control platform cascading interconnection and vehicle service switching. Background Technology

[0002] With the large-scale development of vehicle-road-cloud integration and intelligent connected vehicles, cloud control infrastructure platforms are usually divided into multiple independently operating cloud control infrastructure platform instances according to administrative regions, operating entities, or network deployment conditions, such as edge cloud, regional cloud, and central cloud.

[0003] Existing cloud control infrastructure platforms mostly adopt a regional autonomy and independent operation mode, which has the following problems: First, vehicles need to be repeatedly authenticated when traveling across regions; second, when vehicles travel across regions, the original cloud control infrastructure platform service is interrupted, and it is necessary to reconnect to the target cloud control infrastructure platform, resulting in a discontinuous service experience.

[0004] Existing technologies typically rely on interface connections between cloud control platforms or manual configuration, which is insufficient to meet the continuity requirements in high-speed vehicle movement scenarios. Therefore, it is necessary to propose a technical solution that supports interoperability across cloud control platforms and seamless switching of vehicle services. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a method for cascading and interoperating across cloud control platforms and switching vehicle services to meet the continuity requirements in high-speed vehicle movement scenarios.

[0006] To achieve the above objectives, the present invention provides the following technical solution: This invention provides a method for cascading interoperability and vehicle service switching across cloud control infrastructure platforms, applied to a system composed of a first cloud control infrastructure platform and a second cloud control infrastructure platform. The first and second cloud control infrastructure platforms establish a cross-platform mutual trust relationship through a cloud control infrastructure platform registration mechanism. The method includes: when the second cloud control infrastructure platform receives a vehicle service area switching instruction, the second cloud control infrastructure platform, based on the cross-platform mutual trust relationship, initiates a vehicle cross-platform identity authentication request to the first cloud control infrastructure platform. The vehicle service area switching instruction is sent when a vehicle enters the service area of ​​the second cloud control infrastructure platform from the service area of ​​the first cloud control infrastructure platform; the first cloud control infrastructure platform verifies the vehicle cross-platform identity authentication request and returns the vehicle identity verification result and cross-platform authorization credential to the second cloud control infrastructure platform; the second cloud control infrastructure platform completes vehicle access based on the identity verification result and cross-platform authorization credential, and allocates corresponding cloud control service capabilities to the vehicle based on its identity.

[0007] This embodiment provides a method for cascading interconnection and vehicle service switching across cloud control platforms. By constructing a peer-to-peer interconnection and collaboration mechanism between cross-regional clouds, vehicles can continuously obtain cloud control services during cross-regional and cross-node driving, significantly improving the continuity and availability of cross-regional vehicle-road-cloud collaborative services. At the same time, the cloud automatically completes the migration, mapping, and switching of service instances, while the vehicle side only maintains a unified service access interface, realizing seamless cross-regional cloud control service switching for vehicles. This method significantly reduces the burden on the vehicle-side system and is conducive to large-scale deployment and unified access for different vehicle models.

[0008] Other advantages, objectives, and features of the invention will be set forth in the following description and will be apparent to those skilled in the art in some respects, or may be learned by practice of the invention. The objectives and other advantages of the invention can be realized and obtained through the following description. Attached Figure Description

[0009] To make the objectives, technical solutions, and beneficial effects of this invention clearer, the following figures are provided for illustration: Figure 1 This is a flowchart illustrating a specific example of a method for cascading and interconnecting across cloud control platforms and switching vehicle services in this invention. Figure 2 This is a data interaction diagram of the first cloud control platform, the second cloud control platform, and the vehicle in a cross-cloud control platform cascading interconnection and vehicle service switching method of the present invention. Detailed Implementation

[0010] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0011] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can also refer to the internal connection of two components; and they can refer to a wireless connection or a wired connection. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0012] Furthermore, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0013] This invention provides a method for cascading interoperability and vehicle service switching across cloud control infrastructure platforms, applied to a system composed of a first cloud control infrastructure platform and a second cloud control infrastructure platform. The first and second cloud control infrastructure platforms establish a cross-cloud control infrastructure platform mutual trust relationship through a cloud control infrastructure platform registration mechanism. Figure 1 As shown, the method includes: S101, When the second cloud control platform receives a vehicle service area switching instruction, the second cloud control platform initiates a vehicle cross-platform identity authentication request to the first cloud control platform based on the vehicle service area switching instruction and the cross-platform mutual trust relationship. The vehicle service area switching instruction is sent when the vehicle enters the service area of ​​the second cloud control platform from the service area of ​​the first cloud control platform. S102, the first cloud control platform verifies the vehicle's cross-platform identity authentication request and returns the vehicle identity authentication result and cross-platform authorization certificate to the second cloud control platform; S103, the second cloud control platform completes vehicle access based on identity verification results and cross-platform authorization credentials, and assigns corresponding cloud control service capabilities to the vehicle based on the vehicle's identity.

[0014] For example, it should be noted that in this embodiment, both the first cloud control infrastructure platform and the second cloud control infrastructure platform have independent cloud control service capabilities, including functions such as vehicle identity management, cloud control command issuance, vehicle status collection, and service permission allocation. Furthermore, both parties support data interaction based on a preset cross-platform communication protocol to ensure the security and real-time performance of cross-platform information transmission. At the same time, all vehicles have completed initial access registration on the first cloud control infrastructure platform, which has generated a unique vehicle identity identifier for each vehicle and assigned corresponding cloud control service authorization information to the vehicle based on this vehicle identity identifier.

[0015] When a vehicle detects that its location has moved from the service area of ​​the first cloud control platform to the service area of ​​the second cloud control platform through the positioning module, the vehicle actively sends a vehicle service area switching command to the second cloud control platform. It should be noted that the vehicle service area switching command can be generated by the first cloud control platform and sent to the vehicle. This command can include the vehicle's identity identifier, current location information, and the trusted identifier of the first cloud control platform.

[0016] After receiving a vehicle service area switching command from the vehicle, the second cloud control platform first determines the corresponding platform based on the first cloud control platform information in the command. Then, it verifies the trusted identifier of the first cloud control platform stored locally against the trusted identifier in the command to confirm that a cross-platform trust relationship has been established. In addition, it can determine whether the vehicle has entered the service area of ​​the second cloud control platform based on its current location information. Subsequently, based on this trust relationship, it initiates a cross-platform vehicle identity authentication request to the first cloud control platform. This authentication request includes the following core information: the platform identifier of the second cloud control platform, the vehicle identity identifier, the vehicle's current location information, and the platform signature of the second cloud control platform, used to prove the legitimacy and authenticity of the authentication request and prevent unauthorized attacks.

[0017] After receiving the vehicle cross-platform identity authentication request from the second cloud control platform, the first cloud control platform immediately initiates the identity authentication process. The specific authentication steps are as follows: The first cloud control platform extracts the second cloud control platform identifier and platform signature from the request. Combining this with the locally stored second cloud control platform trusted identifier and platform certificate, it decrypts and verifies the platform signature to confirm that the requester is the second cloud control platform with whom a mutual trust relationship has been established. If verification fails, the authentication request is rejected, and a verification failure message is returned to the second cloud control platform. If verification succeeds, the next step is taken: the first cloud control platform extracts the vehicle identity identifier from the request, queries its local vehicle identity management database to confirm that the vehicle identity identifier has completed initial registration and that the vehicle's current status is normal. It also verifies the authenticity of the vehicle's current location information to confirm that the vehicle has indeed left its service area. If the vehicle identity is invalid or the location information is abnormal, an authentication failure result is returned. If verification passes, the first cloud control platform confirms that the vehicle identity and request are legitimate. Based on the vehicle's original authorization information on its own platform, it generates a cross-platform authorization credential. This cross-platform authorization credential is a short-term valid encrypted credential. As an optional implementation, the cross-platform authorization credential includes: a vehicle identity digest, the first cloud control platform identifier, the credential validity period, and the first cloud control platform signature.

[0018] The first cloud control platform will send the vehicle identity verification result and the generated cross-platform authorization certificate to the second cloud control platform through an encrypted communication channel. When the verification fails, the reason for the failure must be provided, such as invalid vehicle identity or platform signature verification failure.

[0019] After receiving the vehicle authentication result and cross-platform authorization credential from the first cloud control platform, the second cloud control platform first verifies the legality of the cross-platform authorization credential. Specifically, it extracts the first cloud control platform identifier and signature from the credential, combines it with the locally stored trusted identifier and platform certificate of the first cloud control platform, decrypts and verifies the signature, and verifies the validity period of the credential. If the credential has expired or the signature is invalid, the vehicle access is rejected and an access failure message is returned to the vehicle. If the credential verification passes and the authentication result is successful, the vehicle's seamless access is completed. That is, the vehicle does not need to be manually operated and automatically switches to the cloud control service jurisdiction of the second cloud control platform, achieving seamless service switching.

[0020] After seamless vehicle access is achieved, the second cloud control platform, based on the vehicle's identity and in conjunction with a pre-established cross-cloud service capability mapping relationship—meaning the first and second cloud control platforms synchronized and mapped their available service capabilities in advance—assigns corresponding cloud control service capabilities to the vehicle. Specifically, the second cloud control platform, based on the vehicle's identity, retrieves the vehicle service context information pre-sent and stored by the first cloud control platform and completes the service capability mapping.

[0021] It should be further noted that this embodiment supports the same operating entity managing multiple regional cloud control infrastructure platforms, and also supports different operating entities managing different regional cloud control infrastructure platforms while achieving interconnectivity. Through a unified cross-cloud registration, authentication, and operation management mechanism, the platform's scalability, operability, and commercialization capabilities in multi-regional and multi-entity scenarios are effectively improved.

[0022] This invention provides a method for cascading interconnection and vehicle service switching across cloud control platforms. By constructing a peer-to-peer interconnection and collaboration mechanism between cross-regional clouds, vehicles can continuously obtain cloud control services during cross-regional and cross-node driving, significantly improving the continuity and availability of cross-regional vehicle-road-cloud collaborative services. At the same time, the cloud automatically completes the migration, mapping, and switching of service instances, while the vehicle side only maintains a unified service access interface, realizing seamless cross-regional cloud control service switching for vehicles. This method significantly reduces the burden on the vehicle-side system and is conducive to large-scale deployment and unified access for different vehicle models.

[0023] As an optional implementation, the second cloud control platform completes vehicle access based on authentication results and cross-platform authorization credentials, and assigns corresponding cloud control service capabilities to the vehicle based on its identity, including: When the identity verification result and cross-platform authorization credential both pass the authentication conditions, the vehicle service context information is retrieved based on the vehicle identity, and the cloud control service status corresponding to the vehicle is restored according to the vehicle service context information, so that the vehicle can continuously receive cloud control services in the second cloud control basic platform. The vehicle service context information is generated by the first cloud control platform before the vehicle leaves its service area, and synchronized to the second cloud control platform before the vehicle enters the service area of ​​the second cloud control platform. The vehicle service context information includes at least the cloud control service type that the vehicle has enabled, service status parameters, and service validity identifier.

[0024] For example, the second cloud control platform uses the vehicle's identity identifier as a unique index to retrieve the vehicle's service context information. This vehicle service context information is not actively queried and obtained by the second cloud control platform, but is proactively generated and synchronized by the first cloud control platform in advance when the vehicle detects that it is about to leave its service area. Specifically, the vehicle collects its location information in real time through its own positioning module. When it detects that its own location is less than the boundary of the service area of ​​the first cloud control platform, it sends a warning message to the first cloud control platform that it is about to leave the service area. The preset threshold can be set to 1-5 kilometers and adjusted according to the service area coverage.

[0025] After receiving the warning message, the first cloud control platform immediately retrieves the vehicle-related service data stored locally, generates vehicle service context information, and synchronizes the vehicle service context information to the second cloud control platform through the established cross-platform mutual trust channel before the vehicle officially enters the service area of ​​the second cloud control platform. After receiving it, the second cloud control platform associates it with the vehicle's identity identifier and stores it in its local cache.

[0026] After retrieving the vehicle service context information, the second cloud control platform restores the corresponding cloud control service status of the vehicle based on this information. Specifically, it extracts the contents recorded in the vehicle service context information and matches them one by one with the service configuration of its own platform to ensure that the vehicle can continuously receive cloud control services in the second cloud control platform, thereby achieving seamless service continuity across regions and avoiding service interruption or status reset.

[0027] The specific content of the vehicle service context information is as follows: it is all real service status data before the vehicle switches to a different platform, including at least: the types of cloud control services that the vehicle has enabled, the current status parameters of each service, and the service validity identifier. The cloud control service types include traffic light reminders, green wave traffic, collision warning, etc. The current status parameters of each service may include the filtering speed of the green wave traffic service, the collision warning distance, etc. The validity identifier is used to identify whether each cloud control service is in a normal effective state, and can be divided into three states: effective, suspended, and disabled.

[0028] This invention provides a method for cascading and interoperating across cloud control platforms and switching vehicle services. By adding a service context pre-synchronization and status continuity control mechanism, the core service data and operating status can be synchronized and cached in advance before the cross-platform switch. After the platform switch is completed, the original service configuration, operating parameters and business session status of the vehicle can be quickly restored, effectively avoiding the problem of service parameter reset, realizing a seamless cross-platform continuity experience, and reducing the latency of real-time data interaction during the switch.

[0029] As an optional implementation, before a vehicle enters the service area of ​​a second cloud control platform from the service area of ​​a first cloud control platform, the method includes: The first cloud control platform receives vehicle registration requests, which contain vehicle information. The first cloud control platform generates vehicle identification based on vehicle information; Based on the vehicle's identity identifier, initial cloud control service authorization information is generated for the vehicle.

[0030] For example, when a vehicle enters the service area of ​​the first cloud control platform for the first time, the vehicle actively sends an initial registration request to the first cloud control platform. The request contains complete basic information about the vehicle itself, which may include: vehicle unique identifier, vehicle model, and vehicle hardware configuration parameters.

[0031] Upon receiving the initial registration request from a vehicle, the First Cloud Control Platform immediately initiates a vehicle information verification process. The verification includes verifying the legality of the vehicle's VIN code and the authenticity of the vehicle's hardware configuration parameters. During the verification process, if any information is found to be illegal, invalid, or abnormal, the First Cloud Control Platform immediately sends a verification failure message to the vehicle, clearly stating the reason for the failure, and rejects the registration request.

[0032] If all information verifications pass and the vehicle information is confirmed to be legal and valid, the First Cloud Control Platform generates a unique vehicle identity identifier for the vehicle. This vehicle identity identifier is generated using an encryption algorithm and consists of the vehicle's VIN code, the First Cloud Control Platform identifier, and a timestamp. This ensures that the identifier is unique, non-repeatable, and tamper-proof throughout the entire cross-cloud control system, serving as the core basis for subsequent cross-platform vehicle identity recognition and permission matching. After generation, the First Cloud Control Platform associates the vehicle identity identifier with the vehicle's VIN code and stores it in its local vehicle identity management database. Simultaneously, it sends the vehicle identity identifier back to the vehicle, which receives it and stores it in its local communication module for use when initiating various cloud control service requests and cross-platform switching requests.

[0033] Based on the generated vehicle identity identifier, the First Cloud Control Basic Platform generates initial cloud control service authorization information for the vehicle. This authorization information serves as the basis for the vehicle's basic permissions and includes the scope of cloud control services the vehicle can use, service level, validity period of permissions, and permission restrictions. After the initial cloud control service authorization information is generated, it is stored in the permission management database of the First Cloud Control Basic Platform in association with the vehicle identity identifier. At the same time, the authorization information summary is synchronized to the vehicle to serve as the basis for proving its basic permissions when the vehicle subsequently roams across platforms.

[0034] This invention provides a method for cascading and interoperating across cloud control platforms and switching vehicle services. It adopts a unified initial registration and binding and unique identity generation mechanism to achieve the effect of one-time vehicle registration across all domains and universal access across multiple platforms. This simplifies the cross-domain network access process for vehicles from the root and reduces the cost of device access management.

[0035] As an optional implementation, the first cloud control infrastructure platform and the second cloud control infrastructure platform establish a cross-cloud control infrastructure platform mutual trust relationship through a cloud control infrastructure platform registration mechanism, including: The first cloud control infrastructure platform sends a platform registration request to the second cloud control infrastructure platform; The second cloud control platform verifies the platform registration request, and generates a cross-cloud control platform mutual trust relationship after the verification is successful. The first cloud control platform and the second cloud control platform each store the trusted identifier and access policy of the other platform locally.

[0036] For example, the first cloud control infrastructure platform, as the initiator, sends a platform registration request to the second cloud control infrastructure platform. The request is transmitted through an encrypted communication channel and includes: platform identifier, platform certificate, and cloud control service capability summary. It should be noted that the cloud control service capability summary is a summary of the list of cloud control service capabilities that the platform allows to be opened across platforms.

[0037] After receiving the platform registration request from the first cloud control platform, the second cloud control infrastructure platform performs verification, including the following three aspects: First, it extracts the first cloud control infrastructure platform identifier from the request, queries the local platform management database to confirm that the identifier has no duplicate registration records or is not blacklisted, and verifies whether the identifier format conforms to the unified specifications across cloud control systems; Second, it extracts the platform certificate from the request, verifies the validity, completeness, and legality of the certificate through the verification interface provided by the CA institution, and verifies whether the platform information in the certificate is consistent with the information corresponding to the platform identifier; Third, it verifies the completeness of the cloud control service capability summary, such as whether it contains necessary information such as service name and function definition, and also verifies the rationality of the cloud control service capability summary, such as whether there are any illegal services or high-risk services without marked restrictions. If there is any unreasonable content, the second cloud control infrastructure platform can send a supplementary modification request to the first cloud control infrastructure platform to request the improvement of the cloud control service capability summary.

[0038] If all three verifications pass, the second cloud control platform confirms the legitimacy and reliability of the first cloud control platform and then generates a cross-cloud control platform mutual trust relationship. The mutual trust relationship includes core information such as the platform identifiers of both parties, the mutual trust effective time, the mutual trust validity period, and the scope of interoperable services. After generation, the second cloud control platform feeds back the mutual trust relationship information to the first cloud control platform, and at the same time stores the platform identifier and platform certificate of the first cloud control platform in the local trusted platform database.

[0039] After receiving the mutual trust relationship information from the second cloud control platform, the first cloud control platform confirms that the mutual trust relationship has been successfully established. It then locally stores the second cloud control platform's trusted identifier and access policy. The trusted identifier includes the second cloud control platform's platform identifier and platform certificate, used to verify the legitimacy of subsequent requests initiated by the second cloud control platform. The access policy consists of cross-platform service call constraints set by the first cloud control platform for the second cloud control platform. These constraints include: the scope of services that can be called, request frequency limits, concurrent connection limits, data interaction scope, and abnormal request interception rules, used to constrain the second cloud control platform's cross-platform operations and ensure the service security of the first cloud control platform. Simultaneously, the second cloud control platform also locally stores the first cloud control platform's trusted identifier and corresponding access policy, forming a two-way mutual trust system.

[0040] This invention provides a method for cascading and interoperating across cloud control platforms and switching vehicle services. Through multi-platform bidirectional trusted registration and policy binding, a stable and controllable mutual trust boundary can be established between different cloud control platforms. The access rules and security verification logic for cross-domain communication are clearly defined, effectively resisting security risks such as unauthorized platform access and malicious access.

[0041] As an optional implementation, before restoring the cloud control service state corresponding to the vehicle based on the vehicle service context information, the following steps are included: The first cloud control infrastructure platform synchronizes a summary of its cloud control service capabilities that allow cross-platform access to the second cloud control infrastructure platform. The second cloud control infrastructure platform combines cloud control service capability summaries, local security management strategies, and its own service system to match and associate the open service capabilities of the first cloud control infrastructure platform one by one, thus completing the cross-cloud service capability mapping configuration. Restore the cloud control service status corresponding to the vehicle based on the vehicle service context information, including: The second cloud control platform, based on the preset service capability mapping relationship and combined with vehicle service context information, matches and assigns equivalent cloud control service access permissions to the vehicle.

[0042] For example, the first cloud control platform proactively synchronizes its cloud control service capability summary, which it allows to be opened across platforms, to the second cloud control platform. The synchronization occurs after the two parties establish a cross-platform mutual trust relationship and before the vehicle first accesses the platform across platforms. The synchronization channel is the established cross-platform mutual trust encrypted channel to ensure that the description information is not stolen or tampered with during transmission. The specific content of the cloud control service capability summary includes: service name, service function, invocation method, interface specification, usage restrictions, and service dependency conditions.

[0043] After receiving the cloud control service capability summary synchronized from the first cloud control platform, the second cloud control infrastructure platform first organizes its own cloud control service system, clarifying the names, functions, interface specifications, and other information of all cloud control services it can provide. Then, combining the received service capability description information from the first cloud control infrastructure platform, it performs a one-to-one matching process, adhering to the principles of equivalence, interface compatibility, and consistent permissions, mapping each open service capability of the first cloud control infrastructure platform to its corresponding cloud control service capability. Based on local security control policies, it verifies the mapping relationship, blocking service capability mappings that do not conform to local security standards. For example, if a high-risk service opened by the first cloud control infrastructure platform does not conform to the local security policy of the second cloud control infrastructure platform, then establishing a mapping relationship for that service is prohibited. After completing all matching and verification, a fixed cross-cloud service capability mapping relationship table is generated. This table clearly records the one-to-one correspondence between the service capabilities of the first and second cloud control infrastructure platforms, mapping rules, adaptation parameters, permission restrictions, etc., and is stored in the mapping management database of the second cloud control infrastructure platform.

[0044] After completing the cross-cloud service capability mapping configuration, when the vehicle accesses the second cloud control platform across platforms and the second cloud control platform retrieves the vehicle service context information, the corresponding cloud control service status of the vehicle can be restored based on this information.

[0045] First, the second cloud control platform extracts the enabled service types, current status parameters of each service, and service validity identifiers recorded in the vehicle service context information. Using the enabled service types as indexes, it retrieves the cross-cloud service capability mapping table stored locally to find the service capability of the second cloud control platform corresponding to each enabled service. Next, combining the status parameters in the vehicle service context information, it matches and assigns equivalent cloud control service access permissions to the vehicle, ensuring that the vehicle obtains the same service capabilities on the second cloud control platform as on the first cloud control platform. After the allocation is completed, the second cloud control platform synchronizes the service allocation results to the vehicle. Upon receiving the data, the vehicle automatically switches to the service channel of the second cloud control platform, achieving seamless recovery of service status and ensuring that the cloud control service is uninterrupted and the user experience is consistent after the vehicle switches between platforms.

[0046] This invention provides a method for cascading and interoperating across cloud control platforms and switching vehicle services. By pre-constructing cross-cloud service capability mapping relationships and combining them with local security policies for compliance verification, it can quickly and accurately match service permissions, business functions, and resource quotas when a vehicle triggers a cross-platform switch, shortening service response latency and ensuring that the vehicle enjoys consistent and functionally equivalent cloud control services under different cloud control platforms, thus avoiding issues such as missing functions or insufficient permissions.

[0047] As an optional implementation method, a method for cascading interoperability and vehicle service switching across cloud control platforms further includes: The first cloud control platform generates vehicle service records when providing cloud control services to vehicles; The first cloud control platform sends vehicle service records to the second cloud control platform and / or the central platform.

[0048] For example, during the process of providing cloud control services to vehicles, the first cloud control platform generates vehicle service records in real time. The vehicle service records include at least one of the following: vehicle cloud control service usage, vehicle operating status, service anomaly information, and instruction execution results. The first cloud control platform sends the vehicle service records to the second cloud control platform and / or the central platform according to a preset cycle or triggering conditions, so as to realize cross-platform vehicle service data sharing, status synchronization, and operation traceability.

[0049] To better understand this solution, the following describes the data interaction process between the first cloud control platform, the second cloud control platform, and the vehicle, as follows: Figure 2 As shown, it specifically includes: S1, vehicle a registers and subscribes to services on the first cloud control platform A; S2, the first cloud control platform A synchronizes vehicle data to the second cloud control platform B; S3, vehicle a enters the service area of ​​the second cloud control platform B, and the first cloud control platform A issues a service area switching instruction for the vehicle. S4, vehicle a sends the vehicle service area switching command to the second cloud control platform B; S5, the second cloud control platform B determines the first cloud control platform A based on the vehicle service area switching instruction; S6, the second cloud control platform B initiates a cross-platform vehicle identity authentication request to the first cloud control platform A; S7, the first cloud control platform A feeds back the vehicle identity verification result and cross-platform authorization certificate to the second cloud control platform B; S8 parses the vehicle authentication result and cross-platform authorization credential to complete vehicle access; S9 assigns corresponding cloud control service capabilities to vehicles based on their vehicle identities; S10, the first cloud control platform generates vehicle service records when providing cloud control services to vehicles; S11, the first cloud control platform sends the vehicle service records to the second cloud control platform.

[0050] It should be noted that S10 and S11 do not represent the order of steps, but are only used to illustrate the function.

[0051] Finally, it should be noted that the above preferred embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail through the above preferred embodiments, those skilled in the art should understand that various changes can be made to it in form and detail without departing from the scope defined by the claims of the present invention.

Claims

1. A method for cascading interoperability and vehicle service switching across cloud control platforms, characterized in that, Applied to a system composed of a first cloud control infrastructure platform and a second cloud control infrastructure platform, the method involves establishing a cross-cloud control infrastructure platform mutual trust relationship between the first and second cloud control infrastructure platforms through a cloud control infrastructure platform registration mechanism. When the second cloud control platform receives a vehicle service area switching instruction, it initiates a vehicle cross-platform identity authentication request to the first cloud control platform based on the cross-platform mutual trust relationship. The vehicle service area switching instruction is sent when the vehicle enters the service area of ​​the second cloud control platform from the service area of ​​the first cloud control platform. The first cloud control platform verifies the vehicle's cross-platform identity authentication request and returns the vehicle identity authentication result and cross-platform authorization certificate to the second cloud control platform. The second cloud control platform completes vehicle access based on identity verification results and cross-platform authorization credentials, and assigns corresponding cloud control service capabilities to vehicles based on their identities. The second cloud control platform completes vehicle access based on identity verification results and cross-platform authorization credentials, and assigns corresponding cloud control service capabilities to the vehicle based on its identity, including: When the identity verification result and cross-platform authorization credential both pass the authentication conditions, the vehicle service context information is retrieved based on the vehicle identity, and the cloud control service status corresponding to the vehicle is restored according to the vehicle service context information, so that the vehicle can continuously receive cloud control services in the second cloud control basic platform. The vehicle service context information is generated by the first cloud control platform before the vehicle leaves its service area, and synchronized to the second cloud control platform before the vehicle enters the service area of ​​the second cloud control platform. The vehicle service context information includes at least the cloud control service type that the vehicle has enabled, service status parameters, and service validity identifier.

2. The method for cascading interoperability and vehicle service switching across cloud control platforms according to claim 1, characterized in that, Before a vehicle moves from the service area of ​​the first cloud-based control platform to the service area of ​​the second cloud-based control platform, the methods include: The first cloud control platform receives vehicle registration requests, which contain vehicle information. The first cloud control platform generates vehicle identification based on vehicle information; Based on the vehicle's identity identifier, initial cloud control service authorization information is generated for the vehicle.

3. The method for cascading interoperability and vehicle service switching across cloud control platforms according to claim 1, characterized in that, The first and second cloud control infrastructure platforms establish a cross-cloud control infrastructure platform mutual trust relationship through a cloud control infrastructure platform registration mechanism, including: The first cloud control infrastructure platform sends a platform registration request to the second cloud control infrastructure platform; The second cloud control platform verifies the platform registration request, and generates a cross-cloud control platform mutual trust relationship after the verification is successful. The first cloud control platform and the second cloud control platform each store the trusted identifier and access policy of the other platform locally.

4. The method for cascading interoperability and vehicle service switching across cloud control platforms according to claim 1, characterized in that, Before restoring the cloud control service status corresponding to the vehicle based on the vehicle service context information, the following should be included: The first cloud control infrastructure platform synchronizes a summary of its cloud control service capabilities that allow cross-platform access to the second cloud control infrastructure platform. The second cloud control infrastructure platform combines cloud control service capability summaries, local security management strategies, and its own service system to match and associate the open service capabilities of the first cloud control infrastructure platform one by one, thus completing the cross-cloud service capability mapping configuration. Restore the cloud control service status corresponding to the vehicle based on the vehicle service context information, including: The second cloud control platform, based on the preset service capability mapping relationship and combined with vehicle service context information, matches and assigns equivalent cloud control service access permissions to the vehicle.

5. The method for cascading interoperability and vehicle service switching across cloud control platforms according to claim 1, characterized in that, Also includes: The first cloud control platform generates vehicle service records when providing cloud control services to vehicles; The first cloud control platform sends vehicle service records to the second cloud control platform and / or the central platform.

Images